hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.12 Self backhaul
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.13 Flexible broadcast/multicast service
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.14 Subscription aspects
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.15 Energy efficiency
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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 (e.g. energy rationing).
Energy related information can include ratio of renewable energy and carbon emission information when available.
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
NOTE: The following requirements are expected to produce net energy saving in the 5G network i.e. the energy used to operate the network and deliver services based on these requirements is less that the energy saved.
The following requirements are subject to regulatory requirements, in particular to keep delivering critical services such as emergency calls, PWS, MPS and MCS to the extent possible.
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.
Subject to operator’s policy, regulatory requirements and user consent, the 5G network shall enable the operator to provide means to degrade service performance (e.g. QoS, bitrate) to meet energy rationing constraints.
NOTE 4: This assumes that the degradation in service performance will reduce energy consumption in the 5G network to meet energy rationing constraints.
Subject to operator’s policy, regulatory requirements and user consent, the 5G network shall support subscription policies that include alternative (i.e. degraded) service performance (e.g. QoS parameters, maximum bitrate) of services with QoS criteria for energy saving reasons.
NOTE 5: This requirement implies that the policies could disallow some network energy saving action to be performed for some service with QoS criteria e.g. based on applicability conditions (e.g. slice, application).
Subject to operator’s policy, the 5G network shall be able to support a means to target per UE energy saving actions, based on subscription policies.
Subject to operators’ policy, regulatory requirements, and user consent, the 5G system shall provide mechanisms to adjust communication service (e.g. user plane path, suitable Service Hosting Environment, defer background traffic delivery) and control the access of UEs to the network (e.g. block traffic, disable or defer specific application traffic) considering the change of energy supply mix of the network as one of the factors or based on the energy-related characteristics of the network.
NOTE 6: It is assumed that 5G network can obtain energy supply mix information. How to obtain this information is out of scope of this requirement. The adjustment is not assumed to be real-time. It is up to the operators’ policy to define the time difference between obtaining the change on energy supply mix information and the actual adjustment of the communication service.
NOTE 7: Degradation of service experience resulting from the adjustment is subject to subscription-based user consent.
Subject to operator’s policy and regulatory requirements, the 5G network shall be able to trigger charging events corresponding to an impacted UE when degrading performance of services with QoS criteria (e.g. to a lower bitrate) in order to achieve energy saving.
Subject to user consent, operator policy and regulatory requirements, the 5G network shall be able to assist an authorized 3rd party to identify a set of target UEs for whom to adjust the provided application service, considering criteria such as the current and future (e.g. predicted) energy-related characteristics of their serving network.
NOTE 8: Future (e.g. predicted) information can refer to the next hour(s) or day(s), to the remaining serving time before shutdown/shortage etc.
6.15a.3 Support of different energy states
6.15a.3.1 Description
Supporting 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 in NPN and also all kinds of NG-RAN deployment scenarios.
6.15a.4.2 Requirements
NOTE 0: Calculation of energy-related information as described in the following requirements can be done by means of averaging or applying a statistical model to a combination of measurements, service configuration, statistics, computations and estimates. The requirements do not imply that some form of 'real time' monitoring nor exact measurement is required (e.g. at flow level). Instead, they can be met by means of attribution as accurate as possible, e.g. based on data volume and network’s carbon and/or energy KPIs or metrics of the communication service, which could be collected either from the network or from sources external to 3GPP (e.g. energy supply mix provided by electricity grid providers).
The level of accuracy of attribution and associated time granularity can impact what can be done with the energy-related information.
The energy-related information considered in the following requirements only relates to the use of the communication service provided by a telecom operator to its home network subscribers, as a single part of the end-to-end service chain.
The following requirements do not apply to the energy-related information of other providers outside of 3GPP scope potentially involved in the same service chain (e.g. video streaming providers).
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.
The performance requirements related to the exposure of network energy-related characteristics such as energy consumption and CO2e emissions depending on the target use case are documented in clause 7.13.
6.15a.5.2 Requirements
NOTE 0: Exposure and measurement have an energy cost. The goal of the following requirements is to motivate and inform improved use of energy, e.g. energy savings or less environmental impact. This benefit is meant to be greater than the cost. Therefor mechanisms to support exposure and measurement are expected to have minimal energy and environmental impact.
Refer to clause 6.15a.4.2 of the present document for requirements related to monitoring and measurement.
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.
Subject to operator’s policy, regulatory requirements and user consent, the 5G network shall be able to collect, and expose to authorized 3rd parties, the carbon equivalent emissions resulting from the use of the communication service, related to one or more specific UEs of home network subscribers (e.g. fleet of vehicles, IoT devices, company phones etc), over a specific time period (e.g. month etc).
NOTE 3: This requirement does not apply to the use of the communication service when roaming.
NOTE 4: Exposing carbon equivalent emissions can be based on data volume and operator’s energy consumption and carbon intensity information. In particular, it is expected such exposed information to be provided on demand, not more granularly than on a per-day basis.
NOTE 5: The exposed carbon equivalent emissions can further include information to allow to compare subscribers of e.g. the same PLMN, NPN or slice over the same time period. Such information can take the form of e.g. a range (i.e. minimum and maximum) or average of carbon equivalent emissions per subscriber, or the form of a category, class or score of carbon emissions (e.g. A to F, 1 to 5).
Subject to operator’s policy and user consent, the 5G network shall be able to expose to an authorized 3rd party information about network energy consumption and carbon equivalent emissions for a specific service data flow.
NOTE 6: One of the goals of exchanging Energy Consumption data and CO2e data for a specific individual service data flow is to enable applications to provide an indication to the user during the communication service. The frequency of such indications should be meaningful to the user and is assumed to be configurable, e.g. frequency or updates of thresholds for reporting (e.g. based on e.g. a session, down to once per minute).
Subject to operator’s policy, regulatory requirements and user consent, the 5G system shall be able to expose to an authorized 3rd party the current and expected energy-related characteristics of the network resources used in serving a UE.
NOTE 7: This information can be used by applications to schedule non time-critical data transfer to or from the UE.
Subject to operator’s policy, regulatory requirements and user consent, the 5G system shall be able to provide UEs with information related to the current energy-related characteristics of their serving network.
NOTE 8: A subset of target UEs can be selected, for example, based on their location, their energy consumption in the network, their service experience, etc.
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.16 Markets requiring minimal service levels
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.17 Extreme long range coverage in low density areas
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.18 Multi-network connectivity and service delivery across operators
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.19 3GPP access network selection
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
6.20 eV2X aspects
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.21 NG-RAN Sharing
| |
f9a197ded31c88efb7acaa77f7788f20
|
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. For the NG-RAN resources deployed onboard satellites, they can be used by both satellite mobile network operators and terrestrial network operators together by proper network operations. Indirect Network Sharing is one of the possible sharing methods.
In addition, Indirect Network Sharing can offer more options for an operator to provide services to UEs via Shared NG-RAN, when a Disaster Condition occurs in a geographic area, which causes the loss of its UEs’ previous network connection, until the Disaster Condition is not applicable anymore.
NOTE: This scenario assumes that NG-RAN and/or core network of at least one operator is unavailable but that the NG-RAN and core network of at least another operator is available in the disaster area. In case the affected operator has multiple core networks in different geographic areas, when a core network of that operator has broken down in the specific disaster area, the other core network from the different area can be used temporarily in this case.
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.21.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.21.2.2 Indirect network sharing
|
NOTE 1: Charging requirements for "Network Sharing" can be found in clause 9.6 of this document.
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 2: Requirements of Indirect Network Sharing assume no impact on UE.
NOTE 3: For more information on Indirect Network Sharing see Annex I.
Indirect Network Sharing shall be transparent to the user.
NOTE 4: 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 regulatory requirements or operator policy, the 5G network shall support a PLMN operator to be made aware of the failure or recovery of NG-RAN and/or core network in other PLMN(s) in the same area when the Disaster Condition applies, or when the Disaster Condition is not applicable anymore.
Subject to regulatory requirements or operator policy, the 5G network shall support a PLMN operator to be made aware of the availability of other PLMN(s) as Hosting NG-RAN Operator(s) via Indirect Network Sharing in the same area when the Disaster Condition applies.
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.
NOTE 5: The above requirement is applicable to Disaster Condition 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 network shall be able to apply differentiated access control for an authorized UE connecting to Participating Operator’s core network e.g. depending on specifc geographic areas within the coverage of a shared satellite NG-RAN.
Based on operator policy, the 5G network shall minimize network congestion caused by Indirect Network Sharing when a Disaster Condition applies.
NOTE 6: Population density in the different areas where Disaster Condition apply needs to be considered.
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).
Subject to the agreement between operators, the 5G network shall enable the Participating Operator to assist an authorized UE with access network selection when this UE is located both within the coverage of a shared satellite NG-RAN and within the coverage of terrestrial NG-RANs.
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 network shall be able to enable Indirect Network Sharing only when the Disaster Condition applies in a specific area and disable it when no longer applicable.
NOTE 7: It is assumed operators can have sharing agreement for Disaster Condition in the area.
NOTE 8: It is assumed that during a Disaster Condition, previous network communication is temporarily disabled.
The 5G network shall be able to provide a means for a UE to return to the PLMN used prior to Indirect Network Sharing, when a Disaster Condition is no longer applicable.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.22 Unified access control
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.22.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.23 QoS monitoring
| |
f9a197ded31c88efb7acaa77f7788f20
|
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.
|
f9a197ded31c88efb7acaa77f7788f20
|
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.
Subject to user consent, the 5G network shall provide suitable means for an authorized 3rd party to provided E2E QoS parameters for a service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.24 Ethernet transport services
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.24.1 Description
|
This clause includes common, fundamental Ethernet transport requirements, and any requirements necessary to support a 5G LAN-type service. The requirements applicable to the 5G system for supporting cyber-physical applications using Ethernet are described in 3GPP TS 22.104 [21].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.24.2 Requirements
|
The 3GPP system shall be able to support an Ethernet transport service.
The 5G network shall support the routing of non-IP packet (e.g. Ethernet frame) efficiently for private communication between UEs within a 5G LAN-type service.
The 5G network shall be able to provide the required QoS (e.g. reliability, latency, and bandwidth) for non-IP packet (e.g. Ethernet frame) for private communication between UEs within a 5G LAN-type service.
The Ethernet transport service shall support routing based on information extracted from Virtual LAN (VLAN) ID by the 3GPP system.
The Ethernet transport service shall support the transport of Ethernet frames between UEs that Ethernet devices are connected to.
The Ethernet transport service shall support the transport of Ethernet frames between a UE that an Ethernet device is connected to and an Ethernet network in DN (Data Network).
NOTE: If more than one Ethernet devices need to be connected to a UE, they can be connected using an Ethernet switch between the devices and the UE.
The Ethernet transport service shall support the transport of Ethernet broadcast frames.
The Ethernet transport service shall support traffic filtering and prioritization based on source and destination MAC addresses.
The Ethernet transport service shall support traffic filtering and prioritization based on Ethertype (including multiple Ethertypes in double tagging).
The Ethernet transport service shall support traffic filtering and prioritization based on IEEE 802.1Q VLAN tags (including double tagging).
The Ethernet transport service shall support routing based on information extracted by the 3GPP system from the Bridge Protocol Data Units created in the Ethernet network based on a Spanning Tree Protocol (e.g. RSTP, MSTP [54]).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.25 Non-public networks
|
6.25.1 Description
Non-public networks are intended for the sole use of a private entity such as an enterprise, and can be deployed in a variety of configurations, utilising both virtual and physical elements. Specifically, they can be deployed as completely standalone networks, they can be hosted by a PLMN, or they can be offered as a slice of a PLMN.
In any of these deployment options, it is expected that unauthorized UEs, those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs can be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs can access both a non-public network and a PLMN where specifically allowed.
In addition to the requirements in this section, all requirements and KPIs in other sections of TS 22.261, that are not exclusively for PLMNs (i.e. explicitly using the term PLMN) also apply to (i.e. are in scope of) non-public networks, except the requirements in sections 5.1, 6.2.4 and 6.3.2.2. However, hereby it is important to realize that requirements and features are optional to be supported by a non-public network, since non-public network deployments can include different subsets of 5G system requirements and services described in the sections of TS 22.261. The deployment choices are dependent on verticals needs and regulation.
6.25.2 Requirements
The 5G system shall support non-public networks.
The 5G system shall support non-public networks that provide coverage within a specific geographic area.
The 5G system shall support both physical and virtual non-public networks.
The 5G system shall support standalone operation of a non-public network, i.e. a non-public network may be able to operate without dependency on a PLMN.
Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall support for non-public network subscribers:
- access to subscribed PLMN services via the non-public network;
- seamless service continuity for subscribed PLMN services between a non-public network and a PLMN;
- access to selected non-public network services via a PLMN;
- seamless service continuity for non-public network services between a non-public network and a PLMN.
Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall enable a UE, with multiple subscriptions, to simultaneously access multiple non-public networks and corresponding services, via those NPNs or via a different network (PLMN or NPN).
Subject to regional or national regulatory requirements for emergency services, 5G system shall be able to support IMS emergency services for non-public networks.
A non-public network subscriber to access a PLMN service shall have a service subscription using 3GPP identifiers and credentials provided or accepted by a PLMN.
The 5G system shall support a mechanism for a UE to identify and select a non-public network.
NOTE: Different network selection mechanisms may be used for physical vs virtual non-public networks.
The 5G system shall support identifiers for a large number of non-public networks to minimize collision likelihood between assigned identifiers.
The 5G system shall support a mechanism to prevent a UE with a subscription to a non-public network from automatically selecting and attaching to a PLMN or non-public network it is not authorized to select.
The 5G system shall support a mechanism to prevent a UE with a subscription to a PLMN from automatically selecting and attaching to a non-public network it is not authorized to select.
The 5G system shall support a mechanism for a PLMN to control whether a user of a UE can manually select a non-public network hosted by this PLMN that the UE is not authorized to select automatically.
The 5G system may broadcast a human readable network name that a UE may display for manual selection of a non-public network.
The 5G system shall support a change of host of a non-public network from one PLMN to another PLMN without changing the network selection information stored in the UEs of the non-public network.
The 5G system shall enable an NPN to support multiple third-party service providers.
In the event of a loss of communication between RAN and core network, the 5G system shall be able to provide capability to securely re-connect an NPN network function within a short period of time (< 1s).
6.25.3 Groups of interconnected SNPNs
A group of interconnected SNPNs consists of one of more pairs of interconnected SNPNs. The determination of whether a given SNPN can or should be able to participate within a given group of interconnected SNPNs if based on prior arrangement and out of band configuration. How these arrangements and configuration are made is outside the scope of 3GPP and the 5G network.
NOTE 1: The interconnect can be established on temporary basis forming a group of interconnected SNPNs with variable topologies.
NOTE 2: It is assumed the interconnected SNPNs have overlapping radio coverage
The following requirements apply for enabling groups of interconnected SNPNs
Based on SNPN configuration and subject to SNPN operator's policy, the 5G network shall be able to support mechanisms to enable interconnect between two or more SNPNs.
Based on SNPN configuration and subject to SNPN operator’s policy, the 5G network shall be able to support prioritization of resources for a service offered by a SNPN that is consumed by users attached to other interconnected SNPNs.
Based on SNPN configuration and subject to SNPN operator’s policy, the 5G network shall be able to support service continuity for UEs that are moving between interconnected SNPNs.
6.25.4 SNPN cellular hotspots
The following requirements apply to support of Stand-alone Non-Public Network (SNPN) cellular hotspots:
NOTE 1: SNPN hotspot refers to a connectivity hotspot based on 3GPP 5G network technology that provides services in a similar way as provided by WLAN hotspots. Charging requirements are considered out of scope for this functionality.
Based on the SNPN configuration, the 5G network shall support a mechanism for an SNPN to be able to interconnect with a large number of SNPN Credential Providers with which the SNPN might not have preconfigured information detailing the IP addresses used by these SNPN Credential Providers to interconnect with the SNPN.
Based on the SNPN configuration, the 5G network shall support a mechanism for an SNPN Credential Provider to be able to interconnect with a large number of SNPNs with which the SNPN Credential Provider might not have preconfigured information detailing the IP addresses used by these SNPNs to interconnect with the SNPN Credential Provider.
Based on the SNPN configuration, the 5G network shall support a mechanism for an SNPN to be able to determine how to connect to an SNPN Credential Provider capable of verifying the identity presented by a user attempting to connect to that SNPN.
Based on the SNPN configuration, the 5G network shall support a mechanism for an SNPN to be able to securely interconnect with an SNPN Credential Provider in deployments where the required security information is not preconfigured.
Based on the SNPN configuration, the 5G network shall support a mechanism for an SNPN to enable an SNPN Credential Provider to securely notify events (e.g., a user’s subscription ending) to the SNPN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26 5G LAN-type service
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.1 Description
|
5G expands the scope and reach of 3GPP-defined technologies. There are multiple market segments in the realm of residential, office, enterprise and factory, where 5G will need to provide services with similar functionalities to Local Area Networks (LANs) and VPN’s but improved with 5G capabilities (e.g. high performance, long distance access, mobility and security).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.1 General
|
NOTE: Charging requirements for "5G LAN-type service" can be found in clause 9.2 of this document.
The 5G system shall support 5G LAN-type service in a shared RAN configuration.
The 5G system shall support 5G LAN-type service over a wide area mobile network.
The 5G network shall support service continuity for 5G LAN-type service, i.e. the private communication between UEs shall not be interrupted when one or more UEs of the private communication move within the same network that provides the 5G LAN-type service.
The 5G system shall support use of unlicensed as well as licensed spectrum for 5G LAN-type services.
The 5G system shall enable the network operator to provide the same 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.2 5G LAN-virtual network (5G LAN-VN)
|
A UE shall be able to select a 5G LAN-VN, that the UE is a member of, for private communication.
A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands.
The 5G system shall be able to support large numbers of small 5G LAN-VNs.
NOTE: Targeting residential deployments translate into millions of 5GLAN-VN per operator per country. These residential 5G LAN-VNs typically contain between 10-50 devices.
The 5G LAN-VN shall support member UEs that are subscribed to different PLMNs, e.g. a 5G LAN-VN may span multiple countries and have member UEs that have a subscription to a PLMN in their home country.
The 5G system shall support on-demand establishment of UE to UE, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet.
The 5G network shall ensure that only member UEs of the same 5G LAN-VN are able to establish or maintain private communications among each other using 5G LAN-type service.
The 5G system shall allow member UEs of a 5G LAN-VN to join an authorized multicast session over that 5G LAN-VN.
The 5G system shall be able to restrict private communications within a 5G LAN-VN based on UE’s location (i.e. when the UE moves out of the area it can no longer communicate on the 5G LAN-VN).
The 5G network shall enable member UEs of a 5G LAN-VN to use multicast/broadcast over a 5G LAN-type service to communicate with required latency (e.g. 180 ms).
The 5G system shall support a mechanism to provide consistent QoE to all the member UEs of the same 5G LAN-VN.
The 5G system shall support routing based on a private addressing scheme within the 5G LAN-VN.
The 5G system shall support a communication path between a non-3GPP device in the CPN and a UE in the 5G-LAN VN via the eRG of the CPN, for an eRG that is part of the 5G LAN-VN.
The 5G network shall support a communication path between a UE in the 5G-LAN and the non-3GPP devices in the CPN via the legacy residential gateway of the CPN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.3 Creation and management
|
The 5G network shall enable the network operator to scale up/down a 5G LAN-VN, e.g. the coverage, capacity for efficient consumption of network resources.
The 5G network shall enable the network operator to create, manage, and remove 5G LAN-VN including their related functionality (subscription data, routing and addressing functionality).
The 5G network shall enable the network operator to add one or more authorized UEs to an existing 5G LAN-VN.
NOTE 1: A UE needs to be authorized by the MNO to use 5G LAN-type service before it can be added to any 5G LAN-VN.
NOTE 2: some use cases will require user permission for a UE to be added to a 5G LAN-VN.
The 5G system shall enable the network operator to add an authorized UE to multiple independent 5G LAN-VNs.
The 5G network shall enable the network operator to remove one or more UEs from an existing 5G LAN-VN.
NOTE 3: Removing a UE from a 5G LAN-VN does not have impact on other 5G LAN-VNs that the UE is a member of.
The 5G system shall enable the network operator to configure a 5G LAN-VN that is available only within a geographical area.
Based on MNO policy, the 5G network shall provide suitable means to allow an authorised third party to
- monitor changes in QoS policy that pertains to LAN-VN performance;
- configure and receive information regarding the achieved performance for a specific UE;
- configure and receive information regarding the achieved performance for a specific network (e.g, number of active UEs, UE status (connection status) change events in 5G LAN-VN);
- receive notification of changes in specific configuration aspects of the UE in the VN (e.g., changes in group membership information.)
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.4 Privacy
|
The 5G system shall be able to prevent the sharing of a UE’s identifying information (e.g. SUPI, MSISDN) on private communication among UEs using 5G LAN-type service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.5 Traffic types
|
A 5G system shall support all media types (e.g. voice, data, multimedia) for 5G LAN-type service.
The 5G system shall support traffic scenarios typically found in a home setting (from sensors to video streaming, relatively low amount of UEs per group, many devices are used only occasionally) for 5G LAN-type service.
The 5G system shall support traffic scenarios typically found in an office setting (from sensors to very high data rates e.g. for conferencing, medium amount of UEs per group) for 5G LAN-type service.
The 5G system shall support traffic scenarios typically found in an industrial setting (from sensors to remote control, large amount of UEs per group) for 5G LAN-type service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.6 Discovery
|
The 5G system shall enable a member UE to discover other member UEs within the same 5G LAN-VN.
The 5G LAN-type service shall be able to support existing non-3GPP service discovery mechanisms (e.g. mechanisms to discover printers).
6.26.2.7 (void)
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.8 Indirect communication mode
|
The 5G system shall support 5G LAN-type service for authorized UEs using indirect network connection or direct network connection.
The 5G network shall be able to provide a remote UE using 5G LAN-type service with same level of service as if the remote UE would be using a direct network connection (i.e. provide required QoS for the Ethernet packets transferred between remote UE and relay UE if they are using 3GPP access).
The 5G network shall be able to support service continuity for the private communication between a remote UE with other member UEs of the same 5G LAN-VN, when the remote UE changes from one relay UE to another or when the UE changes between direct and indirect network connection.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.26.2.9 Service exposure
|
Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to create/remove a 5G LAN-VN.
Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to manage a 5G LAN-VN dedicated for the usage by the trusted third-party, including the address allocation.
Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to authorize/deauthorize UEs to access a specific 5G LAN-VN managed by the trusted third-party.
Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to add/remove an authorized UE to/from a specific 5G LAN-VN managed by the trusted third-party.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.27 Positioning services
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.27.1 Description
|
5G positioning services aims to support verticals and applications with positioning accuracies better than 10 meters, thus more accurate than the ones of TS 22.071 [24] for LCS. High accuracy positioning is characterized by ambitious system requirements for positioning accuracy in many verticals and applications, including regulatory needs.
In Location-Based-Services and eHealth, higher accuracy is instrumental to new services and applications, both outdoor and indoor.
For example, on the factory floor, it is important to locate assets and moving objects such as forklifts, or parts to be assembled. Similar needs exist in transportation and logistics, for example rail, road and use of UAVs. In some road user cases, UE's supporting V2X application(s) are also applicable to such needs. In cases such as guided vehicles (e.g. industry, UAVs) and positioning of objects involved in safety-related functions, availability needs to be very high.
Mission Critical Organizations require mission critical services to have accurate positioning such that first responders can be located at all times during normal and critical operations, indoors as well as outdoors. The level of positioning accuracy (and other KPIs) required is much more stringent than that required by local and regional regulatory requirements for commercial 5G users.
Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to dynamically adjust partial configuration (i.e. create, manage, and remove) of the 5G LANs for the authorized 5G LAN-VN capable UEs.
NOTE: 5G LAN-VN capable UEs means the operator authorizes UEs to use 5G LAN-type service. The joining to the 5G LAN-VN group and the configuration to the 5G LAN-VN can be dynamically configured by an trusted third party.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.27.2 Requirements
|
The 5G system shall provide 5G positioning services in compliance with regulatory requirements.
NOTE 1: example of regulatory requirements encompasses requirements on emergency calls (e.g. e911), reliability and safety requirement (RAMS) applicable to some use cases and verticals, implementation of Priority, Precedence, Preemption (PPP) mechanisms to ensure sufficient reliability metrics are reached.
The 5G system shall provide different 5G positioning services, supported by different single and hybrid positioning methods to supply absolute and relative positioning.
NOTE 2: hybrid positioning methods include both the combination of 3GPP positioning technologies and the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as, GNSS (e.g. Beidou, Galileo, GPS, Glonass), Network-based Assisted GNSS and High-Accuracy GNSS, Terrestrial Beacon Systems, dead-reckoning sensors (e.g. IMU, barometer), WLAN/Bluetooth-based positioning.
The 5G system shall enable an MCX UE to use the 5G positioning services to determine its position with the associated uncertainty/confidence of the position, on request, triggered by an event or periodically.
The 5G System shall be able to provide the 5G positioning services in case of roaming.
The 5G system shall support mechanisms to determine the UE’s position-related data for period when the UE is outside the coverage of 3GPP RAT-dependent positioning technologies but within the 5G positioning service area (e.g. within the coverage of satellite access).
The 5G system shall be able to make the position-related data available to an application or to an application server existing within the 5G network, external to the 5G network, or in the User Equipment.
NOTE 3: the position service latency can be tailored to the use cases.
The 5G system shall be able to manage and log position-related data in compliance with applicable traceability, authentication and security regulatory requirements.
The 5G network shall be able to request the UE to provide its position-related-data on request—together with the accuracy of its position—triggered by an event or periodically and to request the UE to stop providing its position-related data periodically.
NOTE 4: This requirement does not preclude whether the position is computed in the UE or elsewhere in the 5G System (e.g. core network).
The 5G system shall support mechanisms to configure dynamically the update rate of the position-related data to fulfil different performances (e.g. power consumption, position service latency) or different location modes.
NOTE 5: for example, the 5G System needs to be able to request the UE to provide its location periodically with an update rate ranging from one location every [1 s to 10 s] in location normal mode to one location every [30 s to 300 s, or more] in location power saving mode. The 5G System needs to allow UEs to sleep for extended periods (e.g. one week), without requiring the UE to update its position data.
The 5G system shall allow the UE to trigger a different update rate of the position-related data based on whether the UE is moving or not.
The 5G system shall be able to determine the position-related data of the 5G positioning services with any update rate ranging from one set of position-related data every 0,1 s to one set of position-related data every month.
NOTE 6: the position service latency can be tailored to the use cases.
The 5G System shall be able to negotiate the positioning methods according to the operator's policy or the application’s requirements or the user's preferences and shall support mechanisms to allow the network or the UE to trigger this negotiation.
The 5G system shall supply a method for the operator to configure and manage different positioning services for different users.
The 5G system shall be able to determine the reliability, and the uncertainty or confidence level, of the position-related data.
The 5G system shall be able to access to the positioning methods used for calculating the position-related data and to the associated uncertainty/confidence indicators.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.28 Cyber-physical control applications in vertical domains
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.28.1 Description
|
The 5G system is expected to meet the service requirements for cyber-physical control applications in vertical domains.
A vertical domain is a particular industry or group of enterprises in which similar products or services are developed, produced, and provided. Automation refers to the control of processes, devices, or systems in vertical domains by automatic means. The main control functions of automated control systems include taking measurements, comparing results, computing any detected or anticipated errors, and correcting the process to avoid future errors. These functions are performed by sensors, transmitters, controllers, and actuators.
Cyber-physical systems are to be understood as systems that include engineered, interacting networks of physical and computational components. Cyber-physical control applications are to be understood as applications that control physical processes. Cyber-physical control applications in automation follow certain activity patterns, which are open-loop control, closed-loop control, sequence control, and batch control.
Communication services supporting cyber-physical control applications need to be ultra-reliable, dependable with a high communication service availability, and often require low or (in some cases) very low end-to-end latency.
Communication in automation in vertical domains follows certain communication patterns. The most well-known is periodic deterministic communication, others are a-periodic deterministic communication and Smart Grid.
Smart Grid is a term that refers to enhanced cyber-physical control of electrical grids and to related application. Smart Grid operation can cover power generation, transmission, distribution, and consumption, which can require high communication service availability and communication service reliability, and in some cases a low end-to-end latency with more accurate clock synchronization. 5G system functionalities can be used for Smart Grid control, monitoring, availability assurance, service security, isolation and etc.Communication for cyber-physical control applications supports operation in various vertical domains, for instance industrial automation and energy automation.
For more information about cyber-physical control applications in specific vertical domains, see clauses D.1 to D.4.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.28.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.28.2.1 General
|
The 5G system supports the communication services for cyber-physical control applications in the vertical domains of factories of the future (smart manufacturing), electric power distribution, smart grid, central power generation, and rail-bound mass transit. The associated requirements are described in 3GPP TS 22.104 [21].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.28.2.2 Smart Grid
|
For the 5G system to support the Smart Grid, the 5G systems needs to fulfil at minimum the following requirements.
- 3GPP TS 22.104 clauses 5.2, 5.3, and 5.6 for requirements related to periodic communication, aperiodic communication, and clock synchronization;
- 3GPP TS22.104, clause 5.6.1, 5.6C, 9 and A.4 for Smart Grid specific service requirements;
- 3GPP TS 22.261, clauses 6.10, 6.13, 6.14, and 6.26 for requirements related to the support of secured communication between the 5G system and a trusted third-party;
- 3GPP TS 22.261, clauses 6.23 for the requirements related to information exchange between the 5G system and a trusted third-party;
- 3GPP TS 22.261, clause 8.9 for the requirements on security.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.29 Messaging aspects
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.29.1 Description
|
The 5G system is expected to support advanced capabilities and performance of messaging service especially for massive IoT communication which are introduced by the MSGin5G Service [22]. The MSGin5G Service provides one to one, group and broadcast message services for thing-to-thing and person-to-thing communication with low end-to-end latency and high reliability of message delivery, in a resource efficient manner to optimize the resource usage of the both control plane and user plane in the network, and power saving in the user devices.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.29.2 Requirements
|
The 5G system supports the MSGin5G Service. The associated service level requirements of the MSGin5G Service are described in 3GPP TS 22.262 [22].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.30 Steering of roaming
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.30.1 Description
|
Steering of roaming allows the HPLMN (or subscribed NPN) to steer a UE to a VPLMN or NPN on which the HPLMN (or subscribed NPN) wants the UE to register, when the UE registers on another VPLMN or NPN. This capability can be needed for reasons e.g. reselection to a higher priority PLMN, or NPNs, based on business arrangements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.30.2 Requirements
|
The following set of requirements complement the requirements listed in 3GPP TS 22.011 [3], clause 3.2.2.8.
The 5G system shall support a mechanism for the HPLMN to control the timing when a UE registered on a VPLMN, in automatic mode (see clause 3.1 of TS 23.122 [25]) and currently in CONNECTED mode, enters IDLE mode and initiates higher priority PLMN selection based on the type of ongoing communication.
NOTE 1: Changes needed to support the above requirement are expected to have minimum impact on the 5G system. UE is expected to initiate the above-mentioned PLMN selection e.g. by locally releasing the established N1 NAS signalling connection.
NOTE 1a: The requirement above applies also to the case of a UE registered to a non-subscribed (standalone) NPN, in order to select a higher priority PLMN or NPN.
The UE shall be able to delay conforming to steering of roaming control information from the HPLMN while it is engaged in priority service (e.g. emergency call, MPS session), or a service defined by HPLMN policy not to be interrupted (e.g. MMTEL voice/video call).
NOTE 2: The HPLMN policy can take into account the user's preference for the service(s) not to be interrupted. User preferences can be communicated utilizing non-standard operator-specific mechanisms, e.g. web-based.
The mechanism mentioned above in this clause shall be available to the HPLMN even if the VPLMN the UE is registered on is compliant to an earlier release of the 5G system.
The 5G system shall support mechanisms to enable a credentials holder (e.g. HPLMN or subscribed standalone NPN) to send steering of roaming information to a UE for selecting standalone NPNs (e.g prioritized list of preferred NPNs).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31 Minimization of Service Interruption
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31.1 Description
|
A mobile network can fail to provide service in the event of a disaster (for example a fire.) The requirements listed in this clause provide the 5GS with the capability to mitigate interruption of service. UEs can obtain service in the event of a disaster, if there are PLMN operators prepared to offer service. The minimization of service interruption is constrained to a particular time and place. To reduce the impact to the 5G System and EPS of supporting Disaster Roaming, the potential congestion resulting from an influx or outflux of Disaster Inbound Roamers is taken into account.
Scenarios where network failures render the network subject to a disaster unable to authenticate its subscribers are excluded.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31.2.1 General
|
Subject to regulatory requirements or operator's policy, 3GPP system shall be able to enable a UE of a given PLMN to obtain connectivity service (e.g. voice call, mobile data service) from another PLMN for the area where a Disaster Condition applies.
Subject to regulatory requirements, operator's policy or UE capabilities, the 3GPP system shall be able to support a UE, with 5G-only national roaming access to a VPLMN, to obtain 4G connectivity service from that VPLMN in the area where a Disaster Condition applies.
NOTE: In the above scenario, voice call service is provided by IMS in HPLMN.
Subject to regulatory requirements or operator's policy, in case of shared RAN between participating PLMNs, the 3GPP system shall be able to support a UE of a given PLMN to obtain connectivity service (e.g. voice call, mobile data service) from another participating network when a Disaster Condition applies to the UE’s PLMN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31.2.2 Disaster Condition
|
The 3GPP system shall enable UEs to obtain information that a Disaster Condition applies to a particular PLMN or PLMNs.
NOTE: If a UE has no coverage of its HPLMN, then obtains information that a Disaster Condition applies to the UE's HPLMN, the UE can register with a PLMN offering Disaster Roaming service.
The 3GPP system shall support means for a PLMN operator to be aware of the area where Disaster Condition applies.
The 3GPP system shall be able to support provision of service to Disaster Inbound Roamer only within the specific region where Disaster Condition applies.
The 3GPP system shall be able to provide efficient means for a network to inform Disaster Inbound roamers that a Disaster Condition is no longer applicable.
Subject to regulatory requirements or operator’s policy, the 3GPP system shall support a PLMN operator to be made aware of the failure or recovery of other PLMN(s) in the same country when the Disaster Condition is applies, or when the Disaster Condition is not applicable.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.31.2.3 Disaster Roaming
|
NOTE: Charging requirements for "Minimization of Service Interruption" can be found in clause 9.7 of this document.
The 3GPP system shall be able to provide means to enable a UE to access PLMNs in a forbidden PLMN list if a Disaster condition applies and no other PLMN is available except for PLMNs in the forbidden PLMN list.
The 3GPP system shall provide means to enable that a Disaster Condition applies to UEs of a specific PLMN.
The 3GPP system shall be able to provide a resource efficient means for a PLMN to indicate to potential Disaster Inbound Roamers whether they can access the PLMN or not.
Disaster Inbound Roamers shall perform network reselection when a Disaster Condition has ended.
The 3GPP system shall minimize congestion caused by Disaster Roaming.
The 5G system and EPS shall support a mechanism for the HPLMN to control whether a UE, with HPLMN subscription, should apply Disaster Roaming when a Disaster Condition arises (in the HPLMN or a VPLMN).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.32 UAV aspects
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.32.1 Description
|
The 3GPP system is expected to support various enhanced UAV scenarios, especially for a wide range of applications and scenarios by using low altitude UAVs in various commercial and government sectors.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.32.2 Requirements
|
The 3GPP system supports service requirements and KPIs related to command and control (C2), payload (e.g. camera) and the operation of radio access nodes on-board of UAVs. The associated requirements are described in 3GPP TS 22.125 [26].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.33 Video, imaging and audio for professional applications
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.33.1 Description
|
Audio-Visual (AV) production includes television and radio studios, live news-gathering, sports events, music festivals, among others. Typically, numerous wireless devices such as microphones, in-ear monitoring systems or cameras are used in these scenarios. In the future, the wireless communication service for such devices are expected to be provided by a 5G system. AV production applications require a high degree of confidence, since they are related to the capturing and transmission of data at the beginning of a production chain. This differs drastically when compared to other multimedia services because the communication errors will be propagated to the entire audience that is consuming that content both live and on recorded media. Furthermore, the transmitted data is often post-processed with filters which could actually amplify defects that would be otherwise not noticed by humans. Therefore, these applications call for uncompressed or slightly compressed data, and very low probability of errors. These devices will also be used alongside existing technologies which have a high level of performance and so any new technologies will need to match or improve upon the existing workflows to drive adoption of the technology.
The 3GPP system already plays an important role in the distribution of AV media content and services. Release 14 contains substantial enhancements to deliver TV services of various kinds, from linear TV programmes for mass audiences to custom-tailored on-demand services for mobile consumption. However, it is expected that also in the domain of AV content and service production, 3GPP systems will become an important tool for a market sector with steadily growing global revenues. There are several areas in which 3GPP networks can help to produce AV content and services in an efficient and flexible manner.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.33.2 Requirements
|
The 5G system supports the communication services for video, imaging and audio for professional applications. The associated requirements are described in 3GPP TS 22.263 [28].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.34 Critical medical applications
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.34.1 Description
|
The 5G system is expected to meet the service requirements for critical medical applications where critical medical applications denote medical devices and applications involved in the delivery of care for patient’s survival. Additionally, as the medical industry undergoes a shift to value-based healthcare, where companies and healthcare providers have to move to business models based on providing clinical value with cost efficiency, the 5G system can help to adopt new and more efficient care delivery models in order to reduce administrative and supply costs.
On this matter, 5G technology can especially have an important impact by:
- enabling superior monitoring capability means thus improving the effectiveness of preventive care,
- enabling shifting care location from hospitals to homes and other lower cost facilities,
- improving operating room planning, enabling streamlining equipment usage and simplifying operating theater implementation,
- Enhancing cooperation in critical situations between ambulance and hospital staff.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.34.2 Requirements
|
The 5G system shall support the communication services for critical medical applications. The associated requirements are described:
- in 3GPP TS 22.104 [21] for the requirements related to controlling both local or remote robotic diagnosis or surgery systems,
- in 3GPP TS 22.263 [28] for the requirements related to high quality medical imaging and augmented reality systems located in hybrid operating rooms, in remote healthcare facilities or ambulances,
- in 3GPP TS 22.261 clause 7.5 for the requirements on the support of tele-diagnosis or tele-monitoring systems,
- in 3GPP TS 22.261 clauses 6.10, 8.2 and 8.9 for the requirements on the security of medical data that fulfil regulatory requirements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.35 Service Function Chaining
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.35.1 Introduction
|
In order to support enhancement of service function chaining for 5G networks beyond the requirements for FMSS in TS 22.101, the network operator defines service function chaining policies for service function chaining to steer the traffic associated to the application and its users on per UE basis to appropriate ordered service functions.
A service function chain for 5G networks contains service functions such as firewall functions, NAT, antimalware, parental control, DDoS protection, TCP proxies, load balancers, KPI monitoring, and video optimization, etc.
NOTE: these are non-exhaustive examples of service functions. Other service functions can be provided by an operator.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.35.2 General Requirements
|
The following requirements apply for supporting enhancement of service function chaining for 5G networks:
- The network operator shall be able to define and modify service function chaining policies for steering traffic on per application per UE basis through required service function chaining with ordered service functions to improve the user’s QoE.
- Service functions chaining policies shall be able to distinguish between upstream and downstream traffic.
- The coexistence of traffic with and without service function chaining shall be supported.
- Service function chaining shall provide suitable means for authorized third parties to request a chain of service functions provided by the network operator based on operator’s service function chaining policies.
- In case of roaming, the HPLMN shall be able to apply traffic steering policies and service function chaining polices for home routed traffic.
- In case of roaming with local breakout, the HPLMN shall be able to provide the traffic steering policies and service function chaining policies to the VPLMN providing local breakout with support of service function chaining.
- Service function chaining shall support deployments where the Hosted Services are provided by the operator and deployments where the Hosted Services are provided by a third party.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.35.3 Service Function Management
|
- The service function management shall allow the operator to create, modify, and delete a service function based on operator’s service function chaining policies.
- The service function management shall allow the operator to create, configure, and control a chain of service functions per application and its users on per UE basis based on operator’s policy or request from third parties.
- The service function management shall be able to manage service function chaining for deployments where the Hosted Services are provided by the operator and for deployments where the Hosted Services are provided by a third party.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.36 5G Timing Resiliency
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.36.1 Overview
|
5G systems rely on reference precision timing signals for network synchronization in order to operate. These synchronization references are generated by Primary reference Time Clocks that typically get the timing reference from GNSS receivers and in order to meet the relevant synchronization requirements also during failure conditions, the synchronization network designs typically include means to address potential degradation of the GNSS signal performance. Some deployment of 5G involve applications that themselves can be sensitive to any degradation of the timing signal. In such cases it is beneficial for the 5G system to be enhanced to act as a backup for loss of their GNSS references. In some implementations, timing resiliency enhancements to the 5G system can work in collaboration with different types of time sources (e.g., atomic clock, time service delivered over the fibre) to provide a robust time synchronization.
5G as a consumer of time synchronization benefits from timing resiliency which enables the support of many critical services within the 5G network even during the event of a loss or degradation of the primary GNSS reference timing. Additionally, for time critical services (e.g. financial sector or smart grid), the 5G system can operate in collaboration with or as backup to other timing solutions. A base of clock synchronization requirements when 5G is providing a time signal, if it is deployed in conjunction with an IEEE TSN network or if it is providing support for IEEE 1588 related protocols, is included in [21] clause 5.6.
The enhancements in this clause build on this to add timing resiliency to the 5G system enabling its use as a replacement or backup for other timing sources.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.36.2 General
|
NOTE: Charging requirements for "5G Timing Resiliency" can be found in clause 9.3 of this document.
The 5G system shall support enhanced timing resiliency in collaboration with different types of time sources (e.g., GNSS, TBS/MBS [33] [34], Sync over Fiber [34]) to provide a robust time synchronization.
The 5G system shall be able to maintain accurate time synchronization as appropriate for the supported applications in the event of degradation or loss of the primary timing reference (e.g., GNSS).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.36.3 Monitoring and Reporting
|
The 5G system shall be able to support mechanisms to monitor for timing source failure (e.g., GNSS).
The 5G system shall be able to detect when reference timing signals (e.g., from GNSS or other timing source) are no longer viable for network time synchronization.
The 5G system shall support a mechanism to determine if there is degradation of the 5G time synchronization.
The 5G system shall be able to support mechanisms to indicate to devices (e.g., UEs, applications) that there is an alternate time source available for use (e.g., 5G system internal holdover capability, atomic clock, Sync over Fiber, TBS, GNSS), taking into account the holdover capability of the devices.
The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization.
The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate.
The 5G system shall support a mechanism to report timing errors such as divergence from UTC and time sync degradation to UEs and 3rd party applications.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.36.4 Service Exposure
|
The 5G system shall support a mechanism for a 3rd party application to request resilient timing with specific KPIs (e.g., accuracy, interval, coverage area).
6.37 Ranging based services
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.37.1 Description
|
Ranging-based services are the applications utilizing the distance between two UEs and/or the direction of one UE from the other one. In 3D case, direction includes horizontal direction and elevation direction. Ranging-based services can apply to a variety of verticals, such as consumer, smart home, smart city, smart transportation, smart retail, and industry 4.0. Some ranging-based services can only require the distance measurement, some can only require direction measurement, others can require both distance and direction measurement.
Ranging can be supported with or without 5G coverage and figure 6.37.1-1 is an illustration of ranging between UEs that are in coverage, out of coverage, or with partial coverage. Both licensed and unlicensed spectrum can be used for ranging. If licensed spectrum is used, it shall be fully under operator control.
Figure 6.37.1-1: Illustration of ranging between UEs with or without 5G coverage
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.37.2 Requirements
|
The 5G system shall be able to support for a UE to discover other UEs supporting ranging.
The 5G system shall be able to authorize ranging for a UE or a group of UE when using licensed spectrum.
The 5G system shall be able to protect privacy of a UE and its user, ensuring that no identifiable information can be tracked by undesired entities during ranging.
The 5G system shall be able to enable or disable ranging.
The 5G system shall support mutual ranging, i.e. two UEs shall be able to initiate ranging to each other.
The 5G system shall be able to ensure that the use of Ranging, if in licensed spectrum, is only permitted in network coverage under the full control of the operator who provides the coverage.
NOTE 1: The above requirement does not apply for public safety networks with dedicated spectrum, where ranging might be allowed out of coverage or in partial coverage as well.
The 5G system shall support energy efficient UE ranging operation.
The 5G system shall be able to start ranging and stop ranging according to the application layer’s demand.
The 5G system shall be able to provide mechanisms for a MNO, or authorized 3rd party, to provision and manage ranging operation and configurations.
The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if the requesting UE is LOS with the assisting UE and the assisting UE is LOS with the third UE).
NOTE 2: It cannot be assumed that all ranging UEs support the same application for exchange of information.
The 5G system shall be able to support ranging enabled UEs to determine the ranging capabilities (e.g. capabilities to perform distance and/or angle measurement) of other ranging enabled UEs.
The 5G system shall be able to allow a ranging enabled UE to determine if another ranging enabled UE is stationary or mobile, before and/or during ranging.
NOTE 3: This may require assistance from other ranging enabled UEs.
The 5G system shall allow ranging between 2 UEs triggered by and exposed to a third UE.
The 5G system shall allow ranging service between 2 UEs triggered by and exposed to the application server.
The 5G system shall be able to support one UE initiating ranging to the other UE.
The 5G system shall be able to support ranging between UEs which subscribe to different operators.
The 5G system shall be able to allow roaming UEs to perform ranging.
The 5G system shall be able to ensure the integrity and confidentiality of ranging information used by ranging-enabled UEs.
The 5G system shall be able to ensure that user privacy is not violated during ranging, e.g., subject to regional or national regulatory requirements.
The 5G system shall be able to ensure security protection (e.g., interworking security) when the ranging concerns UEs subscribed with different operators.
The level of security provided by the existing 5G system shall not be adversely affected when ranging is enabled.
The 5G system shall support means to securely identify other ranging capable UEs, with which a certain UE can perform ranging.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38 Personal IoT Networks and Customer Premises Networks
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.1 Description
|
Personal IoT Networks (PINs) and Customer Premises Networks (CPNs) provide local connectivity between UEs and/or non-3GPP devices. The CPN via an eRG or a legacy residential gateway, or PIN Elements via a PIN Element with Gateway Capability can provide access to 5G network services for the UEs and/or non-3GPP devices on the CPN or PIN. CPNs and PINs have in common that in general they are owned, installed and/or (at least partially) configured by a customer of a public network operator.
A Customer Premises Network (CPN) is a network located within a premises (e.g. a residence, office or shop). Via an evolved Residential Gateway (eRG) or a legacy residential gateway, the CPN provides connectivity to the 5G network. The eRG can be connected to the 5G core network via wireline, wireless, or hybrid access: in case of wireless or hybrid access an eRG with USIM is required; in case of wireline access an eRG can be depoyed without a USIM. A Premises Radio Access Station (PRAS) is a base station that can also be installed in a CPN. Through the PRAS, UEs can get access to the CPN and/or 5G network services. The PRAS can be configured to use licensed, unlicensed, or both frequency bands. Connectivity between the eRG and the UE, non-3GPP Device, or PRAS can use any suitable non-3GPP technology (e.g. Ethernet, optical, WLAN).
A Personal IoT Network (PIN) consists of PIN Elements that communicate using PIN Direct Connection or direct network connection and is managed locally (using a PIN Element with Management Capability). Examples of PINs include networks of wearables and smart home / smart office equipment. Via a PIN Element with Gateway Capability, PIN Elements have access to the 5G network services and can communicate with PIN Elements that are not within range to use PIN Direct Connection. A PIN includes at least one PIN Element with Gateway Capability and at least one PIN Element with Management Capability.
A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN.
The requirements as described in 3GPP TS 22.101 [6] clause 26a can also apply to Personal IoT Networks and Customer Premises Networks.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.1 General
|
The 5G system shall support mechanisms to identify a PIN, a PIN Element, an eRG and a PRAS.
Subject to local regulations, the 5G system shall support regulatory requirements for emergency calls, PWS and eCall for UEs connected via a CPN.
NOTE: The above requirement applies to UEs connected via 3GPP access.
The 5G system shall support applications on an Application Server connected to a CPN or PIN.
The 5G system shall be able to support PINs with PIN Elements subscribed to more than one network operator (e.g., a PIN Element that is a MUSIM UE and subscribes to different operators respectively, one PIN Element subscribed to network operator A and another PIN Element subscribed to network operator B).
Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path within the CPN for intra-CPN communications.
NOTE 1: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply.
Subject to regulatory requirements and operator policy, the 5G system shall support a data path not traversing the 5G network for intra-PIN communications via direct connections.
The 5G system shall enable the network operator to provide any 5G services to any UE via a PRAS connected via an eRG.
NOTE 2: Whether the PRAS can be used by UEs from other PLMNs in the same country as the PLMN associated with the PRAS is subject to regulatory policy on national roaming.
The 5G system shall minimize service disruption for a UE that is moving between CPN access and operator provided mobile access.
NOTE 3: CPN access can imply access via a PRAS or can imply access directly via an eRG. Operator provided mobile access implies access via an operator owned base station.
The 5G system shall minimize service disruption when a CPN communication path changes between two PRASes.
The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element (e.g. PIN Element with Gateway Capability) to another PIN Element or operator provided mobile access. The communication path between PIN Elements may include licensed and unlicensed spectrum as well as 3GPP and non-3GPP access.
The 5G system shall be able to support PRAS sharing between multiple PLMNs.
The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.