Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

full Table of Contents for  TS 23.501  Word version:   16.3.0

Top   Up   Prev   Next
1…   3…   4…   4.2.4   4.2.5…   4.2.8            4.2.9…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8   5…   5.4…   5.6…   5.7…   5.8…   5.10…   5.16…   5.17   5.18…   5.27…   5.31   5.32   5.33   5.34   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…


5.18  Network SharingUp
5.18.1  General concepts
A network sharing architecture shall allow multiple participating operators to share resources of a single shared network according to agreed allocation schemes. The shared network includes a radio access network. The shared resources include radio resources.
The shared network operator allocates shared resources to the participating operators based on their planned and current needs and according to service level agreements.
Reproduction of 3GPP TS 23.501, Figure 5.18.1-1: A 5G Multi-Operator Core Network (5G MOCN) in which multiple CNs are connected to the same NG-RAN
Figure 5.18.1-1: A 5G Multi-Operator Core Network (5G MOCN) in which multiple CNs are connected to the same NG-RAN
5.18.2  Broadcast system information for network sharingWord-p. 227
5.18.2a  PLMN list handling for network sharing
5.18.3  Network selection by the UE
5.18.4  Network selection by the networkWord-p. 228
5.18.5  Network Sharing and Network Slicing
5.19  Control Plane Load Control, Congestion and Overload Control
5.19.1  General
In order to ensure that the network functions within 5G System are operating under nominal capacity for providing connectivity and necessary services to the UE. Thus, it supports various measures to guard itself under various operating conditions (e.g. peak operating hour, extreme situations). It includes support for load (re-)balancing, overload control and NAS level congestion control. A 5GC NF is considered to be in overload when it is operating over its nominal capacity resulting in diminished performance (including impacts to handling of incoming and outgoing traffic).
5.19.2  TNLA Load Balancing and TNLA Load Re-Balancing
5.19.3  AMF Load BalancingWord-p. 229
5.19.4  AMF Load Re-Balancing
5.19.5  AMF Control Of OverloadWord-p. 230
5.19.6  SMF Overload ControlWord-p. 231
5.19.7  NAS level congestion control
5.20  External Exposure of Network CapabilityWord-p. 236
The Network Exposure Function (NEF) supports external exposure of capabilities of network functions. External exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability and Analytics reporting capability. The Monitoring capability is for monitoring of specific event for UE in 5G System and making such monitoring events information available for external exposure via the NEF. The Provisioning capability is for allowing external party to provision of information which can be used for the UE in 5G System. The Policy/Charging capability is for handling QoS and charging policy for the UE based on the request from external party. The Analytics reporting capability is for allowing an external party to fetch or subscribe/unsubscribe to analytics information generated by 5G System.
5.20a  Data Collection from an AF [R16]Word-p. 237
An NF that needs to collect data from an AF may subscribe/unsubscribe to notifications regarding data collected from an AF, either directly from the AF or via NEF. The data collected from an AF is used as input for analytics by the NWDAF. The details for the data collected from an AF as well as interactions between NEF, AF and NWDAF are described in TS 23.288.
5.21  Architectural support for virtualized deployments
5.21.0  General
5GC supports different virtualized deployment scenarios, including but not limited to the options below:
  • A Network Function instance can be deployed as distributed, redundant, stateless, and scalable NF instance that provides the services from several locations and several execution instances in each location.
  • A Network Function instance can also be deployed such that several network function instances are present within a NF set provide distributed, redundant, stateless and scalability together as a set of NF instances.
  • The SEPP, although not a Network Function instance, can also be deployed distributed, redundant, stateless, and scalable.
  • The SCP, although not a Network Function instance, can also be deployed distributed, redundant, and scalable.
5.21.1  Architectural support for N2
5.21.2  AMF Management
5.21.3  Network Reliability support with Sets [R16]Word-p. 243
5.21.4  Network Function/NF Service Context Transfer [R16]
5.22  System Enablers for priority mechanism
5.22.1  General
The 5GS and the 5G QoS model allow classification and differentiation of specific services such as listed in clause 5.16, based on subscription-related and invocation-related priority mechanisms. These mechanisms provide abilities such as invoking, modifying, maintaining, and releasing QoS Flows with priority, and delivering QoS Flow packets according to the QoS characteristics under network congestion conditions.
Subscription-related Priority Mechanisms include the ability to prioritize flows based on subscription information, including the prioritization of RRC Connection Establishment based on Unified Access Control mechanisms and the establishment of prioritized QoS Flows.
Invocation-related Priority Mechanisms include the ability for the service layer to request/invoke the activation of prioritized QoS Flows through an interaction over Rx/N5 and packet detection in the UPF.
5.22.2  Subscription-related Priority MechanismsWord-p. 245
5.22.3  Invocation-related Priority Mechanisms
5.22.4  QoS Mechanisms applied to established QoS FlowsWord-p. 246
5.23  Supporting for Asynchronous Type CommunicationWord-p. 247
Asynchronous type communication (ATC) enables 5GC to delay synchronizing UE context with the UE, so as to achieve an efficient signalling overhead and increase system capacity.
5.24  3GPP PS Data OffUp
This feature, when activated by the user, prevents traffic via 3GPP access of all IP packets, Unstructured and Ethernet data except for those related to 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 22.011 [25] and TS 23.221 [23], that are the only allowed services when the 3GPP PS Data Off feature has been activated by the user. The 5GC shall support 3GPP PS Data Off operation in both non-roaming and roaming scenarios.
5.25  Support of OAM FeaturesWord-p. 248
5.26  Configuration Transfer Procedure
The purpose of the Configuration Transfer is to enable the transfer of information between two RAN nodes at any time via NG interface and the Core Network. An example of application is to exchange the RAN node's IP addresses in order to be able to use Xn interface between the NG-RAN node for Self-Optimised Networks (SON), as specified in TS 38.413 [34].

Up   Top   ToC