ETSI TS 123 289 V17.1.0 (2022-05)

5G; Mission Critical services over 5G System; Stage 2 (3GPP TS 23.289 version 17.1.0 Release 17)

RTS/TSGS-0623289vh10

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 6 - Mission-critical applications
• Current Stage: 12 - Completion
• Completion Date: 11-May-2022

Standards Content (Sample)

ETSI TS 123 289 V17.1.0 (2022-05)






TECHNICAL SPECIFICATION
5G;
Mission Critical services over 5G System;
Stage 2
(3GPP TS 23.289 version 17.1.0 Release 17)

---------------------- Page: 1 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 1 ETSI TS 123 289 V17.1.0 (2022-05)

Reference
RTS/TSGS-0623289vh10
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 2 ETSI TS 123 289 V17.1.0 (2022-05)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (https://ipr.etsi.org/).
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and of the 3GPP
Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of the
®
oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 3 ETSI TS 123 289 V17.1.0 (2022-05)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
Introduction . 7
1 Scope . 8
2 References . 8
3 Definitions of terms, symbols and abbreviations . 9
3.1 Terms . 9
3.2 Symbols . 9
3.3 Abbreviations . 9
4 MC service system resource requirements . 9
4.1 Multiple Access . 9
4.1.1 General . 9
4.1.2 Requirements . 9
4.2 Session connectivity . 10
4.2.1 General . 10
4.2.2 Requirements . 10
4.3 QoS characteristics . 10
4.3.1 General . 10
4.3.2 QoS requirements for general purposes . 11
4.3.3 QoS requirements for Mission Critical Push to Talk . 11
4.3.3.1 General . 11
4.3.3.2 5QI values for MCPTT . 11
4.3.3.3 Use of priorities . 11
4.3.4 QoS requirements for Mission Critical Video . 11
4.3.4.1 General . 11
4.3.4.2 5QI values for MCVideo . 11
4.3.4.3 Use of priorities . 12
4.3.5 QoS requirements for Mission Critical Data . 12
4.3.5.1 General . 12
4.3.5.2 5QI values for MCData . 12
4.3.5.3 Use of priorities . 12
4.4 Network Slicing . 12
4.4.1 General . 12
4.4.2 Requirements . 13
4.5 Use of public and non-public networks . 13
4.5.1 General . 13
4.5.2 Requirements . 13
4.6 Migration . 13
4.6.1 General . 13
4.6.2 Public network utilization . 13
4.6.3 Non-Public network utilization . 14
5. MC system functional model . 14
5.1 General . 14
5.2 Description of the planes . 14
5.3 Common functional model description . 15
5.3.1 On-network functional model . 15
5.3.2 Functional entities description . 18
5.3.2.1 General . 18
5.3.2.2 Application plane . 18
5.3.2.3 Signalling control plane . 18
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 4 ETSI TS 123 289 V17.1.0 (2022-05)
5.3.3 Reference points . 18
5.3.3.1 General reference point principle . 18
5.3.3.2 Application plane . 18
5.3.3.2.1 General . 18
5.3.3.3 Signalling control plane . 18
5.3.3.3.1 General . 18
5.3.3.3.2 Reference point SIP-1(between the signalling user agent and the SIP core) . 18
5.3.3.3.3 Reference point SIP-2 (between the SIP core and the SIP AS) . 19
5.3.3.3.4 Reference point SIP-3 (between the SIP core and SIP core) . 19
5.3.3.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy) . 19
5.3.3.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server) . 19
5.3.3.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy) . 19
5.3.3.3.8 Reference point AAA-1 (between the SIP database and the SIP core) . 19
5.3.3.3.9 Reference point AAA-2 (between the SIP core and Diameter proxy) . 19
5.3.3.3.10 Reference points N5 and Rx (between the SIP core and the 5GS) . 19
5.4 MCPTT functional model description . 19
5.4.1 On-network functional model . 19
5.5 MCVideo functional model description . 20
5.5.1 On-network functional model . 20
5.6 MCData functional model description . 21
5.6.1 On-network functional model . 21
6. Application of functional models and deployment scenarios . 22
6.1 General . 22
6.2 On-network architectural model . 22
6.2.1 On-network architectural model diagram . 22
6.2.2 Application services layer . 23
6.2.2.1 Overview . 23
6.2.2.2 Common services core . 23
6.2.2.3 MC services. 23
6.2.3 SIP core . 23
6.2.4 5GS . 23
6.2.5 UE 1 . 23
6.3 Deployment scenarios . 24
6.3.1 Administration of MC service, SIP core and 5GS . 24
6.3.1.1 General . 24
6.3.1.2 Common administration of all planes . 24
6.3.1.3 MC service provider separate from SIP core and 5GS . 24
6.3.1.4 MC service provider administers SIP core, separate from 5GS . 25
6.3.1.5 SIP core partially administered by both PLMN operator and MC service provider . 26
6.3.1.6 PLMN operator administers SIP core with SIP identities administered by MC service provider . 26
6.3.2 Resource management of MC service sessions by SIP core and MC service server . 27
6.3.2.1 General . 27
6.3.2.2 Resource Management of MC service sessions by SIP core . 27
6.3.2.3 Management of MC service sessions by MC service server . 28
6.4 Involved business relationships . 28
6.4.1 General . 28
6.4.2 Public network and non-public network utilization . 28
7. MC procedures for 5GS . 29
7.1 General . 29
7.2 MC service resource management (on-network) . 30
7.2.1 General . 30
7.2.2 Request for unicast resources at session establishment . 30
7.2.3 Request for unicast resources at session establishment from MC service server . 31
7.2.3.1 General . 31
7.2.3.2 Procedure . 31
7.2.4 Request for modification of unicast resources . 32
7.2.5 Request for media resources from MC service server . 34
7.2.5.1 General . 34
7.2.5.2 Procedure . 34
Annex A (normative): Configuration data for MC services using 5GS . 37
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 5 ETSI TS 123 289 V17.1.0 (2022-05)
A.1 General . 37
A.2 Initial MC service UE configuration data . 37
Annex B (informative): Change history . 38
History . 39

ETSI

---------------------- Page: 6 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 6 ETSI TS 123 289 V17.1.0 (2022-05)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 7 ETSI TS 123 289 V17.1.0 (2022-05)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
Introduction
The use of 5GS to support MC services (i.e., MCPTT defined in 3GPP TS 23.379 [6], MCVideo defined in
3GPP TS 23.281 [4], MCData defined in 3GPP TS 23.282 [5]) including common application plane and signalling
plane entities is specified in the present document.
Each MC service supports several types of communications amongst the users (e.g. group communication, peer to peer
communication). There are several general functions and entities (e.g. configuration, identity) which are used by the
MC services. The general functional architecture to support MC services utilizes aspects of the IMS architecture
specified in 3GPP TS 23.228 [2].
An MC service UE in the 5GS context obtains access to a MC service via 3GPP access (i.e., E-UTRA, 5G NR),
wireless non-3GPP access (e.g. WLAN or Satellite) and/or wireline access using the 5GS architecture defined in
3GPP TS 23.501 [7]. Certain MC service functions such as dispatch and administrative functions can be supported
using MC service UEs with 3GPP access and non-3GPP wireless/wireline access. External applications usage of MC
services can be enabled via 3GPP access and/or non-3GPP access.
NOTE: Dispatch consoles and devices used by MC service administrators are considered as MC service UEs to
support MC services.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 23.289 version 17.1.0 Release 17 8 ETSI TS 123 289 V17.1.0 (2022-05)
1 Scope
The present document specifies the use of the 5G System (5GS) considering common functional architecture,
procedures and information flows needed to support mission critical services encompassing the common services core
architecture.
The corresponding service requirements applied in 3GPP TS 23.280 [3], 3GPP TS 22.179 [11], 3GPP TS 22.280 [12],
3GPP TS 22.2
...