Edge & 5G
Gain crucial understandings of Edge software and 5G concepts with Intel® industry experts
86 Discussions

Network Slicing Set to Accelerate Non-Public 5G Network Deployments

0 0 708
Release 16 of the 5G standard advances network slicing, non-public networks. (Source_ Intel) Release 16 of the 5G standard advances network slicing, non-public networks. (Source: Intel)

5G cellular technology has garnered considerable excitement among consumers primarily because of faster speeds, with shortened latencies and higher bandwidth as much-advertised calling cards.

Beyond that consumer market is another world of capabilities in non-public or private networks (NPNs), which represent one of the telecom industry's most promising growth sectors. Work is already well underway. By the end of last year, more than 100 companies worldwide had started testing private 5G deployments, collectively investing hundreds of millions of dollars in labor and equipment [1].

Use cases include Smart Manufacturing (sometimes referred to as Industry 4.0 or the Fourth Industrial Revolution), and the enormous potential of the Internet of Things (IoT). Augmented and virtual reality (AR/VR) is another large opportunity already catching on for technical training, shopping, gaming, and other applications.

By one estimate from Deloitte Insights, one-third of the total private 5G opportunity will come from factories and warehouses over the next five years, with another one-third coming from airports, ports, and logistics hubs [1].

5G cellular technology is a key enabler for non-public networks. One major shift is wider adoption of machine-to-machine communications, including massive Machine Type Communications (mMTC). The new capabilities introduced in 5G - like Network Slicing, reduced latency, higher bandwidth, and secure communications capabilities - are essential in factories deploying wirelessly connected robots, for example, using the Ultra Reliable Low Latency Communications (URLLC) enhancements. The increased availability of licensed, unlicensed, and shared spectrum is further fueling the growth of non-public networks.

I recently collaborated with Sue Rudd, Director, Networks and Service Platforms research at Strategy Analytics, in a webinar entitled "Multi-Domain Orchestration Makes 5G Network Slicing Real for Non-Public Networking in 2021" which is available as a replay. It provides a more detailed look at 5G non-public networking.

In addition, Intel sponsored a recently published white paper, authored by Sue Rudd, which can be accessed at the Strategy Analytics site: Multi-Domain Orchestration makes 5G Network Slicing Real for Non-Public Networking (NPN) in 2021.

Recently enabled capabilities of Network Slicing are bringing the economics of public networks to private, secure domains, further opening new economic opportunities for a variety of enterprises. The concept of network slicing is not new; since the early definition of 4G, separate services could be enabled with the Access Point Name (APN) capability. However, it was a challenge to have dedicated MME/S-GW (mobility management entity/serving gateways) since their selection relies on the geographical distribution of the network.

In 4G's Rel-13, a concept similar to network slicing was defined for a set of subscribers, known as a dedicated core network (DECOR). DECOR enables an operator to deploy multiple dedicated core networks (DCNs) within a Public Land Mobile Network (PLMN) with each DCN consisting of one or multiple CN nodes. DECOR provides the capability to have a dedicated MME/SGW per user equipment (UE) type.

In Rel-14, enhancements to DECOR, called eDECOR, were introduced by adding the assistance information in the UE, and by reducing the signaling needed for a UE to select a DCN. However, with DECOR and eDECOR, it is not possible to employ specific slicing with user equipment simultaneously being able to access multiple slices. Radio Access Network (RAN) slicing was also not supported.

Network slicing was first supported in 3GPP Rel-15, allowing network operators to deploy multiple, separate, end-to-end logical networks, either using separate infrastructures or sharing the same network. Each network slice can be customized independently for different vertical applications or business scenarios.

Just as vertical slices can be used to serve different needs within a particular vertical, horizontal slices can be created to support similar classes of devices, which can then be used to serve end users in multiple verticals. For example, a low-power network slice could be used to connect sensors from a variety of IoT-enabled devices.

Rel-16 introduced support for network slice specific authentication and authorization to enable support for separate authentication and authorization per network slice. The trigger is based on UE subscription information and the operator's policy.

As mentioned in Sue Rudd's recently published paper [2], Rel-16 also enhances management and orchestration. The 3GPP management system provides multi-tenancy support, by associating different tenants with different sets of management capabilities. Every tenant may be authorized to access and consume management services that the operator makes available to this tenant based on the Service Level Agreement (SLA).

Rel-16 also supports a variety of business role models for network slicing that are possible in a 5G system. The Rel-16 enhancements allow a third party to monitor the activities of their UEs when using the network slice, and to monitor resource usage within the network slice. These capabilities are added to support negotiation between the mobile network operator (MNO) and the third party in the service agreement.

Also noted by Rudd, network slicing requires fully automated orchestration capabilities; otherwise, deploying various custom behaviors could be cost prohibitive. With a growing number of network slices, automation of operation is of paramount importance. Operating multiple network function instances and configurations can easily increase operation costs. Network slicing and multi-domain orchestration together create a flexible, scalable, and cost-effective programable network, capable of adapting to the needs of any service or user.

The 3GPP Rel 16 specifications defined support for non-public networks (NPN) as part of a broad study on Industrial IoT which included three key building blocks: 5G LAN-type services, Time Sensitive Communications, and Non-Public Networks.

An NPN may be deployed as a Stand-alone Non-Public Network (SNPN), in which case it is operated by an NPN operator and is not relying on network functions provided by a public land mobile network (PLMN). An NPN may also be deployed as a Public Network Integrated NPN. These PNI-NPNs are NPNs made available via PLMNs by means of dedicated distributed network names (DNNs), or by one or more Network Slice instances allocated for the NPN [3].

Remote provisioning is one of many things planned in the forthcoming Rel-17. Study is ongoing for enhanced support of stand-alone non-public networks, with credentials owned by an entity separate from the SNPN, with onboarding and remote provisioning on the SNPN.

These non-public networks will accelerate the digital transformation that has picked up speed over the past year of working and studying at home. The variety of applications is truly fascinating, as companies embark on building their own private 5G networks for manufacturing, sports facilities, and other sectors pursuing better performance and reduced operational costs. An IDC study estimates that LTE/5G private networks will become a multi-billion-dollar industry in the next five years [4].

[1] Deloitte Insights, Private 5G networks - Enterprise untethered, 2020.

[2] Strategy Analytics, Multi-Domain Orchestration Makes 5G Network Slicing Real for Non-Public Networking in 2021, January 2021.

[3] 3GPP TS 23.501: System architecture for the 5G System (5GS)

[4] IDC Market Forecast - Doc # US47085720, Worldwide Private LTE/5G Infrastructure Forecast, 2020–2024.

Notes & Disclaimers

© Intel Corporation. Intel, the Intel logo, and other Intel marks are trademarks of Intel Corporation or its subsidiaries. Other names and brands may be claimed as the property of other

About the Author
Puneet Jain is a Senior Principal Engineer and Director of Technical Standards in the Next Generation and Standards (NGS) Group at Intel Corporation. He is head of the Network Standards team and is responsible for driving research and standardization on end-to-end network architecture for mobile broadband technologies such as 5G, Beyond 5G, and 6G. Puneet is Chairman of 3GPP SA WG2 since 2019. He has also served as 3GPP SA WG2 Vice-Chairman (2015 - 2019) and Rapporteur of several study/work items on Machine Type Communication (MTC)/Cellular Internet of Things (CIoT) in 3GPP SA WG2. Puneet has also served as oneM2M Steering Committee Vice-Chairman (2014–2016). In his previous roles at Intel, he was chairman of WiMAX-3GPP interworking sub-team at WiMAX Forum, involved in design and development of ATM RAN reference implementation for Intel Network Processors.