Myth vs. Reality in Private Network Slicing
Not all slices are created equal

Myth vs. Reality in Private Network Slicing

Overview

The network slicing concept in 5G is not new, as this builds on the LTE concept (built on 3G..) of wireless access prioritization.

Since wireless spectrum is a precious resource, maximizing the usage and catering to various needs of the applications dictates that wireless access be segmented for different use cases.

For example, if a user is watching a video stream, little buffering will not impact user experience, user can be given bandwidths with some smaller gaps. However, voice calls cannot have gaps.

5G Network slicing takes this concept further by combining the remaining network elements, thus enabling end-to-end network slicing. Slicing allows services to differentiate from each other by leveraging total network experience. For example, a private Network slice adds network separation (VPN-like) as the key offering. Similarly, mission-critical services such as MCPTT leverages network slicing to prioritize traffic across all the network segments such as wireless access, transport, and core networks.

Network slicing

Figure 1: Network Slice (source: Reference 1)

One can also visualize the end-to-end network slicing as a triathlon of different network segments, i.e., wireless, transport, and core networks. One has to compete and allocate resources in all the parts to offer a winning experience.

Triathlon

Figure 2: Triathlon

Separating Hype from Reality

1.    End to End network slicing for bandwidth-sensitive applications:  Normally, wireless access is the constrained layer in any network. It makes sense to allocate and prioritize traffic on wireless layers (e.g., QCI, 5GQI) if there is contention. However, in private networks with 10 Gig LAN connections, “end to end” network slicing does not add much value, given that the constraints are not the same.

2.    “Private” Network slice from the macro: “Private” aspect in this slice type is subjective. Any applications/ networks requiring private slices must carefully inspect every part of the network components to ensure it offers an authentic private slice.

References:

1.    https://www.gsma.com/futurenetworks/wp-content/uploads/2017/11/GSMA-An-Introduction-to-Network-Slicing.pdf



Omprakash Trigunait

IIoT / Industry 4.0 / AI / ML / CoE for L&D/CIA/ Knowledgebase Management / Information Architect/AI/2G/3G/4G/5G Radio & Core /Public Safety/Learning & Knowledge/Telecom IA/IoT/MEC Consultant/DITA/XML/CMS

3 年

Thanks for sharing. This will help me to understand network slicing better.

Good stuff Rajesh. The point about slicing on a private network is something I see confusion on - but logically, the need for both at the same time is questionable.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了