1、INTERNATIONAL TELECOMMUNICATION UN ION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.2630.1 Annex B (032001) SERIES Q: SWITCHING AND SIGNALLING Broadband ISDN - Common aspects of B-ISDN application protocols for access signalling and network signalling and interworking AAL type 2 signallin
2、g protocol - Capability set 1 Annex. B: SDL definition of the AAL type 2 signalling protocol CS-1 ITU-T Recommendation Q.2630.1 - Annex B (Formerly CCIT Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND
3、SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE! ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKLNG OF SIGNALLING S
4、YSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 43 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 SPECIFICA
5、TIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) BROADBAND ISDN General aspects Signalling ATM adaptation layer (SAAL) Signalling network protocols Common aspects of B-ISDN application protocols for access signalling and network B-ISDN application protocols for the network signa
6、lling B-ISDN application protocols for access signalling signalling and interworking _ - Q.l-Q.3 4.4-4.59 4.60-4.99 Q.lO0-Q.119 Q. 120-Q.249 4.250-4.309 4.310-4.399 4.400-4.499 Q.50O-Q.599 Q.600-Q.699 Q.700-Q.799 Q.80O-Q.849 Q.850-Q.999 Q. 1000-Q. 1099 Q. 1 100-Q. 1 199 Q. 12004.1699 Q.1700-Q.1799 Q
7、. 1900-Q. 1999 Q.2000-Q.2999 Q.2000-Q.2099 Q.2 100-Q.2199 Q.2200-Q.2299 Q.2600-Q.2699 Q.2700-Q.2899 4.2900-4.2999 For further details, please refer to the list of ITU-T Recommendations. - ITU-T Recommendation Q.2630.1 AAL type 2 signalling protocol - Capability set 1 ANNEX B SDL definition of the AA
8、L type 2 signalling protocol CS-1 Summary This annex contains the SDL definition of AAL Type 2 Signalling Protocol CS-1 for ITU-T Recommendation Q.2630.1. SDL diagrams are in electronic form only. Source Annex B to ITU-T Recommendation Q.2630.1 was prepared by ITU-T Study Group 11 (2001-2004) and ap
9、proved under the WTSA Resolution 1 procedure on 1 March 2001. ITU-T Q.2630.1IAnnex B (03/2001) i FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permane
10、nt organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishe
11、s the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standard
12、s are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility th
13、at the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommenda
14、tion development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and
15、are therefore strongly urged to consult the TSB patent database. o mu 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. 11 ITU-T Q.26
16、30.l/Annex B (03/2001) CONTENTS B . 1 Introduction . B.2 The SDL system diagram . B.3 The SDL block structure diagram . B.4 SDL specification for the nodal function . B.4.1 Introduction . B.4.2 SDL diagrams for the Nodal Function 1 . B.4.3 Procedures in the nodal function B.4.4 SDL diagrams for the
17、protocol entities B.5.1 Introduction . B.5.2 SDL diagrams for the outgoing, incoming, and maintenance protocol procedures . Data structures of AAL type 2 signalling messages and parameters . B.5 ITU-T Q.2630.1/Annex B (03/2001) Page 1 1 1 7 7 7 14 15 44 44 44 . 111 ITU-T Recommendation Q.2630.1 AAL
18、type 2 signalling protocol - Capability set 1 ANNEX B SDL definition of the AAL type 2 signalling protocol CS-1 The SDL definitions may contain more detail than the prose definition in clause 8. Nevertheless, should there exist any technical difference between this annex and clause 8, then the defin
19、itions in clause 8 take precedence. B.1 Introduction The SDL definitions of the AAL type 2 signalling protocol described in this Recommendation depend on the SDL system and block structure diagrams defined in this annex. The SDL definition in this annex assumes that only a single event occurs at a g
20、iven time, hence, no racing condition within the AAL type 2 signalling entity are considered; resolution of such collisions and racing conditions remains implementation dependent. B.2 The SDL system diagram The SDL system diagram is depicted in Figure B. 1. B.3 The SDL block structure diagrams are d
21、epicted in Figure B.2 (parts 1 to 4 of 4). NOTE 1 - The block USER and its process USER (not shown) are not part of the AAL type 2 signalling entity but used to indicate different served user entities. NOTE 2 - The procedures located in process NodalF2 and called by the process NodalFl are not elabo
22、rated further in this annex. NOTE 3 - The procedure calls by the process NodalFl to procedures located in process NodaiF2 evoke an exchange of implicit signals between the processes NodalFl and NodalF2. NOTE 4 - One STI entity exists per signalling transport converter. These converters are known by
23、Nodal Function 2 with their (SDL) ProcessID. The addition or removal of signalling relations together with the creation or destruction of the STI and STC processes is not shown in these SDL diagrams of this annex. The SDL block structure diagram ITU-T Q.2630.l/Annex B (03/2001) 1 Block AAL20 aa120b0
24、(1) Stimuli k: 4 Tne boi nallist IPPdown := ( YPP-ESTABLISH.response, IPP-REJECT.request XPP-RELEASE.requect, XPP-RELEASE.responce. XPP-CONFUSE.re uest. XPP-UNRECOGNIED.requect, TERM INATE.request) YPP-ESTABLISH.indicaiion. XPP-RELEASEhdication, XPP-RELEASE.cunlirm. XPP-TIMEOUT.indication. XPP-CONFU
25、SE.indication, XPP-UNRECOGNI2ED.indication. XPP-ERRORhdication) ;i nallist IPPup := ( Figure B.2/Q.2630.1- SDL block structure of the AAL type 2 signalling entity (part 2 of4 4 ITU-T Q.2630.1/Annex B (03/2001) Block NodalFu= NodalF1 1 :I A2S NodalFP 1 :1 i/ , ;(IPPdown. OPPdown, MPPdown) 1 ESTABLISH
26、.indica1ion RELEASE.indication RELEASE.conirm ESTABLISH.mnfirm ESTABLISH.request -RELEASE.request Note 1 The proceoures located in process hoOalF2 ano ca .ed oy tne orocess hWalF1 are not elaborated I further in this Annex Note 2: These procedure calls evoke an exchange of implicit signals between t
27、he orocesses NodalF1 and NodalFP: LMO I (IPPup. OPPup. MPPup) LM 1 PP 1 EiDD-PATH.indication REMOVE-PATH.indication PEF 1 STI-IN SERVICE indcation STI.OLiT.OF SERV CE inacation STI-CONGESTION indica1 on STI UNRECOGNIZED inocalion Figure B.21Q.2630.1- SDL block structure of the AAL type 2 signalling
28、entity (part 3 of4 ITU-T Q.2630.1/Annex B (03/2001) 5 Block ProtEnt / LMM ERROR.indication IPP I A (STlup) A2MPPO O: n (STlup) OPP MPP (OPPdown) (STIUP) I LMO A20PPO aa120b3( 1) (MPPdown) STbIN SERVICE indication STI.ObT OF SERVICE ndicatior STI-CONGEST ON inaicat on STI.LNRECOGNIZED indication L PE
29、R IrrAl urrn Mrrh pldown) -1 Pl A2STIO n:n STI 1 TRANSFER.indication IN-SERVICE.indication OUT-OF-SERVICE.indication CONGESTION.indication -TRANSFER.request ignaiiist STldown := ( ERQrequest, ECF.request, REL.request. RLC.requect. RES.request. RSC.request. BLO.requect. BLC.request, UBL.request, UBC.
30、requen, CFN.request UNRECOGNIZED.request) gnallict STlup := ( ERQhdication, ECFhdication. RELmdicalion. RLChdication. REShdication. RSC.indication. BLOhdication. BLChdication, Figure B.21Q.2630.1- SDL block structure of the AAL type 2 signalling entity (part 4 of4) 6 ITU-T Q.2630.UAnnex B (03/2001)
31、B.4 SDL specification for the nodal function Connection established Release Pending B.4.1 Introduction 4 preceeding link succeeding link 5 succeeding link preceeding link 6 preceeding link succeeding link 7 succeeding link preceeding link In Figure B.2 (part 3 of 4) it is shown that the nodal functi
32、on is separated into: 4 Nodal Function 1 This entity contains all functionality that is defined in detail in 8.2 and, therefore, can be specified precisely in SDL diagrams. This entity contains all functionality that contains implementation specific parts, only results are defined in detail in 8.2 (
33、but not their internal mechanisms). These parts are not defined in detail in this Annex either; only the expected result is documented. Therefore, this clause defines the Nodal Function 1 (see B.4.2) and the procedures of the Nodal Function 2 (see B.4.3). The latter by their nature are not specified
34、 in SDL; nevertheless, the functionality expected from these procedures needs to be understood to complete the definition of the SDL diagrams for the AAL type 2 signalling entity. The USER, i.e. the AAL type 2 served user, processes are not defined either, nor the interaction of these processes with
35、 the environment (e.g., for simulation stimuli). It is assumed that for every AAL type 2 connection a separate USER process exists (at both ends of the connection) and that its (SDL process) identity is used to route the signals. NOTE - The processes of the protocol entities are described in 8.3. b)
36、 Nodal Function 2 B.4.2 SDL diagrams for the Nodal Function 1 B.4.2.1 Data structures For the SDL model, the AAL type 2 signalling entity maintains a record of type “CRec“ for every AAL type 2 connection from the instance in time where the connection is being established until it is released. The te
37、rms “preceeding“ and “succeeding“ in the following discussion relate to the direction of the connection establishment. When such a record is looked up (with the protocol procedure entity instances identifier), the record is organized such that the “incoming“ part refers to the link from where a mess
38、age has been received; this is reflected in the status value as described in Table B. 1. Table B.UQ.2630.1- Status values for CRec records Description I Status Value I Incoming part describes I Outgoing part describes Establishment Pending I 2 I preceeding link I succeeding link I 3 I succeeding lin
39、k I preceeding link ITU-T Q.2630.1/Annex B (03/2001) 7 The structure of the record of type “CRec“ is defined in the ASN.l fragment below: IPP-ESTABLISH IPP-RE JECT OPP-ESTABLISH OPP-REJECT XPP-RELEASE XPP-TIMEOUT CRec := SEQUENCE status CRecStatus, - connection status incoming mec, - details incomin
40、g link out going mec - details outgoing link HRec := SEQUENCE peer ENUMERATED user, remote, none, PPU s PID, - ID of protocol entity or user srid PID, - signalling relation identifier ceid CEID - connect ion el emen t i dent i fi er - is ID of signalling relation Not defined ERQmsg, sri ECFmsg Not d
41、efined RLCmsg Not defined Not defined Not defined ERQmsg Not defined Not defined ECFmsg Not defined RLCmsg Not defined Not defined RELmsg RELmsg RLCmsg RLCmsg Not defined - Not defined Not defined For the SDL model, the AAL type 2 signalling entity maintains a record of type “MRec“ for every outgoin
42、g maintenance action from the instance in time where the maintenance action is being started until it is concluded. The structure of the mec is defined in the ASN. 1 fragment below: XPP- UNRECOGNIZED MPP-BLOCK MPP-UNBLOCK MPP-RESET MPP-ERROR TERMINATE mec := SEQUENCE status MRecStatus, - maintenance
43、 action status PPUS PID, - ID of protocol entity srid PID, - signalling relation identifier - is ID of signalling transport entity ceid CEID, - connect ion el emen t i den ti fi er disp BOOLEAN - TRUE: originator is layer management B.4.2.2 Primitives between Nodal Function 1 and the Protocol Entiti
44、es msg msg Not defined Not defined BLOmsg, sqc BLOmsg, sri BLCmsg BLCmsg UBLmsg UBLmsg, sri UBCmsg UBCmsg RESmsg RESmsg, sri RSCmsg, sqc RSCmsg Not defined cause Not defined Not defined - Not defined Not defined Not defined The interface to the AAL type 2 served user is defined in 5.1. The interface
45、 to layer management is defined in 5.3. The interface between the AAL type 2 signalling entity and the AAL type 2 protocol entities are summarized in Table B.2 and are defined after the table. Table B.2/Q.2630.1- Primitives and parameters exchanged between the Nodal Function 1 entity and the Protoco
46、l Entities I XPP-CONFUSE I CNFmsg I CNFmsg I Notdefined I Notdefined I - This primitive has no parameters 8 ITU-T Q.2630.UAnnex B (03/2001) a) IPP-ESTABLISH A newly created incoming protocol entity indicates the establish request (ERQ) message to Nodal Function 1 (with the indication primitive) toge
47、ther with the nodal signalling association identifier “sri“. If the establishment terminates with a served user at this node or if the AAL type 2 nodes beyond the succeeding link acknowledged the establishment, the establish confirm (ECF) message is conveyed to the incoming protocol entity (with the
48、 response primitive) for transmission on the preceeding link. If the establishment can not be completed at this AAL type 2 node or at any AAL type 2 node beyond the succeeding link, the establishment is rejected with a release confirm (RLC) message that is conveyed to the incoming protocol entity (w
49、ith the request primitive) for transmission on the preceeding link. If an establishment is to be continued on a succeeding link the establish request (ERQ) message is conveyed to the newly created outgoing protocol entity (with the request primitive). If the establish confirm (ECF) message is received by this outgoing protocol entity, it is communicated to Nodal Function 1 (with the confirm primitive). If the AAL type 2 nodes beyond the succeeding link cannot accept the establishment, the outgoing protocol entity receives a rel
