ECMA 143-2001 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (4th Edition)《专用综合业务网络(PISN) 电路模式承载业务 局间.pdf

《ECMA 143-2001 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (4th Edition)《专用综合业务网络(PISN) 电路模式承载业务 局间.pdf》由会员分享，可在线阅读，更多相关《ECMA 143-2001 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (4th Edition)《专用综合业务网络(PISN) 电路模式承载业务 局间.pdf（168页珍藏版）》请在麦多课文档分享上搜索。

1、 Standard ECMA-143 4th Edition - December 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch -

2、Internet: helpdeskecma.ch . Standard ECMA-143 4th Edition - December 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (QSIG-BC) Phone: +41 22 849.60.00 - Fax: +41 22

3、849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.ch IW Ecma-143.doc 14-01-02 13,52 . Brief History This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private Integrated Services Networks (PISNs). The series uses ISDN concepts as dev

4、eloped by ITU-T and conforms to the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. This particular Standard defines the signalling protocol for use at the Q-reference point in support of bearer circuit-switched services. The protocol defined in this Stan

5、dard forms part of the PSS1 protocol (informally known as QSIG). This Standard is based upon the practical experience of ECMA member companies and the results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardization bo

6、dies. It represents a pragmatic and widely based consensus. Compared to the 2nd Edition of Standard ECMA-143 (published by ECMA in December 1992), the 3rd Edition had been extended to include support for Multi-rate and changes had been incorporated in order to achieve complete alignment with Interna

7、tional Standard ISO/IEC 11572:1996(E) published by ISO/IEC in December 1996, including amendment 1 and 2, and defect report 001. Compared to the 3rd Edition of Standard ECMA-143 (published by ECMA in June 1997), this 4th Edition is completely aligned with International Standard ISO/IEC 11572:2000(E)

8、 and corrigendum 001. Adopted as 4th Edition of Standard ECMA-143 by the General Assembly of December 2001. . - i - Table of contents 1 Scope 1 2 Conformance 1 3 References (normative) 1 4 Definitions 1 4.1 Private Integrated Services Network (PISN) 1 4.2 Private Integrated services Network eXchange

9、 (PINX) 2 4.3 Side, Incoming Side and Outgoing Side 2 4.4 Outgoing Call and Incoming Call 2 4.5 Originating PINX, Terminating PINX and Transit PINX 2 4.6 Gateway PINX, Incoming Gateway PINX and Outgoing Gateway PINX 2 4.7 Preceding PINX and Subsequent PINX 3 4.8 Inter-PINX link 3 4.9 Route 3 4.10 Si

10、gnalling Carriage Mechanism (SCM) 3 4.11 Unrecognised message 3 4.12 Unexpected message 3 4.13 Unrecognised information element 3 4.14 Information elements with invalid contents 3 5 List of acronyms 4 6 General principles 4 6.1 Protocol model 4 6.2 Services provided to Call Control 5 6.3 Services re

11、quired of the Signalling Carriage Mechanism 6 7 Protocol Control states 6 7.1 States for circuit-mode Call Control 6 7.1.1 Null State (0) 6 7.1.2 Call Initiated (1) 6 7.1.3 Overlap Sending (2) 6 7.1.4 Outgoing Call Proceeding (3) 6 7.1.5 Call Delivered (4) 6 7.1.6 Call Present (6) 6 7.1.7 Call Recei

12、ved (7) 6 7.1.8 Connect Request (8) 7 7.1.9 Incoming Call Proceeding (9) 7 7.1.10 Active (10) 7 7.1.11 Disconnect Request (11) 7 7.1.12 Disconnect Indication (12) 7 7.1.13 Release Request (19) 7 - ii - 7.1.14 Overlap Receiving (25) 7 7.2 States for layer management 7 7.2.1 Null State (Rest 0) 7 7.2.

13、2 Restart Request (Rest 1) 7 7.2.3 Restart (Rest 2) 7 8 Call Control 7 8.1 States for Transit PINX Call Control 8 8.1.1 TCC_Idle (0) 8 8.1.2 TCC_Await Digits (1) 8 8.1.3 TCC_Await Additional Digits (2) 8 8.1.4 TCC_Overlap (3) 8 8.1.5 TCC_Incoming Call Proceeding (4) 8 8.1.6 TCC_Transit Call Proceedi

14、ng (5) 8 8.1.7 TCC_Call Alerting (6) 8 8.1.8 TCC_Call Active (7) 8 8.1.9 TCC_Await Incoming Release (8) 9 8.1.10 TCC_Await Outgoing Release (9) 9 8.1.11 TCC_Await Two-Way Release (10) 9 8.1.12 TCC_Await Incoming Disconnect (11) 9 8.1.13 TCC_Await Outgoing Disconnect (12) 9 8.1.14 TCC_Await Two-Way D

15、isconnect (13) 9 9 General procedures 9 9.1 Use of the services of Signalling Carriage Mechanism 9 9.1.1 Establishment of a Signalling Carriage Mechanism connection 9 9.1.2 Transfer of data 9 9.1.3 Signalling Carriage Mechanism reset 9 9.1.4 Signalling Carriage Mechanism failure 9 9.2 Handling of pr

16、otocol error conditions 10 9.2.1 Protocol discriminator error 10 9.2.2 Message too short 10 9.2.3 Call reference error 10 9.2.4 Message type or message sequence errors 10 9.2.5 General information element errors 11 9.2.6 Mandatory information element errors 11 9.2.7 Non-mandatory information element

17、 errors 12 9.2.8 Signalling Carriage Mechanism reset 13 9.2.9 Signalling Carriage Mechanism failure 13 9.3 Status and status enquiry protocol procedures 14 9.3.1 Status enquiry procedure 14 9.3.2 Receiving a STATUS message 14 10 Circuit-switched Call Control procedures 16 10.1 Call establishment 17

18、10.1.1 Call request 17 10.1.2 Information channel selection 17 - iii - 10.1.3 Overlap sending 18 10.1.4 Call proceeding 18 10.1.5 Call confirmation indication 19 10.1.6 Call connected 20 10.1.7 Use of the PROGRESS message 20 10.1.8 Failure of call establishment 21 10.2 Call clearing 21 10.2.1 Termin

19、ology 21 10.2.2 Exception conditions 21 10.2.3 Clearing 22 10.2.4 Clear collision 22 10.3 Call collisions 22 10.4 Transit PINX Call Control requirements 23 10.4.1 Receipt of address information 23 10.4.2 State TCC_Await_Digits 24 10.4.3 State TCC_Await_Additional_Digits 24 10.4.4 State TCC_Overlap 2

20、5 10.4.5 Channel through connection procedures 26 10.4.6 State TCC_Incoming_Call_Proceeding 26 10.4.7 State TCC_Transit_Call_Proceeding 27 10.4.8 State TCC_Call_Alerting 28 10.4.9 State TCC_Call_Active 28 10.4.10 Call clearing at a Transit PINX 29 10.4.11 Handling of Basic Call information elements

21、at a Transit PINX 30 10.5 Originating PINX Call Control requirements 30 10.5.1 Transmission of the SETUP message 31 10.5.2 Agreement of the information channel 31 10.5.3 Receipt of Progress indicators 31 10.5.4 Receipt of ALERTING message 31 10.5.5 Receipt of CONNECT message 32 10.5.6 Call clearing

22、initiated by the Originating PINX 32 10.5.7 Receipt of an indication of call clearing 32 10.6 Terminating PINX Call Control requirements 32 10.6.1 Receipt of the SETUP message 32 10.6.2 Transmission of ALERTING message 33 10.6.3 Transmission of Progress indicators 33 10.6.4 Transmission of CONNECT m

23、essage 33 10.6.5 Call clearing initiated by the Terminating PINX 33 10.6.6 Receipt of an indication of call clearing 34 10.7 Incoming Gateway PINX Call Control requirements 34 10.7.1 Transmission of the SETUP message 34 10.7.2 Interworking indications in the SETUP Message 35 10.7.3 Agreement of the

24、information channel 35 10.7.4 Receipt of Progress indicators 35 10.7.5 Receipt of ALERTING message 35 10.7.6 Receipt of CONNECT message 36 - iv - 10.7.7 Call clearing initiated by the Incoming Gateway PINX 36 10.7.8 Receipt of an indication of call clearing 36 10.8 Outgoing Gateway PINX Call Control

25、 requirements 37 10.8.1 Receipt of the SETUP message 37 10.8.2 Connection of the information channel 37 10.8.3 Transmission of interworking indications 37 10.8.4 Transmission of ALERTING message 38 10.8.5 Transmission of CONNECT message 38 10.8.6 Call clearing initiated by the Outgoing Gateway PINX

26、39 10.8.7 Receipt of an indication of call clearing 39 11 Procedures for layer management 39 11.1 Restart procedures 39 11.1.1 Sending RESTART 39 11.1.2 Receipt of RESTART 40 11.1.3 Restart collision 40 12 Protocol timers 40 13 Functional definition of messages 43 13.1 Messages for general procedure

27、s 43 13.1.1 STATUS 43 13.1.2 STATUS ENQUIRY 43 13.2 Messages for Circuit Mode Call Control 44 13.2.1 ALERTING 44 13.2.2 CALL PROCEEDING 44 13.2.3 CONNECT 44 13.2.4 CONNECT ACKNOWLEDGE 45 13.2.5 DISCONNECT 45 13.2.6 INFORMATION 45 13.2.7 PROGRESS 45 13.2.8 RELEASE 46 13.2.9 RELEASE COMPLETE 46 13.2.1

28、0 SETUP 46 13.2.11 SETUP ACKNOWLEDGE 47 13.3 Messages for layer management 47 13.3.1 RESTART 47 13.3.2 RESTART ACKNOWLEDGE 47 14 General message format and coding of information elements 48 14.1 Overview 48 14.2 Protocol discriminator 48 14.3 Call reference 49 14.4 Message type 50 14.5 Other informa

29、tion elements for Basic Call control (codeset 0) 51 14.5.1 Coding rules 51 14.5.2 Extension of codesets 53 - v - 14.5.3 Locking shift procedure 54 14.5.4 Non-locking shift procedure 55 14.5.5 Bearer capability 55 14.5.6 Call state 57 14.5.7 Called party number 58 14.5.8 Called party subaddress 61 14

30、.5.9 Calling party number 61 14.5.10 Calling party subaddress 62 14.5.11 Cause 62 14.5.12 Channel identification 67 14.5.13 Connected number 70 14.5.14 Connected subaddress 70 14.5.15 High layer compatibility (layers 4-7) 71 14.5.16 Low layer compatibility (layers 1-3) 71 14.5.17 Progress indicator

31、71 14.5.18 Restart indicator 72 14.5.19 Sending complete 73 14.6 Information elements of codeset 5 73 Annex A - Protocol Implementation Conformance Statement (PICS) for ECMA-143 75 Annex B - Use of the cause information element 87 Annex C - Examples of message sequences 91 Annex D - Manufacturer spe

32、cific information 95 Annex E - SDL diagram for the procedures over a symmetrical link between two peer PINXs 97 Annex F - SDL diagram for the procedures on either side of a Transit-PINX 119 Annex G - Bibliography 137 Annex ZA - Segmentation and reassembly procedures 139 Annex ZB - Additional progres

33、s descriptions 149 - vi - . 1 Scope This Standard defines the signalling procedures and protocol for the purpose of circuit-switched Call Control at the Q-reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PI

34、SN). The Q reference point is defined in ECMA-133. This Standard is based upon that described in ITU-T Recommendation Q.931, including the provisions for symmetrical operation described in annex D of that recommendation. Service specifications are produced in three stages and according to the method

35、 specified in ETS 300 387. This Standard contains the stage 3 specification for the Q reference point and satisfies the requirements identified by the stage 1 and stage 2 specifications in ECMA-142, ECMA-148 and ISO/IEC 11584. This Standard is applicable to PINXs which interconnect to form a PISN. 2

36、 Conformance In order to conform to this Standard, a PINX shall satisfy the requirements identified in the Protocol Implementation Conformance Statement (PICS) proforma in annex A. 3 References (normative) The following standards contain provisions which, through reference in this text, constitute p

37、rovisions of this Standard. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. In the case of references to ECMA Standards that are aligned with I

38、SO/IEC International Standards, the number of the appropriate ISO/IEC International Standard is given in brackets after the ECMA reference. ECMA-133 Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1) ECMA-155 Privat

39、e Integrated Services Networks - Addressing (International Standard ISO/IEC 11571) ISO/IEC 8886 Information technology - Open Systems Interconnection - Data link service definition (1996) ETS 300 387 Private Telecommunication Network (PTN); Method for the specification of basic and supplementary ser

40、vices (1994) ITU-T Rec. E.164 The international public telecommunication numbering plan (1997) ITU-T Rec. I.330 ISDN numbering and addressing principles (Blue Book) (1988) ITU-T Rec. Q.931 ISDN user-network interface layer 3 specification for basic call control (1998) ITU-T Rec. T.50 Information tec

41、hnology - 7-bit coded character set for information interchange (1992) 4 Definitions For the purposes of this Standard, the following definitions apply. 4.1 Private Integrated Services Network (PISN) An ISDN providing services to a specific set of users (contrary to a public ISDN which provides serv

42、ices to the general public). NOTE This definition does not include legal and regulatory aspects and does not indicate any aspects of ownership. - 2 - 4.2 Private Integrated services Network eXchange (PINX) A PISN nodal entity which provides automatic connection handling functions used for the provis

43、ion of telecommunication services based on the definitions of the public ISDN services. A PISN nodal entity consists of one or more nodes. 4.3 Side, Incoming Side and Outgoing Side The term Side is used to describe either of the two PINXs at each end of an Inter-PINX link, and in particular to descr

44、ibe the PSS1 Protocol entity within a PINX. In the context of a call, the Outgoing Side is the Side which routes the call over the Inter-PINX link and the Incoming Side is the Side which receives the call. See figure 1. 4.4 Outgoing Call and Incoming Call From the point of view of the Outgoing Side

45、a call is an Outgoing Call. From the point of view of the Incoming Side a call is an Incoming Call. 4.5 Originating PINX, Terminating PINX and Transit PINX Within the context of a call, the PINX to which the calling user is attached is known as the Originating PINX. Within the context of a call, the

46、 PINX to which the called user is attached is known as the Terminating PINX. Within the context of a call, any PINX through which the call passes, excluding the Originating PINX the Terminating PINX, an Incoming gateway PINX and an Outgoing gateway PINX, is known as a Transit PINX. See figure 1. 4.6

47、 Gateway PINX, Incoming Gateway PINX and Outgoing Gateway PINX Within the context of a call, a PINX which performs interworking between PSS1 and another signalling system, either ISDN or non-ISDN, is known as a Gateway PINX. A Gateway PINX which routes an incoming call from a route employing another

48、 signalling system on to an Inter-PINX link employing PSS1 signalling is known as an Incoming Gateway PINX. A Gateway PINX which routes an incoming call from an Inter-PINX link employing PSS1 signalling on to a route employing another signalling system is known as an Outgoing Gateway PINX. See figur

49、e 1. Forwards directionOriginating PINXor IncomingGateway PINXTransit PINXTerminating PINXor OutgoingGateway PINXInter-PINX link Inter-PINX linkOutgoingsideIncomingsideIncomingsideOutgoingsideBackwards directionFigure 1 - Illustration of terminology through example of a call routed over two Inter-PINX links employing PSS1 - 3 - 4.7 Preceding PINX and Subsequent PINX Within the context of a call, from the point of view of a PINX acting as the Incoming Side of an Inter-PINX link, the PINX at the other end of the link, acting as the Outgoing Side, is known as the Preceding PINX. Within the