|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Cell Broadcast Centre interfaces with
the Evolved Packet Core;
Stage 3
(3GPP TS 29.168 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 1 ETSI TS 129 168 V15.0.0 (2018-07)
Reference
RTS/TSGC-0429168vf00
Keywords
LTE,UMTS
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:
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
If you find errors in the present document, please send your comment to one of the following services:
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 29.168 version 15.0.0 Release 15 2 ETSI TS 129 168 V15.0.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
.
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 29.168 version 15.0.0 Release 15 3 ETSI TS 129 168 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 SBc description . 8
4.1 Transport . 8
4.1.1 General . 8
4.1.2 Network layer . 8
4.1.3 Transport layer . 8
4.1.4 Services expected from signalling transport . 8
4.2. SBc-AP functions . 8
4.2.1 Function of SBc-AP . 8
4.3 SBc-AP procedure . 8
4.3.1 General . 8
4.3.2 List of SBc-AP elementary procedure . 9
4.3.3 Write Replace Warning Procedure . 9
4.3.3.1 General . 9
4.3.3.2 Successful Operation . 9
4.3.3.3 Unsuccessful Operation . 10
4.3.3A Stop Warning Procedure . 10
4.3.3A.1 General . 10
4.3.3A.2 Successful Operation . 10
4.3.3A.3 Unsuccessful Operation . 11
4.3.3B Error Indication . 11
4.3.3B.1 General . 11
4.3.3B.2 Successful Operation . 11
4.3.3B.3 Abnormal Conditions . 12
4.3.3C Write Replace Warning Indication . 12
4.3.3C.1 General . 12
4.3.3C.2 Successful Operation . 12
4.3.3C.3 Abnormal Conditions . 12
4.3.3D Stop Warning Indication . 12
4.3.3D.1 General . 12
4.3.3D.2 Successful Operation . 12
4.3.3D.3 Abnormal Conditions . 13
4.3.3E PWS Restart Indication . 13
4.3.3E.1 General . 13
4.3.3E.2 Successful Operation . 13
4.3.3E.3 Abnormal Conditions . 14
4.3.3F PWS Failure Indication . 14
4.3.3F.1 General . 14
4.3.3F.2 Successful Operation . 14
4.3.3F.3 Abnormal Conditions . 14
4.3.4 Message functional definition and content . 14
4.3.4.1 Message contents . 14
4.3.4.1.1 Presence . 14
4.3.4.1.2 Criticality . 14
4.3.4.1.3 Range . 15
4.3.4.1.4 Assigned Criticality . 15
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 4 ETSI TS 129 168 V15.0.0 (2018-07)
4.3.4.2 Warning Message Transmission Messages . 15
4.3.4.2.1 WRITE-REPLACE WARNING REQUEST . 15
4.3.4.2.2 WRITE-REPLACE WARNING RESPONSE . 16
4.3.4.2.3 STOP WARNING REQUEST . 17
4.3.4.2.4 STOP WARNING RESPONSE . 18
4.3.4.2.5 WRITE REPLACE WARNING INDICATION . 18
4.3.4.2.6 STOP WARNING INDICATION . 18
4.3.4.2.7 PWS RESTART INDICATION . 19
4.3.4.2.8 PWS FAILURE INDICATION . 20
4.3.4.2A Management Messages . 21
4.3.4.2A.1 ERROR INDICATION . 21
4.3.4.3 Information element definition. 21
4.3.4.3.1 Message Type . 21
4.3.4.3.2 Cause . 22
4.3.4.3.3 Criticality Diagnostics . 22
4.3.4.3.4 OMC ID . 23
4.3.4.3.5 Send Write-Replace-Warning-Indication . 23
4.3.4.3.6 Unknown Tracking Area List . 24
4.3.4.3.7 Send Stop Warning Indication . 24
4.3.4.3.8 Stop-All Indicator . 24
4.3.4.3.9 Broadcast Empty Area List. 24
4.3.4.3.10 RAT Selector 5GS . 24
4.3.4.3.11 Unknown 5GS Tracking Area List . 25
4.3.4.3.12 Broadcast Scheduled Area List 5GS . 25
4.3.4.3.13 Broadcast Cancelled Area List 5GS . 25
4.3.4.3.14 Broadcast Empty Area List 5GS . 25
4.4 Message and information element abstract syntax . 26
4.4.1 General . 26
4.4.2 Usage of protocol extension mechanism for non-standard use . 26
4.4.3 Elementary procedure definitions . 26
4.4.4 PDU definitions . 29
4.4.5 Information element definitions . 34
4.4.6 Common definitions . 42
4.4.7 Constant definitions . 43
4.4.8 Container Definitions . 44
4.4.9 Message transfer syntax . 47
4.5 Handling of unknown, unforeseen or erroneous protocol data . 47
4.5.1 General . 47
4.5.2 Transfer Syntax Error . 47
4.5.3 Abstract Syntax Error . 47
4.5.3.1 General . 47
4.5.3.2 Criticality information . 48
4.5.3.3 Presence information . 48
4.5.3.4 Not comprehended IE/IE group . 49
4.5.3.4.1 Procedure code . 49
4.5.3.4.2 Type of Message . 49
4.5.3.4.3 IEs other than the Procedure Code and Type of Message . 49
4.5.3.5 Missing IE or IE group . 50
4.5.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present . 51
4.5.4 Logical Error . 52
4.5.5 Exceptions . 52
Annex A (informative): Change history: . 53
History . 55
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 5 ETSI TS 129 168 V15.0.0 (2018-07)
Foreword
rd
This Technical Specification has been produced by the 3 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.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 6 ETSI TS 129 168 V15.0.0 (2018-07)
1 Scope
The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP
interface between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC), and between the
Public Warning System – Inter Working Function (PWS-IWF) and the CBC.
The present document supports the following functions:
- Warning Message Transmission function in the EPS,
- Warning Message Transmission function in the 5GS via the PWS-IWF (see 3GPP TS 23.041 [14]).
NOTE: The SBc-AP interface is a logical interface between the MME and the CBC and also between the PWS-
IWF and the CBC, when connected to 5GC. The PWS-IWF may not be always explicitly mentioned in
the remainder of the present document.
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] IETF RFC 2460 (December 1998): "Internet Protocol, Version 6 (IPv6) Specification".
[3] IETF RFC 791 (September 1981): "Internet Protocol".
[4] IETF RFC 4960 (September 2007): "Stream Control Transmission Protocol".
[5] Void
[6] Void
[7] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1
Application Protocol (S1AP)"
[8] ITU-T Recommendation X.680 (07/2002): "Information Technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[9] ITU-T Recommendation X.681 (07/2002): "Information Technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[10] ITU-T Recommendation X.691 (07/2002): "Information Technology - ASN.1 encoding rules -
Specification of Packed Encoding Rules (PER)".
[11] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[12] Void
[13] 3GPP TS 22.268: "Public Warning System (PWS) requirements".
[14] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".
[15] Void
[16] 3GPP TS 23.007: "Restoration procedures".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 7 ETSI TS 129 168 V15.0.0 (2018-07)
[17] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
3 Definitions and abbreviations
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].
Elementary Procedure: SBc-AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of
interaction between MME and CBC. These Elementary Procedures are defined separately and are intended to be used to
build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described
under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of
each other as stand alone procedures, which can be active in parallel. Examples on using several SBc-APs together with
each other and EPs from other interfaces can be found in reference [FFS].
An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
- Class 1: Elementary Procedures with response (success and/or failure).
- Class 2: Elementary Procedures without response.
For Class 1 EPs, the types of responses can be as follows:
Successful:
- A signalling message explicitly indicates that the elementary procedure successfully completed with the
receipt of the response.
Unsuccessful:
- A signalling message explicitly indicates that the EP failed.
- On time supervision expiry (i.e. absence of expected response).
Successful and Unsuccessful:
- One signalling message reports both successful and unsuccessful outcome for the different included requests.
The response message used is the one defined for successful outcome.
Class 2 EPs are considered always successful.
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].
5GC 5G Core
CMAS Commercial Mobile Alert System
CBC Cell Broadcast Center
CBS Cell Broadcast Service
EPC Evolved Packet Core
EPS Evolved Packet System
ETWS Earthquake and Tsunami Warning System
MME Mobility Management Entity
PWS Public Warning System
PWS-IWF PWS – Inter Working Function
SCTP Stream Control Transmission Protocol
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 29.168 version 15.0.0 Release 15 8 ETSI TS 129 168 V15.0.0 (2018-07)
4 SBc description
4.1 Transport
4.1.1 General
This subclause specifies the standards for signalling transport to be used across SBc-AP interface. SBc-AP interface is a
logical interface between the MME and the CBC. All the SBc-AP messages described in the present document require
an SCTP association between the MME and the CBC.
4.1.2 Network layer
The MME and the CBC shall support IPv6 (see IETF RFC 2460 [2]) and/or IPv4 (see IETF RFC 791 [3]).
The IP layer of SBc-AP only supports point-to-point transmission for delivering SBc-AP messages.
4.1.3 Transport layer
SCTP (see IETF RFC 4960 [4]) shall be supported as the transport layer of SBc-AP messages.
Semi-permanent SCTP associations shall be established between MME and CBC, i.e. the SCTP associations shall
remain up under normal circumstances.
Local multi-homing should be supported. Remote multi-homing shall be supported.
Multiple local SCTP endpoints may be supported. Multiple remote SCTP endpoints shall be supported. When multiple
local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between
MME and CBC.
Checksum calculation for SCTP shall be supported as specified in RFC 4960 [4].
The CBC shall establish the SCTP association.
The registered port number for SBc-AP is 29168.
The registered payload protocol identifier for SBc-AP is 24.
4.1.4 Services expected from signalling transport
The signalling connection shall provide in-sequence delivery of SBc-AP messages. SBc-AP shall be notified if the
signalling connection breaks.
4.2. SBc-AP functions
4.2.1 Function of SBc-AP
SBc-AP has the following function:
- Warning Messa
...