Bending the Network OPEX Curve with SON
http://media.telecoms.com/tv/webinars/actix/ActixSONwebinarApril2010.f4v
Telecoms.com
news
Events
MVNOs World Congress
- 06-07 June 2023
- View Event
Future Enterprise Networks: Private 5G and Edge
- 15-15 June 2023
- View Event
NGON
- 21-22 June 2023
- View Event
UK comms regulator @Ofcom has released an update to its Connected Nations report, which shows the country is nearin hhttps://t.co/D4fdJpWwuE
28 May 2023 @ 13:15:10 UTC
Facebook owner @Meta has been issued a 1.2 billion fine for ##GDPRviolations in relation to data on European citiz hthttps://t.co/xMcjvqVNUQ
28 May 2023 @ 11:10:10 UTC
President Biden has nominated telco lawyer Anna Gomez for Commissioner of the US Federal Communications Commission hhttps://t.co/So1MdLMx9J
28 May 2023 @ 09:20:11 UTC
is SON depending on planning tool DB?
If so, what is the risk with using non perfect data in planning tool?
Hi Ziv,
Actix currently works on purely operational SON solutions as well as SON solutions for network rollout. Functionality of typical planning tolls are key for the network rollout. Nevertheless, Actix tries to reduce the risk of in-perfect planning data by generating them in the SON system based on operational configuration data.
Neil
Hi!
Very interesting overview!
Which inputs are you using for your SON-solution?
You mentioned RET. How about Smart-antennas?
Thanks,
Erik
Hi Erik,
One of the strenghts of Actix is the correlation of multiple data sources for SON. This includes PM stats, Call Traces, Configuration Data, Alarms, Drive Surveys, Predictions as well as Customer Trouble tickets and marketing forcasts. Smart antennas have a very high potential for interference reduction. Nevertheless, you still need a pilot.
Thanks,
Neil
Thanks for the presentation. Can you please send me a copy of the presentation?
Hi Rani,
We have your email address and will contact you directly soon.
Neil
I would also like to receive the presentation.
Thanks/Fernando
Hello,
will it be possible to publish / send the ppt and contacts for more specific details about the SON application to 2G/3G networks.
thanks
Hi Mohamed,
We have your email address – we’ll contact you directly soon.
Neil
Can you share some detailed case studies for the deployments for SON for 2G/3G? Who are the ISV and NEP supporting it for 2G/3G deployments?
Plz share the Presentation. Good presentation
Please share some case studies for deployments of SON for the 2G/ 3G network and how they have reduced the OPEX of the operators.
Thanks for the presentation. Can you please send me a copy of the presentation?
How difficult would it be to adapt the SON functionality that you developed for NEC for use by other network vendors?
Hi Neil,
Except for some specific interfaces and a few specific algorithms for NEC, the Actix SON Framework and all SON use cases, SON processes and SON algorithms are generic. The Actix SON framework also allows 3rd-parties to develop their own SON pocesses and algorithms.
Neil
Would this need a ‘true’ IMS implementation, or can NGN or a ‘best of breed/need’ IP setup also be used?
Also interested in recieving the presenation, thanks.
What is the status of the objective measurement criteria to measure the SON benifits and who is defining this criteria?
Is this being addressed in the standards group?
Hi Sunil
The Actix view is that the benefits of SON will be measured by technical criteria as well as commercial criteria like time saving, effort minimization and process shortcuts. The technical criteria can be tracked more accurately but the majority of the impact of SON is expected commercially.
In terms of standards – NGMN has a working group that is building some assessment criteria. Actix currently works with the NGMN and various individual customers on scoping success criterias for SON and its measures.
Neil
SON has been slow in standards because it is revenue-destroying for the major network vendors. Also, limited operator push (with a few honourable exception). Operators who farmed out most of their R&D to Tier 1s are paying a price. Also note that whilst SON is currently being defined for LTE, implementing all the features is optional / commercial decision for Network Vendors
Hi Kit,
Great point and agree. Some vendors though will use more complete SON feature sets for competitive differention – especially those without large services arms to maintain.
Neil
Hello,
Thanks for the presentation. Really interesting. I got some questions:
1) Which vendors / techs do you support in your SON solution?
2) How do you automatically set parameters in the network ? You require direct access to the OSS from inside the operator right ?
3) Actix SON needs to run from inside the operator or can be run remotly (web-based) ?
4) How do you change e-tilt automatically ?
Thank you!
Jose Ruy
Hi Jose Ruy,
1) SON is vendor neutral. Actix support most major vendors throughout its product lines.
2) That’s right. Almost all Closed Loop SON processes require direct access to the OSS.
3) Actix allows both, an operator internal usage as well as externally hosted operation (given the right network access)
4) I need to get back to you on this.
Neil
Hi Neil,
Can you please share your presentation.
Many Thanks.
Hi Nishita,
We have your email address and will contact you directly.
Thanks,
Neil
Great presentation … can u please send a copy of the slides
I quite agree with starting from 2G/3G systems before LTE. Can you please share this presentation?
thanks
It appears that Actix provides a centralized SON solution. It seems that many of the SON capabilities are better provided with distributed algorithms. Can you comment on C-SON vs. D-SON vs. Hybrid?
Hi Tom,
Actix believes the overall SON framework will be a hybrid mix between centralized SON activities and distributed SON activities. We have implemented a hybrid system with one of our customers. The future will show which individual processes and algorithms are more effective as C-SON implementation or as D-SON implementation. In general Actix does see a trend towards C-SON. We believe a major operator requirement on SON processes is to operate across different RAN technologies and RAN equipment vendors, which naturally is difficult for D-SON. In addition back to an early comment vendor D-SON implementations will be late due to a lack of commitment.
Neil