S tandard 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: [email protected]
.
S tandard 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: http://www.ecma.ch - Internet: [email protected] 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 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 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 bodies. It 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 of contents 1
Scope
1
2
Conformance
1
3
References (normative)
1
4
Definitions 4 . 1 E x te r n a l d e f in itio n s 4 . 2 O th e r d e f in itio n s 4.2.1 Client User PINX 4.2.2 Server User PINX
2 2 2 2 2
5
List of acronyms
2
6
Signalling protocol for the support of SS-SD 6 . 1 S S - S D d e s c r ip tio n 6 . 2 S S - S D o p e r a tio n a l r e q u ir e me n ts 6.2.1 Re q u ir e me n ts o n a Clie n t U s e r P I N X 6.2.2 Re q u ir e me n ts o n a S e r v e r U s e r P I N X 6.2.3 Re q u ir e me n ts o n a T r a n s it P I N X 6 . 3 S S - S D c o d in g r e q u ir e me n ts 6.3.1 Operations 6.3.2 I n f o r ma t i o n e l e me n t s 6.3.3 Messages 6 . 4 S S - S D s ta te d e f in itio n s 6.4.1 States at the Client User PINX 6.4.2 States at the Server User PINX 6 . 5 S S - S D s ig n a llin g p r o c e d u r e s 6.5.1 Actions at the Client User PINX 6.5.2 Actions at the Server User PINX 6.5.3 Actions at a Transit PINX 6 . 6 S S - S D imp a c t o f in te r w o r k in g w ith p u b lic I S D N s 6.6.1 I n c o min g G a te w a y P I N X p r o c e d u r e s 6.6.2 O u tg o in g G a te w a y P I N X p r o c e d u r e s 6 . 7 S S - S D imp a c t o f in te r w o r k in g w ith n o n - I S D N s 6.7.1 I n c o min g G a te w a y P I N X p r o c e d u r e s 6.7.2 O u tg o in g G a te w a y P I N X p r o c e d u r e s 6 . 8 P r o to c o l in te r a c tio n s b e tw e e n S S - S D a n d o th e r s u p p le me n ta r y s e r v ic e s a n d A N F s 6.8.1 Calling Line Identification Presentation (SS-CLIP) 6.8.2 C o n n e c t e d L i n e I d e n t i f i c a t io n P r e s e n ta tio n ( S S - CO L P ) 6.8.3 Ca llin g /Co n n e c te d L in e I d e n tif ic a tio n Re s tr ic tio n ( S S - CL I R) 6.8.4 C a l l i n g N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C N I P ) 6.8.5 C a l l i n g N a me I d e n t i f i c a t i o n P r e s e n t a t i o n ( S S - C N I R )
3 3 3 3 3 3 4 4 5 5 6 6 6 6 6 7 7 7 7 7 7 7 7 8 8 8 8 8 8
- ii -
6.8.6 C o n n e c t e d N a me I d e n t i f i c a t io n P r e s e n ta tio n ( S S - CO N P ) 6.8.7 C o mp l e t i o n o f C a l l t o B u s y S u b s c r i b e r ( S S - C C B S ) 6.8.8 C o mp l e t i o n o f C a l l o n N o R e p ly ( S S - C C N R ) 6.8.9 Call Transfer (SS-CT) 6.8.10 Ca ll F o r w a r d in g U n c o n d itio n a l ( S S - CF U ) 6.8.11 C a l l F o r w a r d in g B u s y ( S S - C F B ) 6.8.12 Ca ll F o r w a r d in g N o Re p ly ( S S - CF N R) 6.8.13 Call Deflection (SS-CD) 6.8.14 P a t h R e p l a c e me n t ( A N F - P R ) 6.8.15 Call Offer (SS-CO) 6.8.16 Call Intrusion (SS-CI) 6.8.17 Do not Disturb (SS-DND) 6.8.18 Do not Disturb Override (SS-DNDO) 6.8.19 A d v ic e o f Ch a r g e ( S S - A O C) 6.8.20 Recall (SS-RE) 6.8.21 Call Interception (ANF-CINT) 6.8.22 T r a n s it Co u n te r ( A N F - T C) 6.8.23 R o u te R e s t r i c t i o n C l a s s ( A N F - R R C ) 6.8.24 Me s s a g e W a itin g I n d ic a tio n ( S S - MW I ) 6.8.25 W ir e l e s s T e r mi n a l L o c a t i o n R e g i s t r a t i o n ( S S - W T L R ) 6.8.26 W ir e l e s s T e r mi n a l I n c o min g C a l l ( A N F - W T MI ) 6.8.27 W ir e l e s s T e r mi n a l O u t g o in g C a l l ( A N F - W T M O ) 6.8.28 W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f a W T M U s e r ( S S - W T A T ) 6.8.29 W ir e l e s s T e r mi n a l A u t h e n t i c a t i o n o f t h e P I S N ( S S - W T A N ) 6.8.30 P r i v a t e U s e r M o b i l i t y I n c o min g C a l l ( A N F - P U M I ) 6.8.31 P r i v a t e U s e r M o b i l i t y O u t g o in g C a l l ( A N F - P U M O ) 6.8.32 P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( S S - P U M R ) 6.8.33 C o mmo n I n f o r ma t i o n ( A N F - C MN ) 6.8.34 Call Priority Interruption (Protection) (SS-CPI(P)) 6.8.35 Single Step Call Transfer (SS-SSCT) 6 . 9 S S - S D p a r a me t e r v a l u e s ( t i me r s )
8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
A n n e x A - P r o t o c o l I m p l e m e n t a t i o n C o n fo r m a n c e S t a t e m e n t ( P I C S ) p r o f o r m a
11
A n n e x B - Ex a m p le s o f M e s s a g e S e q u e n c e s
15
A n n e x C - S p e c i f i c a t i o n a n d D e s c r i p t i o n L a n g ua g e ( S D L ) R e p r e s e n t a t i o n o f P r o c e d u r e s
19
A n n e x D - A S N . 1 d e f in it io n s a c c o r d in g t o I TU - T R e c s . X . 2 0 8 / X . 2 0 9
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 services 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 in 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 signalling 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 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 requirements 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 reference 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 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 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-143
Private Integrated Services Network (PISN) - Circuit Mode Bearer Services - InterExchange Signalling Procedures 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 Services 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 Network (PTN); Method for the specification of basic and supplementary services (1994)
ITU-T Rec. I.112
Vocabulary of terms for ISDNs (1993)
- 2 -
4
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 services 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)
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:
4.2
5
− Application Protocol Data Unit (APDU)
(ECMA-165)
− BMP String
(ISO/IEC 10646-1)
− Call-Independent
(ECMA-165)
− Client User
(ECMA-310)
− 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 Service
(ITU-T Rec. I.210)
− Supplementary Service Control Entity
(ECMA-165)
− Terminating PINX
(ECMA-165)
− Transit PINX
(ECMA-165)
Other definitions
4.2.1
C lie n t U s e r P I N X The PINX at which the Client User is located.
4.2.2
Server User PINX The PINX at which the Server User is located.
List of acronyms 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 -
6
NFE
Network Facility Extension
PICS
Protocol Implementation Conformance Statement
PINX
Private Integrated services Network eXchange
PISN
Private Integrated Services Network
SDL
Specification and Description Language
SS
Supplementary Service
SS-SD
Supplementary Service Simple Dialog
Signalling protocol for the support of SS-SD
6.1
SS-SD description SS-SD enables two users to communicate via the exchange of display 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 keypad information.
6.2 6.2.1
SS-SD operational requirements 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 supplementary 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 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 procedures 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. Generic 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 coding requirements
6.3.1
O p e r a t io n s 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-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, Extension{} 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 RETURN RESULT ERRORS
ALWAYS RESPONDS CODE keypad
DisplayArg
DisplayString
OPERATION ::= { ARGUMENT RETURN RESULT ALWAYS RESPONDS CODE ::= SEQUENCE { displayString extension }
DisplayArg FALSE {unspecified | noDisplayAvailable | displayTemporarilyNotAvailable | notPresentable } FALSE local: 103}
KeypadArg FALSE FALSE local: 104}
DisplayString, SDExtension
OPTIONAL
::= CHOICE { displayStringNormal [0] IMPLICIT BMPStringNormal, displayStringExtended [1] IMPLICIT BMPStringExtended }
- 5 -
Table 1 - Operations in support of SS-SD (concluded) KeypadArg
::= SEQUENCE { keypadString extension }
[0] IMPLICIT BMPStringNormal, SDExtension OPTIONAL
BMPStringNormal
::= OCTET STRING (SIZE(2..64))
-- shall be used according 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(2..160))
-- shall be used according to ISO/IEC 10646-1 -- coded as a BMP String according to -- ITU-T Rec. X.690
SDExtension
::= CHOICE { extension multipleExtension }
[2] IMPLICIT Extension{{SDExtSet}}, [3] IMPLICIT SEQUENCE OF Extension{{SDExtSet}}
SDExtSet EXTENSION ::= {...} unspecified
ERROR
::= { PARAMETER CODE
Extension{{SDExtSet}} local: 1008}
noDisplayAvailable
ERROR
::= { CODE
local:
1023}
displayTemporarilyNotAvailable
ERROR
::= { CODE
local:
1024}
notPresentable
ERROR
::= { CODE
local:
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 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 6.3.3
Other information elements Any other information element shall be coded in accordance with ECMA-143. Messages The Facility information element shall be conveyed in messages as specified in clause 10 of ECMA-165.
- 6 -
6.4
SS-SD state definitions
6.4.1
S t a t e s a t t h e C lie n t U s e r P I N X The procedures for the Client User PINX are written in terms of the following conceptual states existing within the SS-SD Control entity in that PINX in association with a particular SS-SD request from the Client User.
6.4.1.1 6.4.2
S t a t e S D - I d le SS-SD is not operating. States at the Server User PINX The procedures for the Server User PINX are written in terms of the following conceptual states existing within the SS-SD Control entity in that PINX.
6.4.2.1
6.5
S t a t e S D - I d le SS-SD is not operating.
SS-SD signalling procedures Examples of message sequences are shown in annex B.
6.5.1
A c t io n s a t t h e C lie n t U s e r P I N X The SDL representation of procedures at the Client User PINX is shown in clause C.2 of annex C.
6.5.1.1 Normal procedures 6 . 5 . 1 . 1 . 1 A c t iv a t io n / d e a c t iv a t io n / in t e r r o g a t io n Not applicable. 6.5.1.1.2
I n v o c a t io n a n d o p e r a t io n Due to a request from the Client User the Client User PINX shall send a keypad invoke APDU to the Server User PINX. The element keypadString of the keypad invoke APDU shall contain the Client User's keypad information coded as a BMP String. For the transport of this keypad invoke APDU the Call Reference of an already existing call independent or call related signalling connection shall be used. If no such connection exists and no call has to be established, the Client User shall set up a call independent signalling connection in accordance with the procedures specified in 7.3 of ECMA-165. The Client User is responsible for the clearing of this call independent signalling connection. On receipt of a display invoke APDU from the Server User PINX the Client User PINX shall send the display information in an appropriate format to the Client User.
6.5.1.2 Ex c e p t io n a l p r o c e d u r e s 6 . 5 . 1 . 2 . 1 A c t iv a t io n / d e a c t iv a t io n / in t e r r o g a t io n Not applicable. 6.5.1.2.2
I n v o c a t io n a n d o p e r a t io n Upon an indication that no display is available at the Client User, the Client User PINX shall send a display return error APDU with error value "noDisplayAvailable" to the Server User PINX. Upon an indication that the Client Users display is used by another process, the Client User PINX shall send a display return error APDU with error value "DisplayTemporarilyNotAvailable" to the Server User PINX. Upon an indication that the received display information cannot be presented correctly or completely at the Client Users display, the Client User PINX shall send a display return error APDU with error value "notPresentable" to the Server User PINX. Upon receipt of a keypad reject APDU the Client User PINX shall generate and send DTMF Tones to the Server User PINX.
- 7 -
6.5.2
Actions at the Server User PINX The SDL representation of procedures at the Server User PINX is shown in clause C.1 of annex C.
6.5.2.1 Normal procedures 6 . 5 . 2 . 1 . 1 A c t iv a t io n / d e a c t iv a t io n / in t e r r o g a t io n Not applicable. 6.5.2.1.2
I n v o c a t io n a n d o p e r a t io n On receipt of a keypad invoke APDU the Server User shall deliver the keypad information in an appropriate form to the Server User. On request of the Server User the Server User PINX shall send a display invoke APDU to the Client User PINX. The display invoke APDU shall contain the element displayString with the display information from the Server User coded as a BMP String. For the transport of this display invoke APDU the Call Reference of an already existing call independent or call related signalling connection shall be used. If no such connection exists, and no call has to be established, the Server User shall set up a call independent signalling connection in accordance with the procedures specified in 7.3 of ECMA-165.The Server User is responsible for the clearing of this call independent signalling connection.
6.5.2.2 Ex c e p t io n a l p r o c e d u r e s 6 . 5 . 2 . 2 . 1 A c t iv a t io n / d e a c t iv a t io n / in t e r r o g a t io n Not applicable. 6.5.2.2.2
6.5.3
6.6
I n v o c a t io n a n d o p e r a t io n On receipt of a display return error APDU from the Client User PINX containing the error values defined in 6.3.1 the Server User PINX shall send an appropriate error indication to the Server User.
A c t io n s a t a Tr a n s it P I N X Not applicable.
SS-SD impact of interworking with public ISDNs When interworking with a public ISDN that offers an equivalent supplementary service, a Gateway PINX shall perform the procedures specified below. NOTE The DTMF Tone generation due to received keypad invoke APDUs is out of the scope of this Standard.
6.6.1
I n c o m in g G a t e wa y P I N X p r o c e d u r e s If a SD request is received from the public ISDN (e.g. Display or Keypad Information Elements), the Incoming Gateway PINX shall translate the received information and convert it into a keypad or display invoke APDU and the procedures specified in 6.5.1 or 6.5.2 shall apply.
6.6.2
O u t g o in g G a t e wa y P I N X p r o c e d u r e s The Outgoing Gateway PINX shall translate the keypad and the display invoke APDUs and send it to the public ISDN according to the procedures for the T reference point.
6.7
SS-SD impact of interworking with non-ISDNs NOTE The DTMF Tone generation due to received keypad invoke APDUs is out of the scope of this Standard.
6.7.1
I n c o m in g G a t e wa y P I N X p r o c e d u r e s When interworking with a non-ISDN which supports an equivalent feature the Incoming Gateway PINX shall translate the received information and convert it into a keypad or display invoke APDU and the procedures specified in 6.5.1 or 6.5.2 shall apply.
6.7.2
O u t g o in g G a t e wa y P I N X p r o c e d u r e s When interworking with a non-ISDN which supports an equivalent feature the Outgoing Gateway PINX shall translate the keypad and the display invoke APDUs and send it to the non-ISDN in an appropriate style.
- 8 -
6.8
Protocol interactions between SS-SD and other supplementary services and ANFs This clause specifies protocol interactions with other supplementary services and ANFs for which stage 3 standards had been published at the time of publication of this Standard. For interactions with supplementary services and ANFs for which stage 3 standards are published subsequent to the publication of this Standard, see those other stage 3 standards. NOTE Simultaneous conveyance of APDUs for SS-SD and another supplementary service or ANF in the same message, each in accordance with the requirements of its respective stage 3 standard, does not, on its own, constitute a protocol interaction.
6.8.1
Calling Line Identification Presentation (SS-CLIP) No protocol interaction.
6.8.2
Connected Line Identification Presentation (SS-COLP) No protocol interaction.
6.8.3
C a l l i n g /C o n n e c t e d L i n e I d e n t i f i c a t i o n R e s t r i c t i o n ( S S - C L I R ) No protocol interaction.
6.8.4
Calling Name Identification Presentation (SS-CNIP) No protocol interaction.
6.8.5
Calling Name Identification Presentation (SS-CNIR) No protocol interaction.
6.8.6
Connected Name Identification Presentation (SS-CONP) No protocol interaction.
6.8.7
Completion of Call to Busy Subscriber (SS-CCBS) No protocol interaction.
6.8.8
Completion of Call on No Reply (SS-CCNR) No protocol interaction.
6.8.9
C a ll Tr a n s f e r ( S S - C T) No protocol interaction.
6.8.10
C a ll F o r wa r d in g U n c o n d it io n a l ( S S - C F U ) No protocol interaction.
6.8.11
C a ll F o r wa r d in g Bu s y ( S S - C F B) No protocol interaction.
6.8.12
C a ll F o r wa r d in g N o R e p ly ( S S - C F N R ) No protocol interaction.
6.8.13
C a ll D e f le c t io n ( S S - C D ) No protocol interaction.
6.8.14
Path Replacement (ANF-PR) No protocol interaction.
6.8.15
C a ll O f f e r ( S S - C O ) No protocol interaction.
6.8.16
C a ll I n t r u s io n ( S S - C I ) No protocol interaction.
6.8.17
Do not Disturb (SS-DND) No protocol interaction.
- 9 -
6.8.18
Do not Disturb Override (SS-DNDO) No protocol interaction.
6.8.19
A d v ic e o f C h a r g e ( S S - A O C ) No protocol interaction.
6.8.20
R e c a ll ( S S - R E) No protocol interaction.
6.8.21
Call Interception (ANF-CINT) No protocol interaction.
6.8.22
Tr a n s it C o u n t e r ( A N F - TC ) No protocol interaction.
6.8.23
Route Restriction Class (ANF-RRC) No protocol interaction.
6.8.24
M e s s a g e W a it in g I n d ic a t io n ( S S - M W I ) No protocol interaction.
6.8.25
W i r e l e s s T e r m i n a l L o c a t io n R e g i s t r a t i o n ( S S - W T L R ) No protocol interaction.
6.8.26
Wireless Terminal Incoming Call (ANF-WTMI) No protocol interaction.
6.8.27
Wireless Terminal Outgoing Call (ANF-WTMO) No protocol interaction.
6.8.28
Wireless Terminal Authentication of a WTM User (SS-WTAT) No interaction
6.8.29
Wireless Terminal Authentication of the PISN (SS-WTAN) No protocol interaction.
6.8.30
Private User Mobility Incoming Call (ANF-PUMI) No protocol interaction.
6.8.31
P r i v a t e U s e r M o b i l i t y O u t g o in g C a l l ( A N F - P U M O ) No protocol interaction.
6.8.32
P r i v a t e U s e r M o b i l i t y R e g is t r a t i o n ( S S - P U M R ) No protocol interaction.
6.8.33
Common Information (ANF-CMN) No protocol interaction.
6.8.34
C a ll P r io r it y I n t e r r u p t io n ( P r o t e c t i o n ) ( S S - C P I ( P ) ) No protocol interaction.
6.8.35
Single Step Call Transfer (SS-SSCT) No protocol interaction.
6.9
SS-SD parameter values (timers) Not applicable.
- 10 -
- 11 -
Annex A ( n o r ma tiv e )
Protocol Implementation Conformance Statement (PICS) proforma
A.1
Introduction The supplier of a protocol implementation which is claimed to conform to this Standard shall complete the following Protocol Implementation Conformance Statement (PICS) proforma. A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of which capabilities and options of the protocol have been implemented. The PICS can have a number of uses, including use: − by the protocol implementor, as a check-list to reduce the risk of failure to conform to the standard through oversight; − by the supplier and acquirer, or potential acquirer, of the implementation, as a detailed indication of the capabilities of the implementation, stated relative to the common basis for understanding provided by the standard's PICS proforma; − by the user or potential user of the implementation, as a basis for initially checking the possibility of interworking with another implementation - while interworking can never be guaranteed, failure to interwork can often be predicted from incompatible PICSs; − by a protocol tester, as the basis for selecting appropriate tests against which to assess the claim for conformance of the implementation.
A.2
Instructions for completing the PICS proforma
A.2.1
General structure of the PICS proforma The PICS proforma is a fixed-format questionnaire divided into sub-clauses each containing a group of individual items. Each item is identified by an item number, the name of the item (question to be answered), and the reference(s) to the clause(s) that specifies (specify) the item in the main body of this Standard. The “Status” column indicates whether an item is applicable and if so whether support is mandatory or optional. The following terms are used: m
mandatory (the capability is required for conformance to the protocol);
o
optional (the capability is not required for conformance to the protocol, but if the capability is implemented it is required to conform to the protocol specifications);
o.<n>
optional, but support of at least one of the group of options labelled by the same numeral <n> is required;
x
prohibited;
<c.cond>
conditional requirement, depending on support for the item or items listed in condition <cond>;
<item>:m
simple conditional requirement, the capability being mandatory if item number <item> is supported, otherwise not applicable;
<item>:o
simple conditional requirement, the capability being optional if item number <item> is supported, otherwise not applicable.
Answers to the questionnaire items are to be provided either in the “Support” column, by simply marking an answer to indicate a restricted choice (Yes or No), or in the “Not Applicable” column (N/A).
- 12 -
A.2.2
Additional information Items of additional information allow a supplier to provide further information intended to assist the interpretation of the PICS. It is not intended or expected that a large quantity will be supplied, and a PICS can be considered complete without any such information. Examples might be an outline of the ways in which a (single) implementation can be set up to operate in a variety of environments and configurations. References to items of additional information may be entered next to any answer in the questionnaire, and may be included in items of exception information.
A.2.3
Exception information It may occasionally happen that a supplier will wish to answer an item with mandatory or prohibited status (after any conditions have been applied) in a way that conflicts with the indicated requirement. No preprinted answer will be found in the Support column for this. Instead, the supplier is required to write into the Support column an x.<i> reference to an item of exception information, and to provide the appropriate rationale in the exception item itself. An implementation for which an exception item is required in this way does not conform to this Standard. A possible reason for the situation described above is that a defect in the standard has been reported, a correction for which is expected to change the requirement not met by the implementation.
- 13 -
A.3
PICS proforma for ECMA-311
A.3.1
Implementation identification
Supplier Contact point for queries about the PICS Implementation name(s) and version(s) Other information necessary for full identification, e.g., name(s) and version(s) for machines and/or operating systems; system name(s)
Only the first three items are required for all implementations; other information may be completed as appropriate in meeting the requirement for full identification. The terms name and version should be interpreted appropriately to correspond with a suppliers terminology (e.g. type, series, model).
A.3.2
Protocol summary
Protocol version
1.0
Addenda implemented (if applicable) Amendments implemented Have any exception items been required (see A.2.3)?
Date of Statement
No [ ] Yes [ ] (The answer Yes means that the implementation does not conform to this Standard)
- 14 -
A.3.3
General
Item
Question/feature
A1
Status
N/A
Support
Behaviour as Client User PINX for SS-SD
o.1
[]
Yes [ ] No[ ]
A2
Behaviour as Server User PINX for SS-SD
o.1
[]
Yes [ ] No[ ]
A3
Behaviour as Incoming Gateway PINX for interworking with a public ISDN for SS-SD
o
Yes [ ] No[ ]
A4
Behaviour as Outgoing Gateway PINX for interworking with a public ISDN for SS-SD
o
Yes [ ] No[ ]
A.3.4
References
Procedures
Item
Question/feature
References
Status
N/A
Support
B1
Support of relevant ECMA-143 and ECMA-165 procedures at the Client User PINX
6.2.1
A1:m
[]
m:Yes [ ]
B2
Support of relevant ECMA-143 and ECMA-165 procedures at the Server User PINX
6.2.2
A2:m
[]
m:Yes [ ]
B3
Procedures at the Client User PINX for invocation and operation
6.5.1
A1:m
[]
m:Yes [ ]
B4
Procedures at the Server User PINX for invocation and operation
6.5.2
A2:m
[]
m:Yes [ ]
B7
Procedures at an Incoming Gateway PINX for interworking with a public ISDN for invocation and operation of SS-SD
6.6.1
A3:m
[]
m:Yes [ ]
B8
Procedures at an Outgoing Gateway PINX for interworking with a public ISDN for invocation and operation of SS-SD
6.6.2
A4:m
[]
m:Yes [ ]
A.3.5
Coding
Item
Question/feature
References
Status
N/A
Support
C1
Sending of display invoke APDU from the Server User PINX
6.3.1
A2:m
[]
m:Yes [ ]
C2
Receipt of display invoke APDU at the Client User PINX and sending of display return error APDU in case of an error indication
6.3.1
A1:m
[]
m:Yes [ ]
C3
Sending of keypad invoke APDU from the Client User PINX
6.3.1
A1:m
[]
m:Yes [ ]
C4
Receipt of keypad invoke APDU at the Server User PINX
6.3.1
A2:m
[]
m:Yes [ ]
- 15 -
Annex B ( in f o r ma tiv e )
Examples of Message Sequences
This annex describes some typical message flows for SS-SD. The following conventions are used in the figures of this annex. 1. The following notation is used: Basic call message containing SS-SD information Basic call message without SS-SD information Call Independent Signalling Connection messages containing SS-SD information Call Independent Signalling Connection messages without SS-SD information SS-SD information for the connected users
xxx.inv xxx.rr xxx.re
Invoke APDU for operation xxx Return result APDU for operation xxx Return error APDU for operation xxx
2. The figures show messages exchanged via Protocol Control between PINXs involved in SS-SD. Only messages relevant to SS-SD are shown. 3. Only the relevant information content (e.g. remote operation APDUs, notifications, information elements) is listed below each message name. The Facility and Notification indicator information elements containing remote operation APDUs and notifications are not explicitly shown. Information with no impact on SS-SD is not shown.
- 16 -
Example message sequences with prior existing connection Figure B.1 shows an example of successful invocation and operation of SS-SD initiated by the Server User PINX in case of a basic call connection is established before invocation of SS-SD. Figure B.2 shows an example of unsuccessful invocation and operation of SS-SD initiated by the Server User PINX in case of a basic call connection is established before invocation of SS-SD.
Server User PINX
Transit PINX
Client User PINX
active basic call
Display
Key
display.inv
display.inv
FACILITY
FACILITY
keypad.inv
keypad.inv
...
Key
FACILITY
FACILITY
FACILITY
display.inv
display.inv
FACILITY
FACILITY
keypad.inv
keypad.inv
...
Display
FACILITY
...
B.1.1
Example message sequences for invocation and operation of SS-SD
...
B.1
F ig u r e B. 1 - Ex a m p le o f s u c c e s s f u l in v o c a t io n a n d o p e r a t io n o f S S - S D by the Server User PINX
Display
Key
Display
Key
- 17 -
Server User PINX
Transit PINX
Client User PINX
active basic call
Display
Error indication
FACILITY
FACILITY
display.inv
display.inv
FACILITY
FACILITY
display.re (e.g. “noDisplayAvailable“)
display.re (e.g. “noDisplayAvailable“)
F ig u r e B. 2 - Ex a m p le o f u n s u c c e s s f u l in v o c a t io n a n d o p e r a t io n o f S S - S D by the Server User PINX
- 18 -
B.1.2
Example message sequences of a successful communication without a prior established connection Figure B.3 shows an example for an successful communication between the Server User and the Client User without a prior established connection. After a Call Independant Signalling Connection (CISC) is established (on behalf of the Client User), the communication is realized by the exchange of display and keypad information.
Key
CALL PROCEEDING
CALL PROCEEDING
CONNECT
CONNECT
FACILITY
FACILITY
display.inv
display.inv
FACILITY
FACILITY
keypad.inv
keypad.inv
...
Display
keypad.inv
FACILITY
FACILITY
display.inv
display.inv
FACILITY
FACILITY
keypad.inv
keypad.inv
...
Key
keypad.inv
...
Display
SETUP
...
Key
SETUP
RELEASE
RELEASE
RELEASE COMPLETE
RELEASE COMPLETE
setup request from the Client User
Display Key
Display
Key
F ig u r e B. 3 - Ex a m p le o f s u c c e s s f u l c o m m u n i c a t i o n f o r S S - S D w i t ho u t p r i o r e x i s t i n g c o n n e c t i o n between a Server User PINX and a Client User PINX
- 19 -
Annex C ( in f o r ma tiv e )
Specification and Description Language (SDL) Representation of Procedures
The diagrams in this annex use the Specification and Description Language defined in ITU-T Rec. Z.100 (1999). Each diagram represents the behaviour of an SS-SD Supplementary Service Control entity at a particular type of PINX. In accordance with the protocol model described in ECMA-165, the Supplementary Service Control entity uses, via the Coordination Function, the services of Generic Functional Procedures Control. Where an output symbol represents a primitive to the Coordination Function, and that primitive results in a message being sent, the output symbol bears the name of the message and any remote operations APDU(s) or notification(s) contained in that message. Where an input symbol represents a primitive from the Coordination Function, and that primitive is the result of a message being received, the input symbol bears the name of the message and any remote operations APDU(s) or notification(s) contained in that message. The following abbreviations are used: .inv
invoke APDU
.re
return error APDU
C.1
SDL representation of SS-SD at the Client User PINX Figures C.1 show the behaviour of an SS-SD Supplementary Service Control entity within the Client User PINX. Input signals from the left and output signals to the left represent primitives from and to the Client User. Input signals from the right and output signals to the right represent primitives from and to the Coordination Function in respect of messages received and sent.
- 20 -
SS-SD idle
Receipt of key press events
Receipt of display.inv
display possible?
no
yes
Sending of keypad.inv
display pattern
Sending of display.re
SS-SD idle
Figure C.1 - SDL representation of SS-SD at the Client User PINX
C.2
SDL representation of SS-SD at the Server User PINX Figures C.2 show the behaviour of an SS-SD Supplementary Service Control entity within the Server User PINX. Input signals from the right and output signals to the right represent primitives from and to the Server User. Input signals from the left and output signals to the left represent primitives from and to the Coordination Function in respect of messages received and sent.
- 21 -
SS-SD idle
Receipt of keypad.inv
keypad information
display information
Sending of display.inv
Receipt of display.re
error indication
SS-SD idle
Figure C.2 - SDL representation of SS-SD at the Server User PINX
- 22 -
- 23 -
Annex D ( n o r ma tiv e )
ASN.1 definitions according to ITU-T Recs. X.208 / X.209
This annex lists all ASN.1 modules as they were defined in the first edition of ECMA-311, i.e. based on ITU-T Recommendations X.208 / X.209. Starting with the second edition the ASN.1 modules within ECMA-311 comply with ITU-T Recommendations X.680 / X.690. Please note that regardless of which version of these modules is used as a base of a QSIG implementation, the line encoding remains unchanged. Changes in future editions to modules based on X.680 / X.690 ASN.1 are not reflected in the modules in this annex. Ta b le D . 1 - S S - S D - O p e r a t io n s - b a s e d o n I TU - T R e c s . X . 2 0 8 / X . 2 0 9 SS-SD-Operations { iso (1) standard (0) pss1-simple-dialog (21407) simple-dialog-operations (0)} DEFINITIONS EXPLICIT TAGS ::= BEGIN IMPORTS
OPERATION, ERROR FROM Remote-Operation-Notation {joint-iso-ccitt (2) remote-operations (4) notation (0)} Extension FROM Manufacturer-specific-service-extension-definition {iso (1) standard (0) pss1-generic-procedures (11582) msi-definition (0)};
Display
Keypad
DisplayArg
DisplayString
::= OPERATION ARGUMENT ERRORS
::= OPERATION ARGUMENT ::= SEQUENCE { displayString extension }
DisplayArg {unspecified, noDisplayAvailable, displayTemporarilyNotAvailable, notPresentable }
KeypadArg
DisplayString, SDExtension
OPTIONAL
::= CHOICE { displayStringNormal [0] IMPLICIT BMPStringNormal, displayStringExtended [1] IMPLICIT BMPStringExtended }
- 24 -
Ta b le D . 1 - S S - S D - O p e r a t io n s - b a s e d o n I TU - T R e c s . X . 2 0 8 / X . 2 0 9 ( c o n c lu d e d ) KeypadArg
::= SEQUENCE { keypadString extension }
[0] IMPLICIT BMPStringNormal, SDExtension OPTIONAL
BMPStringNormal
::= OCTET STRING (SIZE(2..64))
-- shall be used according 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(2..160))
-- shall be used according to ISO/IEC 10646-1 -- coded as a BMP String according to -- ITU-T Rec. X.690
SDExtension
::= CHOICE { extension multipleExtension }
[2] IMPLICIT Extension, [3] IMPLICIT SEQUENCE OF Extension
display
Display
::=
localValue 103
keypad
Keypad
::=
localValue 104
unspecified
Unspecified
::=
localValue 1008
noDisplayAvailable
ERROR
::=
localValue 1023
displayTemporarilyNotAvailable
ERROR
::=
localValue 1024
notPresentable
ERROR
::=
localValue 1025
Unspecified END
::=
ERROR PARAMETER Extension
.
.
Free printed copies can be ordered from: ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland Fax: Email:
+41 22 849.60.01 [email protected]
Files of this Standard can be freely downloaded from the ECMA web site (www.ecma.ch). This site gives full information on ECMA, ECMA activities, ECMA Standards and Technical Reports.
ECMA 114 Rue du Rhône CH-1204 Geneva Switzerland See inside cover page for obtaining further soft or hard copies.