ECMA 165-2001 Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol.pdf

《ECMA 165-2001 Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol.pdf》由会员分享，可在线阅读，更多相关《ECMA 165-2001 Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol.pdf（146页珍藏版）》请在麦多课文档分享上搜索。

1、 Standard ECMA-165 4th Edition - June 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol Phone: +41 22 849.60.00 - Fax: +41 22

2、849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.ch . Standard ECMA-165 4th Edition - June 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signallin

3、g Procedures and Protocol (QSIG-GF) Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.ch IW ECMA-165.DOC 04-09-02 09,49 . Brief History This Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private

4、Integrated Services Digital Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to the framework of International Standards on Open Systems Interconnection as defined by ISO/IEC. It has been produced under ITSTC work items M-IT-05 5.1.3 and M-IT-05 5.1.2.2 and under ET

5、SI work items DE/ECMA-00045 and RE/ECMA-00118. This particular Standard defines the signalling protocol for use at the Q reference point between two PINXs for the transport of protocol information as part of Supplementary Services and/or Additional Network Features (ANFs) within a PISN. The protocol

6、 defined in this Standard forms part of the PSS1 protocol (informally known as QSIG). The generic functional procedures provide a flexible and open ended approach to the provision of supplementary service and ANF protocols. These procedures provide: generic protocols which may be utilised in the pro

7、vision of supplementary services and ANFs, both related to existing calls and separate from existing calls where appropriate to the capability required; a dialogue identification protocol to enable supplementary service or ANF information flows to be tied together to form a dialogue; supplementary s

8、ervice and ANF transparency across a PISN, whereby transit PINXs need have no knowledge of the capability provided to the PISN user or PISN itself unless involved in the provision of that capability; and the capability for standardised and manufacturer specific capabilities to coexist in both single

9、 and multi-vendor PISNs. The protocol defined in this Standard is based upon that described in ITU-T Recommendation Q.932 (1993). 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, IT

10、U-T, ETSI and other international and national standardization bodies. It represents a pragmatic and widely based consensus. Compared to the3rdEdition of Standard ECMA-165 (published by ECMA in June 1997), this 4thEdition incorporates changes in order to achieve complete alignment with International

11、 Standard ISO/IEC 11582:1995(E) published by ISO/IEC in July 1995, including Technical Corrigendum 1 (1995), Defect Report 1 (2000) and additional changes as listed in annex L. Adopted as 4th Edition of Standard ECMA-165 by the General Assembly of June 2001. . List of corrected errata for ECMA-165 1

12、0 July 2002 Summary Following is a summary of errors detected and corrected in Standard ECMA-165, Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol. Clause 11.3.3.5, table 35 In the m

13、odule Association-Control-Apdus-asn1-97, the Object Identifier of the ACSE-1 module is wrong. Original IMPORTS ACSE-apdu FROM ACSE-1 joint-iso-itu-t association-control( 2) abstract-syntax( 1) apdus( 0) version( 1) ; Corrected IMPORTS ACSE-apdu FROM ACSE-1 joint-iso-itu-t association-control(2) modu

14、les(0) apdus(0) version1( 1) ; Clause F.2, table F.3 Some of the Object Identifiers defined in the different Hypothetical-service-operation-asn1-97 modules are not well defined. Original Hypothetical-service-operation-asn1-97 iso identified-organization icd-ecma member-company hypothetical-manufactu

15、rer hypothetical-service-offering-asn1-97 Corrected Hypothetical-service-operation-asn1-97 iso( 1) identified-organization( 3) icd-ecma( 12) member-company( 2) hypothetical-manufacturer( 1999) hypothetical-service-offering-asn1-97 ( 9999) Original IMPORTS OPERATION FROM Remote-Operations-Information

16、-Objects joint-iso-ccitt( 2) remote-operations( 4) notation( 0) ; Corrected IMPORTS OPERATION FROM Remote-Operations-Information-Objects joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0) ; Original CODE global: iso( 1) identified-organization( 3) icd-ecma( 0012) member-company(

17、2) hypothetical-manufacturer( 1999) hypothetical-manufacturer-service( 1) Corrected CODE global: iso( 1) identified-organization( 3) icd-ecma( 12) member-company( 2) hypothetical-manufacturer( 1999) hypothetical-manufacturer-service( 1) Clause F.2, table F.4 Some of the Object Identifiers defined in

18、 the different Hypothetical-service-operation-asn1-97 modules are not well defined. Original Hypothetical-service-operation-asn1-97 iso standard hypothetical-Standard( 2222222) first-and-only-module-asn1-97 ( 0) Corrected Hypothetical-service-operation-asn1-97 iso standard hypothetical-standard( 222

19、2222) first-and-only-module-asn1-97 ( 0) Original IMPORTS OPERATION FROM Remote-Operation-Notation joint-iso-ccitt( 2) remote-operations( 4) notation( 0) ; Corrected IMPORTS OPERATION FROM Remote-Operations-Information-Objects joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0) ;

20、Clause F.2, table F.5 Some of the Object Identifiers defined in the different Hypothetical-service-operation-asn1-97 modules are not well defined. Original Hypothetical-service-operation-asn1-97 iso standard hypothetical-Standard( 2222222) first-and-only-module-asn1-97 ( 0) Corrected Hypothetical-se

21、rvice-operation-asn1-97 iso standard hypothetical-standard( 2222222) first-and-only-module-asn1-97 ( 0) Original IMPORTS OPERATION FROM Remote-Operation-Notation joint-iso-ccitt( 2) remote-operations( 4) notation( 0) ; Corrected IMPORTS OPERATION FROM Remote-Operations-Information-Objects joint-iso-

22、itu-t remote-operations(4) informationObjects(5) version1(0) ; Original IDENTIFIER iso identified-organization icd-ecma member-company hypothetical-manufacturer hypothetical-extension-number1 Corrected IDENTIFIER iso identified-organization icd-ecma member-company hypothetical-manufacturer hypotheti

23、cal-extension-number1 (1) Original IDENTIFIER iso identified-organization icd-ecma member-company hypothetical-manufacturer hypothetical-extension-number2 Corrected IDENTIFIER iso identified-organization icd-ecma member-company hypothetical-manufacturer hypothetical-extension-number2 (2) In addition

24、 replace all occurrences of Original extension CHOICE single 2 IMPLICIT ExtensionExampleExtensionSet multiple 3 IMPLICIT SEQUENCE OF ExtensionExampleExtensionSet Corrected extension CHOICE single 2 IMPLICIT ExtensionExampleExtensionSet, multiple 3 IMPLICIT SEQUENCE OF ExtensionExampleExtensionSet -

25、i - Table of contents 1 Scope 1 2 Conformance 1 3 References (normative) 1 4 Definitions 2 4.1 External definitions 2 4.2 ACSE APDU 2 4.3 Additional Network Feature (ANF) 2 4.4 Adjacent PINX 2 4.5 Application Protocol Data Unit (APDU) 3 4.6 Call, Basic call 3 4.7 Call independent signalling connecti

26、on 3 4.8 Call independent 3 4.9 Call related 3 4.10 Connection oriented 3 4.11 Connectionless 3 4.12 Coordination Function 3 4.13 Destination PINX 3 4.14 DSE APDU 3 4.15 Dialogue Service Element (DSE) 3 4.16 End PINX 3 4.17 Gateway PINX 3 4.18 Generic Functional Transport Control (GFT-Control) entit

27、y 3 4.19 Incoming side 4 4.20 Interpretation APDU 4 4.21 Inter-PINX link 4 4.22 Invocation 4 4.23 Link significance 4 4.24 Mistyped 4 4.25 Network significance 4 4.26 Next PINX 4 4.27 Notification 4 4.28 Originating PINX 4 4.29 Outgoing side 4 4.30 PINX address 4 4.31 Preceding PINX 4 4.32 Private S

28、ignalling System No.1 5 4.33 Protocol Control 5 4.34 ROSE APDU 5 4.35 Side 5 4.36 Signalling Carriage Mechanism (SCM) 5 4.37 Source PINX 5 - ii - 4.38 Subsequent PINX 5 4.39 Supplementary service 5 4.40 Supplementary Services Control (SS-Control) entity 5 4.41 Terminating PINX 5 4.42 Terminal, Termi

29、nal Equipment 5 4.43 Transit PINX 5 4.44 Unrecognised 5 5 List of acronyms 5 6 General principles 6 6.1 Application Association 6 6.2 Protocol Model 7 6.3 Application of the protocol model to communication between SS-Control entities in non-Adjacent PINXs 8 6.4 Services provided by ROSE 9 6.5 Servic

30、es provided by ACSE 9 6.6 Services provided by DSE 9 6.7 Services provided by GFT-Control 10 6.7.1 Connection oriented services 10 6.7.2 Connectionless transport services 11 6.7.3 Notification services 11 6.8 Services provided by Protocol Control to GFT-Control 12 6.8.1 Connection oriented transport

31、 services 12 6.8.2 Connectionless transport service 13 6.8.3 Notification services 13 6.9 Services required of the Signalling Carriage Mechanism 13 7 Protocol Control and GFT-Control Requirements 13 7.1 Call related Procedures for the transport of APDUs 13 7.1.1 Protocol Control requirements 13 7.1.

32、2 GFT-Control requirements 14 7.2 Connectionless APDU Transport Mechanism 22 7.2.1 Protocol Control requirements 22 7.2.2 Control requirements 22 7.3 Connection oriented call independent APDU transport mechanism 23 7.3.1 Protocol Control requirements 23 7.3.2 Dynamic Description (SDL) of Connection

33、oriented Protocol Control procedures 28 7.3.3 Generic Functional Transport Control requirements 34 7.4 Call related procedures for the transport of Notifications 37 7.4.1 Categories of notifications 37 7.4.2 Protocol Control requirements 37 7.4.3 GFT-Control requirements 38 8 Application layer requi

34、rements 38 8.1 Coordination Function requirements 38 8.1.1 Inclusion of an Interpretation APDU at a Source PINX 38 - iii - 8.1.2 Handling of APDUs at a Destination PINX 39 8.2 ROSE requirements 39 8.3 ACSE requirements 39 8.4 DSE requirements 40 8.4.1 Actions at the PINX which initiates the dialogue

35、 (PINX A) 40 8.4.2 Actions at the PINX which terminates the dialogue (PINX B) 41 8.4.3 Dialogue Continuation in the Active State 41 8.4.4 Dialogue Protocol Timers 41 8.4.5 Error procedures relating to dialogue control 42 8.4.6 Example of a dialogue 42 8.4.7 Dynamic Description (SDL) of Dialogue Iden

36、tification Protocol Procedures 42 8.5 SS-Control requirements 47 9 Manufacturer Specific Information 47 9.1 Manufacturer specific operations 47 9.2 Manufacturer specific additions to standardised operations 48 9.3 Manufacturer specific notifications 49 10 Message functional definitions and contents

37、49 10.1 ALERTING 49 10.2 CALL PROCEEDING 49 10.3 CONNECT 50 10.4 SETUP 50 10.5 DISCONNECT 50 10.6 RELEASE 51 10.7 RELEASE COMPLETE 51 10.8 FACILITY 51 10.9 NOTIFY 52 10.10 PROGRESS 52 11 General message format and information element coding 52 11.1 Message Type 52 11.2 Call reference 53 11.3 Other i

38、nformation elements 53 11.3.1 Bearer capability 53 11.3.2 Channel identification 54 11.3.3 Facility 54 11.3.4 Notification indicator 63 11.4 Encoding of information described using ASN.1 65 Annex A - Protocol Implementation Conformance Statement (PICS) for ECMA-165 67 Annex B - ASN.1 definitions of

39、generic parameters 77 Annex C - Application of the functional protocol 83 Annex D - Remote operations protocol and application association control 91 - iv - Annex E - Formal ROSE Definitions 93 Annex F - Examples of the use of Manufacturer specific information 95 Annex G - Problem code definitions 1

40、03 Annex H - Bibliography 105 Annex I - Object identifiers defined in ECMA-165 107 Annex J - “Recipe” for migration of X.208 / X.209 based QSIG ASN.1 modules to X.680 / X.690 ASN.1 109 Annex K - ASN.1 definitions according to ITU-T Recs. X.208 / X.209 115 Annex L - Technical changes since third edit

41、ion of ECMA-165 127 1 Scope This Standard defines the signalling protocol for the control of Supplementary Services and Additional Network Features (ANFs) at the Q reference point. The protocol is part of Private Signalling System no. 1 (PSS1), known informally as QSIG. The Q reference point exists

42、between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN) and is defined in ECMA-133. Detailed procedures applicable to individual supplementary services and ANFs are beyond the scope of this Standard and will be specified by

43、 other standards for those services which are standardised and by individual manufacturers for proprietary services using the capabilities defined in this Standard. ECMA-143 defines the Layer 3 protocol for circuit-switched call control at the Q reference point. This Standard defines additional prot

44、ocol procedures, to be used in conjunction with those defined in ECMA-143 for the control of supplementary services and ANFs. NOTE 1 Typical examples of the application of these generic functional procedures to some supplementary services are provided in annex C, for explanatory and illustrative pur

45、poses only. NOTE 2 Specific supplementary services and Additional Network Features may require additional information transfer mechanisms which are service or feature specific and are beyond the scope of this Standard. 2 Conformance In order to conform to this Standard, a PINX shall satisfy the requ

46、irements 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 provisions of this Standard. All standards are subject to revision, and parties t

47、o 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 ISO/IEC International Standards, the number of the appropriate ISO/IEC Internatio

48、nal 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-142 Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer Services - S

49、ervice Description, Functional Capabilities and Information Flows (International Standard ISO/IEC 11574) ECMA-143 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures and Protocol (International Standard ISO/IEC 11572) ECMA-155 Private Integrated Services Networks - Addressing (International Standard ISO/IEC 11571) ECMA-225 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Transit Counter