licing) 5G Network Slicing Figure 13.11 shows the architecture as swim lanes for eMBB, URLLC, and mMTC. Each network lane here is architected for latency, throughput, and security. This eventually helps us to manage the budget and commercial viability of the architecture, both for the network operator and users - enterprise or consumer. The diagram shows that each slice traverses unique and common network elements. 5G gNB 5G gNB Core (UP) Core (CP) (DU-Hi) Transport network 5G gNB (DU-Lo) Edge DC Local DC Central DC Application Server Core (CP) 5G gNB URLLC Transport network 5G gNB Edge DC Local DC Central DC Application Server 5G gNB Transport (CU DU) (CP UP) network Edge DC Local DC Central DC Figure 13.11 - Lane-based architecture of network slicing The task of the operators is somewhat challenging, since the 3GPP standards for 5G are still in the early stages of evolution. Automobile companies such as Telsa and Zoox are working toward autonomous cars. Cellular Vehicle-to-Everything (C-V2X) technology will rely on network slicing and will likely be deployed on a URLLC slice to provide ultra-low latency. As 3GPP standards mature over time, operators will add more capabilities, leading to more commercially viable enterprise use cases in both B2B and B2B2C scenarios. Let us next look at Figure 13.12, which shows 3PGG 5G network architecture for a non-roaming scenario. Note NSSF as part of this architecture. Network slicing architecture and design Application Function Access and Mobility Management Function Authentication Server Function Data Network Nausf Network Exposure Function NF Repository Function Network Slice Selection Function Policy Control Function (R)AN (Radio) Access Network Session Management Function Unified Data Management (R)AN User Plane Function User Equipment Figure 13.12 - 5G network architecture (non-roaming) NSSF is a network function that is responsible for selecting the appropriate network slice for a particular device or application. It is based on the requirements and the capabilities o