1、 ETSI TS 125 419 V4.8.0 (2003-06)Technical Specification Universal Mobile Telecommunications System (UMTS);UTRAN Iu-BC interface:Service Area Broadcast Protocol (SABP)(3GPP TS 25.419 version 4.8.0 Release 4)ETSI ETSI TS 125 419 V4.8.0 (2003-06) 1 3GPP TS 25.419 version 4.8.0 Release 4 Reference RTS/
2、TSGR-0325419v480 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 Individual copie
3、s of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (P
4、DF). In case of dispute, the reference shall be the printing on ETSI printers of the 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
5、 of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing r
6、estriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI
7、for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 125 419 V4.8.0 (2003-06) 2 3GPP TS 25.419 version 4.8.0 Release 4 Intellectual Property Rights IPRs essential or potentially essential to the
8、 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 Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI
9、in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as
10、 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 produced by ETSI 3rd Generation Partnership Project (3GPP). The presen
11、t 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:
12、/webapp.etsi.org/key/queryform.asp . ETSI ETSI TS 125 419 V4.8.0 (2003-06) 3 3GPP TS 25.419 version 4.8.0 Release 4 Contents Intellectual Property Rights2 Foreword.2 Foreword.6 1 Scope 7 2 References 7 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 General .8 4.1 Procedure
13、 Specification Principles.8 4.2 Forwards and Backwards Compatibility 9 4.3 Specification Notations 9 5 Services provided by SABP .9 6 Services expected from the Transport layer .9 7 Functions of SABP.10 8 SABP Procedures .10 8.1 Elementary Procedures.10 8.2 Write-Replace.10 8.2.1 General10 8.2.2 Suc
14、cessful Operation 11 8.2.3 Unsuccessful Operation 12 8.2.4 Abnormal Conditions13 8.3 Kill13 8.3.1 General13 8.3.2 Successful Operation 13 8.3.3 Unsuccessful Operation 14 8.3.4 Abnormal Conditions14 8.4 Load Status Enquiry .14 8.4.1 General14 8.4.2 Successful Operation 14 8.4.3 Unsuccessful Operation
15、 15 8.4.4 Abnormal Conditions15 8.5 Message Status Query 15 8.5.1 General15 8.5.2 Successful Operation 16 8.5.3 Unsuccessful Operation 16 8.5.4 Abnormal Conditions17 8.6 Reset.17 8.6.1 General17 8.6.2 Successful Operation 17 8.6.3 Unsuccessful Operation 17 8.6.4 Abnormal Conditions18 8.7 Restart Ind
16、ication .18 8.7.1 General18 8.7.2 Successful Operation 18 8.7.3 Abnormal Conditions18 8.8 Failure Indication .18 8.8.1 General18 8.8.2 Successful Operation 19 8.8.3 Abnormal Conditions19 8.9 Error Indication 19 ETSI ETSI TS 125 419 V4.8.0 (2003-06) 4 3GPP TS 25.419 version 4.8.0 Release 4 8.9.1 Gene
17、ral19 8.9.2 Successful Operation 19 8.9.3 Abnormal Conditions20 9 Elements for SABP Communication20 9.1 Message Functional Definition and Content 20 9.1.1 General20 9.1.2 Message Contents .20 9.1.2.1 Presence 20 9.1.2.2 Criticality 20 9.1.2.3 Range 20 9.1.2.4 Assigned Criticality.21 9.1.3 WRITE-REPL
18、ACE.21 9.1.4 WRITE-REPLACE COMPLETE.21 9.1.5 WRITE-REPLACE FAILURE.21 9.1.6 KILL .22 9.1.7 KILL COMPLETE .22 9.1.8 KILL FAILURE .22 9.1.9 LOAD QUERY 22 9.1.10 LOAD QUERY COMPLETE.23 9.1.11 LOAD QUERY FAILURE.23 9.1.12 MESSAGE STATUS QUERY.23 9.1.13 MESSAGE STATUS QUERY COMPLETE .23 9.1.14 MESSAGE ST
19、ATUS QUERY FAILURE .24 9.1.15 RESET 24 9.1.16 RESET COMPLETE 24 9.1.17 RESET FAILURE 24 9.1.18 RESTART.25 9.1.19 FAILURE .25 9.1.20 ERROR INDICATION.25 9.2 Information Element Definitions25 9.2.0 General25 9.2.1 MessageType 26 9.2.2 Broadcast Message Content26 9.2.3 Serial Number.26 9.2.4 Old Serial
20、 Number26 9.2.5 New Serial Number 27 9.2.6 Service Areas List.27 9.2.7 Category27 9.2.8 Repetition Period 27 9.2.9 Number of Broadcasts Requested.27 9.2.10 Number of Broadcasts Completed List.28 9.2.11 Service Area Identifier29 9.2.12 Failure List29 9.2.13 Radio Resource Loading List29 9.2.14 Cause
21、30 9.2.15 Data Coding Scheme 32 9.2.16 Recovery Indication32 9.2.17 Criticality Diagnostics 32 9.2.18 Available Bandwidth 34 9.2.19 Message Identifier.34 9.2.20 Message Structure.34 9.3 Message and Information Element Abstract Syntax (with ASN.1)35 9.3.0 General35 9.3.1 Usage of protocol extension m
22、echanism for non-standard use.36 9.3.2 Elementary Procedure Definitions37 9.3.3 PDU Definitions .40 9.3.4 Information Element Definitions 50 9.3.5 Common Definitions.55 9.3.6 Constant Definitions .56 9.3.7 Container Definitions57 9.4 Message Transfer Syntax .60 ETSI ETSI TS 125 419 V4.8.0 (2003-06)
23、5 3GPP TS 25.419 version 4.8.0 Release 4 10 Handling of Unknown, Unforeseen or Erroneous Protocol Data.60 10.1 General .60 10.2 Transfer Syntax Error.60 10.3 Abstract Syntax Error.61 10.3.1 General61 10.3.2 Criticality Information 61 10.3.3 Presence Information 62 10.3.4 Not comprehended IE/IE group
24、62 10.3.4.1 Procedure Code.62 10.3.4.1A Type of Message .62 10.3.4.2 IEs other than the Procedure Code and Type of Message.62 10.3.5 Missing IE or IE group .63 10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 65 10.4 Logical Error 65 10.5 Exceptions
25、 66 Annex A (informative): Guidelines for Usage of the Criticality Diagnostics IE.67 A.1 EXAMPLE MESSAGE Layout .67 A.2 Example on a Received EXAMPLE MESSAGE.68 A.3 Content of Criticality Diagnostics69 A.3.1 Example 1.69 A.3.2 Example 2.70 A.3.3 Example 3.71 A.3.4 Example 4.72 A.3.5 Example 5.73 A.4
26、 ASN.1 of EXAMPLE MESSAGE .74 Annex B (informative): Change history .77 History 79 ETSI ETSI TS 125 419 V4.8.0 (2003-06) 6 3GPP TS 25.419 version 4.8.0 Release 4 Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present
27、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 wh
28、ere: 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
29、 incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 419 V4.8.0 (2003-06) 7 3GPP TS 25.419 version 4.8.0 Release 4 1 Scope The present document specifies the Service Area Broadcast Protocol (SABP) between the Cell Broadcast Centre (CBC) and the Radio Netw
30、ork Controller (RNC). It fulfils the CBC - RNC communication requirements specified in 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 either
31、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-s
32、pecific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 23.930: “Iu Principles“. 2 3GPP TS 25.410: “UTRAN Iu Interface; General Aspects and Principles“. 3 3GPP TS 25.401: “UTRAN Overall Description“. 4 3GPP TR 25.931: “UTRAN F
33、unctions: Examples on Signalling Procedures“. 5 3GPP TS 23.041: “Technical realization of Cell Broadcast Service (CBS)“. 6 3GPP TS 25.414: “UTRAN Iu Interface Data Transport and Transport Signalling“. 7 ITU-T Recommendation X.680 (12/1997): “Information Technology - Abstract Syntax Notation One (ASN
34、.1): Specification of basic notation“. 8 ITU-T Recommendation X.681 (12/1997): “Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification“. 9 ITU-T Recommendation X.691 (12/1997): “Information Technology - ASN.1 encoding rules - Specification of Packed Encoding
35、Rules (PER)“. 10 3GPP TR 25.921: “Guidelines and Principles for Protocol Description and Error Handling“. 11 3GPP 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 prese
36、nt document, the following terms and definitions apply: Elementary Procedure: SABP consists of Elementary Procedures (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 i
37、n a flexible manner. If the independence between some EPs is restricted, it is described under ETSI ETSI TS 125 419 V4.8.0 (2003-06) 8 3GPP TS 25.419 version 4.8.0 Release 4 the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other a
38、s stand alone procedures, which can be active in parallel. Examples on using several SABP EPs together with each other and EPs from other interfaces can be found in reference 4. An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: - Class 1: Elementary
39、Procedures with response (success 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. U
40、nsuccessful - A signalling message explicitly indicates that the EP failed. - On time supervision expiry (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,
41、 and SAI (Service Area Identifier). 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CBC Cell Broadcast Centre CBS Cell Broadcast Service CN Core Network EP Elementary Procedure FP Frame ProtocolPDU Protocol Data Unit RNC Radio Network Controller SA Serv
42、ice Area SABP Service Area Broadcast Protocol 4 General The protocol described in the present document is the protocol between CN (CBC) and RNC needed for the CBC Application. The CBC Application is described in 5. 4.1 Procedure Specification Principles The principle for specifying the procedure log
43、ic is to specify the functional behaviour of the RNC exactly and completely. The CN functional 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 exe
44、cuted: - The procedure text indicates that the receiving node “shall“ perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the ETSI ETSI TS 125 419 V4.8.0 (2003-06) 9 3GPP TS 25.419 version 4.8.0 Release 4
45、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 value. 2) Functionality which “shall, if supported“ be executed: - The procedure text indicates that the receiving node “shall, i
46、f 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 r
47、equired inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. 4.2 Forwards and Backwards Compatibility The
48、 forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regar
49、dless of the standard version. 4.3 Specification Notations For the purposes of the present document, the following notations apply: Procedure When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word “procedure“, e.g. Write-Replace procedure. Message When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word “message“, e.g. WRITE-REPLACE message.
