hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
5.14 Recovery/Restoration
|
The 3GPP system shall allow operational measures to expedite service recovery and restoration (i.e., service restoration after failure/unavailability). Should a disruption occur, MPS shall be re-provisioned, repaired, or restored to required service levels on a priority basis subject to regional/national regulatory requirements and operator policy.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
5.15 Quality of Service (QoS)
|
In certain cases, the QoS characteristics (e.g., packet delay and packet loss) for an MPS session may be the same as the underlying communication service (e.g., voice, video, data or messaging) used to support the MPS session, with the MPS session being provided priority treatment subject to regional/national regulatory and operator policies. In other cases, there may be a need to request specific QoS characteristics for the MPS session (e.g., specific data communications as described in clause 5.4a, 9.3).
The 3GPP network shall allow selection and/or configuration of QoS rule(s) appropriate for MPS Voice, Video, Data and Messaging.
The 3GPP network shall allow enforcement of QoS rule(s) for MPS Voice, Video, Data, and Messaging.
The system shall support means to retain MPS sessions invoked for Voice, Video, Data and Messaging during transient network degradation conditions and recovery (e.g., during short radio link interruption), and re-verify any recovered MPS session afterwards.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
5.16 Inter-network aspects
|
The system shall allow MPS priorities to be signalled across interconnected networks.
NOTE 1: Support of MPS services across networks is based on policy and agreements between the network operators.
NOTE 2: Intermediate 3GPP networks not supporting MPS (e.g., transit networks between an originating network and terminating network) should allow MPS priorities to be signalled transparently, based on operator policy and agreements for MPS.
The system shall support means to identify that an incoming voice, video, data or messaging service session from another network is an MPS session and to handle it with priority.
The system shall support measures to verify policy and admit an incoming MPS session for Voice, Video, Data, or Messaging service received from another network with priority.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
5.17 Interactions with supplementary services
|
Interactions with a supplementary service might occur during set-up or after establishment of an MPS call or session. A supplementary service is a service which modifies or supplements a basic telecommunication service (see definition in 3GPP TR 21.905 [1]).
The system shall provide MPS priority for a supplementary service associated with an MPS call or session in progress when the supplementary service is associated with the Service User authorized for MPS.
When a supplementary service (e.g., Communication Diversion) results in an established authorized MPS call or session being redirected or extended, MPS priority shall be provided for the redirected or extended call or session.
When a supplementary service (e.g., Conference/Three-Party) is used to join an MPS priority call or session (e.g., to add parties to the established MPS call/session), MPS priority shall be retained on that leg when joined to the supplementary service.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
5.18 3GPP and non-3GPP accesses
|
When a UE is using 3GPP RAT(s) as well as non-3GPP WLAN access technology, the 3GPP system will select the most appropriate 3GPP RAT or non-3GPP WLAN access technology for one or more services active on theUE. This subclause covers MPS handling when 3GPP RAT(s) and non-3GPP WLAN access technology are being used for one or more services active on a UE.
The system shall support MPS based on operator policy when the UE is using E-UTRA and non-3GPP WLAN and connected to the same EPC.
The system shall support MPS based on operator policy when the UE is using 3GPP RAT(s) and non-3GPP WLAN and connected to the same 5GC.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
6 MMI aspects
|
In the case when MPS invocation is based on the presence of an MPS-specific service code entered by the originating Service User, this specific service code must be defined for the 3GPP network to recognize such an invocation.
The 3GPP network supporting on-demand invocation of MPS shall recognize a service code indicating a request for MPS.
NOTE: A Service User roaming within or outside the home country must use an MPS-specific service code recognized by the visited PLMN, to indicate a request for MPS based on the agreements between the home and visited PLMNs for MPS.
The choice of an MPS-specific service code is a regional/national and operator matter.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7 Security and privacy
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.1 General
|
Operators support and use a wide range of security tools and capabilities to protect the 3GPP system and all supported application services. It is important that appropriate measures be taken to ensure that the use of these security capabilities does not negatively impact MPS.
Use of security mechanisms (e.g., intrusion detection / prevention systems, deep packet inspection, and encryption) shall not interfere with priority treatment mechanisms supporting authorized MPS usage.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.2 Access Control
|
Access to MPS shall be determined based on the subscriber's profile. A level of authorisation in addition to authorisation to use the IMS is required.
Unauthorized access to MPS shall be prevented.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.3 Integrity
|
The 3GPP system shall be capable of providing integrity protection to MPS signalling and media bearers for voice, video, data, and messaging service.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.4 Confidentiality/Privacy
|
The 3GPP system shall be capable of providing confidentiality protection to MPS signalling and media bearers for voice, video, and data as appropriate.
The 3GPP system shall be capable of maintaining anonymity of the originating Service User to the terminating party, if requested by the originating Service User.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.5 Use of Encryption
|
If encryption is used on MPS communication, priority information shall be accessible to all network elements which have to understand and process that priority information.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
7.6 Attestation of Authorized MPS Priority
|
A 3GPP system receiving a session with MPS priority from another network needs to verify that the session is authorized for MPS priority.
The originating 3GPP system shall provide a means to securely attest to MPS authorization for the session.
The 3GPP system shall provide a means to securely verify the attestation of MPS authorization received from the originating network for the session.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
8 Charging aspects
|
A network supporting MPS shall be capable of recording the following charging information, in addition to non-MPS information:
- MPS invocation attempt and successful session set-up,
- Session bearers (originations and/or terminations) on which MPS was used to gain access to resources,
- Recording of MPS information, e.g., priority level.
The system shall associate MPS related charging events with the MPS subscription.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9 Service specific aspects
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1 MPS for MMTEL voice
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.1 General
|
MPS for MMTEL voice provides the Service User with priority voice communication sessions in periods of severe network congestion during which normal commercial voice service is degraded.
The system shall support:
- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE with a subscription for MPS,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE,the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for MMTEL voice and voice conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
NOTE 2: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription. .
- MPS for all participants of an authorized MMTEL voice conference call.
NOTE 3: MPS for all participants of an MMTEL voice conference call allows a Service User (i.e., the host) to establish an MMTEL voice conference with MPS for all participants, or upgrade on ongoing MMTEL voice conference to MPS for all participants regardless of their subscription to MPS.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.2 Invocation and revocation
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.2.1 Invocation
|
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice/conference call, e.g., when the normal MMTEL call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL voice call or an MPS MMTEL voice conference call, or
- request upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL voice call or conference call during roaming, e.g., when the normal MMTEL voice/conference call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL voice call, or an MPS MMTEL voice conference call when roaming within the home country and outside the home country, or
- requests upgrade of an established MMTEL voice call, or an established MMTEL voice conference call to MPS when roaming within the home country and outside the home country.
NOTE 2: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL voice call) that is recognized by the visited PLMN.
A Service User using a UE that does not have an MPS subscription can invoke MPS to request priority for an MMTEL voice call or MMTEL voice conference call, e.g., when the normal MMTEL voice call or MMTEL voice conference call cannot be established.
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL voice call or MMTEL voice conference call.
NOTE 3: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method that is outside the scope of 3GPP (e.g., by the Service User use of a predetermined access number, such as a special telephone number).
A Service User who is the host of a MMTEL voice conference can invoke MPS to upgrade the entire MMTEL voice conference call to obtain priority treatment for all participants on the MMTEL voice conference call, e.g., when the normal MMTEL voice conference call cannot be established, or to upgrade an already established normal MMTEL conference call to MPS.
The system shall support means for a Service User to:
- initiate MPS for all participants of an MMTEL voice conference call, or
- request upgrade of all participants of an ongoing MMTEL voice conference call to MPS.
The system shall provide MPS for a late participant joining an MPS for MMTEL voice conference after MPS was activated for all participants.
NOTE 4: When MPS is invoked for all participants of a MMTEL voice conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
NOTE 5: The invocation of MPS for all participants may be done using a customized feature of a voice conference service (available only to the host) that indicates a request for priority to the system.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.2.2 Revocation
|
The 3GPP system shall revoke MPS for the following cases:
• upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL voice service),
• upon end of an MPS MMTEL voice call, or an MPS MMTEL voice conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal voice service), and
• upon end of an MPS MMTEL voice conference call where MPS was provided to all participants on the voice conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL voice service).
The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL voice conference where MPS is activated for all participants.
When an MPS MMTEL voice call or an MPS MMTEL voice conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.3 Authentication and authorization
|
The system shall support means to authenticate and authorize an MPS MMTEL voice or voice conference call request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL voice or voice conference call from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN within or outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL voice or voice conference call.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL voice conference call to MPS priority.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.4 Signalling
|
The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL voice or MMTEL voice conference call is identified by the system.
The system shall support a means for MPS activation when normal MMTEL voice service is congested at the request of the Service User.
The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL voice call, or MMTEL voice conference call.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.1.5 Media
|
The system shall provide priority treatment to the audio media flows, when MPS is activated for an MMTEL voice call or MMTEL voice conference call.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2 MPS for MMTEL video
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.1 General
|
The primary purpose of MPS for MMTEL video is to provide the Service User with priority video communication sessions in periods of severe network congestion during which normal commercial video service is degraded.
The system shall support:
- MPS for MMTEL video and video conference calls for an authorized Service User using a UE with a subscription for MPS,
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE,the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for MMTEL video and video conference calls for an authorized Service User using a UE that does not have an MPS subscription, and
NOTE 2: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
- MPS for all participants of an authorized MMTEL video conference call.
NOTE 3: MPS for all participants of an MMTEL video conference call allows a Service User (i.e., the host) to establish an MMTEL video conference with MPS for all participants, or upgrade on ongoing MMTEL video conference to MPS for all participants regardless of their subscription to MPS.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.2 Invocation and revocation
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.2.1 Invocation
|
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL video call or an MPS MMTEL video conference call, or
- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call).
NOTE 2: In the case where the MMTEL video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTEL video call to MPS may be done using a using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call during roaming, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video/conference call to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to:
- initiate MPS for an MMTEL video call, or an MPS MMTEL video conference call when roaming within the home country and outside the home country, or
- request upgrade of an established MMTEL video call, or an established MMTEL video conference call to MPS when roaming within the home country and outside the home country.
NOTE 3: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User inclusion of an MPS-unique identifier or feature code as part of the request to establish an MPS for MMTEL video call) that is recognized by the visited PLMN.
NOTE 4: In the case where the MMTel video call is already established but becomes unacceptable, the invocation by the Service User to upgrade the MMTel video call to MPS may be done using a using a specialized MPS application on the UE (i.e., as an alternative to releasing and retrying the call which may fail) that is recognized by the visited PLMN.
A Service User, using a UE that does not have an MPS subscription, can invoke MPS to request priority for an MMTEL video call or MMTEL video conference call, e.g., when the normal MMTEL video call, or MMTEL video conference call cannot be established
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for an MMTEL video call or MMTEL video conference call.
NOTE 5: MPS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine access number, such as a special telephone number) and is outside the scope of 3GPP.
A Service User who is the host of a MMTEL video conference can invoke MPS to upgrade the entire MMTEL video conference call to obtain priority treatment for all participants on the MMTEL video conference call, e.g., when the normal MMTEL video call cannot be established, or to upgrade an already established normal MMTEL video conference call to MPS.
The system shall support means for a Service User to:
- initiate MPS for all participants of an MMTEL video conference call, or
- request upgrade of all participants of an ongoing MMTEL video conference call to MPS.
The system shall provide MPS for a late participant joining an MPS for MMTEL video conference after MPS was activated for all participants.
NOTE 6: When MPS is invoked for all participants of a MMTEL video conference, the user priority level is based on the host MPS Service User, except in cases where an individual participant used MPS to join the conference with a higher user priority level, the higher user priority level is kept.
NOTE 7: The invocation of MPS for all participants may be done using a customized feature of a video conference service (available only to the host) that indicates a request for priority to the system.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.2.2 Revocation
|
The 3GPP system shall revoke MPS for the following cases:
• upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE with an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal MMTEL video service),
• upon end of an MPS MMTEL video call, or an MPS MMTEL video conference call from a UE that does not have an MPS subscription, and the UE shall return to normal conditions (i.e., use of normal video service), and
• upon end of an MPS MMTEL video conference call where MPS was provided to all participants on the video conference call, and the UEs shall return to normal conditions (i.e., use of normal MMTEL video service).
The 3GPP system shall revoke MPS for an individual participant leaving an ongoing MPS for MMTEL video conference where MPS is activated for all participants.
When an MPS MMTEL video call or an MPS MMTEL video conference call is not explicitly ended, upon UE detachment/deregistration (e.g., orderly power down), the 3GPP system in the RPLMN shall automatically revoke MPS such that MPS priority treatment shall not automatically apply to subsequent calls upon subsequent registration.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.3 Authentication and authorization
|
The system shall support means to authenticate and authorize an MPS MMTEL video or video conference call request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS MMTEL video or video conference call from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., a calling card number, PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for MMTEL video or video conference call.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize a Service User request to establish or upgrade all participants of an MMTEL video conference call to MPS priority.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.4 Signalling
|
The system shall provide priority treatment to the invocation signalling in the network once the request by the Service User for MPS for an MMTEL video or MMTEL video conference call is identified by the system.
The system shall support a means for MPS activation when normal MMTEL video service is congested at the request of the Service User.
The system shall provide priority treatment to the affected signalling when MPS is activated for an MMTEL video call, or MMTEL video conference call.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.2.5 Media
|
The system shall provide priority treatment to the audio and video media flows, when MPS is activated for an MMTEL video call or MMTEL video conference call.
The system shall support a means to differentiate the priority between the audio and video streams of a given MPS MMTEL video call.
The system shall support a means to differentiate the priority between the audio and video streams of MPS participants (Service Users) on an MMTEL video conference call.
The system shall retain the audio of an MPS for MMTEL video call or MMTEL video conference call when both the audio and video cannot be supported but the audio can be supported.
The system shall support priority re-establishment of the video media when an MPS MMTEL video call, or an MPS MMTEL video conference call, is in progress with only audio media and the conditions which previously blocked the video media are no longer applicable.
NOTE: This requirement does not imply the need to introduce a new IMS feature. It adds the need for priority treatment using the existing IMS feature for re-establishment of the video media.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3 MPS for DTS
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.1 General
|
MPS for Data Transport Service (DTS) is a generic priority packet transport service that applies independently of the specific data application being used. It is a specific example of Priority Data Bearer Service described in clause 5.4a. MPS for DTS provides the Service User with priority for applications using the default bearer upon request (in the case of EPS), or QoS flow associated with the default QoS rule upon request (in the case of 5GS), to one or more selected active Packet Data Networks (PDNs)/Data Networks (DNs), in periods of severe network congestion during which normal commercial data service is degraded. MPS for DTS may also apply to other bearers (in the case of EPS) and other QoS Flows (in the case of 5GS) based on operator policy and regulatory rules.
NOTE 1: Service Data Flows (SDFs) previously mapped to the default bearer (in case of EPS) / QoS flow associated with the default QoS rule (in case of 5GS), are upgraded to MPS priority.
The system shall support:
- MPS for DTS for an authorized Service User using a UE with a subscription for MPS, and
NOTE 2: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
- MPS for DTS for an authorized Service User using a UE that does not have an MPS subscription.
NOTE 3: In this case, the Service User’s MPS subscription information (e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User borrows a UE that does not have an MPS subscription..
MPS for DTS may be used to by a Service User to obtain priority access (e.g., Virtual Private Network (VPN) access) to an enterprise network (e.g., a private corporate network or private Government Agency network to download data and/or access enterprise applications such as email, text/chat/presence, voice and video).
The system shall support for an authorised Service User, an end-to-end MPS for DTS connection between the MPS subscribed UE and an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
NOTE 4: The end-to-end MPS for DTS connection between the UE and an associated enterprise network is supported either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
MPS for DTS provides an IoT device with subscription to MPS with priority for applications using a specific default bearer (in the case of EPS), or default QoS flow (in the case of 5GS), towards a single specified PDN/DN;in the case of IoT connectivity to an enterprise, MPS also provides priority for the terminating access network (connected to the enterprise).
The system shall support:
- MPS for DTS for an authorized IoT device with a subscription for MPS, and
- an end-to-end MPS for DTS connection between the MPS subscribed IoT device and an associated enterprise network supporting MPS on demand based on operator policy when agreements are in place for MPS.
NOTE 5: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for DTS through machine interactions that may not directly involve a human Service User.
An authorized enterprise network supporting MPS uses MPS for DTS to activate priority for remote MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network based on operator policy when agreements are in place for MPS.
The system shall support:
- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed UEs associated with the enterprise network on demand based on operator policy when agreements are in place for MPS, and
- for an authorized enterprise network supporting MPS, activation of MPS for DTS for remote MPS subscribed IoT devices associated with the enterprise network on demand based on operator policy when agreements are in place for MPS.
NOTE 6: MPS for DTS activation by an authorized enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.2 Invocation and revocation
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.2.1 Invocation
|
A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for a DTS session.
NOTE 1: MPS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL).
A Service User, using a UE with an MPS subscription, can invoke MPS to request priority during roaming, e.g., when the normal data sessions cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE with an MPS subscription to initiate MPS for DTS session when roaming within the home country and outside the home country.
NOTE 2: MPS for DTS invocation using a UE with an MPS subscription is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL) recognized by the visited PLMN.
A Service User, using a UE that does not have an MPS subscription, can invoke MPS for DTS to request priority, e.g., when the normal data session cannot be established, or to upgrade an already established normal data session to MPS.
The system shall support means for a Service User using a UE that does not have a subscription for MPS to initiate MPS for DTS.
NOTE 3: MPS for DTS invocation using a UE that does not have an MPS subscription is done using a predetermined method (e.g., by the Service User use of a predetermine URL address) and is outside the scope of 3GPP.
A Service User, using a UE with an MPS subscription, can invoke MPS for DTS to obtain priority for Virtual Private Network (VPN) access to an enterprise network (e.g., a Government Agency private enterprise network), e.g., when normal data session cannot be established or is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to initiate an MPS for DTS session to an associated enterprise network supporting MPS on demand based on operator policy and when agreements are in place for MPS.
NOTE 4: Invocation of MPS for DTS is done either using a web browser (e.g., use of a predetermined address (i.e., URL) in a web browser) or using a user-selectable option provided as part of the VPN client in the UE with an MPS subscription.
An IoT device with an MPS subscription can invoke MPS for DTS to request priority when normal data service is degraded.
The system shall support means for an IoT device with an MPS subscription to initiate an MPS for DTS session to an enterprise network supporting MPS.
NOTE 5: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for DTS in support of the data communication needs. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
An authorized enterprise network supporting MPS activates MPS for DTS to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal data service is unacceptable.
The 3GPP system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for DTS for the following cases:
- a specific MPS subscribed UE or IoT device, and
- a group of MPS subscribed UEs or IoT devices.
NOTE 6: MPS for DTS invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of DTS in IoT devices) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) may be responsible for determining whether or not to invoke MPS for DTS. The MPS specialized application allows invocation/revocation of the DTS through machine interactions that may not directly involve a human Service User.
The system shall support receiving and authenticating MPS for DTS invocation requests from authorized MPS Service Users via public non-3GPP networks.
NOTE 7: The intent of the above requirement is to allow an authorized MPS Service User to send a request via the Internet to establish an MPS for DTS session for one or more active PDNs/DNs of a UE.
The system shall support discovery and selection of active data connections upon receipt of an MPS for DTS invocation request by an authorized MPS Service User.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.2.2 Revocation
|
The system shall support means to release an MPS for DTS session for the cases:
- an MPS Service User using a UE with an MPS subscription,
- an MPS Service User using a UE that does not have an MPS subscription, and
- an IoT device with an MPS subscription.
The system shall support means for an authorized enterprise network supporting MPS to explicitly request to release an MPS for DTS session or group of MPS for DTS sessions while maintaining basic connectivity to the MPS subscribed UE(s) or IoT device(s).
The system shall support means for an MPS Service User to explicitly release an MPS for DTS session from a UE with an MPS subscription when roaming, including outside the home country.
If MPS for DTS is not explicitly revoked by the Service User or an IoT device, the system in the RPLMN shall automatically revoke MPS:
- upon UE detachment/deregistration (e.g., power down), or
- when all the connections pertaining to the MPS for DTS session are released (without explicit release of the MPS for DTS session).
The system shall automatically revoke MPS when the maximum allowed duration for an MPS for DTS session is reached.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.3 Authentication and authorization
|
The system shall support means to authenticate and authorize an MPS for DTS session request from a UE with an MPS subscription.
The system shall support means to authenticate and authorize a Service User request for an MPS for DTS session from a UE that does not have an MPS subscription.
NOTE 1: The method for authenticating and authorizing the Service User using a UE that does not have an MPS subscription is predetermined. As part of the authentication and authorization process, the Service User provides MPS credentials (e.g., PIN or security token) specifically assigned for the purpose of obtaining MPS from a UE that does not have an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize an MPS for DTS session.
NOTE 2: The method for authenticating and authorizing UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize an MPS for DTS session request from an IoT device with an MPS subscription.
The system shall support means to authenticate and authorise an enterprise network supporting MPS requesting activation of MPS for DTS for the following cases:
- a specific MPS subscribed UE or IoT device, and
- a group of MPS subscribed UEs or IoT devices.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.4 Signalling
|
The system shall provide priority treatment to the invocation signalling in the network once the MPS for DTS request is identified by the system.
The system shall support a means for MPS for DTS activation when normal data service is congested.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.5 Media
|
The system shall provide priority treatment to the affected media flows when an MPS for DTS session is activated.
The system shall provide priority treatment to the affected media flows when MPS for DTS is activated for the connection between an MPS subscribed UE or IoT device and an associated enterprise network supporting MPS.
NOTE: Both the MPS subscribed UE or IoT device and the enterprise network must be served by the same PLMN.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.6 QoS
|
The system shall be capable of supporting a set of default QoS characteristics for an active MPS for DTS session.
The system shall be capable of verifying authorization for a requested QoS modification to an active MPS for DTS session.
The system shall be capable of making authorized QoS modifications in support of MPS for DTS for all media traffic supported via the default bearer (in the case of EPS), or the default QoS flow (in the case of 5GS).
The system shall support means to allow a Service User to request QoS modifications for an active MPS for DTS session.
The system shall support means to provide a Service User with an indication that a requested QoS modification of an active MPS for DTS session was successful.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.3.7 Security
|
The system shall support security capabilities to verify an enterprise network's authorization to request MPS for DTS activation.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4 MPS for Messaging Services
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.1 General
|
MPS for Messaging provides priority for messaging services in periods of network congestion during which normal commercial messaging services are degraded.
The system shall support MPS priority for messaging services supported using IMS Messaging, SMS and/or MMS, or MSGin5G for an authorized Service User using a UE with a subscription for MPS.
NOTE 1: MPS for Messaging may make use of commercial messaging service offerings provided by the operator. However, the messaging service applications are not in scope.
NOTE 2: The MPS Service User might not know whether the messaging service is supported using IMS Messaging, SMS and/or MMS, or MSGin5G.
NOTE 3: SMS options in scope are SMS via NAS and SMS over IP (i.e., SMS over MAP and SMS over SGs are not in scope).
The system shall support MPS priority for messaging using SMS and/or MMS or MSGin5G for an authorized IoT device with a subscription for MPS.
NOTE 4: An MPS specialized application on the MPS subscribed IoT device is used to support MPS for Messaging through machine interactions that might not directly involve a human Service User.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.2 Invocation and revocation
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.2.1 Invocation
|
A Service User using a UE with an MPS subscription can activate MPS for Messaging to request priority, e.g., when the normal messaging service is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging.
NOTE 1: MPS for Messaging invocation is done using a predetermined method (e.g., by the Service User using a web browser to enter a predetermined address such as an URL or sending a message to the MPS operator to activate MPS for Messaging).
A Service User using a UE with an MPS subscription can invoke MPS for Messaging to request priority during roaming, e.g., when the normal messaging service is degraded.
The system shall support means for a Service User using a UE with an MPS subscription to activate MPS for Messaging when roaming within the home country and outside the home country.
NOTE 2: MPS for Messaging invocation is done using a predetermined method recognized by the visited PLMN.
An IoT device with an MPS subscription can invoke MPS for Messaging to request priority when normal messaging service is degraded.
The system shall support means for an authorized IoT device with an MPS subscription to activate MPS for Messaging.
NOTE 3: An MPS specialized application on the MPS subscribed IoT device is responsible for determining whether or not to invoke MPS for Messaging in support of the text communication needs. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
An authorized enterprise network supporting MPS activates MPS for Messaging to request priority for MPS subscribed UEs and MPS subscribed IoT devices associated with the enterprise network when normal messaging service is degraded.
The system shall support means for an authorized enterprise network supporting MPS to request activation of MPS for Messaging for the following cases:
- a specific MPS subscribed UE or MPS subscribed IoT device, and
- a group of MPS subscribed UEs or MPS subscribed IoT devices.
NOTE 4: MPS for Messaging invocation done by the enterprise network supporting MPS involves prearrangement and configuration (i.e., subscription arrangement identifying the enterprise network authorization for remote activation of MPS for Messaging) within the MPS Service Provider PLMN. For example, an MPS specialized application hosted in the enterprise network (e.g., IoT application server) might be responsible for determining whether or not to invoke MPS for Messaging. The MPS specialized application allows invocation/revocation of MPS for Messaging through machine interactions that might not directly involve a human Service User.
The system shall support receiving and authenticating MPS for Messaging invocation requests from authorized MPS Service Users using UEs with an MPS subscription and authorized IoT devices with an MPS subscription via public non-3GPP networks.
NOTE 4: The intent of the above requirement is to allow an authorized MPS Service User or authorized IoT device to send a request via the Internet to activate or enable MPS for Messaging.
Based on national/regional regulatory rules and operator policy, the system shall support means to activate:
- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
- MPS for Messaging and MPS for DTS together.
NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.2.2 Revocation
|
The system shall support means to revoke MPS for Messaging for the cases:
- a Service User using a UE with an MPS subscription, and
- an IoT device with an MPS subscription.
The system shall support means for an authorized enterprise network supporting MPS to explicitly request to revoke MPS for Messaging for a individual or group of MPS subscribed UEs or MPS subscribed IoT devices while maintaining basic connectivity to the MPS subscribed UE(s) or MPS subscribed IoT device(s).
The system shall support means for a Service User to explicitly revoke MPS for Messaging from a UE with an MPS subscription when roaming, including outside the home country.
If MPS for Messaging is not explicitly revoked by the Service User or IoT device, the system in the RPLMN shall automatically revoke MPS upon UE detachment/deregistration (e.g., power down).
The system shall support means for an authorized IoT device with an MPS subscription to revoke MPS for Messaging.
The system shall automatically revoke MPS when the maximum allowed duration for MPS for Messaging is reached.
Based on national/regional regulatory rules and operator policy, the system shall support means to revoke:
- MPS for Messaging separately from MPS for DTS described in clause 9.2, or
- MPS for Messaging and MPS for DTS together.
NOTE 5: The intent of the above requirement is to allow the MPS Service Provider flexibility to activate/revoke MPS for Messaging and MPS for DTS separately or in combination.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.3 Authentication and authorization
|
The system shall support means to authenticate and authorize an MPS for Messaging activation request from a UE with an MPS subscription.
The system shall support means for a visited PLMN, including a visited PLMN outside of the home country, to verify with the home PLMN that a UE is authorized for MPS, and to authorize MPS for Messaging.
NOTE 1: The MPS subscription related information is associated with the UE’s HPLMN subscription and is either stored in the UE and the HPLMN, or only in the HPLMN. In the case that the MPS subscription is stored in the UE, the UE’s membership in a special access class as per TS 22.011 [6] is used for EUTRAN access to the EPC and membership in Access Identity 1 as per TS 22.261 [7] is used for 5G (NR and E-UTRAN access to the 5GC). In the case where the MPS subscription is stored only in the HPLMN (5GC), the HPLMN (5GC) can provide MPS indication during the UE registration.
NOTE 2: The method for authenticating and authorizing a UE for MPS when roaming is based on operator policy and roaming agreements between the visited PLMN and home PLMN for MPS as per clause 5.8.
The system shall support means to authenticate and authorize an MPS for Messaging activation request from an IoT device with an MPS subscription.
The system shall support means to authenticate and authorise an enterprise network that supports MPS when it requests activation of MPS for Messaging for the following cases:
- a specific MPS subscribed UE or MPS subscribed IoT device, and
- a group of MPS subscribed UEs or MPS subscribed IoT devices.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.4 Signalling
|
The system shall provide priority treatment to the invocation signalling in the network once the MPS for Messaging request is identified by the system.
The system shall support a means for MPS for Messaging activation when normal messaging service is congested.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.5 Message origination and termination
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.5.1 IMS Messaging
|
When MPS for Messaging is authorized and activated for an originating UE with a subscription for MPS using IMS Messaging for the messaging service, the system shall provide:
- end to end priority treatment for point to point messages when the recipient(s) is using IMS Messaging regardless whether the recipient(s) have a subscription for MPS, and
- priority treatment for messages to/from the Message Service Center.
When MPS for Messaging is authorized and activated for a terminating UE with a subscription for MPS using IMS Messaging for the messaging service, the system shall provide priority treatment for all messages to/from the Message Service Center.
When a terminating network receives an incoming message with an MPS for Messaging indication, the message shall receive priority treatment in the terminating PLMN.
NOTE: End to end priority can be provided by the 3GPP system for the point to point messages when both the originating UE and the destination UE are using IMS Messaging service. When the originating UE is using IMS Messaging service but the destination UE is not using IMS Messaging service, priority treatment is provided by the 3GPP system only to/from the Message Service Center.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.5.2 SMS and MMS
|
When MPS for Messaging is authorized and activated for a UE or IoT device with a subscription for MPS using SMS or MMS for the messaging service, the system shall provide priority treatment for all messages to/from the Message Service Center.
NOTE 1: The SMS and MMS platforms and inter system aspects are outside 3GPP scope.
NOTE 2: The above requirement is not applicable for SMS over MAP and SMS over SGs.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.5.3 MSGin5G
|
When MPS for Messaging is authorized and activated for an originating UE or IoT device with a subscription for MPS using MSGin5G for the messaging service, the system shall provide:
- end to end priority treatment for point to point messages when the recipient(s) is using MSGin5G regardless whether the recipient(s) have a subscription for MPS, and
- priority treatment for messages to/from the Message Service Center.
When MPS for Messaging is authorized and activated for a terminating UE or IoT device with a subscription for MPS using MSGin5G for the messaging application service, the system shall provide priority treatment for all messages to/from the Message Service Center.
When a terminating network receives an incoming message with an MPS for Messaging indication, the message shall receive priority treatment in the terminating PLMN.
NOTE 1: End to end priority can be provided by the 3GPP system for the point to point messages when both the originating UE and the destination UE are using MSGin5G service. When the originating UE is using MSGin5G but the destination UE is not using MSGin5G, priority treatment is provided by the 3GPP system only to/from the Message Service Center.
NOTE 2: MSGin5G is only applicable to 5GS.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
9.4.8 Security
|
The system shall support security capabilities to verify an enterprise network's authorization to request MPS for Messaging activation.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10 Non-3GPP access
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1 MPS when access to the EPC/5GC is WLAN
|
MPS can be supported for MMTEL voice/video calls and data sessions when the access to the EPC/5GC is WLAN and the 3GPP system is used for the MPS authorization. In this case, MPS priority treatment can be provided by:
- both the WLAN access and the EPC/5GC (i.e., when the WLAN supports MPS), or
- only the EPC/5GC (i.e., when the WLAN does not support MPS).
The following subclauses provide requirements specific to WLAN access to EPC/5GC.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.1 MPS for MMTEL voice and video
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.1.1 General
|
For a UE with WLAN access to the EPC/5GC, the system shall support the requirements in clauses 9.1 and 9.2 for MMTEL voice and voice conference calls and MMTEL video and video conference calls by an authorized MPS Service User using
- a UE with a subscription for MPS, and
- a UE that does not have an MPS subscription.
The system shall support the requirements in clauses 9.1 and 9.2 for MPS for MMTEL voice and voice conference calls and MPS for MMTEL video and video conference calls terminating to a UE with WLAN access to the EPC/5GC regardless of the terminating UE subscription for MPS.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.1.2 Authentication and authorization
|
For a UE with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for MMTEL voice/video authorization based on the UE subscription information.
For a UE that does not have a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for MMTEL voice/video authorization based on Service User credentials not associated with the UE (e.g., a calling card number, PIN or security token).
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.1.3 WLAN Interworking
|
For a UE with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN:
- indication of MPS for MMTEL voice/video authorization,
- priority marking of transport parameters of MPS for MMTEL voice/video signalling and media, and
- QoS characteristics of MPS for MMTEL voice/video signalling and media.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.2 MPS for DTS
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.2.1 General
|
For a UE or IoT device with WLAN access to the EPC/5GC, the system shall support the requirements in clause 9.3 on MPS for DTS sessions for:
- an authorized Service User using a UE with a subscription for MPS,
- an authorized Service User using a UE that does not have an MPS subscription,
- an authorized IoT device with a subscription for MPS, and
- an authorized enterprise network activation of MPS for DTS for remote MPS subscribed UEs/IoT devices associated with the enterprise network.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.2.2 Authentication and authorization
|
For a UE or IoT device with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for DTS authorization based on the UE subscription information.
For a UE that does not have a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for DTS authorization based on Service User credentials not associated with the UE (e.g., a calling card number, PIN or security token).
For an authorized enterprise network that is activating MPS for DTS for a remote UE or IoT device with a 3GPP subscription for MPS, the system shall support MPS for DTS authorization based on the UE or IoT device subscription information.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.2.3 WLAN interworking
|
For a UE or IoT with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN:
- indication of MPS for DTS authorization,
- priority marking of transport parameters of MPS for DTS signalling and media, and
- QoS characteristics of MPS for DTS signalling and media.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.3 Void
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.4 MPS for Messaging services
| |
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.4.1 General
|
For a UE or IoT device with WLAN access to the EPC/5GC, the system shall support the requirements in clause 9.4 on MPS for Messaging supported using IMS Messaging, SMS and/or MMS, or MSGin5G.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.4.2 Authentication and authorization
|
For a UE or IoT device with a 3GPP subscription for MPS and with WLAN access to the EPC/5GC, the system shall support MPS for Messaging authorization based on the UE subscription information.
For an authorized enterprise network that is activating MPS for Messaging for a remote UE or IoT device with a 3GPP subscription for MPS, the system shall support MPS for Messaging authorization based on the UE or IoT device subscription information.
|
89ea20b01c703949b0169bf5d5287c1e
|
22.153
|
10.1.4.3 WLAN interworking
|
For a UE or IoT with WLAN access to the EPC/5GC, the 3GPP system shall support delivery of the following to the WLAN: - indication of MPS for Messaging authorization, - priority marking of transport parameters of MPS for Messaging signalling and media, and - QoS characteristics of MPS for Messaging signalling and media. Annex A (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New WI SP-37 SP-070576 - 22.146 - - Rel-8 - Raised to v.2.0.0 by MCC for approval as v.8.0.0 1.3.0 2.0.0 PRIOR SP-37 - - 22.146 - - Rel-8 - Raised to v.8.0.0 by MCC following SA#37 approval 2.0.0 8.0.0 PRIOR SP-40 SP-080305 S1-080438 22.153 0004 - Rel-8 D CR to TS 22.153 on applicability of MPS 8.0.0 8.1.0 PRIOR SP-40 SP-080310 S1-080727 22.153 0003 1 Rel-9 B CR to TS 22.153 on an optional service invocation method for MPS 8.0.0 9.0.0 ePRIOR SP-41 SP-080494 - 22.153 0006 1 Rel-9 A Trusted domain support 9.0.0 9.1.0 PRIOR SP-42 SP-080778 S1-084394 22.153 0007 3 Rel-9 F Correction to priority levels and networks 9.1.0 9.2.0 EPRIOR SP-42 SP-080778 S1-084365 22.153 0008 1 Rel-9 C Indication of MPS 9.1.0 9.2.0 EPRIOR SP-47 SP-100188 S1-100101 22.153 0011 - Rel-10 F Clarification of MPS Service Aspects - Video and Data Bearer service 9.2.0 10.0.0 TEI10 SP-47 SP-100188 S1-100458 22.153 0012 3 Rel-10 B Priority for data bearer services 9.2.0 10.0.0 TEI10 SP-49 SP-100580 S1-102180 22.153 0013 - Rel-10 B Priority for data bearer services 10.0.0 10.1.0 TEI10 SP-51 SP-110172 S1-110182 22.153 0014 2 Rel-11 F Clarifying PS to CS handover requirements for multimedia priority calls 10.1.0 11.0.0 TEI11 SP-52 SP-110376 S1-111413 22.153 0016 1 Rel-11 B Priority treatment for Network Management functions 11.0.0 11.1.0 TEI11 SP-52 SP-110376 S1-111414 22.153 0017 1 Rel-11 C Clarification of Priority Information 11.0.0 11.1.0 TEI11 2014-10 - - - - - - - Update to Rel-12 version (MCC) 11.1.0 12.0.0 2015-06 - - - - - - - Update to Rel-13 version (MCC) 12.0.0 13.0.0 SP-68 SP-150270 S1-151607 22.153 0019 3 Rel-14 C Additions to MPS description 12.0.0 14.0.0 MPS_Mods SP-68 SP-150270 S1-151540 22.153 0020 2 Rel-14 C MPS Policy Control 12.0.0 14.0.0 MPS_Mods SP-68 SP-150270 S1-151542 22.153 0021 2 Rel-14 C Priority in Advance of Service Invocation 12.0.0 14.0.0 MPS_Mods SP-69 SP-150537 S1-152174 22.153 0022 - Rel-14 F MPS exemption from load rebalancing 14.0.0 14.1.0 MPS_Mods SP-69 SP-150537 S1-152681 22.153 0024 3 Rel-14 F MPS priority during initial Attach 14.0.0 14.1.0 MPS_Mods SP-70 SP-150751 S1-154442 22.153 0025 1 Rel-14 F Addition of end-to-end-cases in general description 14.1.0 14.2.0 MPS_Mods SP-70 SP-150751 S1-154443 22.153 0026 1 Rel-14 F Clarification of high level MPS requirements. 14.1.0 14.2.0 MPS_Mods SP-70 SP-150751 S1-154444 22.153 0027 1 Rel-14 F Fix inconsistent requirements on invocation of MPS priority. 14.1.0 14.2.0 MPS_Mods SP-70 SP-150751 S1-154445 22.153 0028 1 Rel-14 B MPS security requirements 14.1.0 14.2.0 MPS_Mods SP-71 SP-160097 S1-160332 22.153 0029 1 Rel-14 F Text alignment for terminating UE option 14.2.0 14.3.0 MPS_Mods SP-71 SP-160097 S1-160333 22.153 0030 1 Rel-14 F Update to Priority Data Bearer Service 14.2.0 14.3.0 MPS_Mods SP-71 SP-160097 S1-160334 22.153 0031 1 Rel-14 B MPS Anonymity Requirement 14.2.0 14.3.0 MPS_Mods SP-72 SP-160356 S1-161096 22.153 0032 Rel-14 D Editorial Corrections 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161097 22.153 0033 Rel-14 F Update to Handover Materials 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161099 22.153 0035 Rel-14 F Update on Number of Priority Levels 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161102 22.153 0038 Rel-14 F Clarification of CS Domain Interworking 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161442 22.153 0036 1 Rel-14 F Alignment of requirement for priority before service invocation 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161443 22.153 0037 1 Rel-14 F MPS priority for CS fallback 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161445 22.153 0040 1 Rel-14 F Correction of MPS Roaming Requirement 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161558 22.153 0039 3 Rel-14 B QoS for MPS 14.3.0 14.4.0 MPS_Mods SP-72 SP-160356 S1-161559 22.153 0034 2 Rel-14 B Service code for MPS 14.3.0 14.4.0 MPS_Mods 2018-06 - - - - - Rel-15 - Raised to Rel-15 by MCC 14.4.0 15.0.0 - 2019-09 - - - - - Rel-16 - Created by MCC due to Rel-17 CR#0041 and 42 15.0.0 16.0.0 - Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2019-09 SA#85 SP-190867 0041 3 B Common MPS Voice, Video and Data updates based on TR 22.854, MPS Phase 2 Feasibility Study 17.0.0 2019-09 SA#85 SP-190806 0042 2 B MPS service specific updates based on TR 22.854, MPS Phase 2 Feasibility Study 17.0.0 2019-12 SA#86 SP-191018 0044 1 D Editorial clean-up to close out MPS Phase 2 additions 17.1.0 2019-12 SA#86 SP-191018 0045 3 B Attestation of Authorized MPS Priority Markings 17.1.0 2019-12 SA#86 SP-191018 0046 1 B Addition of requirements to upgrade an established MMTEL voice call to MPS 17.1.0 2019-12 SA#86 SP-191018 0043 3 F Clarifications on MPS2 requirements and terminology 17.1.0 2020-12 SA#90e SP-201027 47 0 D Editorial Cleanup of MPS Phase 2 Additions 17.2.0 2020-12 SA#90e SP-201027 48 1 F Alignment of descriptive text with associated requirement for MPS invocation from a non-subscribed UE 17.2.0 2021-09 SA#93e SP-211072 0049 1 B MPS when access to EPC/5GC is WLAN (MPS_WLAN) 18.0.0 2021-09 SA#93e SP-211039 0050 1 B Fallback in 5GS 18.0.0 2021-12 SP-94 SP-211492 0052 1 D Editorial correction of reference (Rel-18 Mirror) 18.1.0 2021-12 SP-94 SP-211492 0054 1 F MPS for DTS description alignment (Rel-18 Mirror) 18.1.0 2021-12 SP-94 SP-211501 0055 1 B MPS and Supplementary Services Interactions 18.1.0 2022-09 SA#97 SP-220940 0056 1 B MPS for Messaging services 19.0.0 2023-06 SA#100 SP-230531 0060 A Correction to MPS requirements 19.1.0 2023-06 SA#100 SP-230532 0061 1 B MPS for Messaging when access is WLAN 19.1.0 2023-06 SA#100 SP-230535 0062 2 B Multiple Access Technologies 19.1.0 2024-09 SA#105 SP-241143 0065 1 A MPS Subscription Alignment 19.2.0 2024-09 SA#105 SP-241143 0070 A Editorial Correction 19.2.0
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
1 Scope
|
The present document provides Stage 1 normative service and performance requirements for diverse service enablers to enhance XR-based services. The term 'metaverse' in the title of the present document embraces the broader implications of AR and VR.
Service enablers considered in this document include:
- Localized mobile metaverse service functionality;
- Avatar-based real-time communication functionality;
- Digital asset management functionality;
- Operation efficiency, exposure, coordination of mobile metaverse services.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) Multimedia core network Subsystem (IMS)".
[3] ITU-T Recommendation Y.3090 (02/22): "Digital twin network - Requirements and architecture" (https://www.itu.int/rec/T-REC-Y.3090-202202-I).
[4] 3GPP TS 22.101: "Service principles".
[5] ITU-T Recommendation F.703 (11/00): "Multimedia conversational services".
[6] European Commission: "Shaping Europe's digital future", https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/shaping-europe-digital-future_en.
[7] 3GPP TS 22.261: "Service requirements for the 5G system".
[8] 5GAA: "C-V2X Use Cases Volume II: Examples and Service Level Requirements", 5G Automobile Association White Paper, https://5gaa.org/wp-content/uploads/2020/10/5GAA_White-Paper_C-V2X-Use-Cases-Volume-II.pdf <accessed 02.09.22>.
[9] O. Holland et al.: "The IEEE 1918.1 "Tactile Internet" Standards Working Group and its Standards," Proceedings of the IEEE, vol. 107, no. 2, Feb. 2019."
[10] A. Ebrahimzadeh, M. Maier and R. H. Glitho: "Trace-Driven Haptic Traffic Characterization for Tactile Internet Performance Evaluation," 2021 International Conference on Engineering and Emerging Technologies (ICEET), 2021, pp. 1-6.
[11] Quote from Ursula von der Leyen, President of the European Commission, in her State of the Union address, 16 September 2020: <https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-digital-identity_en>, accessed 16 November 2023.
[12] "European Digital Identity", European Commission: <https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-digital-identity_fr>, accessed 16 November 23.
[13] glTF 2.0 specification, https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html, last accessed 14 Nov. 2023.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
3 Definitions of terms, symbols and abbreviations
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
avatar: a digital representation specific to media that encodes facial (possibly body) position, motions and expressions of a person or some software generated entity.
Conference: An IP multimedia session with two or more participants. Each conference has a "conference focus". A conference can be uniquely identified by a user. Examples for a conference could be a Telepresence or a multimedia game, in which the conference focus is located in a game server.
NOTE 1: This definition was taken from 3GPP TS 22.228 [2].
Conference Focus: The conference focus is an entity which has abilities to host conferences including their creation, maintenance, and manipulation of the media. A conference focus implements the conference policy (e.g., rules for talk burst control, assign priorities and participant’s rights).
NOTE 2: This definition was taken from 3GPP TS 22.228 [2].
digital asset: digitally stored information that is uniquely identifiable and can be used to realize value according to their licensing conditions and applicable regulations. Examples of digital assets include digital representation (avatar), software licenses, gift certificates, tokens and files (e.g., music files) that have been purchased. This is not an exhaustive list of examples.
digital representation: the mobile metaverse media associated with the presentation of a particular virtual or physical object. The digital representation could present the current state of the object. One example of a digital representation is an avatar, see Annex A.
digital twin: A real-time representation of physical assets in a digital world.
NOTE 3: This definition was taken from ITU-T Recommendation Y.3090 [3].
digital wallet: one type of digital asset container, also known as e-wallet or mobile wallet. It is a software application that securely stores digital credentials typically part of personal data, such as payment information, loyalty cards, tickets, and other digital assets. It allows users to make electronic transactions, such as payments and transfers, conveniently and securely using their digital credentials.
NOTE 4: Digital wallets typically employ encryption and authentication mechanisms to protect the stored information and ensure the security of transactions.
gesture: a change in the pose that is considered significant, i.e., as a discriminated interaction with a mobile metaverse service.
immersive: a characteristic of a service experience or AR/MR/VR media, seeming to surround the user, so that they feel completely involved.
localization: A known location in 3 dimensional space, including an orientation, e.g., defined as pitch, yaw and roll.
location related service experience: user interaction and information provided by a service to a user that is relevant to the physical location in which the user accesses the service.
location agnostic service experience: user interaction and information provided by a service to a user that has little or no relation to the physical location in which the user accesses the service. Rather the service provides interaction and information concerning either a distant or a non-existent physical location.
mobile metaverse media: media communicated or enabled using the 5G system including audio, video, XR (including haptic) media, and data from which media can be constructed (e.g., a 'point cloud' that could be used to generate XR media.)
mobile metaverse: the user experience enabled by the 5G system of interactive and/or immersive XR media, including haptic media.
mobile metaverse server: an application server that supports one or more mobile metaverse services to a user access by means of the 5G system.
mobile metaverse service: the service that provides a mobile metaverse experience to a user by means of the 5G system.
pose: the relative location, orientation and direction of the parts of a whole. The pose can refer the user, specifically used in terms of identifying the position of a user's body. The pose can also also refer to an entity or object (whose parts can adopt different locations, orientations, etc.) that the user interacts with by means of mobile metaverse services.
service information: this information is out of scope of standardization but could contain, e.g., a URL, media data, media access information, etc. This information is used by an application to access a service.
spatial anchor: an association between a location in space (three dimensions) and service information that can be used to identify and access services, e.g., information to access AR media content.
spatial map: A collection of information that corresponds to space, including information gathered from sensors concerning characteristics of the forms in that space, especially appearance information.
spatial mapping service: A service offered by a mobile network operator that gathers sensor data in order to create and maintain a Spatial Map that can be used to offer customers Spatial Localization Service.
spatial localization service: A service offered by a mobile network operator that can provide customers with Localization.
User Identifier: a piece of information used to identify one specific User Identity in one or more systems.
NOTE 5: This definition was taken from 3GPP TS 22.101 [4].
User Identity: information representing a user in a specific context. A user can have several user identities, e.g., a User Identity in the context of his profession, or a private User Identity for some aspects of private life.
NOTE 6: This definition was taken from 3GPP TS 22.101 [4].
User Identity Profile: A collection of information associated with the User Identities of a user.
NOTE 7: This definition was taken from 3GPP TS 22.101 [4].
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AI Artificial Intelligence
CCTV ClosedCircuit TeleVision
DoF Degrees of Freedom
DVE Distributed Virtual Environment
FACS Facial Action Coding System
FOV Field Of View
LiDAR Light Detection And Ranging
MR Mixed Reality
VRU Vulnerable Road User
XR eXtended Reality
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
4 Overview
|
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 immersive 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. The present document uses this term to refer to a shared, perceived set of interactive perceived spaces that can be persistent.
In addition to services that offer location-independent user experiences, this feature also considers 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 located where specific services are offered.
The present document focuses on how to make these services function well, consistently and with diverse support mechanisms over mobile telecommunications networks.
Requirements for diverse service enablers are introduced to the 5G system to support these services, including avatar call functionality, coordination of mobile metaverse services, digital asset management and support for spatial anchors.
5. Functional service requirements
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.1 General requirements
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.1.1 Operational efficiency, exposure, and coordination
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.1.1.1 Description
|
These capabilities whose service requirements are defined in clause 5.1.1.2 enable diverse mobile metaverse services.
One important class of services involves several users who take part in mobile metaverse services simultaneously, for example, to support a 'virtual sport event' where some of the environment or objects in the match are virtual, that is, they are produced by an application that provides the user with XR media. Users could be local (in the same location) or remote and have a service experience that is immersive and meets the expectations set by the interactive activity.
Another important class of services are those that require coordination of diverse service data flows of sensor data and media in order to satisfy the needs of a digital twin or situational awareness service.
The service requirements in this clause correspond to means by which the 5G system provides access to digital assets and communication services for mobile metaverse services so that:
- the service experience of users of the same service are compatible and consistent;
- the service experience of a user involving media from different services is consistent, even when these services have different performance characteristics;
- the services can operate over a sufficient duration for devices with constrained energy storage;
- the services can communicate efficiently to a large number of authorized users;
- the communication performance for specific mobile metaverse services to specific users can be monitored and exposed to third parties.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.1.1.2 Requirements
|
[R-5.1.1-001] Subject to operator policy, the 5G system shall support a mechanism that enables flexible adjustment of communication services based on e.g., the type of devices (e.g., wearables), or communication duration (e.g., more than one hour), such that the services can be operated with reduced energy utilization.
NOTE 1: Metaverse service experience over an extended period of time (e.g., 2h) requires significant power consumption by the UE. In some cases, a device with no external power supply cannot sustain downloading and rendering of media over a long interval, e.g., for the duration of an entire feature film or athletic event.
[R-5.1.1-002] The 5G system shall provide a means to associate and coordinate data flows related to one or multiple UEs e.g., associated with the same object in digital twin applications provided by the mobile metaverse service.
[R-5.1.1-003] Subject to operator policy, regulatory requirements and user consent, the 5G system (including IMS) shall be able to expose network performance information (e.g., observed or predicted bitrate, latency or packet loss) related to one or more users to an authorized third party metaverse application.
NOTE 2: The network performance information can be per UE and can take into account all available access network types, i.e., 3GPP and non-3GPP.
[R-5.1.1-004] Subject to operator policy, the 5G system (including IMS) shall support a mechanism, including enabling one or more authorized third party(ies) to coordinate multiple service data flows of a single mobile metaverse service delivered to/from one or more UE(s). Multiple UEs may be associated with one user/location or different users at different locations potentially using different access networks, i.e., 3GPP and non-3GPP.
NOTE 3: Coordination refers to the ability to provide an acceptable level of user experience for a given service, e.g., based on latency and synchronization constraints (due to multiple sources or long distance between UEs/users). This can be based on a quantitative bound.
NOTE 4: It is not assumed that it is always possible to coordinate and provide the same capabilities regardless of whether 3GPP or non-3GPP access is used.
[R-5.1.1-005] The 5G system shall enable the coordination of diverse media, transmitted to a UE from one or more mobile metaverse services associated with a physical location, to be combined to form a localized service experience.
[R-5.1.1-006] Subject to operator policy, the 5G system shall support exposure mechanisms enabling an authorized third party to determine one or more subscribers to whom mobile metaverse media can be distributed in a resource efficient manner.
[R-5.1.1-007] Subject to operator policy and user consent, the 5G system shall support a means to provide resource efficient communication of third party mobile metaverse media to one or more subscribers.
[R-5.1.1-008] The 5G system shall provide a means to maintain consistent user experience, for a given UE, when XR media from different mobile metaverse services have different communication performance, e.g., resolution, latency or packet loss.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2 Specific functional areas
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.1 Localized mobile metaverse service
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.1.1 Description
|
Localized mobile metaverse services are immersive and integrated into a user's ordinary experiences. Such service experiences are location-related and can include presentation of AR, MR media.
Localized experiences are effectively present in the user's environment, so that the mobile metaverse media provided for a given mobile metaverse service is both appropriate to and integrated with both the physical world and with mobile metaverse media content displayed. Localized mobile metaverse services can be associated with specific places (3D locations in the physical world). The association between these places and service information is termed a spatial anchor.
Spatial anchors enable mobile metaverse services to be discovered and accessed, if the user is authorized. For example, the service information can convey the mobile metaverse server access information. When the user's application accesses the mobile metaverse service, the media associated with the service can be obtained by the user.
Figure 5.2.1.1-1: Services offering relevant information are anchored in space
Spatial anchors can associate diverse information with spatial location, beyond access control and access information of mobile metaverse services. Type of service information can also allow a user to discover appropriate spatial anchors, e.g., when the user seeks restaurants.
Spatial anchors can be defined by third parties, e.g., service providers, to offer relevant localized services, e.g., associated with specific items or features in their place of business. This information and its associated authorization information, determining who can discover the spatial anchor, can be managed - created, deleted and modified.
Users' localization is important in order to discover spatial anchors. The 5G system offers a spatial localization service to determine this information. Using sensor data related to the user's location, the 5G system can identify where the user is. This is possible by means of processing the sensor data as well as a spatial map. The result, precise user location and orientation in space, can be exposed to authorized third parties.
The spatial map is created using processed sensor data. The 5G system supports a spatial mapping service to customers that, for example, want to offer mobile metaverse services associated with spatial anchors on their premises. Creation of a spatial map for a location makes localization there possible, as well as assignment of spatial anchors in that location.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.1.2 Requirements
|
[R-5.2.1-001] Subject to operator policy, the 5G system shall provide a means to define and expose to an authorized third party a spatial anchor, i.e., an association between a physical location (a point or volume in three-dimensional space) and service information.
NOTE 1: Service information can include information to enable users to discover and access services, e.g., type of service, URLs, configuration data, the distance between the user and the spatial anchor, etc.
[R-5.2.1-002] Subject to operator policy, the 5G system shall enable an authorized third party to request the information associated with a specific spatial anchor.
NOTE 2: How the service and location information is used by the third party to access a mobile metaverse server and the AR media itself is out of scope of this requirement.
[R-5.2.1-003] Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide a means for a UE to provide sensor data (e.g., from UE sensors, cameras, etc.) to the network in order to derive localization information, e.g., to produce or modify a spatial map or discover or find spatial anchors. The 5G system shall enable an authorized third party to obtain all the spatial anchors in a given three dimensional area.
NOTE 3: How an authorized third party identifies which three-dimensional area to request spatial anchors in is not in scope of the 3GPP standard. Spatial localization and mapping information could be used to identify areas of interest.
[R-5.2.1-004] Subject to operator policy and regulatory requirements, the 5G system shall support mechanisms to expose a spatial map or derived localization information to authorized third parties.
[R-5.2.1-005] Subject to operator policy, regulatory requirements and user consent, the 5G System shall be able to process and expose information related to a UE's location and direction of orientation in space to authorized third parties.
NOTE 4: This requirement does not affect the ability of regulatory services, e.g., Lawful Interception service, to access required information without consent of the user.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.2 Avatar-based real-time communication
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.2.1 Description
|
A user can take part in mobile metaverse services that provide digital representations of several other users simultaneously, for example, to support a Conference using XR media. As these services are interactive and immersive, the 5G system provides a means so that the experience of each user of the same service is compatible and consistent. Users can participate together in this way, whether some of those in the Conference service are located in the same place: these users can experience remote users as AR or MR media. This media is conversational - meaning that all parties can participate, and real time - meaning that all users perceive each other's actions effectively simultaneously.
Avatars are employed in mobile metaverse services mainly to represent a user. To improve the user experience of this representation, the 5G system makes it possible to associate the user and the avatar representation and to expose this information to authorized third parties. This information could be valuable, as avatars can represent organizations, individual users, even groups of users.
The 5G system supports a means by which user's pose, gestures and expressions are captured as input for the conversational mobile metaverse service. Devices (e.g., UEs) can capture this information in a standardized form, which is used for the creation of an animated digital representation of the user (e.g., 3D avatar) that can be presented to other users. The system supports communication of this animated digital representation as "avatar media" as well as audio and other media as needed. The 5G system supports the creation of avatar media. Privacy and user consent is needed for sensor data used to capture a user's pose, gestures and (facial) expressions is sent from the UE to the network encoded as avatar media to be rendered.
The 5G system further supports predictive digital representation models in that it enables presentation of avatar media to users based upon timing and other information, so that information can be extrapolated or inferred even if it is not yet available from the network. Correction of these predictions is possible over time, as new information becomes available, e.g., from the real world. The 5G system can in this way enable the user experience of synchronized mobile metaverse services even where communication latencies (e.g., due to distance between users) do not permit this.
Capabilities of UEs differ. For example: some UEs can render avatar media, others video, others only text. To support interactive avatar communication, media transcoding can occur in the 5G network. Similarly, the display capabilities of UEs also differ. Avatar, video or text data can be transcoded as appropriate to be displayed to the user.
Capabilities of users also vary. To support accessibility for those with disability due to physical (e.g., impaired hearing, sight, etc.), environmental (e.g., in a noisy environment), conversational media can be transcoded. This is consistent with the objective for Total Conversation [5], clause 4.5. Avatar functionality provides new options, as media can be transcoded to and from an avatar call.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.2.2 Requirements
|
[R-5.2.2-001] The 5G system shall support 5G CN to provide real-time feedback in support of conversational XR communication among multiple users simultaneously.
NOTE 1: The feedback can include information such as network condition and achieved QoS. Such information can be used by the IMS, for example, to trigger the codec negotiation.
[R-5.2.2-002] Subject to operator policy and user consent, the 5G system (including IMS) shall support multimedia conversational communications between two or more users including transfer of real time avatar media and audio media.
NOTE 2: Avatar media can be transmitted on both uplink and downlink.
NOTE 3: Confidentiality of the data used to produce the avatar (e.g., from the UE cameras, etc.) is assumed.
[R-5.2.2-003] Subject to operator policy and user consent, the 5G system (including IMS) shall support change of media types between video and avatar media for parties of a multimedia conversational communication.
[R-5.2.2-004] Subject to operator policy, the 5G system (including IMS) shall support transcoding between media such as text, video and avatar media in multimedia conversational communications.
NOTE 4: Text, video or other media could allow a party to control the appearance of its avatar, e.g., to express behaviour, movement, affect, emotions, etc.
NOTE 5: The transcoding of media enables avatar communication, e.g., in scenarios in which UE participating in an IMS call or other service does not support e.g., FACS, encoding avatar media, generating avatar media, etc.
[R-5.2.2-005] Subject to operator policy, regulatory requirements and user consent, the 5G system (including IMS) shall support the capabilities of rendering the avatar based on the body movement information (e.g., body motion or facial expression) of a human user.
[R-5.2.2-006] Subject to operator policy, regulatory requirements and user consent, the 5G system (including IMS) shall support the encoding of sensor data capturing the facial expression and movement and gestures of a person, in a standard form.
[R-5.2.2-007] Subject to operator policy and regulatory requirements, the 5G system shall support mechanisms to uniquely identify an avatar, to associate the avatar with a subscriber and to expose this association to authorized third parties.
NOTE 6: As specified in clause 7.2.3, the subscriber that the avatar is associated with can temporarily authorize third parties to use the avatar.
[R-5.2.2-008] The 5G system (including IMS) shall support compensating for the end-to-end communication latency between the users and/or objects involved in a multimedia conversational communication during rendering the digital representation (e.g., avatar) of the users and/or objects involved (e.g., by using a predictive digital representation model).
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.3 Digital asset management
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.3.1 Description
|
Mobile metaverse services can depend upon information that is associated with the user, e.g., User Identifiers and personal data that are commonly required and represented in a machine-readable format. The requirements as described in 3GPP TS 22.101 [4] clause 26a apply for identification of users. These can be used to provide proof for regulatory constrained service, e.g., proof of residential address for services that are restricted to local residents.
Further, the services can benefit from common information, such as avatar parameters and configuration information, so that a user's digital representation is consistent across different applications. Users can benefit from the support of associating their digital assets with different User Identities, to flexibly control their stored information.
Finally, some more specific information used by different services can also be shared in different mobile metaverse services and be considered 'digital assets' in that the user needs or could benefit from having this information available when access mobile metaverse services. The 5G system provides a means to improve interoperability of the use of digital assets between the various metaverse platforms. For this, digital asset formats e.g., avatar format have to be adaptable and consistent with the characteristics and constraints of the service (e.g., performance, graphics). According to regulations, this information can be considered as personal data.
An example of such service is the EU digital wallet initiative [6]. Both the digital wallet and the digital asset management functionality described in the present document emphasize the need for security, privacy and control over access to authorized parties. This initiative is summarized in Annex B.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
5.2.3.2 Requirements
|
[R-5.2.3-001] Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to provide functionality to store digital assets associated with a user, and to remove such digital assets associated with a user.
[R-5.2.3-002] Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide a means to allow a user to securely access and update their digital assets.
[R-5.2.3-003] Subject to operator policy and user consent, the 5G system shall be able to allow an authorized third party to retrieve the digital asset(s) associated with a user, e.g., when the user accesses a specific application.
NOTE 1: When a user accesses an immersive mobile metaverse service, the authorized third party (service provider) could obtain relevant digital assets of a user associated with that service.
[R-5.2.3-004] The 5G system (including IMS) shall support at least one common avatar format to enable interoperability with multiple immersive mobile metaverse services.
[R-5.2.3-005] The 5G system shall be able to associate a stored digital asset with one or more User Identities.
[R-5.2.3-006] Subject to operator policy, regulatory requirements and user consent, the 5G system shall support a mechanism for users to define conditions (e.g., based on user location information) to restrict the access to, and management of, stored digital assets associated with User Identity.
[R-5.2.3-007] The 5G system shall support mechanisms to request specific formats of stored digital assets associated with a user by an authorized mobile metaverse service.
NOTE 2: The main use case considered during development of this requirement was that stored digital assets such as avatar representation can be provided at different levels of graphical accuracy.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
6 Performance requirements
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
6.1 Description
|
The performance requirements shown in table 6.2-1 feature exemplary use cases of mobile metaverse services that require communication services with specific performance levels.
5G-enabled Traffic Flow Simulation and Situation Awareness is a use case in which the real conditions of a road including vehicles and other factors are captured with sensors, modelled in a simulation and used to provide guidance for vehicles and users for efficiency and safety. This is a specific example of a broad category of 'situational awareness' services that capture 'virtual representations' of the real world to then advise or control actions taken in the real world.
Collaborative and concurrent engineering is a form of Conference in which multiple users participate, both together at the same site and remotely, to interact with virtual and physical objects collectively. The use case considers audio, video and haptic interaction.
Metaverse-based Tele-Operated Driving is a use case that enables remote user actuation of equipment, specifically remote-controlled driving in a hazardous environment. The interaction of the user and the remote equipment is facilitated by a digital twin representing the vehicle and the environment it operates in. The status of the digital twin is determined by sensors in the vehicle's vicinity and carried by the vehicle.
The performance requirements for other AR/VR/XR services are included in 3GPP TS 22.261 [7] including:
- clause 7.6.1 AR/VR;
- clause 7.11 KPIs for tactile and multi-modal communication service.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
6.2 Performance requirements
|
[R-6.2-001] The 5G system shall support various mobile metaverse services with the following KPIs.
NOTE: Unless stated otherwise, the "Max allowed end-to-end latency" refers to the maximum transmission delay expected between a UE and the mobile metaverse server or vice-versa.
Table 6.2-1: Performance requirements for Mobile Metaverse Services
Use Cases
Characteristic parameter (KPI)
Influence quantity
Remarks
Max allowed end-to-end latency
Service bit rate: user-experienced data rate
Reliability
Area Traffic capacity
Message size (byte)
Transfer Interval
Positioning accuracy
UE Speed
Service Area
5G-enabled Traffic Flow Simulation and Situational Awareness
(NOTE 2)
[5-20] ms (NOTE 1)
[10~100] Mbit/s
[8]
(NOTE 6)
> 99.9%
1.14 Tbit/s/km2
(NOTE 5)
-
20~100 ms
(NOTE 3)
-
< 250 km/h
City or Country wide
(NOTE 4)
UL
Collaborative and concurrent engineering
[≤10] ms
[9]
(NOTE 7)
[1-100] Mbit/s
[9]
[> 99.9%]
[9]
[1.55] Tbit/s/km2
(NOTE 8)
Video: 1500
Audio: 100
[9]
-
-
Stationary or Pedestrian
typically
< 100 km2
(NOTE 9)
UL and DL audio/video
[5] ms UL
[1-50] ms DL
[9]
(NOTE 7)
[<1] Mbit/s
[9]
[> 99.9%] (without compression)
[> 99.999%] (with compression (NOTE 10))
[10]
[2.25] Tbit/s/km2
(NOTE 8)
1 DoF: 2-8
3 DoFs: 6-24
6 DoFs: 12-48
[9]
0.25-10 ms
[9]
UL and DL haptic feedback
Metaverse-based Tele-Operated Driving
(NOTE 16)
[100] ms
[8]
(NOTE 11)
[10~50] Mbit/s
[8]
99%
[8]
[~360] Mbit/s/km2
(NOTE 14)
-
20~100 ms [8]
(NOTE 12)
[10] cm
[8]
[10-50] km/h (vehicle)
[8]
Stationary or Pedestrian
Up to 10 km radius
[8]
(NOTE 13)
UL real-time vehicle data (video streaming and/or sensor data)
[8]
[20] ms
[8]
[0.1~0.4] Mbit/s
[8]
99.999%
[8]
[~4] Mbit/s/km2
(NOTE 14)
Up to 8Kb
[8]
20 ms
[8]
(NOTE 12)
[10] cm
[8]
[10-50] km/h (vehicle)
[8]
Stationary or Pedestrian
Up to 10 km radius
[8]
(NOTE 13)
DL control traffic (commands from the remote driver)
[8]
1-20 ms
(NOTE 15)
16 kbit/s -2 Mbit/s
(without haptic compression encoding);
0.8 - 200 kbit/s
(with haptic compression encoding)
(NOTE 15)
99.999%
(NOTE 15)
[~20] Mbit/s/km2
(NOTE 14)
2-8 (1 DoF) (NOTE 15)
Stationary or Pedestrian
Up to 10 km radius
[8]
(NOTE 13)
Haptic feedback
Viewports streaming from rendering device to AR glasses through direct device connection
(tethered/relaying case)
(NOTE 17)
10 ms (i.e., UL+DL between AR Glasses display and the rendering UE) (NOTE 18)
[200-2000] Mbit/s
99.9 %
(NOTE 18)
-
-
-
-
Stationary or pedestrian (between rendering device and AR glasses)
Up to direct device connection ranging
Immersive AR interactive experience: tethered link
Pose information from AR glasses to rendering device through direct device connection
(tethered/relaying case)
(NOTE 17)
5 ms
(NOTE 18)
[100-400] Kbit/s
(NOTE 18)
99.9 %
(NOTE 18)
-
-
-
-
Stationary or pedestrian (between rendering device and AR glasses)
Up to direct device connection ranging
Movie streaming from metaverse server to the rendering device
(NOTE 20)
Only relevant for live streaming.
[1-5] s in case of live streaming
[0.1-50] Mbit/s (i.e., covering a complete OTT ladder from low resolution to 3D-8K)
(NOTE 19)
99.9 %
-
-
-
-
Pedestrians and users in vehicles
-
Immersive AR interactive experience: NG-RAN multimodal communication link
Avatar information streaming between remote UEs (end to end)
10 ms (i.e., 20ms between both UEs excluding metaverse server processing time)
(NOTE 22)
[0.1-30] Mbit/s
(NOTE 21)
99.9 %
-
-
-
-
Pedestrians and users in vehicles
-
Interactive data exchange: voice and text between remote UEs (end to end)
(NOTE 22)
10 ms (i.e., 20ms between both UEs excluding metaverse server processing time)
[0.1-0.5] Mbit/s
99.9 %
-
-
-
-
Pedestrians and users in vehicles
-
NOTE 1: The mobile metaverse server receives the data from various sensors, performs data processing, rendering and provide feedback to the vehicles and users.
NOTE 2: Based on [8] and 3GPP TS 22.261 [7], typical data volume include 1) camera: 8 Mbit/s per sensor (unstructured), 2) LiDAR: 35 Mbit/s per sensor (unstructured), 3) radar: 160 Kbit/s per sensor (unstructured), and 4) real-time Status information including Telemetry data: [< 50 kbit/s] per sensor/vehicle/VRU (structured). Typical urban density [8] considers 120 vehicles and 220 users/smartphones (120 drivers + 100 VRU) present in an area of 40m*250m to actively enjoy immersive metaverse services for traffic simulation and traffic awareness.This further considers 2 cameras, 2 Radars, 2 LiDARs on road side per direction, which communicate with the same equipment at previous roadside infrastructure node, Estimated vehicle equipments are 7 cameras, 8 radar and 1 LiDAR for each vehicle.
NOTE 3: The frequency considers different sensor types such as Radar/LiDAR (10Hz) and camera (10~50Hz).
NOTE 4: The service area for traffic flow simulation and situational awareness depends on the actual deployment, for example, it can be deployed for a city or a district within a city or even countrywide. In some cases a local approach (e.g., the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
NOTE 5: The calculation is this table is done per one 5G network, in case of N 5G networks to be involved for such use case in the same area, this value can be divided by N.
NOTE 6: User experienced data rate refers to the data rate needed for the vehicle or human, the value is observed from industrial practice.
NOTE 7: The network based conference focus is assumed, which receives data from all the participants, performs rendering (image synthesis), and then distributes the results to all participants. As rendering and hardware introduce some delay, the communication delay for haptic feedback is typically less than 5ms.
NOTE 8: To support at least 15 users present at the same location (e.g., in an area of 20m*20m) to actively enjoy immersive Metaverse service concurrently, the area traffic capacity is calculated considering per user consuming non-haptic XR media (e.g., for video per stream up to 40000 kbit/s) and concurrently 60 haptic sensors (per haptic sensor generates data up to 1024 kbit/s).
NOTE 9: In practice, the service area depends on the actual deployment. In some cases a local approach (e.g., the application servers are hosted at the network edge) is preferred in order to satisfy the requirements of low latency and high reliability.
NOTE 10: The arrival interval of compressed haptic data usually follow some statistical distributions, such as generalized Pareto distribution, and Exponential distribution [10].
NOTE 11: The end-to-end latency does not include sensor acquisition or actuator control on the vehicle side, processing, and rendering on the user side (estimated additional 100ms total). Target e2e user experienced max delay depends on reaction time of the remote driver (e.g., at 50km/h, 20ms means 27cm of remote vehicle movement).
NOTE 12: UL data transfer interval around 20ms (video) to 100ms (sensor), DL data transfer interval (commands) around 20ms.
NOTE 13: The service area for teleoperation depends on the actual deployment; for example, it can be deployed for a warehouse, a factory, a transportation hub (seaport, airport etc.), or even a city district or city. In some cases, a local approach (e.g., the application servers are hosted at the network edge) is preferred to satisfy low latency and high-reliability requirements.
NOTE 14: The area traffic capacity is calculated for one 5G network, considering 4 cameras + sensors on each vehicle. Density is estimated to 10 vehicles/km2, each of the vehicles with one user controlling them. [8]
NOTE 15: KPI comes from 3GPP TS 22.261 [7] clause 7.11 “remote control robot” use case.
NOTE 16: Examples of typical data volume including 1) ~8Mbps video stream. Four cameras per vehicle (one for each side): 4*8=32Mbps. 2) sensor data (interpreted objects), assuming 1 kB/object/100 ms and 50 objects: 4 Mbps [8].
NOTE 17: These KPIs are only valid for cases where the viewport rendering is done in the tethered device and streamed down to the AR glasses. In the case of rendering capable AR glasses, these KPIs are not valid.
NOTE 18: These values are aligned with the tactile and multi-modal communication KPI table in TS 22.261 [7], clause 7.11.
NOTE 19: These values are aligned with “high-speed train” DL KPI from TS 22.261 [7] clause 7.1
NOTE 20: To leverage existing streaming assets and delivery ecosystem, it is assumed that the legacy streaming data are delivered to the rendering device, which incrusts this in the virtual screen prior to rendering. For a live streaming event, the user-experience end-to-end latency is expected to be competitive with traditional live TV services, typically [1-5] seconds.
NOTE 21: For example, the glTF format [13] can be used to deliver avatar representation and animation metadata in a standardized manner. Based on this format, the required bitrate for transmitting such data is highly dependent on avatar’s complexity (e.g., basic model versus photorealistic).
NOTE 22: These values are aligned with “immersive multi-modal VR” KPIs in TS 22.261 [7], clause 7.11.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7 Security, authorization and privacy
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.1 Description
|
Security and privacy requirements are important to consider in the context of the present document. Regulatory requirements and user consent are mentioned throughout, emphasizing the importance of data confidentiality. The requirements listed below identify specific capabilities needed for authorization to support functionality described in other clauses of the present document. These requirements supplement the general security requirements for the 5G system defined in 3GPP TS 22.261 [7].
This clause includes requirements that provide functionality to define and enforce authorization policies. These policies are articulated in the case of avatar-based real-time communication to provide users with the ability to define specific authorization rights to use avatars and multimedia communication services on behalf of a subscriber.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.2 Requirements
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.2.1 General
|
[R-7.2.1-001] Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to support mechanisms to expose to a trusted third party the result of the UE authenticating the user.
NOTE: How a UE authenticates the user's identity at the terminal equipment, e.g., using biometrics, is out of the scope of the present document.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.2.2 Localized mobile metaverse service
|
[R-7.2.2-001] Subject to operator policy, regulatory requirements and user consent, the 5G system shall support mechanisms to authorize Spatial Localization Service.
[R-7.2.2-002] Subject to operator policy, the 5G system shall provide an authorized third party a means to define authorization to access spatial anchor information and to manage the spatial anchor(s), e.g., add, remove or modify spatial anchors.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.2.3 Avatar-based real-time communication
|
[R-7.2.3-001] Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to authorize the avatar to be used in mobile metaverse services.
[R-7.2.3-002] Subject to operator policy, regulatory requirements, and user consent, the 5G system shall provide time-bound authorization for specified subscribers to use an avatar in mobile metaverse services.
[R-7.2.3-003] Subject to operator policy, regulatory requirements and user consent, the 5G system shall be able to identify the subscriber who has the right to use an avatar in mobile metaverse services.
[R-7.2.3-004] Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide a means to temporarily authorize a third party to use a subscriber's digital representation and access specific multimedia communication services on behalf of the subscriber, including not by means of a UE, with restrictive conditions e.g., authorized list of parties.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
7.2.4 Digital asset management
|
[R-7.2.4-001] Subject to operator policy, regulatory requirements and user consent, the 5G system shall provide secure means to authorize the use of digital assets associated with a user (e.g., digital assets belonging to a third party customer).
[R-7.2.4-002] The 5G system shall provide mechanisms to certify the authenticity of digital assets associated with a user.
|
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8 Charging aspects
| |
72a4e55cbcd7a63aa54799710b138216
|
22.156
|
8.1 Description
|
This clause gathers all charging requirements that apply to functionalities whose requirements are specified in other clauses of the present document.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.