hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.2 Gateways
|
Subject to operator policy, the 5G network shall support an authorised eRG without a USIM to access the 5G core network via wireline access only.
The 5G system shall be able to support access to the 5G network and its services via at least one gateway (i.e. PIN Element with Gateway Capability or eRG or legacy residential gateway) for authorised UEs and authorised non-3GPP devices in a PIN or a CPN.
NOTE 1: The legacy residential gateway does not provide direct access to 5GC.
The 5G system shall be able to support IP traffic offload to data network for a CPN.
NOTE 2: The priority of offload can be from default configuration, network or user.
Under operator control, an eRG, shall be able to efficiently deliver 5G multicast/broadcast services to authorized UEs and non-3GPP devices in the CPN.
NOTE 3: The multicast service(s) that each of the authorized UEs and/or non-3GPP devices is allowed to receive may be different.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.3 Operation without 5G core network connectivity
|
The 5G system shall allow PIN Elements to communicate when there is no connectivity between a PIN Element with Gateway Capability and a 5G network. For a Public Safety PIN licensed spectrum may be used for PIN direct communications otherwise unlicensed spectrum shall be used.
When a CPN has lost connectivity with the 5G network, the 5G system shall provide an operator-controlled mechanism to enable:
- in the default configuration, or under certain conditions configured by the operator, the PRAS radio interface shall be deactivated; and
- under certain other conditions configured by the operator, the CPN shall continue existing intra-CPN communication, as long as no interaction with the 5G network is needed (e.g. refreshing security keys).
NOTE 1: The requirement above relates to intra-CPN operations and is subject to operator policy and control, under certain situations.
NOTE 2: Setting up new intra-CPN or intra-PIN communication sessions without connection to the 5G network is only possible with non-3GPP provided credentials.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.4 Discovery
|
The 5G system shall enable a UE or non-3GPP device in a CPN or PIN to discover other UEs or non-3GPP devices within the same CPN or PIN subject to acess rights.
The 5G system shall efficiently support service discovery mechanisms where a UE or non-3GPP device in a CPN or PIN can discover, subject to access rights:
- availability and reachability of other entities (e.g. other UEs or non-3GPP devices) on the CPN or PIN;
- capabilities of other entities on the CPN (e.g. PRAS, eRG) or PIN (e.g. relay UE, connection types) and/or;- services provided by other entities on the CPN or PIN (e.g. the entity is a printer).
The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by other PIN elements of the same PIN.
The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by UEs that are not members of the PIN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.5 Relay Selection
|
In addition to the relay selection requirements in 6.9.2.4, relay selection within a PIN is enabled for both UEs and non-3GPP device and supports the additional selection criteria:
- The 5G system shall support a mechanism for a PIN Element to select a relay for PIN direct connection that enables access to the target PIN Element.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.6 Security
|
The 5G system shall provide user privacy; location privacy, identity protection and communication confidentiallity for non-3GPP devices and UEs that are using the PIN Element with Gateway Capability, eRG or PRAS.
NOTE 1: Privacy protection should not block differentiated routing and QoS for different destinations and services for the UE(s).
The 5G system shall support a mechanism to minimize the security risk of communications using an eRG.
The 5G system shall enable the network operator associated with an eRG to control the security policy of an eRG.
Subject to operator policy, the 5G network shall provide support to authenticate an eRG without a USIM to access the 5G core network via wireline access only.
The 5G system shall support a mechanism to minimize the security risk of communications via a PRAS.
The PRAS (and its associated backhaul connectivity) shall provide a level of security equivalent to regular 5G base stations.
The 5G system shall enable the network operator associated with the Premises Radio Access Station (PRAS) to control the security policy of the PRAS.
The 5G system shall support authentication of a UE with 3GPP credentials for communication with entities (UEs, non-3GPP devices) in a CPN.
NOTE 2: To support this functionality the CPN needs to be connected with the 5G core network.
The 5G system shall provide support for a network operator to authenticate a PRAS.
The 5G system shall provide support for a network operator to authorize a PRAS for its use in a CPN.
The 5G system shall support a PIN Element using non operator managed credentials (e.g. provided by a third party) for performing communications within the PIN when those communications use PIN direct connections.
The 5G system shall support a mechanism to mitigate repeated and unauthorized attempts to access PIN Elements (e.g. mitigate a malicious flood of messages).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.7 QoS
|
The 5G system shall support real time E2E QoS monitoring and control for any intra-CPN data traffic to or from a UE (i.e. via eRG or via PRAS and eRG).
The 5G system shall support real time E2E QoS monitoring and control for any data traffic between a UE within a CPN and the 5G network (i.e. via eRG or via PRAS and eRG).
6.38.2.8 Charging
The 5G system shall support charging data collection for data traffic to/from individual UEs in a CPN or PIN (i.e., UEs behind the PIN Element with Gateway Capability or eRG and/or PRAS).
The 5G system shall be able to generate charging data that can differentiate between backhaul for the PRAS and other data traffic over the same access.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.38.2.9 Creation and Management
|
The 5G system shall support a mechanism for the network operator to provision an eRG with:
- policies on which transport (e.g. wireless, cable, etc.) is best suited for different negotiated QoS levels,
- authentication credentials,
- identification,
- initial OA&M information, and
- associated subscription.
The 5G system shall enable the network operator to configure a PRAS with:
- radio settings pertaining to licensed spectrum,
- authentication credentials,
- identification,
- initial OA&M information, and
- associated subscription.
Subject to operator policy, the 5G system shall enable the Authorised Administrator to provision a PRAS with UE access considerations (allowing all UEs, or allowing specific UEs only)
The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of an eRG.
The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of a PRAS.
The 5G system shall support mechanisms for a network operator or authorized 3rd party (e.g., a PIN User) to create, remove and manage a PIN, including:
- Authorizing/deauthorizing PIN Elements;
- Authorizing/deauthorizing PIN Elements with Management Capability;
- Authorizing/deauthorizing PIN Elements with Gateway Capability;
- Establishing duration of the PIN;
- Configure PIN Elements to enable service discovery of other PIN Elements;
- Authorize/deauthorise if a PIN Element can use a PIN Element with Gateway Capability to communicate with the 5GS;
- Authorize/deauthorise for a PIN Element(s):
- which other PIN Element it can communicate with,
- which applications/service or service in that PIN it can access,
- which PIN Element it can use as a relay.
- Authorize/deauthorise a UE to perform service discovery of PIN Elements over the 5G network;
- Configure a PIN Element for external connectivity e.g.via 5G system;
NOTE1: The authorization can include the consideration of the location and time validity of the PIN and its PIN elements.
The 5G system shall support a mechanism to enable a UE that is not a PIN Element of the PIN or a non-3GPP device that is not a PIN element of the PIN to request to join the PIN.
The 5G system shall support mechanisms for a network operator to configure the following policies in a PIN:
- Configure the connectivity type (e.g. licensed, unlicensed PIN direct connection) a PIN Element can use.
5G system shall be able to support mechanism to provide life span information of the PIN to the authorized 3rd party or the PIN elements when the PIN is created for limited time span.
The 5G system shall provide means to control which UEs can connect to a PRAS.
The 5G system shall support mechanisms to provision a PIN Element to use either licensed (under control of a MNO) or unlicensed spectrum (may be under the control of the MNO, or not) (e.g., when it has no connectivity to the 5G system).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.39 5G IMS Multimedia Telephony Service
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.39.1 Description
|
The 5G system is expected to support advanced capabilities and performance of enhanced IMS multimedia telephony service to meet new demands from consumers, business customers and vertical markets. Nowadays 3GPP has introduced new network capabilities and new types of devices (e.g. AR/VR/XR devices, robot, etc.), which can bring promising improvements to IMS multimedia telephony service. While more and more individual consumers enjoy multimedia telephony services across the globe, multimedia telephony services become popular also among business customers. There are several primary business functions that organizations use multimedia telephony services for, including internal communication, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. While business customers consider the multimedia telephony services offer attractive features to their business, they also experience some practical issues that expect support from the 5G system.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.39.2 General
|
The following set of requirements complement the requirements listed in 3GPP TS 22.173 [37].
The IMS multimedia telephony service shall support AR media processing.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.39.3 Service Exposure
|
Requirements in this clause are subject to regulatory requirements and operator policy.
The 5G system shall provide means to allow a trusted third-party to update the multimedia telephony service subscription and allocate a third-party specific identity to an authorized user.
NOTE: The third party is authorized to change user identities for those subscriptions authorized by the operator.
The following requirements apply to the originating side:
- The 5G network shall provide a means for third parties (e.g. enterprises) to be authorized to verify the use of calling identity information by its authorized users.
- The 5G network shall provide a means for authorized third parties to verify that an authenticated user is authorized to include or reference the pre-established calling identity information included in the call setup or retrieved by the called party.
- The 5G network shall provide a means to verify the authenticity of the pre-established stored identity information that is referenced by the call setup and retrieved by the called party.
The following requirements apply to the terminating side.
- The 5G network shall provide a means for third parties (e.g. enterprises) to be able to verify the caller’s authorization to use the identity information either in addition to or instead of verification performed by the terminating PLMN.
- The 5G network shall provide a means to verify the authenticity of any stored identity information referenced by the call setup to be presented to the called party.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.40 AI/ML model transfer in 5GS
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.40.1 Description
|
Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors. In mobile communications systems, mobile devices (e.g. smartphones, automotive, robots) are increasingly replacing conventional algorithms (e.g. speech recognition, image recognition, video processing) with AI/ML models to enable applications. The 5G system can at least support three types of AI/ML operations:
- AI/ML operation splitting between AI/ML endpoints
The AI/ML operation/model is split into multiple parts according to the current task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network endpoints, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the operation/model up to a specific part/layer and then sends the intermediate data to the network endpoint. The network endpoint executes the remaining parts/layers and feeds the inference results back to the device.
- AI/ML model/data distribution and sharing over 5G system
Multi-functional mobile terminals might need to switch the AI/ML model in response to task and environment variations. The condition of adaptive model selection is that the models to be selected are available for the mobile device. However, given the fact that the AI/ML models are becoming increasingly diverse, and with the limited storage resource in a UE, it can be determined to not pre-load all candidate AI/ML models on-board. Online model distribution (i.e. new model downloading) is needed, in which an AI/ML model can be distributed from a NW endpoint to the devices when they need it to adapt to the changed AI/ML tasks and environments. For this purpose, the model performance at the UE needs to be monitored constantly.
- Distributed/Federated Learning over 5G system
The cloud server trains a global model by aggregating local models partially-trained by each end devices. Within each training iteration, a UE performs the training based on the model downloaded from the AI server using the local training data. Then the UE reports the interim training results to the cloud server via 5G UL channels. The server aggregates the interim training results from the UEs and updates the global model. The updated global model is then distributed back to the UEs and the UEs can perform the training for the next iteration.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.40.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.40.2.1 Requirements for direct network connection
|
Based on operator policy, the 5G system shall be able to provide means to allow an authorized third-party to monitor the resource utilisation of the network service that is associated with the third-party.
NOTE 1: Resource utilization in the preceding requirement refers to measurements relevant to the UE’s performance such as the data throughput provided to the UE.
Based on operator policy, the 5G system shall be able to provide an indication about a planned change of bitrate, latency, or reliability for a QoS flow to an authorized 3rd party so that the 3rd party AI/ML application is able to adjust the application layer behaviour if time allows. The indication shall provide the anticipated time and location of the change, as well as the target QoS parameters.
Based on operator policy, 5G system shall be able to provide means to predict and expose predicted network condition changes (i.e. bitrate, latency, reliability) per UE, to an authorized third party.
Subject to user consent, operator policy and regulatory constraints, the 5G system shall be able to support a mechanism to expose monitoring and status information of an AI-ML session to a 3rd party AI/ML application.
NOTE 2: Such mechanism is needed for AI/ML application to determine an in-time transfer of AI/ML model.
5G system shall be able to provide event alerting to an authorized 3rd party, together with a predicted time of the event (e.g., alerting about traffic congestion or UE moving into/out of a different geographical area).
NOTE 3: A 3rd party AI/ML application may use the prediction information to minimize disturbance in the transfer of learning data and AI/ML model data.
The 5G system shall be able to expose aggregated QoS parameter values for a group of UEs to an authorized service provider.
The 5G system shall be able to support an authorised 3rd party to change aggregated QoS parameter values associated with a group of UEs, e.g. UEs of a FL group.
Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to expose information (e.g. candidate UEs) to an authorized 3rd party to assist the 3rd party to determine member(s) of a group of UEs (e.g. UEs of a FL group).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.40.2.2 Requirements for direct device connection
|
NOTE 1: Charging requirements for "AI/ML model transfer in 5GS" can be found in clause 9.9 of this document.
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall support a means to authorize specific UEs to transmit data (e.g. AI-ML model data for a specific application,) via direct device connection in a certain location and time.
Based on user consent, operator policy, and trusted 3rd party’s request, the 5G system shall be able to provide means for an operator to authorize specific UEs who participate in the same service (e.g. for the same AI-ML FL task) to exchange data with each other via direct device connection, e.g. when direct network connection cannot fulfil the required QoS.
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to dynamically add or remove specific UEs to/from the same service (e.g. a AI-ML federated learning task) when communicating via direct device connection.
Based on user consent and operator policy, the 5G system shall be able to provide means for the network to configure and modify remote UEs’ communication QoS, when a relay UE is involved, e.g., to satisfy end to end latency for proximity-based work task offloading.
NOTE 2: for proximity-based work task offloading, the data packet size transmitted over the sidelink and Uu parts of the UE indirect network connection can be different.
Subject to user consent and operator policy, the 5G system shall be able to support configuration of the QoS (e.g., latency, reliability, data rate) of a communication path using direct device connection, e.g., for AI-ML data transfer.
Based on user consent, operator policy and trusted 3rd party request, the 5G system shall be able to support means to monitor the QoS characteristics (e.g. data rate, latency) of traffic transmitted via direct device connection or relayed by a UE, and 5G network expose the monitored information to the 3rd party.
NOTE 3: The monitoring information doesn’t include user position-related data.
Subject to user consent, operator policy and trusted 3rd party request, the 5G system shall be able to provide means the network to predict and expose QoS information changes for UEs’ traffic using direct or indirect network connection (e.g., bitrate, latency, reliability).The 5G system shall be able to support a mechanism for a trusted third-party to negotiate with the 5G system for a suitable QoS for direct device connections of multiple UEs exchanging data with each other (e.g. a group of UEs using the same AI-ML service).
Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support and provision an aggregated QoS for multiple remote UEs served by a relay UE.
Based on user consent, operator policy and trusted 3rd party’s request, the 5G system shall be able to support configuring specific QoS limitations applied to multiple UEs communicating via direct device connection (e.g. part of a joint AI-ML inference task).
NOTE 4: the above requirement assumes unicast type of communication.
Subject to user consent, regulation, trusted 3rd party’s request and operator policy, the 5G network shall be able to expose information to assist the 3rd party to determine candidate UEs for data transmission via direct device connection (e.g. for AIML model transfer for a specific application).
NOTE 5: the information does not include user’s specific positioning and can include QoS information
Subject to user consent, operator policy, regulation and trusted 3rd party’s request, the 5G network shall be able to expose information of certain UEs using the same service to the 3rd party (e.g. to assist a joint AIML task of UEs in a specific area using direct device communication)
NOTE 6: the information does not include user’s exact positioning information.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41 Providing Access to Local Services
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.1 Description
|
Providing access to local services refers to the capability to provide access to a hosting network and a set of services offered by the hosting network provider, and 3rd party service providers including other network operators and 3rd party application providers. The services can be localized (i.e. provided at specific/limited area) and can be bounded in time. The user can become aware of the available access to local services, and the process to gain and terminate access to the hosting network and local services. This process should be efficient, and convenient from a user experience standpoint.
Providing access to local services creates new opportunities for users and service providers. For example, access can be provided in areas where there is no coverage provided by other networks (for example, on a fairground established far from other infrastructure), or the access and local services can be established as needed (on a short-term basis), without the need for long term business relationships, permanently installed equipment, etc.
The type of local services and access for localized services via a hosting network can be promoted and arranged through different channels. Principally the service providers (e.g., brick and mortar businesses, entertainment venues, construction contractors, first responder agencies, etc.) will provide information and proper incentive or instructions to potential users so that they will seek to access the local services via hosting networks.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.1 General
|
In the requirements below, it is assumed that:
- Both the home network and the hosting network can be a PLMN or NPN.
- Only subscribers of a public network can roam into a PLMN. Examples of interworking scenarios between network operators and application providers for localized services are indicated in Annex H.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.2 Configuration of Localized Services in Hosting Network
|
NOTE: The term "Service provider of localized services" includes also 3rd party service provider.
The 5G system shall support suitable mechanisms to allow automatically establishing localized service agreements for a specific occasion (time and location) and building temporary relationship among hosting network operator and other service providers including network operators or 3rd party application providers.
The 5G system shall support means for the service provider to request the hosting network via standard mechanisms to provide access to 3rd party services at a specific period of time and location. This period of time shall be flexible, so that a change in service provision can be decided at any time (e.g., to cancel or prolong local services in the locality of service delivery) based on localized services agreements.
Based on localized services agreements, the 5G system shall provide suitable means to allow the service provider to request and provision various localized service requirements, including QoS, expected/maximum number of users, event information for discovery, network slicing, required IP connectivity etc, and routing policies for the application of the localized services via the hosting network.
The 5G system shall support means for a hosting network to create policies and configure resources for the requested time and location for the 3rd party services based on the received request.
The 5G system shall support means for a hosting network to notify the service provider of the accepted service parameters and routing policies.
Subject to regulatory requirements and localized service agreements, the 5G system shall allow a home network operator to automatically negotiate policies with the hosting network for allowing the home network’s subscribers to connect at a specific occasion, e.g., time and location, for their home network services.
Subject to the automatic localized services agreements between the hosting network operator and home network operator, for UE with only home network subscription and with authorization to access hosting networks the 5G system shall support:
- access to the hosting network and use home network services or selected localized services via the hosting network,
- seamless service continuity for home network services or selected localized services when moving between two hosting networks or a host network and the home network.
The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of their spatial extent (in terms of a particular topology, for example a single cell), as specified by a service provider of localized services.
The 5G system shall support a mechanism to enable configuration of a network that provides access to localized services such that the services can be limited in terms of the resources or capacity available, to correspond to requirements that apply only to the locality of service delivery, as specified by a service provider of localized services.
The 5G system shall support means for a hosting network to provide a 3rd party service provider with information for automatic discovery of the hosting network by the UEs to allow access to specific 3rd party services.
The 5G system shall support secure mechanisms to allow a home network to coordinate with a hosting network for a subscriber to temporarily access the hosting network (e.g., based on temporary credentials) at a given time (start time and duration) and location.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.3 User Manual Selection of Localized Services via Hosting Network
|
The hosting network shall allow a UE to manually select temporary localized services which are provided via local breakout at the hosting network.
NOTE: Localized services which are provided via local breakout at the hosting network can be based on interworking scenarios for hosting network owned/collaborative services as indicated in Annex H.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.4 UE Configuration, Provisioning, Authentication and Authorization
|
Subject to localized services agreements, the 5G system shall enable a home network operator to authorize a UE for using its home network services via a hosting network for a certain period of time and/or location.
The 5G system shall allow a trusted 3rd party service provider to provide UEs with localized service policy (e.g., QoS, network slice in the hosting or home network, service restriction such as time and location) via the hosting network or the UE’s home network.
The 5G system shall enable a UE to use credentials provided by the hosting network with or without coordination with the home network of the UE, to make use of localized services via the hosting network with a certain time (including starting time and the duration) and location validity.
The 5G system shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network.
The 5G system shall provide support to enable secure means to authenticate and authorize a user of a UE accessing a hosting network, including cases in which a UE has no subscription to the hosting network and still needs to get authorized to use localized services via the hosting network.
NOTE: It can be assumed that a network provider deploying a hosting network has access to respective identification information about the user, e.g., through a separate registration process outside the scope of 3GPP.
The 5G system shall be able to authenticate and authorize the UE of a user authenticated to a hosting network to access the hosting network and its localized services on request of a service provider.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.5 UE Discovery, Selection and Access
|
Subject to operator’s policy and agreement between a 3rd party service provider and operator, the 5G system shall enable a UE to receive and use configuration provided by a 3rd party service provider to discover and access a hosting network and localized services, including the considerations of prior service agreement with a 3rd party service provider and no prior subscription to hosting network. If the UE is able to obtain services from two networks simultaneously, it may additionally select the hosting network. If the UE cannot maintain the connection to the home network while selecting the hosting network, the selection shall only be done on request by the user, i.e., using manual selection.
The 5G system shall support secure means for a UE to select and access localized services which may be provided by a 3rd party service provider via a hosting network, independent of prior subscription to the hosting network or 3rd party service provider.
The 5G system shall enable the home network to allow a UE to automatically select a hosting network for accessing localized services when specified conditions (e.g., predefined time, location) are fulfilled.
The 5G system shall be able to prevent a UE to re-access the hosting network after the localized services were terminated if the authorization for the localized services is no longer valid (e.g., can be based on certain conditions such as time or location of the user).
The 5G system may support means for a UE which may or may not have prior subscription to the hosting network to display human readable information on how to gain access to the hosting network and available 3rd party services.
The 5G system shall support a mechanism to allow a user to manually select a specific local hosting network.
NOTE: Additional information can be presented to the user to facilitate the manual network selection.
The 5G system shall be able to limit access of specific UEs to a configurable area of a hosting network's coverage area.
The 5G system shall be able to maintain privacy of a user against the hosting network while the UE does not make use of the hosting network, for example, to prevent tracking of UEs by hosting networks.
The 5G system shall enable the home network to instruct a UE to select a hosting network with certain conditions (e.g., predefined time, location) based on the request from a service provider.
The 5G system shall enable the home network to allow a UE to select a hosting network or change to another hosting network, without any additional user intervention as long as the delivered services, both localized services and home routed services, are unchanged.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.6 Hosting Network Localized Services and Home Operator Services
|
The 5G system shall enable the home network operator to indicate to the UE what services are preferred to be used from the home network when the UE connects to a hosting network and the requested services are available from both the hosting and the home network.
Based on localized service agreements, the hosting network shall be able to provide required connectivity and QoS for a UE simultaneously connected to the hosting network for localized services and its home network for home network services.
A UE shall be able to connect to its home network via the hosting network, if supported by the hosting network and the home network based on localized service agreements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.7 Returning to Home Network
|
The 5G system shall provide mechanisms to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time.
The 5G system shall provide mechanisms to minimize the impact on the UEs communication e.g., to prevent user plane and control plane outages when returning to a home network together with other high number of UEs in a very short period of time, after terminating their temporary local access to a hosting network.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.8 Charging
|
The 5G system shall be able to collect charging information for the use of localized services at the hosting network and provide the charging records to UEs’ home operators based on localized service agreements and charging policies provided by the service providers of localized services.
6.41.2.9 Regulatory Services
A hosting network using the 5G system shall be able to support regulatory services (e.g., PWS, LI, and emergency calls), based on regional/national regulatory requirements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.41.2.10 Multicast/Broadcast
|
The operator of a hosting network shall support a mechanism allowing different service providers of localized services to disseminate their services and content over broadcast/multicast transport. This mechanism should also provide means to include diverse content in the same transmission, e.g., to include advertisements with other content, or to include multiple content in the same media delivered to the user.
A hosting network shall provide multicast and broadcast services in an energy efficient manner to UEs receiving this service.
A hosting network shall support resource efficient content delivery through multicast/broadcast.
A hosting network shall support a mechanism to provide low latency signalling for efficient content delivery to many UEs.
Subject to home operator policy, a hosting network shall be able to prioritize specific multicast and broadcast services for local access over home routed access, even if the same service is available in both networks.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.42 Mobile base station relays
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.42.1 Description
|
The requirements below refer to a "mobile base station relay", which is a mobile base station acting as a relay between a UE and the 5G network, i.e. providing a NR access link to UEs and connected wirelessly (using NR) through a donor NG-RAN to the 5G Core. Such mobile base station relay is assumed to be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle).
NOTE: The radio link used between a mobile base station relay and served UEs, as well as between mobile base station relay and donor RAN, is assumed to be NR-Uu; in that regard, it should be clear that a mobile base station relay is different than a UE relay (which uses instead a PC5-based link to provide indirect connection to remote UEs).
Few main underlying assumptions are:
- requirements cover single-hop relay scenarios as baseline (multi-hop is not precluded);
- legacy UEs are supported;
- other stage-1 requirements (e.g. on wireless self-backhaul), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. relays on board of moving vehicles), thus cannot cover the requirements below, which are intended to be specific to mobile base station relays;
- the identified requirements do not intend to imply or exclude specific network/relay architectures and topology solutions (e.g. could be IAB based, or others);
- the MNO managing mobile base station relays, and the RAN/5GC they connect to, can be a PLMN or an NPN operator.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.42.2 Requirements
|
The 5G system shall support efficient operation of mobile base station relays.
The 5G system shall be able to support means, for a mobile network operator, to configure, provision and control the operation of a mobile base station relay, e.g. activation/deactivation, permitted location(s) or time of operation.
The 5G system shall be able to support provisioning and configuration mechanisms to control UEs’ selection and access to a mobile base station relay, e.g. based on UE’s authorization, geographic or temporary restrictions, relay’s load.
The 5G system shall be able to support RAN sharing between multiple PLMNs for UEs connected to the 5G network via mobile base station relays.
NOTE 1: the above requirement assumes both relay and (donor) RAN resources, including UE access link and relay backhaul link, are shared among operators.
The 5G system shall be able to configure and provision specific required QoS for traffic relayed via a mobile base station relay.
NOTE 2: QoS is end-to-end, i.e. from UE to 5GC.
Subject to regulatory requirements and operator policy, the 5G network shall support a mechanism to determine suitable QoS parameters for traffic relayed via a mobile base station when the connection quality of the serving mobile base station relay changes e.g. during mobility between terrestrial access network and satellite access network.
Subject to regulatory requirements and based on operator policy, the 5G system shall support means to configure and expose monitoring information of a mobile base station relay to an MNO’s authorized third-party.
The 5G system shall be able to provide means to optimize network behaviour to efficiently deliver data based on the mobility information (e.g., itinerary), known or predicted, of mobile base station relays.
The 5G system shall be able to support communication from/to users of one MNO (MNO-A) via mobile base station relays, where the traffic between the relay and the MNO-A network is transported using 5G connectivity (RAN and 5GC) provided by a different MNO (MNO-B).
NOTE 3: The 5G connectivity provided to the MNO-A relays by the different MNO (MNO-B) assumes a generic wireless backhaul transport, independent from the mobile base station relay functionalities.
The 5G system shall be able to support UEs connectivity to RAN using simultaneously, a link without mobile base station relay and a link via a mobile base station relay, or simultaneous links via different mobile base station relays.
NOTE 4: The above requirements cover scenarios were the two links (to the RAN) could be connected to the same or different RAN node(s), and assuming both relay(s) and RAN belong to the same PLMN.
The 5G system shall be able to provide means to support efficient UE cell selection and cell reselection (between mobile base station relays or between relays and RAN) in the presence of mobile base station relays.
The 5G system shall be able to ensure end-to-end service continuity, in the presence of mobile base station relays.
NOTE 5: The above requirement intends to cover different scenarios of UE mobility (e.g. UE moving between two mobile base station relays, or between macro RAN and relay) and relay mobility (e.g. base station relay moving between different donor RAN nodes).
The 5G system shall be able to support mechanisms to optimize mobility and energy efficiency for UEs located in a vehicle equipped with a base station relay.
NOTE 6: The above requirements cover scenarios where mobile base station relays provide 5G access for both UEs in the vehicle and around the vehicle.
The 5G system shall be able to support incremental deployment of connectivity by means of one or a series of mobile base station relays for use only in specific locations where UEs would receive no other 3GPP access (terrestrial or non-terrestrial) coverage, e.g., for public safety scenarios.
The 5G system shall be able to support mobile base station relays using 3GPP satellite NG-RAN (NR satellite access).
The 5G system shall be able to support mobile base station relays accessing to 5GC via NR satellite access and NR terrestrial access simultaneously.
The 5G system shall be able to support service continuity for mobile base station relays using at least one 3GPP satellite NG-RAN.
NOTE 7: This requirement applies to scenarios where there is a transition between two 3GPP NG-RAN, operated by the same MNO, involving at least one 3GPP satellite NG-RAN.
The 5G system shall be able to identify and differentiate UEs’ traffic carried via a mobile base station relay and collect charging information, including specific relay information (e.g. geographic location served by the relay).
The 5G system shall support means for a mobile base station relay to have a certain subscription with a HPLMN, used to get access and connectivity to the HPLMN network (via a donor RAN).
The 5G system shall support the ability of a base station relay to roam from its HPLMN into a VPLMN.
The 5G system shall support mechanisms, for the HPLMN controlling a mobile base station relay, to enable/disable mobile relay operation if the relay is roaming in a VPLMN.
The 5G system shall support mechanisms to disable mobile relay operation by a VPLMN where a mobile base station relay is roaming to.
The 5G system shall be able to fulfil necessary regulatory requirements (e.g. for support of emergency services) when UEs access the 3GPP network via a mobile base station relay.
The 5G system shall be able to support priority services (e.g. MPS) when UEs access the 3GPP network via a mobile base station relay.
The 5G system shall be able to support location services for the UEs accessing 5GS via a mobile base station relay.
The 5G system shall ensure that existing end-to-end 5G security between the UE and 3GPP network is unaffected when the UE accesses the 3GPP network via a mobile base station relay.
The 5G system shall be able to minimize radio interference possibly caused by mobile base station relays.
The 5G system shall minimize the impact of the presence of mobile base station relays on radio network management (e.g. through automatic neighbour cell list configuration).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.43 Tactile and multi-modal communication service
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.43.1 Description
|
The tactile and multi-modal communication service can be applied in multiple fields, e.g. industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education, culture and smart grid [38]. These services support applications enabling input from more than one sources and/or output to more than one destinations to convey information more effectively. As figure 6.43.1-1 illustrates, the input and output can be different modalities including:
• Video/Audio media;
• Information received by sensors about the environment, e.g. brightness, temperature, humidity, etc.;
• Haptic data: can be feelings when touching a surface (e.g., pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness).
Figure 6.43.1-1. Multi-modal interactive system
For immersive multi-modal VR applications, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization), particularly when the synchronization threshold between two or more modalities is less than the latency KPI for the application. Example synchronization thresholds [41] [42] [43] [44] are summarised in table 6.43.1-1.
Table 6.43.1-1: Typical synchronization thresholds for immersive multi-modality VR applications
Media components
synchronization threshold (note 1)
audio-tactile
audio delay:
50 ms
tactile delay:
25 ms
visual-tactile
visual delay:
15 ms
tactile delay:
50 ms
NOTE 1: for each media component, "delay" refers to the case where that media component is delayed compared to the other.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.43.2 Requirements
|
The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.
NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs’ flows (e.g., haptic, audio and video) of a multi-modal communication session.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44 Roaming value-added services
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.1 Description
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.1.1 Overview
|
Roaming value-added services (RVAS) form part of the roaming services ecosystem and have traditionally been provided by either the PLMN or outsourced to a fully trusted entity. The RVAS provider acting on behalf of the PLMN could be any trusted 3rd party. The RVAS described here are all RVAS enabled by the PLMN for 5GS roaming.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.1.2 Welcome SMS
|
The "Welcome SMS" service sends a SMS to a roaming subscriber’s UE when the UE is registered in a new network for the first time. The SMS typically follows a predefined template and is sent on behalf of the home operator and may contain relevant information related to the visited country, e.g., the cost to call home, how to reach the operator’s customer service, local emergency services number, etc.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.1.3 Steering of Roaming (SoR) during the registration
|
The "Steering of Roaming (SoR) during the registration procedure" service makes the home operator able to steer a user to a certain network during the registration procedure when the user tries to register to a new (non-preferred) network.
NOTE: This functionality is different from Steering of Roaming described in clause 6.30, which aims to influence which network a UE would try to register on.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.1.4 Subscription-based routing to a particular core network (e.g. in a different country)
|
The "Subscription-based routing to a particular core network" service forwards the traffic from the HPLMN to a target PLMN. Some operators use more than one PLMN ID, e.g., multi-national operators. Due to certain business and operational demands, it might be necessary to route traffic of a certain customer segment, typically from a certain IMSI range of USIMs, of a PLMN to another PLMN and to further handle the subscriber there. This means the UE is not handled by the "real" HPLMN (according to MNC and MCC) but by some alternative PLMN.
This subscription-based routing enables the case where several national subsidiaries of a multi-national operator offer various services for different customer segments but for operational efficiency the actual service for a certain group is provided by only one dedicated network.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.2.1 Welcome SMS
|
The 5G system shall be able to support mechanisms for the HPLMN to provide a notification, including equipment and subscription identifiers, to a trusted application server when a UE successfully registers in a VPLMN. In response to the notification, the trusted application server can indicate specific actions to the HPLMN (e.g., send an SMS to the UE).
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.2.2 Steering of Roaming (SoR) during the registration procedure
|
The 5G system shall be able to support mechanisms enabling the HPLMN to:
- provide a notification, including subscription and equipment identifiers, to a trusted application server when a UE tries to register in a VPLMN.
- receive a notification reply from the trusted application server indicating specific actions to the HPLMN, e.g., reject UE registration (with a specific cause), trigger a SoR command.
NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.44.2.3 Subscription-based routing to a particular core network (e.g. in a different country)
|
The 5G system shall be able to support a mechanism such that all traffic pertaining to UEs of specific subscribers which is sent to the HPLMN is forwarded to a target PLMN, e.g., to enable further handling of those UEs by the target PLMN. The forwarding mechanism shall minimize traffic in the HPLMN, e.g., by using efficient means to forward traffic from selected UEs.
NOTE 1: The above requirement assumes that the HPLMN has an agreement with the target PLMN, and routing policies are in place.
NOTE 2: In case of UEs connected via a VPLMN, it is assumed that traffic is forwarded to the target PLMN by the HPLMN.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.45 Support of Roaming services providers
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.45.1 Overview
|
In the roaming ecosystem, a roaming services provider provides the technical and commercial means to facilitate the deployment and operation of roaming services between a client operator and a set of selected connected operators.
The roaming services provider handles the technical implementation of the roaming relations in a scalable and operationally efficient way.
With a roaming services provider present in the roaming ecosystem, operators can choose not to establish a bilateral direct agreement with specific operators. A trusted relation exists between the involved operator and the roaming services provider.
Roaming services providers, according to their role and responsibilities, assume financial and technical liability to apply all necessary controls and access to all communications.
Among other functionalities, a roaming services provider needs to:
• Process identifiers and potentially other information transmitted in signalling messages between PLMNs in a secure manner.
• Be able to modify, add or delete information that is relevant to their role, respecting what is contractually agreed in service level agreements (SLAs) and enforced technically.
• Isolate the individual operator signalling flows from each other
• Report on the detection of and mitigation of security breaches.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.45.2 Requirements
|
The 5G system shall allow roaming services to be provided by a roaming services provider in charge of managing roaming agreements, by mediating between two or more PLMNs, while maintaining the privacy and 5G security of any information transmitted between the home and the serving PLMN.
NOTE 1: A PLMN can support both bi-lateral direct relationships with other PLMNs and make use of roaming service provider services toward different roaming partners.
The 5G system shall allow a roaming services provider to be a trusted entity for either a home PLMN, a visited PLMN or both.
NOTE 2: The expected maximum number of roaming service providers is two, one for the home PLMN and another for the visited PLMN.
The 5G system shall allow a roaming services provider to accept or reject registration attempts, on behalf of the involved PLMNs, based on the roaming agreements.
NOTE 3: Rejecting user registrations using an appropriate release cause permits the UE to be able to reselect another roaming partner or technology.
The 5G system shall allow a roaming services provider to identify the origin and destination PLMN, and to verify the authenticity, of every transmitted message.
The 5G system shall allow the Roaming services provider to be able to originate and modify messages as per contractually agreed SLAs.
The 5G system shall allow the involved PLMNs to be able to identify the origin of any message generated by the roaming services providers as well as to identify any modification made to the exchanged messages by the roaming services providers.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46 Satellite access
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.1 Overview
|
The following requirements apply for a 5G system with satellite access.
NOTE: For the KPIs for a 5G system with satellite access, see clause 7.4.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.2 General
|
NOTE 1: Charging requirements for "Satellite Access" can be found in clause 9.3 of this document.
A 5G system with satellite access shall support different configurations where the radio access network is either a satellite NG-RAN or a non-3GPP satellite access network, or both.
Subject to operator’s policies, a 5G System with satellite access shall be able to support Resilient Notification Service to notify users, with valid subscription to the notification service, about a missed mobile terminated service when the user is unreachable via satellite access.
NOTE 2: The Resilient Notification Service can provide the user with service information e.g. caller’s information and service type.
A UE supporting satellite access shall be able to provide or assist in providing its location to the 5G network.
A 5G system with satellite access shall be able to determine a UE's location in order to provide service (e.g. route traffic, support emergency calls) in accordance with the governing national or regional regulatory requirements applicable to that UE.
NOTE 3: This is also applicable for UE using only satellite access. The determination of a UE’s location can be based on 3GPP and/or non-3GPP positioning technologies subject to operator’s policies.
A 5G system with satellite access shall be able to support low power MIoT type of communications.
Subject to the regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to provide services to an authorized UE independently of the UE’s GNSS capability.
Subject to regulatory requirements and operator’s policies, a 5G system with satellite access shall be able to support collection of information on usage statistics and location of the UEs that are connected to the satellite.
Subject to regulatory requirements and operator’s policy, a 5G System supporting satellite access and Broadcast Services shall be able to deliver Media Broadcast to a UE which is not registered.
NOTE 4: Subject to an agreement (SLA) between the MNO and the SNO the above requirement can be applied
NOTE 5: The UEs are adapted for receiving broadcast services only and are not expected to initiate transmission
Subject to the regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support a mechanism to deliver specific data traffic of a UE related to specific service(s) to a preferred geographical location.
NOTE 6: There are satellite ground stations deployed within the preferred geographical location. The link between satellite and satellite ground station location is out of 3GPP scope
Subject to operator’s policy, the 5G network with satellite access shall be able to maintain the connection to an available core network with the same service level agreement (SLA) for resilient satellite communication.
NOTE 7: The resilient communication can be achieved through a single satellite or multiple satellites in different orbit types with different characteristics
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.3 Service continuity
|
For a 5G system with satellite access, the following requirements apply:
• A 5G system with satellite access shall support service continuity between 5G terrestrial access network and 5G satellite access networks owned by the same operator or owned by different operators having an agreement.
• Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support service continuity (with minimum service interruption) for a UE engaged in an active communication, when the UE changes from a direct network connection via 5G terrestrial access to an indirect network connection via a relay UE (using satellite access) and vice-versa.
NOTE: It is assumed that the 5G terrestrial access network and the satellite access network belong to the same operator.
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support service continuity (with minimum service interruption) of a UE-Satellite-UE communication when the UE communication path moves between serving satellites (due to the movement of the UE and/or the satellites).
- Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support service continuity (with minimum service interruption) of a UE-Satellite-UE communication when the communication path between UEs extends to additional satellites (through ISLs).
- Subject to regulatory requirements and operator’s policies, a 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall support minimum service interruption when the UE communication path (e.g., Relay or CPE) changes between terrestrial access and satellite access networks or between satellites networks potentially supporting different orbit types with different characteristics.
Subject to regulatory requirements and operator’s policies, a 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall support minimum service interruption when the UE communication path (e.g., Relay or CPE) changes between terrestrial access and satellite access networks or between satellites networks potentially supporting different orbit types with different characteristics.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.4 Roaming aspects
|
For a 5G system with satellite access, the following requirements apply:
- A 5G system with satellite access shall enable roaming of UE supporting both satellite access and terrestrial access between 5G satellite networks and 5G terrestrial networks.
- UEs supporting satellite access shall support optimized network selection and reselection to PLMNs with satellite access, based on home operator policy.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.5 Resource efficiency
|
For a 5G system with satellite access, the following requirements apply:
- A 5G system with satellite access shall support the use of satellite links between the radio access network and core network, by enhancing the 3GPP system to handle the latencies introduced by satellite backhaul.
- A 5G system with satellite access shall be able to support meshed connectivity between satellites interconnected with ISLs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.6 Efficient user plane
|
For a 5G system with satellite access, the following requirements apply:
• A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS.
• A 5G system with satellite access shall be capable of supporting simultaneous use of 5G satellite access network and 5G terrestrial access networks.
- A 5G system with satellite access shall be able to support both UEs supporting only satellite access and UEs supporting simultaneous connectivity to 5G satellite access network and 5G terrestrial access network.
- Subject to regulatory requirements and operator’s policies, a 5G system with satellite access shall be able to support an efficient communication path and resource utilization for a UE using only satellites access, e.g. to minimize the latencies introduced by satellite links involved.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.7 Satellite and Relay UEs
|
For a 5G system with satellite access, the following requirements apply:
- A 5G system with satellite access shall be able to support relay UEs with satellite access.
NOTE: The connection between a relay UE and a remote UE is the same regardless of whether the relay UE is using satellite access or not.
- A 5G system with satellite access shall support mobility management of relay UEs and the remote UEs connected to the relay UE between a 5G satellite access network and a 5G terrestrial network, and between 5G satellite access networks.
- A 5G system with satellite access shall support joint roaming between different 5G networks of a relay UE and the remote UEs connected to that relay UE.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.8 Store and Forward Satellite Operation
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.8.1 Description
|
NGSO (MEO/LEO) based satellite access is raising higher demands on the amount of ground stations, and the availability and stability of the connectivity to ground station for UEs to obtain end-to-end network services anytime.
S&F (Store and Forward) Satellite operation in some level provides a way to enable autonomously network service to UEs without the satellite always being connected to the ground station, which can extend the service availability for the areas without the connectivity to ground station via feeder link or ISL (e.g. at sea, very remote areas lack of ground-station infrastructures), improve the ground segment affordability with fewer ground stations and allow more robust UE services with the satellite under intermittently/temporarily unavailable feeder link.
This is particularly relevant for delay-tolerant communications via NGSO space segment.
The requirements below refer to S&F (Store and Forward) Satellite operation.
NOTE: For more information on Store and Forward Satellite operation see Annex J.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.8.2 Requirements
|
Subject to operator’s policies, a 5G system with satellite access shall be able to support S&F Satellite operation for authorized UEs e.g. store data on the satellite when the feeder link is unavailable; and forward the data once the feeder link between the satellite and the ground segment becomes available.
A 5G system with satellite access shall be able to inform a UE whether S&F Satellite operation is applied.
Subject to operator’s policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to allow the operator or a trusted 3rd party to apply, on a per UE and/or satellite basis, an S&F data retention period.
Subject to operator’s policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to allow the operator or a trusted 3rd party to apply, on a per UE and/or satellite basis, an S&F data storage quota.
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access supporting S&F Satellite operation shall be able to support a mechanism to configure and provision specific store and forward QoS and policies for a UE (e.g. forwarding priority, acknowledgment policy).
A 5G system with satellite access supporting S&F Satellite operation shall be able to provide related information (e.g. estimated delivery time to the authorised 3rd party) to an authorized UE.
A 5G system with satellite access shall be able to inform an authorised 3rd party whether S&F Satellite operation is applied for communication with a UE and to provide related information (e.g. estimated delivery time to the authorised UE).
Subject to operator’s policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to support forwarding of the stored data from one satellite to another satellite (e.g., which has an available feeder link to the ground network), through ISLs.
NOTE: It is assumed that the satellite constellation knows which satellite has a feeder link available. However, this is outside the scope of 3GPP.
Subject to operator’s policies, a 5G system with satellite access supporting the S&F Satellite operation shall be able to support suitable means to resume communication between the satellite and the ground station once the feeder link becomes available.
A 5G system with satellite access supporting S&F Satellite operation shall support mechanisms for a UE to register with the network when the network is in S&F Satellite operation.
A 5G system with satellite access supporting S&F Satellite operation shall support mechanisms to authorize subscribers for receiving services when the network is in S&F Satellite operation.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.9 UE-Satellite-UE communication
|
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support UE-Satellite-UE communication regardless of whether the feeder link is available or not.
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to provide QoS control of a UE-Satellite-UE communication.
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support different types of UE-Satellite-UE communication (e.g. voice, messaging, broadband, unicast, multicast, broadcast).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.10 Positioning aspects for satellite access
|
For a 5G system with satellite access, the following requirements apply:
- Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support 3GPP positioning methods for UEs using only satellite access.
- A 5G system with satellite access shall be able to provide positioning service to a UE using only satellite access and the information on positioning services (e.g. supported positioning performance).
NOTE 1: UE can be with or without GNSS capabilities
- A 5G system with satellite access shall be able to support negotiation of positioning methods, between UE and network, according e.g. to 3GPP RAT and UE positioning capability, the availability of non-3GPP positioning technologies (e.g. GNSS). - Subject to the regulatory requirements and operator’s policy, the 5G system with satellite access shall be able to provide location information of a UE that uses only satellite access for emergency service to a PSAP.
NOTE 2: the accuracy of a UE’s location information will be in compliance with regulatory requirements.
6.46.11 IMS voice using GEO satellite access
The 5G system with GEO satellite access shall be able to support IMS voice communication as defined in TS 22.228 [55].
The 5G system with GEO satellite access shall be able to provide mechanisms to optimize IMS voice (e.g., call setup, transmission overhead) and support a codec for the transfer of the voice considering the transmission data rate, latency and packet size.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.12 Multi-orbit
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.12.1 Description
|
A 5G system with satellite access can be composed of multiple satellite orbit types such as GEO, MEO, LEO and each of these satellite orbit types can have different characteristics (e.g., altitude, orbital characteristics, satellite capabilities).
The requirements below refer to multi-orbit.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.12.2 Requirements
|
A 5G network with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to improve the network’s energy efficiency of the satellite access network, by e.g., switching different power saving modes of the satellites based on user density and/or data demand.
Subject to regulatory requirements and operator’s policy, a 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to assist a UE (e.g., provide the UE with the necessary information) to acquire and access the suitable satellite among those available.
NOTE 1: The information provided to the UE can include satellites information operated by roaming partners.
NOTE 2: Acquisition of satellite signals may be required prior to the initial access procedure, including, e.g. the determination of the antenna pointing direction. In this use case, network selection procedures follow the existing procedures.
Subject to regulatory requirements and operator policies, the 5G network with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall support the selection of suitable satellites for the UE and the switching between satellites with orbit types having different characteristics depending on e.g. latency requirements, QoS requirements, access capabilities and availability.
A 5G network with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to support establishing the initial UE connection to the network through satellites with a given characteristics and then having the UE data traffic using satellite with different characteristics.
Subject to regulatory requirements and operator’s policies, a 5G network with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to provide high throughput performance and maintain consistent QoE to the users accessing the UE (e.g., Relay or CPE) when the UE is moving with a high speed.
Based on regulatory requirements, operators’ policy and agreement with 3rd party, the 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall support a mechanism to provide suitable Service Hosting Environment across satellites with orbit types having different characteristics.
NOTE 3: One example is an operator can choose the most suitable service hosting environment on-board of satellites, based on the topology of satellites as they are moving on the orbits.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.46.12.3 Requirements related to mobile base station relays
|
Subject to regulatory requirements and operator’s policies, the 5G network with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall be able to support mobile base station relays to access satellites with orbit types having different characteristics considering e.g., availability of the coverage, latency, data rate, required QoS.
Subject to regulatory requirements and operator’s policies, the 5G system with satellite access supporting multiple satellite orbit types with different characteristics (e.g., altitude, orbital characteristics, satellite capabilities) shall support connectivity between a mobile base station relay and the 5G Core through simultaneously using terrestrial and one multi orbit satellite access path taking into account the respective capabilities (e.g., latency, data rate) and availability of the different satellite access (e.g., over GEO, MEO, LEO) to map the traffic with the aggregated QoS required at the mobile base station relay.
6.47 5G wireless sensing service6.47.1 Description
The 3GPP system is expected to support 5G wireless sensing service to acquire information about characteristics of the environment and/or objects within the environment, such as the distance (range), angle, or instantaneous linear velocity of objects, etc.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.47.2 Requirements
|
The 3GPP system supports the 5G wireless sensing service to acquire information in various scenarios. The associated requirements are described in 3GPP TS 22.137 [51].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.48 Ambient power-enabled IoT
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.48.1 Description
|
An Ambient IoT technology has characteristics of low complexity, low data rate, small size, energy harvesting, lower capabilities and lower power consumption than previously defined 3GPP IoT technologies (e.g. NB-IoT/eMTC devices). Ambient IoT devices can be maintenance free and can have long life span (e.g. more than 10 years)
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.48.2 Requirements
|
Service requirements associated with Ambient IoT are described in 3GPP TS 22.369 [52] to support the ambient power enabled IoT service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.49 Mobile Metaverse Services
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.49.1 Description
|
Mobile metaverse services refer to a shared, perceived set of interactive perceived spaces that can be persistent. The term metaverse has been used in various ways to refer to the broader implications of AR and VR. Metaverse in diverse sectors evokes a number of possible user experiences, products and services can emerge once virtual reality and augmented reality become commonly available and find application in our work, leisure and other activities. Functional enhancements and capabilities included in standards specifications make these services function well, consistently and with diverse support mechanisms over mobile telecommunications networks.
In addition to services that offer virtual or location-independent user experiences, mobile metaverse services also supports content and services that are associated or applicable only in a particular location. These metaverse services are mobile in the sense that mobile users are able to interact with services anywhere and in particular when in the locations where specific services are offered. Requirements for diverse service enablers are introduced to the 5G system to support these services, including avatar call functionality, coordination of services, digital asset management and support for spatial anchors.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.49.2 Requirements
|
The 5G system supports services and service enablers for Mobile Metaverse Services. The associated functional and performance requirements are documented in TS 22.156 [53].
Related requirements concerning media exist in the present document, including in clause 6.43 related to tactile and multi-modal communication, and performance requirements in clause 7, especially 7.6.1 for AR/VR services and 7.11 for tactile and multi-modal communication service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50 Traffic steering and switching over two 3GPP access networks
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50.1 Introduction
|
The following requirements cover scenarios and functionalities for supporting enhanced traffic steering and switching of a DualSteer device’s user data (for different services) across two 3GPP access networks, assuming the ability to differentiate the two connections for the same device and minimize impacts to CN, O&M or IT systems.
Target scenarios cover two 3GPP access networks belonging to the same PLMN, or between two different PLMNs, or between one PLMN and one PLMN-integrated NPN, over same or different RAT, which can use terrestrial and/or satellite access (including the case of two different satellite orbits). Scenarios may also include traffic steering and/or switching across E-UTRA/EPC and NR/5GC, with anchoring in 5GC.
Traffic policies are intended to be in full control of the home network operator.
The requirements below can apply to different DualSteer device types (e.g., smartphones, IoT, UAV, VSAT devices).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50.2 Requirements
|
For the requirements below, the following applies:
- a subscriber with two subscriptions/SUPIs, sharing one subscription profile from the same operator;
- for simultaneous transmission over two networks, a DualSteer device is assumed to include two separate UEs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50.2.1 General
|
Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and/or switching of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN and non-simultaneous transmission over the two networks.
Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and/or switching with simultaneous transmission of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN.
Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and/or switching of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business/roaming agreement between PLMN operators (if different), data anchoring in the HPLMN and non-simultaneous transmission over the two networks.
Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and/or switching with simultaneous transmission of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business/roaming agreement between PLMN operators (if different) and HPLMN data anchoring.
NOTE 1: Inter-PLMN requirements can apply also to PLMN-NPN scenarios assuming a PLMN-integrated NPN (NPN hosted by a PLMN or offered as a slice of a PLMN).
For traffic steering and/or switching of user data across two 3GPP access networks, the 5G system shall be able to allow a HPLMN to provide policies and criteria for a DualSteer device to connect to an additional PLMN/NPN, or an additional RAT within the same PLMN.
NOTE 2: The above requirements assume configuration of traffic policies, under HPLMN control or negotiated between the HPLMN and other network operators, considering e.g., user subscription, application/traffic type, service preference, QoS requirements, location, time, UE capabilities, mobility, connectivity conditions.
For any particular service, at any given time, the DualSteer device shall transmit all traffic of that service using only a single 3GPP access network.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50.2.2 Mobility and connectivity changes
|
Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to minimize service interruption when switching a DualSteer device’s user data, for one or multiple services, between two 3GPP access networks.
Subject to HPLMN policy and network control, for traffic steering and/or switching of user data across two 3GPP access networks, the 5G system may be able to support mechanisms to change one 3GPP access network to the non-3GPP access network of the same subscription (and vice versa).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.50.2.3 Other aspects
|
NOTE 1: Charging requirements for "Traffic steering and switching over two 3GPP access networks" can be found in clause 9.15 of this document.
Subject to home network operator policy and network control, the 5G system shall be able to support traffic steering and/or switching of a DualSteer device’s user data between a NPN and a PLMN, for one or more a DualSteer devices with a NPN subscription accessing NPN services, to meet specific QoS requirements for each device, assuming non-simultaneous transmission over the two 3GPP access networks.
NOTE 2: The above assumes a NPN hosted by a PLMN or offered as a slice of a PLMN, data anchoring in the NPN, and a business/roaming agreement between the PLMN and the NPN operator (if different).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.51 Monitoring of network elements interactions in 5G
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.51.1 Overview
|
External monitoring systems are often used by MNOs to track network activity for network surveillance and troubleshooting to perform diagnosis and fault analysis of their system. Such monitoring system is fully under the control of the MNOs, and the monitoring can be performed at signalling level. Due to the introduction of encryption of the signalling exchanged between network functions, there is no standardized, secure interface to share signalling traffic between the 5G network and the monitoring system.
A number of capabilities are required for the 5G network to continue supporting this feature, with regards to performance to minimise the impact on the real-time traffic and to consider the security needed to protect the copies sent towards the external monitoring system.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.51.2 Requirements
|
NOTE 1: The monitoring system is outside of the 5G network. Both the monitoring system and the monitored network elements in the requirements below are fully under the control of the MNO.
The monitored network elements in the 5G network shall support the transmission of a secured copy of the outgoing and incoming signalling traffic to a monitoring system.
The 5G network shall enable the MNO to configure network monitoring, e.g., switching on/off per network element, selecting what type of elements and what type of signalling from these elements is the target for monitoring.
The 5G network shall allow the monitoring (i.e., transmit secured copies of outgoing and incoming signalling traffic) of a transmitting network element and, separately, the monitoring of the receiving network element while facilitating correlation of the information received from both network elements by the external system.
NOTE 2: These requirements do not imply/assume any design of the network elements. How the copies are created within the element, e.g., physical, virtual or container based, is expected to be implementation specific.
The signalling traffic shall be securely transmitted from the monitored network elements of the 5G network to the monitoring system while minimizing the degradation of network performance.
NOTE 3: The monitoring system is not integrated with the key management scheme of the 5G core.
The transmission of signalling traffic from the monitored network elements of the 5G network to the monitoring system shall be compliant with privacy legislation, data protection regulations and protection of confidential system internal data.
The transmission of signalling traffic from the monitored network elements of the 5G network to the monitoring system shall be limited regarding the number of file formats (e.g., JSON, PCAP, etc.) to assist with the ingestion of traffic feeds.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7 Performance requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.1 High data rates and traffic densities
|
Several scenarios require the support of very high data rates or traffic densities of the 5G system. The scenarios address different service areas: urban and rural areas, office and home, and special deployments (e.g. massive gatherings, broadcast, residential, and high-speed vehicles). The scenarios and their performance requirements can be found in table 7.1-1.
- Urban macro – The general wide-area scenario in urban area
- Rural macro – The general wide-area scenario in rural area
- Indoor hotspot – The scenario for offices and homes, and residential deployments.
- Broadband access in a crowd – The scenario for very dense crowds, for example, at stadiums or concerts. In addition to a very high connection density the users want to share what they see and hear, putting a higher requirement on the uplink than the downlink.
- Dense urban – The scenario for pedestrian users, and users in urban vehicles, for example, in offices, city centres, shopping centres, and residential areas. The users in vehicles can be connected either directly or via an onboard base station to the network.
- Broadcast-like services – The scenario for stationary users, pedestrian users, and users in vehicles, for example, in offices, city centres, shopping centres, residential areas, rural areas and in high speed trains. The passengers in vehicles can be connected either directly or via an onboard base station to the network.
- High-speed train – The scenario for users in trains. The users can be connected either directly or via an onboard base station to the network.
- High-speed vehicle – The scenario for users in road vehicles. The users can be connected either directly or via an onboard base station to the network.
- Airplanes connectivity – The scenario for users in airplanes. The users can be connected either directly or via an onboard base station to the network.
Table 7.1-1 Performance requirements for high data rate and traffic density scenarios.
Scenario
Experienced data rate (DL)
Experienced data rate (UL)
Area traffic capacity
(DL)
Area traffic capacity
(UL)
Overall user density
Activity factor
UE speed
Coverage
1
Urban macro
50 Mbit/s
25 Mbit/s
100 Gbit/s/km2
(note 4)
50 Gbit/s/km2
(note 4)
10 000/km2
20 %
Pedestrians and users in vehicles (up to 120 km/h
Full network (note 1)
2
Rural macro
50 Mbit/s
25 Mbit/s
1 Gbit/s/km2
(note 4)
500 Mbit/s/km2
(note 4)
100/km2
20 %
Pedestrians and users in vehicles (up to 120 km/h
Full network (note 1)
3
Indoor hotspot
1 Gbit/s
500 Mbit/s
15 Tbit/s/km2
2 Tbit/s/km2
250 000/km2
note 2
Pedestrians
Office and residential (note 2) (note 3)
4
Broadband access in a crowd
25 Mbit/s
50 Mbit/s
[3,75] Tbit/s/km2
[7,5] Tbit/s/km2
[500 000]/km2
30 %
Pedestrians
Confined area
5
Dense urban
300 Mbit/s
50 Mbit/s
750 Gbit/s/km2
(note 4)
125 Gbit/s/km2
(note 4)
25 000/km2
10 %
Pedestrians and users in vehicles (up to 60 km/h)
Downtown (note 1)
6
Broadcast-like services
Maximum 200 Mbit/s (per TV channel)
N/A or modest (e.g. 500 kbit/s per user)
N/A
N/A
[15] TV channels of [20 Mbit/s] on one carrier
N/A
Stationary users, pedestrians and users in vehicles (up to 500 km/h)
Full network (note 1)
7
High-speed train
50 Mbit/s
25 Mbit/s
15 Gbit/s/train
7,5 Gbit/s/train
1 000/train
30 %
Users in trains (up to 500 km/h)
Along railways
(note 1)
8
High-speed vehicle
50 Mbit/s
25 Mbit/s
[100] Gbit/s/km2
[50] Gbit/s/km2
4 000/km2
50 %
Users in vehicles (up to 250 km/h)
Along roads
(note 1)
9
Airplanes connectivity
15 Mbit/s
7,5 Mbit/s
1,2 Gbit/s/plane
600 Mbit/s/plane
400/plane
20 %
Users in airplanes (up to 1 000 km/h)
(note 1)
NOTE 1: For users in vehicles, the UE can be connected to the network directly, or via an on-board moving base station.
NOTE 2: A certain traffic mix is assumed; only some users use services that require the highest data rates [2].
NOTE 3: For interactive audio and video services, for example, virtual meetings, the required two-way end-to-end latency (UL and DL) is 2‑4 ms while the corresponding experienced data rate needs to be up to 8K 3D video [300 Mbit/s] in uplink and downlink.
NOTE 4: These values are derived based on overall user density. Detailed information can be found in [10].
NOTE 5: All the values in this table are targeted values and not strict requirements.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.2 Low latency and high reliability
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.2.1 Overview
|
Several scenarios require the support of very low latency and very high communications service availability. Note that this implies a very high reliability. The overall service latency depends on the delay on the radio interface, transmission within the 5G system, transmission to a server which can be outside the 5G system, and data processing. Some of these factors depend directly on the 5G system itself, whereas for others the impact can be reduced by suitable interconnections between the 5G system and services or servers outside of the 5G system, for example, to allow local hosting of the services.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.2.2 Scenarios and KPIs
|
Different deployments of URLLC capabilities will depend on the 3GPP system being able to meet specific sets of KPIs with different values and ranges applicable for each attribute. A common, yet flexible, 5G approach to URLLC will enable the 5G system to meet the specific sets of KPIs needed in a given implementation. To provide clear and precise requirements for specific types of services, the corresponding KPI requirements are included in other specifications as follows:
- Cyber-physical control applications in vertical domains can be found in 22.104 [21].
- V2X can be found in 22.186 [9].
- Rail communications can be found in 22.289 [23].
Some scenarios requiring very low latency and very high communication service availability are described below:
- Motion control – Conventional motion control is characterised by high requirements on the communications system regarding latency, reliability, and availability. Systems supporting motion control are usually deployed in geographically limited areas but can also be deployed in wider areas (e.g. city- or country-wide networks), access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers.
- Discrete automation – Discrete automation is characterised by high requirements on the communications system regarding reliability and availability. Systems supporting discrete automation are usually deployed in geographically limited areas, access to them can be limited to authorized users, and they can be isolated from networks or network resources used by other cellular customers.
- Process automation – Automation for (reactive) flows, e.g. refineries and water distribution networks. Process automation is characterized by high requirements on the communications system regarding communication service availability. Systems supporting process automation are usually deployed in geographically limited areas, access to them is usually limited to authorized users, and it will usually be served by non-public networks.
- Automation for electricity distribution and smart grid (mainly medium and high voltage). Electricity distribution and smart grid are is characterized by high requirements on the communications service availability and security, as well as low latency in some cases. In contrast to the above use cases, electricity distribution and smart grid are deeply immersed into the public space. Since electricity distribution is an essential infrastructure, it is well served by network slices to provide service isolation and security, or by non-public networks.
- Wireless road-side infrastructure backhaul in intelligent transport systems – Automation solutions for the infrastructure supporting street-based traffic. This use case addresses the connection of the road-side infrastructure, e.g. roadside units, with other infrastructure, e.g. a traffic guidance system. As is the case for automation electricity, the nodes are deeply immersed into the public space.
- Remote control – Remote control is characterised by a UE being operated remotely by a human or a computer. For example, Remote Driving enables a remote driver or a V2X application to operate a remote vehicle with no driver or a remote vehicle located in a dangerous environment.
- Rail communications (e.g. railway, rail-bound mass transit) have been using 3GPP based mobile communication (e.g. GSM-R) already for some time, while there is still a driver on-board of the train. The next step of the evolution will be providing fully automated train operation that requires highly reliable communication with moderate latencies but at very high speeds of up to 500 km/h.
For specific requirements, refer to the specifications noted above [21], [9], [23].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.2.3 Other requirements
|
7.2.3.1 (void)
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.2.3.2 Wireless road-side infrastructure backhaul
|
Intelligent Transport Systems embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public.
Road-side infrastructure such as traffic light controllers, roadside units, traffic monitoring in urban areas and along highways and streets is wirelessly connected to traffic control centres for management and control purposes. The backhaul communication between the road-side infrastructure and the traffic control centre requires low-latency, high communication service availability, and high-capacity connections for reliable distribution of data. Road-side infrastructure is deployed alongside streets in urban areas and alongside major roads and highways every 1-2 km.
For more information about infrastructure backhaul, see clause D.5.
To support wireless road-side infrastructure backhaul the 5G system shall support the performance requirements in table 7.2.3.2-1.
Table 7.2.3.2-1 Performance requirements for wireless ITS infrastructure backhaul scenario
Scenario
Max. allowed end-to-end latency
(note 1)
Survival time
Communication service availability
(note 2)
Reliability
(note 2)
User experienced data rate
Payload
size
(note 3)
Traffic density
(note 4)
Connection density
(note 5)
Service area dimension
(note 6)
wireless road-side infrastructure backhaul
30 ms
100 ms
99,9999%
99,999%
10 Mbit/s
Small to big
10 Gbit/s/km2
1 000/km2
2 km along a road
NOTE 1: This is the maximum end-to-end latency allowed for the 5G system to deliver the service in the case the end-to-end latency is completely allocated to the 5G system from the UE to the Interface to Data Network.
NOTE 2: Communication service availability relates to the service interfaces, and reliability relates to a given system entity. One or more retransmissions of network layer packets can take place in order to satisfy the reliability requirement.
NOTE 3: Small: payload typically ≤ 256 bytes
NOTE 4: Based on the assumption that all connected applications within the service volume require the user experienced data rate.
NOTE 5: Under the assumption of 100% 5G penetration.
NOTE 6: Estimates of maximum dimensions; the last figure is the vertical dimension.
NOTE 7: All the values in this table are example values and not strict requirements. Deployment configurations should be taken into account when considering service offerings that meet the targets.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3 High-accuracy positioning
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3.1 Description
|
Adaptability and flexibility are among the key features of the 5G system to serve a wide diversity of verticals and services, in different environments (e.g. rural, urban, indoor). This applies to high-accuracy positioning and translates into the ability to satisfy different levels of services and requirements, for instance on performance (e.g. accuracy, positioning service availability, positioning service latency) and on functionality (e.g. security).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3.2.1 General
|
The 5G System shall provide different 5G positioning services with configurable performances working points (e.g. accuracy, positioning service availability, positioning service latency, energy consumption, update rate, TTFF) according to the needs of users, operators and third parties.
The 5G system shall support the combination of 3GPP and non-3GPP positioning technologies to achieve performances of the 5G positioning services better than those achieved using only 3GPP positioning technologies.
NOTE 1: For instance, the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as GNSS (e.g. Beidou, Galileo, GLONASS, and GPS), Terrestrial Beacon Systems (TBS), sensors (e.g. barometer, IMU), WLAN/Bluetooth-based positioning, can support the improvement of accuracy, positioning service availability, reliability and/or confidence level, the reduction of positioning service latency, the increase of the update rate of the position-related data, increase the coverage (service area).
NOTE 2: The combination can vary over time to optimise the performances, and can be the combination of multiple positioning technologies at the same epoch and/or the combination of multiple positioning technologies at different epochs.
The corresponding positioning information shall be acquired in a timely fashion, be reliable, and be available (e.g. it is possible to determine the position).
UEs shall be able to share positioning information between each other e.g. to a controller if the location information cannot be processed or used locally.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3.2.2 Requirements for horizontal and vertical positioning service levels
|
The 5G system shall be able to provide positioning services with the performances requirements reported in Table 7.3.2.2-1.
NOTE: The requirements do not preclude any type of UE, including specific UE such as for example V2X, MTC.
Table 7.3.2.2-1 Performance requirements for Horizontal and Vertical positioning service levels
Positioning service level
Absolute(A) or Relative(R) positioning
Accuracy
(95 % confidence level)
Positioning service availability
Positioning service latency
Coverage, environment of use and UE velocity
Horizontal Accuracy
Vertical Accuracy
(note 1)
5G positioning service area
5G enhanced positioning service area
(note 2)
Outdoor and tunnels
Indoor
1
A
10 m
3 m
95 %
1 s
Indoor - up to 30 km/h
Outdoor
(rural and urban) up to 250 km/h
NA
Indoor - up to 30 km/h
2
A
3 m
3 m
99 %
1 s
Outdoor
(rural and urban) up to 500 km/h for trains and up to 250 km/h for other vehicles
Outdoor
(dense urban) up to 60 km/h
Along roads up to 250 km/h and along railways up to 500 km/h
Indoor - up to 30 km/h
3
A
1 m
2 m
99 %
1 s
Outdoor
(rural and urban) up to 500 km/h for trains and up to 250 km/h for other vehicles
Outdoor
(dense urban) up to 60 km/h
Along roads up to 250 km/h and along railways up to 500 km/h
Indoor - up to 30 km/h
4
A
1 m
2 m
99,9 %
15 ms
NA
NA
Indoor - up to 30 km/h
5
A
0,3 m
2 m
99 %
1 s
Outdoor
(rural) up to 250 km/h
Outdoor
(dense urban) up to 60 km/h
Along roads and along railways up to 250 km/h
Indoor - up to 30 km/h
6
A
0,3 m
2 m
99,9 %
10 ms
NA
Outdoor
(dense urban) up to 60 km/h
Indoor - up to 30 km/h
7
R
0,2 m
0,2 m
99 %
1 s
Indoor and outdoor (rural, urban, dense urban) up to 30 km/h
Relative positioning is between two UEs within 10 m of each other or between one UE and 5G positioning nodes within 10 m of each other (note 3)
NOTE 1: The objective for the vertical positioning requirement is to determine the floor for indoor use cases and to distinguish between superposed tracks for road and rail use cases (e.g. bridges).
NOTE 2: Indoor includes location inside buildings such as offices, hospital, industrial buildings.
NOTE 3: 5G positioning nodes are infrastructure equipment deployed in the service area to enhance positioning capabilities (e.g. beacons deployed on the perimeter of a rendezvous area or on the side of a warehouse).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.3.2.3 Other performance requirements
|
The 5G system shall be able to provide the 5G positioning services with a TTFF less than 30 s and, for some 5G positioning services, shall support mechanisms to provide a TTFF less than 10 s.
NOTE 1: In some services, a TTFF of less than 10s can only be achievable at the expense of a relaxation of some other performances (e.g. horizontal accuracy can be 1 m or 3 m after 10 s TTFF, and reach a steady state accuracy of 0,3 m after 30 s).
The 5G system shall support a mechanism to determine the UE's velocity with a positioning service availability of 99%, an accuracy better than 0,5 m/s for the speed and an accuracy better than 5 degree for the 3-Dimension direction of travel.
The 5G system shall support a mechanism to determine the UE's heading with an accuracy better than 30 degrees (0,54 rad) and a positioning service availability of 99,9 % for static users and with an accuracy better than 10 degrees (0,17 rad) and a positioning service availability of 99 % for users up to 10 km/h.
For power consumption aspects for various usage scenarios see TS 22.104 [21]
Low power high accuary positioning use cases and example scenarios for Industrial IoT devices can be found in 3GPP TS 22.104 [21].
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.4 KPIs for a 5G system with satellite access
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.4.1 Description
|
Satellite access networks are based on infrastructures integrated on a minimum of satellites that can be placed in either GEO, MEO or LEO.
The propagation delay via satellite associated with these orbit ranges can be summarized in Table 7.4.1-1:
Table 7.4.1-1: Propagation delay via satellite
UE to serving satellite propagation delay [ms] [NOTE 1]
UE to ground max propagation delay [ms] [NOTE 2]
Min
Max
LEO
1
13
26
MEO
24
99
198
GEO
120
136
272
NOTE1: The serving satellite provides the satellite radio link to the UE. The delay range for LEO is calculated at elevation angle 90° with 300 km and 10° with 1 500 km. The delay range for MEO is calculated at elevation angle 90° with 7 000 km and 10° with 25 000 km. The delay range for GEO is calculated at elevation angle 90° to 10° with 35 786km.
NOTE2: delay between UE and ground station via satellite link; Inter satellite links are not considered
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.4.2 Requirements
|
A 5G system providing service with satellite access shall be able to support GEO based satellite access with up to 285 ms end-to-end latency.
NOTE 1: 5 ms network latency is assumed and added to satellite one-way delay.
A 5G system providing service with satellite access shall be able to support MEO based satellite access with up to 95 ms end-to-end latency.
NOTE 2: 5 ms network latency is assumed and added to satellite one-way delay.
A 5G system providing service with satellite access shall be able to support LEO based satellite access with up to 35 ms end-to-end latency.
NOTE 3: 5 ms network latency is assumed and added to satellite one-way delay.
A 5G system shall support negotiation on quality of service taking into account latency penalty to optimise the QoE for UE.
The 5G system with satellite access shall support high uplink data rates for 5G satellite UEs.
The 5G system with satellite access shall support high downlink data rates for 5G satellite UEs.
The 5G system with satellite access shall support communication service availabilities of at least 99,99%.
Table 7.4.2-1: Performance requirements for satellite access
Scenario
Experienced data rate (DL)
Experienced data rate (UL)
Area traffic capacity
(DL)
(note 1)
Area traffic capacity
(UL)
(note 1)
Overall user density
Activity factor
UE speed
UE type
Others
Pedestrian
(note 2)
[1] Mbit/s
[100] kbit/s
1,5 Mbit/s/km2
150 kbit/s/km2
[100]/km2
[1,5] %
Pedestrian
Handheld
-
Public safety
[3,5] Mbit/s
[3,5] Mbit/s
TBD
TBD
TBD
N/A
100 km/h
Handheld
-
Vehicular connectivity
(note 3)
50 Mbit/s
25 Mbit/s
TBD
TBD
TBD
50 %
Up to 250 km/h
Vehicle mounted
-
Airplanes connectivity
(note 4)
[1] Gbit/s
per plane
[300] Mbit/s
per plane
TBD
TBD
TBD
40%
Up to [1500] km/h
Airplane mounted
-
Stationary
50 Mbit/s
25 Mbit/s
TBD
TBD
TBD
N/A
Stationary
Building mounted
-
Video surveillance
(note 4a)
[0,5] Mbit/s
[3] Mbit/s
TBD
TBD
TBD
N/A
Up to 120km/h or
stationary
(note 4b)
Vehicle mounted or fixed installation
-
Narrowband IoT connectivity
[2] kbit/s
[10] kbit/s
8 kbit/s/km2
40 kbit/s/km2
[400]/km2
[1] %
[Up to 100 km/h]
IoT
-
IMS voice call using GEO
(note 7)
[1-3] kbit/s
[1-3] kbit/s
N/A
N/A
N/A
N/A
TBD
Handheld
Call set up time (note 8) ≤30 s
(note 9)
Note 1: Area capacity is averaged over a satellite beam.
Note 2: Data rates based on Extreme long-range coverage target values in clause 6.17.2. User density based on rural area in Table 7.1-1.
Note 3: Based on Table 7.1-1
Note 4: Required experienced peak data rate corresponding to the aggregated passenger traffic at aircraft level
Based on an assumption of 450 seats, average take rate of 75% (free model) and load factor of 85%
Assumption of 3:1 Downlink / Uplink ratio, anticipating future usages
The Downlink & Uplink throughput can be achieved using one or multiple linksNote 4a: Refer to video surveillance data transmitted (in UL) from a UE on the ground (e.g. picture or video from a camera) using satellite NG-RAN to connect to 5GC, and video surveillance-related configuration or control data sent (in DL) to the UE/device. 0.5 Mbit/s for DL experienced data rate is based on MAVLINK protocol that is widely used for UAV control. 3 Mbit/s for UL experienced data rate is based on the assumed sum from 2.5 Mbit/s for video streaming and 0.5 Mbit/s for data transmission.
Note 4b: Up to 120km/h applies to vehicle mounted while stationary applies to fixed installation.
Note 5: All the values in this table are targeted values and not strict requirements.
Note 6: Performance requirements for all the values in this table should be analyzed independently for each scenario.
Note 7: All the values defined for IMS voice call using GEO satellite access are generic for both regular and emergency calls.
Note 8: call set up time refers to [56];
Note 9: 30s is the upper bound that is derived based on the user’s patience suggestions (30s) in [57];
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.5 High-availability IoT traffic
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.5.1 Description
|
Several scenarios require the support of highly reliable machine type communication such as those, typically (but not restricted to) related to medical monitoring. They involve different deployment areas, different device speeds and densities and require a high-availability communication service to transfer a low data rate uplink data stream from one or several devices to an application.
Their related performance requirements can be found in table 7.5.2-1.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.5.2 Requirements
|
Table 7.5.2‑1: Performance requirements for highly reliable machine type communication
Profile
Characteristic parameter
Influence quantity
Communication service availability: target value in %
Communication service reliability (Mean Time Between Failure)
End-to-end latency: maximum
Bit rate
Direction
Message
Size
[byte]
Transfer Interval
Survival Time
UE speed
(km/h)
# of UEs
connection
Service Area
Medical monitoring (note 2)
> 99,9999
<1 year (>> 1 month)
< 100 ms
< 1 Mbit/s
Uplink
~ 1000
50 ms
Transfer Interval
< 500
10/km2 to 1000/km2
Country wide including rural areas and deep indoor. (note 1)
NOTE 1: "deep indoor" term is meant to be places like e.g. elevators, building’s basement, underground parking lot, …
NOTE 2: These performance requirements aim energy-efficient transmissions performed using a device powered with a 3.3V battery of capacity < 1000 mAh that can last at least 1 month without recharging and whereby the peak current for transmit operations stays below 50 mA.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
7.6 High data rate and low latency
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.