hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
72a4e55cbcd7a63aa54799710b138216 | 22.156 | 8.2 Requirements | |
72a4e55cbcd7a63aa54799710b138216 | 22.156 | 8.2.1 Localized mobile metaverse service | [R-8.2.1-001] The 5G system shall be able to collect charging information for the actions related to spatial anchors, where a third party creates, deletes, or modifies a spatial anchor or associated service information.
NOTE: It is assumed that exposure of network anchors and associated service information can be a service provided by a network operator to third parties.
[R-8.2.1-002] The 5G system shall support the collection of charging information associated with the exposure of a spatial map or derived localization information to authorized third parties.
[R-8.2.1-003] The 5G system shall support the collection of charging information associated with the production or modification of a spatial map on behalf of an authorized third party.
[R-8.2.1-004] The 5G system shall support the collection of charging information associated with exposing spatial location service information to authorized third parties.
[R-8.2.1-005] The 5G system shall be able to collect charging information associated with distribution of third party mobile metaverse media to one or more subscribers. |
72a4e55cbcd7a63aa54799710b138216 | 22.156 | 8.2.2 Avatar-based real-time communication | [R-8.2.2-001] The 5G system shall support collection of charging information associated with initiating and terminating avatar call.
[R-8.2.2-002] The 5G system shall be able to collect charging information for transcoding services associated with avatar call. |
72a4e55cbcd7a63aa54799710b138216 | 22.156 | 8.2.3 Digital asset management | [R-8.2.3-001] The 5G system shall be able to collect charging information per UE or per application, related to the use of digital assets associated with a user (e.g., typically a human user with a certain subscription). [R-8.2.3-002] The 5G system shall be able to collect charging information per UE for managing the digital assets associated with a user (e.g., typically a human user with a certain subscription) or a third party. NOTE: A third party who has digital assets could be an enterprise customer having service level agreement with the operator. Annex A (informative): Mobile metaverse services A.1 Introduction This document defines the "mobile metaverse" as the user experience enabled by the 5G system of interactive and/or immersive XR media, including haptic media. For clarity and unambiguity with respect to many divergent technical and commercial developments, this document avoids the use of the term "metaverse" without qualification with the term "mobile". This annex provides background information for the present document and further explanation of the term mobile metaverse, and the services that it enables. The term mobile metaverse implies the combination of various technologies to fuse physical and digital worlds, widely impacting society and the economy. Users will access these mobile metaverse services with devices for interaction with XR media and sensors, enabled by mobile telecommunication standards. Mobile metaverse services are expected to be provided via many and diverse service providers, each catering to different customers, companies and communities. An entertainment company might provide one mobile metaverse service for consumers such as a virtual theme park, while offering a separate mobile metaverse service to its employees. Some providers may specialize in interactive tools to create content, while others present that content. In general, mobile metaverse services can be divided into three general categories: industrial, enterprise and consumer mobile metaverse services. There are commonalities among these categories. These mobile metaverse services will apply across these domains to varying degrees, sharing technologies, devices and interfaces, and functionalities described in this document. Ultimately, mobile metaverse services will be defined by the applications they enable and the business models they adopt. Besides "experiencing" virtual world and/or augmented real world media as a passive consumer (where the media is read-only), mobile metaverse services also can enable interaction, the user can "create" and even "control" elements of the media. Depending on the mobile metaverse service, the consequence of user interaction could be experienced by other users. As discussed below, in some cases, user interaction may result even in changes to the real world, through 'actuation' (remote control mechanisms) as discussed in clause A.4. Mobile metaverse services face technical challenges specific to the media and interactions they offer to users, in the context of mobile networks. Some of these technical challenges are addressed by mobile telecommunications standards, of which this document is a contribution. Another set of challenges are not technical in nature, such as regulatory and safety implications, only some of which are discussed in the present document. Other technical and non-technical challenges are expected to be addressed separately depending on the target environment/vertical. A.2 Consumer mobile metaverse services There has been some initial development of commercial consumer-oriented mobile metaverse services, specifically in metaverse gaming and VR social media 'virtual worlds'. Mobile metaverse consumer services considered during the study of mobile metaverse services relate to the following use cases: - Attending (live) VR events (sports, gaming, concerts, etc.) either as spectator or performer, including while moving / commuting; - Virtual shopping or visit experience (tourism, real estate, etc.); - Presentation of AR content on a virtual screen, e.g., a feature length movie; - Interaction with AR content in a location-aware manner, offering spatial localization and mapping to support applications generating AR content for enhanced localized experiences (e.g., in museums, shopping malls); - Situation awareness about the user's physical surroundings, while walking or driving; - Experience immersive communications with other entities - digital representations of users or application-generated content, including customer support services, by leveraging avatars, digital assets and wallets. A.3 Enterprise mobile metaverse services Remote working has driven demand for better collaboration and communication tools, and thanks to extended reality (XR) and virtual reality (VR) technologies, many of those tools contribute to the enterprise metaverse. The enterprise mobile metaverse will eventually envelop the core productivity applications that make business function, e.g., as a digital drafting tool for architecture and engineering, and training sessions via AR and/or VR. Eventually, the enterprise and industrial mobile metaverses will interlink, merging the IT systems in office branches with the Operational Technology (OT) systems of the shop floor. Main mobile metaverse enterprise services considered during the study of mobile metaverse services relate to the following use cases: - XR-enabled collaborative and concurrent engineering based on geospatial digital twins (and avatars), for research & prototyping, visual testing & simulation, planning & optimisation, which can further be used for training - Virtual showrooms, products or stores; - Interaction with AR content in a location-aware manner, e.g., creating spatial anchors and discovery of them for AR content enhanced in-store shopping experiences; A.4 Industrial mobile metaverse services Industrial mobile metaverse services are expected to provide cost, productivity, safety and flexibility gains. In particular, industrial OT systems begin to support mobile services that include XR media for monitoring and analysis, and also for control of operations through the digital orchestration of robot fleets or user-guided remote operations. Industrial users will gain the ability to visualize and reconfigure their operations, e.g., in response to changing supply and demand or disruptions. By fusing digital and physical realities, the digital twin has begun to transform many industries. Seaports have begun using digital twins to track every container on their docks. Aerospace companies design and build engines and fuselages virtually to simulate how an aircraft will fly and perform. Many new factories exist just as much digitally, as data and virtual representation, as they do in the physical world. This kind of mobile metaverse service aims at control and awareness of operations down to the smallest detail. Some of the mobile metaverse service enabler requirements support digital twin applications. Main mobile metaverse industrial services considered during the study of mobile metaverse services relate to the following use cases: - Remote critical health care, including surgery and treatment; - AR/VR based tele-operation of a remote device or vehicle (e.g., driving). A.5 Common aspects Common enablers associated with mobile metaverse services are virtual, augmented, mixed and other media (expressed collectively as extended reality, XR.) Whilst these are essential to the realization of the immersive experience of mobile metaverse services, they are not the only enabling functionalities. This document does not focus on XR media and media services per se, but rather identifies requirements for complementary enablers common to all mobile metaverses services, including: - Enabling localized (i.e., location-aware) mobile metaverse services by considering the essential mobility aspect of 5G connectivity, and collection and exposure of sensor data or 'results of processed sensor data' as needed by mobile metaverse services to integrate media into an immersive user's experience and expectations; - Enhancing real-time communications, including over IMS, with avatar-based capabilities, thus allowing more immersiveness in virtual reality, augmented reality, etc. user experiences; - Enhancing XR media delivery to make it possible to support user experience of multiple services simultaneously; - Securely storing, exposing and managing digital assets. Other key enablers of the metaverse implied by some immersive experiences relate to digital twins, defined in this document as "a real-time representation of physical assets in a digital world". With respect to the metaverse, “geospatial” digital twins relate to the concept of adding geospatial information to a digital twin, such as 3D models, precise location and temporal information – enabling for example holographic-type of object animation. The value proposition of geospatial Digital twins is about enabling immersive user experience, collaboration and simulations that are very close to what to expect in the real world by all 3 categories of mobile metaverse services. It is foreseen that additional functionalities will be defined in the future to provide capabilities to better offer and operate mobile metaverse services. Annex B (informative): The EU Digital Identity Wallet Initiative B.1 Overview This annex provides an example of a framework in which a digital asset management services can enable a diverse set of activity for individuals, including health care, commerce, e-government and any activity in which exchange of official documents is essential. This annex does not imply that the digital asset management capabilities specified in the present document can serve or fulfill the EU Digital Identity Wallet initiative goals, though this is not excluded. Rather, this annex provides an overview of the emergence of digital asset management as an essential means to act efficiently and effectively in an increasingly large set of activities. B.2 The Initiative The European Commission intends to establish a sovereign digital/digital identity as part of its digital transformation strategy [11]. While the digital wallet initiative is specific to Europe, the ideas behind it could be generally applicable. That is, to encourage and ease e-commerce, e-government and provide users with control over how their data is accessed, a digital wallet approach could have applicability and value in a broader international context. This digital identity [11] will allow by 2030 the citizens of the union to authenticate themselves to the main public services (or to some services of non-public companies), using a "wallet". This wallet will be an application that will store (in a secure way) a certain number of data and certified documents (identity card, driving license, certificates of personal qualities - like the majority -) in order to share them with the relevant services (e.g., school registration) securely. These solutions are meant to be compatible in all European countries. “Every time an App or website asks us to create a new digital identity or to easily log on via a big platform, we have no idea what happens to our data in reality. That is why the Commission will propose a secure European e-identity. One that we trust and that any citizen can use anywhere in Europe to do anything from paying your taxes to renting a bicycle. A technology where we can control ourselves what data is used and how." [6] The following indented text is a summary of a discussion of "European Digital Identity" [11]. The EU Digital ID Wallet is intended to allow European citizens to safely save their documents and personal information in a manner that complies with privacy regulations, as well as to give the data owners full control how the data is used (who can access it), and to track how it has been used. The information stored in the wallet could have general utility in many circumstances, even outside of the country in which the information was issued. Examples given are driver's licenses, medical records or certification such as university degree titles. It is acknowledged that people need to establish their identity in many ways. This process is currently complex, as each activity requires different credentials and as the form of credentials vary, identification requires different process. Having a single digital identity wallet will simplify these processes. The goal of the program is to bring the following benefits: - To support the ability of every person eligible for a national ID card to have a digital identity that is recognized anywhere in the EU; - To provide a simple and safe way to control how much information you want to hsare with services that require the sharing of information; - To allow mobile phone apps and other devices to support a means to - provide identity services on- and off-line; - store and exchange information provided by governments, e.g., name, surname, date of birth, nationality; - to use information as confirmation ofthe right to reside, work, or study in a particular member state. Today only 60% of the EU population in 14 Member States are able to use their national electronic ID (eID) beyond their own country. Only 14% of key public service providers across all Member states allow cross-border authenticaiton with an eID system, e.g., to prove a person's identity as part of authentication with a service accessed by means of the Internet without the need of a password.There are many situations where such identity information is needed, mainly during interaction with the government. For example, filing tax returns, changing one's address. Many other activities require identification, e.g., opening a bank account, renting a car, checking into a hotel, applying for a bank loan, etc. Various aspects of the intiative are of general interest for services offered over the internet, including: - Qualification of web sites and services, to ensure they are trustworthy and reliable. This could (partially) address threats such as phishing and illegitimate services; - An electronic signature framework, to express agreement to the content of a document; - A means to demonstrate that a set of data existed at a specific time, e.g., that a bill or fine was paid on time; - A 'seal of authenticity' that can be attached to digital content, such as football tickets, to avoid counterfeit in the digital domain. B.3 Example use cases Use cases include identification on public websites, but also for banking or medical services, education, mobility, etc. It generally involves making life easier for citizens and businesses by producing a framework of trust in the exchange of identity papers without the need for verification by physical meeting. The following indented text is a summary of a discussion of "European Digital Identity" [12]. Figure B.3-1: Example of use, applying for a bank loan [12] Benefits for the citizen: - Easy to identify itself - Management of identity information storage and usage permissions Benefits for businesses: - User-friendliness and compliance with user identification legislation. - Reduction in 'business integration requirements' for services, that currently has to contend with diverse documents and processes. Annex C (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 08.2023 SA1 103 S1-232605 TS skeleton 0.0.0 08.2023 SA1 103 S1-232074 S1-232406 S1-232407 S1-232076 S1-232623 S1-232419 S1-232620 S1-232412 S1-232421 S1-232080 S1-232422 Scope References Terminology & Acronyms Overview Localized mobile metaverse services Avatar-based real-time communication Digital asset management Performance requirements Security, authorization, privacy Charging aspects Annex - Metaverse 0.1.0 09.2023 SA#101 SP-231018 MCC clean-up 1.0.0 11.2023 SA1 104 S1-233431 S1-233152 S1-233438 S1-233433 S1-233146 S1-233434 S1-233158 S1-233442 cleanup numbering requirements Mobile metaverse service interconnection addition of KPI requirements Digital asset management Addition of Agreed Consolidated Requirements except for Digital Asset Management revising traffic flow KPIs Informative Annex on The EU Digital Identity Wallet Initiative 1.1.0 12.2023 SA#102 SP-231407 MCC clean-up 2.0.0 12.2023 SA#102 SP-231666 2nd MCC clean-up, this time based on S1-233528r2 when v.2.0.0 was based on S1-233528 2.1.0 12.2023 SA#102 - Approved at SA#102 19.0.0 2024-03 SA#103 SP-240202 0001 2 D Correction to Metaverse requirements 19.1.0 |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 1 Scope | The present document provides the service requirements for operation of the MCPTT Service. MCPTT makes use of capabilities included in Group Communications System Enablers and Proximity Services, with additional requirements specific to the MCPTT Service. The MCPTT Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specification do not apply to GSM or UMTS. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 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] TSB-102-B: "Project 25 TIA-102 Document Suite Overview".
[3] TIA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards".
[4] TIA-102.BABA: "Vocoder Description".
[5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6] 3GPP TS 22.468: "Group Communication System Enablers for LTE (GCSE_LTE)".
[7] ITU-T Recommendation P.862: "Perceptual evaluation of speech quality (PESQ): An objective method for end-to-end speech quality assessment of narrow-band telephone networks and speech codecs".
[8] ITU-T Recommendation P.862.1: "Mapping function for transforming P.862 raw result scores to MOS-LQO".
[9] ITU-T Recommendation P.863: "Perceptual objective listening quality assessment".
[10] TIA-102.BABG: "Enhanced Vocoder Methods of Measurement for Performance", March 2010.
[11] 3GPP TS 26.190: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Transcoding functions".
[12] 3GPP TS 26.194: "Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; Voice Activity Detector (VAD)".
[13] 3GPP TS 22.011: "Service accessibility".
[14] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Stations (MS) in idle mode".
[15] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)".
[16] ISBN 2-7461-1832-4: “UIC Project EIRENE System Requirements Specification”.
[17] ETSI EN 301 515 V3.0.0 (2018-03): “Global System for Mobile communication (GSM); Requirements for GSM operation on railways”. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 3 Definitions and abbreviations | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in 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 TR 21.905 [1]. Definitions provided in 3GPP TS 22.280 [15] also apply to this specification.
Affiliated MCPTT Group Member: An MCPTT Group Member who has indicated an interest in the group and is prepared to receive and/or transmit Group Communications from/to the particular MCPTT Group.
Automatic Commencement Private Call: A Private Call in which the initiation of the Private Call does not require any action on the part of the receiving MCPTT User.
Broadcast Group Call: A group call where the initiating MCPTT User expects no response from the other MCPTT Users, so that when his transmission is complete, so is the call.
Call Commencement Mode: This is a setting that determines the conditions under which a call is started.
Dispatcher: An MCPTT User who participates in MCPTT communications for command and control purposes.
Floor control: An arbitration system in an MCPTT Service that determines who has the authority to transmit (talk) at a point in time during an MCPTT call.
Group-Broadcast Group: A collection of groups defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
Group Regroup: The temporary combining of a multiplicity of groups into a single group.
Hang Time: A configurable maximum length of the inactivity (silence) period between consecutive MCPTT transmissions within the same call.
Imminent Peril Call: An urgent MCPTT Group call that highlights the potential of death or serious injury, but is less critical than an MCPTT Emergency Group Call. For example a call prioritized in the event of immediate threat to any human life such as resulting from an MCPTT User's observation of or engagement in a situation involving imminent peril to the general public (e.g., a forest fire about to encircle campers, tanker truck ready to explode near a school, casualties at the scene of a car bombing).
In-progress Emergency: An emergency condition for a group that has been accepted by the MCPTT Service, but has not yet been cancelled by an authorized user.
In-progress Imminent Peril: An imminent peril condition for a group that has been accepted by the MCPTT Service and has not yet been cancelled by an authorized MCPTT User.
Late call entry: An Affiliated MCPTT Group Member joins in an in progress MCPTT Group Call.
Location: The current physical location (i.e., co-ordinates plus estimated accuracy and timestamp) of the MCPTT UE that can be cross-referenced to a map.
Losing audio: Audio of an overridden talker that is routed to selected authorized MCPTT Users.
Manual Commencement Private Call: A Private Call in which the initiation of the Private Call requires the receiving MCPTT User to perform some action to accept or reject the Private Call setup.
MCPTT Administrator: An individual authorized to control parameters of the MCPTT Service for an organization including, for example, user and group definition, user/group aliases, user priorities, group membership/priorities/hierarchies, security and privacy controls.
MCPTT Emergency Alert: A notification from the MCPTT UE to the MCPTT Service that the MCPTT User has an emergency condition.
MCPTT Emergency Group Call: An urgent MCPTT Group call that highlights the potential of death or serious injury to the initiator.
MCPTT Emergency Private Call: An urgent MCPTT Private Call that highlights the potential of death or serious injury to the initiator.
MCPTT Emergency State: A heightened condition of alarm for an MCPTT User indicating a need for immediate assistance due to a personal life-threatening situation.
MCPTT Group: A defined set of MCPTT Users identified independently of transport or network type.
MCPTT Ad hoc Group: The combining of a multiplicity of MCPTT Users into a group based on pre-defined criteria for the duration of a communication.
MCPTT Group Member: An MCPTT User who has been authorized to participate in Group Communications of a particular MCPTT Group.
MCPTT Request: The action taken by an MCPTT User to request the permission to transmit voice on a call.
MCPTT Service: A Push To Talk communication service supporting applications for Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with fast setup times, high availability, reliability and priority handling.
MCPTT system: The collection of applications, services, and enabling capabilities required to provide Mission Critical Push To Talk for a Mission Critical Organization.
MCPTT UE: A UE that enables an MCPTT User to participate in MCPTT Service.
MCPTT User: A user of an MCPTT Service, who has a device with the capability to participate in MCPTT Services.
MCPTT User Profile: The set of information that allows an MCPTT User to employ the MCPTT Service in a given role and/or from a given MCPTT device.
Mission Critical Push To Talk: A group communication service with fast setup times, ability to handle large groups, strong security and priority handling.
Off-Network MCPTT Service: The collection of functions and capabilities required to provide MCPTT using ProSe Discovery and the ProSe Communication path for MCPTT Users using Public Safety ProSe-enabled UEs as a direct communication between UEs.
Partner MCPTT System: Allied MCPTT system that provides MCPTT Services to an MCPTT User based on the MCPTT User Profile that is defined in the Primary MCPTT System of that MCPTT User.
Pre-emption: The act of terminating on-going calls in order to free up resources for a higher priority call request.
Primary MCPTT System: MCPTT system where the MCPTT User Profile of an MCPTT User is defined.
Private Call: A call between a pair of MCPTT Users using the MCPTT Service with or without MCPTT Floor control.
Project 25 RFSS: A Project 25 Radio Frequency (RF) Subsystem as defined in TSB-102-B [2].
Receiving MCPTT Group Member: An Affiliated MCPTT Group Member who is currently receiving Group Communication from an MCPTT Group.
Selected MCPTT Group: The MCPTT Group that a particular Affiliated MCPTT Group Member uses for transmission.
System Call: A special case of a Broadcast Group Call that is transmitted to all users in a dynamically defined geographic area.
Transmitting MCPTT Group Member: An Affiliated MCPTT Group Member who is currently transmitting a Group Communication to a Selected MCPTT Group.
User-Broadcast Group: A collection of users defined by the MCPTT Administrator (e.g., representing a particular organizational structure) and intended to be the recipients of Broadcast Group Calls.
User ID: The main unique identifier for an MCPTT User.
User Regroup: The temporary combining of a multiplicity of users into a new group. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in 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 TR 21.905 [1].
FIFO First In First Out
GCSE_LTE Group Communication System Enablers for LTE
KPI Key Performance Indicator
MCPTT Mission Critical Push To Talk
MOS-LQO Mean Opinion Score – Listening Quality Objective
P25 Project 25
PESQ Perceptual Evaluation of Speech Quality
POLQA Perceptual Objective Listening Quality Assessment
ProSe Proximity Services
PTT Push To Talk
RFSS Radio Frequency (RF) Subsystem as defined in the TIA-102 specifications (P25)
TETRA Terrestrial Trunked Radio
TIA Telecommunications Industry Association
UIC Union Internationale des Chemins de Fer |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4 Mission Critical Push To Talk overview | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.1 General | A Push To Talk service provides an arbitrated method by which two or more users may engage in communication. Users may request permission to transmit (e.g., traditionally by means of a press of a button). The Mission Critical Push To Talk (MCPTT) service supports an enhanced PTT service, suitable for mission critical scenarios, based upon 3GPP system services. The requirements for Mission Critical Push To Talk (MCPTT) service defined within can also form the basis for a non-mission critical Push To Talk (PTT) service.
The MCPTT Service is intended to support communication between several users (a group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. However, the MCPTT Service also supports Private Calls between pairs of users. The MCPTT Service builds on the existing 3GPP transport communication mechanisms provided by the 3GPP architectures to establish, maintain, and terminate the actual communication path(s) among the users.
The MCPTT Service also builds upon service enablers: Group Communications System Enablers and Proximity Services. To the extent feasible, it is expected that the end user's experience to be similar regardless if the MCPTT Service is used under coverage of a 3GPP network or based on ProSe without network coverage. To clarify this intent, the requirements are grouped according to applicability to on-network use, off-network use, or both.
Though the MCPTT Service primarily focuses on the use of the 3GPP system there might be users who access the MCPTT Service through non-3GPP access technology, dispatchers and administrators are examples of this. Dispatchers and administrators are special users who have particular admin and call management privileges which normal users might not have. In MCPTT dispatchers can use an MCPTT UE (i.e., 3GPP) or a non-3GPP access connection to the MCPTT Service based on a "dispatcher and Administrator" interface. Through this interface a user is able to access and manage the services related to on the network and those common to on the network and off the network.
The MCPTT Service allows users to request the permission to talk (transmit voice/audio) and provides a deterministic mechanism to arbitrate between requests that are in contention (i.e., Floor control). When multiple requests occur, the determination of which user's request is accepted and which users' requests are rejected or queued is based upon a number of characteristics (including the respective priorities of the users in contention). MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. MCPTT Service also supports a mechanism to limit the time a user talks (hold the floor) thus permitting users of the same or lower priority a chance to gain the floor.
The MCPTT Service provides the means for a user to monitor activity on a number of separate calls and enables the user to switch focus to a chosen call. An MCPTT Service user may join an already established MCPTT Group call (Late call entry). In addition the MCPTT Service provides the User ID of the current speaker(s) and user's Location determination features.
The users of an MCPTT Service may have more stringent expectations of performance than the users of a commercial PTT service.
MCPTT is primarily targeting to provide a professional Push To Talk service to e.g., public safety, transport companies, utilities or industrial and nuclear plants. In addition to this a commercial PTT service for non-professional use (e.g., groups of people on holiday) may be delivered through an MCPTT system. Based on their operational model, the performance and MCPTT features in use vary per user organization, where functionality which is more mission critical specific (e.g., Ambient Listening and Imminent Peril Call) might not be available to commercial customers.
MCPTT Users expect to communicate with other MCPTT Users as outlined above, however MCPTT Users also need to be able to communicate with non MCPTT Users using their MCPTT UEs for normal telephony services. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.2 Typical use of the MCPTT Service | NOTE: Even though this subclause is written from an organization specific perspective the text is illustrative for typical use of MCPTT Services by all MCPTT Users.
Public safety workers often operate in groups and perform different tasks during the day/week. Many tasks and operations are controlled, assisted and/or coordinated by a dispatcher.
For their communications public safety workers are organized in groups. People that are working together communicate in the same MCPTT Group, the group communication helping them to coordinate quickly.
People with different tasks often communicate in separate MCPTT Groups.
Many of the public safety tasks are routine tasks, that are handled by standard procedures and communication structures, using dedicated MCPTT Groups. Communication structures and MCPTT Groups are also prepared for the handling of large incidents and control of large events. Similarly there are MCPTT Groups and procedures for coordination with public safety workers from other organizations and/or other countries.
The standard procedures and communication structures help the public safety workers to do their work successfully. This results in a long list of (>100) MCPTT Groups available to a public safety worker, from which the correct one is selected depending on the task. To help the public safety worker to quickly find and select the correct MCPTT Group for the task, the MCPTT Groups in the radio are often structured in folders and/or accessible via key-shortcuts. In addition to pre-established MCPTT Groups that users select, there are also provisions in MCPTT systems to merge MCPTT Groups and to select on behalf of a user which group they should be using and for a dispatcher to push them onto it. The large number of MCPTT Groups provisioned on devices is helpful for the device to be able to operate on the network and off the network. However the ability to provision over the air is also seen as a very useful feature, as currently Land Mobile Radio devices often have to be locally re-programmed, rather than updated over the air. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.3 Overview of MCPTT Group affiliation, call and transmission | An MCPTT Service provides Group Call and Private Call capabilities, which have various process flows, states and permissions associated with them. The figure 4.3.1, figure 4.3.2, and figure 4.3.3 indicate the high level flows, states and permissions associated with Group Calls and Private Calls. The diagrams apply to the on-network case and off-network case, as from a user perspective the service and concepts should appear similar on the network and off the network. From a technical perspective there might be differences between the on-network states and off-network states (e.g., off the network Affiliation might not require notifying an application server of a user's affiliation and there might also be other differences in the detail depending on the extent to which the off-network capabilities can match the on-network capabilities).
If an MCPTT User wants to communicate with an MCPTT Group they have to be allowed to access the MCPTT Group (i.e., be an MCPTT Group Member), they then have to affiliate and then can have an MCPTT Group as their Selected MCPTT Group. If an MCPTT User is only affiliated to a group this is so that they can receive from the group, however if an MCPTT User has a Selected MCPTT Group this is their group for transmitting on. The differences in states enable an MCPTT User to receive from multiple MCPTT Groups, but specify which MCPTT Group they would like to transmit on.
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.1: MCPTT User state diagram- transmit and receive for a particular MCPTT Group
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.2: MCPTT User state diagram- transmit only for a particular MCPTT Group
NOTE: This diagram is for illustrative purposes only and does not supersede the requirements. The diagram is not exhaustive and does not include all the different scenarios.
Figure 4.3.3: MCPTT User state diagram- receive only for a particular MCPTT Group
It is possible for an MCPTT User to be affiliated with one or more MCPTT Groups. Normally, while in operation, an MCPTT User informs the MCPTT Service about which MCPTT Groups he would like to be affiliated to. These affiliations remain in effect until the MCPTT User removes them, or changes them, or signs out of the service. Some MCPTT Users have permanent affiliations to certain MCPTT Groups and those affiliations are set up implicitly (i.e., automatically) when operating on the network. For those users, the MCPTT Group affiliation starts when the MCPTT Service successfully signs in the user and ends when the MCPTT User's explicit or implicit (e.g., due to inactivity or the turning off of all its devices) request to sign out of the MCPTT Service is acknowledged.
Every time a PTT request is granted a user can start an MCPTT transmission or "talk burst". An MCPTT Group Call consists of one or more MCPTT transmissions. Whether two consecutive transmissions from same or different users are part of the same call, or the second transmission starts a new call, depends on the configurable maximum length of the inactivity period between the consecutive MCPTT transmissions. This inactivity period can be seen as a Hang Time that starts at the end of the preceding transmission. While this timer is running, the resources associated with the call stay assigned to the call (except in case of pre-emption), which could reduce the latency of future floor requests for this group versus groups who are not involved in a call. When a new transmission starts during the inactivity period, the timer is stopped, reset and restarted again at the end of that transmission.
The MCPTT Service recognizes a number of "special" group calls including: Broadcast Group Call, Emergency Group Call and Imminent Peril group call.
A Broadcast Group Call can be seen as a special group call with only one MCPTT transmission.
While the In-progress Emergency state or In-progress Imminent Peril state is active, the inactivity period is conceptually set to infinity; i.e., the resources assigned to calls during these states are never released (except in case of pre-emption). An MCPTT Emergency Group Call or an Imminent Peril group call can be seen as having an unspecified number of transmissions: essentially, all the transmissions to a group during In-progress Emergency state or In-progress Imminent Peril are part of the same MCPTT Group Call.
Conditions on starting ("commencement") and continuing an MCPTT call can be established. Usually at least the call initiator (but also other users) are kept informed via notifications of the starting, stopping, queuing, etc., of a call.
In general, commencement conditions are related to the presence on the call (i.e., participation) of certain members of the group, and/or of a minimum number of members, as well as on the availability of resources (e.g., GBR bearers) of proper ARP. If the commencement conditions are not met, the call does not start (it can be queued or rejected). Normally, commencement conditions are not checked for individual transmission within a call.
Continuation conditions are similar (though not required to be identical) to commencement conditions and get re-evaluated when pre-emption, degradation of priority, motion out of communication range, de-selection of the group or de-affiliation (explicit or implicit) occur. If the continuation conditions are not met, the call stops. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.4 General handling of requests | Request handling is by no means specific only to MCPTT Service, but it plays a central role in its functionality.
Requests appear in the MCPTT Service in many forms and under many circumstances: e.g., requests for the floor during a call, requests for starting a call, requests for resources. Conceptually, requests are accompanied by priority information that is used in the arbitration, in case of contention; see also subclause 4.6 for a brief explanation and examples on how priority processing is modelled.
Upon arrival, a request is immediately granted, denied, or queued.
If queued, a request can be dropped due to queue overflow (i.e., too many items queued) or can be cancelled by an authorized user, who is usually the initiator of the request. Either way, the net result is that the request is denied.
When a request denial is communicated, the request may be re-requested either manually by user action or automatically. In the automatic case, while the request remains denied, it may be automatically repeated a configurable number of times where a minimum time interval between re-transmissions may also be applied.
There are many "queuing disciplines" possible that govern the placement of items in a queue and their subsequent removal from the queue: e.g., FIFO, priority order. Assuming that the queuing discipline chosen places the highest priority requests towards the top of the queue, the granted request is either, depending on the design and configuration, the front-most entry in the queue or the first entry counting from the top that can be satisfied by the available resources. For example, if the topmost entry in the queue is awaiting for ten GBR bearers of given characteristics to become available and the second entry in the queue is waiting for seven GBR bearers to become available, and at some point in time eight GBR bearers become available, then it is possible that the second request is granted ahead of the first one, which continues to wait. Alternatively, neither the first request nor the second request is granted and the wait continues until at least ten GBR bearers become available, at which time the first request is granted while the second request continues to wait. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5 Overview of MCPTT UE and MCPTT User in the MCPTT Service | The MCPTT Service supports MCPTT User Profiles. The MCPTT User Profile contains important information related to the MCPTT User receiving the MCPTT Service, including the MCPTT User identity, which is globally unique and independent of the mobile subscriber identity (IMSI) assigned by a 3GPP network operator. Part of the content of the MCPTT User Profile (e.g., containing some display preferences, some UE audio settings, some address books) can be set/modified/updated by the MCPTT User, but significant portions might be set/modified/updated only by authorized persons. The MCPTT User Profile is stored permanently in database(s) associated with the infrastructure providing the MCPTT Service. Relevant parts of the profile might be downloaded to and cached temporarily or permanently on certain MCPTT UEs. When stored on an MCPTT UE, the MCPTT User Profile associated with an MCPTT User might be confidentiality and integrity protected, with the information available only to a trusted application client associated to the MCPTT User, upon authentication. The MCPTT User Profile information can be synchronized automatically or on demand between the cache on the MCPTT UE and the main copy held in the database(s) of the MCPTT Service infrastructure. The MCPTT User Profile is part of the MCPTT application service domain and forms the basis of MCPTT application layer security and identifies an MCPTT User to the MCPTT Service.
Each MCPTT User has at least one MCPTT User Profile, and possibly several. Typically, one of the MCPTT User Profiles is designated as the default MCPTT User Profile, to be used unless an MCPTT User Profile is explicitly selected. In general, a user profile is associated with a specific device, with a specific mode of operation (i.e., on the network or off the network) and/or with a specific situation (e.g., user being off-duty, in a certain city, or playing a certain role). When an MCPTT User Profile is synchronized between the infrastructure and an MCPTT device, information could be downloaded to the device and updated, as necessary. Subsequently and subject to permissions, the MCPTT User might choose a different associated MCPTT User Profile to be downloaded and stored on the device. Only one MCPTT User Profile is active at a time. Authorized users are allowed to create, delete and alter MCPTT User Profiles for an MCPTT User and/or pre-stored MCPTT User Profiles.
The MCPTT Service supports MCPTT UEs which connect to the MCPTT Service. The capabilities of an MCPTT UE are specified in the present document. The MCPTT Application that is resident on the MCPTT UE establishes this connection, employing application layer security in its connection to the MCPTT Service. An MCPTT UE is capable of operating in on-network and off-network modes. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5.1 MCPTT User association to MCPTT UE in on-network mode | Consistent with the 3GPP paradigm, when an MCPTT UE is powered on, it accesses the 3GPP system, and connects to the 3GPP network. During this phase, the credentials from a USIM application (or possibly, an ISIM application, if IMS is used) on a UICC associated with the MCPTT UE is used for authentication with an HSS. This is followed by the MCPTT Application, resident on the MCPTT UE, establishing a connection, employing application layer security in its connection to the MCPTT Service.
Possibilities for the MCPTT UE, when connecting to the MCPTT Service:
- An MCPTT UE, with credentials of an MCPTT User at the time of connection to the MCPTT Service, is able to authenticate using a specific MCPTT User identity (e.g., via an Identity Management service). After successful user authentication the MCPTT User Profiles are made available to the MCPTT UE for use in both on-network and off-network operation modes.
- An MCPTT UE, without credentials of a specific MCPTT User at the time of connection to the MCPTT Service, proceeds using a default identity associated with the MCPTT UE itself. In this case, the MCPTT Service is capable of assigning a temporary MCPTT User Identity to this MCPTT UE. Some level of authentication might be attempted, and, depending on the results, an appropriate MCPTT User Profile associated with this temporary MCPTT User Identity and with the circumstances of the access is made available to the MCPTT UE for use in both on-network and off-network operation modes.
- The MCPTT Administrator is able to retrieve hardware and software parameters to define specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE for use in both on-network and off-network operation modes. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5.2 MCPTT User and MCPTT UE relationship | A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
The MCPTT Service allows the same MCPTT User to sign in (and stay simultaneously signed in) from different MCPTT UEs. For example, an incident manager or commander might use a portable phone, a command tablet, or a separate messaging unit. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5.3 MCPTT Users accessing the service through non-3GPP access interface | This document primarily focuses on MCPTT Users accessing and managing the MCPTT Service through MCPTT UEs, however there might be some dispatchers and administrators who might access the service through a non-3GPP access interface. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5.4 Shareable MCPTT UEs and gateway UEs | The conceptual model for shareable MCPTT UEs is that of a pool of UEs, each UE being interchangeable with any other, and users randomly choosing one or more UEs from the pool, each user for his temporary exclusive use. A shareable MCPTT UE can be used by user who can gain access to the MCPTT client application stored on it and can become an authenticated MCPTT User. A shareable MCPTT UE can serve only one MCPTT User at a time. An MCPTT User who signs into a shareable MCPTT UE that is already in-use causes the sign-off of the previous MCPTT User.
An MCPTT User can simultaneously have several active MCPTT UEs, which, from an MCPTT Service point of view, are addressable individually and/or collectively within the context of their association to the MCPTT User.
The conceptual model for a gateway UE is that of a UE capable of providing service to an MCPTT User employing a non-3GPP device. A gateway UE is usable simultaneously by multiple MCPTT Users. Unlike a shareable MCPTT UE, if a new person enters his valid credentials towards signing in the MCPTT Service, his successful signing in and becoming an MCPTT User does not affect the initial MCPTT Users already served by the gateway UE.
A gateway UE is typically installed in a vehicle (e.g., a police car, fire truck) and has wired and/or wireless connections to various devices in use by the MCPTT Users.
A gateway UE differs functionally from a ProSe relay node. In the ProSe paradigm, the relay node and the devices served by it are all (ProSe enabled) 3GPP UEs, and are "visible" to the 3GPP system as UEs. In the gateway UE paradigm, only the gateway UE is an 3GPP device and only it is "visible" at the 3GPP network layer.
Figure 4.5.4.1 shows schematically some of the relationships between MCPTT Users and MCPTT UEs.
Figure 4.5.4-1: Relationships between MCPTT Users and MCPTT UEs |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.5.5 MCPTT User association to MCPTT UE in off-network mode | A user can enter his identifying/authenticating credentials (e.g., user name/ password, PIN, biometrics, asserted identity from a remote, trusted device). This step typically gives the MCPTT User access to local information and applications stored on the MCPTT UE, and in particular, to the MCPTT client application.
After successful local user authentication an MCPTT User Profile, which was previously made available to the MCPTT UE, is used for off-network operation mode. This previously configured MCPTT User Profile information allows the MCPTT User to be identified using the same MCPTT User Identity as in the on-network mode.
An MCPTT UE, without credentials of a specific MCPTT User, operates in off-network mode, if so configured by an MCPTT Administrator. The MCPTT Administrator defines specific parameters and attributes (e.g., groups, MCPTT Emergency behaviour, priority and QoS attributes) associated with a temporary MCPTT User Identity for operation of the MCPTT UE in off-network operation mode. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6 Overview of MCPTT priorities | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.1 MCPTT priority model | Many non-public safety 3GPP users today subscribe to one particular priority and QoS level of service (e.g., "gold", "silver" or "bronze"), which always provides fixed differentiation. This model, effective and relatively straightforward for non-public safety users, falls short when it comes to the needs of the public safety applications.
MCPTT Priority and QoS is situational. The MCPTT Service is intended to provide a real-time priority and QoS experience for MCPTT calls, as public safety users have significant dynamic operational conditions that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the 3GPP system.
Another feature of a mission critical service is transparency of interactions between the users and the system. A first responder that needs to change the QoS of his communications is not to be distracted from his mission due to complicated UE behaviours or service interactions. Instead, the service acts in an anticipatory and adaptive manner to provide the proper quality of experience to the user, automatically, or with simple and minimal interaction.
The mission critical service is also expected to provide the ability to interface with public safety systems (e.g., Computer Aided Dispatch) in order to determine the user's state (e.g., incident severity), environment and conditions and to affect the most appropriate priority and QoS experience for the user.
The MCPTT Priority handling for on-network use for MCPTT Calls is conceptually modelled as shown in figure 4.6.1.1. The conceptual model identifies three areas of prioritization: prioritization between and within calls, inter-system prioritization, and prioritization at the transport layer (3GPP system and UE). At the Application Layer a generic, network side, functional entity, "MCPTT Priority and QoS Control", processes with each request static, preconfigured information about users and groups participating in MCPTT, as well as dynamic (or situational) information about them. Based on the results of this processing, the "MCPTT Priority and QoS Control" provides information to and directs interactions with other functional entities, systems, or layers to ensure, to the extent possible, that from a quality of experience point of view, calls and transmissions are handled properly in accordance to established policy rules.
Error! Objects cannot be created from editing field codes.
Figure 4.6.1-1: A conceptual on-network MCPTT priority model
The User Static Attributes include information categorizing the user, possibly by several criteria (e.g., first responder, second responder, supervisor, dispatcher, administrator), as well as jurisdictional boundaries and possibly a preconfigured system-wide individual priority level.
The Group Static Attributes include information about the nature/type of the group and the owning organization(s), the jurisdictional boundaries for transmitters and receivers within the group, the normal hours of operation for the group, pre-emption dispositions relative to other groups, and the default minimum priority of the group, i.e., the minimum priority characteristics that are provided to all the Participants in a group call associated with this group, regardless of their individual priority characteristics.
The User Dynamic Attributes include the user/Participant's operational status (e.g., on/off duty), his location, the type of incident (e.g., MCPTT Emergency or Imminent Peril) he might be involved in and whether or not he initiated it, whether or not he is individually involved in a formally managed incident and if yes, the boundaries of the incident area, the incident severity and his assigned role in the resolution of the incident.
The Group Dynamic Attributes include the type of incident (e.g., MCPTT Emergency or Imminent Peril), if any, the group is currently handling and in case of involvement in a formally managed incident the boundaries of the incident area and the incident severity. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.2 Generic processing of priority information | This functionality applies to MCPTT Call initiations and transmissions for the management of potentially contended resources (e.g., GBR bearers) and also for Floor control during an MCPTT Group Call.
Each request for exclusive access to resource(s) or for preferential treatment over a contending request arrives accompanied by priority information. This information stays associated with the companion request, whether the request is granted or is queued. The priority information is used for comparison between requests and facilitates the adding and removing of requests from queues and/or authorized interruption of service associated with a previously granted request, if still active. For each request, whether initially queued or not, the requesting party is informed (directly or indirectly) when his request is granted or denied. Other users/Participants are also notified of the disposition of a request and the notification includes the identity of the requestor, as needed. In addition, each requestor can be notified of the position of his request in the queue and he is allowed to cancel his requests while queued. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.3 Handling of MCPTT priority information for Floor control | Floor control is applied in the context of a single MCPTT Call and is triggered by a Participant request for the permission to transmit. Priority information accompanies each grant request. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.4 Handling of MCPTT priority information for interactions at the transport layer | At the Transport Layer, the MCPTT Service uses3GPP controls to adapt the overall behaviour of the MCPTT System to the needs for resources and/or preferential treatment over other contenders, based on the priority information accompanying the request.
The following four controls are available, to be used as necessary, based on the phase of the MCPTT call:
• 3GPP system Access Controls;
• UE Access Controls;
• 3GPP system Admission Controls; and
• 3GPP system Scheduling Controls.
3GPP system Access Controls and UE Access Controls are used to allow preferential treatment of public safety UEs in situations of access congestion. The controls use priority and QoS mechanisms (e.g., using mechanisms like Access Class Barring, Service Specific Access Control, Access Control for Circuit Switched Fallback, Extended Access Barring).
Admission Controls are used for the establishment and maintenance of the priority levels and of the pre-emption vulnerability and capability of bearers associated with transmissions and calls. At the start of an MCPTT call, the MCPTT Service requires bearers with proper ARP and pre-emption characteristics are in place prior to the call proceeding.
Scheduling Controls (e.g., QCI and bandwidth for the bearers) are used for assuring the appropriate QoS necessary for meeting the Participants' expectation in the perceived quality of the delivered information, primarily in terms of when the service starts and the real-time characteristics of the delivered traffic (e.g., perceived delay, choppiness, clarity). |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.5 Handling of MCPTT priority information for interactions with non-3GPP PTT systems | An MCPTT call can be mixed, with some Participants served by one network/system and other Participants served by a different network(s)/system(s). In general the systems can be quite different. For example, some Participants use MCPTT/LTE, while others could use a P25-based system. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.6.6 MCPTT priority for Private Call | The MCPTT Service uses User Static Attributes of the Participants, potentially adjusted based on User Dynamic Attributes, if applicable. By default, the priority of an MCPTT Private Call is the same as the priority of the originator of the call. Similar to group calls there are MCPTT Emergency Private Calls (with Floor control), which also have a similarly high priority. These are used where there is immediate danger to the user and are typically used to communicate with a dispatcher. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 4.7 Overview of MCPTT identifiers | The main identifiable entities in use by the MCPTT Service are Mission Critical Organizations, MCPTT Groups, MCPTT Users, and MCPTT Administrators. The UEs are identified at the transport or network layer, but in some situations they might also be identified by the MCPTT Service. Each identifiable entity is distinct from all others and has an identifier (ID) associated to it, unique within a proximate identity domain. Those domains correspond to identifiable entities and can be nested within other domains in a multi-level hierarchical fashion. For example an MCPTT User might have an identifier unique within the domain corresponding to a Mission Critical Organization. The top-down concatenation of identifiers can generate unique identifiers within larger contexts, eventually leading to the identifiers being globally unique.
Each identifier can be associated with one or more aliases, which can be used for displaying and selection purposes. Some aliases are shortened equivalents of the identifier used for efficient signalling and are not intended for human interactions. At a minimum, each entity has one alias (default) which is the alphanumeric representation of its identifier. Most entities have a main alias, which is the entity's name. Some aliases can be pictures, icons or other graphic representations. It is up to the implementation to decide if aliases have to be unique and if so, within which domain. Finally, some aliases are public, can be created/deleted only by authorized persons and are available to the MCPTT Service, while other aliases are private, can be created/deleted by their owners and might be residing only on certain UEs or be part of some private address books.
It is possible in principle for User IDs, Group IDs, as well as for aliases, to be defined system wide with certain values, but have different values for each application: e.g., the system wide User ID might be different from the MCPTT User ID and different from the video User ID for the same user. However, this type of separation might not be beneficial, and in practice only one identifier is likely to be used.
For simplicity, the term "User ID" is employed to identify an MCPTT User, without distinction of whether it is an identifier or an alias. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5 MCPTT Service requirements common for on the network and off the network | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1 General group call requirements | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.1 General aspects | [R-5.1.1-001] Void
[R-5.1.1-002] Void
[R-5.1.1-003] Void
[R-5.1.1-004] Void
[R-5.1.1-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.2 Group/status information | [R-5.1.2-001] Void
[R-5.1.2-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.3 Group configuration | [R-5.1.3-001] Void
[R-5.1.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.4 Identification | [R-5.1.4-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.5 Membership/affiliation | [R-5.1.5-001] Void
[R-5.1.5-002] Void
[R-5.1.5-003] Void
[R-5.1.5-004] Void
[R-5.1.5-005] Void
[R-5.1.5-006] Void
[R-5.1.5-007] Void
[R-5.1.5-008] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.6 Group Call administration | [R-5.1.6-001] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.7 Prioritization | [R-5.1.7-001] Void
[R-5.1.7-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.1.8 Charging requirements for MCPTT | [R-5.1.8-001] Void
[R-5.1.8-002] Void
[R-5.1.8-003] Void
[R-5.1.8-004] Void
[R-5.1.8-005] Void
[R-5.1.8-006] Void
[R-5.1.8-007] Void
[R-5.1.8-008] Void
[R-5.1.8-009] Void
[R-5.1.8-010] Void
[R-5.1.8-011] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.2 Broadcast Group | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.2.1 General Broadcast Group Call | [R-5.2.1-001] Void
[R-5.2.1-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.2.2 Group-Broadcast Group (e.g., announcement group) | [R-5.2.2-001] Void
[R-5.2.2-002] Void
[R-5.2.2-003] Void
[R-5.2.2-004] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.2.3 User-Broadcast Group (e.g., System Call) | [R-5.2.3-001] Void
[R-5.2.3-002] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.3 Late call entry | [R-5.3-001] Void
[R-5.3-002] Void
[R-5.3-003] Void
[R-5.3-004] Void
[R-5.3-005] Void |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.4 Dynamic group management (i.e., dynamic regrouping) | NOTE: No common on-network and off-network dynamic group management requirements have been identified. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.5 Receiving from multiple MCPTT calls | |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.5.1 Overview | MCPTT Users receive call traffic of their affiliated MCPTT Groups. This multiple receiving, called monitoring by some organizations, provides MCPTT Users current information about police, fire or critical medical events that are occurring within their jurisdictions. This is useful for dispatchers or those that might not be the primary support for that event at that moment. The information gained by monitoring might be useful for the dispatcher to determine any actions to take or be useful later if the MCPTT User is deployed to provide additional support for that event. The MCPTT User might be assigned to support the activities of more than one MCPTT Group on the same shift. This means that the MCPTT User receives multiple MCPTT Groups.
An MCPTT User with limited speaker resources (e.g., a handheld UE) might find that playing out concurrent received audio from multiple active MCPTT Groups becomes confusing and could also cause undesired voice distortion for the receiving user. During periods of time when the MCPTT User is receiving audio from multiple MCPTT Groups, which MCPTT Group's audio is presented to the MCPTT User is determined by the MCPTT User's choice, the priority associated with the talker of the Selected MCPTT Group(s), other considerations or combinations of these. The MCPTT UE is aware of all the active groups to which the MCPTT User has affiliated or selected and the identity of the other active receiving groups is available for display on the MCPTT UE. When the receive activity from the Selected MCPTT Group stops, the MCPTT UE might present the audio from the next group per the MCPTT User's choice or by other means.
If none of the multiple groups to which the MCPTT User has affiliated or selected is active, the MCPTT UE would continue to monitor for activity by any of the multiple affiliated or Selected MCPTT Groups. Monitoring for activity of multiple MCPTT Groups is also known as scanning and the list of the multiple groups is also known as a scan list. |
025654ae449f21f6a2c0a037ab2affe6 | 22.179 | 5.5.2 Requirements | [R-5.5.2-001] Void
[R-5.5.2-002] Void
[R-5.5.2-003] Void
[R-5.5.2-004] Void
[R-5.5.2-005] Void
[R-5.5.2-006] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N5) of MCPTT Group transmissions that an MCPTT UE simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N10) of MCPTT Private Calls (with Floor control) in which an MCPTT UE simultaneously participates.
[R-5.5.2-008] Void
[R-5.5.2-009] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to limit the total number (N7) of MCPTT Group transmissions that an MCPTT User simultaneously receives in one MCPTT Group call in case of override.
[R-5.5.2-010] Void
[R-5.5.2-011] Void
[R-5.5.2-012] Void
[R-5.5.2-013] Void |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.