ETSI TS 125 419-2017 Universal Mobile Telecommunications System (UMTS) UTRAN Iu-BC interface Service Area Broadcast Protocol (SABP) (V14 0 0 3GPP TS 25 419 version 14 0 0 Release 1.pdf

1、 ETSI TS 125 419 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); UTRAN Iu-BC interface: Service Area Broadcast Protocol (SABP) (3GPP TS 25.419 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 419 V14.0.0 (2017-04)13GPP TS 25.419 version 14.0.0 Release 14Refere

2、nce RTS/TSGR-0325419ve00 Keywords 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 Important notice The pres

3、ent 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 ETS

4、I. 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 t

5、he 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: h

6、ttps:/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

7、 be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the

8、benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 125 419 V14.0.0 (2017-04)23GPP TS 25.419 version 14.0.0 Rel

9、ease 14Intellectual Property Rights 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 can be found in ETSI SR 000 314: “Intellectual P

10、roperty 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

11、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. Foreword This Technical Specification (TS) has been pr

12、oduced 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

13、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

14、 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 ETSI TS 125 419 V14.0.0 (2017-04)33GPP TS 25.419 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3For

15、eword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 General . 8g34.1 Procedure Specification Principles . 8g34.2 Forwards and Backwards Compatibility 9g34.3 Specification Notations 9g35 Servic

16、es provided by SABP . 9g36 Services expected from the Transport layer . 9g37 Functions of SABP . 10g38 SABP Procedures . 10g38.1 Elementary Procedures . 10g38.2 Write-Replace . 10g38.2.1 General 10g38.2.2 Successful Operation 11g38.2.3 Unsuccessful Operation 12g38.2.4 Abnormal Conditions 13g38.3 Kil

17、l 13g38.3.1 General 13g38.3.2 Successful Operation 13g38.3.3 Unsuccessful Operation 14g38.3.4 Abnormal Conditions 14g38.4 Load Status Enquiry . 14g38.4.1 General 14g38.4.2 Successful Operation 14g38.4.3 Unsuccessful Operation 15g38.4.4 Abnormal Conditions 15g38.5 Message Status Query 15g38.5.1 Gener

18、al 15g38.5.2 Successful Operation 16g38.5.3 Unsuccessful Operation 16g38.5.4 Abnormal Conditions 17g38.6 Reset . 17g38.6.1 General 17g38.6.2 Successful Operation 17g38.6.3 Unsuccessful Operation 17g38.6.4 Abnormal Conditions 18g38.7 Restart Indication . 18g38.7.1 General 18g38.7.2 Successful Operati

19、on 18g38.7.3 Abnormal Conditions 18g38.8 Failure Indication . 18g38.8.1 General 18g38.8.2 Successful Operation 19g38.8.3 Abnormal Conditions 19g3ETSI ETSI TS 125 419 V14.0.0 (2017-04)43GPP TS 25.419 version 14.0.0 Release 148.9 Error Indication 19g38.9.1 General 19g38.9.2 Successful Operation 19g38.

20、9.3 Abnormal Conditions 20g39 Elements for SABP Communication 20g39.1 Message Functional Definition and Content 20g39.1.1 General 20g39.1.2 Message Contents . 20g39.1.2.1 Presence 20g39.1.2.2 Criticality 20g39.1.2.3 Range 20g39.1.2.4 Assigned Criticality . 21g39.1.3 WRITE-REPLACE . 21g39.1.4 WRITE-R

21、EPLACE COMPLETE . 21g39.1.5 WRITE-REPLACE FAILURE . 21g39.1.6 KILL . 22g39.1.7 KILL COMPLETE . 22g39.1.8 KILL FAILURE . 22g39.1.9 LOAD QUERY 22g39.1.10 LOAD QUERY COMPLETE. 23g39.1.11 LOAD QUERY FAILURE . 23g39.1.12 MESSAGE STATUS QUERY . 23g39.1.13 MESSAGE STATUS QUERY COMPLETE . 23g39.1.14 MESSAGE

22、 STATUS QUERY FAILURE . 24g39.1.15 RESET 24g39.1.16 RESET COMPLETE 24g39.1.17 RESET FAILURE 24g39.1.18 RESTART. 25g39.1.19 FAILURE . 25g39.1.20 ERROR INDICATION . 25g39.2 Information Element Definitions 25g39.2.0 General 25g39.2.1 MessageType 26g39.2.2 Broadcast Message Content 26g39.2.3 Serial Numb

23、er . 26g39.2.4 Old Serial Number 26g39.2.5 New Serial Number 27g39.2.6 Service Areas List . 27g39.2.7 Category 27g39.2.8 Repetition Period 27g39.2.9 Number of Broadcasts Requested . 27g39.2.10 Number of Broadcasts Completed List . 28g39.2.11 Service Area Identifier 29g39.2.12 Failure List 29g39.2.13

24、 Radio Resource Loading List 29g39.2.14 Cause 30g39.2.15 Data Coding Scheme 32g39.2.16 Recovery Indication 32g39.2.17 Criticality Diagnostics 32g39.2.18 Available Bandwidth 34g39.2.19 Message Identifier. 34g39.2.20 Message Structure . 34g39.2.21 Paging ETWS Indicator 35g39.2.22 Warning Type . 35g39.

25、2.23 Warning Security Information 36g39.2.24 Broadcast Message Content Validity Indicator. 36g39.3 Message and Information Element Abstract Syntax (with ASN.1) 36g39.3.0 General 36g39.3.1 Usage of protocol extension mechanism for non-standard use . 36g39.3.2 Elementary Procedure Definitions 38g39.3.

26、3 PDU Definitions . 41g3ETSI ETSI TS 125 419 V14.0.0 (2017-04)53GPP TS 25.419 version 14.0.0 Release 149.3.4 Information Element Definitions 51g39.3.5 Common Definitions. 56g39.3.6 Constant Definitions . 57g39.3.7 Container Definitions 59g39.4 Message Transfer Syntax . 62g310 Handling of Unknown, Un

27、foreseen or Erroneous Protocol Data . 62g310.1 General . 62g310.2 Transfer Syntax Error . 62g310.3 Abstract Syntax Error . 62g310.3.1 General 62g310.3.2 Criticality Information 63g310.3.3 Presence Information 63g310.3.4 Not comprehended IE/IE group 64g310.3.4.1 Procedure Code . 64g310.3.4.1A Type of

28、 Message . 64g310.3.4.2 IEs other than the Procedure Code and Type of Message . 64g310.3.5 Missing IE or IE group . 65g310.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 66g310.4 Logical Error 67g310.5 Exceptions 67g3Annex A (informative): Guidelines

29、 for Usage of the Criticality Diagnostics IE . 68g3A.1 EXAMPLE MESSAGE Layout . 68g3A.2 Example on a Received EXAMPLE MESSAGE . 69g3A.3 Content of Criticality Diagnostics 70g3A.3.1 Example 1 . 70g3A.3.2 Example 2 . 71g3A.3.3 Example 3 . 72g3A.3.4 Example 4 . 73g3A.3.5 Example 5 . 74g3A.4 ASN.1 of EX

30、AMPLE MESSAGE . 75g3Annex B (informative): Change history . 78g3History 80g3ETSI ETSI TS 125 419 V14.0.0 (2017-04)63GPP TS 25.419 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present documen

31、t 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

32、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 increm

33、ented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 419 V14.0.0 (2017-04)73GPP TS 25.419 version 14.0.0 Release 141 Scope The present document specifies the Service Area Broadcast Protocol (SABP) between the Cell Broadcast Centre (CBC) and the Radio Network Con

34、troller (RNC). It fulfils the CBC - RNC communication requirements specified in TS 23.041 5 and is defined over the Iu-BC reference point. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are eith

35、er 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 no

36、n-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 Void 2 Void 3 Void 4 3GPP TR 25.931: “UTRAN Functions: Examples on Signalling Procedures“. 5 3GPP TS 23.041: “Technical realization of Cell Broadcast Service (CBS)“. 6 3GPP TS

37、 25.414: “UTRAN Iu Interface Data Transport and Transport Signalling“. 7 ITU-T Recommendation X.680 (2002-07): “Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 8 ITU-T Recommendation X.681 (2002-07): “Information Technology - Abstract Syntax Notation

38、One (ASN.1): Information object specification“. 9 ITU-T Recommendation X.691 (2002-07): “Information Technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)“. 10 3GPP TR 25.921 (Version 7.0.0): “Guidelines and Principles for Protocol Description and Error Handling“. 11 3GPP

39、TS 25.324: “Broadcast/Multicast Control BMC“. 12 3GPP TS 23.003: “Numbering, addressing and identification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: Elementary Procedure: SABP consists of Elementary Procedur

40、es (EPs). An Elementary Procedure is a unit of interaction between the CN (CBC) and the RNC. These EPs 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 des

41、cription. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each ETSI ETSI TS 125 419 V14.0.0 (2017-04)83GPP TS 25.419 version 14.0.0 Release 14other as stand alone procedures, which can be active in parallel. Examples on using several SABP EPs together with each o

42、ther and EPs from other interfaces can be found in reference TR 25.931 4. 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 or failure). - Class 2: Elementary Procedures without response. For Cl

43、ass 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

44、 (i.e. absence of expected response). Class 2 EPs are considered always successful. Message Reference: This is defined as consisting of the following parameters: Message Identifier, Serial Number, and SAI (Service Area Identifier). 3.2 Abbreviations For the purposes of the present document, the foll

45、owing abbreviations apply: CBC Cell Broadcast Centre CBS Cell Broadcast Service CN Core Network EP Elementary Procedure FP Frame Protocol PDU Protocol Data Unit RNC Radio Network Controller SA Service Area SABP Service Area Broadcast Protocol 4 General The protocol described in the present document

46、is the protocol between CN (CBC) and RNC needed for the CBC Application. The CBC Application is described in TS 23.041 5. 4.1 Procedure Specification Principles The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and completely. The CN functiona

47、l behaviour is left unspecified. The following specification principles have been applied for the procedure text in clause 8: - The procedure text discriminates between: 1) Functionality which “shall“ be executed: - The procedure text indicates that the receiving node “shall“ perform a certain funct

48、ion Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause v

49、alue. ETSI ETSI TS 125 419 V14.0.0 (2017-04)93GPP TS 25.419 version 14.0.0 Release 142) Functionality which “shall, if supported“ be executed: - The procedure text indicates that the receiving node “shall, if supported,“ perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. - Any required inclusion of an optional IE i