Conceptio › Archive › ECMA International

ECMA Internationalopen access

ECMA-242 — Private Integrated Services Network (PISN) - Inter-exchange signalling protocol - Message waiting indication supplementary service (QSIG-MWI) (December 2001)

ECMA International · ECMA International

ECMA International · Standards · License: Open Access

ecma ecmainternational exchange integrated inter message network pisn

ecma, standard, ecma international, specification, ecma-242, ecma 242, 242, private, integrated, services, network, pisn, inter-exchange, signalling, protocol, message, waiting, indication, supplementary, service, qsig-mwi

S tandard ECMA-242

4th Edition - December 2001

Standardizing Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Message Waiting Indication Supplementary Service

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected]

Draft S tandard ECMA-242

4th Edition - December 2001

Standardizing Information

and

Communication

Systems

Private Integrated Services Network (PISN) Inter-Exchange Signalling Protocol Message Waiting Indication Supplementary Service (QSIG-MWI)

Phone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http://www.ecma.ch - Internet: [email protected] IW

Ecma-242.doc

14-01-02 10,13

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 Message Waiting Indication 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 2nd Edition of Standard ECMA-242 (published by ECMA in September 1997), the 3rd Edition incorporated changes to allow indication of multimedia messages. Compared to the 3rd Edition of Standard ECMA-242 (published by ECMA in December 1998), this 4th Edition incorporates migration to ASN.1 version 1997 as well as changes in order to achieve complete alignment with International Standard ISO/IEC 15506:2000(E) published by ISO/IEC in March 2000.

Adopted as 4th Edition of Standard ECMA-242 by the General Assembly of December 2001.

- i -

Table of contents 1

Scope

Conformance

References (normative)

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 Me s s a g e Ce n tr e P I N X 4.2.2 Served User 4.2.3 Me s s a g e Ce n tr e 4.2.4 Me s s a g e W a itin g I n d ic a tio n

2 2 2 2 2 2 2

5 6

List of acronyms Signalling protocol for the support of SS-MWI 6 . 1 S S - MW I d e s c r ip tio n 6 . 2 S S - MW I 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 Me s s a g e Ce n tr e P I N X 6.2.2 Re q u ir e me n ts o n a S e r v e d 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 - MW I 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 - MW I s ta te d e f in itio n s 6.4.1 States at the Message Centre PINX 6.4.2 States at the Served User PINX 6 . 5 S S - MW I s ig n a llin g p r o c e d u r e s 6.5.1 A c tio n s a t th e Me s s a g e Ce n tr e P I N X 6.5.2 Actions at the Served User PINX 6.5.3 Actions at a Transit PINX 6 . 6 S S - MW I 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 - MW I 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 . 8 P r o to c o l in te r a c tio n s b e tw e e n S S - MW I 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 I n te r a c tio n w ith A d v ic e O f Ch a r g e ( S S - A O C) 6.8.2 Interaction with Call Deflection (SS-CD) 6.8.3 I n te r a c tio n w ith 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.4 I n t e r a c t i o n w i t h C a l l F o r w a r d in g B u s y ( S S - C F B ) 6.8.5 I n te r a c tio n w ith Ca ll F o r w a r d in g N o Re p ly ( S S - CF N R) 6.8.6 Interaction with Call Interception (ANF-CINT) 6.8.7 Interaction with Call Intrusion (SS-CI)

2 3 3 3 3 3 3 4 4 8 8 8 8 8 8 9 10 10 10 11 11 11 11 11 11 11 11 11 11 11

- ii -

6.8.8 Interaction with Call Offer (SS-CO) 6.8.9 Interaction with Call Transfer (SS-CT) 6.8.10 I n t e r a c t i o n w i t h 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.11 I n t e r a c t i o n w i t h C o n n e c t e d 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 O N P ) 6.8.12 I n t e r a c t i o n w i t h 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.13 I n te r a c tio n w ith Co mp le tio n o f Ca ll o n N o Re p ly ( S S - CCN R) 6.8.14 Interaction with Do Not Disturb (SS-DND) 6.8.15 I n t e r a c t i o n w i t h D o N o t D is t u r b O v e r r i d e ( S S - D N D O ) 6.8.16 I n t e r a c t i o n w i t h P a t h R e p l a c e me n t ( A N F - P R ) 6.8.17 Interaction with Recall (SS-RE) 6.8.18 I n t e r a c t i o n w i t h 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.19 Interaction with Authentication of the PISN (SS-WTAN) 6.8.20 Interaction with Authentication of a WTM user (SS-WTAT) 6.8.21 I n t e r a c t i o n w i t h 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 is t r a t i o n ( S S - W T L R ) 6.8.22 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l M o b i l i t y I n c o min g C a l l ( S S - W T M I ) 6.8.23 I n t e r a c t i o n w i t h W ir e l e s s T e r mi n a l M o b i l i t y O u t g o in g C a l l ( S S - W T M O ) 6 . 9 S S - MW I p a r a me t e r v a l u e s ( t i me r s ) 6.9.1 T i me r T 1 6.9.2 T i me r T 2

12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 13

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

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

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

Annex D - Imported ASN.1 definitions

A n n e x E - 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

Scope This Standard specifies the signalling protocol for the support of the Message Waiting Indication supplementary service (SS-MWI) at the Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within a Private Integrated Services Network (PISN). The supplementary service MWI enables a Served User to be sent a Message Waiting Indication and also enables this Message Waiting Indication to be cancelled. The Served User may also be permitted to interrogate the Message Centre for any Message Waiting Indication. 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-241. The signalling protocol for SS-MWI 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-MWI and other supplementary services and ANFs. NOTE 1 Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in the relevant stage 1 specifications. This Standard is applicable to PINXs which can interconnect to form a PISN.

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-MWI 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.

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-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-241

Private Integrated Services Network (PISN) - Specification, Functional Model and Information Flows - Message Waiting Indication Supplementary Service (International Standard ISO/IEC 15505)

ISO/IEC 8601

Data elements and interchange formats - Information interchange - Representation of date and times

- 2 -

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. Q.950 Supplementary services protocols, structure and general principles (2000) 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: − Application Protocol Data Unit (APDU)

(ECMA-165)

− Call-Independent

(ECMA-165)

− Gateway PINX

(ECMA-165)

− Originating PINX

(ECMA-165)

− 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-165)

− Transit PINX

(ECMA-165)

4.2

Other definitions

4.2.1

Message Centre PINX The PINX serving the Message Centre entity for activation, deactivation.

4.2.2

Served User The user to whom the Message Waiting Indication is sent on initiative of the Message Centre.

4.2.3

Message Centre The entity which activates or deactivates the Message Waiting Indication as a result of storage or retrieval of messages.

4.2.4

M e s s a g e W a it in g I n d ic a t io n An indication to the Served User when messages are waiting for the Served User. NOTE The indication may be a lamp, special tone, display etc. This is outside the scope of this Standard.

List of acronyms ANF

Additional Network Feature

APDU

Application Protocol Data Unit

ASN.1

Abstract Syntax Notation no. 1

ISDN

Integrated Services Digital Network

- 3 -

MWI

Message Waiting Indication

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

Supplementary Service

Signalling protocol for the support of SS-MWI

6.1

SS-MWI description SS-MWI enables a Served User to be sent a Message Waiting Indication and also enables this Message Waiting Indication to be cancelled. This service also includes an option to interrogate the Message Waiting Indication stored against the Served User.

6.2

SS-MWI operational requirements

6.2.1

Requirements on a Message Centre PINX 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 Served User PINX 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 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-MWI 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 E. Table 1 - Operations in support of SS-MWI

MWI-Operations-asn1-97 { iso (1) standard (0) pss1-message-waiting-indication (15506) message-waiting-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)} basicServiceNotProvided, notActivated, userNotSubscribed, invalidServedUserNr FROM General-Error-List {ccitt recommendation q 950 general-error-list (1) } PartyNumber FROM Addressing-Data-Elements-asn1-97 {iso (1) standard (0) pss1-generic-procedures (11582) addressing-data-elements-asn1-97 (20) } ;

MWI-Operations OPERATION ::= { mWIActivate | mWIDeactivate | mWIInterrogate } mWIActivate

OPERATION ::= { ARGUMENT MWIActivateArg RESULT DummyRes ERRORS { userNotSubscribed | invalidServedUserNr | basicServiceNotProvided | unspecified } CODE local: 80}

- 5 -

Table 1 - Operations in support of SS-MWI (continued) mWIDeactivate

OPERATION ::= { ARGUMENT MWIDeactivateArg RESULT DummyRes ERRORS { userNotSubscribed | invalidServedUserNr | basicServiceNotProvided | unspecified } CODE local: 81}

mWIInterrogate

OPERATION ::= { ARGUMENT MWIInterrogateArg RESULT MWIInterrogateRes ERRORS { userNotSubscribed | invalidServedUserNr | notActivated | invalidMsgCentreId | unspecified } CODE local: 82}

MWIActivateArg

::=

SEQUENCE { servedUserNr PartyNumber, basicService BasicService, msgCentreId MsgCentreId OPTIONAL, nbOfMessages [3] IMPLICIT NbOfMessages OPTIONAL, originatingNr [4] PartyNumber OPTIONAL, timestamp TimeStamp OPTIONAL, priority [5] IMPLICIT INTEGER (0..9) OPTIONAL, -- The value 0 means the highest priority and 9 the lowest argumentExt CHOICE { extension [6] IMPLICIT Extension{{MWIExtSet}}, multipleExtension [7] IMPLICIT SEQUENCE OF Extension{{MWIExtSet}} } OPTIONAL }

DummyRes

::=

CHOICE { null NULL, extension [1] IMPLICIT Extension{{MWIExtSet}}, multipleExtension [2] IMPLICIT SEQUENCE OF Extension{{MWIExtSet}} }

MWIDeactivateArg

::=

SEQUENCE { servedUserNr PartyNumber, basicService BasicService, msgCentreId MsgCentreId OPTIONAL, argumentExt CHOICE { extension [3] IMPLICIT Extension{{MWIExtSet}}, multipleExtension [4] IMPLICIT SEQUENCE OF Extension{{MWIExtSet}} } OPTIONAL }

- 6 -

Table 1 - Operations in support of SS-MWI (continued) MWIInterrogateArg

::=

MWIInterrogateRes

::=

SEQUENCE SIZE(1..10) OF MWIInterrogateResElt

MWIInterrogateResElt

::=

SEQUENCE { basicService BasicService, msgCentreId MsgCentreId OPTIONAL, nbOfMessages [3] IMPLICIT NbOfMessages OPTIONAL, originatingNr [4] PartyNumber OPTIONAL, timestamp TimeStamp OPTIONAL, priority [5] IMPLICIT INTEGER (0..9) OPTIONAL, -- The value 0 means the highest priority and 9 the lowest argumentExt CHOICE { extension [6] IMPLICIT Extension{{MWIExtSet}}, multipleExtension [7] IMPLICIT SEQUENCE OF Extension{{MWIExtSet}} } OPTIONAL }

BasicService ::= ENUMERATED { -- All basic service values which were previously imported from Call Diversion -- Operations have been retained to allow for backward compatibility with edition 2. -- A new service value was added for group 2,3 fax and numerous MWI service -- classes were added for multimedia. -- MWI Services: ---

For compatibility among vendors, speech is recommended for voice mail indications. allServices (0), speech (1), unrestrictedDigitalInformation (2), audio3100Hz (3), telephony (32), teletex (33), telefaxGroup4Class1 (34), videotextSyntaxBased (35), videotelephony (36), telefaxGroup2-3 (37), reservedNotUsed1 (38), reservedNotUsed2 (39), reservedNotUsed3 (40), reservedNotUsed4 (41), reservedNotUsed5 (42),

- 7 -

Table 1 - Operations in support of SS-MWI (continued) --- MWI Service Classes: email video fileTransfer shortMessageService speechAndVideo speechAndFax speechAndEmail videoAndFax videoAndEmail faxAndEmail speechVideoAndFax speechVideoAndEmail speechFaxAndEmail videoFaxAndEmail speechVideoFaxAndEmail multimediaUnknown serviceUnknown

(51), (52), (53), (54), (55), (56), (57), (58), (59), (60), (61), (62), (63), (64), (65), (66), (67),

--- Reserved for future additions: futureReserve1 futureReserve2 futureReserve3 futureReserve4 futureReserve5 futureReserve6 futureReserve7 futureReserve8 }

(68), (69), (70), (71), (72), (73), (74), (75)

MsgCentreId

::=

CHOICE { integer [0] IMPLICIT INTEGER (0..65535), partyNumber [1] PartyNumber, -- The party number must be a complete number as required -- for routing purposes. numericString [2] IMPLICIT NumericString (SIZE (1..10)) }

NbOfMessages

::=

INTEGER (0..65535)

TimeStamp

::= GeneralizedTime (SIZE (12..19)) -- a VisibleString containing: -- the (local) date in 8 digits (YYYYMMDD), -- followed by (local) time of day in 4 or 6 digits (HHMM[SS]), -- optionally followed by the letter "Z" or -by a local time differential in 5 digits ("+"HHMM or "-"HHMM); -this date and time representation follows ISO 8601 -- Examples: 1) 19970621194530, meaning 21 June 1997, 19:45:30; -2) 19970621194530Z, meaning the same as 1); -3) 19970621194530-0500, meaning the same as 1), -5 hours retarded in relation to UTC time

- 8 -

Table 1 - Operations in support of SS-MWI (concluded) MWIExtSet EXTENSION ::= {...} invalidMsgCentreId

ERROR

::=

{

CODE

local:

1018}

unspecified

ERROR

::=

{

PARAMETER Extension{{MWIExtSet}} CODE local: 1008}

END

-- of MWI-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 APDU of operations defined in 6.3.1, the destination Entity data element of the NFE shall contain the value endPINX. When conveying the invoke APDU of operation mwiActivate, mwiDeactivate and mwiInterrogate, the interpretation APDU shall either be omitted or have the value rejectAnyUnrecognizedInvokePdu. 6.3.2.2

6.3.3

6.4

Other information elements Any other information element (e.g. Calling party number) shall be coded in accordance with ECMA-165. Messages The Facility information element shall be conveyed in messages as specified in clause 10 of ECMA-165.

SS-MWI state definitions

6.4.1

States at the Message Centre PINX The procedures for the Message Centre PINX are written in terms of the following conceptual states existing within the SS-MWI Supplementary Service Control entity in that PINX in association with an activation or deactivation request from the Message Centre entity.

6.4.1.1

S t a t e M W I - M c - I d le Activation, deactivation is not in progress. The Message Center PINX is ready for receipt of mwiInterrogate invoke APDU.

6.4.1.2

S t a t e M W I - M c - W a it A mwiActivate or mwiDeactivate invoke APDU has been sent. The Message Centre PINX is waiting for the response.

6.4.2

States at the Served User PINX The procedures for the Served User PINX are written in terms of the following conceptual states existing within the SS-MWI Supplementary Service Control entity in that PINX in association with a particular call-independent signalling connection for the Served User.

6.4.2.1

S t a t e M W I - S e r - I d le The Served User PINX is ready for receipt of mwiActivate or mwiDeactivate invoke APDU.

6.4.2.2

S t a t e M W I - S e r - W a it A mwiInterrogate invoke APDU has been sent. The Served User PINX is waiting for the response.

6.5

SS-MWI signalling procedures Examples of message sequences are shown in annex B.

- 9 -

6.5.1

A c t io n s a t t h e M e s s a g e C e n t r e P I N X The SDL representation of procedures at the Message Centre PINX is shown in clause C.1 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 On receipt of an activation / deactivation request from the Message Centre entity, the Message Centre PINX shall send a mwiActivate/mwiDeactivate invoke APDU to the Served User PINX using the call reference of a call-independent signalling connection. The call-independent signalling connection shall be established (or used, if an appropriate connection is already available) in accordance with the procedures specified in 7.3 of ECMA-165. The Message Centre PINX shall start timer T1 and enter the MWI-Mc-Wait state. The mwiActivate/mwiDeactivate invoke APDU shall contain the PISN number of the Served User and the service for which the activation / deactivation applies. The Message Centre PINX may optionally include in the mwiActivate invoke APDU any of the following: • an identifier for the Message Centre, in the element msgCentreId; • the number of messages for the Served User in the element nbOfMessages; • the number of the user that has left a message, in the element originatingNr; • the time when a message was left, in the element timestamp; • the highest priority of the messages for the Served User in the element priority. In state MWI-Mc-Wait, on receipt of a mwiActivate or mwiDeactivate return result APDU, the Message Centre PINX shall stop timer T1, and enter state MWI-Mc-Idle. NOTE The Message Centre PINX should indicate acceptance to the Message Centre entity. The Message Centre PINX is responsible for clearing the call-independent signalling connection towards the Served User PINX. This may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate. 6.5.1.1.2

I n t e r r o g a t io n In state MWI-Mc-Idle, on receipt of a mwiInterrogate invoke APDU using the call reference of a call-independent signalling connection (as specified in 7.3 of ECMA-165) and if the interrogation is possible and the Message Centre identifier, if received, is correct, the Message Centre PINX shall get the status of SS-MWI, send back a mwiInterrogate return result APDU to the Served User PINX and stay in state MWI-Mc-Idle. The information that may be included in the return result APDU is analogous to the mwiActivate invoke APDU as described in 6.5.1.1.1.

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 state MWI-Mc-Wait, on receipt of a mwiActivate/mwiDeactivate return error APDU from the Served User PINX, the Message Centre PINX shall stop timer T1 and enter state MWI-Mc-Idle. If timer T1 expires, the Message Centre PINX shall enter state MWI-Mc-Idle. NOTE The Message Centre PINX should indicate rejection to the Message Centre entity. The Message Centre PINX is responsible for clearing the call-independent signalling connection towards the Served User PINX. This may occur on receipt of a return error APDU or on expiry of timer T1. Alternatively, the signalling connection may be retained for other applications, if appropriate. 6.5.1.2.2

I n t e r r o g a t io n On receipt of a mwiInterrogate invoke APDU using the call reference of a call-independent signalling connection (as specified in 7.3 of ECMA-165) and if interrogation is not possible or an

- 10 -

incorrect Message Centre identifier is included, the Message Centre PINX shall send back a mwiInterrogate return error APDU to the Served User PINX and stay in state MWI-Mc-Idle. 6.5.2

A c t io n s a t t h e S e r v e d U s e r P I N X The SDL representation of procedures at the Served User PINX is shown in clause C.2 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 On receipt of a mwiActivate/mwiDeactivate invoke APDU using the call reference of a callindependent signalling connection (as specified in 7.3 of ECMA-165) and if activation / deactivation is possible, the Served User PINX shall activate / deactivate SS-MWI and send back a mwiActivate/mwiDeactivate return result APDU to the Message Centre PINX and remain in MWISer-Idle state. 6.5.2.1.2

I n t e r r o g a t io n On receipt of an interrogation request from the Served User, the Served User PINX shall send a mwiInterrogate invoke APDU to the Message Centre PINX using the call reference of a call-independent signalling connection. The call-independent signalling connection shall be established (or used, if an appropriate connection is already available) in accordance with the procedures specified in 7.3 of ECMA-165. The Served User PINX shall start timer T2 and enter the MWI-Ser-Wait state. The mwiInterrogate invoke APDU shall contain the PISN number of the Served User, the service for which the interrogation applies, and optionally the Message Centre identifier. In state MWI-Ser-Wait, on receipt of a mwiInterrogate return result APDU, the Served User PINX shall stop timer T2, and enter state MWI-Ser-Idle. NOTE The Served User PINX should indicate the result to the Served User. The Served User PINX is responsible for clearing the call-independent signalling connection towards the Message Centre PINX. This may occur on receipt of a return result APDU. Alternatively, the signalling connection may be retained for other applications, if appropriate.

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 On receipt of a mwiActivate/mwiDeactivate invoke APDU and if the activation / deactivation request cannot be accepted, the Served User PINX shall send a mwiActivate/mwiDeactivate return error APDU with an appropriate error value and remain in state MWI-Ser-Idle. 6.5.2.2.2

I n t e r r o g a t io n In state MWI-Ser-Wait, on receipt of a mwiInterrogate return error APDU from the Message Centre PINX, the Served User PINX shall stop timer T2, and enter state MWI-Ser-Idle. If timer T2 expires, the Served User shall enter MWI-Ser-Idle. NOTE The Served User PINX should indicate rejection to the Served User. The Served User PINX is responsible for clearing the call-independent signalling connection towards the Message Centre PINX. This may occur on receipt of a return errorAPDU or on expiry of timer T2. Alternatively, the signalling connection may be retained for other applications, if appropriate.

6.5.3

6.6

A c t io n s a t a Tr a n s it P I N X Not applicable.

SS-MWI 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.

- 11 -

NOTE The interrogation function is not supported in the corresponding public ISDN service. 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 MWI activation or deactivation request is received from the public ISDN, the Incoming Gateway PINX shall translate the received APDU and convert it into a mwiActivate or mwiDeactivate invoke APDU and the procedures specified in 6.5.1 or 6.5.2 shall apply. The Incoming Gateway PINX shall translate the mwiActivate or mwiDeactivate return result APDU received from the Served User PINX into corresponding information and send it to the public ISDN.

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 mwiActivate or the mwiDeactivate invoke APDU and send it to the public ISDN according to the procedures for the T reference point. When receiving a response, the Outgoing Gateway PINX shall generate a mwiActivate or mwiDeactivate return result APDU (if the activation / deactivation was accepted) or a mwiActivate or mwiDeactivate return error APDU (if the activation / deactivation was rejected).

6.7

SS-MWI impact of interworking with non-ISDNs Not applicable.

6.8

Protocol interactions between SS-MWI 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-MWI 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

I n t e r a c t io n wit h A d v ic e O f C h a r g e ( S S - A O C ) No interaction.

6.8.2

Interaction with Call Deflection (SS-CD) No interaction.

6.8.3

I n t e r a c t io n wit h 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 interaction. NOTE A MWI should not be redirected to the diverted-to user. The indication may be given to the Served User.

6.8.4

I n t e r a c t io n wit h C a ll F o r wa r d in g Bu s y ( S S - C F B) No interaction. NOTE A MWI should not be redirected to the diverted-to user. The indication may be given to the Served User.

6.8.5

I n t e r a c t i o n wit h 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 ) No interaction. NOTE A MWI should not be redirected to the diverted-to user. The indication may be given to the Served User.

6.8.6

Interaction with Call Interception (ANF-CINT) No interaction.

6.8.7

I n t e r a c t i o n wit h C a l l I n t r u s i o n ( S S - C I ) No interaction.

- 12 -

6.8.8

I n t e r a c t i o n wit h C a l l O f f e r ( S S - C O ) No interaction.

6.8.9

I n t e r a c t io n wit h C a ll Tr a n s f e r ( S S - C T) No interaction.

6.8.10

Interaction with Calling Name Identification Presentation (SS-CNIP) No interaction.

6.8.11

Interaction with Connected Name Identification Presentation (SS-CONP) No interaction.

6.8.12

Interaction with Completion of Call to Busy Subscriber (SS-CCBS) No interaction.

6.8.13

I n t e r a c t i o n wit h C o m p l e t i o n o f C a l l o n N o R e p l y ( S S - C C N R ) No interaction.

6.8.14

I n t e r a c t i o n wit h D o N o t D i s t u r b ( S S - D N D ) No interaction.

6.8.15

Interaction with Do Not Disturb Override (SS-DNDO) No interaction.

6.8.16

Interaction with Path Replacement (ANF-PR) No interaction.

6.8.17

Interaction with Recall (SS-RE) No interaction.

6.8.18

I n t e r a c t i o n wit h R o u t e R e s t r i c t i o n C l a s s ( A N F - R R C ) No interaction.

6.8.19

I n t e r a c t i o n wit h 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 ) No interaction.

6.8.20

I n t e r a c t io n wit h A u t h e n t ic a t i o n o f a W T M u s e r ( S S - W T A T ) No interaction.

6.8.21

Interaction with Wireless Terminal Location Registration (SS-WTLR) No interaction. NOTE A MWI may be directed to the new location.

6.8.22

I n t e r a c t i o n w i t h W i r e l e s s T e r m in a l M o b i l i t y I n c o m i n g C a l l ( S S - W T M I ) No interaction.

6.8.23

I n t e r a c t i o n w i t h W i r e l e s s T e r m in a l M o b i l i t y O u t g o i n g C a l l ( S S - W T M O ) No interaction

6.9 6.9.1

SS-MWI parameter values (timers) Timer T1 Timer T1 shall operate at the Message Centre PINX during state MWI-Mc-Wait. Its purpose is to protect against an absence of response to the mwiActivate or mwiDeactivate invoke APDU. Timer T1 shall have a value not less than 15 seconds.

- 13 -

6.9.2

Timer T2 Timer T2 shall operate at the Served User PINX during state MWI-Ser-Wait. Its purpose is to protect against an absence of response to the mwiInterrogate invoke APDU. Timer T2 shall have a value not less than 15 seconds.

- 14 -

- 15 -

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 A.2.1

Instructions for completing the PICS proforma 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);

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;

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).

- 16 -

A.2.2

A d d it io n a l in f o r m a t io n 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

Ex c e p t io n in f o r m a t io n 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 pre-printed 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.

- 17 -

A.3

PICS proforma for ECMA-242

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)

- 18 -

A.3.3

General

Item

Question/feature

Behaviour as Message Centre PINX for activation and deactivation of SS-MWI

o.1

Behaviour as Message Centre PINX for interrogation of SS-MWI

A1:o

Behaviour as Served User PINX for activation and deactivation of SS-MWI

o.1

Behaviour as Served User PINX for interrogation of SS-MWI

A3:o

Behaviour as Incoming Gateway PINX for interworking with a public ISDN for activation and deactivation of SS-MWI

Yes [ ] No[ ]

Behaviour as Outgoing Gateway PINX for interworking with a public ISDN for activation and deactivation of SS-MWI

Yes [ ] No[ ]

A.3.4

References

Status

N/A

Support Yes [ ] No[ ]

[]

Yes [ ] No[ ] Yes [ ] No[ ]

[]

Yes [ ] No[ ]

Procedures

Item

Question/feature

References

Status

N/A

Support

Support of relevant ECMA-165 procedures at the Message Centre PINX

6.2.1

A1:m

[]

m:Yes [ ]

Support of relevant ECMA-165 procedures at the Served User PINX

6.2.2

A3:m

[]

m:Yes [ ]

Procedures at the Message Centre PINX for activation and deactivation

6.5.1

A1:m

[]

m:Yes [ ]

Procedures at the Message Centre PINX for interrogation

6.5.1

A2:m

[]

m:Yes [ ]

Procedures at the Served User PINX for activation and deactivation

6.5.2

A3:m

[]

m:Yes [ ]

Procedures at the Served User PINX for interrogation

6.5.2

A4:m

[]

m:Yes [ ]

Procedures at an Incoming Gateway PINX for interworking with a public ISDN for activation and deactivation

6.6.1

A5:m

[]

m:Yes [ ]

Procedures at an Outgoing Gateway PINX for interworking with a public ISDN for activation and deactivation

6.6.2

A6:m

[]

m:Yes [ ]

- 19 -

A.3.5

C o d in g

Item

Question/feature

References

Status

N/A

Support

Sending of mwiActivate invoke APDU and receipt of mwiActivate return result and error APDU

6.3.1

A1:m

[]

m:Yes [ ]

Receipt of mwiActivate invoke APDU and sending of mwiActivate return result and error APDU

6.3.1

A3:m

[]

m:Yes [ ]

Sending of mwiDeactivate invoke APDU and receipt of mwiDeactivate return result and error APDU

6.3.1

A1:m

[]

m:Yes [ ]

Receipt of mwiDeactivate invoke APDU and sending of mwiDeactivate return result and error APDU

6.3.1

A3:m

[]

m:Yes [ ]

Sending of mwiInterrogate invoke APDU and receipt of mwiInterrogate return result and error APDU

6.3.1

A4:m

[]

m:Yes [ ]

Receipt of mwiInterrogate invoke APDU and sending of mwiInterrogate return result and error APDU

6.3.1

A2:m

[]

m:Yes [ ]

A.3.6

Timers

Item

Question/feature

References

Status

N/A

Support

Support of timer T1

6.9.1

A1:m

[]

m:Yes [ ]

Support of timer T2

6.9.2

A4:m

[]

m:Yes [ ]

- 20 -

- 21 -

Annex B ( in f o r ma tiv e )

Examples of Message Sequences

This annex describes some typical message flows for SS-MWI. The following conventions are used in the figures of this annex. 1. The following notation is used:

Call-independent signalling connection message without SS-MWI information Call-independent signalling connection message containing SS-MWI information 96-0167-A

2. The figures show messages exchanged via Protocol Control between PINXs involved in SS-MWI. Only messages relevant to SS-MWI 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-MWI is not shown.

- 22 -

B.1

Example message sequence for activation of SS-MWI Figure B.1 shows an example of activation of SS-MWI where the connection is not cleared by the Message Centre PINX after the first activation of MWI. Served User PINX

Transit PINX

Message Centre PINX

SETUP mwiActivate.inv

CALL PROCEEDING CALL PROCEEDING

CONNECT

mwiActivate.res

FACILITY

mwiActivate.inv

FACILITY

mwiActivate.res

RELEASE

RELEASE COMPLETE RELEASE COMPLETE

96-0168-A

F ig u r e B. 1 - Ex a m p le o f a c t iv a t io n o f S S - M W I

- 23 -

B.2

Example message sequence for deactivation of SS-MWI Figure B.2 shows an example of deactivation of SS-MWI. Message Centre PINX

Served User PINX

Transit PINX

SETUP

mwiDeactivate.inv

CALL PROCEEDING CALL PROCEEDING

CONNECT

mwiDeactivate.res

RELEASE

RELEASE COMPLETE RELEASE COMPLETE

96-0169-A

F ig u r e B. 2 - Ex a m p le o f d e a c t iv a t io n o f S S - M W I

- 24 -

B.3

Example message sequence for interrogation of SS-MWI Figure B.3 shows an example of interrogation of SS-MWI. Served User PINX

Transit PINX

Message Centre PINX

SETUP mwiInterrogate.inv

SETUP mwiInterrogate.inv CALL PROCEEDING

CALL PROCEEDING

CONNECT mwiInterrogate.res

RELEASE

RELEASE COMPLETE

RELEASE

RELEASE COMPLETE

96-0170-A

F ig u r e B. 3 - Ex a m p le o f in t e r r o g a t io n o f S S - M W I

- 25 -

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-MWI 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

res.

return result APDU

err.

return error APDU

rej.

reject APDU

C.1

SDL representation of SS-MWI at the Message Centre PINX Figures C.1, C.2 and C.3 show the behaviour of an SS-MWI Supplementary Service Control entity within the Message Centre PINX. Input signals from the left and output signals to the left represent primitives from and to the Message Centre. 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. Also protocol timer expiry is indicated by an input signal from the right.

- 26 -

MWI-Mc-Idle

activation request from the MC

Message with mwiActivate.inv

Start T1

MWI-Mc-Wait

Message with mwiActivate.res

Message with mwiActivate.err .

Stop T1

activation accepted

activation rejected

T1 expiry

MWI-Mc-Idle

96-0171-A

F ig u r e C . 1 - S D L r e p r e s e n t a t io n o f S S - M W I a c t iv a t io n a t t h e M e s s a g e C e n t r e P I N X

- 27 -

MWI-Mc-Idle

deactivation request from the MC

Message with mwiDeactivate.inv

Start T1

MWI-Mc-Wait

Message with mwiDeactivate.res

Message with mwiDeactivate.err

Stop T1

deactivation accepted

deactivation rejected

T1 expiry

MWI-Mc-Idle

96-0172-A

F ig u r e C . 2 - S D L r e p r e s e n t a t io n o f S S - M W I d e a c t iv a t io n a t t h e M e s s a g e C e n t r e P I N X

- 28 -

MWI-Mc-Idle

Message with mwiInterrogate.inv

interrogation possible?

Yes

Interrogate MWI

Message with mwiInterrogate.err .

Message with mwiInterrogate.res

MWI-Mc-Idle

96-0173-A

F ig u r e C . 3 - S D L r e p r e s e n t a t io n o f S S - M W I in t e r r o g a t io n a t t h e M e s s a g e C e n t r e P I N X

- 29 -

C.2

SDL representation of SS-MWI at the Served User PINX Figures C.4 and C.5 show the behaviour of an SS-MWI Supplementary Service Control entity within the Served User PINX. Input signals from the right and output signals to the right represent primitives from and to the 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.

MWI-Ser-Idle

Message with mwiActivate.inv

activation possible?

Message with mwiDeactivate.inv

deactivation possible?

Yes

Activate MWI

Deactivate MWI

Message with mwiActivate.res

MWI-Ser-Idle

Message with mwiActivate.err

Message with mwiDeactivate.res

Message with mwiDeactivate.err

MWI-Ser-Idle

96-0174-A

F ig u r e C . 4 - S D L r e p r e s e n t a t io n o f S S - M W I a c t iv a t i o n / d e a c t i v a t i o n a t t h e S e r v e d U s e r P I N X

- 30 -

MWI-Ser-Idle

Interrogate request from the Served User

Message with mwiInterrogate.inv

Start T2

MWI-Ser-Wait

Message with mwiInterrogate.res

Message with mwiInterrogate.err

Stop T2

interrogation accepted

interrogation rejected

T2 expiry

MWI-Ser-Idle

96-0175-A

F ig u r e C . 5 - S D L r e p r e s e n t a t io n o f S S - M W I in t e r r o g a t io n a t t h e S e r v e d U s e r P I N X

- 31 -

Annex D ( in f o r ma tiv e )

Imported ASN.1 definitions

The content of this annex has been deleted to remove duplicate ASN.1 definitions defined elsewhere.

- 32 -

- 33 -

Annex E ( 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-242, i.e. based on ITU-T Recommendations X.208 / X.209. Starting with the fourth edition the ASN.1 modules within ECMA-242 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 E. 1 - S S - M W I - 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-MWI-Operations { iso (1) standard (0) pss1-message-waiting-indication (15506) message-waiting-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)} basicServiceNotProvided, notActivated, userNotSubscribed, invalidServedUserNumber FROM General-Error-List {ccitt (2) recommendation (0) q (17) 950 general-error-list (1) } PartyNumber FROM Addressing-Data-Elements {iso (1) standard (0) pss1-generic-procedures (11582) addressing-data-elements (9) } ;

MWIActivate

::=

OPERATION ARGUMENT RESULT ERRORS {

MWIActivateArg DummyRes userNotSubscribed, invalidServedUserNumber, basicServiceNotProvided, unspecified }

- 34 -

Ta b le E. 1 - S S - M W I - 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 ) MWIDeactivate

MWIInterrogate

::=

OPERATION ARGUMENT RESULT ERRORS {

MWIDeactivateArg DummyRes userNotSubscribed, invalidServedUserNumber, basicServiceNotProvided, unspecified } MWIInterrogateArg MWInterrogateRes userNotSubscribed, invalidServedUserNumber, notActivated, invalidMsgCentreId, unspecified }

MWIActivateArg

::=

SEQUENCE { servedUserNr PartyNumber, basicService BasicService, msgCentreId MsgCentreId OPTIONAL, nbOfMessages [3] IMPLICIT NbOfMessages OPTIONAL, originatingNr [4] PartyNumber OPTIONAL, timestamp TimeStamp OPTIONAL, priority [5] IMPLICIT INTEGER (0..9) OPTIONAL, -- The value 0 means the highest priority and 9 the lowest argumentExt CHOICE { extension [6] IMPLICIT Extension, multipleExtension [7] IMPLICIT SEQUENCE OF Extension } OPTIONAL }

DummyRes

::=

CHOICE { null NULL, extension [1] IMPLICIT Extension, multipleExtension [2] IMPLICIT SEQUENCE OF Extension }

MWIDeactivateArg

::=

SEQUENCE { servedUserNr PartyNumber, basicService BasicService, msgCentreId MsgCentreId OPTIONAL, argumentExt CHOICE { extension [3] IMPLICIT Extension, multipleExtension [4] IMPLICIT SEQUENCE OF Extension } OPTIONAL }

- 35 -

Ta b le E. 1 - S S - M W I - 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 ) MWIInterrogateArg

::=

MWIInterrogateRes

::=

SEQUENCE SIZE(1..10) OF MWIInterrogateResElt

MWIInterrogateResElt

::=

SEQUENCE { basicService BasicService, msgCentreId MsgCentreId OPTIONAL, nbOfMessages [3] IMPLICIT NbOfMessages OPTIONAL, originatingNr [4] PartyNumber OPTIONAL, timestamp TimeStamp OPTIONAL, priority [5] IMPLICIT INTEGER (0..9) OPTIONAL, -- The value 0 means the highest priority and 9 the lowest argumentExt CHOICE { extension [6] IMPLICIT Extension, multipleExtension [7] IMPLICIT SEQUENCE OF Extension } OPTIONAL }

BasicService

::= ENUMERATED { -- All basic service values which were previously imported from Call Diversion -- Operations have been retained to allow for backward compatibility with edition 2. -- A new service value was added for group 2,3 fax and numerous MWI service -- classes were added for multimedia. -- MWI Services: -For compatibility among vendors, speech is recommended for voice mail -indications. allServices (0), speech (1), unrestrictedDigitalInformation (2), audio3100Hz (3), telephony (32), teletex (33), telefaxGroup4Class1 (34), videotextSyntaxBased (35), videotelephony (36), telefaxGroup2-3 (37), reservedNotUsed1 (38), reservedNotUsed2 (39), reservedNotUsed3 (40), reservedNotUsed4 (41), reservedNotUsed5 (42), --

- 36 -

Ta b le E. 1 - S S - M W I - 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 ) -- MWI Service Classes: email video fileTransfer shortMessageService speechAndVideo speechAndFax speechAndEmail videoAndFax videoAndEmail faxAndEmail speechVideoAndFax speechVideoAndEmail speechFaxAndEmail videoFaxAndEmail speechVideoFaxAndEmail multimediaUnknown serviceUnknown --- Reserved for future additions: futureReserve1 futureReserve2 futureReserve3 futureReserve4 futureReserve5 futureReserve6 futureReserve7 futureReserve8 }

(51), (52), (53), (54), (55), (56), (57), (58), (59), (60), (61), (62), (63), (64), (65), (66), (67),

(68), (69), (70), (71), (72), (73), (74), (75)

MsgCentreId

::=

NbOfMessages

::=

INTEGER (0..65535)

TimeStamp

- 37 -

Ta b le E. 1 - S S - M W I - 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 ) mwiActivate mwiDeactivate mwiInterrogate invalidMsgCentreId unspecified Unspecified

MWIActivate ::= localValue 80 MWIDeactivate ::= localValue 81 MWIInterrogate ::= localValue 82 ERROR ::= localValue 1018 Unspecified ::= localValue 1008 ::= ERROR PARAMETER Extension

END

-- of SS-MWI-Operations

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.

ECMA-242 — Private Integrated Services Network (PISN) - Inter-exchange signalling protocol - Message waiting indication supplementary service (QSIG-MWI) (December 2001)

Related documents