1、 ETSI TR 125 921 V7.0.0 (2007-06)Technical Report Universal Mobile Telecommunications System (UMTS);Guidelines and principles forprotocol description and error handling (3GPP TR 25.921 version 7.0.0 Release 7)ETSI ETSI TR 125 921 V7.0.0 (2007-06) 1 3GPP TR 25.921 version 7.0.0 Release 7 Reference RT
2、R/TSGR-0225921v700 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 cop
3、ies 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
4、(PDF). 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 stat
5、us 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, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced excep
6、t as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONT
7、Mand the TIPHON logo are Trade Marks currently being registered by ETSI 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 TR 125 921 V7.0.0 (2007-06) 2 3GPP TR 25.921 version 7.0.0 Release 7 Int
8、ellectual 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 Property Ri
9、ghts (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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including
10、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. Foreword This Technical Report (TR) has been produ
11、ced 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 bet
12、ween GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 125 921 V7.0.0 (2007-06) 3 3GPP TR 25.921 version 7.0.0 Release 7 Contents Intellectual Property Rights2 Foreword.2 Foreword.7 1 Scope 8 2 References 8 3 Void8 4 Principles to ensure com
13、patibility 9 4.1 Introduction 9 4.2 Level 1 of principles: Protocol level.9 4.3 Level 2 of principles: Message level 9 4.3.1 New messages.9 4.3.2 Partial decoding 9 4.4 Level 3 of principles: Information element level .9 4.4.1 New IE9 4.4.2 Void 9 4.4.3 Adding mandatory IE9 4.4.4 Absent optional IE
14、9 4.4.5 Comprehension required.10 4.4.6 Partial Decoding .10 4.5 Level 4 of principles: Values level.10 4.5.1 Spare values and spare fields 10 4.5.2 Unspecified values10 4.5.3 Void 10 4.5.4 Extension of value set .10 5 Message Sequence Charts 10 6 Specification and Description Language10 7 Protocol
15、procedure specification rules .11 7.1 General .11 7.1a Specification of algorithms and formulas.12 7.2 RRC specific rules12 7.3 RLC specific rules12 8 Message specification.13 8.1 Void13 8.2 Definitions13 8.3 Logical description.13 8.4 Message contents description.14 8.5 Compilability of the transfe
16、r syntax .14 8.6 Efficiency/Compactness.14 8.7 Evolvability/Extensibility.14 8.8 Inter IE dependency14 8.9 Intra IE dependency14 8.10 Support of error handling .14 9 Usage of tabular format14 9a Usage of Iub/Iur Frame Protocol14 9a.1 Extensions for future releases in Data and Control Frames14 9.1 Ta
17、bular description of messages and IEs in RRC 15 9.1.1 Message description15 9.1.1.1 The general description.16 9.1.1.2 The Information Element table .16 9.1.1.2.0 IE/Group Name column.16 ETSI ETSI TR 125 921 V7.0.0 (2007-06) 4 3GPP TR 25.921 version 7.0.0 Release 7 9.1.1.2.1 Need and multiplicity (M
18、ulti) columns .16 9.1.1.2.2 Type and reference column .19 9.1.1.2.3 Semantics description20 9.1.1.2.4 Expressing differences between FDD and TDD modes 20 9.1.1.2.5 Version column .20 9.1.1.3 Explanatory clauses.21 9.1.2 IE type description21 9.1.3 Extension for further releases .21 9.1.3.1 Basic pri
19、nciple.21 9.1.3.2 Critical or non-critical .21 9.1.3.3 Topics left unresolved.22 9.1a Tabular description of messages and IEs in RANAP, RNSAP, NBAP, PCAP, and SABP .22 9.1a.1 Message description22 9.1a.1.1 The Information Element table .22 9.1a.1.1.1 IE/Group Name column.23 9.1a.1.1.2 Presence and R
20、ange columns 23 9.1a.1.1.3 IE Type and reference column.25 9.1a.1.1.4 Semantics description column .25 9.1a.1.1.5 Expressing differences between FDD and TDD modes 25 9.1a.1.1.6 Criticality column25 9.1a.1.1.7 Assigned Criticality column 25 9.1a.1.2 Explanatory clauses.25 9.1a.2 IE type description25
21、 9.1a.3 Extension for further releases .26 9.1a.3.1 Basic principle.26 9.2 Basic types26 9.2.1 Enumerated.26 9.2.2 Boolean.26 9.2.3 Integer.27 9.2.4 Bit string .28 9.2.5 Octet string28 9.2.6 Real.28 10 Usage of ASN.129 10.1 Message level .29 10.2 Information element level.29 10.3 Component level 29
22、10.4 Extensions for future releases in RRC29 10.4.1 Basic principles.29 10.4.2 Naming convention.29 10.4.3 Recommendations for extensions for further releases in RRC .32 10.4.3.1 General32 10.4.3.2 Critical Extensions 33 10.4.3.3 Non-critical Extensions.33 10.4.3.4 Examples of non-critical extension
23、s35 10.4.3.4.1 Addition of a separate IE.35 10.4.3.4.2 Addition of an IE to a structured group .36 10.4.3.4.3 Addition of a new CHOICE group 36 10.4.3.4.4 Extension of value range .37 10.4.3.4.5 Replacement of a spare value with a new element 37 10.4.3.4.6 Introducing new System Information Block Ty
24、pes.38 10.4.3.5 Additional guidelines on the use of variable length extension containers.40 10.4.3.6 Use of non critical extensions for release independent features 41 10.5 Extensions for future releases in RANAP, RNSAP, NBAP; PCAP, and SABP 41 10.5.1 Allowed Extension41 10.5.2 Not Allowed Extension
25、.42 10.5.3 Recommendations for extensions for further releases 42 10.5.3.1 General42 10.5.3.2 Usage of Presence and Assigned Criticality in Future Releases .42 10.5.3.2.1 New Procedures.42 10.5.3.2.2 New IEs .43 10.5.3.2.3 Changing the Presence of an IE.43 ETSI ETSI TR 125 921 V7.0.0 (2007-06) 5 3GP
26、P TR 25.921 version 7.0.0 Release 7 10.5.3.2.4 Changing the Assigned Criticality of an IE.44 10.5.3.2.5 Removing IEs 44 10.5.4 Use of extensions44 10.6 Comments.45 11 Message transfer syntax specification46 11.1 Selection of transfer syntax specification method 46 11.2 Specialised encoding (only RRC
27、) 47 11.2.1 General47 11.2.2 Notation in ASN.1 47 11.2.3 Notation in ECN .47 11.2.3.1 Use of CSN.1 47 11.2.3.2 Reference to informally specified encodings in other specifications 48 11.2.4 Notation in Link Module 48 11.2.5 Detailed and Commented Examples.48 11.2.5.1 Example 1 .48 11.2.5.2 Example 2
28、.49 11.2.5.3 Example 3 .49 11.2.5.4 Example 4 .50 11.2.5.5 Example 5 .50 11.2.5.6 Example 6 .51 11.2.5.7 Example 7 .51 11.2.5.8 Example 8 .52 11.2.5.9 Example 9 .53 11.2.6 Complete Modules53 11.2.6.1 ASN.1 module.53 11.2.6.2 ECN module54 11.2.6.3 Link Module56 12 Guidelines involving different speci
29、fication parts .56 12.1 Correction of inconsistencies between tabular and ASN.1 in RRC56 12.1.1 Correcting the “need“ of an IE57 12.1.1.1 IE is optional in ASN.1 while it is correctly specified as mandatory in the tabular57 12.1.1.2 IE is mandatory in ASN.1 while it is correctly specified as optiona
30、l in tabular57 12.1.2 Removing an IE 57 12.1.2.1 IE is optional in ASN.1 while it should be absent.57 12.1.2.2 IE is optional in ASN.1 while the associated functionality should be removed from this release 57 Annex A: Usage of ASN.159 A.1 Message level .59 A.1.1 Messages.59 A.1.2 Message definition6
31、0 A.1.3 Messages and ASN.1 modules61 A.1.4 Messages and SDL62 A.2 Information element level.62 A.2.1 Message contents 63 A.2.2 Optional IEs and default values 63 A.2.3 New IEs 63 A.2.4 Comprehension required.63 A.2.5 Partial decoding 64 A.2.6 Error specification.64 A.3 Component level 64 A.3.1 Exten
32、sibility65 A.3.2 Comprehension required.65 A.3.3 Partial decoding 65 A.3.4 Boolean.65 A.3.5 Integer.65 A.3.6 Enumerated.66 A.3.7 Bit string .66 A.3.8 Octet string66 A.3.9 Null .67 A.3.10 Sequence.67 A.3.11 Sequence-of 68 ETSI ETSI TR 125 921 V7.0.0 (2007-06) 6 3GPP TR 25.921 version 7.0.0 Release 7
33、A.3.12 Choice.68 A.3.13 Restricted character string types .68 A.3.14 IEs and ASN.1 modules69 Annex B: Handling of DS-41.70 Annex C: Change history 71 History 72 ETSI ETSI TR 125 921 V7.0.0 (2007-06) 7 3GPP TR 25.921 version 7.0.0 Release 7 Foreword This Technical Report (TR) has been produced by the
34、 3rdGeneration 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 rele
35、ase 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.
36、technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 125 921 V7.0.0 (2007-06) 8 3GPP TR 25.921 version 7.0.0 Release 7 1 Scope The present document provides a guideline for protocol specif
37、ication of UMTS stage 2 and 3 including the usage of formal languages and rules for error handling. The present document covers control-plane and user-plane protocols specified in TSG-RAN such as RRC, RLC, RANAP, RNSAP, NBAP, PCAP, and SABP. 2 References The following documents contain provisions wh
38、ich, 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
39、 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 ITU-T Recommendation X.680: “Information technology - Abstract Syntax No
40、tation One (ASN.1): Specification of the basic notation“. 2 ITU-T Recommendation X.681: “Information technology - Abstract Syntax Notation One (ASN.1): Information object specification“. 3 ITU-T Recommendation X.682: “Information technology - Abstract Syntax Notation One (ASN.1): Constraint specific
41、ation“. 4 ITU-T Recommendation X.690: “Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)“. 5 ITU-T Recommendation X.691: “Information technology - ASN.1 encoding rules: Specification of Pa
42、cked Encoding Rules (PER)“. 6 CSN.1: “specification, version 2.0“. 7 ITU-T Recommendation Z.100: “Specification and description language (SDL)“. 8 ITU-T Recommendation Z.105: “SDL Combined with ASN.1 modules (SDL/ASN.1)“. 9 ITU-T Recommendation Z.120: “Message Sequence Chart (MSC)“. 10 ISO/IEC 9646-
43、3: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)“. 11 3GPP TR 21.801: “Specification drafting rules“. 12 ETSI EG 202 106 (DEG/MTS-00050): “Methods for Testing and Specification (MTS); Gui
44、delines for the use of formal SDL as a descriptive tool“. 13 3GPP TS 24.008: “Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3“. 3 Void ETSI ETSI TR 125 921 V7.0.0 (2007-06) 9 3GPP TR 25.921 version 7.0.0 Release 7 4 Principles to ensure compatibility 4.1 Introduction Th
45、e rules intend to prevent incompatibilities between several phases of UMTS evolution (in analogy to what happened from GSM phase 1 to GSM phase 2). 4.2 Level 1 of principles: Protocol level It shall be possible to inter-work different versions of any protocol specification. An unknown protocol shall
46、 not cause problems to any entity that terminates the protocol. As a consequence, introduction of new protocol shall not disturb any receiving entity. 4.3 Level 2 of principles: Message level 4.3.1 New messages The protocols shall specify a mechanism such that new message types shall be able to be i
47、ntroduced without causing any unexpected behaviour or damage. The protocols may define a mechanism that allows a different behaviour, on received messages that are not understood, when a specific reaction is requested from the receiving entity. This mechanism has to be implemented from the beginning
48、. A special care has to be taken into account when defining broadcast messages and the associated Error handling. Further refinement on this paragraph is needed. 4.3.2 Partial decoding PDU extensions are allowed in a compatible way, e.g. by utilising partial decoding or other mechanisms that allows
49、the decoder to skip the extensions. Partial decoding means that a PDU can be decoded in parts. One part forms a complete value that can be separated from other parts. 4.4 Level 3 of principles: Information element level 4.4.1 New IE New elements shall generally be discarded when not understood. In some cases new elements might be taken into account when specific behaviour is requested from the receiving side (e.g. a rejection of the message is expected when the element is not understood: “comprehension required“). 4.4.2 Void 4.4.3 Adding mandator
