Since our last blog on this area, the 3GPP standards supporting 5G network data analytics have moved on quite considerably so it’s worth pausing for a moment to see what’s changed. If you didn’t know before reading this, network analytics is set to transform the way 5G networks and beyond will operate, offering features such as self-healing, autonomous network optimization, predictive fault diagnosis and user experience optimization.
When the concept of analytics was introduced to 5G by the 3GPP, the list of capabilities was pretty underwhelming; essentially, if you were interested in Network Slice Load Level, fantastic. Otherwise, there wasn’t really anything else to get excited about. However, in Release 16 and Release 17 of the 3GPP specifications, both the suite of potential analytics use cases and the architecture supporting network analytics has evolved considerably.
To begin with, what’s changed about the architecture? Originally, we had the NWDAF (Network Data Analytics Function), the critical component of the analytics architecture which will harvest the raw data, process it and produce meaningful analytical data. Along the way, ML (Machine Learning) trained models can be generated by the NWDAF and utilized by other NWDAFs in the network, with a view to eventually having full closed loop automation to assist with a wide range of network optimization tasks. From an architectural perspective, the NWDAF remains the main analytics function, but we now have support from three additional functions, as outlined in Figure 2.
These functions are detailed as follows:
All of these functions are considered to be part of the SBA (Service Based Architecture) and as such, the 3GPP have defined each of their Service Based Interfaces. For example, the Nadrf SBI defines the exact format a request to store analytics data should follow. Alternatively, the Nnwdaf SBI defines the exact way in which a network function can subscribe to the delivery of specific analytics data, amongst many other capabilities.
As can be seen in Figure 3, the 3GPP have now standardized a much wider range of network analytics use cases, moving way beyond the original Slice Load level requirement.
The various use cases can briefly be described as follows:
In all of the above cases, analytics data can be generated by the NWDAF on a statistical basis (historical or present), as well as a predictive basis. Moreover, different combinations of analytics can be used together e.g. based on historical usage of a particular cell and the device’s predicted mobility, the network can forecast that in 10mins time, the device’s QoS may diminish and as such preventative action can be taken to protect the user’s service experience.
At the time of writing, we’re some way off seeing these analytics in live 5G networks, particularly when areas such as network slicing are in their infancy. However, it’s clear that the impact these analytics can have on many different facets of the network is significant. Although we may not see all of these use cases as a commercial reality, there’s a huge amount of interest from vendors and service providers alike; hopefully, there’s enough interest to see analytics move beyond what we see here, with ML and AI unlocking the door to a huge range of new network analytics features.
For more information on this topic, check out our latest course “5G Network Data Analytics” or our other 5G training courses.