S tandard ECMA-164
4th Edition - December 2001
Standardizing Information
and
Communication
Systems
Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Name Identification Supplementary Services
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]
.
S tandard ECMA-164
4th Edition - December 2001
Standardizing
Information
and
Communication
Systems
Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Name Identification Supplementary Services (QSIG-NA)
Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW
Ecma-164.doc
14-01-02 14,08
.
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 Calling Name Identification Presentation (CNIP) and Connected Name Identification Presentation (CONP) supplementary services. 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, 2nd and 3rd Editions of Standard ECMA-164 (published by ECMA in March 1992, June 1993 September 1998 respectively), this 4th Edition incorporates additional character sets for the coding of the Name identification as well as migration to ASN.1 version 1997. Differences between this ECMA Standard and the ISO/IEC International Standard with which it is aligned are clearly identified.
Adopted as 4th Edition of Standard ECMA-164 by the General Assembly of December 2001.
- i -
Table of contents 1
Scope
1
2
Conformance
1
3
References (normative)
1
Definitions E x te r n a l d e f in itio n s N a me
2 2 3
5
Acronyms
3
6
SS-CNIP and SS-CONP Coding Requirements Operations I n f o r ma t i o n E l e me n t s Messages
4 4 6 6
4 4.1 4.2
6.1 6.2 6.3 7
Signalling Protocol for the Support of SS-CNIP 7.1 SS-CNIP Description 7 . 2 S S - CN I P O p e r a tio n a l Re q u ir e me n ts 7.2.1 Re q u ir e me n ts o n th e O r ig in a tin g P I N X a n d th e I n c o min g G a te w a y P I N X 7.2.2 Re q u ir e me n ts o n th e T e r min a tin g P I N X a n d th e O u tg o in g G a te w a y P I N X 7.2.3 Re q u ir e me n ts o n a T r a n s it P I N X 7.3 SS-CNIP State Definitions 7 . 4 S S - CN I P S ig n a llin g P r o c e d u r e s f o r I n v o c a tio n a n d O p e r a tio n 7.4.1 Actions at the Originating PINX 7.4.2 A c t i o n s a t t h e T e r mi n a t i n g P I N X 7.4.3 Actions at a Transit PINX 7 . 5 S S - CN I P I mp a c t o f I n te r w o r k in g w ith P u b lic I S D N s o r w ith N o n - I S D N s 7.5.1 A c t i o n s a t t h e I n c o min g G a t e w a y P I N X 7.5.2 Actions at the Outgoing Gateway PINX 7 . 6 P r o to c o l in te r a c tio n s b e tw e e n S S - CN I P an 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 7.6.1 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 ) 7.6.2 C o mp l e t i o n o f C a l l s t o B u s y S u b s c r i b e r s ( S S - C C B S ) 7.6.3 C o mp l e t i o n o f C a l l s o n N o R e p ly ( S S - C C N R ) 7.6.4 Call Transfer (SS-CT) 7.6.5 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 ) 7.6.6 C a l l F o r w a r d in g B u s y ( S S - C F B ) 7.6.7 Ca ll F o r w a r d in g N o Re p ly ( S S - CF N R) 7.6.8 Call Deflection (SS-CD) 7.6.9 P a t h R e p l a c e me n t ( A N F - P R )
8 8.1
Signalling Protocol for the Support of SS-CONP SS-CONP General Description
6 6 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 8 8 9 9 9 9 9 9
- ii -
8 . 2 S S - CO N P O p e r a tio n a l Re q u ir e me n ts 8.2.1 Re q u ir e me n ts o n th e T e r min a tin g P I N X a n d th e O u tg o in g G a te w a y P I N X 8.2.2 Re q u ir e me n ts o n th e O r ig in a tin g P I N X a n d th e I n c o min g G a te w a y P I N X 8.2.3 Re q u ir e me n ts o n a T r a n s it P I N X 8 . 3 S S - CO N P S ta te D e f in itio n s 8 . 4 S S - CO N P S ig n a llin g P r o c e d u r e s f o r I n v o c a tio n a n d O p e r a tio n 8.4.1 A c t i o n s a t t h e T e r mi n a t i n g P I N X 8.4.2 Actions at the Originating PINX 8.4.3 Actions at a Transit PINX 8 . 5 S S - CO N P I mp a c t o f I n te r w o r k in g w ith P u b lic I S D N s o r w ith N o n - I S D N s 8.5.1 A c t i o n s a t t h e O u tg o in g G a te w a y P I N X 8.5.2 A c t i o n s a t t h e I n c o min g G a t e w a y P I N X 8 . 6 P r o to c o l I n te r a c tio n b e tw e e n S S - CO N P a n d o th e r s u p p le me n ta r y s e r v ic e a n d A N F s 8.6.1 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 ) 8.6.2 C o mp l e t i o n o f C a l l s t o B u s y S u b s c r i b e r s ( S S - C C B S ) 8.6.3 Co mp le tio n o f Ca lls o n N o Re p ly ( S S - CCN R) 8.6.4 Call Transfer (SS-CT) 8.6.5 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 ) 8.6.6 C a l l F o r w a r d in g B u s y ( S S - C F B ) 8.6.7 Ca ll F o r w a r d in g N o Re p ly ( S S - CF N R) 8.6.8 Call Deflection (SS-CD) 8.6.9 P a t h R e p l a c e me n t ( A N F - P R )
9 9 9 9 10 10 10 10 11 11 11 12 12 12 12 12 12 12 12 12 12 12
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
13
Annex B - Specification and Description Language (SDL) Representation
19
A n n e x C - 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
25
1
Scope This Standard specifies the signalling protocol for the support of name identification supplementary services at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). The name identification supplementary services are Calling Name Identification Presentation (SS-CNIP) and Connected Name Identification Presentation (SS-CONP). Calling Name Identification Presentation (CNIP) is a supplementary service which is offered to the called user and which provides the name of the calling user (calling party name) to the called user. Connected Name Identification Presentation (CONP) is a supplementary service which is offered to the calling user and which provides to the calling user the following: − the name of the user who answers the call (connected party name); − optionally the name of the alerting user (called party name); − optionally the name of the called user who cannot be reached (busy party name). The supplementary service Calling/connected Name Identification Restriction (CNIR) has no impact on the signalling at Q reference point. Provision of a user's name to the PISN is outside the scope of this Standard. The Q reference point is defined in ECMA-133. Service specifications are produced in three stages 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-163. The signalling protocol for SS-CNIP and SS-CONP 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 Q reference point between name identification supplementary services and other supplementary services and ANFs. This Standard is applicable to PINXs which can be interconnected 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.
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-142
Private Integrated Services Network (PISN) - Circuit-mode 64 kbit/s Bearer Services Service Description, Functional Capabilities and Information Flows (International Standard ISO/IEC 11574)
ECMA-143
Private Integrated Services Network (PISN) - Circuit-mode Bearer Services - InterExchange Signalling Procedures and Protocol (International Standard ISO/IEC 11572)
- 2 -
ECMA-163
Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Name Identification Supplementary Services (International Standard ISO/IEC 13864)
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-174
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Diversion Supplementary Services (International Standard ISO/IEC 13873)
ECMA-178
Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - Call Transfer Supplementary Service (International Standard ISO/IEC 13869)
ISO 8859-1
Information processing - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet No.1 (1987)
ISO 8859-2
Information processing - 8-bit single-byte coded graphic character sets - Part 2: Latin alphabet No. 2 (1987)
ISO 8859-3
Information processing - 8-bit single-byte coded graphic character sets - Part 3: Latin alphabet No. 3 (1988)
ISO 8859-4
Information processing - 8-bit single-byte coded graphic character sets - Part 4: Latin alphabet No.4 (1988)
ISO 8859-5
Information processing - 8-bit single-byte coded graphic character sets - Part 5: Latin/Cyrillic alphabet (1988)
ISO 8859-7
Information processing - 8-bit single-byte coded graphic character sets - Part 7: Latin/Greek alphabet (1987)
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)
ITU-T Rec. I.210
Principles of telecommunication services supported by an ISDN and the means to describe them (1993)
ITU-T Rec. Z.100 Specification and description language (1999) ANSI T1.641-1995 American National Standard for Telecommunications - Calling Name Identification Presentation
4
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)
− Basic Service
(ITU-T Rec. I.210)
− Call, Basic Call
(ECMA-165)
− Coordination Function
(ECMA-165)
− Incoming Gateway PINX
(ECMA-143)
− Integrated Services Digital Network
(ITU-T Rec. I.112)
− Originating PINX
(ECMA-143)
- 3 -
4.2
− Outgoing Gateway PINX
(ECMA-143)
− Private Integrated Services Network (PISN)
(ECMA-133)
− Private Integrated services Network eXchange (PINX)
(ECMA-133)
− Signalling
(ITU-T Rec. I.112)
− Supplementary Service
(ITU-T Rec. I.210)
− Supplementary Service Control Entity
(ECMA-165)
− Terminating PINX
(ECMA-143)
− Transit PINX
(ECMA-143)
− User
(ECMA-142)
Name A string of maximum 50 characters which is used for the name identification of the PISN user of a call.
5
Acronyms APDU
Application Protocol Data Unit
ASN.1
Abstract Syntax Notation One
ISDN
Integrated Services Digital Network
NFE
Network Facility Extension
PICS
Protocol Implementation Conformance Statement
PISN
Private Integrated Services Network
PINX
Private Integrated services Network eXchange
SDL
Specification and Description Language
SSCE
Supplementary Service Control Entity
SS-CNIP
Calling Name Identification Presentation supplementary service
SS-CONP
Connected Name Identification Presentation supplementary service
- 4 -
6 6.1
SS-CNIP and SS-CONP Coding Requirements 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 C. Table 1 - Operations in Support of SS-CNIP and SS-CONP
Name-Operations-asn1-97 { iso ( 1) standard ( 0) pss1-name (13868) name-operations-asn1-97( 1) } DEFINITIONS ::= BEGIN IMPORTS OPERATION
FROM Remote-Operations-Information-Objects {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)}
EXTENSION, Extension{} FROM Manufacturer-specific-service-extension-class-asn1-97 { iso standard pss1-generic-procedures (11582) msi-class-asn1-97 ( 11) }; Name-Operations OPERATION ::= { callingName | calledName | connectedName | busyName } callingName
OPERATION ::= { ARGUMENT RETURN RESULT ALWAYS RESPONDS CODE }
NameArg FALSE FALSE local: 0
OPERATION ::= { ARGUMENT RETURN RESULT ALWAYS RESPONDS CODE }
NameArg FALSE FALSE local: 1
connectedName OPERATION ::= { ARGUMENT RETURN RESULT ALWAYS RESPONDS CODE }
NameArg FALSE FALSE local: 2
calledName
busyName
OPERATION ::= { ARGUMENT RETURN RESULT ALWAYS RESPONDS CODE }
NameArg FALSE FALSE local: 3
- 5 -
Table 1 - Operations in Support of SS-CNIP and SS-CONP (continued) NameArg
::=
CHOICE { name Name, nameSequence SEQUENCE { name Name, extension NameExtension OPTIONAL } }
NameExtension ::=
CHOICE { single [5] IMPLICIT Extension{{NameExtensionSet}}, multiple [6] IMPLICIT SEQUENCE OF Extension{{NameExtensionSet}} }
NameExtensionSet
EXTENSION ::= {...}
Name
::= CHOICE {
namePresentationAllowed namePresentationRestricted nameNotAvailable
NamePresentationAllowed, NamePresentationRestricted, NameNotAvailable }
NamePresentationAllowed ::= CHOICE { namePresentationAllowedSimple [0] IMPLICIT NameData, namePresentationAllowedExtended [1] IMPLICIT NameSet } -- iso8859-1 is implied in namePresentationAllowedSimple. NamePresentationRestricted ::= CHOICE { namePresentationRestrictedSimple [2] IMPLICIT NameData, namePresentationRestrictedExtended [3] IMPLICIT NameSet, namePresentationRestrictedNull [7] IMPLICIT NULL} -- iso8859-1 is implied in namePresentationRestrictedSimple. -- namePresentationRestrictedNull shall only be used in the -- case of interworking where the other network provides an -- indication that the name is restricted without the name itself. NameNotAvailable
::= [4] IMPLICIT NULL
NameData
::= OCTET STRING (SIZE (1..50)) -- The maximum allowed size of the name field is 50 octets. -- The minimum required size of the name field is 1 octet.
NameSet
::= SEQUENCE { nameData NameData, characterSet CharacterSet OPTIONAL } -- If characterSet is not included, iso8859-1 is implied.
CharacterSet
::= INTEGER { unknown (0), iso8859-1 (1), -- The character set "iso8859-1" is specified in International -- Standard ISO 8859-1 -- The value 2 was assigned for CCITT Rec. T.61 -- which has been withdrawn by ITU-T. iso8859-2 (3), -- The character set “iso8859-2” is specified in International -- Standard ISO 8859-2
- 6 -
Table 1 - Operations in Support of SS-CNIP and SS-CONP (concluded) iso8859-3 (4), --The character set “iso8859-3” is specified in International -- Standard ISO 8859-3 iso8859-4 (5), --The character set “iso8859-4” is specified in International -- Standard ISO 8859-4 iso8859-5 (6), --The character set “iso8859-5” is specified in International -- Standard ISO 8859-5 iso8859-7 (7), --The character set “iso8859-7” is specified in International -- Standard ISO 8859-7 iso10646-BmpString (8), -- The character set “iso10646-BmpString” is specified in International -- Standard ISO 10646-1 and in ITU-T Rec. X.680 -- with this character set, each character occupies 2 octets in NameData iso10646-utf-8String (9) -- The character set “iso10646-utf-8String” is specified in International -- Standard ISO 10646-1 -- UTF-8-String is defined in Annex R of ISO 10646-1 -- with this character set, each character occupies a variable -- number of octets (1…6) in NameData } (0..255) -- Other character sets might be added in further editions of -- this Standard END
6.2
-- of Name-Operations-asn1-97
Information Elements The operations defined in 6.1 for the support of SS-CNIP and SS-CONP shall be coded in the Facility information element in accordance with ECMA-165. When conveying the invoke APDU of the operations defined in 6.1, the destinationEntity data element of the NFE shall contain value endPINX. The Interpretation APDU in the Facility information element shall be included and shall have the value "discardAnyUnrecognisedInvokeAPDU (0)".
6.3
Messages Basic call messages ALERTING, CONNECT, DISCONNECT, FACILITY, RELEASE, RELEASE COMPLETE, PROGRESS and SETUP shall be used for conveying the Facility information element in support of SS-CNIP and SS-CONP as specified in ECMA-165.
7 7.1
Signalling Protocol for the Support of SS-CNIP SS-CNIP Description Calling Name Identification Presentation (SS-CNIP) is a supplementary service which is offered to the called user and which provides the name of the calling user to the called user. The PISN provides the calling user's name and delivers the calling user's name to the called user whenever an incoming call is presented. The presentation of the calling user's name may be restricted as specified in SS-CNIR. Some users may have a service profile which permits the override of calling name identification restriction. This supplementary service is applicable to all basic services, defined in ECMA-142.
- 7 -
7.2
SS-CNIP Operational Requirements
7.2.1
Requirements on the Originating PINX and the Incoming Gateway PINX Call establishment procedures, as specified in ECMA-143, shall apply. Additionally, these PINXs shall be responsible for obtaining the name information. An Originating PINX may limit, to less than 50, the number of characters that can be registered against a user. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Source PINX, shall apply.
7.2.2
R e q u i r e m e n t s o n t h e T e r m i n a t i n g P IN X a n d t h e O u t g o i n g G a t e w a y P I N X Call establishment procedures, as specified in ECMA-143, shall apply. Additionally, these PINXs shall be responsible for delivering the name information to the user or to the other network. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Destination PINX, shall apply.
7.2.3
Requirements on a Transit PINX Call establishment procedures, as specified in ECMA-143, shall apply. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply.
7.3
SS-CNIP State Definitions No specific state definitions are required.
7.4
SS-CNIP Signalling Procedures for Invocation and Operation
7.4.1 A c t io n s a t t h e O r ig in a t in g P I N X 7.4.1.1 Normal procedures If the calling user's name is available and presentation is allowed, the callingName invoke APDU shall be sent in the SETUP message from the Originating PINX to the Terminating PINX. Within the argument, the NamePresentationAllowed type shall be chosen for the element of type Name. If the calling user's name is available and presentation is restricted, the callingName invoke APDU shall also be sent in the SETUP message from the Originating PINX to the Terminating PINX. Within the argument, the NamePresentationRestricted type shall be chosen for the element of type Name. If the calling user's name is not available, the callingName invoke APDU may be sent in the SETUP message from the Originating PINX to the Terminating PINX. Within the argument, the NameNotAvailable type shall be chosen for the element of type Name. 7.4.1.2
Ex c e p t io n a l p r o c e d u r e s Not applicable.
7.4.2 Actions at the Terminating PINX 7.4.2.1 Normal procedures If the callingName invoke APDU has been received with an element of type NamePresentationAllowed in the argument, the name information including the presentation indicator shall be delivered to the called user if able and authorized to receive the calling name information If the callingName invoke APDU has been received with an element of type NamePresentationRestricted in the argument, no name information other than the presentation indictor shall be delivered to the called user, unless the called user has an override capability. If either the callingName invoke APDU has not been received or the callingName invoke APDU has been received with an element of type NameNotAvailable in the argument, no name information other than the presentation indicator "name not available" shall be delivered to the called user. 7.4.2.2
Ex c e p t io n a l p r o c e d u r e s Not applicable.
- 8 -
7.4.3
7.5 7.5.1
A c t io n s a t a Tr a n s it P I N X No special actions are required in support of SS-CNIP.
SS-CNIP Impact of Interworking with Public ISDNs or with Non-ISDNs A c t io n s a t t h e I n c o m in g G a t e wa y P I N X On calls incoming from another network, if the other network provides the calling user's name information, it shall be sent to the Terminating PINX as specified in 7.4.1 (the Incoming Gateway PINX thereby acting as an Originating PINX). If the other network does not provide the calling user name, but provide an indication that the calling user name is restricted, the incoming gateway PINX shall include the callingName invoke APDU in the SETUP message sent to the Terminating PINX. Within the argument, choice namePresentationRestrictedNull of type NamePresentationRestricted shall be chosen for the element of type Name. If the number of characters in the calling party name exceeds 50, the PINX shall truncate the excess characters. A public network may send delayed calling user’s name information (e.g. in a FACILITY message subsequent to sending the SETUP message when conforming to ANSI T1.641-1995). In this case, the Incoming Gateway PINX may include the name information in a callingName invoke APDU in a FACILITY message and send it to the Terminating PINX, after the first backwards end-to-end message (i.e. ALERTING, PROGRESS or CONNECT) has been received. As defined in 6.2, the Interpretation APDU shall be included in the Facility information element in that FACILITY message and shall have the value “discardAnyUnrecognisedInvokeAPDU (0)”.
7.5.2
7.6
A c t io n s a t t h e O u t g o in g G a t e wa y P I N X On outgoing calls to another network, the PISN shall deliver the calling user's name information to the other network as specified in 7.4.2 (the Outgoing Gateway PINX thereby acting as a Terminating PINX), if the other network supports an equivalent supplementary service.
Protocol interactions between SS-CNIP 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 1 Simultaneous conveyance of APDUs for SS-CNIP 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. NOTE 2 Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications.
7.6.1
Connected Name Identification Presentation (SS-CONP) No protocol interaction.
7.6.2
Completion of Calls to Busy Subscribers (SS-CCBS) No protocol interaction.
7.6.3
Completion of Calls on No Reply (SS-CCNR) No protocol interaction.
7.6.4
C a ll Tr a n s f e r ( S S - C T) Protocol interactions are specified in ECMA-178.
7.6.5
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 ) Protocol interactions are specified in ECMA-174.
- 9 -
7.6.6
C a ll F o r wa r d in g Bu s y ( S S - C F B) Protocol interactions are specified in ECMA-174.
7.6.7
C a l l F o r wa r d i n g N o R e p l y ( S S - C F N R ) Protocol interactions are specified in ECMA-174.
7.6.8
Call Deflection (SS-CD) The protocol interactions with Call Deflection Immediate shall be as specified in 7.6.5 for interaction with SS-CFU. The protocol interactions with Call Deflection from Alert shall be as specified in 7.6.7 for interaction with SS-CFNR.
7.6.9
8
Path Replacement (ANF-PR) No protocol interaction.
Signalling Protocol for the Support of SS-CONP
8.1
SS-CONP General Description Connected Name identification Presentation (SS-CONP) is a supplementary service which is offered to the calling user and which provides to the calling user the following: -
the name of the user that answers the call;
-
optionally the name of the alerting user;
-
optionally the name of the called user that cannot be reached.
The PISN provides the connected user's name and delivers the connected user's name to the calling user whenever an incoming call is answered by the called user. Optionally, the PISN provides the name of the busy user and delivers the name to the calling user whenever the called user cannot be reached because of a busy condition. Optionally, the PISN provides the name of the alerted user and delivers the name to the calling user whenever an incoming call commences alerting at the called user. The presentation of the connected user's name, busy user's name and alerted user's name may be restricted as specified in SS-CNIR. Some users may have a service profile which permits the override of connected name identification restriction. This supplementary service is applicable to all basic services defined in ECMA-142.
8.2 8.2.1
SS-CONP Operational Requirements R e q u i r e m e n t s o n t h e T e r m i n a t i n g P IN X a n d t h e O u t g o i n g G a t e w a y P I N X Call establishment procedures and the call release procedures, as specified in ECMA-143, shall apply. Additionally, these PINXs shall be responsible for obtaining the name information. A Terminating PINX may limit, to less than 50, the number of characters that can be registered against a user. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Source PINX, shall apply.
8.2.2
Requirements on the Originating PINX and the Incoming Gateway PINX Call establishment procedures and the call release procedures, as specified in ECMA-143, shall apply. Additionally, these PINXs shall be responsible for delivering the name information to the user or to the other network. Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Destination PINX, shall apply.
8.2.3
Requirements on a Transit PINX Call establishment and release procedures, as specified in ECMA-143, shall apply.
- 10 -
Generic procedures for the call related control of supplementary services, as specified in ECMA-165 for a Transit PINX, shall apply.
8.3
SS-CONP State Definitions No specific state definitions are required.
8.4
SS-CONP Signalling Procedures for Invocation and Operation
8.4.1 Actions at the Terminating PINX 8.4.1.1 Normal procedures When an incoming call is answered by the called user and the connected user's name is available and presentation is allowed, the connectedName invoke APDU shall be sent in the CONNECT message from the Terminating PINX to the Originating PINX. Within the argument, the NamePresentationAllowed type shall be chosen for the element of type Name. When the called user cannot be reached because of a busy condition and the called user's name is available and presentation is allowed, the busyName invoke APDU may be sent in the message that indicates the busy condition. Within the argument, the NamePresentationAllowed type shall be chosen for the element of type Name. When an incoming call commences alerting at the called user and the called user's name is available and presentation is allowed, the calledName invoke APDU may be sent in the ALERTING message from the Terminating PINX to the Originating PINX. Within the argument, the NamePresentationAllowed type shall be chosen for the element of type Name. When an incoming call is answered by the called user and the connected user's name is available and presentation is restricted, the connectedName invoke APDU shall be sent in the CONNECT message from the Terminating PINX to the Originating PINX. Within the argument, the NamePresentationRestricted type shall be chosen for the element of type Name. When the called user cannot be reached because of a busy condition and the called user's name is available and presentation is restricted, the busyName invoke APDU may be sent in the message that indicates the busy condition. Within the argument, the NamePresentationRestricted type shall be chosen for the element of type Name. When an incoming call commences alerting at the called user and the called user's name is available and presentation is restricted, the calledName invoke APDU may be sent in the ALERTING message from the Terminating PINX to the Originating PINX. Within the argument, the NamePresentationRestricted type shall be chosen for the element of type Name. When an incoming call is answered by the called user and the connected user's name is not available, the connectedName invoke APDU may be sent in the CONNECT message from the Terminating PINX to the Originating PINX. Within the argument, the NameNotAvailable type shall be chosen for the element of type Name. When the called user cannot be reached because of a busy condition and the called user's name is not available, the busyName invoke APDU may be sent in the message that indicates the busy condition. Within the argument, the NameNotAvailable type shall be chosen for the element of type Name. When an incoming call commences alerting at the called user and the called user's name is not available, the calledName invoke APDU may be sent in the ALERTING message from the Terminating PINX to the Originating PINX. Within the argument, the NameNotAvailable type shall be chosen for the element of type Name. 8.4.1.2
Ex c e p t io n a l p r o c e d u r e s Not applicable.
8.4.2 A c t io n s a t t h e O r ig in a t in g P I N X 8.4.2.1 Normal procedures If the connectedName invoke APDU has been received in the CONNECT message with an element of type NamePresentationAllowed in the argument, the name information including the presentation
- 11 -
indicator shall be delivered to the calling user if able and authorized to receive the connected name information. If the busyName invoke APDU has been received in the messages that indicates the busy condition. with an element of type NamePresentationAllowed in the argument, the name information including the presentation indicator may be delivered to the calling user if able and authorized to receive the connected name information. If the calledName invoke APDU has been received in the ALERTING message with an element of type NamePresentationAllowed in the argument, the name information including the presentation indicator may be delivered to the calling user if able and authorized to receive the connected name information. If the connectedName invoke APDU has been received in the CONNECT message with an element of type NamePresentationRestricted in the argument, no name information other than the presentation indicator shall be delivered to the calling user, unless the calling user has an override capability. If the busyName invoke APDU has been received in the messages that indicates the busy condition with an element of type NamePresentationRestricted in the argument, no name information other than the presentation indicator may be delivered to the calling user, unless the calling user has an override capability. If the calledName invoke APDU has been received in the ALERTING message with an element of type NamePresentationRestricted in the argument, no name information other than the presentation indicator may be delivered to the calling user, unless the calling user has an override capability. If either the connectedName invoke APDU has not been received in the CONNECT message or the connectedName invoke APDU has been received in the CONNECT message with an element of type NameNotAvailable in the argument, no name information other than the presentation indicator "name not available" shall be delivered to the calling user. If either calledName invoke APDU has not been received in the ALERTING message or the calledName invoke APDU has been received in the ALERTING message with an element of type NameNotAvailable in the argument, only the presentation indicator "name not available" may be delivered to the calling user. If either the busyName invoke APDU has not been received in the messages that indicates the busy condition or the busyName invoke APDU has been received in the DISCONNECT message with an element of type NameNotAvailable in the argument, only the presentation indicator "name not available" may be delivered to the calling user. 8.4.2.2 8.4.3
8.5 8.5.1
Ex c e p t io n a l p r o c e d u r e s Not applicable. A c t io n s a t a Tr a n s it P I N X No special actions are required in support of SS-CONP.
SS-CONP Impact of Interworking with Public ISDNs or with Non-ISDNs A c t io n s a t t h e O u t g o in g G a t e wa y P I N X On outgoing calls to another network, if the other network provides the name of the user who has answered the call and the name of the alerted user or the name of the user who cannot be reached, it shall be sent to the Originating PINX as specified in 8.4.1 (the Outgoing Gateway PINX thereby acting as a Terminating PINX). If the other network does not provide the name information of the user who has answered the call, of the alerted user, or of the user who cannot be reached, but provides an indication that the name is restricted, the Outgoing Gateway PINX shall include the appropriate name invoke APDU (connectedName, calledName or busyName) in the appropriate call control message sent to the Originating PINX. Within the argument, choice namePresentationRestrictedNull of type NamePresentationRestricted shall be chosen for the element of type Name. If the number of characters in the connected/called/busy party name exceeds 50, the PINX shall truncate the excess characters.
- 12 -
8.5.2
8.6
A c t io n s a t t h e I n c o m in g G a t e wa y P I N X On calls incoming from another network, the PISN shall deliver the name of the user who has answered the call and the name of the alerted user or the name of the user who cannot be reached, to the other network as specified in 8.4.2 (The Incoming Gateway PINX thereby acting as an Originating PINX), if this network supports an equivalent supplementary service.
Protocol Interaction between SS-CONP and other supplementary service 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 1 Simultaneous conveyance of APDUs for SS-CONP and another supplementary service of or ANF in the same message, each in accordance with the requirements of its respective stage 3 standards, does not, on its own, constitute a protocol interaction. NOTE 2 Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the reverent stage 1 specification.
8.6.1
Calling Name Identification Presentation (SS-CNIP) No protocol interaction.
8.6.2
Completion of Calls to Busy Subscribers (SS-CCBS) No protocol interaction.
8.6.3
Completion of Calls on No Reply (SS-CCNR) No protocol interaction.
8.6.4
C a ll Tr a n s f e r ( S S - C T) Protocol interactions are specified in ECMA-178.
8.6.5
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 ) Protocol interactions are specified in ECMA-174.
8.6.6
C a ll F o r wa r d in g Bu s y ( S S - C F B) Protocol interactions are specified in ECMA-174.
8.6.7
C a l l F o r wa r d i n g N o R e p l y ( S S - C F N R ) Protocol interactions are specified in ECMA-174.
8.6.8
Call Deflection (SS-CD) The protocol interactions with Call Deflection Immediate shall be as specified in 7.6.5 for interaction with SS-CFU. The protocol interactions with Call Deflection from Alert shall be as specified in 7.6.7 for interaction with SS-CFNR.
8.6.9
Path Replacement (ANF-PR) No protocol interaction.
- 13 -
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 Protocol Implementation Conformance Statement (PICS) proforma in A.3. 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:
A.2
-
by a 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 PICS proforma;
-
by user (or potential user) of the implementation, as a basis for initially checking the possibility of interworking with another implementation (note that, while interworking cannot be guaranteed, failure to interwork can often be predicted from incompatible PICS);
-
by a protocol tester, as the basis for selecting appropriate tests against which to assess the claim for conformance of the implementation.
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 subclauses 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).
- 14 -
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 requirements. 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.
- 15 -
A.3
PICS proforma for ECMA-164
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 supplier's 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.)
- 16 -
A.3.3
Supplementary Services
Item
Name of Item
Reference
Status
N/A
Support
A1
Support of SS-CNIP
7
o.1
Yes [ ] No [ ]
A2
Support of SS-CONP
8
o.1
Yes [ ] No [ ]
Reference
Status
A.3.4
Procedures for SS-CNIP
Item
Name of Item
N/A
Support
B1
Procedures at the Originating PINX
7.4.1
A1:o.2
Yes [ ] No [ ]
B2
Procedures at the Terminating PINX
7.4.2
A1:o.2
Yes [ ] No [ ]
B3
Procedures at the Incoming Gateway PINX
7.5.1
A1:o.2
Yes [ ] No [ ]
B4
Procedures at the Outgoing Gateway PINX
7.5.2
A1:o.2
Yes [ ] No [ ]
B5
Encoding of the callingName APDU
6
A1:m
Yes [ ]
B6
Sending of the callingName APDU in SETUP
6, 7.4.1
c.1
[]
Yes [ ]
B7
Receipt of callingName APDU in SETUP
6, 7.4.2
c.2
[]
Yes [ ]
B8
Sending of character set number
6.1
c.3
[]
Yes [ ] No [ ]
B9
Sending of callingName APDU in FACILITY
7.5.1
B3: o
[]
Yes [ ] No [ ]
B10
Receipt of callingName APDU in FACILITY
7.4.2
B2: o
[]
Yes [ ] No [ ]
c.1:
if B1 or B3 then m else N/A
c.2
if B2 or B4 then m else N/A
c.3
if B1 or B3 then o else N/A
- 17 -
A.3.5
Procedures for SS-CONP
Item
Name of Item
Reference
Status
N/A
Support
C1
Procedures at the Terminating PINX
8.4.1
A2:o.3
Yes [ ] No [ ]
C2
Procedures at the Originating PINX
8.4.2
A2:o.3
Yes [ ] No [ ]
C3
Procedures at the Outgoing Gateway PINX
8.5.1
A2:o.3
Yes [ ] No [ ]
C4
Procedures at the Incoming Gateway PINX
8.5.2
A2:o.3
Yes [ ] No [ ]
C5
Encoding of connectedName APDU
6
A2:m
Yes [ ]
C6
Encoding of busyName APDU
6
A2:o
Yes [ ] No [ ]
C7
Encoding of calledName APDU
6
A2:o
Yes [ ] No [ ]
C8
Sending of connectedName APDU in CONNECT
6, 8.4.1
c.1
[]
Yes [ ]
C9
Receipt of connectedName APDU in CONNECT
6, 8.4.2
c.2
[]
Yes [ ]
C10
Sending of busyName APDU in DISCONNECT
6, 8.4.1
c.3
[]
Yes [ ] No [ ]
C11
Receipt of busyName APDU in DISCONNECT
6, 8.4.2
c.4
[]
Yes [ ] No [ ]
C12
Sending of calledName APDU in ALERTING
6, 8.4.1
c.3
[]
Yes [ ] No [ ]
C13
Receipt of calledName APDU in ALERTING
6, 8.4.3
c.4
[]
Yes [ ] No [ ]
C14
Sending of character set number
6.1
c.3
[]
Yes [ ] No [ ]
c.1:
if C1 or C3 then m else N/A
c.2:
if C2 or C4 then m else N/A
c3:
if C1 or C3 then o else N/A
c4:
if C2 or C4 then o else N/A
- 18 -
- 19 -
Annex B ( in f o r ma tiv e )
Specification and Description Language (SDL) Representation
The diagrams in this annex use the Specification and Description Language defined in ITU-T Rec. Z.100 (1999). Each diagram represents the behavior of an SS-CNIP or SS-CONP Supplementary Service Control entity at a particular type of PINX. In accordance with the protocol model described in CD 11582, the Supplementary Service Control entity uses, via the Coordination Function, the services of Generic Functional Procedures Control and Basic Call Control. Where an output symbol represents a primitive to the Coordination Function, and that primitive results in a layer 3 message being sent, the output bears the name of the message and any remote operations APDU(s) or notification(s) contained in that message. In case of a message specified in DIS 11572, basic call actions associated with the sending of that message are deemed to occur.
B.1
SDL Representation of SS-CNIP Figure B.1 shows the behavior of an SS-CNIP Supplementary Service Control entity within the Originating PINX. Figure B.2 shows the behavior of an SS-CNIP Supplementary Service Control entity within the Terminating PINX. In figure B.1 output signals to the right represent messages sent via the outgoing side protocol control and input signals from the left represent primitives from the SSCE user. In figure B.2 output signals to the right represent primitives to the SSCE user and input signals from the left represent messages received via the incoming side protocol control.
- 20 -
CNIP-S-Idle
CNIP request detected
obtain name, if available, and presentation indicator
name available ?
NO
YES
include in SETUP callingName invoke APDU
CNIP-S-Idle
F ig u r e B. 1 - S D L R e p r e s e n t a t io n o f S S - C N I P a t t h e O r ig in a t in g P I N X
- 21 -
CNIP-D-Idle
SETUP with callingName invoke APDU
NO
name available ?
NO
presentation restricted ?
SETUP without callingName invoke APDU
YES
YES
include name
include presentation indicator
CNIP indication NOTE - Override of presentation restriction is implementation specific and outside the scope of this Standard CNIP-D-Idle
Figure B.2 - SDL Representation of SS-CNIP at the Terminating PINX
- 22 -
B.2
SDL Representation of SS-CONP Figure B.3 shows the behavior of an SS-CONP Supplementary Service Control entity within the Terminating PINX. Figure B.4 shows the behavior of an SS-CNIP Supplementary Service Control entity within the Originating PINX. In figure B.3 output signals to the left represent messages sent via the incoming side protocol control and input signals from the right represent primitives from the SSCE user. In figure B.4 output signals to the left represent primitives to the SSCE user and input signals from the right represent messages received via the outgoing side protocol control.
- 23 -
CONP-S-Idle
CONP request detected
obtain name, if available, and presentation indicator
name available ?
NO
YES
user answering include in CONNECT: connectedName invoke APDU
user alerting include in ALERTING: calledName invoke APDU
user busy include in DISCONNECT busyName invoke APDU
CONP-S-Idle
Figure B.3 - SDL Representation of SS-CONP at the Terminating PINX
- 24 -
CONP-D-Idle
CONNECT with connectedName invoke APDU
ALERTING with calledName invoke APDU
NO
name available ?
presentation restricted ?
DISCONNECT with busyName invoke APDU
YES
CONNECT without connectedName invoke APDU
YES
ALERTING without calledName invoke APDU
DISCONNECT without busyName invoke APDU
NO include name
include presentation indicator
CNIP indication
NOTE - Override presentation restriction is implementation specific and outside the scope of this Standard.
CONP-D-Idle
F ig u r e B. 4 - S D L R e p r e s e n t a t io n o f S S - C O N P a t t h e O r ig in a t in g P I N X
- 25 -
Annex C ( 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 third edition of ECMA-164, i.e. based on ITU-T Recommendations X.208 / X.209. Starting with the fourth edition the ASN.1 modules within ECMA-164 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 C . 1 - N a m e - 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 Name-Operations { iso ( 1) standard ( 0) pss1-name (13868) name-operations( 0) } DEFINITIONS ::= BEGIN EXPORTS
Name, NameSet;
IMPORTS OPERATION, ERROR
FROM
Extension
FROM
Remote-Operation-Notation { joint-iso-ccitt( 2) remote-operations( 4) notation( 0) } Manufacturer-specific-service-extension-definition { iso standard pss1-generic-procedures (11582) msi-definition ( 0) };
CallingName ::= OPERATION ARGUMENT CHOICE { Name, SEQUENCE {Name, CHOICE { [5] IMPLICIT Extension, [6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }} CalledName ::= OPERATION ARGUMENT CHOICE { Name, SEQUENCE {Name, CHOICE { [5] IMPLICIT Extension, [6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }}
- 26 -
Ta b le C . 1 - N a m e - 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 t in u e d ) ConnectedName ::=
OPERATION ARGUMENT CHOICE { Name, SEQUENCE {Name, CHOICE { [5] IMPLICIT Extension, [6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }}
BusyName ::=
OPERATION ARGUMENT CHOICE { Name, SEQUENCE {Name, CHOICE { [5] IMPLICIT Extension, [6] IMPLICIT SEQUENCE OF Extension } OPTIONAL }}
Name
::= CHOICE {
NamePresentationAllowed, NamePresentationRestricted, NameNotAvailable }
NamePresentationAllowed ::= CHOICE {
namePresentationAllowedSimple [0] IMPLICIT NameData, namePresentationAllowedExtended [1] IMPLICIT NameSet } -- iso8859-1 is implied in namePresentationAllowedSimple.
NamePresentationRestricted ::= CHOICE {
namePresentationRestrictedSimple [2] IMPLICIT NameData, namePresentationRestrictedExtended [3] IMPLICIT NameSet, namePresentationRestrictedNull [7] IMPLICIT NULL} -- iso8859-1 is implied in namePresentationRestrictedSimple. -- namePresentationRestrictedNull shall only be used in the -- case of interworking where the other network provides an -- indication that the name is restricted without the name itself.
NameNotAvailable ::= [4] IMPLICIT NULL NameData
::= OCTET STRING (SIZE (1..50)) -- The maximum allowed size of the name field is 50 octets. -- The minimum required size of the name field is 1 octet.
NameSet
::= SEQUENCE { nameData NameData, characterSet CharacterSet OPTIONAL } -- If characterSet is not included, iso8859-1 is implied.
- 27 -
Ta b le C . 1 - N a m e - 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 ) CharacterSet
::= INTEGER {
unknown (0), iso8859-1 (1), -- The value 2 was assigned for CCITT Rec. T.61 -- which has been withdrawn by ITU-T. iso8859-2 (3), iso8859-3 (4), iso8859-4 (5), iso8859-5 (6), iso8859-7 (7), iso10646-BmpString (8), iso10646-utf-8String (9) } (0..255) -- The character set "iso8859-1" is specified in International -- Standard ISO 8859-1 -- The character set “iso8859-2” is specified in International -- Standard ISO 8859-2 --The character set “iso8859-3” is specified in International -- Standard ISO 8859-3 --The character set “iso8859-4” is specified in International -- Standard ISO 8859-4 --The character set “iso8859-5” is specified in International -- Standard ISO 8859-5 --The character set “iso8859-7” is specified in International -- Standard ISO 8859-7 -- Other character sets might be added in further editions of -- this Standard -- The character set “iso10646-BmpString” is specified in International -- Standard ISO 10646-1 and in ITU-T Rec. X.680 -- with this character set, each character occupies 2 octets -- in NameData -- The character set “iso10646-utf-8String” is specified in International -- Standard ISO 10646-1 -- UTF-8-String is defined in Annex R of ISO 10646-1 -- with this character set, each character occupies a variable -- number of octets (1…6) in NameData
callingName calledName connectedName busyName
CallingName CalledName ConnectedName BusyName
END
-- of name operations
::= localValue 0 ::= localValue 1 ::= localValue 2 ::= localValue 3
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.