LTE; Common functional architecture to support mission critical services; Stage 2 (3GPP TS 23.280 version 14.6.0 Release 14)

RTS/TSGS-0623280ve60

General Information

Status
Published
Publication Date
03-Jul-2018
Current Stage
12 - Completion
Completion Date
04-Jul-2018
Ref Project

Buy Standard

Standard
ETSI TS 123 280 V14.6.0 (2018-07) - LTE; Common functional architecture to support mission critical services; Stage 2 (3GPP TS 23.280 version 14.6.0 Release 14)
English language
146 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TS 123 280 V14.6.0 (2018-07)






TECHNICAL SPECIFICATION
LTE;
Common functional architecture to support mission critical
services;
Stage 2
(3GPP TS 23.280 version 14.6.0 Release 14)

---------------------- Page: 1 ----------------------
3GPP TS 23.280 version 14.6.0 Release 14 1 ETSI TS 123 280 V14.6.0 (2018-07)



Reference
RTS/TSGS-0623280ve60
Keywords
LTE
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

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 only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
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
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 2018.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 23.280 version 14.6.0 Release 14 2 ETSI TS 123 280 V14.6.0 (2018-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 IPR Policy, no investigation, 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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 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.280 version 14.6.0 Release 14 3 ETSI TS 123 280 V14.6.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 10
1 Scope . 11
2 References . 11
3 Definitions, symbols and abbreviations . 12
3.1 Definitions . 12
3.2 Symbols . 13
3.3 Abbreviations . 13
4 Introduction . 14
5 Assumptions and architectural requirements . 15
5.1 Assumptions . 15
5.1.1 Service continuity . 15
5.1.2 Trust domain . 15
5.2 Architectural requirements . 15
5.2.1 General architectural requirements . 15
5.2.2 Roaming requirements . 16
5.2.3 UE-to-network relay MC service requirements . 16
5.2.4 MC service user profile requirements . 16
5.2.5 MC service group affiliation and MC service group de-affiliation . 16
5.2.6 GCS AS requirements for the MC services . 17
5.2.7 Bearer management . 17
5.2.7.0 General . 17
5.2.7.1 MBMS bearer management . 18
5.2.7.2 EPS bearer considerations . 18
5.2.8 External applications access to services in a MC system . 19
6 Involved business relationships . 19
7 Functional model . 22
7.1 General . 22
7.2 Description of the planes . 22
7.3 Functional model description . 22
7.3.1 On-network functional model . 22
7.3.2 Off-network functional model . 25
7.4 Functional entities description . 26
7.4.1 General . 26
7.4.2 Application plane . 26
7.4.2.1 General . 26
7.4.2.2 Common services core . 26
7.4.2.2.1 Configuration management client. 26
7.4.2.2.2 Configuration management server . 26
7.4.2.2.3 Group management client . 27
7.4.2.2.4 Group management server . 27
7.4.2.2.5 Identity management client . 27
7.4.2.2.6 Identity management server . 27
7.4.2.2.7 Key management client . 27
7.4.2.2.8 Key management server . 27
7.4.2.2.9 Location management client . 27
7.4.2.2.10 Location management server . 27
7.4.2.3 MC service . 28
7.4.2.3.1 MC service client . 28
7.4.2.3.2 MC service server . 28
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 23.280 version 14.6.0 Release 14 4 ETSI TS 123 280 V14.6.0 (2018-07)
7.4.2.3.3 MC service user database . 28
7.4.3 Signalling control plane . 28
7.4.3.1 SIP entities . 28
7.4.3.1.1 Signalling user agent . 28
7.4.3.1.2 SIP AS . 28
7.4.3.1.3 SIP core . 28
7.4.3.1.3.1 General . 28
7.4.3.1.3.2 Local inbound / outbound proxy . 29
7.4.3.1.3.3 Registrar finder . 29
7.4.3.1.3.4 Registrar / application service selection . 29
7.4.3.2 SIP database . 30
7.4.3.2.1 General . 30
7.4.3.2.2 SIP database logical functions . 30
7.4.3.3 HTTP entities . 31
7.4.3.3.1 HTTP client . 31
7.4.3.3.2 HTTP proxy . 31
7.4.3.3.3 HTTP server . 31
7.5 Reference points . 31
7.5.1 General reference point principle . 31
7.5.2 Application plane . 32
7.5.2.1 General . 32
7.5.2.2 Reference point CSC-1 (between the identity management client and the identity management
server) . 32
7.5.2.3 Reference point CSC-2 (between the group management client and the group management server
for configuration while UE is on-network) . 32
7.5.2.4 Reference point CSC-3 (between the MC service server and the group management server) . 32
7.5.2.5 Reference point CSC-4 (between the configuration management client and the configuration
management server for configuration while UE is on-network) . 32
7.5.2.6 Reference point CSC-5 (between the MC service server and the configuration management
server) . 33
7.5.2.7 Reference point CSC-7 (between the group management servers) . 33
7.5.2.8 Reference point CSC-8 (between the key management server and the key management client) . 33
7.5.2.9 Reference point CSC-9 (between the key management server and the MC service server) . 33
7.5.2.10 Reference point CSC-10 (between the key management server and the group management
server) . 33
7.5.2.11 Reference point CSC-11 (between the configuration management client and the configuration
management server for configuration while UE is off-network). 33
7.5.2.12 Reference point CSC-12 (between the group management client and the group management
server for configuration while UE is off-network) . 34
7.5.2.13 Reference point CSC-13 (between the configuration management server and the MC service user
database) . 34
7.5.2.14 Reference point CSC-14 (between the location management client and the location management
server) . 34
7.5.2.15 Reference point CSC-15 (between the location management server and the MC service server) . 34
7.5.3 Signalling control plane . 34
7.5.3.1 General . 34
7.5.3.2 Reference point SIP-1(between the signalling user agent and the SIP core) . 34
7.5.3.3 Reference point SIP-2 (between the SIP core and the SIP AS) . 35
7.5.3.4 Reference point SIP-3 (between the SIP core and SIP core) . 35
7.5.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy) . 35
7.5.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server) . 35
7.5.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy) . 35
7.5.3.8 Reference point AAA-1 (between the SIP database and the SIP core) . 35
8 Identities . 36
8.1 Application plane . 36
8.1.1 Mission Critical user identity (MC ID) . 36
8.1.2 MC service user identity (MC service ID) . 36
8.1.3 MC service group identity (MC service group ID) . 36
8.1.3.1 General . 36
8.1.3.2 MC service group ID management (off-network operation) . 37
8.2 SIP signalling control plane. 37
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 23.280 version 14.6.0 Release 14 5 ETSI TS 123 280 V14.6.0 (2018-07)
8.3 Relationship between identities in different planes . 38
8.3.1 Relationship between MC service ID and public user identity . 38
8.3.2 Relationship between MC service group ID and public service identity . 38
9 Application of functional model to deployments . 39
9.1 General . 39
9.2 Architecture model and deployment scenarios for on-network operations . 39
9.2.1 On-network architectural model . 39
9.2.1.1 On-network architectural model diagram . 39
9.2.1.2 Application services layer . 40
9.2.1.2.1 Overview . 40
9.2.1.2.2 Common services core . 40
9.2.1.2.3 MC services . 40
9.2.1.3 SIP core . 40
9.2.1.4 EPS . 41
9.2.1.5 UE 1 . 41
9.2.1.6 UE 2 . 41
9.2.2 Deployment scenarios . 41
9.2.2.1 Administration of MC service, SIP core and EPS . 41
9.2.2.1.1 General . 41
9.2.2.1.2 Common administration of all planes . 41
9.2.2.1.3 MC service provider separate from SIP core and EPS . 42
9.2.2.1.4 MC service provider administers SIP core, separate from EPS . 43
9.2.2.1.5 SIP core partially administered by both PLMN operator and MC service provider . 43
9.2.2.1.6 PLMN operator administers SIP core with SIP identities administered by MC service
provider . 44
9.2.2.2 MC service user database, SIP database and HSS . 45
9.2.2.3 Control of bearers by SIP core and MC service server . 48
9.2.2.3.1 General . 48
9.2.2.3.2 Control of bearers by SIP core . 48
9.2.2.3.3 Control of bearers by MC service server . 48
9.3 Architecture model for off-network operations . 48
9.3.1 Off-network architectural model diagram . 48
9.3.2 UE 3 . 49
9.3.3 UE 4 . 49
9.3.4 Offline common services server . 50
9.4 Architecture model for roaming . 50
10 Procedures and information flows . 50
10.1 MC service configuration . 50
10.1.1 General . 50
10.1.2 Information flows for MC service configuration . 51
10.1.2.1 Store group configuration request . 51
10.1.2.2 Store group configuration response . 51
10.1.2.3 Get group configuration request . 51
10.1.2.4 Get group configuration response . 52
10.1.2.5 Subscribe group configuration request . 52
10.1.2.6 Subscribe group configuration response . 52
10.1.2.7 Notify group configuration request . 52
10.1.2.8 Notify group configuration response . 52
10.1.3 MC service UE configuration data . 53
10.1.3.1 General . 53
10.1.3.2 Procedures . 53
10.1.3.3 Structure of UE configuration data . 53
10.1.4 MC service user profile .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.