1、 Standard ECMA-311 2nd Edition - December 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Simple Dialog Supplementary Service Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet
2、: helpdeskecma.ch . Standard ECMA-311 2nd Edition - December 2001 Standardizing Information and Communication Systems Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Simple Dialog Supplementary Service (QSIG-SD) Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL:
3、 http:/www.ecma.ch - Internet: helpdeskecma.ch IW Ecma-311.doc 14-01-02 10,50 . 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 developed by ITU-T
4、and conforms to the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. This particular Standard specifies the signalling protocol for use at the Q reference point in support of the Simple Dialog supplementary service. The protocol defined in this Standard fo
5、rms 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 bodies. I
6、t represents a pragmatic and widely based consensus. Compared to the 1st Edition of Standard ECMA-311 (published by ECMA in June 2000), this 2nd Edition incorporates migration to ASN.1 version 1997. Adopted as 2nd Edition of Standard ECMA-311 by the General Assembly of December 2001. . - i - Table o
7、f contents 1 Scope 1 2 Conformance 1 3 References (normative) 1 4 Definitions 2 4.1 External definitions 2 4.2 Other definitions 2 4.2.1 Client User PINX 2 4.2.2 Server User PINX 2 5 List of acronyms 2 6 Signalling protocol for the support of SS-SD 3 6.1 SS-SD description 3 6.2 SS-SD operational req
8、uirements 3 6.2.1 Requirements on a Client User PINX 3 6.2.2 Requirements on a Server User PINX 3 6.2.3 Requirements on a Transit PINX 3 6.3 SS-SD coding requirements 4 6.3.1 Operations 4 6.3.2 Information elements 5 6.3.3 Messages 5 6.4 SS-SD state definitions 6 6.4.1 States at the Client User PINX
9、 6 6.4.2 States at the Server User PINX 6 6.5 SS-SD signalling procedures 6 6.5.1 Actions at the Client User PINX 6 6.5.2 Actions at the Server User PINX 7 6.5.3 Actions at a Transit PINX 7 6.6 SS-SD impact of interworking with public ISDNs 7 6.6.1 Incoming Gateway PINX procedures 7 6.6.2 Outgoing G
10、ateway PINX procedures 7 6.7 SS-SD impact of interworking with non-ISDNs 7 6.7.1 Incoming Gateway PINX procedures 7 6.7.2 Outgoing Gateway PINX procedures 7 6.8 Protocol interactions between SS-SD and other supplementary services and ANFs 8 6.8.1 Calling Line Identification Presentation (SS-CLIP) 8
11、6.8.2 Connected Line Identification Presentation (SS-COLP) 8 6.8.3 Calling/Connected Line Identification Restriction (SS-CLIR) 8 6.8.4 Calling Name Identification Presentation (SS-CNIP) 8 6.8.5 Calling Name Identification Presentation (SS-CNIR) 8 - ii - 6.8.6 Connected Name Identification Presentati
12、on (SS-CONP) 8 6.8.7 Completion of Call to Busy Subscriber (SS-CCBS) 8 6.8.8 Completion of Call on No Reply (SS-CCNR) 8 6.8.9 Call Transfer (SS-CT) 8 6.8.10 Call Forwarding Unconditional (SS-CFU) 8 6.8.11 Call Forwarding Busy (SS-CFB) 8 6.8.12 Call Forwarding No Reply (SS-CFNR) 8 6.8.13 Call Deflect
13、ion (SS-CD) 8 6.8.14 Path Replacement (ANF-PR) 8 6.8.15 Call Offer (SS-CO) 8 6.8.16 Call Intrusion (SS-CI) 8 6.8.17 Do not Disturb (SS-DND) 8 6.8.18 Do not Disturb Override (SS-DNDO) 9 6.8.19 Advice of Charge (SS-AOC) 9 6.8.20 Recall (SS-RE) 9 6.8.21 Call Interception (ANF-CINT) 9 6.8.22 Transit Cou
14、nter (ANF-TC) 9 6.8.23 Route Restriction Class (ANF-RRC) 9 6.8.24 Message Waiting Indication (SS-MWI) 9 6.8.25 Wireless Terminal Location Registration (SS-WTLR) 9 6.8.26 Wireless Terminal Incoming Call (ANF-WTMI) 9 6.8.27 Wireless Terminal Outgoing Call (ANF-WTMO) 9 6.8.28 Wireless Terminal Authenti
15、cation of a WTM User (SS-WTAT) 9 6.8.29 Wireless Terminal Authentication of the PISN (SS-WTAN) 9 6.8.30 Private User Mobility Incoming Call (ANF-PUMI) 9 6.8.31 Private User Mobility Outgoing Call (ANF-PUMO) 9 6.8.32 Private User Mobility Registration (SS-PUMR) 9 6.8.33 Common Information (ANF-CMN) 9
16、 6.8.34 Call Priority Interruption (Protection) (SS-CPI(P) 9 6.8.35 Single Step Call Transfer (SS-SSCT) 9 6.9 SS-SD parameter values (timers) 9 Annex A - Protocol Implementation Conformance Statement (PICS) proforma 11 Annex B - Examples of Message Sequences 15 Annex C - Specification and Descriptio
17、n Language (SDL) Representation of Procedures 19 Annex D - ASN.1 definitions according to ITU-T Recs. X.208 / X.209 23 1 Scope This Standard specifies the signalling protocol for the support of the Simple Dialog supplementary service (SS-SD) at the Q reference point between Private Integrated servic
18、es Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). Supplementary service SD enables a user to communicate with another user or application by the exchange of keypad and display information transparently over a PISN. The Q reference point is defined i
19、n ECMA-133. Service specifications are produced in three stages and according to the method 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-310. The signal
20、ling protocol for SS-SD operates on top of the signalling protocol for basic circuit switched call control, as specified in ECMA-143, and uses certain aspects of the generic procedures for the control of supplementary services specified in ECMA-165. This Standard also specifies additional signalling
21、 protocol requirements for the support of interactions at the Q reference point between SS-SD and other supplementary services and ANFs. This Standard is applicable to PINXs which can interconnect to form a PISN. 2 Conformance In order to conform to this Standard, a PINX shall satisfy the requiremen
22、ts identified in the Protocol Implementation Conformance Statement (PICS) proforma in annex A. Conformance to this Standard includes conforming to those clauses that specify protocol interactions between SS-SD and other supplementary services and ANFs for which signalling protocols at the Q referenc
23、e point are supported in accordance with the stage 3 standards concerned. 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 to agreements based on this
24、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 International Standard is given in br
25、ackets after the ECMA reference. ECMA-133 Private Integrated Services Network (PISN) - Reference Configuration for PISN Exchanges (PINX) (International Standard ISO/IEC 11579-1) ECMA-143 Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - Inter-Exchange Signalling Procedures
26、and Protocol (International Standard ISO/IEC 11572) ECMA-165 Private Integrated Services Network (PISN) - Generic Functional Protocol for the Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol (International Standard ISO/IEC 11582) ECMA-310 Private Integrated Servi
27、ces Network (PISN) - Specification, Functional Model and Information Flows - Simple Dialog Supplementary Service ISO/IEC 10646-1 Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1 Architecture and Basic Multilingual Plane (1993) ETS 300 387 Private Telecommunication
28、 Network (PTN); Method for the specification of basic and supplementary services (1994) ITU-T Rec. I.112 Vocabulary of terms for ISDNs (1993) - 2 - ITU-T Rec. I.210 Principles of telecommunication services supported by an ISDN and the means to describe them (1993) ITU-T Rec. Q.950 Supplementary serv
29、ices protocols, structure and general principles (2000) ITU-T Rec. X.690 Information Technology - ASN.1 Encoding Rules - Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) ITU-T Rec. Z.100 Specification and description language (1999) 4
30、 Definitions For the purposes of this Standard, the following definitions apply: 4.1 External definitions This Standard uses the following terms defined in other documents: Application Protocol Data Unit (APDU) (ECMA-165) BMP String (ISO/IEC 10646-1) Call-Independent (ECMA-165) Client User (ECMA-310
31、) Display Information (ECMA-310) Gateway PINX (ECMA-165) Keypad Information (ECMA-310) Originating PINX (ECMA-165) Private Integrated Services Network (PISN) (ECMA-133) Private Integrated services Network eXchange (PINX) (ECMA-133) Server User (ECMA-310) Signalling (ITU-T Rec. I.112) Supplementary S
32、ervice (ITU-T Rec. I.210) Supplementary Service Control Entity (ECMA-165) Terminating PINX (ECMA-165) Transit PINX (ECMA-165) 4.2 Other definitions 4.2.1 Client User PINX The PINX at which the Client User is located. 4.2.2 Server User PINX The PINX at which the Server User is located. 5 List of acro
33、nyms ANF Additional Network Feature APDU Application Protocol Data Unit ASN.1 Abstract Syntax Notation no. 1 BMP Basic Multilingual Plane ISDN Integrated Services Digital Network - 3 - NFE Network Facility Extension PICS Protocol Implementation Conformance Statement PINX Private Integrated services
34、Network eXchange PISN Private Integrated Services Network SDL Specification and Description Language SS Supplementary Service SS-SD Supplementary Service Simple Dialog 6 Signalling protocol for the support of SS-SD 6.1 SS-SD description SS-SD enables two users to communicate via the exchange of disp
35、lay and keypad information. The Server User is the user who exclusively sends the display information. The user who receives that information and who is able to answer the Server User with keypad information is called the Client User. SS-SD shall be exclusively used to convey display information and
36、 keypad information. 6.2 SS-SD operational requirements 6.2.1 Requirements on a Client User PINX Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as specified in ECMA-143, shall apply. Generic procedures for call-related control of s
37、upplementary services, as specified in ECMA-165 for an End PINX, shall apply. Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in ECMA-165 for an Originating PINX and for a Terminating PINX, shall apply. 6.2.2 Requirements on a Server
38、User PINX Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release procedures, as specified in ECMA-143, shall apply. Generic procedures for call-related control of supplementary services, as specified in ECMA-165 for an End PINX, shall apply. Generic p
39、rocedures for the call-independent control (connection-oriented) of supplementary services, as specified in ECMA-165 for a Terminating PINX and for an Originating PINX, shall apply. 6.2.3 Requirements on a Transit PINX Basic call procedures specified in ECMA-143 for a Transit PINX shall apply. Gener
40、ic procedures for call-related control of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply. Generic procedures for the call-independent control (connection-oriented) of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply. - 4 - 6.3 SS-SD c
41、oding requirements 6.3.1 Operations The operations defined in Abstract Syntax Notation number 1 (ASN.1) in table 1 shall apply. The notation is in accordance with ITU-T Rec. X.680 and X.690. The ITU-T Rec. X.208 and X.209 superseded version is in annex D. Table 1 - Operations in support of SS-SD SS-
42、SD-Operations-asn1-97 iso (1) standard (0) pss1-simple-dialog (21407) simple-dialog-operations-asn1-97 (1) DEFINITIONS EXPLICIT TAGS := BEGIN IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects joint-iso-itu-t (2) remote-operations (4) informationObjects (5) version1 (0) EXTENSION, E
43、xtension FROM Manufacturer-specific-service-extension-class-asn1-97 iso (1) standard (0) pss1-generic-procedures (11582) msi-class-asn1-97(11); SD-Operations OPERATION := display | keypad display OPERATION := ARGUMENT DisplayArg RETURN RESULT FALSE ERRORS unspecified | noDisplayAvailable | displayTe
44、mporarilyNotAvailable | notPresentable ALWAYS RESPONDS FALSE CODE local: 103 keypad OPERATION := ARGUMENT KeypadArg RETURN RESULT FALSE ALWAYS RESPONDS FALSE CODE local: 104 DisplayArg := SEQUENCE displayString DisplayString, extension SDExtension OPTIONAL DisplayString := CHOICE displayStringNormal
45、 0 IMPLICIT BMPStringNormal, displayStringExtended 1 IMPLICIT BMPStringExtended - 5 - Table 1 - Operations in support of SS-SD (concluded) KeypadArg := SEQUENCE keypadString 0 IMPLICIT BMPStringNormal, extension SDExtension OPTIONAL BMPStringNormal := OCTET STRING (SIZE(264) - shall be used accordin
46、g to - ISO/IEC 10646-1 (section 6.2) - coded as a BMP String according to - ITU-T Rec. X.690 (section 8.20.8) BMPStringExtended := OCTET STRING (SIZE(2160) - shall be used according to ISO/IEC 10646-1 - coded as a BMP String according to - ITU-T Rec. X.690 SDExtension := CHOICE extension 2 IMPLICIT
47、ExtensionSDExtSet, multipleExtension 3 IMPLICIT SEQUENCE OF ExtensionSDExtSet SDExtSet EXTENSION := . unspecified ERROR := PARAMETER ExtensionSDExtSet CODE local: 1008 noDisplayAvailable ERROR := CODE local: 1023 displayTemporarilyNotAvailable ERROR := CODE local: 1024 notPresentable ERROR := CODE l
48、ocal: 1025 END - of SS-SD-Operations-asn1-97 6.3.2 Information elements 6.3.2.1 Facility information element The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ECMA-165. When conveying the invoke APDUs of operations defined in 6.3.1, the destination
49、 Entity data element of the NFE shall contain the value endPINX. When conveying the invoke APDUs of operations defined in 6.3.1, the interpretation APDU shall either be omitted or have the value rejectAnyUnrecognizedInvokePdu. 6.3.2.2 Other information elements Any other information element shall be coded in accordance with ECMA-143. 6.3.3 Messages The Facility information element shall be conveyed in messages as specified in clause 10 of ECMA-165.
