1、 ETSI TS 129 168 V14.2.0 (2018-01) Universal Mobile Telecommunications System (UMTS); LTE; Cell Broadcast Centre interfaces with the Evolved Packet Core; Stage 3 (3GPP TS 29.168 version 14.2.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 129 168 V14.2.0 (2018-01)13GPP TS 29.168 version 14.2.0 Re
2、lease 14Reference RTS/TSGC-0429168ve20 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Importa
3、nt 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 au
4、thorization 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 shou
5、ld 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 fol
6、lowing 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
7、 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3G
8、PPTM 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 ETSI TS 129 168 V14.2.0 (2018-01)23GPP
9、 TS 29.168 version 14.2.0 Release 14Intellectual Property Rights Essential patents IPRs essential or potentially essential to the present document 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 c
10、an 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 ET
11、SI 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. Tradema
12、rks 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
13、 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 re
14、fer 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/
15、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). “mus
16、t“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 168 V14.2.0 (2018-01)33GPP TS 29.168 version 14.2.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Defi
17、nitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 SBc description 8g34.1 Transport 8g34.1.1 General 8g34.1.2 Network layer . 8g34.1.3 Transport layer 8g34.1.4 Services expected from signalling transport . 8g34.2. SBc-AP functions . 8g34.2.1 Function of SBc-AP 8g34.3 SBc-AP p
18、rocedure 9g34.3.1 General 9g34.3.2 List of SBc-AP elementary procedure 9g34.3.3 Write Replace Warning Procedure 9g34.3.3.1 General 9g34.3.3.2 Successful Operation . 10g34.3.3.3 Unsuccessful Operation . 10g34.3.3A Stop Warning Procedure . 11g34.3.3A.1 General 11g34.3.3A.2 Successful Operation . 11g34
19、.3.3A.3 Unsuccessful Operation 11g34.3.3B Error Indication . 12g34.3.3B.1 General 12g34.3.3B.2 Successful Operation . 12g34.3.3B.3 Abnormal Conditions 12g34.3.3C Write Replace Warning Indication . 12g34.3.3C.1 General 12g34.3.3C.2 Successful Operation . 13g34.3.3C.3 Abnormal Conditions 13g34.3.3D St
20、op Warning Indication . 13g34.3.3D.1 General 13g34.3.3D.2 Successful Operation . 13g34.3.3D.3 Abnormal Conditions 13g34.3.3E PWS Restart Indication . 13g34.3.3E.1 General 13g34.3.3E.2 Successful Operation . 14g34.3.3E.3 Abnormal Conditions 14g34.3.3F PWS Failure Indication . 14g34.3.3F.1 General 14g
21、34.3.3F.2 Successful Operation . 15g34.3.3F.3 Abnormal Conditions 15g34.3.4 Message functional definition and content 15g34.3.4.1 Message contents 15g34.3.4.1.1 Presence . 15g34.3.4.1.2 Criticality . 15g34.3.4.1.3 Range . 16g34.3.4.1.4 Assigned Criticality . 16g3ETSI ETSI TS 129 168 V14.2.0 (2018-01
22、)43GPP TS 29.168 version 14.2.0 Release 144.3.4.2 Warning Message Transmission Messages . 16g34.3.4.2.1 WRITE-REPLACE WARNING REQUEST 16g34.3.4.2.2 WRITE-REPLACE WARNING RESPONSE 17g34.3.4.2.3 STOP WARNING REQUEST 17g34.3.4.2.4 STOP WARNING RESPONSE 17g34.3.4.2.5 WRITE REPLACE WARNING INDICATION . 1
23、8g34.3.4.2.6 STOP WARNING INDICATION . 18g34.3.4.2.7 PWS RESTART INDICATION 19g34.3.4.2.8 PWS FAILURE INDICATION . 19g34.3.4.2A Management Messages . 20g34.3.4.2A.1 ERROR INDICATION . 20g34.3.4.3 Information element definition 20g34.3.4.3.1 Message Type 20g34.3.4.3.2 Cause . 20g34.3.4.3.3 Criticalit
24、y Diagnostics . 21g34.3.4.3.4 OMC ID. 22g34.3.4.3.5 Send Write-Replace-Warning-Indication 22g34.3.4.3.6 Unknown Tracking Area List 23g34.3.4.3.7 Send Stop Warning Indication . 23g34.3.4.3.8 Stop-All Indicator 23g34.3.4.3.9 Broadcast Empty Area List 23g34.4 Message and information element abstract sy
25、ntax . 24g34.4.1 General 24g34.4.2 Usage of protocol extension mechanism for non-standard use . 24g34.4.3 Elementary procedure definitions . 24g34.4.4 PDU definitions 26g34.4.5 Information element definitions 31g34.4.6 Common definitions . 37g34.4.7 Constant definitions 37g34.4.8 Container Definitio
26、ns 39g34.4.9 Message transfer syntax . 41g34.5 Handling of unknown, unforeseen or erroneous protocol data . 41g34.5.1 General . 41g34.5.2 Transfer Syntax Error . 41g34.5.3 Abstract Syntax Error . 41g34.5.3.1 General 41g34.5.3.2 Criticality information 42g34.5.3.3 Presence information 42g34.5.3.4 Not
27、 comprehended IE/IE group 43g34.5.3.4.1 Procedure code 43g34.5.3.4.2 Type of Message . 43g34.5.3.4.3 IEs other than the Procedure Code and Type of Message . 43g34.5.3.5 Missing IE or IE group . 44g34.5.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 4
28、5g34.5.4 Logical Error 46g34.5.5 Exceptions 46g3Annex A (informative): Change history: 47g3History 49g3ETSI ETSI TS 129 168 V14.2.0 (2018-01)53GPP TS 29.168 version 14.2.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents
29、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: V
30、ersion 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
31、 third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 168 V14.2.0 (2018-01)63GPP TS 29.168 version 14.2.0 Release 141 Scope The present document specifies the procedures and the SBc Application Part (SBc-AP) messages used on the SBc-AP inter
32、face between the Mobility Management Entity (MME) and the Cell Broadcast Centre (CBC). The present document supports the following functions. - Warning Message Transmission function in the EPS. 2 References The following documents contain provisions which, through reference in this text, constitute
33、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
34、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
35、 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 Recommendat
36、ion 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): “
37、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
38、(CBS)“. 15 Void 16 3GPP TS 23.007: “Restoration procedures“. ETSI ETSI TS 129 168 V14.2.0 (2018-01)73GPP TS 29.168 version 14.2.0 Release 143 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
39、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 ar
40、e 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
41、 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: Elementa
42、ry 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 res
43、ponse. 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 respo
44、nse 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
45、over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. 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 W
46、arning System SCTP Stream Control Transmission Protocol ETSI ETSI TS 129 168 V14.2.0 (2018-01)83GPP TS 29.168 version 14.2.0 Release 144 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
47、 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-
48、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 rema
49、in 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 reg
