5G network slicing: automation, assurance and optimization of 5G transport slices

5G network slicing: automation, assurance and optimization of 5G transport slices


Hi, my name is Reza Rokui, I’m a product line manager (PLM) at Nokia. I’m responsible for the carrier-assist solution for 5G network slicing. In today’s talk we are going to talk about the 5G network slicing and how the carrier-assist solution can be used for automation, assurance, and optimization of transport slices. Network slices are an end-to-end concept as is shown here, Operator Y has three customers: BMW, Fiat and Public safety, and each one needs multiple end-to-end individual, independent, logical networks. Each of these networks are called network slices, the color represents the SLA requirement for each of them. In this example, Operator Y created five network slices. It contains RAN slices, each of the network slices contain RAN slices, which is a context in your RAN, core slices, which is a context and personality in core, and transport slices which are the connectivity between RAN and core. Each individual domain has a controller, RAN controller, core controller, transport controller, and we have an end-to-end orchestrator. Let’s get back to the Network and see how, for example, the green Infotainment slice is created in this network. The logical flow is, I have a customer, Honda, who needs an end-to-end network slice for Infotainment and the budget for the SLA is 10 Mb/s. The customer portal sends a request to the Operator. And the Operator uses its network slice blueprints, or templates, to generate a network slice profile. And after that it goes through various decompositions, triggering various actions in the network. The first thing it does, it sends a request to NFVO, which is creating the virtual RAN, virtual core, or both, if it is needed. The second portion is, it sends a request to the RAN controller to create the RAN slice, and give the personality to the RAN equipment. By the same token, it sends a request to the 5G core controller to create the core slice which is a personality in the core. And last, but not least, it sends a request to the transport slice controller to create the connectivity between this, RAN and core. At this point, it’s stitching all these slices, creating a single end-to-end network slice for a specific customer which is from the service type that is explained before. The role of the carrier-SDN solution from Nokia is to control for the transport slice, as is shown in this picture. Interface for 4 and 5 are defined in 3GPP and interface 6, that is not defined in any Standardized Development Organizations (SDOs) yet and Nokia is working towards making that one standard as well. This is the network that I am going to use for a portion of the demo. I have a transport network which is connecting the RAN to the core. Network Service Platform (NSP) as a transport slice controller, is used for three different use cases, automation transport slices, monitoring of the transport slices, and optimization. In the demo I just showed optimization, but these are the three important use cases that should be addressed by any transport slice controller. During the demo, NSP receives various connectivity APIs from the northbound, during the demo POSTMAN is simulating those APIs The transport slice controller intelligently receives that message, and creates the services, tunnel and LSP, which are needed in the network. Let’s get back to the demo. This is NSP Launchpad Service Fulfillment, and IP/MPLS Optimization and Service Supervision application are used in the context of transport slices. The first transport slice is created for the Honda Infotainment. The service time and S-NSSAI is 10 and 20, and we showed the optimization of how NSP is used for the monitoring of the transport slices. When we inject the latency of 20 milliseconds for the IGP link we will see the latency is changed. And we will see momentarily that readout happen in the network, in other words NSP intelligently monitors transport slices and we do the readout. If I put the latency back to 2 milliseconds again, nothing will happen because, in this case, the path is still valid, unless I go to the readout and after readout we will see that the NSP again brings back the original path of the LSP. In summary, carrier-SDN solution from Nokia is addressing the 5G transport slice in three important areas: automation or creation of the transport slices, assurance or monitoring of the transport slices, and closed-loop optimization. These are the three main important aspects that should be addressed with any transport slice controller. Thank you for your attention, and hopefully I see you later.

Leave a Reply

Your email address will not be published. Required fields are marked *