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.3 TETRA | [R-6.18.3.3-001] The MCPTT Service shall enable interworking with non-3GPP PTT Systems that are compliant with the ETSI TETRA standards.
[R-6.18.3.3-002] Interworking between the MCPTT Service and TETRA shall be capable of interworking with a multiplicity of independently administered TETRA systems (Switching and manag... |
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 ba... |
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... |
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 networ... |
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 wh... |
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 ... |
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 ... |
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 ... |
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-... |
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 co... |
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 ... |
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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 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.
-... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 3 Definitions, symbols and abbreviations
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 Carbo... |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 5 High-level requirements
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 serv... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 5.1.2 Requirements
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 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),
- ... |
ac78a8585cc1fb76fae88ca4aff4257c | 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).
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6 Basic capabilities
| |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.1 Network slicing
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.1.2 Requirements
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 sl... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 emerge... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.2 Diverse mobility management
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 activat... |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 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: ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.2.4 Roaming related requirements
| Satellite access related roaming requirements are covered in clause 6.46.4.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.3 Multiple access technologies
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 te... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.3.2 Requirements
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 dyn... |
ac78a8585cc1fb76fae88ca4aff4257c | 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).
|
ac78a8585cc1fb76fae88ca4aff4257c | 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.
|
ac78a8585cc1fb76fae88ca4aff4257c | 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).
T... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.4 Resource efficiency
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.4.2 Requirements
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 f... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 m... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 plan... |
ac78a8585cc1fb76fae88ca4aff4257c | 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.
|
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.5 Efficient user plane
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 suppor... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.6 Efficient content delivery
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 conte... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 ... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.9 Connectivity models
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 S... |
ac78a8585cc1fb76fae88ca4aff4257c | 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.
|
ac78a8585cc1fb76fae88ca4aff4257c | 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 vi... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 pr... |
ac78a8585cc1fb76fae88ca4aff4257c | 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 laye... |
ac78a8585cc1fb76fae88ca4aff4257c | 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/... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.9.2.5 Satellite and Relay UEs
| Satellite and relay UEs related requirements are covered in clause 6.46.7.
|
ac78a8585cc1fb76fae88ca4aff4257c | 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, ou... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.10 Network capability exposure
| |
ac78a8585cc1fb76fae88ca4aff4257c | 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 slic... |
ac78a8585cc1fb76fae88ca4aff4257c | 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... |
ac78a8585cc1fb76fae88ca4aff4257c | 22.261 | 6.11 Context-aware network
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.