d TWAG for non- AMF & multiple N3 to UPFs. 3GPP access Unified registration, authentication, session management for 3GPP, non-3GPP access (including untrusted, trusted WLAN and in Rel Procedures Access-dependent procedures 16 also fixed access), common N1/N2/N3 for 3GPP and non-3GPP access, enabling seamless mobility. E2E multiple slices per UE with shared AMF, Network slicing Single slice per UE with multiple PGW slicing aware RAN and per slice SMF/UPF (potentially slice specific PCF, NRF, etc.). QoS flow-based framework, including QoS model QCI-based bearers reflective QoS support. Native support for cloud-based deployment with service-based architecture and servicebased Cloud-native Possible but node-based (box-driven) interfaces within 5GC CP; definition of NF services. Support for edge computing. Application Local applications Support LIPA/SIPTO-based deployment influence on traffic routing. Improved Session model including different Supports full IP address preservation for Session and Service Continuity modes. Support centralized GWs or break before make solution Session/service continuity for concurrent (e.g., local and central) access to for local GWs (LIPA/SIPTO); service continuity a data network. No service continuity with with 2G/3G PS and SRVCC 2G/3G PS and no support of SRVCC. Unified Policy framework for access and mobility control, QoS and charging enforcement, Policy framework Support SM/QoS-based policies policy provisioning in the UE; introducing NWDA (Network Data Analytics) for data analytics support. SMS over NAS (including over Non-3GPP), SMS over NAS over 3GPP access, IMS services support of IMS services over 3GPP access and Services supported over 3GPP access and non-3GPP access, LCS, non-3GPP access, LCS, MPS, MCPTT, mobile MPS, MCPTT, mobile broadband broadband. Support for RRC inactive (RRC state machine Support for RRC INACTIVE state Support not specified includes 3 states: RRC IDLE, INACTIVE, and CONNECTED). Figure 9.12 - The main differences between the EPC and 5GC In this comparis