Content for TS 23.180 Word version: 19.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Introduction
5 Architectural requirements
5.1 General requirements
5.2 MC service requirements
5.3 Network broadcast/multicast session requirements
5.4 IP connectivity functionality
6 Involved business relationships
...
...
1 Scope p. 8
This document specifies the functional architecture, procedures and information flows needed to support mission critical services in the IOPS mode of operation. IOPS mode of operation allows an isolated 3GPP network to maintain a level of MC services in case the backhaul connection is lost. For example, for EPS the IOPS mode of operation is defined in TS 23.401.
The corresponding service requirements are defined in TS 22.346 and TS 22.280.
The present document is applicable to support mission critical services in the IOPS mode of operation for 3GPP access types, such as E-UTRAN or 5G.
The functional architecture to support mission critical services in the IOPS mode of operation can be used for public safety applications and also for general commercial applications, e.g. utility companies and railways, for the case of a backhaul failure.
2 References p. 8
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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[3]
TS 23.280: "Common functional architecture to support mission critical services ".
[4]
TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2".
[5]
TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[6]
TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2".
[7]
TS 23.002: "Network Architecture".
[8]
TS 23.203: "Policy and charging control architecture".
[9]
TS 22.346: "Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1".
[10]
TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2".
[11]
TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1".
[12]
TS 22.289: "Mission Critical services over 5G System; Stage 2".
[13]
TS 23.501: "System architecture for the 5G System (5GS)".
[14]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
[15]
TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
3 Definitions and abbreviations p. 9
3.1 Definitions p. 9
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
IOPS MC system:
The collection of application functions and enabling capabilities required to support mission critical services in the IOPS mode of operation.
IOPS mode of operation:
Provides the ability to maintain a level of communications for MC users in case the backhaul connection is lost.
IOPS 3GPP system:
It is a group of 3GPP core entities that are either co-sited with or co-located in an IOPS capable base station.
Broadcast/multicast session:
Is either the MBMS bearer in EPS or the MBS session in 5GS.
Unicast session:
A unicast session is either a unicast bearer in EPS, or a unicast PDU session in 5GS.
For the purposes of the present document, the following terms given in TS 23.280 apply
MC service
MC service client
MC service group
MC service ID
MC service user
MC service UE
MC user
3.2 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
APN
Access Point Name
DNN
Data Network Name
IOPS
Isolated Operation for Public Safety
EPC
Evolved Packet Core
EPS
Evolved Packet System
MBMS
Multimedia Broadcast and Multicast Service
MC
Mission Critical
PLMN
Public Land Mobile Network
4 Introduction p. 9
For the case of a backhaul failure, mission critical (MC) services (e.g. MCPTT defined in TS 23.379 and MCData defined in TS 23.282) can also be supported based on the availability of an isolated operation for public safety (IOPS) MC system. The IOPS MC system provides MC services support to the MC service UE via a single public land mobile network (PLMN) dedicated to the IOPS mode of operation, for example as defined in TS 23.401.
A common functional architecture, including application plane and signalling plane, to support MC services in the IOPS mode of operation is specified in this document.
5 Architectural requirements p. 10
5.1 General requirements p. 10
5.1.1 Description p. 10
This clause specifies the general requirements for the support of MC services in the IOPS mode of operation.
5.1.2 Requirements p. 10
[AR-5.1.2-a]
For the case of a backhaul failure between the radio access network and the macro 3GPP core network, the IOPS MC system shall provide support for MC services in the IOPS mode of operation until the failure is recovered.
[AR-5.1.2-b]
MC service UEs within the coverage of the local IOPS 3GPP systems shall be able to provide MC services over the IOPS MC system.
[AR-5.1.2-c]
The IOPS MC system shall provide mechanisms to verify the availability of MC service UEs within the IOPS MC system.
5.2 MC service requirements p. 10
5.2.1 Description p. 10
This clause specifies the MC service requirements in the IOPS mode of operation.
5.2.2 Requirements p. 10
[AR-5.2.2-a]
The following MCPTT service features shall be supported in the IOPS mode of operation
- MCPTT group call
- MCPTT emergency group call
- MCPTT private call
- MCPTT emergency private call
The following MCData service features shall be supported in the IOPS mode of operation
- MCData short data service
5.3 Network broadcast/multicast session requirements p. 10
5.3.1 Description p. 10
This clause specifies the network bearer requirements in the IOPS mode of operation.
5.3.2 Requirements p. 10
[AR-5.3.2-a]
The IOPS MC system shall provide support for unicast session establishment and modification to support MC services via unicast transmissions in the IOPS mode of operation.
[AR-5.3.2-b]
The IOPS MC system shall provide support for broadcast/multicast session establishment and modification to support MC services via multicast transmissions in the IOPS mode of operation.
[AR-5.3.2-c]
The IOPS MC system shall support announcement of broadcast/multicast session to the MC service UEs.
5.4 IP connectivity functionality p. 11
5.4.1 Description p. 11
The support of MC services in the IOPS mode of operation can be based on the support of the IP connectivity functionality. The IP connectivity functionality enables that MC services are provided by the MC service clients via the IOPS MC connectivity function.
An IOPS MC connectivity function supporting the IP connectivity functionality does not provide MC services. Instead, the IOPS MC connectivity function enables discovering MC service users and provides IP connectivity for the communication among the discovered MC service users, i.e. it distributes the related IP traffic to the MC service UEs over IP unicast and/or multicast transmissions. A MC service UE supporting the IP connectivity functionality in the IOPS mode of operation enables transmitting the IP packets related to a MC service communication over the IOPS MC connectivity function.
This clause specifies requirements for the support of the IP connectivity functionality in the IOPS mode of operation.
5.4.2 General requirements p. 11
[AR-5.4.2-a]
The IOPS MC connectivity function supporting the IP connectivity functionality shall support discovering MC service users within the coverage of the local IOPS 3GPP system.
[AR-5.4.2-b]
The IOPS MC connectivity function supporting the IP connectivity functionality shall support announcement, subscription and notification mechanisms for discovered MC service users supporting the IP connectivity functionality.
[AR-5.4.2-c]
The IOPS MC connectivity function supporting the IP connectivity functionality shall provide IP connectivity for communication among MC service users requesting the support of the IP connectivity functionality.
[AR-5.4.2-d]
The MC service UEs supporting the IP connectivity functionality in the IOPS mode of operation shall enable transmitting the IP packets related to a MC service communication over the IOPS MC connectivity function.
5.4.3 Bearer management requirements p. 11
[AR-5.4.3-a]
The MC service UEs shall use specific APNs or DNNs for the support of the IP connectivity functionality, as follows:
- An APN/DNN for the IOPS related application signalling related to the IP connectivity functionality support, e.g. for IOPS discovery, subscription and notification.
- An MC service APN/DNN for the communication with another MC user or group via the IOPS MC connectivity function based on the IP connectivity functionality, e.g. for the signalling and media.
6 Involved business relationships p. 11
The description of the involved business relationships for the support of MC services in the IOPS mode of operation is contained in clause 6 of TS 23.280, and clause 6.4 of TS 23.289.
