LTE and 5G 1.0 5.pdf

On to 5G! ● ● ● goal: 10x increase in peak bitrate, 10x decrease in latency, 100x increase in traffic capacity over 4G 5G NR (new radio): ● two frequency bands: FR1 (450 MHz–6 GHz) and FR2 (24 GHz–52 GHz): millimeter wave frequencies not backwards-compatible with 4G ● MIMO: multiple directional...

On to 5G! ● ● ● goal: 10x increase in peak bitrate, 10x decrease in latency, 100x increase in traffic capacity over 4G 5G NR (new radio): ● two frequency bands: FR1 (450 MHz–6 GHz) and FR2 (24 GHz–52 GHz): millimeter wave frequencies not backwards-compatible with 4G ● MIMO: multiple directional antennae ● millimeter wave frequencies: much higher data rates, but over shorter distances ● pico-cells: cells diameters: 10-100 m ● massive, dense deployment of new base stations required Wireless and Mobile Networks: 7- 20 5G Usage scenarios • Enhanced Mobile Broadband (eMBB): • Support very high data rates. 5G performance targets recommended by ITU suggest, peak data rate of 20 Gbps in downlink and 10 Gbps in uplink • Ultra-Reliable and Low Latency Communication (URLLC): • Support <1 ms latency in access network • Support <10 ms latency end to end • For low-latency applications such as AR/VR, V2X communication, ehealth services. • Reliability > 99% (meaning that a packet reaches the destination in the allowed latency budget in 99% of the cases) • Massive machine Type Communication (mMTC): • Support very high connection density. • Smart cities, Industrial IoT cases fall under this category. • generally these applications expect low data rates. • Between 10,000 and 1,000,000 devices per km². 4G shortfalls • Enhanced Mobile Broadband (eMBB): • For 4G networks, peak data rate of 1000 Mbps in downlink and 500 Mbps in uplink. This data rate is insufficient to support the eMBB scenarios. • Ultra-Reliable and Low Latency Communication (URLLC): • Multiplayer gaming applications, industrial robots, self-driving cars and many such time-critical applications demand quick response – at times requiring network latency less than 1 ms, which 4G networks struggle to achieve or can't manage at all • Network Slicing: • There is a need to separate users, devices and applications that require a different quality of service for different use cases. From 4G to 5G • The 4G Mobility management entity (MME) functionality has been divided into: • AMF (Access and mobility function): handles the UE registration and mobility management • SMF (session management function): handles the PDU session management • AUSF (authentication server function): handles the UE authentication part based on authentication vectors from Unified Data Management (which stores the UE subscription data and user-context). • The 4G S-GW and P-GW have been divided into : • SMF (session management function): handles the UE IP address assignment and UPF selection • UPF (user plane function): acts as PDU session anchor – it is responsible for packet routing, QoS enforcement and charging functionality New 5G core functions • Network Slice Selection Function (NSSF): NSSF helps in setting up multiple virtual network slices of the RAN, core and transport networks to meet specific service requirements. • Network Exposure Function (NEF): This is the capability exposure function used by the external network entities to interface with 5G core network. • Network Repository Function (NRF): It aids the 5G services based architecture. It acts as repository of all services offered by the different network functions. 4G to 5G The 5G base station : gNB • In order to support high data rates and low latency needs of 5G, the access network has been revamped. • At the access side, the 4G eNodeB (eNB) is now called 5G gNB (nextgeneration node B): • The gNB is split into two parts: • gNB centralized unit (gNB-CU) and gNB distributed unit (gNB-DU). • Both are connected to each other using ethernet based IP midhaul network. • Generally, gNB-CU is virtualized and runs in context of virtualized core or virtualized edge. • gNB-DU might be integrated with the radio head or can be virtualized and run on the edge or cloud.