hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5 High-level requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5.1 Migration to 5G | 5.1.1 Description
The 5G system supports most of the existing EPS services, in addition to many new services. The existing EPS services can be accessed using the new 5G access technologies even where the EPS specifications might indicate E-UTRA(N) only. Only new or changed service requirements for new or changed services are specified in this TS. The few EPS capabilities that are not supported by the 5G system are identified in clause 5.1.2.2 below. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5.1.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5.1.2.1 Interworking between 5G systems | The 5G system shall support a UE with a 5G subscription roaming into a 5G Visited Mobile Network which has a roaming agreement with the UE's 5G Home Mobile Network.
The 5G system shall enable a Visited Mobile Network to provide support for establishing home network provided data connectivity as well as visited network provided data connectivity.
The 5G system shall enable a Visited Mobile Network to provide support for services provided in the home network as well as provide services in the visited network. Whether a service is provided in the visited network or in the home network is determined on a service by service basis.
The 5G system shall provide a mechanism for a network operator to limit access to its services for a roaming UE, (e.g. based on roaming agreement).
The 5G system shall provide a mechanism for a network operator to direct a UE onto a partnership network for routing all or some of the UE user plane and associated control plane traffic over the partnership network, subject to an agreement between the operators. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5.1.2.2 Legacy service support | In principle, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468). However,
- voice service continuity from NG-RAN to GERAN shall not be supported,
- voice service continuity from NG-RAN to UTRAN CS should be supported (see Note),
- voice service continuity from GERAN to NG-RAN shall not be supported,
- voice service continuity from UTRAN to NG-RAN shall not be supported,
- CS fallback from NG-RAN to GERAN shall not be supported,
- CS fallback from NG-RAN to UTRAN shall not be supported,
- seamless handover between NG-RAN and GERAN shall not be supported,
- seamless handover between NG-RAN and UTRAN shall not be supported,
- access to a 5G core network via GERAN or UTRAN shall not be supported,
- video service continuity between 5GS and UMTS shall not be supported,
- IP address preservation for PS service when UE moves between 5GS and GSM/UMTS shall not be supported, and
- Service continuity between 5GS and CDMA2000 shall not be supported.
NOTE: Architectural or protocol changes needed to support voice service continuity from NG-RAN to UTRAN CS are expected to have minimum impact on architecture, specifications, or the development of the 5G New Core and New Radio. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 5.1.2.3 Interoperability with legacy 3GPP systems | The 5G system shall support mobility procedures between a 5G core network and an EPC with minimum impact to the user experience (e.g. QoS, QoE). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6 Basic capabilities | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1 Network slicing | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.1 Description | Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g. priority, charging, policy control, security, and mobility), differences in performance requirements (e.g. latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g. MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO).
A network slice can provide the functionality of a complete network, including radio access network functions, core network functions (e.g. potentially from different vendors) and IMS functions. One network can support one or several network slices. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.2.1 General | The serving 5G network shall support providing connectivity to home and roaming users in the same network slice.
In shared 5G network configuration, each operator shall be able to apply all the requirements from this clause to their allocated network resources.
The 5G system shall be able to support IMS as part of a network slice.
The 5G system shall be able to support IMS independent of network slices.
For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to support the UE to access the most suitable network slice in minimum time (e.g. based on the location of the UE, ongoing applications, UE capability, frequency configured for the network slice).
5G system shall minimize signalling exchange and service interruption time for a network slice, e.g. when restrictions related to radio resources change (e.g., frequencies, RATs).
For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice.
The 5G system shall be able to minimize power consumption of a UE (e.g. reduce unnecessary cell measurements), in an area where no authorized network slice is available.
When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the active applications (e.g., providing early notification).
NOTE 1: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE.
The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference).
The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs
For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply:
- When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to:
- be registered to more than one VPLMN simultaneously; and
- use network slices from more than one VPLMN simultaneously
- The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs.
- The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices.
NOTE 2: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.2.2 Management | The 5G system shall allow the operator to create, modify, and delete a network slice.
The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice.
The 5G system shall allow the operator to configure the information which associates a UE to a network slice.
The 5G system shall allow the operator to configure the information which associates a service to a network slice.
The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.
The 5G system shall support a mechanism for the VPLMN, as authorized by the HPLMN, to assign a UE to a network slice with the needed services or to a default network slice.
The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator.
Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.
Creation, modification, and deletion of a network slice shall have no or minimal impact on traffic and services in other network slices in the same network.
The 5G system shall support scaling of a network slice, i.e. adaptation of its capacity.
The 5G system shall enable the network operator to define a minimum available capacity for a network slice. Scaling of other network slices on the same network shall have no impact on the availability of the minimum capacity for that network slice.
The 5G system shall enable the network operator to define a maximum capacity (e.g., number of UEs, number of data sessions) for a network slice.
The 5G system shall enable the network operator to define a priority order between different network slices in case multiple network slices compete for resources on the same network.
The 5G system shall support means by which the operator can differentiate policy control, functionality and performance provided in different network slices. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.2.3 Network slice constraints | The 5G system shall support a mechanism to prevent a UE from trying to access a radio resource dedicated to a specific private slice for any purpose other than that authorized by the associated third-party.
NOTE 1: UEs that are not authorized to access a specific private slice will not be able to access it for emergency calls if the private slice does not support emergency services.
The 5G system shall support a mechanism to configure a specific geographic area in which a network slice is accessible, i.e. a UE shall be within the geographical area in order to access the network slice.
The 5G system shall support a mechanism to limit a UE to only receiving service from an authorized slice.
For a UE authorized to access to multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall minimize service interruption time when the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications).
For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice.
NOTE 2: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN).
The 5G system shall support a mechanism to prevent a UE from registering with a network slice when the maximum number of UEs for that slice are registered.
The 5G system shall support a mechanism to prevent a UE from establishing a new data session within a network slice when the maximum number of data sessions for that slice are established.
NOTE 3: Based on national/regional regulations and operator policy, exemptions can be provided for UEs configured for priority services (e.g., MPS) and for priority service sessions. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.1.2.4 Cross-network slice coordination | The 5G system shall support a mechanism to provide time stamps with a common time base at the monitoring API, for services that cross multiple network slices and 5G networks.
The 5G system shall provide suitable APIs to coordinate network slices in multiple 5G networks so that the selected communication services of a non-public network can be extended through a PLMN (e.g. the service is supported by a slice in the non-public network and a slice in the PLMN).
The 5G system shall provide a mechanism to enable an MNO to operate a hosted non-public network and private slice(s) of its PLMN associated with the hosted non-public network in a combined manner. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.2 Diverse mobility management | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.2.1 Description | A key feature of 5G is support for UEs with different mobility management needs. 5G will support UEs with a range of mobility management needs, including UEs that are
- stationary during their entire usable life (e.g. sensors embedded in infrastructure),
- stationary during active periods, but nomadic between activations (e.g. fixed access),
- mobile within a constrained and well-defined space (e.g. in a factory), and
- fully mobile.
Moreover, some applications require the network to ensure seamless mobility of a UE so that mobility is hidden from the application layer to avoid interruptions in service delivery while other applications have application specific means to ensure service continuity. But these other applications can still require the network to minimize interruption time to ensure that their application-specific means to ensure service continuity work effectively.
With the ever-increasing multimedia broadband data volumes, it is also important to enable the offloading of IP traffic from the 5G network onto traditional IP routing networks via an IP anchor node close to the network edge. As the UE moves, changing the IP anchor node can be needed in order to reduce the traffic load in the system, reduce end-to-end latency and provide a better user experience.
The flexible nature of a 5G system will support different mobility management methods that minimize signalling overhead and optimize access for these different types of UEs. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.2.2 General requirements | The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs.
The 5G system shall enable operators to specify and modify the types of mobility support provided for a UE or group of UEs.
The 5G system shall optimize mobility management support for a UE or group of UEs that use only mobile originated communications.
The 5G system shall support inter- and/or intra- access technology mobility procedures within 5GS with minimum impact to the user experience (e.g. QoS, QoE). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.2.3 Service continuity requirements | The 5G system shall enable packet loss to be minimized during inter- and/or intra- access technology changes for some or all connections associated with a UE.
The 5G system shall minimize interruption time during inter- and/or intra- access technology mobility for some or all connections associated with a UE.
NOTE: The interruption time includes all delays which have impact on service continuity.
For applications that require the same IP address during the lifetime of the session, the 5G system shall enable maintaining the IP address assigned to a UE when moving across different cells and access technologies for connections associated with a UE.
The 5G system shall enable minimizing impact to the user experience (e.g. minimization of interruption time) when changing the IP address and IP anchoring point for some or all connections associated with a UE.
The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa.
The 5G system shall support service continuity for a remote UE, when the remote UE changes from one relay UE to another and both relay UEs use 3GPP access to the 5G core network.
Satellite access related service continuity requirements are covered in clause 6.46.3. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.2.4 Roaming related requirements | Satellite access related roaming requirements are covered in clause 6.46.4. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3 Multiple access technologies | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.1 Description | The 5G system will support 3GPP access technologies, including one or more NR and E-UTRA as well as non-3GPP access technologies. Interoperability among the various access technologies will be imperative. For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-3GPP access technology for a service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE. New technology such as satellite and wide area base stations will increase coverage and availability. This clause provides requirements for interworking with the various combinations of access technologies. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.2.1 General | Based on operator policy, the 5G system shall enable the UE to select, manage, and efficiently provision services over the 3GPP or non-3GPP access.
Based on operator policy, the 5G system shall support steering a UE to select certain 3GPP access network(s).
Based on operator policy, the 5G system shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type.
Based on operator policy, the 5G system shall be able to provide simultaneous data transmission via different access technologies (e.g. NR, E-UTRA, non-3GPP), to access one or more 3GPP services.
When a UE is using two or more access technologies simultaneously, the 5G system shall be able to optimally distribute user traffic over the access technologies in use, taking into account e.g. service, traffic characteristics, radio characteristics, and UE's moving speed.
The 5G system shall be able to support data transmissions optimized for different access technologies (e.g. 3GPP, non-3GPP) and accesses to local data networks (e.g. local traffic routing) for UEs that are simultaneously connected to the network via different accesses.
NOTE: This applies to the scenario with simultaneous 3GPP and non-3GPP accesses.
Based on operator policy, the 5G system shall be able to add or drop the various access connections for a UE during a session.
The 5G system shall be able to support mobility between the supported access networks (e.g. NG-RAN, WLAN, fixed broadband access network, 5G satellite access network).
The 5G system shall support UEs with multiple radio and single radio capabilities.
The 5G system shall support dynamic and static network address allocation of a common network address to the UE over all supported access types.
The 5G system shall support a set of identities for a single user in order to provide a consistent set of policies and a single set of services across 3GPP and non-3GPP access types.
The 5G system shall support the capability to operate in licensed and/or unlicensed bands. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.2.2 E-UTRA access | The 5G system shall be able to support seamless handover between NR and E-UTRA.
The 5G system shall support UEs with dual radio capability (i.e. a UE that can transmit on NR and E-UTRA simultaneously) as well as UEs with single radio capability (i.e. a UE that cannot transmit on NR and E-UTRA simultaneously). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.2.3 Satellite access | The 5G system shall be able to provide services using satellite access.
NOTE: Additional requirements related to satellite access can be found in clause 6.46. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.3.2.4 Fixed broadband access | The 5G system shall be able to efficiently support connectivity using fixed broadband access.
NOTE: The specification of fixed broadband access network is outside the scope of 3GPP.
The 5G system shall support use of a relay UE that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4 Resource efficiency | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.1 Description | 5G introduces the opportunity to design a system to be optimized for supporting diverse UEs and services. While support for IoT is provided by EPS, there is room for improvement in efficient resource utilization that can be designed into a 5G system whereas they are not easily retrofitted into an existing system. Some of the underlying principles of the potential service and network operation requirements associated with efficient configuration, deployment, and use of UEs in the 5G network include bulk provisioning, resource efficient access, optimization for UE originated data transfer, and efficiencies based on the reduced needs related to mobility management for stationary UEs and UEs with restricted range of movement.
As sensors and monitoring UEs are deployed more extensively, the need to support UEs that send data packages ranging in size from a small status update in a few bits to streaming video increases. A similar need exists for smart phones with widely varying amounts of data. Specifically, to support short data bursts, the network should be able to operate in a mode where there is no need for a lengthy and high overhead signalling procedure before and after small amounts of data are sent. The system will, as a result, avoid both a negative impact to battery life for the UE and wasting signalling resources.
For small form factor UEs it will be challenging to have more than 1 antenna due to the inability to get good isolation between multiple antennas. Thus, these UEs need to meet the expected performance in a 5G network with only one antenna.
Cloud applications like cloud robotics perform computation in the network rather than in a UE, which requires the system to have high data rate in the uplink and very low round trip latency. Supposed that high density cloud robotics will be deployed in the future, the 5G system need to optimize the resource efficiency for such scenario.
Additional resource efficiencies will contribute to meeting the various KPIs defined for 5G. Control plane resource efficiencies can be achieved by optimizing and minimizing signalling overhead, particularly for small data transmissions. Mechanisms for minimizing user plane resources utilization include in-network caching and application in a Service Hosting Environment closer to the end user. These optimization efforts contribute to achieving lower latency and higher reliability.
Diverse mobility management related resource efficiencies are covered in clause 6.2.
Security related resource efficiencies are covered in clause 8.8. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.2.1 General | The 5G system shall minimize control and user plane resource usage for data transfer from send only UEs.
The 5G system shall minimize control and user plane resource usage for stationary UEs (e.g. lower signalling to user data resource usage ratio).
The 5G system shall minimize control and user plane resource usage for transfer of infrequent small data units.
The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of small data units.
The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of continuous uplink data that requires both high data rate (e.g. 10 Mbit/s) and very low end-to-end latency (e.g. 1-10 ms).
The 5G network shall optimize the resource use of the control plane and/or user plane to support high density connections (e.g. 1 million connections per square kilometre) taking into account, for example, the following criteria:
- type of mobility support;
- communication pattern (e.g. send-only, frequent or infrequent);
- characteristics of payload (e.g. small or large size data payload);
- characteristics of application (e.g. provisioning operation, normal data transfer);
- UE location;
- timing pattern of data transfer (e.g. real time or non-delay sensitive).
The 5G system shall efficiently support service discovery mechanisms where UEs can discover, subject to access rights:
- status of other UEs (e.g. sound on/off);
- capabilities of other UEs (e.g. the UE is a relay UE) and/or;
- services provided by other UEs (e.g. the UE is a colour printer).
The 5G system shall be able to minimise the amount of wireless backhaul traffic (e.g. consolidating data transmissions to 1 larger rather than many smaller), when applicable (e.g. providing service in an area subject to power outages).
The 5G system shall support small form factor UEs with single antenna.
NOTE: Small form factor UEs are typically expected to have the diagonal less than 1/5 of the lowest supported frequency wave length.
Satellite access related resource efficiency requirements are covered in clause 6.46.5.
The 5G system shall support UEs with different characteristics such as data rate, power consumption, etc. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.2.2 Efficient bulk operations for IoT | The 5G network shall optimize the resource use of the control plane and/or user plane to support bulk operation for high connection density (e.g. 1 million connections per square kilometre) of multiple UEs.
The 5G system shall support a timely, efficient, and/or reliable mechanism to transmit the same information to multiple UEs. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.2.3 Efficient management for IoT | The 5G network shall optimize the resource use of the control plane and/or user plane to manage (e.g. provide service parameters, activate, deactivate) a UE.
The 5G network shall be able to provide policies for background data transfer to a UE so that the 5G system can optimally use the control plane and/or user plane resources. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.4.2.4 Efficient control plane | The 5G system shall minimize the signalling that is required prior to user data transmission.
NOTE: The amount of signalling overhead may vary based on the amount of data to be transmitted, even for the same UE. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.5 Efficient user plane | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.5.1 Description | 5G is designed to meet diverse services with different and enhanced performances (e.g. high throughput, low latency and massive connections) and data traffic model (e.g. IP data traffic, non-IP data traffic, short data bursts and high throughput data transmissions).
User plane should be more efficient for 5G to support differentiated requirements. On one hand, a Service Hosting Environment located inside of operator's network can offer Hosted Services closer to the end user to meet localization requirement like low latency, low bandwidth pressure. These Hosted Services contain applications provided by operators and/or trusted 3rd parties. On the other hand, user plane paths can be selected or changed to improve the user experience or reduce the bandwidth pressure, when a UE or application changes location during an active communication, or due to operational needs in the service hosting environment (e.g. based on usage information).
The 5G network can also support multiple wireless backhaul connections (e.g. satellites and/or terrestrial), and efficiently route and/or bundle traffic among them. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.5.2 Requirements | Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path between UEs attached to the same network, modifying the path as needed when the UE moves during an active communication.
The 5G network shall enable a Service Hosting Environment provided by operator.
Based on operator policy, the 5G network shall be able to support routing of data traffic between a UE attached to the network and an application in a Service Hosting Environment for specific services, modifying the path as needed when the UE moves during an active communication.
Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and:
- an application in a Service Hosting Environment; or
- an application server located outside the operator’s network; or
- an application server located in a customer premises network or personal IoT network.
The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to:
- another location served by a different Service Hosting Environment; or
- another location served by an application server located outside the operator’s network; or
- another location served by an application server located in a customer premises network or personal IoT network, and vice versa.
The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows:
- within a Service Hosting Environment; or
- from a Service Hosting Environment to another Service Hosting Environment; or
- from a Service Hosting Environment to an application server located place outside the operator’s network; or
- from a Service Hosting Environment to an application server located in a customer premises network or personal IoT network, and vice versa.
The 5G network shall be able to interact with applications in a Service Hosting Environment for efficient network resource utilization and offloading data traffic to the most suitable Service Hosting Environment, e.g. close to the UE's point of attachment to the access network or based on usage information.
NOTE: To accomplish offloading data traffic, usage information might be exposed to the Service Hosting Environment.
The 5G network shall support configurations of the Service Hosting Environment in the network (e.g. access network, core network), that provide application access close to the UE's point of attachment to the access network.
The 5G system shall support mechanisms to enable a UE to access the closest Service Hosting Environment for a specific hosted application or service.
The 5G network shall enable instantiation of applications for a UE in a Service Hosting Environment close to the UE's point of attachment to the access network.
The 5G system shall be able to suspend or stop application instances in a Service Hosting Environment.
NOTE: Not all applications will always be available in all Service Hosting Environments. Therefore, it may be needed to instantiate an application at a Service Hosting Environment nearby for serving a particular UE.
Based on operator policy, the 5G system shall provide a mechanism such that one type of traffic (from a specific application or service) to/from a UE can be offloaded close to the UE's point of attachment to the access network, while not impacting other traffic type to/from that same UE.
Satellite access related efficient user plane requirements are covered in clause 6.46.6.
The 5G System shall enable the discovery of a suitable Hosted Service. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.6 Efficient content delivery | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.6.1 Description | Video-based services (e.g. live streaming, VR) and personal data storage applications have been instrumental for the massive growth in mobile broadband traffic. Subject to service agreement between the operator and the content provider, the information of content and content itself can be aware by operator. In-network content caching provided by the operator, a third-party or both, can improve user experience, reduce backhaul resource usage and utilize radio resource efficiently.
The operation of in-network caching includes flexible management of the location of the content cache within the network and efficient delivery of content to and from the appropriate content caching application. Examples of services are the delivery of popular video content from a content caching application via broadcast, and secure storage of a user's personal data or files using a distributed caching application. Such a service could also provide a student with a wireless backpack, where students can resume their work through the same or a different UE at any time, with very fast response times from the network. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.6.2 Requirements | The 5G system shall enable efficient delivery of content from a content caching application under the control of the operator (e.g. a cache located close to the UE).
The 5G system shall support a content caching application in a UE under the control of the operator.
The 5G system shall support configurations of content caching applications in the network (e.g. access network, core network), that provide content close to the UE.
Based on operator policy, the 5G system shall support an efficient mechanism for selection of a content caching application (e.g. minimize utilization of radio, backhaul resources and/or application resource) for delivery of the cached content to the UE.
The 5G system shall support a mechanism for the operator to manage content distribution across content caching applications.
The 5G system shall support delivery of cached content from a content caching application via the broadcast/multicast service.
For a 5G system with satellite access, the following requirement applies.
- A 5G system with satellite access shall be able to optimise the delivery of content from a content caching application by taking advantage of satellites in supporting ubiquitous service, as well as broadcasting/multicasting on very large to global coverages. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.7 Priority, QoS, and policy control | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.7.1 Description | The 5G network will support many commercial services (e.g. medical) and regional or national regulatory services (e.g. MPS, Emergency, Public Safety) with requirements for priority treatment. Some of these services share common QoS characteristics such as latency and packet loss rate but can have different priority requirements. For example, UAV control and air traffic control can have stringent latency and reliability requirements but not necessarily the same priority requirements. In addition, voice-based services for MPS and Emergency share common QoS characteristics as applicable for normal public voice communications yet can have different priority requirements. The 5G network will need to support mechanisms that enable the decoupling of the priority of a particular communication from the associated QoS characteristics such as latency and reliability to allow flexibility to support different priority services (that need to be configurable to meet operator needs, consistent with operator policies and corresponding national and regional regulatory policies).
The network needs to support flexible means to make priority decisions based on the state of the network (e.g. during disaster events and network congestion) recognizing that the priority needs can change during a crisis. The priority of any service can be different for a user of that service based on operational needs and regional or national regulations. Therefore, the 5G system should allow a flexible means to prioritise and enforce prioritisation among the services (e.g. MPS, Emergency, medical, Public Safety) and among the users of these services. The traffic prioritisation can be enforced by adjusting resource utilization or pre-empting lower priority traffic.
The network must offer means to provide the required QoS (e.g. reliability, latency, and bandwidth) for a service and the ability to prioritize resources when necessary to meet the service requirements. Existing QoS and policy frameworks handle latency and improve reliability by traffic engineering. In order to support 5G service requirements, it is necessary for the 5G network to offer QoS and policy control for reliable communication with latency required for a service and enable the resource adaptations as necessary.
The network needs to allow multiple services to coexist, including multiple priority services (e.g. Emergency, MPS and MCS) and must provide means to prevent a single service from consuming or monopolizing all available network resources, or impacting the QoS (e.g. availability) of other services competing for resources on the same network under specific network conditions. For example, it is necessary to prevent certain services (e.g. citizen-to-authority Emergency) sessions from monopolizing all available resources during events such as disaster, emergency, and DDoS attacks from impacting the availability of other priority services such as MPS and MCS.
Also, as 5G network is expected to operate in a heterogeneous environment with multiple access technologies, multiple types of UE, etc., it should support a harmonised QoS and policy framework that applies to multiple accesses.
Further, for QoS control in EPS only covers RAN and core network, but for 5G network E2E QoS (e.g. RAN, backhaul, core network, network to network interconnect) is needed to achieve the 5G user experience (e.g. ultra-low latency, ultra-high bandwidth). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.7.2 Requirements | The 5G system shall allow flexible mechanisms to establish and enforce priority policies among the different services (e.g. MPS, Emergency, medical, Public Safety) and users.
NOTE 1: Priority between different services is subject to regional or national regulatory and operator policies.
The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
The 5G system shall enable the network operator to define and statically configure a maximum resource assignment for a specific service that can be adjusted based on the network state (e.g. during congestion, disaster, emergency and DDoS events) subject to regional or national regulatory and operator policies.
The 5G system shall allow decoupling of the priority of a particular communication from the associated QoS characteristics such as end-to-end latency and reliability.
The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses.
The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve an UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability.
The 5G system shall support a mechanism to determine suitable QoS parameters for traffic over a satellite backhaul, based e.g. on the latency and bandwidth of the specific backhaul .
NOTE 3: The case where a backhaul connection has dynamically changed latency and/or bandwidth needs to be considered. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.8 Dynamic policy control | The 5G system shall support the creation and enforcement of prioritisation policy for users and traffic, during connection setup and when connected.
NOTE: Prioritisation, pre-emption, and precedence of critical traffic associated with certain priority services (e.g. MPS and Emergency) are subject to regional/national regulatory and operator policies.
The 5G system shall support optimised signalling for prioritised users and traffic where such signalling is prioritized over other signalling traffic.
Based on operator policy, the 5G system shall allow flexible means for authorized entities to create and enforce priority among the different service flows.
Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
Based on operator policy, the 5G system shall maintain a session when prioritization of that session changes in real time, provided that the new priority is above the threshold for maintaining the session. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9 Connectivity models | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.1 Description | The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relay UEs can be used to improve the energy efficiency and coverage of the system.
Remote UEs can be anything from simple wearables, such as sensors embedded in clothing, to a more sophisticated wearable UE monitoring biometrics. They can also be non-wearable UEs that communicate in a Personal Area Network such as a set of home appliances (e.g. smart thermostat and entry key), or the electronic UEs in an office setting (e.g. smart printers), or a smart flower pot that can be remotely activated to water the plant.
When a remote UE is attempting to establish an indirect network connection, there might be several relay UEs that are available in proximity and supporting selection procedures of an appropriate relay UE among the available relay UEs is needed.
Indirect network connection covers the use of relay UEs for connecting a remote UE to the 3GPP network. There can be one or more relay UE(s) (more than one hop) between the network and the remote UE.
A ProSe UE-to-UE Relay can also be used to connect two remote Public Safety UEs using direct device connection. There can be one or more ProSe UE-to-UE Relay(s) (more than one hop) between the two remote Public Safety UEs. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.278 [5], clauses 7B and 7C. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2.1 General | The 5G system shall support the relaying of traffic between a remote UE and a gNB using one or more relay UEs.
The 5G system shall support same traffic flow of a remote UE to be relayed via different indirect network connection paths.
The 5G system shall support different traffic flows of a remote UE to be relayed via different indirect network connection paths.
The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band.
The connection between a remote UE and a relay UE shall be able to use fixed broadband technology.
The 5G system shall support indirect network connection mode in a VPLMN when a remote UE and a relay UE subscribe to different PLMNs and both PLMNs have a roaming agreement with the VPLMN.
The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode.
The network operator shall be able to define the maximum number of hops supported in their networks when using relay UEs.
The 5G system shall be able to manage communication between a remote UE and the 5G network across multi-path indirect network connections. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2.2 Services and Service Continuity | A 5G system shall be able to support all types of traffic e.g. voice, data, IoT small data, multimedia, MCX for indirect network connection mode.
The 5G system shall be able to support QoS for a user traffic session between the remote UE and the network using 3GPP access technology.
The 5G system shall be able to provide indication to a remote UE (alternatively, an authorized user) on the quality of currently available indirect network connection paths.
The 5G system shall be able to maintain service continuity of indirect network connection for a remote UE when the communication path to the network changes (i.e. change of one or more of the relay UEs, change of the gNB).
NOTE: It does not apply to a traffic flow of a remote UE using different indirect network connection paths. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2.3 Permission and Authorization | The 5G system shall enable the network operator to authorize a UE to use indirect network connection. The authorization shall be able to be restricted to using only relay UEs belonging to the same network operator. The authorization shall be able to be restricted to only relay UEs belonging to the same application layer group.
The 5G system shall enable the network operator to authorize a UE to relay traffic as relay UE. The authorization shall be able to allow relaying only for remote UEs belonging to the same network operator. The authorization shall be able to allow relaying only for remote UEs belonging to the same application layer group.
The 5G system shall support a mechanism for an end user to provide/revoke permission to an authorized UE to act as a relay UE.
The 5G system shall support a mechanism for an authorized third-party to provide/revoke permission to an authorized UE to act as a relay UE.
The 5G system shall provide a suitable API by which an authorized third-party shall be able to authorize (multiple) UEs under control of the third-party to act as a relay UE or remote UE.
The 5G system shall provide a suitable API by which an authorized third-party shall be able to enable/disable (multiple) UEs under control of the third-party to act as a relay UE or remote UE. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2.4 Relay UE Selection | The 3GPP system shall support selection and reselection of relay UEs based on a combination of different criteria e.g.
- the characteristics of the traffic that is intended to be relayed (e.g. expected message frequency and required QoS),
- the subscriptions of relay UEs and remote UE,
- the capabilities/capacity/coverage when using the relay UE,
- the QoS that is achievable by selecting the relay UE,
- the power consumption required by relay UE and remote UE,
- the pre-paired relay UE,
- the 3GPP or non-3GPP access the relay UE uses to connect to the network,
- the 3GPP network the relay UE connects to (either directly or indirectly),
- the overall optimization of the power consumption/performance of the 3GPP system, or
- battery capabilities and battery lifetime of the relay UE and the remote UE.
NOTE: Reselection may be triggered by any dynamic change in the selection criteria, e.g. by the battery of a relay UE getting depleted, a new relay capable UE getting in range, a remote UEs requesting additional resources or higher QoS, etc. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.2.5 Satellite and Relay UEs | Satellite and relay UEs related requirements are covered in clause 6.46.7. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.9.3 Requirements on direct device connection for Public Safety | The following requirement complement the requirements listed in 3GPP TS 22.278 [5], clauses 7A.
The 5G system shall support the relaying of traffic between two remote Public Safety UEs using direct device connection via one or more ProSe UE-to-UE Relay(s) (one or more hops, assuming single-path), while in coverage, out-of-coverage, or partial coverage. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.10 Network capability exposure | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.10.1 Description | 3GPP SEES and (e)FMSS features allow the operator to expose network capabilities e.g. QoS policy to third-party ISPs/ICPs. With the advent of 5G, new network capabilities need to be exposed to the third-party (e.g. to allow the third-party to customize a dedicated physical or virtual network or a dedicated network slice for diverse use cases; to allow the third-party to manage a trusted third-party application in a Service Hosting Environment to improve user experience, and efficiently utilize backhaul and application resources). |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.10.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.101 [6], clause 29.
Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to assign a UE to a network slice used for the third-party, to move a UE from one network slice used for the third-party to another network slice used for the third-party, and to remove a UE from a network slice used for the third-party based on subscription, UE capabilities, and services provided by the network slice.
The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide the 3GPP network via encrypted connection with the expected communication behaviour of UE(s).
NOTE 1: The expected communication behaviour is, for instance, the application servers a UE is allowed to communicate with, the time a UE is allowed to communicate, or the allowed geographic area of a UE.
The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide via encrypted connection the 3GPP network with the actions expected from the 3GPP network when detecting behaviour that falls outside the expected communication behaviour.
NOTE 2: Such actions can be, for instance, to terminate the UE's communication, to block the transferred data between the UE and the not allowed application.
The 5G network shall be able to provide secure means for providing communication scheduling information (i.e. the time period the UE(s) will use a communication service) to an NPN via encrypted connection. This communication scheduling information is used by the 5G network to perform network energy saving and network resource optimization.
The 5G network shall provide a mechanism to expose broadcasting capabilities to trusted third-party broadcasters' management systems.
Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment.
Based on operator policy, the 5G network shall provide suitable APIs to allow a third-party to monitor this trusted third-party owned application(s) in the operator's Service Hosting Environment.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity.
Based on operator policy, a 5G network shall provide suitable APIs to allow one type of traffic (from trusted third-party owned applications in the operator's Service Hosting Environment) to/from a UE to be offloaded to a Service Hosting Environment close to the UE's location.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.
Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.
The 5G system shall support the means for disengagement (tear down) of communication services by an authorized third-party.
Based on operator policy, the 5G network shall expose a suitable API to provide the security logging information of UEs, for example, the active 3GPP security mechanisms (e.g. data privacy, authentication, integrity protection) to an authorized third-party.
Based on operator policy, the 5G system shall provide suitable means to allow a trusted and authorized third-party to consult security related logging information for the network slices dedicated to that third-party.
Based on operator policy, the 5G network shall be able to acknowledge within 100 ms a communication service request from an authorized third-party via a suitable API.
The 5G network shall provide suitable APIs to allow a trusted third-party to monitor the status (e.g. locations, lifecycle, registration status) of its own UEs.
NOTE 3: The number of UEs could be in the range from single digit to tens of thousands.
The 5G network shall provide suitable APIs to allow a trusted third-party to get the network status information of a private slice dedicated for the third-party, e.g. the network communication status between the slice and a specific UE.
The 5G system shall support APIs to allow the non-public network to be managed by the MNO's Operations System.
The 5G system shall provide suitable APIs to allow third-party infrastructure (i.e. physical/virtual network entities at RAN/core level) to be used in a private slice.
A 5G system shall provide suitable APIs to enable a third-party to manage its own non-public network and its private slice(s) in the PLMN in a combined manner.
The 5G system shall support suitable APIs to allow an MNO to offer automatic configuration services (for instance, interference management) to non-public networks deployed by third parties and connected to the MNO's Operations System through standardized interfaces.
The 5G system shall be able to:
- provide a third-party with secure access to APIs (e.g. triggered by an application that is visible to the 5G system), by authenticating and authorizing both the third-party and the UE using the third-party's service.
- provide a UE with secure access to APIs (e.g. triggered by an application that is not visible to the 5G system), by authenticating and authorizing the UE.
- allow the UE to provide/revoke consent for information (e.g., location, presence) to be shared with the third-party.
- preserve the confidentiality of the UE's external identity (e.g. MSISDN) against the third-party.
- provide a third-party with information to identify networks and APIs on those networks.
Based on operator policy, the 5G system shall provide means by which an MNO informs a third party of changes in UE subscription information. The 5G system shall also provide a means for an authorised third party to request this information at any time from the MNO.
NOTE 4: Examples of UE subscription information include IP address, 5G LAN-VN membership, and configuration parameters for data network access.
NOTE 5: These changes can have strong impacts in the stability of the third-party service.
The 5G system shall provide a means by which an MNO can inform authorised 3rd parties of changes in the
- RAT type that is serving a UE;
- cell ID;
- RAN quality of signal information;
- assigned frequency band.
This information listed above shall be provided with a suitable frequency via OAM and/or 5G core network.
NOTE 6: The information aids the third party user to take proactive actions so that it can achieve high service availability in delivery of its services. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.11 Context-aware network | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.11.1 Description | A variety of sensors such as accelerometer, gyroscope, magnetometer, barometer, proximity sensor, and GPS can be integrated in a UE. Also, different applications running on the UE can have different communication needs (e.g. different traffic time). In addition, a UE can support different access technologies such as NR, E-UTRA, WLAN access technology, and fixed broadband access technology. The information gathered by sensors, the utilized access technologies, the application context, and the application traffic characteristics can provide useful information to the applications installed in the UE and can also help the 5G system utilize resources in an efficient and optimized way. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.11.2 Requirements | The 5G system shall support network resource utilization efficiently and network optimization based on system information, including:- network conditions, such as network load and congestion information;
- information on served UEs such as access information (e.g. 3GPP access, non-3GPP access), cell type (e.g. macro cell, small cell), user experienced data rate;
- application's characteristics (e.g. expected traffic over time);
- information on prioritized communication such as user subscription profile and priority level, priority services (e.g. MPS, Emergency, and Public Safety), application used for priority communications (e.g. voice, video, and data) and traffic associated with priority communications (signalling and media);
- subject to user consent, enhanced traffic characteristic of UE (e.g. Mobility information (e.g. no mobility, nomadic, spatially restricted mobility, full mobility), location, sensor-level information (e.g. direction, speed, power status, display status, other sensor information installed in the UE), application-level information (e.g. foreground applications, running background application, and user settings).
The 5G system shall support mechanisms to collect system information for network optimization within an operator configured time scale. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.12 Self backhaul | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.12.1 Description | The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and management (e.g. backhaul availability, backhaul capacity and scalability). The use of wireless backhaul for such access nodes helps to address some of the challenges.
Wireless self-backhauling in the radio access network can enable simpler deployment and incremental rollout by reducing reliance on the availability of wired backhaul at each access node location. Network planning and installation efforts can be reduced by leveraging plug and play type features -- self-configuration, self-organizing, and self-optimization. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.12.2 Requirements | The 5G network shall enable operators to support wireless self-backhaul using NR and E-UTRA.
The 5G network shall support flexible and efficient wireless self-backhaul for both indoor and outdoor scenarios.
The 5G network shall support flexible partitioning of radio resources between access and backhaul functions.
The 5G network shall support autonomous configuration of access and wireless self-backhaul functions.
The 5G network shall support multi-hop wireless self-backhauling.
NOTE 1: This is to enable flexible extension of range and coverage area.
The 5G network shall support autonomous adaptation on wireless self-backhaul network topologies to minimize service disruptions.
The 5G network shall support topologically redundant connectivity on the wireless self-backhaul.
NOTE 2: This is to enhance reliability and capacity and reduce end-to-end latency. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.13 Flexible broadcast/multicast service | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.13.1 Description | The proliferation of video services, ad-hoc multicast/broadcast streams, software delivery over wireless, group communications and broadcast/multicast IoT applications have created a need for a flexible and dynamic allocation of radio resources between unicast and multicast services within the network as well as support for a stand-alone deployment of multicast/broadcast network. Moreover, enabling such a service over a network for a wide range of inter-site distances between the radio base stations will enable a more efficient and effective delivery system for real-time and streaming multicast/broadcast content over wide geographic areas as well as in specific geographic areas spanning a limited number of base stations. A flexible multicast/broadcast service will allow the 5G system to efficiently deliver such services. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.13.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.146 [7], TS 22.246 [8] and TS 22.101 [6], clause 32.
The 5G system shall support operation of downlink only broadcast/multicast over a specific geographic area (e.g. a cell sector, a cell or a group of cells).
The 5G system shall support operation of a downlink only broadcast/multicast system over a wide geographic area in a spectrally efficient manner for stationary and mobile UEs.
The 5G system shall enable the operator to reserve 0% to 100% of radio resources of one or more radio carriers for the delivery of broadcast/multicast content.
The 5G network shall allow the UE to receive content via a broadcast/multicast radio carrier while a concurrent data session is ongoing over another radio carrier.
The 5G system shall be able to support broadcast/multicast of UHD streaming video (e.g. 4K/8K UHD).
NOTE 1: Taking into account the bandwidth needs for different streaming video resolution.
The 5G network shall allow the operator to configure and broadcast multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service in a stand-alone 3GPP based broadcast/multicast system.
The 5G network shall support parallel transfer of multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service to the same UE taking into account e.g. UE capability, radio characteristics, application information.
The 5G system shall support parallel transfer of multiple multicast/broadcast user services to a UE.
The 5G system shall support a stand-alone multicast/broadcast network comprising of multiple cells with inter-site distances of up to 200 km.
The 5G system shall support multicast/broadcast via a 5G satellite access network, or via a combination of a 5G satellite access network and other 5G access networks.
The 5G system shall support interworking of 5G multicast/broadcast with non-3GPP digital terrestrial broadcast networks.
NOTE 1A: Any impact on the non-3GPP digital terrestrial broadcast standard is out of scope of 3GPP standardization.
The 5G system shall be able to setup or modify a broadcast/multicast service area within [1s].
NOTE 2: For MCPTT related KPIs see 3GPP TS 22.179 [30], clause 6.15.
The 5G system shall be able to apply QoS, priority and pre-emption to a broadcast/multicast service area.
The 5G system shall support downlink parallel transfer of the same content, via broadcast/multicast and/or unicast, such that all receiver group members in a given area receive the media at the same time according to user perception.
NOTE 3: In this context user perception refers to a difference in delay of typically less than 20 ms.
The 5G system shall support a mechanism to inform a media source of relevant changes in conditions in the system (e.g. capacity, failures).
The 5G system shall provide means for a media source to provide QoS requirement requests to the broadcast/multicast service.
The 5G system shall provide means for the broadcast/multicast service to inform the media source of the available QoS, including modification of available QoS characteristics and availability of the broadcast/multicast service.
The 5G system shall be able to support broadcast/multicast of voice, data and video group communication, allowing at least 800 concurrently operating groups per geographic area.
NOTE 4: In this context "concurrently operating groups" means that the associated media streams are delivered concurrently.
The 5G system shall support delivery of the same UE-originated data in a resource-efficient manner in terms of service bit rate to UEs distributed over a large geographical area.
The 5G system shall allow a UE to request a communication service to simultaneously send data to different groups of UEs at the same time.
The 5G system shall allow different QoS policy for each group the UE communicates with. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.14 Subscription aspects | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.14.1 Description | With the Internet of Things, it is expected that the diversity of IoT devices (e.g. sensors, UAVs, smart flower pots) and the usage models will largely vary. Moreover, when the IoT device is manufactured, the deployment location and specific usage might not be known. Sometimes the IoT devices will be added to existing subscriptions, other times they can be part of a new subscription for the user. Sometimes the IoT devices can be leased. During their life cycle these IoT devices go through different stages, involving the change in ownership when the IoT device is deployed and possibly afterwards, the activation of the IoT device by the preferred operator, a possible change of operators, etc. These stages need to be managed securely and efficiently. A method of dynamic subscription generation and management is needed in addition to statically provisioned subscription. Once the subscription is established, subscription management becomes necessary, for example, to modify the subscription when the ownership of the IoT device changes, to update or refresh credentials due to suspected leakage or theft of security keys or as a preventive measure.
The Internet of Things will also support various connectivity models: The IoT devices can connect with the network directly or connect with the network using another IoT device as a relay UE, or they can be capable of using both types of connections. The direct device connection between the IoT device and the relay UE can be using 3GPP or non-3GPP RAT. The relay UE can access the network also using 3GPP or non-3GPP access networks (e.g. WLAN, fixed broadband access network). In order to identify and manage the IoT devices, a subscription with the 5G network is needed, even if the access is done via non-3GPP access. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.14.2 Requirements | An IoT device which is able to access a 5G PLMN in direct network connection mode using a 3GPP RAT shall have a 3GPP subscription.
The 5G system shall allow the operator to identify a UE as an IoT device based on UE characteristics (e.g. identified by an equipment identifier or a range of equipment identifiers) or subscription or the combination of both.
The 5G system shall be able to provide mechanisms to change the association between a subscription and address/number of an IoT device (e.g. changing the owner and subscription information associated with the IoT device) within the same operator and in between different operators in an automated or manual way.
The 5G system shall be able to support identification of subscriptions independently of identification of IoT devices. Both identities shall be secure.
An IoT device which is able to connect to a UE in direct device connection mode shall have a 3GPP subscription, if the IoT device needs to be identifiable by the core network (e.g. for IoT device management purposes or to use indirect network connection mode).
Based on operator policy, the 5G system shall support a mechanism to provision on-demand connectivity (e.g. IP connectivity for remote provisioning). This on-demand mechanism should enable means for a user to request on-the-spot network connectivity while providing operators with identification and security tools for the provided connectivity.
The 5G system shall support a secure mechanism for a home operator to remotely provision the 3GPP credentials of a uniquely identifiable and verifiably secure IoT device.
The 5G system shall support a secure mechanism for the network operator of an NPN to remotely provision the non-3GPP identities and credentials of a uniquely identifiable and verifiably secure IoT device.
Based on MNO and NPN policy, the 5G system shall support a mechanism to enable MNO to update the subscription of an authorized UE in order to allow the UE to connect to a desired NPN. This on-demand mechanism should enable means for a user to request on-the-spot network connectivity which is authorized by its MNO.
Based on operator policy, the 5G system shall provide means for authorised 3rd parties to request changes to UE subscription parameters for access to data networks, e.g., static IP address and configuration parameters for data network access. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.15 Energy efficiency | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.15.1 Description | Energy efficiency is a critical issue in 5G. The potential to deploy systems in areas without a reliable energy source requires new methods of managing energy consumption not only in the UEs but throughout all components of the 5G system.
Small form factor UEs also typically have a small battery and this not only puts constrains on general power optimization but also on how the energy is consumed. With smaller batteries it is more important to understand and follow the limitations for the both the maximum peak and continuous current drain. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.15.2 Requirements | The 5G access network shall support an energy saving mode with the following characteristics:
- the energy saving mode can be activated/deactivated either manually or automatically;
- service can be restricted to a group of users (e.g. public safety user, emergency callers).
NOTE: When in energy saving mode the UE's and Access transmit power may be reduced or turned off (deep sleep mode), end-to-end latency and jitter may be increased with no impact on set of users or applications still allowed.
The 5G system shall support mechanisms to improve battery life for a UE over what is possible in EPS.
The 5G system shall optimize the battery consumption of a relay UE via which a UE is in indirect network connection mode.
The 5G system shall support UEs using small rechargeable and single coin cell batteries (e.g. considering impact on maximum pulse and continuous current).
6.15a Energy Efficiency as a Service Criteria
6.15a.1 Description
Climate change and the rising consumption of energy motivate increased energy efficiency. Energy efficiency is a strategic priority for telecom operators around the world.
Energy efficiency as a service criteria allows services to be delivered with diverse energy efficiency and energy consumption policies. Energy consumption and efficiency information and network energy states can be exposed to third parties and energy consumption can be constrained.
Energy related information can include ratio of renewable energy and carbon emission information when available. Calculation of energy related information as described in the following requirements is done by means of averaging or applying a statistical model. The requirements do not imply that some form of 'real time' monitoring is required.
6.15a.2 Energy related information as a service criteria
6.15a.2.1 Description
Energy consumption can be monitored and considered through O&M as part of network operations [47], as well as a service criteria.
For best-effort traffic, that is, without QoS criteria, policies can be defined to limit energy use for services. This is not in conflict with the principle that performance policies will not be traded off for energy efficiency, since best-effort service has no performance guarantees.
Specifically, best-effort traffic can be subject to a policy that limits the maximum energy consumption over time, or further constrained by location (so that the energy consumption limit only applies when used in a specified service area.)
Additionally, policies can be defined with a maximum energy credit limit, e.g. for best-effort services to limit the total amount of energy consumption according to an energy charging rate. These policies expand the options of subscription policies to control energy consumption in the 5G system.
6.15a.2.2 Requirements
Subject to operator’s policy, the 5G system shall support subscription policies that define a maximum energy credit limit for services without QoS criteria.
Subject to operator’s policy, the 5G system shall support a means to associate energy consumption information with charging information based on subscription policies for services without QoS criteria.
Subject to operator’s policy, the 5G system shall support a mechanism to perform energy consumption credit limit control for services without QoS criteria.
NOTE 1: The result of the credit control is not specified by this requirement.
NOTE 2: Credit control [49] compares against a credit control limit. It is assumed charging events are assigned a corresponding energy consumption and this is compared against a policy of energy credit limit. It is assumed there can be a new policy to limit energy consumption allowed.
Subject to operator’s policy, the 5G system shall support a means to define subscription policies and means to enforce the policy that define a maximum energy consumption (i.e. quantity of energy for a specified period of time) for services without QoS criteria.
NOTE 3: The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services.
The 5G system shall provide a mechanism to include Energy related information as part of charging information.
Subject to operator policy and agreement with 3rd party, the 5G system shall provide a mechanism to support the selection of an application server based on energy related information associated with a set of application servers.
Subject to user consent and operator policy, 5G system shall be able to provide means to modify a communication service based on energy related information criteria based on subscription policies.
Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to provide means to operate part or the whole network according to energy consumption requirements, which may be based on subscription policies or requested by an authorized 3rd party.
6.15a.3 Support of different energy states
6.15a.3.1 Description
Different energy states is beneficial for verticals and operators to save energy according to different working status of telecommunication equipment and manufacturing.
6.15a.3.2 Requirements
The 5G system shall support different energy states of network elements and network functions.
5G system shall support dynamic changes of energy states of network elements and network functions.
NOTE: This requirement also includes the condition when providing network elements or functions to an authorised 3rd party, the dynamic changes can be based on pre-configured policy (the time of changing energy states, which energy state map to which level of load, etc.)
The 5G system shall support different charging mechanisms based on the different energy states of network elements and network functions.
6.15a.4 Monitoring and measurement
6.15a.4.1 Description
Different levels of monitoring and measurement related to energy consumption and efficiency bring more support in energy efficiency and energy saving. In this section, monitoring and measurement related to energy consumption and efficiency include network functions under NPN condition and also all kinds of NG-RAN deployment scenarios.
6.15a.4.2 Requirements
Subject to operator's policy, the 5G network shall support energy consumption monitoring at per network slice and per subscriber granularity.
NOTE 1: Energy consumption monitoring as described in the preceding requirement is done by means of averaging or applying a statistical model. The requirement does not imply that some form of 'real time' monitoring is required. The granularity of the subscription policies can either apply to the subscriber (all services), or to particular services.
Subject to operator’s policy and agreement with 3rd party, the 5G system shall be able to monitor energy consumption for serving this 3rd party.
NOTE 2: The granularity of energy consumption measurement could vary according to different situations, for example, when several services share a same network slice, etc.
NOTE 3: The energy consumption information can be related to the network resources of network slice, NPNs, etc.
Subject to operator policy and regulatory requirements, the 5G system shall be able to monitor the energy consumption for serving the 3rd party, together with the network performance statistic information for the services provided by that network, related to same time interval e.g. hourly or daily.
NOTE 4: The network performance statistic information could be the data rate, packet delay and packet loss, etc.
6.15a.5 Information exposure
6.15a.5.1 Description
Information related to energy consumption and efficiency is not only necessary for network internal optimization, but also will benefit the service adjustment for 3rd party.
6.15a.5.2 Requirements
Subject to operator’s policy and agreement with 3rd party, the 5G system shall be able to expose information on energy consumption for serving this 3rd party.
NOTE 1: Energy consumption information can include ratio of renewable energy and carbon emission information when available. The reporting period could be set, e.g., on monthly or yearly basis and can vary based on location.
NOTE 2: The energy consumption information can be related to the network resources of network slice, NPNs, etc.
Subject to operator’s policy,agreement with 3rd party and consent by the customer, the 5G system shall be able to expose the network performance statistic information (e.g. the data rate, packet delay and packet loss) together with energy consumption information resulting from service provided to the customer, to the authorized third party, related to the same time interval e.g. hourly or daily.
Subject to operator’s policy, the 5G system shall support a means to expose energy consumption to authorized third parties for services, including energy consumption information related to the condition of energy credit limit (e.g. when the energy consumption is reaching the energy credit limit).
Subject to operator policy, the 5G system shall provide means for the trusted 3rd party, to configure which network performance statistic information (e.g. the data rate, packet delay and packet loss) for the communication service provided to the 3rd party, needs to be exposed along with the information on energy consumption for serving this 3rd party.
Based on operator’s policy and agreement with 3rd party, the 5G system shall be able to expose energy consumption information and prediction on energy consumption of the 5G network per application service to the 3rd party.
Subject to operator’s policy and agreement with 3rd party, the 5G system shall support a mechanism for the 3rd party to provide current or predicted energy consumption information over a specific period of time.
6.15a.6 Network actions leveraging energy efficiency as a service criteria
6.15a.6.1 Description
This clause addresses requirements to the 5G system that leverage energy-related information (e.g., energy consumption, energy efficiency), amongst others (e.g., network load), as criteria for network internal optimization actions targeting energy savings, within and across operators in a localized (i.e., geographically bound) and/or temporal (i.e., time bound) manner.
One of the strategies to save energy within mobile networks is to shut down some RAN nodes at times of low usage.
Eventually only one communication service could be used on a local basis among operators at times of low usage, as further energy saving gain to be exploited. Agreements could be put in place between operators so that in the low load periods (e.g., nighttime) only one of multiple mobile networks may be active in an area and will provide communication service to the subscribers of all networks, whereas the other networks can apply cell shutdown of their own infrastructure to obtain network energy savings.
Alternatively, based on risks of power outage nation-wide/region-wide, regulators could ask operators to “optimize” their coverage e.g., shutdown some nodes in overlapping coverage areas during energy peak hours and/or in specific geographical areas, whilst still guaranteeing minimum coverage/service (in particular to fullfill regulatory requirements for services such as emergency calls, PWS, MPS and MCS).
This can also apply between NPN operators and/or with PLMN operators.
6.15a.6.2 Requirements
Subject to regulatory requirements and operators’ policies, the 5G system shall enable an operator to temporarily serve UEs of other operators within a geographical area for the purpose of saving energy of the other operators.
NOTE 1: The other operators are assumed to stop providing access to their own network infrastructure within the same geographical area to save energy during that time.
NOTE 2: Policies may include predefined times/locations, energy consumption/efficiency thresholds, etc.
NOTE 3: It is assumed that the 5G system can collect charging information associated with serving UEs of other operators. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.16 Markets requiring minimal service levels | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.16.1 Description | A key aspect of 5G system flexibility is the ability to support both the very high-end markets as well as very low-end markets. Some systems will be deployed in areas where there are constraints on energy resources (e.g. sporadic access to power) and lower end user expectations for availability, reliability, and data rates. In such cases, the system needs additional flexibility to adapt power consumption needs based on fluctuations in power availability. The system should be efficient in order to provide essential services in harsh environments (e.g. far remote rural areas, very large territories) while taking into account the local constraints (adapting resources consumptions to long distances, dealing with variable conditions and possibly disconnections). Content delivery should be optimized in order to reduce constraints on transport networks, on low-end UEs (e.g. small screen, limited energy consumption), variable network conditions, and client profiles. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.16.2 Requirements | In constrained circumstances (e.g. reduced power supply), the 5G system shall be able to support a minimal user experience (e.g. user experienced data rate of [100] kbit/s, E2E latency of 50 ms, lower availability of the network of 95%).
The 5G system shall support centralized automation and management of the network in order to reduce local management tasks.
The 5G system shall support a mechanism to reduce data transfer rate at the cell edge for very large coverage area (e.g. 100 kbit/s for more than 100 km cell coverage, 1 Mbit/s for 100 km cell coverage).
The 5G system shall be able to give priority to services (e.g. e-Health) when resources are limited. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.17 Extreme long range coverage in low density areas | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.17.1 Description | A fully connected society is expected in the near future. The network access everywhere over long distances (e.g. at remote rural areas or at sea) including both humans and machines need to be supported. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.17.2 Requirements | The 5G system shall support the extreme long-range coverage (up to 100 km) in low density areas (up to 2 user/km2).
The 5G system shall support a minimum user throughput of 1 Mbit/s on DL and 100 kbit/s on UL at the edge of coverage.
The 5G system shall support a minimum cell throughput capacity of 10 Mbit/s/cell on DL (based on an assumption of 1 GB/month/sub).
The 5G system shall support a maximum of [400] ms E2E latency for voice services at the edge of coverage. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.18 Multi-network connectivity and service delivery across operators | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.18.1 Description | Given the multitude of use cases for new verticals and services, each operator, based on its business model, can deploy a network serving only a subset of the vertical industries and services. However, this should not prevent an end-user from accessing all new services and capabilities that will be accessible via 5G systems. To provide a better user experience for their subscribers with UEs capable of simultaneous network access, network operators could contemplate a variety of sharing business models and partnership with other network and service providers to enable its subscribers to access all services via multiple networks simultaneously, and with minimum interruption when moving. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.18.2 Requirements | The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis.
For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator.
When a service is offered by multiple operators, the 5G system shall be able to maintain service continuity with minimum service interruption when the serving network is changed to a different serving network operated by a different operator.
NOTE 1: A business agreement is required between the network operators.
In the event of the same service being offered by multiple operators, unless directed by the home operator's network, the UE shall be prioritized to receive subscribed services from the home operator's network.
NOTE 2: If the service is unavailable (e.g. due to lack of network coverage) from the home operator's network, the UE may be able to receive the service from another operator's network.
NOTE 3: QoS provided by the partner operator's network for the same service will be based on the agreement between the two operators and could be different than that provided by the home operator's network. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.19 3GPP access network selection | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.19.1 Description | The 5G system will support the concept of "network slices" where different NG-RANs potentially are connected to network slices of different SSTs. A 5G UE can provide assistance information (e.g. SST) to enable the network to select one or more network slices. A 5G system is foreseen to support one or more SSTs, but possibly not all existing SSTs.
A 5G network operator controls and is responsible for what SSTs that should be available to a specific UE and subscription combination, based on associated subscription type, network operator policies, network capabilities and UE capabilities. The network operator can populate the Operator Controlled PLMN Selector list with associated access technology identifiers, stored in the 5G UE, with the PLMN/RAT combinations enabling access to the SSTs that are available to the 5G UE with associated subscription.
The UE uses the list of PLMN/RAT combinations for PLMN selection, if available, typically during roaming situations. In non-roaming situations, the UE and subscription combination typically matches the HPLMN/EHPLMN capabilities and policies, from a SST perspective. That is, a 5G UE accessing its HPLMN/EHPLMN should be able to access SSTs according to UE capabilities and the related subscription.
Optionally, a 5G system supports, subject to operator policies, a User Controlled PLMN Selector list that enables the 5G UE user to specify preferred PLMNs with associated access technology identifier in priority order. The user can obtain information about suitable PLMN/RAT combination that would support services preferred by the user. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.19.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.011 [3], clause 3.2.
The 5G system shall support selection among any available PLMN/RAT combinations, identified through their respective PLMN identifier and Radio Access Technology identifier, in a prioritised order. The priority order may, subject to operator policies, be provisioned in an Operator Controlled PLMN Selector lists with associated RAT identifiers, stored in the 5G UE.
The 5G system shall support, subject to operator policies, a User Controlled PLMN Selector list stored in the 5G UE, allowing the UE user to specify preferred PLMNs with associated RAT identifier in priority order. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.20 eV2X aspects | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.20.1 Description | The 3GPP system is expected to support various enhanced V2X scenarios.
Vehicles Platooning enables the vehicles to dynamically form a group travelling together. All the vehicles in the platoon receive periodic data from the leading vehicle, in order to carry on platoon operations. This information allows the distance between vehicles to become extremely small, i.e. the gap distance translated to time can be very low (sub second). Platooning applications can allow the vehicles following to be autonomously driven.
Advanced Driving enables semi-automated or fully-automated driving. Longer inter-vehicle distance is assumed. Each vehicle and/or RSU shares data obtained from its local sensors with vehicles in proximity, thus allowing vehicles to coordinate their trajectories or manoeuvres. In addition, each vehicle shares its driving intention with vehicles in proximity. The benefits of this use case group are safer traveling, collision avoidance, and improved traffic efficiency.
Extended Sensors enables the exchange of raw or processed data gathered through local sensors or live video data among vehicles, Road Site Units, UEs of pedestrians and V2X application servers. The vehicles can enhance the perception of their environment beyond what their own sensors can detect and have a more holistic view of the local situation.
Remote Driving enables a remote driver or a V2X application to operate a remote vehicle for those passengers who cannot drive themselves or a remote vehicle located in dangerous environments. For a case where variation is limited and routes are predictable, such as public transportation, driving based on cloud computing can be used. In addition, access to cloud-based back-end service platform can be considered for this use case group. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.20.2 Requirements | The 3GPP system supports the transport of messages with different performance requirements to support V2X scenarios. The associated requirements are described in eV2X 3GPP TS 22.186 [9]. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.21 NG-RAN Sharing | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.21.1 Description | The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and acquiring spectrum and antenna locations. RAN sharing is seen as a technical solution to these issues.
In RAN Sharing operations, NG-RAN resources can be used by multiple network operators. Indirect Network Sharing is one of the possible sharing methods.
During NG-RAN sharing, the security and privacy of shared networks, non-shared networks, and subscribers need to be maintained without negative effects. Especially in the case of Indirect Network Sharing, where the involvement of the core network of the hosting operator e.g. for signalling exchange between the users and the core network of the participating operator could cause exposure of the subscriber’s information to the hosting network, an extra scrutiny of the security mechanism is expected to avoid sharing the information that is not needed for the Indirect Network Sharing operation (e.g. network topology) and protect the information that is needed for the Indirect Network Sharing operation between the hosting operator and the participating operator. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.21.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.21.2.1 General | Requirements related to NG-RAN sharing are described in 3GPP TS 22.101 [6], mainly in clause 28.2.
A 5G satellite access network shall support NG-RAN sharing. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.21.2.2 Indirect network sharing | The 5G system shall be able to support Indirect Network Sharing between the Shared NG-RAN and one or more Participating NG-RAN Operators’ core networks, by means of the connection being routed through the Hosting NG-RAN Operator’s core network.
NOTE 1: Requirements of Indirect Network Sharing assume no impact on UE.
NOTE 2: For more information on Indirect Network Sharing see Annex I.
Indirect Network Sharing shall be transparent to the user.
NOTE 3: This requirement is aligned with the existing requirement in 3GPP TS 22.101 [6] clause 4.9.
The following existing service requirements related to network sharing in 3GPP TS 22.101 [6] are applied to Indirect Network Sharing:
- clause 4.2.1,
- clause 28.2.3, and
- clause 28.2.5.
Subject to the agreement between the hosting and participating operator, the 5G system shall support a means to
enable a UE of the Participating NG-RAN Operator to:
- access their subscribed PLMN services when accessing a Shared NG-RAN, and/or,
- obtain its subscribed services, including Hosted Services, of participating operator via a Shared NG-RAN.
Based on operator policy, the 5G system shall support a mechanism to enable an authorized UE with a subscription to a Participating Operator to select and access a Shared NG-RAN.
Based on operator policy, the 5G system shall support access control for an authorized UE accessing a Shared NG-RAN and be able to apply differentiated access control for different Shared NG-RANs when more than one Shared NG-RAN are available for the Participating Operator to choose from.
Based on operator policy, the 5G system shall enable the Participating Operator to provide steering information in order to assist a UE with access network selection amongst the Hosting Operator’s available Shared RAN(s).
The 5G system shall support service continuity for UEs that are moving between different Shared NG-RANs and/or between a Shared NG-RAN and a non-Shared NG-RAN.
The 5G system shall be able to provide a UE accessing a Shared NG-RAN network with positioning service in compliance with regulatory requirements.
Subject to regulatory requirements and mutual agreement between the participating operators and the hosting operator, the requirements to support regulatory services, e.g., PWS or emergency calls apply to Indirect Network Sharing.
Subject to agreement between operators the 5G system shall enable the Shared NG-RAN of a hosting operator to provide services for inbound roaming users.
The 5G core network shall be able to support collection of charging information associated with a UE accessing a Shared NG-RAN using Indirect Network Sharing, which refers to the resource usage of hosting operator’s core network. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22 Unified access control | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22.1 Description | Depending on operator's policies, deployment scenarios, subscriber profiles, and available services, different criterion will be used in determining which access attempt should be allowed or blocked when congestion occurs in the 5G System. These different criteria for access control are associated with Access Identities and Access Categories. The 5G system will provide a single unified access control where operators control accesses based on these two.
In unified access control, each access attempt is categorized into one or more of the Access Identities and one of the Access Categories. Based on the access control information applicable for the corresponding Access Identity and Access Category of the access attempt, the UE performs a test whether the actual access attempt can be made or not.
The unified access control supports extensibility to allow inclusion of additional standardized Access Identities and Access Categories and supports flexibility to allow operators to define operator-defined Access Categories using their own criterion (e.g. network slicing, application, and application server).
NOTE: Clauses 4.1 through 4.4a of TS 22.011 are obsolete and replaced by clause 6.22.2 of this specification. However, when a UE is configured for EAB according to TS 22.011, the UE is also configured for delay tolerant service for 5G system. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22.2 Requirements | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22.2.1 General | Based on operator policy, the 5G system shall be able to prevent UEs from accessing the network using relevant barring parameters that vary depending on Access Identity and Access Category. Access Identities are configured at the UE as listed in Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in Table 6.22.2.3-1. One or more Access Identities and only one Access Category are selected and tested for an access attempt.
The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in one or more areas of the RAN.
The UE shall be able to determine whether or not a particular new access attempt is allowed based on barring parameters that the UE receives from the broadcast barring control information and the configuration in the UE.
In the case of multiple core networks sharing the same RAN, the RAN shall be able to apply access control for the different core networks individually.
The unified access control framework shall be applicable both to UEs accessing the 5G CN using E-UTRA and to UEs accessing the 5G CN using NR.
The unified access control framework shall be applicable to UEs in RRC Idle, RRC Inactive, and RRC Connected at the time of initiating a new access attempt (e.g. new session request).
NOTE 1: "new session request" in RRC Connected refers to events, e.g. new MMTEL voice or video session, sending of SMS (SMS over IP, or SMS over NAS), sending of IMS registration related signalling, new PDU session establishment, existing PDU session modification, and service request to re-establish the user plane for an existing PDU session.
The 5G system shall support means by which the operator can define operator-defined Access Categories to be mutually exclusive.
NOTE 2: Examples of criterion of operator-defined Access Categories are network slicing, application, and application server.
The unified access control framework shall be applicable to inbound roamers to a PLMN.
The serving PLMN should be able to provide the definition of operator-defined Access Categories to the UE. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22.2.2 Access identities | Table 6.22.2.2-1: Access Identities
Access Identity number
UE configuration
0
UE is not configured with any parameters from this table
1 (NOTE 1)
UE is configured for Multimedia Priority Service (MPS).
2 (NOTE 2)
UE is configured for Mission Critical Service (MCS).
3
UE for which Disaster Condition applies (note 4)
4-10
Reserved for future use
11 (NOTE 3)
Access Class 11 is configured in the UE.
12 (NOTE 3)
Access Class 12 is configured in the UE.
13 (NOTE 3)
Access Class 13 is configured in the UE.
14 (NOTE 3)
Access Class 14 is configured in the UE.
15 (NOTE 3)
Access Class 15 is configured in the UE.
NOTE 1: Access Identity 1 is used by UEs configured for MPS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN, PLMNs equivalent to HPLMN, and visited PLMNs of the home country.
Access Identity 1 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country.
NOTE 2: Access Identity 2 is used by UEs configured for MCS, in the PLMNs where the configuration is valid. The PLMNs where the configuration is valid are HPLMN or PLMNs equivalent to HPLMN and visited PLMNs of the home country. Access Identity 2 is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country.
NOTE 3: Access Identities 11 and 15 are valid in Home PLMN only if the EHPLMN list is not present or in any EHPLMN. Access Identities 12, 13 and 14 are valid in Home PLMN and visited PLMNs of home country only. For this purpose, the home country is defined as the country of the MCC part of the IMSI.
NOTE 4: The configuration is valid for PLMNs that indicate to potential Disaster Inbound Roamers that the UEs can access the PLMN. See clause 6.31.
Any number of these Access Identities may be barred at any one time. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.22.2.3 Access categories | Table 6.22.2.3-1: Access Categories
Access Category number
Conditions related to UE
Type of access attempt
0
All
MO signalling resulting from paging
1 (NOTE 1)
UE is configured for delay tolerant service and subject to access control for Access Category 1, which is judged based on relation of UE’s HPLMN and the selected PLMN.
All except for Emergency, or MO exception data
2
All
Emergency
3
All except for the conditions in Access Category 1.
MO signalling on NAS level resulting from other than paging
4
All except for the conditions in Access Category 1.
MMTEL voice (NOTE 3)
5
All except for the conditions in Access Category 1.
MMTEL video
6
All except for the conditions in Access Category 1.
SMS
7
All except for the conditions in Access Category 1.
MO data that do not belong to any other Access Categories (NOTE 4)
8
All except for the conditions in Access Category 1
MO signalling on RRC level resulting from other than paging
9
All except for the conditions in Access Category 1
MO IMS registration related signalling (NOTE 5)
10 (NOTE 6)
All
MO exception data
11-31
Reserved standardized Access Categories
32-63 (NOTE 2)
All
Based on operator classification
NOTE 1: The barring parameter for Access Category 1 is accompanied with information that define whether Access Category applies to UEs within one of the following categories:
a) UEs that are configured for delay tolerant service;
b) UEs that are configured for delay tolerant service and are neither in their HPLMN nor in a PLMN that is equivalent to it;
c) UEs that are configured for delay tolerant service and are neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in a PLMN that is equivalent to their HPLMN.
When a UE is configured for EAB, the UE is also configured for delay tolerant service. In case a UE is configured both for EAB and for EAB override, when upper layer indicates to override Access Category 1, then Access Category 1 is not applicable.
NOTE 2: When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is neither 0 nor 2, the UE applies the Access Category based on operator classification. When there are an Access Category based on operator classification and a standardized Access Category to both of which an access attempt can be categorized, and the standardized Access Category is 0 or 2, the UE applies the standardized Access Category.
NOTE 3: Includes Real-Time Text (RTT).
NOTE 4: Includes IMS Messaging.
NOTE 5: Includes IMS registration related signalling, e.g. IMS initial registration, re-registration, and subscription refresh.
NOTE 6: Applies to access of a NB-IoT-capable UEto a NB-IOT cell connected to 5GC when the UE is authorized to send exception data.
Access Category 0 in Table 6.22.2.3-1shall not be barred, irrespective of Access Identities.
NOTE: The network can control the amount of access attempts relating to Access Category 0 by controlling whether to send paging or not. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.23 QoS monitoring | |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.23.1 Description | The QoS requirements specified for particular services such as URLLC services, vertical automation communication services, and V2X, mandate QoS guarantees from the network. However, the network cannot always guarantee the required QoS of the service. An example reason for this shortcoming is that the latency and/or packet error rate increase due to interference in a radio cell. In such cases, it is critical that the application and/or application server is notified in a timely manner. Hence, the 5G system should be able to support QoS monitoring/assurance for URLLC services, V2X and vertical automation.
For more information on QoS assurance see Annex F.
Vertical automation systems are locally distributed and are typically served by wired and wireless communication networks of different types and with different characteristics. If the operation of the system or one of its sub-processes does not work properly, there is a need for quickly finding and eliminating the related error or fault in order to avoid significant operation and thus financial losses. To that end, automation devices and applications implement diagnosis and error-analysis algorithms, as well as predictive maintenance features.
Due to their inherent challenges, wireless communication systems are usually under suspicion in case an error occurs in a distributed automation application. Therefore, diagnosis and fault analysis features for 5G systems are required. The 5G system needs to provide sufficient monitoring information as input for such diagnosis features.
QoS monitoring can be used for the following activities:
- assessing and assuring the dependability of network operation;
- assessing and assuring the dependability of the communication services;
- excluding particular communication errors;
- identifying communication errors;
- analysing the location of an error including the geographic location of the involved network component (UE; front-haul component; core node);
- activation of application-related countermeasures.
This section provides requirements for both functionality and service exposure. In addition, the service exposure requirements on QoS monitoring in 22.101 [6], clause 29.2 apply. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.23.2 Requirements | The 5G system shall provide a mechanism for supporting real-time E2E QoS monitoring within a system.
NOTE 1: The end points in E2E are the termination points of the communication service within the boundary of the 5G system.
The 5G system shall support combined QoS monitoring for a group of UEs.
NOTE 1A: Combined monitoring stands for the monitoring of several UEs for which the monitoring results are reported together. An example for combined QoS monitoring is that the 5G networks monitors the service bit rates of all connections associated with the group of UEs.
The 5G network shall provide an interface to an application for QoS monitoring (e.g. to initiate QoS monitoring, request QoS parameters, events, logging information).
The 5G system shall be able to provide real time QoS parameters and events information to an authorized application/network entity.
NOTE 2: The QoS parameters to be monitored and reported can include latency (e.g. UL/DL or round trip), jitter, and packet loss rate.
The 5G system shall be able to log the history of the communication events.
NOTE 3: The communication history may include timestamps of communication events and position-related information. Examples of such information are the positions of UEs and of radio base stations associated with communication events. Communication events include instances when the required QoS is not met.
The 5G system shall support different levels of granularity for QoS monitoring (e.g. per flow or set of flows).
The 5G system shall be able to provide event notification upon detecting an error that the negotiated QoS level cannot be met/guaranteed.
The 5G system shall be able to provide information that identifies the type and the location of a communication error (e.g. cell ID).
The 5G system shall be able to provide notification of communication events to authorized entities per pre-defined patterns.
NOTE 4: An example for a communication event is that the service bit rate drops below a pre-defined threshold for QoS parameters. When such an event occurs, the authorized entity is notified, and the event is logged.
The 5G system shall support event-based QoS monitoring.
NOTE 5: An example for a triggering event is a position change of the pertinent UE. A position change can, for instance, be inferred from a 5G position service that tracks the UE.
The 5G system shall be able to respond to a request from an authorized entity to provide real-time QoS monitoring information within a specified time after receiving the request (e.g., within 5 s).
NOTE 6: The response time can be specified by the user.
The 5G system shall support real time QoS monitoring with a specified update/refresh rate.
NOTE 6a: The update/refresh rate can be specified by the user.
NOTE 6b: The update/refresh rates for QoS monitoring measurements and reporting can be different.
The 5G system shall be able to provide statistical information of service parameters and error types while a communication service is in operation.
NOTE 7: The time span for collection and evaluation of statistical values can be specified by the user.
The 5G system shall provide information on the current availability of a specific communication service in a particular area (e.g. cell ID) upon request of an authorized entity.
The 5G system shall provide a means by which an MNO informs a third party of network events (failure of network infrastructure affecting UEs in a particular area, etc.).
Based on MNO policy, the 5G system shall provide a mechanism to automatically report service degradations, communications loss, and sustained connection loss in a specific geographic area (e.g., a cell sector, a cell or a group of cells) to a third party.
NOTE 8: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE’s location, and the time(s) during which the degradation occurred.
The 5G system shall provide a mechanism for an authorised third party to report to an MNO service degradations, communication loss, and sustained connection loss.
NOTE 9: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE’s location, and the time(s) during which the degradation occurred.
NOTE 10: What the MNO does with such reports is out of scope of 3GPP.
Based on operator request, for direct network connection scenarios in non-public networks, the 5G system shall be able to activate/deactivate efficient QoS monitoring with a finer granularity (e.g. per data packet) in a specific QoS flow (e.g. supporting URLLC services) to report on data packets not meeting the required QoS level.
NOTE 11: The QoS parameters to be monitored and reported can include latency (e.g. UL or DL).
NOTE 12: The above requirement does not assume UE impacts. |
ae111ecbab6e4b668cabf5bf3611373d | 22.261 | 6.24 Ethernet transport services |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.