hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 5
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.18.3.4 Legacy land mobile radio
|
[R-6.18.3.4-001] The MCPTT Service shall enable interworking with legacy Land Mobile Radio systems that are compliant with the TIA-603-D [3] Standard.
[R-6.18.3.4-002] Interworking between the MCPTT Service and TIA-603 systems shall be capable of interworking with a multiplicity of independently administered systems based on the TIA-603-D [3] Standard.
[R-6.18.3.4-003] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Group calls between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-004] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized MCPTT User to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
[R-6.18.3.4-005] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize an MCPTT User to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-006] Interworking between the MCPTT Service and TIA-603 systems shall provide a mechanism for an authorized TIA-603 subscriber unit or console to initiate an override within a PTT Group call that has both MCPTT Users and TIA 603 subscriber units and consoles.
[R-6.18.3.4-007] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize a TIA-603 subscriber unit or TIA-603 console to be able to initiate an override of a PTT Group call between MCPTT Users and TIA-603 subscriber units and consoles.
[R-6.18.3.4-008] Interworking between the MCPTT Service and TIA-603 systems shall support interoperable PTT Private Calls (with Floor control) between MCPTT Users and TIA-603 subscriber units or consoles.
[R-6.18.3.4-009] Interworking between the MCPTT Service and TIA-603 systems shall support a means of reconciling codecs between interoperable calls.
[R-6.18.3.4-010] Interworking between the MCPTT Service and TIA-603 systems shall support conveyance of Losing audio from TIA 603 subscribers units and consoles to suitably privileged MCPTT Users.
[R-6.18.3.4-011] The MCPTT Service shall provide a mechanism for an MCPTT Administrator to authorize MCPTT Users to be able to receive Losing audio from TIA-603 subscribers units and consoles.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.18.3.5 Void
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.18.4 GSM-R
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.18.4.1 Overview
|
GSM-R, governed by 3GPP standards, is widely and globally used for rail communication. GSM-R offers capabilities analogous to those provided by MCPTT, including group calls, point-to point calls, broadcast calls, dynamic group management and the bearer service for train safety applications.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.18.4.2 Requirements
|
[R-6.18.4.2-001] Void
[R-6.18.4.2-002] Void
[R-6.18.4.2-002a] Void
[R-6.18.4.2-002b] Void
[R-6.18.4.2-003] The MCPTT Service shall enable interworking between Ad hoc Group Calls and Advanced Speech Call Items used in GSM-R.
NOTE: The impact on GSM-R needs to be minimised.
[R-6.18.4.2-004] Interworking between the MCPTT Service and GSM-R shall support interoperable PTT Private Calls between an MCPTT User and a GSM-R mobile station or controller terminal.
[R-6.18.4.2-005] Interworking between the MCPTT Service and GSM-R voice services shall support a means of reconciling codecs.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
6.19 MCPTT coverage extension using ProSe UE-to-Network Relays
|
[R-6.19-001] Void
[R-6.19-002] Void
[R-6.19-003] Void
[R-6.19-004] Void
[R-6.19-005] Void
[R-6.19-006] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7 MCPTT Service requirements specific to off-network use
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.1 Off-network Push To Talk overview
|
The MCPTT Service while operating in off-network mode comprises a set or collection of functions necessary to provide Mission Critical Push To Talk (MCPTT) using a ProSe direct (UE-to-UE) Communication path (ProSe direct communication path) for transport. The ProSe direct communication path does not traverse the network infrastructure.
Users operating off the network are either out of network coverage (not served by a 3GPP network) (e.g., in a remote mountain area fighting a forest fire 20 miles from the nearest network) or have selected a ProSe direct communication path for MCPTT while in network coverage. MCPTT Users operating off the network need to be in ProSe direct communication range in order to communicate.
NOTE 1: While the network is likely to be a primary, reliable transport of MCPTT communications, there are many situations where MCPTT communications are needed in areas where the network is not available, or coverage is not reliable.
MCPTT Users outside of the coverage of the fixed network might be first responders in a rural area assisting in a response to a plane crash, fire fighters in a remote mountain area fighting a forest fire or police officers inside a residence responding to a domestic issue. Off-network MCPTT communications are expected to be immediately accessible to users in the absence of the network.
MCPTT Users in network coverage might be working in a confined area, such as fire fighters fighting a structure fire where direct UE-to-UE communication is more desirable and reliable. Users can communicate directly with one another without having to overcome the resistance of a building and distance to the nearest base station to communicate with other members of their team inside the building that are nearby.
To operate off the network, an MCPTT UE is capable of automatically switching to a ProSe direct communication path for use of MCPTT when detecting an off-network (out of coverage) condition. In addition a mechanism is provided for an authorized user to select (manually switch to) a ProSe direct communication path for use of off-network MCPTT communications (e.g., while in network coverage).
When operating off the network, the MCPTT Service is provided by the MCPTT application on the UE as compared to operations on the network, where the MCPTT Application on the UE interacts with an MCPTT server and the network to provide the MCPTT Service.
NOTE 2: For MCPTT UEs that have selected a ProSe Direct Communication path for use of MCPTT while in network coverage, signalling with the network and MCPTT Service might be available (e.g., radio resource allocation, MCPTT User Profile management updates and cryptographic key management updates), while the MCPTT User transmissions would be direct between the MCPTT UEs (e.g., not traversing the network).
The Off-Network MCPTT Service builds upon ProSe enablers to establish, maintain and terminate the signalling and communication path(s) among the off-network users. To the extent feasible, it is expected that the end user's experience is similar regardless if the MCPTT Service is used with a 3GPP network or based on the use of a ProSe direct communication path.
The Off-Network MCPTT Service is intended to support communication between a group of 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.
When operating 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).
The Off-Network MCPTT Service provides a means for a user with higher priority (e.g., MCPTT Emergency condition) to override (interrupt) the current talker. The Off-Network 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 Off-Network 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 Off-Network MCPTT Service user might join an already established MCPTT Group call (Late call entry). In addition the Off-Network MCPTT Service supports User IDs, aliases and user Location determination features.
For operation off the network (e.g., when out of network coverage), an MCPTT UE is (pre-)provisioned by an MCPTT Administrator and/or authorized user with the following in order to use MCPTT:
a) An MCPTT User Profile associated with each of the intended MCPTT Users of the MCPTT UE that might be used for off-network operation;
1) An alphanumeric identifier (with a minimum length of N3) (i.e., alias) for each MCPTT User;
2) A number of off-network MCPTT Groups for use by the MCPTT User;
3) An alphanumeric identifier (i. e., alias) for the authorized off-network MCPTT Groups;
4) A Mission Critical Organization name if available, associated with each of the intended MCPTT Users or Administrator;
5) A number of off-network MCPTT Users for Private Call for which the MCPTT User is authorized;
b) Authentication and end to end security keys.
NOTE 3: MCPTT UEs can be provisioned for off-network use by either configuration outside of network coverage or by attaching to the network.
An MCPTT UE operating off the network is capable of transmitting the talker Location information, User ID, alias(es), off-network MCPTT Group ID, group alias and, if available, Mission Critical Organization name of the user who is talking (i.e., whose UE is transmitting) to all other users in a call including MCPTT UEs operating off the network that are late entering a call in progress.
The Off-Network MCPTT Service uses the capabilities defined in ProSe TS 22.278 [5], including the ProSe Relay capabilities defined in ProSe TS 22.278 [5] and GCSE_LTE TS 22.468 [6].
NOTE 4: As indicated in TS 22.278 [5] use of a ProSe Direct Communication path outside of network coverage is only applicable for Public Safety ProSe enabled UEs. For non-Public Safety ProSe enabled UEs the selection of the most appropriate communication path (ProSe Communication path (direct or routed via local basestation) or 3GPP network path) is under network control and based on operator preferences.
MCPTT Service requirements specific to off-network use are defined in clause 7. Common MCPTT service requirements defined in clause 5 apply whether the MCPTT Service is in use on the network or off the network.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.2 General off-network MCPTT requirements
|
[R-7.2-001] Void
[R-7.2-002] Void
[R-7.2-003] Void
[R-7.2-004] Void
[R-7.2-005] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3 Floor control
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3.1 General aspects
|
[R-7.3.1-001] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which off-network Participant(s) are allowed to transmit to other off-network Participants.
[R-7.3.1-002] The off-network Floor control functionality in an MCPTT Service shall determine at a point in time which received transmission(s) from off-network Participant(s) shall be presented to the receiving off-network Participant(s).
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3.2 Requesting permission to transmit
|
[R-7.3.2-001] A Participant in an off-network MCPTT Group call, with the authority to transmit, shall be able to request to transmit to the off-network MCPTT Group.
[R-7.3.2-002] The off-network Floor control functionality shall have a mechanism for resolving simultaneous requests for permission to transmit within the same call.
[R-7.3.2-003] Following an MCPTT Request for permission to transmit, the Affiliated MCPTT Group Member that is allowed to transmit shall be given an indication that the member is allowed to transmit on the member's Selected MCPTT Group.
[R-7.3.2-004] Following an MCPTT Request for permission to transmit, an Affiliated MCPTT Group Member that is not allowed to transmit on the Selected MCPTT Group shall be given an indication that permission to transmit was rejected or queued.
[R-7.3.2-005] Following an MCPTT Private Call (with Floor control) request for permission to transmit, the MCPTT User that is allowed to transmit shall be given an indication that the user is allowed to transmit to the targeted MCPTT User.
[R-7.3.2-006] Following an MCPTT Private Call (with Floor control) request for permission to transmit, an MCPTT User that is not allowed to transmit shall be given an indication that the permission to transmit was rejected.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3.3 Override
|
[R-7.3.3-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that Floor control override may operate during off-network MCPTT.
[R-7.3.3-002] The MCPTT Service shall provide a mechanism for MCPTT Administrators to create a priority hierarchy for determining what Participants, Participant types, and urgent transmission types, when operating off the network, be granted a request to override an active off-network MCPTT transmission.
[R-7.3.3-003] The priority hierarchy used for granting a request to override an active MCPTT transmission shall contain at least four (4) levels.
[R-7.3.3-004] The MCPTT Service shall provide a mechanism for Participants, to override an active MCPTT transmission of a transmitting Participant when the priority level of the overriding Participant or call type are ranked higher than the priority level of the transmitting Participant or call type.
[R-7.3.3-005] If an authorized Participant overrides an MCPTT transmission, the MCPTT Service shall provide a means of notifying the overridden Participant(s) that the transmission has been overridden.
[R-7.3.3-006] The MCPTT Service shall provide a mechanism to enable an MCPTT Administrator to configure which MCPTT Group transmission a Participant(s) receives, overriding and/or overridden for cases where an authorized Participant overrides an off-network MCPTT transmission. This mechanism, at the receiving Participant, shall also determine which transmission should be presented to the MCPTT User when an unauthorized transmission override has occurred due to a failure of transmit Floor control (e.g., due to the best effort nature of ProSe direct communication).
[R-7.3.3-007] If the MCPTT Group has been configured to only allow the overriding transmitting Participant to transmit, the MCPTT Service shall revoke the transmit permission of the overridden transmitting Participant.
[R-7.3.3-008] If the MCPTT Group has been configured to allow both overriding and overridden transmitting Participants to transmit, the MCPTT Service shall provide a mechanism for authorized receiving Participants to be able to listen to both the overriding transmission and any overridden Participant transmissions, dependent on configuration.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3.4 Terminating permission to transmit
|
[R-7.3.4-001] A transmitting Participant shall be able to indicate to the Off-Network MCPTT Service that the Participant no longer wants to transmit.
[R-7.3.4-002] The MCPTT Service shall provide an indication to receiving Participants that the transmitting Participant has finished transmitting.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.3.5 Transmit time limit
|
[R-7.3.5-001] An MCPTT UE shall be pre-provisioned by an MCPTT Administrator and/or authorized user with the necessary information in order that a transmit time limit function may operate during off-network MCPTT.
[R-7.3.5-002] The MCPTT Service shall enable an MCPTT Administrator to configure the limit for the length of time that a Participant transmits from a single request to transmit.
[R-7.3.5-003] The Floor control functionality shall have a configurable limit for the length of time that a Participant transmits from a single request to transmit.
[R-7.3.5-004] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant is within a configurable amount of time before his transmit time limit is reached.
[R-7.3.5-005] The Floor control functionality shall provide an indication to the transmitting Participant that the Participant's transmit time limit has been reached.
[R-7.3.5-006] The Floor control functionality shall remove the permission to transmit from the transmitting Participant when the Participant's transmit time limit has been reached.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.4 Call Termination
|
[R-7.4-001] The MCPTT Service when operating off the network shall terminate a call after a period of inactivity.
[R-7.4-002] The MCPTT Service when operating off the network shall provide a mechanism for an MCPTT Administrator to preconfigure the inactivity timer.
[R-7.4-003] Void
[R-7.4-004] Void
[R-7.4-005] Void
[R-7.4-006] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.5 Broadcast Group
|
[R-7.5-001] Void
[R-7.5-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.6 Dynamic group management (i.e., dynamic regrouping)
|
NOTE: No specific off-network MCPTT requirements for dynamic group management have been identified.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.7 MCPTT priority requirements
|
[R-7.7-001] Void
[R-7.7-002] The Off-Network MCPTT Service shall pass these attributes to the ProSe transport layer for the purposes of prioritizing the associated user data.
[R-7.7-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.8 Call types based on priorities
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.8.1 MCPTT Emergency Group Call requirements
|
[R-7.8.1-001] Void
[R-7.8.1-002] Void
[R-7.8.1-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.8.2 MCPTT Emergency Group Call cancellation requirements
|
[R-7.8.2-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.8.3 Imminent Peril Call
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.8.3.1 Imminent Peril group call requirements
|
[R-7.8.3.1-001] Void
[R-7.8.3.1-002] Void
[R-7.8.3.1-003] Void
[R-7.8.3.1-004] Void
[R-7.8.3.1-005] Void
7.8.3.2 Imminent Peril group call cancellation requirements
[R-7.8.3.2-001] Void
[R-7.8.3.2-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.9 Location
|
[R-7.9-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.10 Security
|
[R-7.10-001] Void
[R-7.10-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11 Audio MCPTT Call performance
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.1 MCPTT Access time and Mouth-to-ear latency
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.1.1 General overview
|
For MCPTT Users, one of the most important performance criteria is the MCPTT Access time (KPI 1). The MCPTT Access time is defined as the time between when an MCPTT User requests to speak (normally by pressing the MCPTT control on the UE) and when this user gets a signal to start speaking. This time does not include confirmations from receiving users.
The Mouth-to-ear latency (KPI 3) is the time between an utterance by the transmitting user, and the playback of the utterance at the receiving user's speaker. Figure 7.11.1.1.1 illustrates the MCPTT Access time and Mouth-to-ear latency.
Figure 7.11.1.1-1: Illustration of MCPTT Access time and Mouth-to-ear latency
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.1.2 Requirements
|
NOTE: The MCPTT Access time and Mouth-to-ear latency for off-network use is FFS.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.2 Late call entry performance
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.2.1 General overview
|
An MCPTT User is able to join or leave an already ongoing MCPTT Group Call. Late call entry is the activity when an Affiliated MCPTT Group Member joins an MCPTT Group Call in which other Affiliated MCPTT Group Members are already active. The Late call entry time (KPI 4) is the time to enter an ongoing MCPTT Group Call measured from the time that the user decides to monitor such an MCPTT Group Call, to the time when the UE's speaker starts to play the audio. The performance requirements for Late call entry time only applies to when there is ongoing voice transmitted at the time the MCPTT User joins the call.
In a Late call entry there might be an initial lost audio of the voice burst sent to the new Receiving MCPTT Group Member.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.2.2 Requirements
|
NOTE: The Late call entry time (KPI 4) for off-network use is FFS.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.11.3 Audio / Voice quality
|
[R-7.11.3-001] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.12 Off-network MCPTT operations
|
[R-7.12-001] Void
[R-7.12-002] Void
[R-7.12-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.13 Off-network UE functionality
|
[R-7.13-001] Void
[R-7.13-002] Void
[R-7.13-003] Void
[R-7.13-004] Off-network MCPTT UEs shall support a minimum number of (N8) simultaneous off-network MCPTT calls.
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.14 Switching to off-network MCPTT
|
[R-7.14-001] Void
[R-7.14-002] Void
[R-7.14-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.15 Off-network recording and audit requirements
|
[R-7.15-001] Void
[R-7.15-002] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.16 Off-network UE-to-UE Relay
| |
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.16.1 Private Calls
|
[R-7.16.1-001] Void
[R-7.16.1-002] Void
[R-7.16.1-003] Void
|
025654ae449f21f6a2c0a037ab2affe6
|
22.179
|
7.16.2 Group Calls
|
[R-7.16.2-001] Void [R-7.16.2-002] Void Annex A (informative): Variables Table A.1: List of variables Variable Meaning Value Reference B1 Number of levels of group hierarchy 5.2.2 B2 Number of levels of user hierarchy 5.2.3 KPI 1 MCPTT Access time < 300 ms 6.15.3.2 KPI 2 End-to-end MCPTT Access time < 1000 ms 6.15.3.2 KPI 3 Mouth-to-ear latency < 300 ms 6.15.3.2 KPI 4a Maximum Late call entry time (without application layer encryption) < 150 ms 6.15.4.2 KPI 4b Maximum Late call entry time (with application layer encryption) < 350 ms 6.15.4.2 N1 Number of receiving members present for an MCPTT Group. 6.4.2 N2 Total number of MCPTT Groups that an MCPTT User can be affiliated to simultaneously 5.1.5 N3 Minimum length of alphanumeric identifiers (i.e., Alias ID) 5.8, 6.4.3, 7.1, and 7.2 N4 Number of simultaneous MCPTT Group calls received by a UE 5.5.2 N5 Total number of MCPTT Group transmissions that a UE can receive 5.5.2 N6 Number of simultaneous MCPTT Group calls received by a user 5.5.2 N7 Total number of MCPTT Group transmissions that a user can receive 5.5.2 N8 Minimum number of simultaneous off-network MCPTT calls supported by an off-network MCPTT UE. 7.13 N9 Maximum number of simultaneous audios received by an MCPTT User in a single MCPTT Group 6.2.3.1 N10 Total number of MCPTT Private Calls (with Floor control) in which a UE simultaneously participates 5.5.2 N11 Total number of MCPTT Group Members of an MCPTT Group 6.1 Annex A1 (Informative): MCPTT Requirements for MCCoRe This table provides an exhaustive list of those requirements in 3GPP TS 22.179 that have been mapped to MCCoRe. 5 MCPTT Service Requirements common for on the network and off the network 5.1 General Group call requirements 5.1.1 General Aspects R-5.1.1-001 R-5.1.1-001 R-5.1.1-002 R-5.1.1-002 R-5.1.1-003 R-5.1.1-003 R-5.1.1-004 R-5.1.1-004 R-5.1.1-005 R-5.1.1-005 5.1.2 Group/status information R-5.1.2-001 R-5.1.2-001 R-5.1.2-002 R-5.1.2-002 5.1.3 Group configuration R-5.1.3-001 R-5.1.3-001 R-5.1.3-002 R-5.1.3-002 5.1.4 Identification R-5.1.4-001 R-5.1.4-001 5.1.5 Membership/affiliation R-5.1.5-001 R-5.1.5-001 R-5.1.5-002 R-5.1.5-002 R-5.1.5-003 R-5.1.5-003 R-5.1.5-004 R-5.1.5-004 R-5.1.5-005 R-5.1.5-005 R-5.1.5-006 R-5.1.5-006 R-5.1.5-007 R-5.1.5-007 R-5.1.5-008 R-5.1.5-008 5.1.6 Group Call administration R-5.1.6-001 R-5.1.6-001 5.1.7 Prioritization R-5.1.7-001 R-5.1.7-001 R-5.1.7-002 R-5.1.7-002 5.1.8 Charging requirements for MCPTT R-5.1.8-001 R-5.1.8-001 R-5.1.8-002 R-5.1.8-002 R-5.1.8-003 R-5.1.8-003 R-5.1.8-004 R-5.1.8-004 R-5.1.8-005 R-5.1.8-005 R-5.1.8-006 R-5.1.8-006 R-5.1.8-007 R-5.1.8-007 R-5.1.8-008 R-5.1.8-008 R-5.1.8-009 R-5.1.8-009 R-5.1.8-010 R-5.1.8-010 R-5.1.8-011 R-5.1.8-011 5.2 Broadcast Group 5.2.1 General Broadcast Group Communication R-5.2.1-001 R-5.2.1-001 R-5.2.1-002 R-5.2.1-002 5.2.2 Group-Broadcast Group (e.g., announcement group) R-5.2.2-001 R-5.2.2-001 R-5.2.2-002 R-5.2.2-002 R-5.2.2-003 R-5.2.2-003 R-5.2.2-004 R-5.2.2-004 5.2.3 User-Broadcast Group (e.g., System Communication) R-5.2.3-001 R-5.2.3-001 R-5.2.3-002 R-5.2.3-002 5.3 Late call entry R-5.3-001 R-5.3-001 R-5.3-002 R-5.3-002 R-5.3-003 R-5.3-003 R-5.3-004 R-5.3-004 R-5.3-005 R-5.3-005 5.4 Dynamic group management (i.e., dynamic regrouping) NA 5.5 Receiving from multiple MCPTT calls 5.5.1 Overview NA 5.5.2 Requirements R-5.5.2-004 R-5.4.2-001 R-5.5.2-005 R-5.4.2-002 R-5.5.2-008 R-5.4.2-003 R-5.5.2-010 R-5.4.2-004 R-5.5.2-011 R-5.4.2-005 R-5.5.2-012 R-5.4.2-006 R-5.5.2-013 R-5.4.2-007 5.6 Private Call NA 5.6.1 Private Call Overview NA 5.6.2 Private Call (with Floor control) general requirements NA 5.6.3 Private Call (with Floor control) commencement requirements NA 5.6.4 Private Call (with Floor control) termination NA 5.6.5 Private Call (with Floor control) administration NA 5.7 MCPTT priority requirements NA 5.7.1 Overview NA 5.7.2 Call types based on priorities NA 5.7.2.1 MCPTT Emergency Group Call NA 5.7.2.1.1 MCPTT Emergency Group Call requirements R-5.7.2.1.1-002 R-5.6.2.2.1-002 R-5.7.2.1.1-003 R-5.6.2.2.1-003 R-5.7.2.1.1-004 R-5.6.2.2.1-004 R-5.7.2.1.1-005 R-5.6.2.2.1-005 R-5.7.2.1.1-006 R-5.6.2.2.1-006 R-5.7.2.1.1-007 R-5.6.2.2.1-007 R-5.7.2.1.1-008 R-5.6.2.2.1-008 R-5.7.2.1.1-009 R-5.6.2.2.1-009 R-5.7.2.1.1-010 R-5.6.2.2.1-010 R-5.7.2.1.1-011 R-5.6.2.2.1-011 R-5.7.2.1.1-012 R-5.6.2.2.1-012 R-5.7.2.1.1-013 R-5.6.2.2.1-013 R-5.7.2.1.1-014 R-5.6.2.2.1-014 R-5.7.2.1.1-001 R-5.6.2.2.1-001 5.7.2.1.2 MCPTT Emergency Group Call cancellation requirements R-5.7.2.1.2-001 R-5.6.2.2.2-001 R-5.7.2.1.2-002 R-5.6.2.2.2-002 R-5.7.2.1.2-003 R-5.6.2.2.2-003 R-5.7.2.1.2-004 R-5.6.2.2.2-004 R-5.7.2.1.2-005 R-5.6.2.2.2-005 5.7.2.2 Imminent Peril group call NA 5.7.2.2.1 Imminent Peril group call requirements R-5.7.2.2.1-001 R-5.6.2.3.1-001 R-5.7.2.2.1-002 R-5.6.2.3.1-002 R-5.7.2.2.1-003 R-5.6.2.3.1-003 R-5.7.2.2.1-004 R-5.6.2.3.1-004 R-5.7.2.2.1-005 R-5.6.2.3.1-005 R-5.7.2.2.1-006 R-5.6.2.3.1-006 R-5.7.2.2.1-007 R-5.6.2.3.1-007 R-5.7.2.2.1-008 R-5.6.2.3.1-008 R-5.7.2.2.1-009 R-5.6.2.3.1-009 5.7.2.2.2 Imminent Peril group call cancellation requirements R-5.7.2.2.2-001 R-5.6.2.3.2-001 R-5.7.2.2.2-002 R-5.6.2.3.2-002 R-5.7.2.2.2-003 R-5.6.2.3.2-003 R-5.7.2.2.2-004 R-5.6.2.3.2-004 5.7.2.3 MCPTT Emergency Private Call (with Floor Control) NA 5.7.2.3.1 MCPTT Emergency Private Call (with Floor Control) requirements NA 5.7.2.3.2 MCPTT Emergency Private Call (with Floor Control) cancellation requirements NA 5.7.2.4 MCPTT Emergency Alert NA 5.7.2.4.1 MCPTT Emergency Alert requirements R-5.7.2.4.1-001 R-5.6.2.4.1-001 R-5.7.2.4.1-002 R-5.6.2.4.1-002 R-5.7.2.4.1-003 R-5.6.2.4.1-003 R-5.7.2.4.1-004 R-5.6.2.4.1-004 R-5.7.2.4.1-005 R-5.6.2.4.1-005 R-5.7.2.4.1-006 R-5.6.2.4.1-006 R-5.7.2.4.1-007 R-5.6.2.4.1-007 R-5.7.2.4.1-008 R-5.6.2.4.1-008 R-5.7.2.4.1-009 R-5.6.2.4.1-009 R-5.7.2.4.1-010 R-5.6.2.4.1-010 R-5.7.2.4.1-011 R-5.6.2.4.1-011 R-5.7.2.4.1-012 R-5.6.2.4.1-012 5.7.2.4.2 MCPTT Emergency Alert cancellation requirements R-5.7.2.4.2-001 R-5.6.2.4.2-001 R-5.7.2.4.2-002 R-5.6.2.4.2-002 R-5.7.2.4.2-003 R-5.6.2.4.2-003 5.8 User ID R-5.8-001 R-5.7-001 R-5.8-002 R-5.7-002 R-5.8-003 R-5.7-003 5.9 MCPTT UE Management R-5.9-001 R-5.8-001 R-5.9-002 R-5.8-002 5.10 MCPTT User Profile R-5.10-001 R-5.9-001 R-5.10-002 R-5.9-002 5.11 Support for multiple devices R-5.11-001 R-5.10-001 R-5.11-002 R-5.10-002 5.12 Location R-5.12-001 R-5.11-001, R-5.11-002 R-5.12-002 R-5.11-003 R-5.12-003 R-5.11-004 R-5.12-004 R-5.11-005 R-5.12-005 R-5.11-006 R-5.12-006 R-5.11-007 R-5.12-007 R-5.11-008 R-5.12-008 R-5.11-009 R-5.12-009 R-5.11-010 R-5.12-010 R-5.11-011 R-5.12-012 R-5.11-012 R-5.12-013 R-5.11-013 R-5.12-014 R-5.11-014 R-5.12-015 R-5.11-015 5.13 Security R-5.13-001 R-5.12-001 R-5.13-002 R-5.12-002 R-5.13-003 R-5.12-003 R-5.13-004 R-5.12-004 R-5.13-005 R-5.12-005 R-5.13-006 R-5.12-006 R-5.13-007 R-5.12-007 R-5.13-008 R-5.12-008 R-5.13-009 R-5.12-009 R-5.13-010 R-5.12-010 R-5.13-011 R-5.12-011 R-5.13-012 R-5.12-012 R-5.13-013 R-5.12-013 5.14 Audio/voice quality R-5.14-001 R-5.13-001 5.15 Interactions between MCPTT Group calls and MCPTT Private Calls (with Floor Control) NA 5.16 Relay requirements R-5.16-001 R-5.14-001 R-5.16-002 R-5.14-002 R-5.16-003 R-5.14-003 5.17 Gateway Requirements R-5.17-001 R-5.15-001 5.18 Control and management by Mission Critical Organizations NA 5.18.1 Overview NA 5.18.2 General Requirements R-5.18.2-001 R-5.16.2-001 R-5.18.2-002 R-5.16.2-002 R-5.18.2-003 R-5.16.2-003 R-5.18.2-004 R-5.16.2-004 R-5.18.2-005 R-5.16.2-005 5.18.3 Operational visibility for Mission Critical Organizations R-5.18.3-001 R-5.16.3-001 5.19 General Administrative – groups and users R-5.19-001 R-5.17-001 R-5.19-002 R-5.17-002 R-5.19-003 R-5.17-003 R-5.19-004 R-5.17-004 R-5.19-005 R-5.17-005 R-5.19-006 R-5.17-006 R-5.19-007 R-5.17-007 R-5.19-008 R-5.17-008 6 MCPTT Service requirements specific to on-network use NA 6.1 General administrative – groups and users R-6.1-001 R-6.1-001 R-6.1-002 R-6.1-002 R-6.1-003 R-6.1-003 R-6.1-006 R-6.1-004 R-6.1-007 R-6.1-005 6.2 MCPTT calls NA 6.2.1 Commencement modes for MCPTT Group calls NA 6.2.2 Queuing R-6.2.2-001 R-6.2.2-001 R-6.2.2-002 R-6.2.2-002 R-6.2.2-003 R-6.2.2-003 R-6.2.2-004 R-6.2.2-004 R-6.2.2-005 R-6.2.2-005 R-6.2.2-006 R-6.2.2-006 6.2.3 Floor control NA 6.2.3.1 General aspects NA 6.2.3.2 Requesting permission to transmit NA 6.2.3.3 Override NA 6.2.3.3.1 General aspects NA 6.2.3.3.2 Override – one transmitting Participant NA 6.2.3.3.3 Override – simultaneously Transmitting MCPTT Group Members NA 6.2.3.4 Terminating permission to transmit NA 6.2.3.5 Transmit time limit NA 6.2.3.6 Audio cut-in designated MCPTT Groups NA 6.2.3.6.1 Overview NA 6.2.3.6.2 Requirements NA 6.2.3.6.3 Requesting permission to transmit NA 6.2.3.6.4 Terminating permission to transmit NA 6.2.3.6.5 Transmit time limit NA 6.2.3.7 MCPTT Groups designated for multi-talker control NA 6.2.3.7.1 Overview NA 6.2.3.7.2 General Aspects NA 6.2.3.7.3 Requesting permission to transmit NA 6.2.3.7.3 Requesting permission to transmit NA 6.2.3.7.4 Override NA 6.2.3.7.4.1 General Aspects NA 6.2.4 Call termination NA 6.3 General requirements R-6.3-001 R-6.3-001 R-6.3-002 R-6.3-002 R-6.3-003 R-6.3-003 R-6.3-004 R-6.3-004 6.4 General group call NA 6.4.1 General aspects R-6.4.1-001 R-6.4.1-001 6.4.2 Group status/information R-6.4.2-001 R-6.4.2-001 R-6.4.2-002 R-6.4.2-002 R-6.4.2-003 R-6.4.2-003 R-6.4.2-004 R-6.4.2-004 R-6.4.2-005 R-6.4.2-005 R-6.4.2-006 R-6.4.2-006 R-6.4.2-007 R-6.4.2-007 6.4.3 Identification R-6.4.3-001 R-6.4.3-001 R-6.4.3-002 R-6.4.3-002 6.4.4 Membership/affiliation R-6.4.4-001 R-6.4.4-001 R-6.4.4-002 R-6.4.4-002 6.4.5 Membership/affiliation list R-6.4.5-001 R-6.4.5-001 R-6.4.5-002 R-6.4.5-002 R-6.4.5-003 R-6.4.5-003 R-6.4.5-004 R-6.4.5-004 R-6.4.5-005 R-6.4.5-005 R-6.4.5-006 R-6.4.5-006 R-6.4.5-007 R-6.4.5-007 R-6.4.5-008 R-6.4.5-008 6.4.6 Authorized user remotely changes another MCPTT User’s affiliated and/or Selected MCPTT Group(s) NA 6.4.6.1 Mandatory change R-6.4.6.1-001 R-6.4.6.1-001 R-6.4.6.1-002 R-6.4.6.1-002 R-6.4.6.1-003 R-6.4.6.1-003 R-6.4.6.1-004 R-6.4.6.1-004 6.4.6.2 Negotiated change R-6.4.6.2-001 R-6.4.6.2-001 R-6.4.6.2-002 R-6.4.6.2-002 R-6.4.6.2-003 R-6.4.6.2-003 R-6.4.6.2-004 R-6.4.6.2-004 R-6.4.6.2-005 R-6.4.6.2-005 R-6.4.6.2-006 R-6.4.6.2-006 6.4.7 Prioritization R-6.4.7-001 R-6.4.7-001 R-6.4.7-002 R-6.4.7-002 R-6.4.7-003 R-6.4.7-003 R-6.4.7-004 R-6.4.7-004 6.4.8 Relay requirements R-6.4.8-001 R-6.4.8-001 6.4.9 Administrative R-6.4.9-001 R-6.4.9-001 R-6.4.9-003 R-6.4.9-002 R-6.4.9-004 R-6.4.9-003 R-6.4.9-007 R-6.4.9-004 R-6.4.9-006 R-6.4.9-005 R-6.4.9-007 R-6.4.9-006 6.5 Broadcast Group NA 6.5.1 General Broadcast Group Call R-6.5.1-001 R-6.5.1-001 R-6.5.1-002 R-6.5.1-002 6.5.2 Group-Broadcast Group (e.g., announcement group) R-6.5.2-001 R-6.5.2-001 6.5.3 User-Broadcast Group (e.g., System Call) R-6.5.3-001 R-6.5.3-001 6.6 Dynamic group management (i.e., dynamic reporting) NA 6.6.1 General dynamic regrouping R-6.6.1-001 R-6.6.1-001 R-6.6.1-002 R-6.6.1-002 R-6.6.1-003 R-6.6.1-003 R-6.6.1-004 R-6.6.1-004 R-6.6.1-005 R-6.6.1-005 R-6.6.1-006 R-6.6.1-006 6.6.2 Group Regrouping NA 6.6.2.1 Service Description NA 6.6.2.2 Requirements R-6.6.2.2-001 R-6.6.2.2-001 R-6.6.2.2-002 R-6.6.2.2-002 R-6.6.2.2-003 R-6.6.2.2-003 R-6.6.2.2-004 R-6.6.2.2-004 R-6.6.2.2-005 R-6.6.2.2-005 R-6.6.2.2-006 R-6.6.2.2-006 R-6.6.2.2-007 R-6.6.2.2-007 6.6.3 Temporary Group-Broadcast Group R-6.6.3-001 R-6.6.3-001 R-6.6.3-002 R-6.6.3-002 6.6.4 User regrouping NA 6.6.4.1 Service description NA 6.6.4.2 Requirements R-6.6.4.2-001 R-6.6.4.2-001 R-6.6.4.2-002 R-6.6.4.2-002 R-6.6.4.2-003 R-6.6.4.2-003 R-6.6.4.2-004 R-6.6.4.2-004 R-6.6.4.2-005 R-6.6.4.2-005 6.7 Private Call NA 6.7.0 Overview NA 6.7.1 General Requirements R-6.7.1-002 R-6.7.2-001 R-6.7.1-003 R-6.7.2-002 R-6.7.1-004 R-6.7.2-003 R-6.7.1-011 R-6.7.2-004 R-6.7.1-014 R-6.7.2-005 6.7.2 Administrative R-6.7.2-001 R-6.7.3-001 R-6.7.2-002 R-6.7.3-002 R-6.7.2-003 R-6.7.3-003 R-6.7.2-004 R-6.7.3-004 R-6.7.2-005 R-6.7.3-005 R-6.7.2-006 R-6.7.3-006 R-6.7.2-007 R-6.7.3-007 R-6.7.2-008 R-6.7.3-008 6.7.3 Prioritization R-6.7.3-001 R-6.7.4-001 R-6.7.3-002 R-6.7.4-002 R-6.7.3-003 R-6.7.4-003 R-6.7.3-004 R-6.7.4-004 R-6.7.3-005 R-6.7.4-005 R-6.7.3-006 R-6.7.4-006 R-6.7.3-007 R-6.7.4-007 6.7.4 Private Call (without Floor control) commencement requirements R-6.7.4-004 R-6.7.5-001 R-6.7.4-008 R-6.7.5-002 R-6.7.4-011 R-6.7.5-003 6.7.4a Private Call (with Floor control) commencement requirements NA 6.7.5 Private Call (without Floor control) termination R-6.7.5-001 R-6.7.6-001 R-6.7.5-003 R-6.7.6-002 6.7.6 Call back request requirements NA 6.8 MCPTT Priority Requirements NA 6.8.1 General R-6.8.1-001 R-6.8.1-001 R-6.8.1-003 R-6.8.1-002 R-6.8.1-004 R-6.8.1-003 R-6.8.1-005 R-6.8.1-004 R-6.8.1-006 R-6.8.1-005 R-6.8.1-007 R-6.8.1-006 R-6.8.1-008 R-6.8.1-007 R-6.8.1-009 R-6.8.1-008 R-6.8.1-010 R-6.8.1-009 R-6.8.1-011 R-6.8.1-010 R-6.8.1-012 R-6.8.1-011 R-6.8.1-013 R-6.8.1-012 R-6.8.1-014 R-6.8.1-013 R-6.8.1-015 R-6.8.1-014 R-6.8.1-016 R-6.8.1-015 R-6.8.1-017 R-6.8.1-016 6.8.2 3GPP system access controls R-6.8.2-001 R-6.8.2-001 6.8.3 3GPP system admission controls R-6.8.3-001 R-6.8.3-001 6.8.4 3GPP system scheduling controls R-6.8.4-001 R-6.8.4-001 6.8.5 UE access controls R-6.8.5-001 R-6.8.5-001 6.8.6 Application layer priorities NA 6.8.6.1 Overview NA 6.8.6.2 Requirements R-6.8.6.2-001 R-6.8.7.2-001 R-6.8.6.2-002 R-6.8.7.2-002 R-6.8.6.2-003 R-6.8.7.2-003 R-6.8.6.2-005 R-6.8.7.2-004 R-6.8.6.2-006 R-6.8.7.2-005 6.8.7 Call types based on priorities NA 6.8.7.1 MCPTT Emergency Group Call requirements R-6.8.7.1-001 R-6.8.8.1-001 R-6.8.7.1-002 R-6.8.8.1-002 R-6.8.7.1-003 R-6.8.8.1-003 R-6.8.7.1-004 R-6.8.8.1-004 6.8.7.2 MCPTT Emergency Private Call (with Floor control) requirements NA 6.8.7.3 Imminent Peril group call requirements R-6.8.7.3-001 R-6.8.8.3-001 R-6.8.7.3-002 R-6.8.8.3-002 R-6.8.7.3-003 R-6.8.8.3-003 6.8.7.4 MCPTT Emergency Alert NA 6.8.7.4.1 Requirements R-6.8.7.4.1-001 R-6.8.8.4.1-001 R-6.8.7.4.1-002 R-6.8.8.4.1-002 R-6.8.7.4.1-003 R-6.8.8.4.1-003 R-6.8.7.4.1-004 R-6.8.8.4.1-004 R-6.8.7.4.1-005 R-6.8.8.4.1-005 R-6.8.7.4.1-006 R-6.8.8.4.1-006 6.8.7.4.2 MCPTT Emergency Alert cancellation requirements R-6.8.7.4.2-001 R-6.8.8.4.2-001 R-6.8.7.4.2-002 R-6.8.8.4.2-002 6.9 IDs and aliases R-6.9-001 R-6.9-001 R-6.9-002 R-6.9-002 R-6.9-003 R-6.9-003 R-6.9-004 R-6.9-004 6.10 User Profile Management R-6.10-001 R-6.10-001 R-6.10-002 R-6.10-002 R-6.10-003 R-6.10-003 R-6.10-004 R-6.10-004 6.11 Support for multiple devices R-6.11-001 R-6.11-001 R-6.11-002 R-6.11-002 R-6.11-003 R-6.11-003 6.12 Location R-6.12-001 R-6.12-001 R-6.12-002 R-6.12-002 R-6.12-003 R-6.12-003 R-6.12-004 R-6.12-004 R-6.12-005 R-6.12-005 R-6.12-006 R-6.12-006 R-6.12-007 R-6.12-007 6.13 Security NA 6.13.1 Overview NA 6.13.2 Cryptographic protocols R-6.13.2-001 R-6.13.2-001 R-6.13.2-002 R-6.13.2-002 R-6.13.2-003 R-6.13.2-003 6.13.3 Authentication R-6.13.3-001 R-6.13.3-001 6.13.4 Access control R-6.13.4-001 R-6.13.4-001 R-6.13.4-002 R-6.13.4-002 R-6.13.4-003 R-6.13.4-003 R-6.13.4-004 R-6.13.4-004 R-6.13.4-005 R-6.13.4-005 R-6.13.4-006 R-6.13.4-006 R-6.13.4-007 R-6.13.4-007 R-6.13.4-008 R-6.13.4-008 R-6.13.4-009 R-6.13.4-009 R-6.13.4-010 R-6.13.4-010 6.13.5 Regulatory Issues R-6.13.5-001 R-6.13.5-001 6.14 Interactions for MCPTT Group Calls and MCPTT Private Calls R-6.14-001 R-6.14-001 R-6.14-002 R-6.14-002 6.15 Audio MCPTT call performance NA 6.16 Additional services for MCPTT calls NA 6.16.1 Discreet listening capabilities R-6.16.1-001 R-6.15.1-001 6.16.2 Ambient listening NA 6.16.2.1 Overview of ambient listening NA 6.16.2.2 Ambient listening requirements NA 6.16.2.2.1 General Ambient Listening Requirements R-6.16.2.2.1-001 R-6.15.2.2.1-001 R-6.16.2.2.1-002 R-6.15.2.2.1-002 R-6.16.2.2.1-003 R-6.15.2.2.1-003 6.16.2.2.2 Remotely initiated ambient listening requirements R-6.16.2.2.2-001 R-6.15.2.2.2-001 R-6.16.2.2.2-002 R-6.15.2.2.2-002 6.16.2.2.3 Locally initiated ambient listening requirements R-6.16.2.2.3-001 R-6.15.2.2.3-001 R-6.16.2.2.3-002 R-6.15.2.2.3-002 6.16.3 Remotely initiated MCPTT call NA 6.16.3.1 Overview NA 6.16.3.2 Requirements R-6.16.3.2-003 R-6.15.3.2-003 R-6.16.3.2-004 R-6.15.3.2-004 R-6.16.3.2-002 R-6.15.3.2-002 R-6.16.3.2-001 R-6.15.3.2-001 6.16.4 Recording and audit requirements R-6.16.4-001 R-6.15.4-001 R-6.16.4-002 R-6.15.4-002 R-6.16.4-005 R-6.15.4-005 R-6.16.4-006 R-6.15.4-006 R-6.16.4-007 R-6.15.4-007 R-6.16.4-008 R-6.15.4-008 R-6.16.4-009 R-6.15.4-009 R-6.16.4-010 R-6.15.4-010 R-6.16.4-003 R-6.15.4-003 R-6.16.4-004 R-6.15.4-004 6.17 Interaction with telephony services R-6.17-001 R-6.16-001 R-6.17-003 R-6.16-002 6.18 Interworking NA 6.18.1 Non-3GPP access R-6.18.1-001 R-6.17.1-001 6.18.2 Interworking between MCCore systems R-6.18.2-001 R-6.17.2-001 R-6.18.2-002 R-6.17.2-002 R-6.18.2-003 R-6.17.2-003 R-6.18.2-004 R-6.17.2-004 R-6.18.2-005 R-6.17.2-005 R-6.18.2-006 R-6.17.2-006 R-6.18.2-007 R-6.17.2-007 6.18.3 Interworking with non-3GPP PTT systems NA 6.18.3.1 Overview NA 6.18.3.2 Project 25 NA 6.18.3.3 TETRA NA 6.18.3.4 Legacy land mobile radio NA 6.18.4 GSM-R NA 6.18.4.1 Overview NA 6.18.4.2 Requirements NA 6.19 MCPTT coverage extension using ProSe UE-to-Network Relays R-6.19-001 R-6.18-001 R-6.19-002 R-6.18-002 R-6.19-003 R-6.18-003 R-6.19-004 R-6.18-004 R-6.19-005 R-6.18-005 R-6.19-006 R-6.18-006 7 MCPTT Service Requirements specific to off-network use NA 7.1 Off-network Push To Talk overview NA 7.2 General off-network MCPTT requirements R-7.2-001 R-7.2-001 R-7.2-002 R-7.2-002 R-7.2-003 R-7.2-003 R-7.2-004 R-7.2-004 R-7.2-005 R-7.2-005 7.3 Floor control NA 7.3.1 General Aspects NA 7.3.2 Requesting permission to transmit NA 7.3.3 Override NA 7.3.4 Terminating permission to transmit NA 7.3.5 Transmit time limit NA 7.4 Call Termination R-7.4-003 R-7.4-001 R-7.4-004 R-7.4-002 R-7.4-005 R-7.4-003 R-7.4-006 R-7.4-004 7.5 Broadcast Group R-7.5-001 R-7.5-001 R-7.5-002 R-7.5-002 7.6 Dynamic group management (i.e., dynamic regrouping) NA 7.7 MCPTT priority requirements R-7.7-001 R-7.6-001 R-7.7-003 R-7.6-002 7.8 Call types based on priorities NA 7.8.1 MCPTT Emergency Group Call requirements R-7.8.1-001 R-7.7.1-001 R-7.8.1-002 R-7.7.1-002 R-7.8.1-003 R-7.7.1-003 7.8.2 MCPTTEmergency Group Call cancellation requirements R-7.8.2-001 R-7.7.2-001 7.8.3 Imminent Peril Call NA 7.8.3.1 Imminent Peril group call requirements R-7.8.3.1-001 R-7.7.3.1-001 R-7.8.3.1-002 R-7.7.3.1-002 R-7.8.3.1-003 R-7.7.3.1-003 R-7.8.3.1-004 R-7.7.3.1-004 R-7.8.3.1-005 R-7.7.3.1-005 7.8.3.2 Imminent Peril group call cancellation requirements R-7.8.3.2-001 R-7.7.3.2-001 R-7.8.3.2-002 R-7.7.3.2-002 7.9 Location R-7.9-001 R-7.8-001 7.10 Security R-7.10-001 R-7.9-001 R-7.10-002 R-7.9-002 7.11 Audio MCPTT Call performance NA 7.11.1 MCPTT Access time and Mouth-to-ear latency NA 7.11.1.1 General overview NA 7.11.1.2 Requirements NA 7.11.2 Late call entry performance NA 7.11.2.1 General overview NA 7.11.2.2 Requirements NA 7.11.3 Audio/voice quality NA 7.12 Off-network MCPTT operations R-7.12-001 R-7.10-001 R-7.12-002 R-7.10-002 R-7.12-003 R-7.10-003 7.13 Off-network UE functionality R-7.13-001 R-7.11-001 R-7.13-002 R-7.11-002 R-7.13-003 R-7.11-003 7.14 Switching to off-network MCPTT R-7.14-001 R-7.13-001 R-7.14-002 R-7.13-002 R-7.14-003 R-7.13-003 7.15 Off-network recording and audit requirements R-7.15-001 R-7.14-001 R-7.15-002 R-7.14-002 7.16 Off-network UE-to-UE relay NA 7.16.1 Private Communications R-7.16.1-001 R-7.15.1-001 R-7.16.1-002 R-7.15.1-002 R-7.16.1-003 R-7.15.1-003 7.16.2 Group Communications R-7.16.2-001 R-7.15.2-001 R-7.16.2-002 R-7.15.2-002 Annex B (informative): Bibliography - 3GPP TS 22.115: "Service aspects; Charging and billing". Annex C (informative): MCPTT scalability guide The MCPTT Service might support an authorized MCPTT UE to be an MCPTT member of at least 5,000 MCPTT Groups. The MCPTT Service might support a minimum of 500,000 MCPTT Groups. The MCPTT Service might support MCPTT Group membership from two MCPTT Users to all the MCPTT Users signed on the MCPTT system. The MCPTT Service might support an MCPTT Group Call where all the Participants are located in one cell of the MCPTT system. The MCPTT Service might support an MCPTT Group Call with one or more Participants located in every cell of the MCPTT system. The MCPTT Service might support a range of 36 to 150 simultaneous MCPTT Group Calls in every cell of the MCPTT system per regional regulatory requirement. The MCPTT Service might support a minimum of 2000 MCPTT Users within an MCPTT Group or a combination of different MCPTT Groups, in every cell of the MCPTT system. NOTE: The concurrent number of Participants in a cell is subject to radio capacity limitation in a cell per operator policy. Annex D (informative): Change history Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New Work Item SP-66 SP-140844 Raised by MCC to version 13.0.0 following SA's approval 2.1.0 13.0.0 SP-66 - - Correction of Figure 4.6.1-1 (previously corrupted) and of some typos, including: consistent use of capital and spaces instead of hyphens in "Push To Talk", removal of the requirement numbering for the three paragraph of sections 6.6.2.1 and 6.6.4.1 since they are not requirements 13.0.0 13.0.1 SP-67 SP-150040 S1-150011 22.179 1 - Rel-13 F Replacement of Home and Visited by Primary and Partner 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150225 22.179 2 1 Rel-13 F Completion of application of S1-144278 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150226 22.179 3 1 Rel-13 F Clarification of number and types of Private Calls 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150228 22.179 5 1 Rel-13 F Completion of application of S1-144570 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150016 22.179 6 - Rel-13 F Improper use of 'emergency' 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150230 22.179 7 2 Rel-13 D Correct use of MCPTT terminology 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150229 22.179 8 1 Rel-13 F Clarifying KPI requirement 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150019 22.179 9 - Rel-13 D Wording correction 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150021 22.179 11 - Rel-13 F Change the title of TS 22.179 to align with MCPTT WID and agreed contribution S1-144232 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150022 22.179 12 - Rel-13 D Changing Ues to UEs 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150023 22.179 13 - Rel-13 D Editorial clean ups 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150342 22.179 14 2 Rel-13 F Correction of type of Private Calls supported in for both on and off the network use. 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150025 22.179 15 - Rel-13 F Clarification of dedicated MCPTT Group type used for Imminent Peril Group call communication by MCPTT User 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150026 22.179 16 - Rel-13 F Replacement of personality management with user profile management 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150027 22.179 17 - Rel-13 F Modify text in first sentence of third paragraph for clause 7.1 Off-Network Push-to-Talk overview. 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150028 22.179 18 - Rel-13 F Replacement of clause 5.14 title Audio/ video quality with Audio/ voice quality. 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150232 22.179 19 1 Rel-13 F Convert 2nd sentence of 5th requirement in clause 6.2.4 Call Termination into a new requirement 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150309 22.179 20 2 Rel-13 F Move two requirements from clause 6.1 General Administrative -groups and users into common clause 5.19 General Administrative -groups and users. 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150234 22.179 21 1 Rel-13 B Charging for MCPTT usage 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150092 22.179 22 - Rel-13 F Reinstatement of MCPTT User Profile 13.0.1 13.1.0 MCPTT-SA1 SP-67 SP-150040 S1-150093 22.179 23 - Rel-13 F Fix improper multiple requirements 13.0.1 13.1.0 MCPTT-SA1 SP-67 SP-150040 S1-150094 22.179 24 - Rel-13 F Remove implementation-specific requirement for default value 13.0.1 13.1.0 MCPTT-SA1 SP-67 SP-150040 S1-150236 22.179 26 1 Rel-13 F CR- to clarify requirements in 6.4.9 and 6.2.4. 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150265 22.179 28 1 Rel-13 F CR to clarify what call type refers to in 6.2.3.3.1 13.0.1 13.1.0 MCPTT SP-67 SP-150040 S1-150107 22.179 30 - Rel-13 D Separation of supplementary service, callback, requirements 13.0.1 13.1.0 MCPTT SP-68 SP-150354 - 22.179 31 1 Rel-13 F Clarification on the update and use of codecs in MCPTT 13.1.0 13.2.0 MCPTT SP-68 SP-150355 - 22.179 32 1 Rel-13 F Clarification on Broadcast Groups Off-Network Requirement R-7.5-002 13.1.0 13.2.0 MCPTT SP-70 SP-150750 S1-154482 22.179 0033 1 Rel-13 F Edits, formatting, and style corrections 13.2.0 13.3.0 MCPTT SP-70 SP-150750 S1-154483 22.179 0034 1 Rel-13 F MCPTT Emergency Group Call correction 13.2.0 13.3.0 MCPTT SP-70 SP-150750 S1-154546 22.179 0035 1 Rel-13 F KPI 4 when MBMS is used 13.2.0 13.3.0 MCPTT SP-71 SP-160103 S1-160313 22.179 0036 1 Rel-14 C Mission Critical Push to Talk over LTE Realignment (MCPTT-R) 13.3.0 14.0.0 MCImp-MCPTTR SP-72 SP-160359 S1-161580 22.179 38 3 Rel-14 B Inclusion of “first-to-answer” commencement mode for private calls 14.0.0 14.1.0 MCPTT SP-72 SP-160391 - 22.179 40 Rel-14 B Introduction of Audio cut-in requirements in MCPTT 14.0.0 14.1.0 MCImp-MCPTTR SP-72 SP-160359 S1-161626 22.179 37 2 Rel-14 C Mission Critical Push to Talk over LTE for Realignment (MCPTT-R) 14.0.0 14.1.0 MCPTT SP-73 SP-160542 S1-162402 22.179 0043 1 Rel-14 F Remove definitions for participant and participant type in MCPTT TS 22.179 that are being added to MCCoRe TS 22.280. 14.1.0 14.2.0 MCImp-MCPTTR SP-73 SP-160542 S1-162404 22.179 0044 1 Rel-14 D In MCPTT TS 22.179 Provide editorial changes to sub-clause 6.6.2.2. 14.1.0 14.2.0 MCImp-MCPTTR SP-73 SP-160542 S1-162405 22.179 0045 1 Rel-14 F Remove definition for Mission Critical Organization in MCPTT TS 22.179 that was added to MCCoRe TS 22.280 as a common definition. 14.1.0 14.2.0 MCImp-MCPTTR SP-73 SP-160542 S1-162400 22.179 0046 1 Rel-14 F Clarifications and corrections to audio cut-in 14.1.0 14.2.0 MCImp-MCPTTR SP-74 SP-160890 S1-163011 22.179 0047 Rel-14 D Editorial change to MCPTT TS 22.179 sub-clause 6.2.3.6.2 14.2.0 14.3.0 MCImp-MCPTTR SP-74 SP-160890 S1-163012 22.179 0048 Rel-14 D Editorial changes to Annex A1 sub-clause 6.2.3.6 14.2.0 14.3.0 MCImp-MCPTTR SP-76 SP-170445 S1-172430 22.179 0052 6 Rel-15 B multi-talker group call 14.3.0 15.0.0 MONASTERY SP-77 SP-170696 S1-173507 22.179 0054 2 Rel-15 F Clarify MCPTT group in 6.2.3.7 15.0.0 15.1.0 MONASTERY SP-77 SP-170696 S1-173506 22.179 0055 3 Rel-15 F Correction on behavior of groups configured for multi talker control wrt groups using public safety floor control 15.0.0 15.1.0 MONASTERY SP-78 SP-170985 S1-174039 22.179 0057 Rel-15 F Removing 'over LTE' from the title of the specification 15.1.0 15.2.0 MCOver SP-78 SP-170985 S1-174541 22.179 0058 1 Rel-15 F Updates to the wording in the specification to clarify that the requirements are applicable from LTE onwards 15.1.0 15.2.0 MCOver SP-78 SP-170997 S1-174424 22.179 0061 3 Rel-16 B Addition of requirement on interworking with SCP in GSM-R 15.2.0 16.0.0 MONASTERY2 SP-79 SP-180134 S1-180433 22.179 0062 1 Rel-16 B Adding more functionality to interworking between FRMCS and GSM-R 16.0.0 16.1.0 MONASTERY2 SP-80 SP-180310 S1-181707 22.179 0064 4 Rel-16 F Interworking between MCX Service system and GSM-R 16.1.0 16.2.0 MONASTERY2 SP-80 SP-180310 S1-181708 22.179 0063 2 Rel-16 B Adding functionality to 22.179 to support assured voice communication 16.1.0 16.2.0 MONASTERY2 SP-81 SP-180757 S1-182565 22.179 0066 1 Rel-16 B Enhancement for interworking of group communication between FRMCS and GSM-R 16.2.0 16.3.0 MONASTERY2 SP-81 SP-180761 S1-182613 22.179 0065 1 Rel-16 B Application of MCPTT to maritime usage 16.2.0 16.3.0 MARCOM Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2018-12 SP-82 SP-181000 0067 1 C Addition of new Group Call Commencement Modes 16.4.0 2018-12 SP-82 SP-181000 0068 1 B Move interworking of functional alias from MCPTT to MCCoRe TS, MCPTT part 16.4.0 2019-03 SA#83 SP-190084 0069 B Add forwarding for private calls 16.5.0 2019-12 SA#86 SP-191036 0073 1 C Group and Private call setup KPIs 17.0.0 2022-03 SP#95e SP-220081 0075 1 F Clarification on use of MCPTT Late call entry KPIs 17.1.0 2023-06 SA#100 - CR 0076r2 in SP-230529 creates Rel-19 from Rel-17. Version 18.0.0 is a technical-content duplicate of v.17.1.0. created for administrative reasons. 18.0.0 2023-06 SA#100 SP-230529 0076 2 C Usage of multi-talker control for Ad hoc Group Emergency Voice Communications 19.0.0 2023-09 SA#101 SP-231022 0077 1 C Enhancement of multi-talker control 19.1.0 2023-12 SA#102 SP-231395 0078 2 C Enhancement of multi-talker control due to updates of FRMCS functional requirements 19.2.0 2024-09 SA#105 SP-241145 0081 1 F Enhancement of interworking with GSM-R using Ad hoc Group Calls 19.3.0
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
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] NGMN 5G White Paper v1.0, February 2015.
[3] 3GPP TS 22.011: "Service accessibility".
[4] Void
[5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6] 3GPP TS 22.101: "Service aspects; Service principles".
[7] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service (MBMS)".
[8] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services".
[9] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios".
[10] NGMN, "Recommendations for NGMN KPIs and Requirements for 5G", June 2016
[11] 3GPP TS 22.115: "Service aspects; Charging and billing".
[12] Void
[13] Soriano, R., Alberto, M., Collazo, J., Gonzales, I., Kupzo, F., Moreno, L., & Lorenzo, J. OpenNode. Open Architecture for Secondary Nodes of the Electricity Smartgrid. In Proceedings CIRED 2011 21st International Conference on Electricity Distribution, CD1. June 2011.
[14] North American Electric Reliability Council. Frequently Asked Questions (FAQs) Cyber Security Standards CIP–002–1 through CIP–009–1. Available: http://www.nerc.com/docs/standards/sar/Revised_CIP-002-009_FAQs_06Mar06.pdf. 2006.
[15] McTaggart, Craig, et al. "Improvements in power system integrity protection schemes". Developments in Power System Protection (DPSP 2010). Managing the Change, 10th IET International Conference on. IET, 2010.
[16] IEEE Power Engineering Society – Power System Relaying Committee – System Protection Subcommittee Working Group C-6. Wide Area Protection and Emergency Control.
[17] Begovic, Miroslav, et al. "Wide-area protection and emergency control". Proceedings of the IEEE 93.5, pp. 876-891, 2005.
[18] ITU-T Recommendation G.1000 "Communications quality of service: A framework and definitions".
[19] IEC 61907, "Communication network dependability engineering".
[20] NIST, "Framework for Cyber-Physical Systems", 2016.
[21] 3GPP TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".
[22] 3GPP TS 22.262: "Message Service within the 5G System".
[23] 3GPP TS 22.289: "Mobile Communication System for Railways".
[24] 3GPP TS 22.071: "Location Services".
[25] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[26] 3GPP TS 22.125: "Unmanned Aerial System (UAS) support in 3GPP".
[27] Void
[28] 3GPP TS 22.263: "Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)".
[29] Void
[30] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT)".
[31] IEEE 1588-2019, IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems.
[32] IEC 61850-9-3-2016 - IEC/IEEE International Standard - Communication networks and systems for power utility automation – Part 9-3: Precision time protocol profile for power utility automation.
[33] 3GPP TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN"
[34] ATIS-0900005: "Technical Report on GPS Vulnerability", https://access.atis.org/apps/group_public/download.php/36304/ATIS-0900005.pdf
[35] European Commission, Regulatory Technical Standard 25. Level of accuracy of business clocks
https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25_en.pdf (annex https://ec.europa.eu/finance/securities/docs/isd/mifid/rts/160607-rts-25-annex_en.pdf)
[36] 5G-ACIA, "Exposure of 5G capabilities for Connected Industries and Automation Applications", 5G-ACIA white pater, February 2021, https://5g-acia.org/wp-content/uploads/2021/04/5G-ACIA_ExposureOf5GCapabilitiesForConnectedIndustriesAndAutomationApplications.pdf
[37] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services".
[38] ITU-T, "Technology Watch Report: The Tactile Internet", August 2014.
[39] D. Soldani, Y. Guo, B. Barani, P. Mogensen, I. Chih-Lin, S. Das, "5G for ultra-reliable low-latency communications". IEEE Network. 2018 Apr 2; 32(2):6-7.
[40] 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.
[41] Altinsoy, M. E., Blauert, J., & Treier, C., "Inter-Modal Effects of Non-Simultaneous Stimulus Presentation," A. Alippi (Ed.), Proceedings of the 7th International Congress on Acoustics, Rome, Italy, 2001.
[42] Hirsh I.J., and Sherrrick C.E, 1961. J. Exp. Psychol 62, 423-432
[43] Altinsoy, M.E. (2012). "The Quality of Auditory-Tactile Virtual Environments," Journal of the Audio Engineering Society, Vol. 60, No. 1/2, pp. 38-46, Jan.-Feb. 2012.
[44] M. Di Luca and A. Mahnan, "Perceptual Limits of Visual-Haptic Simultaneity in Virtual Reality Interactions," 2019 IEEE World Haptics Conference (WHC), 2019, pp. 67-72, doi: 10.1109/WHC.2019.8816173.
[45] K. Antonakoglou et al., "Toward Haptic Communications Over the 5G Tactile Internet", IEEE Communications Surveys & Tutorials, 20 (4), 2018.
[46] ETSI GS OEU 020 (v1.1.1): "Operational energy Efficiency for Users (OEU); Carbon equivalent Intensity measurement; Operational infrastructures; Global KPIs; Global KPIs for ICT Sites".
[47] 3GPP TS 28.310: "Management and orchestration; Energy efficiency of 5G".
[48] ETSI EN 303 472: "Environmental Engineering (EE); Energy Efficiency measurement methodology and metrics for RAN equipment".
[49] 3GPP TS 32.299: " Telecommunication management; Charging management; Diameter charging applications".
[50] N. Nonaka et al., "Experimental Trial aboard Shinkansen Test Train Running at 360 km/h for 5G Evolution," 2022 IEEE 95th Vehicular Technology Conference: (VTC2022-Spring), Helsinki, Finland, 2022.
[51] 3GPP TS 22.137: " Service requirements for Integrated Sensing and Communication ".
[52] 3GPP TS 22.369: " Service requirements for Ambient power-enabled IoT ".
[53] 3GPP TS 22.156: "Mobile Metaverse Services".
[54] IEEE Std 802.1Q: "IEEE Standard for Local and Metropolitan Area Networks---Bridges and Bridged Networks".
[55] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) Multimedia core network Subsystem ".
[56] ITU-T E.800: "Definitions of terms related to quality of service".
[57] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8177735/.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
3 Definitions, symbols and abbreviations
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions 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].
5G enhanced positioning area: a subset of the 5G positioning service area that is assumed to be provided with additional infrastructure or deploy a particular set of positioning technologies to enhance positioning services.
NOTE 1: The enhanced positioning service area represents for example a factory plant, a dense urban area, an area along a road or railway track, a tunnel and covers both indoor and outdoor environments.
5G LAN-type service: a service over the 5G system offering private communication using IP and/or non-IP type communications.
5G LAN-virtual network: a virtual network capable of supporting 5G LAN-type service.
5G satellite access network: 5G access network using at least one satellite.
5G positioning service area: a service area where positioning services would solely rely on infrastructures and positioning technologies that can be assumed to be present anywhere where 5G is present (e.g. a country-wide operator-supplied 5G network, GNSS, position/motion sensors).
NOTE 2: This includes both indoor and any outdoor environments.
active communication: a UE is in active communication when it has one or more connections established. A UE may have any combination of PS connections (e.g. PDP contexts, active PDN connections).
activity factor: percentage value of the amount of simultaneous active UEs to the total number of UEs where active means the UEs are exchanging data with the network.
Ambient IoT device: An ambient power-enabled Internet of Things device is an IoT device powered by energy harvesting, being either battery-less or with limited energy storage capability (e.g., using a capacitor).
aggregated QoS: QoS requirement(s) that apply to the traffic of a group of UEs.
area traffic capacity: total traffic throughput served per geographic area.
authorised administrator: a user or other entity authorised to partially configure and manage a network node in a CPN (e.g. a PRAS, or eRG) or a PIN element in a PIN.
carbon emission: quantity of equivalent carbon dioxide emitted (e.g. kg of CO2 equivalent).
carbon intensity: quantity of CO2 equivalent emission per unit of final energy consumption for an operational period of use. [46]
communication service availability: percentage value of the amount of time the end-to-end communication service is delivered according to a specified QoS, divided by the amount of time the system is expected to deliver the end-to-end service.
NOTE 3: The end point in "end-to-end" is the communication service interface.
NOTE 4: The communication service is considered unavailable if it does not meet the pertinent QoS requirements. For example, the communication service is unavailable if a message is not correctly received within a specified time, which is the sum of maximum allowed end-to-end latency and survival time.
Customer Premises Network: a network located within a premise (e.g. a residence, office or shop), which is owned, installed and/or (at least partially) configured by the customer of a public network operator.
direct device connection: the connection between two UEs without any network entity in the middle.
direct network connection: one mode of network connection, where there is no relay UE between a UE and the 5G network.
Disaster Condition: This is the condition that a government decides when to initiate and terminate, e.g. a natural disaster. When this condition applies, users may have the opportunity to mitigate service interruptions and failures.
Disaster Inbound Roamer: A user that (a) cannot get service from the PLMN it would normally be served by, due to failure of service during a Disaster Condition, and (b) is able to register with other PLMNs.
Disaster Roaming: This is the special roaming policy that applies during a Disaster Condition.
DualSteer device: A device supporting traffic steering and switching of user data (for different services) across two 3GPP access networks; it can be a single UE, in case of non-simultaneous data transmission over the two networks, or two separate UEs in case of simultaneous data transmission over the two networks.
end-to-end latency: the time that it takes to transfer a given piece of information from a source to a destination, measured at the communication interface, from the moment it is transmitted by the source to the moment it is successfully received at the destination.
energy availability: the remaining amount of energy (e.g. in kWh) locally available for consumption. For devices, network elements and functions, energy availability may be limited and/or intermittent, in particular when relying on batteries and/or renewable energy sources (e.g. off-grid base stations, satellites etc) or during power grid heavy load or disruptions.
energy capacity: the maximum amount of energy (e.g. in kWh) that can be locally available for consumption (either locally produced and/or stored) by a device or a network element or function.
energy charging rate: a means of determining the energy consumption consequence (use of energy credit) associated with charging events.
energy credit: a quantity of energy credit associated with the subscriber that can be used for credit control by the 5G system.
energy rationing: A situation in which the availability of energy either across the network or at a particular network element or function is limited or reduced.
energy-related characteristics: information which characterize the energy to power the operator’s network in terms of energy consumption, energy supply mix, carbon footprint, energy capacity and availability conditions.
NOTE: Which energy-related characteristics are relevant depends on the scenario.
energy state: state of a cell, a network element and/or a network function with respect to energy, e.g. (not) energy saving states, which are defined in TS 28.310 [47].
energy supply mix: the combination of the various energy sources (i.e. renewable and not) used to meet energy needs of a device or a network element or function.
evolved Residential Gateway: a gateway between the public operator network (fixed/mobile/cable) and a customer premises network.
holdover: A clock A, previously synchronized/syntonized to another clock B (normally a primary reference or a Master Clock) but whose frequency is determined in part using data acquired while it was synchronized/syntonized to B, is said to be in holdover or in the holdover mode as long as it is within its accuracy requirements.
NOTE 4a: holdover is defined in [31]
Holdover time: the time period that is available to repair the first priority timing source when it is lost (e.g., when the primary GNSS reference is lost). During this period the synchronization accuracy requirement should be guaranteed, e.g., by means of defining multiple synchronization references.
Hosted Service: a service containing the operator's own application(s) and/or trusted third-party application(s) in the Service Hosting Environment, which can be accessed by the user.
Hosting NG-RAN Operator: the operator that has operational control of a Shared NG-RAN.
NOTE 4b: Hosting NG-RAN Operator is a Hosting RAN Operator.
Hosting RAN Operator: as defined in 3GPP TS 22.101 [6].
hybrid access: access consisting of multiple different access types combined, such as fixed wireless access and wireline access.
indirect network connection: one mode of network connection, where there is a relay UE between a UE and the 5G network.
Indirect Network Sharing: a type of NG-RAN Sharing in which the communication between the Shared NG-RAN and the Participating Operator’s core network is routed through the Hosting NG-RAN Operator’s core network.
IoT device: a type of UE which is dedicated for a set of specific use cases or services and which is allowed to make use of certain features restricted to this type of UEs.
NOTE 5: An IoT device may be optimized for the specific needs of services and application being executed (e.g. smart home/city, smart utilities, e-Health and smart wearables). Some IoT devices are not intended for human type communications.
maximum energy consumption: a policy establishing an upper bound on the quantity of energy consumption [47] by the 5G system in a specific period of time, or space, e.g. energy consumption inside a given service area.
maximum energy credit limit: a policy establishing an upper bound on the aggregate quantity of energy consumption by the 5G system to provide services to a specific subscriber, e.g. in kilowatt hours.
NOTE: The terms maximum energy credit limit is distinct from 'maximum energy consumption' because the credit limit is a total amount of energy consumed, where maximum energy consumption is a limit to the consumption in a given interval of time.
network slice: a set of network functions and corresponding resources necessary to provide the required telecommunication services and network capabilities.
NG-RAN: a radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
NG-RAN Sharing: the sharing of NG-RAN among a number of operators.
non-public network: a network that is intended for non-public use.
NR: the new 5G radio access technology.
Participating NG-RAN Operator: authorized operator that is using Shared NG-RAN resources provided by a Hosting NG-RAN Operator.
NOTE 5a: Participating NG-RAN Operator is a Participating Operator.
Participating Operator: as defined in 3GPP TS 22.101 [6].
Personal IoT Network: A configured and managed group of at least one UE PIN Element and one or more PIN Element that communicate with each other.
PIN Element: UE or non-3GPP device that can communicate within a PIN.
PIN direct connection: the connection between two PIN Elements without any 3GPP RAN or core network entity in the middle.
NOTE 5A: A PIN direct connection could internally be relayed by other PIN Elements.
NOTE 5B: When a PIN direct connection is between two PIN Elements that are UEs this direct connection is typically known as a direct device connection.
PIN Element with Gateway Capability: a UE PIN Element that has the ability to provide connectivity to and from the 5G network for other PIN Elements.
NOTE 5C: A PIN Element can have both PIN management capability and Gateway Capability.
PIN Element with Management Capability: A PIN Element with capability to manage the PIN.
positioning service availability: percentage value of the amount of time the positioning service is delivering the required position-related data within the performance requirements, divided by the amount of time the system is expected to deliver the positioning service according to the specification in the targeted service area.
proximity-based work task offloading: a relay UE receives data from a remote UE via direct device connection and performs calculation of a work task for the remote UE. The calculation result can be further sent to network server.
positioning service latency: time elapsed between the event that triggers the determination of the position-related data and the availability of the position-related data at the system interface.
Premises Radio Access Station: a base station installed at a customer premises network.
priority service: a service that requires priority treatment based on regional/national or operator policies.
private communication: a communication between two or more UEs belonging to a restricted set of UEs.
private network: an isolated network deployment that does not interact with a public network.
private slice: a dedicated network slice deployment for the sole use by a specific third-party.
ProSe UE-to-UE Relay: a Public Safety ProSe-enabled UE that acts as a relay between two other Public Safety ProSe-enabled UEs.
Ranging: refers to the determination of the distance between two UEs and/or the direction of one UE from the other one via direct device connection.
relative positioning: relative positioning is to estimate position relatively to other network elements or relatively to other UEs.
reliability: in the context of network layer packet transmissions, percentage value of the packets successfully delivered to a given system entity within the time constraint required by the targeted service out of all the packets transmitted.
renewable energy: energy from renewable sources as energy from renewable non-fossil sources, namely wind, solar, aerothermal, geothermal, hydrothermal and ocean energy, hydropower, biomass, landfill gas, sewage treatment plant gas and biogases
NOTE 2: This definition was taken from [48].
Resilient Notification Service: a highly reliable service that delivers notifications directly to user devices, such as smartphones, when in poor conditions in satellite access
satellite: a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO) typically at an altitude between 300 km to 1 500 km, Medium-Earth Orbit (MEO) typically at an altitude between 7 000 to 25 000 km, or Geostationary satellite Earth Orbit (GEO) at 35 786 km altitude.
satellite access: direct connectivity between the UE and the satellite.
satellite NG-RAN: a NG-RAN which uses NR in providing satellite access to UEs.
service area: geographic region where a 3GPP communication service is accessible.
NOTE 6: The service area can be indoors.
NOTE 7: For some deployments, e.g. in process industry, the vertical dimension of the service area can be considerable.
service continuity: the uninterrupted user experience of a service that is using an active communication when a UE undergoes an access change without, as far as possible, the user noticing the change.
NOTE 8: In particular service continuity encompasses the possibility that after a change the user experience is maintained by a different telecommunication service (e.g. tele- or bearer service) than before the change.
NOTE 9: Examples of access changes include the following. For EPS: CS/PS domain change. For EPS and 5G: radio access change, switching between a direct network connection and an indirect network connection.
Service Hosting Environment: the environment, located inside of 5G network and fully controlled by the operator, where Hosted Services are offered from.
serving satellite: a satellite providing the satellite access to an UE. In the case of NGSO, the serving satellite is always changing due to the nature of the satellite constellation.
Shared NG-RAN: as defined in 3GPP TS 22.101 [6].
NOTE: Shared NG-RAN can be a shared satellite NG-RAN.
Stand-alone Non-Public Network: A non-public network not relying on network functions provided by a PLMN
SNPN Credential Provider: Entity within the 5G system that creates and manages identity information and provides authentication services for those identities for the purpose of accessing a SNPN
NOTE: The SNPN Credential Provider can also authorize access to a non-public network for a subscriber associated with an identity handled by this SNPN Credential Provider.
S&F Satellite operation: S&F (Store and Forward) Satellite operation is an operation mode of a 5G system with satellite-access where the 5G system can provide some level of service (in storing and forwarding the data) when satellite connectivity is intermittently/temporarily unavailable, e.g. to provide communication service for UEs under satellite coverage without a simultaneous active feeder link connection to the ground segment.
S&F data retention period: it is the data storage validity period for a 5G system with satellite access supporting store and forward operation (e.g. after which undelivered data stored is being discarded).
synchronization threshold: A synchronization threshold can be defined as the maximum tolerable temporal separation of the onset of two stimuli, one of which is presented to one sense and the other to another sense, such that the accompanying sensory objects are perceived as being synchronous.
NOTE 10: This definition is based on [41].
survival time: the time that an application consuming a communication service may continue without an anticipated message.
Time to First Fix (TTFF): time elapsed between the event triggering for the first time the determination of the position-related data and the availability of the position-related data at the positioning system interface.
Traffic steering: the procedure that selects an access network and transfers traffic over the selected access network. This can apply to traffic of one or multiple services/applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are steered across different networks (with simultaneous data over the two networks).
Traffic switching: the procedure that moves all traffic from one access network to another access network in a way that minimizes service interruption. This can apply to traffic of one or multiple services/applications across two 3GPP access networks, including scenarios where all services use the same network connection (no simultaneous data over the two networks) or different services are moved to different networks (with simultaneous data over the two networks).
UE-Satellite-UE communication: for a 5G system with satellite access, it refers to the communication between UEs under the coverage of one or more serving satellites, using satellite access without the user traffic going through the ground segment.
User Equipment: An equipment that allows a user access to network services via 3GPP and/or non-3GPP accesses.
user experienced data rate: the minimum data rate required to achieve a sufficient quality experience, with the exception of scenario for broadcast like services where the given value is the maximum that is needed.
wireless backhaul: a link which provides an interconnection between 5G network nodes and/or transport network using 5G radio access technology.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
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].
5G LAN-VN 5G LAN-Virtual Network
A/S Actuator/Sensor
CO2 Carbon dioxide
CO2e Carbon dioxide equivalent
CPN Customer Premises Network
eFMSS Enhancement to Flexible Mobile Service Steering
eRG Evolved Residential Gateway
eV2X Enhanced V2X
FL Federated Learning
FMSS Flexible Mobile Service Steering
GEO Geostationary satellite Earth Orbit
ICP Internet Content Provider
ID Identification
IMU Inertial Measurement Unit
IOPS Isolated E-UTRAN Operation for Public Safety
ISL Inter-Satellite Link
LEO Low-Earth Orbit
MBS Metropolitan Beacon System
MCS Mission Critical Services
MCX Mission Critical X, with X = PTT or X = Video or X = Data
MEO Medium-Earth Orbit
MIoT Massive Internet of Things
MMTEL Multimedia Telephony
MOCN Multi-Operator Core Network
MPS Multimedia Priority Service
MSGin5G Message Service Within the 5G System
MSTP Multiple Spanning Tree Protocol
NGSO Non-Geostationary Satellite Orbit
NPN Non-Public Network
PIN Personal IoT Network
PRAS Premises Radio Access Station
RSTP Rapid Spanning Tree Protocol
RVAS Roaming Value-Added Service
SEES Service Exposure and Enablement Support
SNPN Stand-alone Non-Public Network
S&F Store and Forward
SST Slice/Service Type
TBS Terrestrial Beacon System
TTFF Time To First Fix
UAV Uncrewed Aerial Vehicle
UTC Coordinated Universal Time
XR eXtended Reality
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
4 Overview
|
Unlike previous 3GPP systems that attempted to provide a 'one size fits all' system, the 5G system is expected to be able to provide optimized support for a variety of different services, different traffic loads, and different end user communities. Various industry white papers, most notably, the NGMN 5G White Paper [2], describe a multi-faceted 5G system capable of simultaneously supporting multiple combinations of reliability, latency, throughput, positioning, and availability. This technology revolution is achievable with the introduction of new technologies, both in access and the core, such as flexible, scalable assignment of network resources. In addition to increased flexibility and optimization, a 5G system needs to support stringent KPIs for latency, reliability, throughput, etc. Enhancements in the radio interface contribute to meeting these KPIs as do enhancements in the core network, such as network slicing, in-network caching and hosting services closer to the end points.
A 5G system also supports new business models such as those for IoT and enterprise managed networks. Drivers for the 5G KPIs include services such as Uncrewed Aerial Vehicle (UAV) control, Augmented Reality (AR), and factory automation. Network flexibility enhancements support self-contained enterprise networks, installed and maintained by network operators while being managed by the enterprise. Enhanced connection modes and evolved security facilitate support of massive IoT, expected to include tens of millions of UEs sending and receiving data over the 5G network.
Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers. Enhanced charging and security mechanisms handle new types of UEs connecting to the network in different ways. The enhanced flexibility of the 5G system also allows to cater to the needs of various verticals. For example, the 5G system introduces the concept of non-public networks providing exclusive access for a specific set of users and specific purpose(s). Non-public networks can, depending on deployment and (national) regulations, support different subsets of 5G functionality. In this specification 5G network requirements apply to both NPNs and PLMNs, unless specified otherwise. Additionally, there are specific requirements dedicated only to NPNs or PLMNs, which are indicated accordingly. More information can be found in Section 6.25.
Mobile Broadband (MBB) enhancements aim to meet a number of new KPIs. These pertain to high data rates, high user density, high user mobility, highly variable data rates, deployment, and coverage. High data rates are driven by the increasing use of data for services such as streaming (e.g. video, music, and user generated content), interactive services (e.g. AR), and IoT. These services come with stringent requirements for user experienced data rates as well as associated requirements for latency to meet service requirements. Additionally, increased coverage in densely populated areas such as sports arenas, urban areas, and transportation hubs has become essential for pedestrians and users in urban vehicles. New KPIs on traffic and connection density enable both the transport of high volumes of data traffic per area (traffic density) and transport of data for a high number of connections (e.g. UE density or connection density). Many UEs are expected to support a variety of services which exchange either a very large (e.g. streaming video) or very small (e.g. data burst) amount of data. The 5G system will handle this variability in a resource efficient manner. All of these cases introduce new deployment requirements for indoor and outdoor, local area connectivity, high user density, wide area connectivity, and UEs travelling at high speeds.
Another aspect of 5G KPIs includes requirements for various combinations of latency and reliability, as well as higher accuracy for positioning. These KPIs are driven by support for both commercial and public safety services. On the commercial side, industrial control, industrial automation, UAV control, and AR are examples of those services. Services such as UAV control will require more precise positioning information that includes altitude, speed, and direction, in addition to horizontal coordinates.
Support for Massive Internet of Things (MIoT) brings many new requirements in addition to those for the enhanced KPIs. The expansion of connected things introduces a need for significant improvements in resource efficiency in all system components (e.g. UEs, IoT devices, radio, access network, core network).
The 5G system also aims to enhance its capability to meet KPIs that emerging V2X applications require. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5 High-level requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5.1 Migration to 5G
|
5.1.1 Description
The 5G system supports most of the existing EPS services, in addition to many new services. The existing EPS services can be accessed using the new 5G access technologies even where the EPS specifications might indicate E-UTRA(N) only. Only new or changed service requirements for new or changed services are specified in this document. The few EPS capabilities that are not supported by the 5G system are identified in clause 5.1.2.2 below.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5.1.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5.1.2.1 Interworking between 5G systems
|
The 5G system shall support a UE with a 5G subscription roaming into a 5G Visited Mobile Network which has a roaming agreement with the UE's 5G Home Mobile Network.
The 5G system shall enable a Visited Mobile Network to provide support for establishing home network provided data connectivity as well as visited network provided data connectivity.
The 5G system shall enable a Visited Mobile Network to provide support for services provided in the home network as well as provide services in the visited network. Whether a service is provided in the visited network or in the home network is determined on a service by service basis.
The 5G system shall provide a mechanism for a network operator to limit access to its services for a roaming UE, (e.g. based on roaming agreement).
The 5G system shall provide a mechanism for a network operator to direct a UE onto a partnership network for routing all or some of the UE user plane and associated control plane traffic over the partnership network, subject to an agreement between the operators.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5.1.2.2 Legacy service support
|
In principle, the 5G system shall support all EPS capabilities (e.g. from TSs 22.011, 22.101, 22.278, 22.185, 22.071, 22.115, 22.153, 22.173, 22.468). However,
- voice service continuity from NG-RAN to GERAN shall not be supported,
- voice service continuity from NG-RAN to UTRAN CS should be supported (see Note),
- voice service continuity from GERAN to NG-RAN shall not be supported,
- voice service continuity from UTRAN to NG-RAN shall not be supported,
- CS fallback from NG-RAN to GERAN shall not be supported,
- CS fallback from NG-RAN to UTRAN shall not be supported,
- seamless handover between NG-RAN and GERAN shall not be supported,
- seamless handover between NG-RAN and UTRAN shall not be supported,
- access to a 5G core network via GERAN or UTRAN shall not be supported,
- video service continuity between 5GS and UMTS shall not be supported,
- IP address preservation for PS service when UE moves between 5GS and GSM/UMTS shall not be supported, and
- Service continuity between 5GS and CDMA2000 shall not be supported.
NOTE: Architectural or protocol changes needed to support voice service continuity from NG-RAN to UTRAN CS are expected to have minimum impact on architecture, specifications, or the development of the 5G New Core and New Radio.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
5.1.2.3 Interoperability with legacy 3GPP systems
|
The 5G system shall support mobility procedures between a 5G core network and an EPC with minimum impact to the user experience (e.g. QoS, QoE).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6 Basic capabilities
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1 Network slicing
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.1 Description
|
Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g. priority, charging, policy control, security, and mobility), differences in performance requirements (e.g. latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g. MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO).
A network slice can provide the functionality of a complete network, including radio access network functions, core network functions (e.g. potentially from different vendors) and IMS functions. One network can support one or several network slices.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.2.1 General
|
The serving 5G network shall support providing connectivity to home and roaming users in the same network slice.
In shared 5G network configuration, each operator shall be able to apply all the requirements from this clause to their allocated network resources.
The 5G system shall be able to support IMS as part of a network slice.
The 5G system shall be able to support IMS independent of network slices.
For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to support the UE to access the most suitable network slice in minimum time (e.g. based on the location of the UE, ongoing applications, UE capability, frequency configured for the network slice).
5G system shall minimize signalling exchange and service interruption time for a network slice, e.g. when restrictions related to radio resources change (e.g., frequencies, RATs).
For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice.
The 5G system shall be able to minimize power consumption of a UE (e.g. reduce unnecessary cell measurements), in an area where no authorized network slice is available.
When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the active applications (e.g., providing early notification).
NOTE 1: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE.
The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference).
The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs
For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply:
- When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to:
- be registered to more than one VPLMN simultaneously; and
- use network slices from more than one VPLMN simultaneously
- The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs.
- The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices.
NOTE 2: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.2.2 Management
|
The 5G system shall allow the operator to create, modify, and delete a network slice.
The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice.
The 5G system shall allow the operator to configure the information which associates a UE to a network slice.
The 5G system shall allow the operator to configure the information which associates a service to a network slice.
The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice.
The 5G system shall support a mechanism for the VPLMN, as authorized by the HPLMN, to assign a UE to a network slice with the needed services or to a default network slice.
The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator.
Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network.
Creation, modification, and deletion of a network slice shall have no or minimal impact on traffic and services in other network slices in the same network.
The 5G system shall support scaling of a network slice, i.e. adaptation of its capacity.
The 5G system shall enable the network operator to define a minimum available capacity for a network slice. Scaling of other network slices on the same network shall have no impact on the availability of the minimum capacity for that network slice.
The 5G system shall enable the network operator to define a maximum capacity (e.g., number of UEs, number of data sessions) for a network slice.
The 5G system shall enable the network operator to define a priority order between different network slices in case multiple network slices compete for resources on the same network.
The 5G system shall support means by which the operator can differentiate policy control, functionality and performance provided in different network slices.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.2.3 Network slice constraints
|
The 5G system shall support a mechanism to prevent a UE from trying to access a radio resource dedicated to a specific private slice for any purpose other than that authorized by the associated third-party.
NOTE 1: UEs that are not authorized to access a specific private slice will not be able to access it for emergency calls if the private slice does not support emergency services.
The 5G system shall support a mechanism to configure a specific geographic area in which a network slice is accessible, i.e. a UE shall be within the geographical area in order to access the network slice.
The 5G system shall support a mechanism to limit a UE to only receiving service from an authorized slice.
For a UE authorized to access to multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall minimize service interruption time when the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications).
For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice.
NOTE 2: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN).
The 5G system shall support a mechanism to prevent a UE from registering with a network slice when the maximum number of UEs for that slice are registered.
The 5G system shall support a mechanism to prevent a UE from establishing a new data session within a network slice when the maximum number of data sessions for that slice are established.
NOTE 3: Based on national/regional regulations and operator policy, exemptions can be provided for UEs configured for priority services (e.g., MPS) and for priority service sessions.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.1.2.4 Cross-network slice coordination
|
The 5G system shall support a mechanism to provide time stamps with a common time base at the monitoring API, for services that cross multiple network slices and 5G networks.
The 5G system shall provide suitable APIs to coordinate network slices in multiple 5G networks so that the selected communication services of a non-public network can be extended through a PLMN (e.g. the service is supported by a slice in the non-public network and a slice in the PLMN).
The 5G system shall provide a mechanism to enable an MNO to operate a hosted non-public network and private slice(s) of its PLMN associated with the hosted non-public network in a combined manner.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.2 Diverse mobility management
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.2.1 Description
|
A key feature of 5G is support for UEs with different mobility management needs. 5G will support UEs with a range of mobility management needs, including UEs that are
- stationary during their entire usable life (e.g. sensors embedded in infrastructure),
- stationary during active periods, but nomadic between activations (e.g. fixed access),
- mobile within a constrained and well-defined space (e.g. in a factory), and
- fully mobile.
Moreover, some applications require the network to ensure seamless mobility of a UE so that mobility is hidden from the application layer to avoid interruptions in service delivery while other applications have application specific means to ensure service continuity. But these other applications can still require the network to minimize interruption time to ensure that their application-specific means to ensure service continuity work effectively.
With the ever-increasing multimedia broadband data volumes, it is also important to enable the offloading of IP traffic from the 5G network onto traditional IP routing networks via an IP anchor node close to the network edge. As the UE moves, changing the IP anchor node can be needed in order to reduce the traffic load in the system, reduce end-to-end latency and provide a better user experience.
The flexible nature of a 5G system will support different mobility management methods that minimize signalling overhead and optimize access for these different types of UEs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.2.2 General requirements
|
The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs.
The 5G system shall enable operators to specify and modify the types of mobility support provided for a UE or group of UEs.
The 5G system shall optimize mobility management support for a UE or group of UEs that use only mobile originated communications.
The 5G system shall support inter- and/or intra- access technology mobility procedures within 5GS with minimum impact to the user experience (e.g. QoS, QoE).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.2.3 Service continuity requirements
|
The 5G system shall enable packet loss to be minimized during inter- and/or intra- access technology changes for some or all connections associated with a UE.
The 5G system shall minimize interruption time during inter- and/or intra- access technology mobility for some or all connections associated with a UE.
NOTE: The interruption time includes all delays which have impact on service continuity.
For applications that require the same IP address during the lifetime of the session, the 5G system shall enable maintaining the IP address assigned to a UE when moving across different cells and access technologies for connections associated with a UE.
The 5G system shall enable minimizing impact to the user experience (e.g. minimization of interruption time) when changing the IP address and IP anchoring point for some or all connections associated with a UE.
The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa.
The 5G system shall support service continuity for a remote UE, when the remote UE changes from one relay UE to another and both relay UEs use 3GPP access to the 5G core network.
Satellite access related service continuity requirements are covered in clause 6.46.3.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.2.4 Roaming related requirements
|
Satellite access related roaming requirements are covered in clause 6.46.4.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3 Multiple access technologies
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.1 Description
|
The 5G system will support 3GPP access technologies, including one or more NR and E-UTRA as well as non-3GPP access technologies. Interoperability among the various access technologies will be imperative. For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-3GPP access technology for a service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE. New technology such as satellite and wide area base stations will increase coverage and availability. This clause provides requirements for interworking with the various combinations of access technologies.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.2.1 General
|
Based on operator policy, the 5G system shall enable the UE to select, manage, and efficiently provision services over the 3GPP or non-3GPP access.
Based on operator policy, the 5G system shall support steering a UE to select certain 3GPP access network(s).
Based on operator policy, the 5G system shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type.
Based on operator policy, the 5G system shall be able to provide simultaneous data transmission via different access technologies (e.g. NR, E-UTRA, non-3GPP), to access one or more 3GPP services.
When a UE is using two or more access technologies simultaneously, the 5G system shall be able to optimally distribute user traffic over the access technologies in use, taking into account e.g. service, traffic characteristics, radio characteristics, and UE's moving speed.
The 5G system shall be able to support data transmissions optimized for different access technologies (e.g. 3GPP, non-3GPP) and accesses to local data networks (e.g. local traffic routing) for UEs that are simultaneously connected to the network via different accesses.
NOTE: This applies to the scenario with simultaneous 3GPP and non-3GPP accesses.
Based on operator policy, the 5G system shall be able to add or drop the various access connections for a UE during a session.
The 5G system shall be able to support mobility between the supported access networks (e.g. NG-RAN, WLAN, fixed broadband access network, 5G satellite access network).
The 5G system shall support UEs with multiple radio and single radio capabilities.
The 5G system shall support dynamic and static network address allocation of a common network address to the UE over all supported access types.
The 5G system shall support a set of identities for a single user in order to provide a consistent set of policies and a single set of services across 3GPP and non-3GPP access types.
The 5G system shall support the capability to operate in licensed and/or unlicensed bands.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.2.2 E-UTRA access
|
The 5G system shall be able to support seamless handover between NR and E-UTRA.
The 5G system shall support UEs with dual radio capability (i.e. a UE that can transmit on NR and E-UTRA simultaneously) as well as UEs with single radio capability (i.e. a UE that cannot transmit on NR and E-UTRA simultaneously).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.2.3 Satellite access
|
The 5G system shall be able to provide services using satellite access.
NOTE: Additional requirements related to satellite access can be found in clause 6.46.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.3.2.4 Fixed broadband access
|
The 5G system shall be able to efficiently support connectivity using fixed broadband access.
NOTE: The specification of fixed broadband access network is outside the scope of 3GPP.
The 5G system shall support use of a relay UE that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
The 5G system shall support use of a home base station that supports multiple access types (e.g. 5G RAT, WLAN access, fixed broadband access).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4 Resource efficiency
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.1 Description
|
5G introduces the opportunity to design a system to be optimized for supporting diverse UEs and services. While support for IoT is provided by EPS, there is room for improvement in efficient resource utilization that can be designed into a 5G system whereas they are not easily retrofitted into an existing system. Some of the underlying principles of the potential service and network operation requirements associated with efficient configuration, deployment, and use of UEs in the 5G network include bulk provisioning, resource efficient access, optimization for UE originated data transfer, and efficiencies based on the reduced needs related to mobility management for stationary UEs and UEs with restricted range of movement.
As sensors and monitoring UEs are deployed more extensively, the need to support UEs that send data packages ranging in size from a small status update in a few bits to streaming video increases. A similar need exists for smart phones with widely varying amounts of data. Specifically, to support short data bursts, the network should be able to operate in a mode where there is no need for a lengthy and high overhead signalling procedure before and after small amounts of data are sent. The system will, as a result, avoid both a negative impact to battery life for the UE and wasting signalling resources.
For small form factor UEs it will be challenging to have more than 1 antenna due to the inability to get good isolation between multiple antennas. Thus, these UEs need to meet the expected performance in a 5G network with only one antenna.
Cloud applications like cloud robotics perform computation in the network rather than in a UE, which requires the system to have high data rate in the uplink and very low round trip latency. Supposed that high density cloud robotics will be deployed in the future, the 5G system need to optimize the resource efficiency for such scenario.
Additional resource efficiencies will contribute to meeting the various KPIs defined for 5G. Control plane resource efficiencies can be achieved by optimizing and minimizing signalling overhead, particularly for small data transmissions. Mechanisms for minimizing user plane resources utilization include in-network caching and application in a Service Hosting Environment closer to the end user. These optimization efforts contribute to achieving lower latency and higher reliability.
Diverse mobility management related resource efficiencies are covered in clause 6.2.
Security related resource efficiencies are covered in clause 8.8.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.2 Requirements
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.2.1 General
|
The 5G system shall minimize control and user plane resource usage for data transfer from send only UEs.
The 5G system shall minimize control and user plane resource usage for stationary UEs (e.g. lower signalling to user data resource usage ratio).
The 5G system shall minimize control and user plane resource usage for transfer of infrequent small data units.
The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of small data units.
The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of continuous uplink data that requires both high data rate (e.g. 10 Mbit/s) and very low end-to-end latency (e.g. 1-10 ms).
The 5G network shall optimize the resource use of the control plane and/or user plane to support high density connections (e.g. 1 million connections per square kilometre) taking into account, for example, the following criteria:
- type of mobility support;
- communication pattern (e.g. send-only, frequent or infrequent);
- characteristics of payload (e.g. small or large size data payload);
- characteristics of application (e.g. provisioning operation, normal data transfer);
- UE location;
- timing pattern of data transfer (e.g. real time or non-delay sensitive).
The 5G system shall efficiently support service discovery mechanisms where UEs can discover, subject to access rights:
- status of other UEs (e.g. sound on/off);
- capabilities of other UEs (e.g. the UE is a relay UE) and/or;
- services provided by other UEs (e.g. the UE is a colour printer).
The 5G system shall be able to minimise the amount of wireless backhaul traffic (e.g. consolidating data transmissions to 1 larger rather than many smaller), when applicable (e.g. providing service in an area subject to power outages).
The 5G system shall support small form factor UEs with single antenna.
NOTE: Small form factor UEs are typically expected to have the diagonal less than 1/5 of the lowest supported frequency wave length.
Satellite access related resource efficiency requirements are covered in clause 6.46.5.
The 5G system shall support UEs with different characteristics such as data rate, power consumption, etc.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.2.2 Efficient bulk operations for IoT
|
The 5G network shall optimize the resource use of the control plane and/or user plane to support bulk operation for high connection density (e.g. 1 million connections per square kilometre) of multiple UEs.
The 5G system shall support a timely, efficient, and/or reliable mechanism to transmit the same information to multiple UEs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.2.3 Efficient management for IoT
|
The 5G network shall optimize the resource use of the control plane and/or user plane to manage (e.g. provide service parameters, activate, deactivate) a UE.
The 5G network shall be able to provide policies for background data transfer to a UE so that the 5G system can optimally use the control plane and/or user plane resources.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.4.2.4 Efficient control plane
|
The 5G system shall minimize the signalling that is required prior to user data transmission.
NOTE: The amount of signalling overhead may vary based on the amount of data to be transmitted, even for the same UE.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.5 Efficient user plane
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.5.1 Description
|
5G is designed to meet diverse services with different and enhanced performances (e.g. high throughput, low latency and massive connections) and data traffic model (e.g. IP data traffic, non-IP data traffic, short data bursts and high throughput data transmissions).
User plane should be more efficient for 5G to support differentiated requirements. On one hand, a Service Hosting Environment located inside of operator's network can offer Hosted Services closer to the end user to meet localization requirement like low latency, low bandwidth pressure. These Hosted Services contain applications provided by operators and/or trusted 3rd parties. On the other hand, user plane paths can be selected or changed to improve the user experience or reduce the bandwidth pressure, when a UE or application changes location during an active communication, or due to operational needs in the service hosting environment (e.g. based on usage information).
The 5G network can also support multiple wireless backhaul connections (e.g. satellites and/or terrestrial), and efficiently route and/or bundle traffic among them.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.5.2 Requirements
|
Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path between UEs attached to the same network, modifying the path as needed when the UE moves during an active communication.
The 5G network shall enable a Service Hosting Environment provided by operator.
Based on operator policy, the 5G network shall be able to support routing of data traffic between a UE attached to the network and an application in a Service Hosting Environment for specific services, modifying the path as needed when the UE moves during an active communication.
Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and:
- an application in a Service Hosting Environment; or
- an application server located outside the operator’s network; or
- an application server located in a customer premises network or personal IoT network.
The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to:
- another location served by a different Service Hosting Environment; or
- another location served by an application server located outside the operator’s network; or
- another location served by an application server located in a customer premises network or personal IoT network, and vice versa.
The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows:
- within a Service Hosting Environment; or
- from a Service Hosting Environment to another Service Hosting Environment; or
- from a Service Hosting Environment to an application server located place outside the operator’s network; or
- from a Service Hosting Environment to an application server located in a customer premises network or personal IoT network, and vice versa.
The 5G network shall be able to interact with applications in a Service Hosting Environment for efficient network resource utilization and offloading data traffic to the most suitable Service Hosting Environment, e.g. close to the UE's point of attachment to the access network or based on usage information.
NOTE: To accomplish offloading data traffic, usage information might be exposed to the Service Hosting Environment.
The 5G network shall support configurations of the Service Hosting Environment in the network (e.g. access network, core network), that provide application access close to the UE's point of attachment to the access network.
The 5G system shall support mechanisms to enable a UE to access the closest Service Hosting Environment for a specific hosted application or service.
The 5G network shall enable instantiation of applications for a UE in a Service Hosting Environment close to the UE's point of attachment to the access network.
The 5G system shall be able to suspend or stop application instances in a Service Hosting Environment.
NOTE: Not all applications will always be available in all Service Hosting Environments. Therefore, it may be needed to instantiate an application at a Service Hosting Environment nearby for serving a particular UE.
Based on operator policy, the 5G system shall provide a mechanism such that one type of traffic (from a specific application or service) to/from a UE can be offloaded close to the UE's point of attachment to the access network, while not impacting other traffic type to/from that same UE.
Satellite access related efficient user plane requirements are covered in clause 6.46.6.
The 5G System shall enable the discovery of a suitable Hosted Service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.6 Efficient content delivery
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.6.1 Description
|
Video-based services (e.g. live streaming, VR) and personal data storage applications have been instrumental for the massive growth in mobile broadband traffic. Subject to service agreement between the operator and the content provider, the information of content and content itself can be aware by operator. In-network content caching provided by the operator, a third-party or both, can improve user experience, reduce backhaul resource usage and utilize radio resource efficiently.
The operation of in-network caching includes flexible management of the location of the content cache within the network and efficient delivery of content to and from the appropriate content caching application. Examples of services are the delivery of popular video content from a content caching application via broadcast, and secure storage of a user's personal data or files using a distributed caching application. Such a service could also provide a student with a wireless backpack, where students can resume their work through the same or a different UE at any time, with very fast response times from the network.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.6.2 Requirements
|
The 5G system shall enable efficient delivery of content from a content caching application under the control of the operator (e.g. a cache located close to the UE).
The 5G system shall support a content caching application in a UE under the control of the operator.
The 5G system shall support configurations of content caching applications in the network (e.g. access network, core network), that provide content close to the UE.
Based on operator policy, the 5G system shall support an efficient mechanism for selection of a content caching application (e.g. minimize utilization of radio, backhaul resources and/or application resource) for delivery of the cached content to the UE.
The 5G system shall support a mechanism for the operator to manage content distribution across content caching applications.
The 5G system shall support delivery of cached content from a content caching application via the broadcast/multicast service.
For a 5G system with satellite access, the following requirement applies.
- A 5G system with satellite access shall be able to optimise the delivery of content from a content caching application by taking advantage of satellites in supporting ubiquitous service, as well as broadcasting/multicasting on very large to global coverages.
6.7 Priority, QoS, and policy control
6.7.1 Description
The 5G network will support many commercial services (e.g. medical) and regional or national regulatory services (e.g. MPS, Emergency, Public Safety) with requirements for priority treatment. Some of these services share common QoS characteristics such as latency and packet loss rate but can have different priority requirements. For example, UAV control and air traffic control can have stringent latency and reliability requirements but not necessarily the same priority requirements. In addition, voice-based services for MPS and Emergency share common QoS characteristics as applicable for normal public voice communications yet can have different priority requirements. The 5G network will need to support mechanisms that enable the decoupling of the priority of a particular communication from the associated QoS characteristics such as latency and reliability to allow flexibility to support different priority services (that need to be configurable to meet operator needs, consistent with operator policies and corresponding national and regional regulatory policies).
The network needs to support flexible means to make priority decisions based on the state of the network (e.g. during disaster events and network congestion) recognizing that the priority needs can change during a crisis. The priority of any service can be different for a user of that service based on operational needs and regional or national regulations. Therefore, the 5G system should allow a flexible means to prioritise and enforce prioritisation among the services (e.g. MPS, Emergency, medical, Public Safety) and among the users of these services. The traffic prioritisation can be enforced by adjusting resource utilization or pre-empting lower priority traffic.
The network must offer means to provide the required QoS (e.g. reliability, latency, and bandwidth) for a service and the ability to prioritize resources when necessary to meet the service requirements. Existing QoS and policy frameworks handle latency and improve reliability by traffic engineering. In order to support 5G service requirements, it is necessary for the 5G network to offer QoS and policy control for reliable communication with latency required for a service and enable the resource adaptations as necessary.
The network needs to allow multiple services to coexist, including multiple priority services (e.g. Emergency, MPS and MCS) and must provide means to prevent a single service from consuming or monopolizing all available network resources, or impacting the QoS (e.g. availability) of other services competing for resources on the same network under specific network conditions. For example, it is necessary to prevent certain services (e.g. citizen-to-authority Emergency) sessions from monopolizing all available resources during events such as disaster, emergency, and DDoS attacks from impacting the availability of other priority services such as MPS and MCS.
Also, as 5G network is expected to operate in a heterogeneous environment with multiple access technologies, multiple types of UE, etc., it should support a harmonised QoS and policy framework that applies to multiple accesses.
Further, for QoS control in EPS only covers RAN and core network, but for 5G network E2E QoS (e.g. RAN, backhaul, core network, network to network interconnect) is needed to achieve the 5G user experience (e.g. ultra-low latency, ultra-high bandwidth).
6.7.2 Requirements
The 5G system shall allow flexible mechanisms to establish and enforce priority policies among the different services (e.g. MPS, Emergency, medical, Public Safety) and users.
NOTE 1: Priority between different services is subject to regional or national regulatory and operator policies.
The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service.
The 5G system shall enable the network operator to define and statically configure a maximum resource assignment for a specific service that can be adjusted based on the network state (e.g. during congestion, disaster, emergency and DDoS events) subject to regional or national regulatory and operator policies.
The 5G system shall allow decoupling of the priority of a particular communication from the associated QoS characteristics such as end-to-end latency and reliability.
The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses.
The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service.
NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect.
The 5G system shall be able to support QoS for applications in a Service Hosting Environment.
A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve an UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability.
The 5G system shall support a mechanism to determine suitable QoS parameters for traffic over a satellite backhaul, based e.g. on the latency and bandwidth of the specific backhaul .
NOTE 3: The case where a backhaul connection has dynamically changed latency and/or bandwidth needs to be considered.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.8 Dynamic policy control
|
The 5G system shall support the creation and enforcement of prioritisation policy for users and traffic, during connection setup and when connected.
NOTE: Prioritisation, pre-emption, and precedence of critical traffic associated with certain priority services (e.g. MPS and Emergency) are subject to regional/national regulatory and operator policies.
The 5G system shall support optimised signalling for prioritised users and traffic where such signalling is prioritized over other signalling traffic.
Based on operator policy, the 5G system shall allow flexible means for authorized entities to create and enforce priority among the different service flows.
Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration.
Based on operator policy, the 5G system shall maintain a session when prioritization of that session changes in real time, provided that the new priority is above the threshold for maintaining the session.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9 Connectivity models
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.1 Description
|
The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relay UEs can be used to improve the energy efficiency and coverage of the system.
Remote UEs can be anything from simple wearables, such as sensors embedded in clothing, to a more sophisticated wearable UE monitoring biometrics. They can also be non-wearable UEs that communicate in a Personal Area Network such as a set of home appliances (e.g. smart thermostat and entry key), or the electronic UEs in an office setting (e.g. smart printers), or a smart flower pot that can be remotely activated to water the plant.
When a remote UE is attempting to establish an indirect network connection, there might be several relay UEs that are available in proximity and supporting selection procedures of an appropriate relay UE among the available relay UEs is needed.
Indirect network connection covers the use of relay UEs for connecting a remote UE to the 3GPP network. There can be one or more relay UE(s) (more than one hop) between the network and the remote UE.
A ProSe UE-to-UE Relay can also be used to connect two remote Public Safety UEs using direct device connection. There can be one or more ProSe UE-to-UE Relay(s) (more than one hop) between the two remote Public Safety UEs.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2 Requirements
|
The following set of requirements complement the requirements listed in 3GPP TS 22.278 [5], clauses 7B and 7C.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2.1 General
|
The 5G system shall support the relaying of traffic between a remote UE and a gNB using one or more relay UEs.
The 5G system shall support same traffic flow of a remote UE to be relayed via different indirect network connection paths.
The 5G system shall support different traffic flows of a remote UE to be relayed via different indirect network connection paths.
The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band.
The connection between a remote UE and a relay UE shall be able to use fixed broadband technology.
The 5G system shall support indirect network connection mode in a VPLMN when a remote UE and a relay UE subscribe to different PLMNs and both PLMNs have a roaming agreement with the VPLMN.
The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode.
The network operator shall be able to define the maximum number of hops supported in their networks when using relay UEs.
The 5G system shall be able to manage communication between a remote UE and the 5G network across multi-path indirect network connections.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2.2 Services and Service Continuity
|
A 5G system shall be able to support all types of traffic e.g. voice, data, IoT small data, multimedia, MCX for indirect network connection mode.
The 5G system shall be able to support QoS for a user traffic session between the remote UE and the network using 3GPP access technology.
The 5G system shall be able to provide indication to a remote UE (alternatively, an authorized user) on the quality of currently available indirect network connection paths.
The 5G system shall be able to maintain service continuity of indirect network connection for a remote UE when the communication path to the network changes (i.e. change of one or more of the relay UEs, change of the gNB).
NOTE: It does not apply to a traffic flow of a remote UE using different indirect network connection paths.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2.3 Permission and Authorization
|
The 5G system shall enable the network operator to authorize a UE to use indirect network connection. The authorization shall be able to be restricted to using only relay UEs belonging to the same network operator. The authorization shall be able to be restricted to only relay UEs belonging to the same application layer group.
The 5G system shall enable the network operator to authorize a UE to relay traffic as relay UE. The authorization shall be able to allow relaying only for remote UEs belonging to the same network operator. The authorization shall be able to allow relaying only for remote UEs belonging to the same application layer group.
The 5G system shall support a mechanism for an end user to provide/revoke permission to an authorized UE to act as a relay UE.
The 5G system shall support a mechanism for an authorized third-party to provide/revoke permission to an authorized UE to act as a relay UE.
The 5G system shall provide a suitable API by which an authorized third-party shall be able to authorize (multiple) UEs under control of the third-party to act as a relay UE or remote UE.
The 5G system shall provide a suitable API by which an authorized third-party shall be able to enable/disable (multiple) UEs under control of the third-party to act as a relay UE or remote UE.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2.4 Relay UE Selection
|
The 3GPP system shall support selection and reselection of relay UEs based on a combination of different criteria e.g.
- the characteristics of the traffic that is intended to be relayed (e.g. expected message frequency and required QoS),
- the subscriptions of relay UEs and remote UE,
- the capabilities/capacity/coverage when using the relay UE,
- the QoS that is achievable by selecting the relay UE,
- the power consumption required by relay UE and remote UE,
- the pre-paired relay UE,
- the 3GPP or non-3GPP access the relay UE uses to connect to the network,
- the 3GPP network the relay UE connects to (either directly or indirectly),
- the overall optimization of the power consumption/performance of the 3GPP system, or
- battery capabilities and battery lifetime of the relay UE and the remote UE.
NOTE: Reselection may be triggered by any dynamic change in the selection criteria, e.g. by the battery of a relay UE getting depleted, a new relay capable UE getting in range, a remote UEs requesting additional resources or higher QoS, etc.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.2.5 Satellite and Relay UEs
|
Satellite and relay UEs related requirements are covered in clause 6.46.7.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.9.3 Requirements on direct device connection for Public Safety
|
The following requirement complement the requirements listed in 3GPP TS 22.278 [5], clauses 7A.
The 5G system shall support the relaying of traffic between two remote Public Safety UEs using direct device connection via one or more ProSe UE-to-UE Relay(s) (one or more hops, assuming single-path), while in coverage, out-of-coverage, or partial coverage.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.10 Network capability exposure
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.10.1 Description
|
3GPP SEES and (e)FMSS features allow the operator to expose network capabilities e.g. QoS policy to third-party ISPs/ICPs. With the advent of 5G, new network capabilities need to be exposed to the third-party (e.g. to allow the third-party to customize a dedicated physical or virtual network or a dedicated network slice for diverse use cases; to allow the third-party to manage a trusted third-party application in a Service Hosting Environment to improve user experience, and efficiently utilize backhaul and application resources).
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.10.2 Requirements
|
The following set of requirements complement the requirements listed in 3GPP TS 22.101 [6], clause 29.
Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to assign a UE to a network slice used for the third-party, to move a UE from one network slice used for the third-party to another network slice used for the third-party, and to remove a UE from a network slice used for the third-party based on subscription, UE capabilities, and services provided by the network slice.
The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide the 3GPP network via encrypted connection with the expected communication behaviour of UE(s).
NOTE 1: The expected communication behaviour is, for instance, the application servers a UE is allowed to communicate with, the time a UE is allowed to communicate, or the allowed geographic area of a UE.
The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide via encrypted connection the 3GPP network with the actions expected from the 3GPP network when detecting behaviour that falls outside the expected communication behaviour.
NOTE 2: Such actions can be, for instance, to terminate the UE's communication, to block the transferred data between the UE and the not allowed application.
The 5G network shall be able to provide secure means for providing communication scheduling information (i.e. the time period the UE(s) will use a communication service) to an NPN via encrypted connection. This communication scheduling information is used by the 5G network to perform network energy saving and network resource optimization.
The 5G network shall provide a mechanism to expose broadcasting capabilities to trusted third-party broadcasters' management systems.
Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment.
Based on operator policy, the 5G network shall provide suitable APIs to allow a third-party to monitor this trusted third-party owned application(s) in the operator's Service Hosting Environment.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity.
Based on operator policy, a 5G network shall provide suitable APIs to allow one type of traffic (from trusted third-party owned applications in the operator's Service Hosting Environment) to/from a UE to be offloaded to a Service Hosting Environment close to the UE's location.
Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network.
Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party.
Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party.
Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party.
The 5G system shall support the means for disengagement (tear down) of communication services by an authorized third-party.
Based on operator policy, the 5G network shall expose a suitable API to provide the security logging information of UEs, for example, the active 3GPP security mechanisms (e.g. data privacy, authentication, integrity protection) to an authorized third-party.
Based on operator policy, the 5G system shall provide suitable means to allow a trusted and authorized third-party to consult security related logging information for the network slices dedicated to that third-party.
Based on operator policy, the 5G network shall be able to acknowledge within 100 ms a communication service request from an authorized third-party via a suitable API.
The 5G network shall provide suitable APIs to allow a trusted third-party to monitor the status (e.g. locations, lifecycle, registration status) of its own UEs.
NOTE 3: The number of UEs could be in the range from single digit to tens of thousands.
The 5G network shall provide suitable APIs to allow a trusted third-party to get the network status information of a private slice dedicated for the third-party, e.g. the network communication status between the slice and a specific UE.
The 5G system shall support APIs to allow the non-public network to be managed by the MNO's Operations System.
The 5G system shall provide suitable APIs to allow third-party infrastructure (i.e. physical/virtual network entities at RAN/core level) to be used in a private slice.
A 5G system shall provide suitable APIs to enable a third-party to manage its own non-public network and its private slice(s) in the PLMN in a combined manner.
The 5G system shall support suitable APIs to allow an MNO to offer automatic configuration services (for instance, interference management) to non-public networks deployed by third parties and connected to the MNO's Operations System through standardized interfaces.
The 5G system shall be able to:
- provide a third-party with secure access to APIs (e.g. triggered by an application that is visible to the 5G system), by authenticating and authorizing both the third-party and the UE using the third-party's service.
- provide a UE with secure access to APIs (e.g. triggered by an application that is not visible to the 5G system), by authenticating and authorizing the UE.
- allow the UE to provide/revoke consent for information (e.g., location, presence) to be shared with the third-party.
- preserve the confidentiality of the UE's external identity (e.g. MSISDN) against the third-party.
- provide a third-party with information to identify networks and APIs on those networks.
Based on operator policy, the 5G system shall provide means by which an MNO informs a third party of changes in UE subscription information. The 5G system shall also provide a means for an authorised third party to request this information at any time from the MNO.
NOTE 4: Examples of UE subscription information include IP address, 5G LAN-VN membership, and configuration parameters for data network access.
NOTE 5: These changes can have strong impacts in the stability of the third-party service.
The 5G system shall provide a means by which an MNO can inform authorised 3rd parties of changes in the
- RAT type that is serving a UE;
- cell ID;
- RAN quality of signal information;
- assigned frequency band.
This information listed above shall be provided with a suitable frequency via OAM and/or 5G core network.
NOTE 6: The information aids the third party user to take proactive actions so that it can achieve high service availability in delivery of its services.
Subject to user consent, the 5G network shall provide suitable means for an authorized 3rd party to provided E2E QoS parameters for a service.
|
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.11 Context-aware network
| |
f9a197ded31c88efb7acaa77f7788f20
|
22.261
|
6.11.1 Description
|
A variety of sensors such as accelerometer, gyroscope, magnetometer, barometer, proximity sensor, and GPS can be integrated in a UE. Also, different applications running on the UE can have different communication needs (e.g. different traffic time). In addition, a UE can support different access technologies such as NR, E-UTRA, WLAN access technology, and fixed broadband access technology. The information gathered by sensors, the utilized access technologies, the application context, and the application traffic characteristics can provide useful information to the applications installed in the UE and can also help the 5G system utilize resources in an efficient and optimized way.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.