Conceptio › Archive › ECMA International

ECMA Internationalopen access

ECMA-345 — Private Integrated Services Network (PISN) – Use of QSIG for Message Centre Access (MCA) profile standard (June 2003)

ECMA International · ECMA International

ECMA International · Standards · License: Open Access

access centre ecma ecmainternational integrated message network pisn

ecma, standard, ecma international, specification, ecma-345, ecma 345, 345, private, integrated, services, network, pisn, use, qsig, for, message, centre, access, mca, profile

Standard ECMA-345 June 2003

International

Standardizing

Information

and

Communication

Systems

Private Integrated Services Network (PISN) – Use of QSIG for Message Centre Access (MCA) Profile Standard

Phone/Fax: +41 22 849.60.00/01

http://www.ecma-international.org

mailto: h e l p d e s k @ e c m a . c h

Standard ECMA-345 June 2003

International

Standardizing

Information

and

Communication

Systems

Private Integrated Services Network (PISN) – Use of QSIG for Message Centre Access (MCA) Profile Standard

Phone/Fax: +41 22 849.60.00/01 IW Ecma-345.doc 16-07-03 09,47

http://www.ecma-international.org

mailto: h e l p d e s k @ e c m a . c h

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. It has been produced under ETSI work item DTS/ECMA-00223. 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 regional standardization bodies. It represents a pragmatic and widely based consensus.

This ECMA Standard has been adopted by the General Assembly of June 2003.

- i -

Table of contents 1

S co p e

Con for manc e

R ef e r en ce s ( n o r mat iv e)

D ef in it io ns 4.1 Ex tern al d efin itions 4.2 S erv ed U ser 4.3 S erv ed U ser PINX 4.4 Me s sag e Cen tr e 4.4 .1 MCM Me ssage Cen tr e 4.4 .2 MW I Mes sag e Cen tre 4.5 MCA-Pro f ile -1 4.6 MCA-Pro f ile -2 4.7 MCA-Pro f ile -3 4.8 MCA-Pro f ile -4 4.9 Me s sag e D epo sit 4.9 .1 D ir ect Me ssage Depo sit 4.9 .2 Messag e D epo sit af ter D iv ersion 4.9 .3 Me s sag e D epo sit a f ter T ran sf er 4.10 Me s sag e Cen tr e Mon itor ing 4.11 Messag e Brow sing 4.12 Me s sag e Retr ieva l 4.13 Me s sag e Cen tr e Tran sf er A cro nym s

2 2 3 4 4 4 4 4 4 4 4 4 4 4 5 5 5 5 5 5

S p e c if i cat io n f ra m e wo r k 6.1 G ener a l D e scr ip tion 6.2 S c enar io s 6.2 .1 Me s sag e D epo sit 6.2 .2 Me s sag e Cen tr e Mon itor ing 6.2 .3 Messag e Brow sing 6.2 .4 Me s sag e Retr ieva l 6.2 .5 Me s sag e Cen tr e Tran sf er

6 6 6 6 7 7 7 7

Profiles 7.1 MCA-Pro f ile -1 7.1 .1 Me s sag e D epo sit 7.1 .2 Me s sag e Cen tr e Mon itor ing 7.1 .3 Messag e Brow sing 7.1 .4 Me s sag e Retr ieva l 7.1 .5 Me s sag e Cen tr e Tran sf er

8 8 8 9 9 9 9

- ii -

7.2 MCA-Pro f ile -2 7.2 .1 Me s sag e D epo sit 7.2 .2 Messag e Cen tr e Mon itor ing 7.2 .3 Messag e Brow sing 7.2 .4 Me s sag e Retr ieva l 7.2 .5 Me s sag e Cen tr e Tran sf er 7.3 MCA-Pro f ile -3 7.3 .1 Me s sag e D epo sit 7.3 .2 Messag e Cen tr e Mon itor ing 7.3 .3 Messag e Brow sing 7.3 .4 Me s sag e Retr ieva l 7.3 .5 Me s sag e Cen tr e Tran sf er 7.4 MCA-Pro f ile -4 7.4 .1 Me s sag e D epo sit 7.4 .2 Messag e Cen tr e Mon itor ing 7.4 .3 Messag e Brow sing 7.4 .4 Me s sag e Retr ieva l 7.4 .5 Me s sag e Cen tr e Tran sf er

9 9 10 10 10 10 11 11 11 11 12 12 12 12 12 12 12 13

Annex A - R equirements List (RL)

Annex B - Prof ile specif ic IC S proforma

Annex C - Example Message Flo ws

Scope This Profile Standard specifies the combination of base standards, together with the selection of appropriate options and parameter values, necessary to specify how QSIG / PSS1 can be used for Message Centre Access (MCA) procedures. This Standard identifies the necessary or optional employment of particular functions, procedures and services for

•

a Calling User to deposit messages for a Served User at a Message Centre,

•

a Served User to monitor the Served User's Mailbox for new messages,

•

a Served User to browse through the messages saved in the Served User's Mailbox,

•

a Served User to retrieve the messages saved in the Served User's Mailbox and

•

a Served User to get connected to the Originator of a message or any other destination.

Conformance A system conforms to this Standard if it correctly performs all the mandatory capabilities defined in one or more of the requirement list (RL) (annex A) and one or more of the profile specific ICS (annex B). NOTE For the purpose of this Standard capabilities marked as optional in the base standards may be mandatory or excluded.

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 64kbit/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)

ECMA-155

Private Integrated ISO/IEC 11571)

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

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Call Diversion Supplementary Services (CFSD) (International Standard ISO/IEC 13872)

ECMA-174

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Call Diversion Supplementary Services (QSIG-CF) (International Standard ISO/IEC 13873)

ECMA-177

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Call Transfer Supplementary Service (CTSD) (International Standard ISO/IEC 13865)

Services

Network

–

Addressing

(International

Standard

- 2 -

ECMA-178

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Call Transfer Supplementary Service (QSIG-CT) (International Standard ISO/IEC 13869)

ECMA-241

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

ECMA-242

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Message Waiting Indication Supplementary Service (QSIG-MWI) (International Standard ISO/IEC 15506)

ECMA-299

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Single Step Call Transfer Supplementary Service (SSCT-SD) (International Standard ISO/IEC 19459)

ECMA-300

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Single Step Call Transfer Supplementary Service (QSIG-SSCT) (International Standard ISO/IEC 19460)

ECMA-310

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Simple Dialog Supplementary Service (SDSD) (International Standard ISO/IEC 21407)

ECMA-311

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Simple Dialog Supplementary Service (QSIG-SD) (International Standard ISO/IEC 21408)

ECMA-343

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Make Call Request Supplementary Service (MCRSD)

ECMA-344

Private Integrated Services Network (PISN) – Inter-Exchange Signalling Protocol – Make Call Request Supplementary Service (QSIG-MCR)

ECMA-346

Private Integrated Services Network (PISN) – Specification, Functional Model and Information Flows – Message Centre Monitoring and Mailbox Identification Supplementary Services (MCM-SD / MID-SD)

ECMA-347

Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol – Message Centre Monitoring and Mailbox Identification Supplementary Services (QSIG-MCM / QSIG-MID)

ECMA TR/76

Private Integrated Services Network (PISN) – Architecture and Scenarios for Private Integrated Services Networking (ISO/IEC TR 14475)

ISO/IEC 9646-7

Information technology – Open Systems Interconnection – Conformance testing methodology and framework – Part 7: Implementation Conformance statements (1994)

ITU-T Rec. E.164

The international public telecommunication numbering plan (1997)

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: – Basic Call

(ECMA-165)

– Call

(ECMA-165)

– Call Independent Signalling Connection

(ECMA-165)

– Call Related

(ECMA-165)

– Complete Number

(ECMA-155)

- 3 -

4.2

– Compressed Information

(ECMA-346)

– Display information

(ECMA-310)

– Diverted-to PINX

(ECMA-174)

– Keypad information

(ECMA-310)

– Mailbox

(ECMA-346)

– Mailbox Identification

(ECMA-346)

– Make Call Request

(ECMA-343)

– Message Centre

(ECMA-346)

– Message Centre PINX

(ECMA-347)

– Message Type

(ECMA-346)

– Message Status

(ECMA-346)

– MCR Co-operating PINX

(ECMA-344)

– MCR Co-operating User

(ECMA-343)

– MCR Destination PINX

(ECMA-344)

– MCR Destination User

(ECMA-343)

– MCR Requesting PINX

(ECMA-344)

– MCR Requesting User

(ECMA-343)

– New Message

(ECMA-346)

– Original Call

(ECMA-343)

– Originator

(ECMA-346)

– Private Integrated Services Network (PISN)

(ECMA-133)

– Private Integrated services Network eXchange (PINX)

(ECMA-133)

– Requested Call

(ECMA-343)

– Rerouting PINX

(ECMA-174)

– Retrieved Message

(ECMA-346)

– Secondary Call

(ECMA-178)

– Served User

(ECMA-173, ECMA-346)

– Server User

(ECMA-310)

– Served User PINX

(ECMA-174, ECMA-347)

– Server User PINX

(ECMA-311)

– Transferred User

(ECMA-299)

– Transferring User

(ECMA-178)

– Telecommunication Service

(ECMA-142)

– User

(ECMA-142)

– User B

(ECMA-177)

– Q reference point

(ECMA-133)

Served User The Served User as defined in Message Centre Monitoring (ECMA-346). For MCA, the Served User may also act as Served User in Call Diversion (as defined in ECMA-173), as a User B in Call Transfer (as defined in ECMA-177), as a Client User in Simple Dialog (as defined in ECMA-310), as a Transferred User

- 4 -

in Single Step Call Transfer (as defined in ECMA-299) and as a Co-operating User in Make Call Request (as defined in ECMA-343).

4.3

Served User PINX The Served User PINX as defined in ECMA-347. For MCA, the Served User PINX may also act as Served User PINX or Rerouting PINX for Call Diversion (as defined in ECMA-173), as a Primary PINX for Call Transfer (as defined in ECMA-177), as a Client User PINX for Simple Dialog (as defined in ECMA-311), as a Transferred PINX for Single Step Call Transfer (as defined in ECMA-300) and as a Co-operating PINX for Make Call Request (as defined in ECMA-344).

4.4

Message Centre Depending on the MCA-Profile, either the MCM or the MWI Message Centre.

4.4 .1

MCM M essag e C ent re The Message Centre as defined in ECMA-346. This definition is used in MCA-Profile-3 and MCA-Profile-4. For MCA, the MCM Message Centre may also act as Diverted-to PINX for Call Diversion (as defined in ECMA-174), as a Server User PINX for Simple Dialog (as defined in ECMA-311), a Transferring PINX for Call Transfer (as defined in ECMA-178), a Transferring PINX for Single Step Call Transfer (as defined in ECMA-300) and a Requesting PINX for Make Call Request (as defined in ECMA-344).

4.4 .2

MWI M essag e C ent re The Message Centre as defined in ECMA-241. This definition is used in MCA-Profile-1 and MCA-Profile-2. For MCA, the MWI Message Centre may also act as Diverted-to PINX for Call Diversion (as defined in ECMA-174), as a Server User PINX for Simple Dialog (as defined in ECMA-311), as a Transferring PINX for Call Transfer (as defined in ECMA-178) and as a Transferring PINX for Single Step Call Transfer (as defined in ECMA-300).

4.5

MCA-Profile-1 MCA-Profile-1 is a profile, which describes the interoperation of supplementary services for Message Centre Access purposes. Supplementary services involved in MCA-Profile-1 are Call Diversion, Message Waiting Indication and Call Transfer.

4.6

MCA-Profile-2 MCA-Profile-2 is a profile, which describes the interoperation of supplementary services for Message Centre Access purposes. Supplementary services involved in MCA-Profile-2 are Call Diversion, Message Waiting Indication, Call Transfer, Single Step Call Transfer and Simple Dialog.

4.7

MCA-Profile-3 MCA-Profile-3 is a profile, which describes the interoperation of supplementary services for Message Centre Access purposes. Supplementary services involved in MCA-Profile-3 are Call Diversion, Call Transfer, Single Step Call Transfer, Simple Dialog, Message Centre Monitoring and Mailbox Identification.

4.8

MCA-Profile-4 MCA-Profile-4 is a profile, which describes the interoperation of supplementary services for Message Centre Access purposes. Supplementary services involved in MCA-Profile-4 are Call Diversion, Call Transfer, Single Step Call Transfer, Simple Dialog, Message Centre Monitoring, Mailbox Identification and Make Call Request.

4.9

Message Deposit The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox at a Message Centre.

4.9 .1

D irect M e ssage Depo sit The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox by directly calling the Message Centre, i.e. without a prior call to the Served User.

4.9 .2

M essage Depo sit a fter D iv ersion The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox if the Originator gets diverted to the Served User’s Mailbox.

- 5 -

4.9 .3

4.10

M essage Depo sit a fter Tra nsfer The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox if the Originator gets transferred to the Served User’s Mailbox.

Message Centre Monitoring The part of MCA describing how a Message Centre informs a Served User about the status and status changes of Messages in the Served User’s Mailbox.

4.11

Message Browsing The part of MCA describing how a Served User can contact a Message Centre to get access to the Served User’s Mailbox, for example; configuration update, message browsing or message deletion purposes.

4.12

Message Retrieval The part of MCA describing how a Served User can retrieve Messages from the Served User’s Mailbox.

4.13

Message Centre Transfer The part of MCA describing how a Served User can request the Message Centre to get connected (e.g. transferred) to the Originator of a specific Message or any other destination.

Acronyms APDU

Application Protocol Data Unit

ASN.1

Abstract Syntax Notation One

Basic Call

Supplementary Service Call Diversion

CISC

Call Independent Signalling Connection

Corporate telecommunication Network

Supplementary Service Call Transfer

DTMF

Dual Tone Multiple Frequency

Generic Functional protocol (for the support of supplementary services)

MCA

Message Centre Access

MCM

Supplementary Service Message Centre Monitoring

MCR

Supplementary Service Make Call Request

MID

Supplementary Service Mailbox Identification

MWI

Supplementary Service Message Waiting Indication

NFE

Network Facility Extension

PINX

Private Integrated services Network eXchange

PISN

Private Integrated Services Network

PNP

Private Numbering Plan

QSIG

Q reference point SIGnalling system

Requirements List

Supplementary Service Simple Dialog

Supplementary Service

SSCT

Supplementary Service Single Step Call Transfer

- 6 -

Specification framework

6.1

General Description This Standard describes the usage and interoperability of basic and supplementary services within a PISN for the purpose of Message Centre Access (MCA). MCA incorporates functionality for the use of accessing a Message Centre due to the following reasons: •

an Originator deposits a Message in the Mailbox of a Served User (Message Deposit);

•

a Message Centre informs a Served User about Messages in the Served User’s Mailbox (Message Centre Monitoring);

•

a Served User contacts the Message Centre to, for example, update configuration and browse or delete messages (Message Browsing);

•

a Served User contacts the Message Centre in order to retrieve messages stored in the Served User’s Mailbox (Message Retrieval);

•

a Served User contacts the Message Centre to request connection to the Originator of a Message or any other destination (Message Centre Transfer).

To obtain the functionality needed for these procedures, different Supplementary Services were standardised in the past. Some of these Supplementary Services have similar functionality (e.g. Message Waiting Indication and Message Centre Monitoring or Call Transfer and Single Step Call Transfer) that leads to a variety of different combinations of these services. To restrict the variety for interworking purposes and to allow a smooth migration from older services to newer ones, four different profiles were defined for MCA:

6.2

•

MCA-Profile-1 which makes use of Message Waiting Indication, Call Diversion and Call Transfer;

•

MCA-Profile-2 which makes use of Message Waiting Indication, Call Diversion, Simple Dialog, Call Transfer and Single Step Call Transfer;

•

MCA-Profile-3 which makes use of Message Centre Monitoring, Mailbox Identification, Call Diversion, Simple Dialog, Call Transfer and Single Step Call Transfer;

•

MCA-Profile-4 which makes use of Message Centre Monitoring, Mailbox Identification, Call Diversion, Simple Dialog, Make Call Request, Call Transfer, Single Step Call Transfer.

Scenarios

6.2 .1 M essage Depo sit 6.2 .1.1 D irect M e ssage Depo sit An Originating User may directly call a specific Message Centre to deposit a Message of a telecommunication service Message Type within the Mailbox of a specific Served User. Due to information received during call establishment, the Message Centre will connect the Originator to the indicated Mailbox, which then will provide further information either by means of B-Channel announcements or display information. NOTE The signalling information provided during call establishment may not be sufficient to identify the required Mailbox. In such cases the Message Centre will require more information from the Originator, e.g. the party number of the Served User for whom a Message is to be deposited, in order to identify the mailbox. After the Originator has deposited the Message, the Message Centre may either offer further services to the Originator or release the connection. Clearing of the connection is the responsibility of the Originator.

- 7 -

6.2 .1.2

M essage Depo sit a fter D iv ersion The call from an Originator to a Served User may be diverted to the Served User’s Mailbox, to allow the Originator to deposit a Message for the Served User. After the Originator has deposited the Message, the Message Centre may either offer further services to the Originator or release the connection. Clearing of the connection is the responsibility of the Originator.

6.2 .1.3

M essage Depo sit a fter Tra nsfer The call from an Originator may be transferred, e.g. by an attendant using Call Transfer or Single Step Call Transfer, to the Served User’s Mailbox to allow the Originator to deposit a Message for the Served User. After the Originator has deposited the Message, the Message Centre may either offer further services to the Originator or release the connection. Clearing of the connection is the responsibility of the Originator.

6.2 .2

M essage Centre Monito ring A Message Centre shall be able to inform the Served User about changes in the Served User’s Mailbox, e.g. after the receipt of a New Message or after a Message has been retrieved. The procedures needed for this functionality are defined in Message Waiting Indication and Message Centre Monitoring.

6.2 .3

M essage Bro wsing A Message Centre may be able to allow the Served User to browse through the messages in the Served User's mailbox regardless whether the messages are new or already retrieved. The procedures needed for this functionality are defined in Simple Dialog and Message Centre Monitoring. NOTE Procedures using DTMF and announcements may be required for certain profiles or if Simple Dialog and Message Centre Monitoring are not implemented.

6.2 .4

M essage Ret r ieva l A Message Centre shall be able to allow the Served User to retrieve messages from the Served User's mailbox. The procedures needed for this functionality are defined in Simple Dialog, Message Centre Monitoring and Make Call Request. NOTE Procedures using DTMF and announcements may be required for certain profiles or if Simple Dialog is not implemented.

6.2 .5

M essage Cen t r e T ra n s f e r A Message Centre may be able to connect the Served User to the Originator of a Message or any other destination. The procedures related to this functionality are defined in Call Transfer, Single Step Call Transfer and Make Call Request.

- 8 -

Profiles

7.1

MCA-Profile-1

7.1 .1 7.1 .1.1

M essage Depo sit Various message types may be accepted depending on the capabilities of the Message Centre. D irect M e ssage Depo sit Two procedures may be used in order to access the mailbox of the Served User: 1.

Direct Access: the Mailbox of the Served User is identified using the Served User's individual Party Number (or a Message Centre Party Number in combination with an individual Subaddress). NOTE The individual Party Number may consist of a prefix identifying the Message Centre and the Party Number of the Served User, e.g. if the Message Centre is identified by 1234 and Served User's Party Number is 9876, then a Called Party Number 12349876 may identify the Served User's mailbox at the Message Centre.

Indirect Access: the Originator sets up a call related connection to the Message Centre using the Complete Number of the Message Centre. The Message Centre uses announcements and the Calling User identifies the Served User's mailbox by sending DTMF.

After being connected to the Served User's Mailbox the Originator may deposit a message. The type of message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility Information Elements in the SETUP message. After deposit of a new message the Message Centre PINX shall send a mwiActivate invoke APDU to the Served User PINX according to ECMA-242. 7.1 .1.2

M essage Depo sit a fter D iv ersion After the Originator's call is diverted to the Message Centre, the Served User shall be identified using either information provided in element divertingNr or, in case of multiple diversion, in element originalCalledNr of the received divertingLegInformation2 invoke APDU. If both elements are present it is up to the implementation and/or administration of the Message Centre which mailbox is appropriate. After being connected to the Served User's Mailbox the Originator may deposit a message. The type of message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility Information Elements in the SETUP message. After deposit of a new message the Message Centre shall send a mwiActivate invoke APDU to the Served User PINX according to ECMA-242.

7.1 .1.3

M essage Depo sit a fter Tra nsfer In order to transfer the Originator to the Served User's mailbox the Transferring User establishes a Call to the Message Centre. The Served User's mailbox shall be identified using either of the procedures as described in 7.1.1.1. In either case, on receipt of a ctComplete invoke APDU, the Message Centre PINX shall stop any procedures for message deposit and/or announcements related to the call of the Transferring User and shall start new procedures for message deposit and/or give new announcements related to the call of the Originator. After being connected to the Served User's Mailbox the Originator may deposit a message. The type of message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility Information Elements in the SETUP message. After deposit of a new message the Message Centre shall send a mwiActivate invoke APDU to the Served User PINX according to ECMA-242.

- 9 -

7.1 .2

M essage Centre Monito ring The Message Centre and the Served User shall use procedures as described ECMA-242 for Message Centre Monitoring purposes.

7.1 .3

M essage Bro wsing In order to browse through messages the Served User shall establish a Basic Call (as defined in ECMA-143) with the Message Centre. The Served User may be requested to provide authentication to the Message Centre and shall then send the authentication using DTMF. The Message Centre shall indicate available messages and browsing options for the Served User by announcements. For message browsing the Message Centre shall act on DTMF provided by the Served User.

7.1 .4

M essage Ret r ieva l The Served User indicates the request for retrieval of a message via DTMF provided by the Served User using the already established Basic Call for Message Browsing. The Message Centre introduces the retrieved messages of type Basic Service (as defined in ECMA-242) in an appropriate form into the B-channel. The retrieval of other message types is out of the scope of this Standard. NOTE Other messages may be converted in a way appropriate to be introduced into the B-Channel, e.g. email may be announced to the Served User using an email-to-speech service.

7.1 .5

M essage Cen t r e T ra n s f e r The Served User may indicate the request for transfer to the Originator of a message or any other destination via DTMF provided by the Served User using the already established Basic Call for Message Browsing. If Address Information of the Originator is available, the Message Centre PINX shall set up the Secondary Call and shall act according to the procedures described in Call Transfer on receipt of an ALERTING or a CONNECT Message from the Originating PINX.

7.2

MCA-Profile-2 In addition to MCA-Profile-1, Simple Dialog shall be supported by the Message Centre PINX and the Served User PINX. Simple Dialog shall replace the procedures using DTMF and announcements described in 7.1. A Message Centre PINX and a Served User PINX complying with MCA-Profile-2 shall be capable of using DTMF and announcements as described in 7.1. This provides interoperability, if a Served User PINX complying with MCA-Profile-1 is connected to a Message Centre PINX complying with MCA-Profile-2, or vice versa.

7.2 .1

M essage Depo sit The same procedures as described in 7.1.1 for Message Deposit in MCA-Profile-1 shall apply. If Simple Dialog is supported by the Originating User PINX, then Simple Dialog shall replace the procedures using DTMF and announcements described in 7.1. NOTE Interworking between Simple Dialog and DTMF is not required and is outside the scope of this Standard.

7.2 .1.1

M essage Depo sit a fter Sing le- St ep Ca ll Transf er In order to transfer the Originator to the Served User's mailbox the Transferring User shall provide the Complete Number to identify the Served User’s mailbox. This Number is transported in element rerouteingNumber in the ssctInitiate invoke APDU, which is used for the Called Party Number IE in the SETUP message sent to the Message Centre. After being connected to the Served User's Mailbox the Originator may deposit a message. After deposit of a new message the Message Centre shall send a mwiActivate invoke APDU to the Served User PINX according to ECMA-242.

- 10 -

7.2 .2

M essage Centre Monito ring The same procedures as described in 7.1.2 for Message Centre Monitoring in MCA-Profile-1 shall apply.

7.2 .3

M essage Bro wsing The same procedures as described in 7.1.3 for Message Browsing in MCA-Profile-1 shall apply to connect the Served User to the Message Centre. The communication (including authentication) between Message Centre and Served User shall use Simple Dialog on the call reference of the call between Message Centre and Served User, if both Served User PINX and Message Centre PINX support MCA-Profile-2. Optionally, the Message Centre may assist the Served User using announcements. If either the Message Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not support Simple Dialog, then the PINX supporting MCA-Profile-2 shall fall back to procedures described in 7.1.3. NOTE Using DTMF and announcements may also be required if the Served User accesses the Served User's mailbox from the Public Network.

7.2 .4

M essage Ret r ieva l The Served User PINX shall indicate the request for retrieval of a message by sending an appropriate keypad invoke APDU to the Message Centre PINX. The Message Centre delivers the retrieved message using the Basic Call already established for Message Browsing. The Message Centre introduces the retrieved messages of type Basic Service (as defined in ECMA-242) in an appropriate form into the B-channel. The retrieval of other message types is outside the scope of this Standard. NOTE Other messages may be converted in a way appropriate to be introduced into the B-Channel, e.g. email may be announced to the Served User using an email-to-speech service. If either the Message Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not support Simple Dialog, then the PINX supporting MCA-Profile-2 shall fall back to procedures as described in 7.1.4.

7.2 .5 M essage Cen t r e T ra n s f e r 7.2 .5.1 M essage Centre Trans fer us ing S ing le Step Ca ll Tran sfer After browsing through the Served User's mailbox the Served User may indicate the request for transfer to the Originator of a message or any other destination via Simple Dialog using the already established call for Message Browsing. If Address Information of the Originator is available, the Message Centre PINX shall send a ssctInitiate invoke APDU transporting the Party Number of the Originator of the Message in element rerouteingNumber towards the Served User PINX. On receipt of a ssctInitiate.rej APDU from the Served User PINX the Message Centre PINX shall fall back to Call Transfer procedures as described in 7.2.5.2. 7.2 .5.2

M essage Centre Transfer using Call Transfer The same procedures as described in 7.1.5 for Message Centre Transfer in MCA-Profile-1 shall apply, except that the communication between Message Centre and Served User shall use Simple Dialog, if both, Served User PINX and Message Centre PINX support Profile 2. If either the Message Centre PINX or the Served User PINX support only Profile 1, then the PINX supporting Profile 2 shall use fall back to procedures as described in 7.1.5.

- 11 -

7.3

MCA-Profile-3 Message Waiting Indication shall be replaced by Message Centre Monitoring (ECMA-347) in MCA-Profile-3. Mailbox Identification shall be supported at the Message Centre PINX and may be supported at the Served User PINX. Simple Dialog shall be supported as described in 7.2. A Message Centre PINX and a Served User PINX complying with MCA-Profile-3 shall be capable of using DTMF and announcements as described in 7.1. This provides interoperability if Simple Dialog is not implemented at the PINX where the Originator of a message is located. Provision of DTMF and announcements may offer a reduced functionality if Served Users access their mailbox from the public network (for example). NOTE Interworking between Simple Dialog and DTMF is not required and therefore outside of scope of this Standard.

7.3 .1

M essage Depo sit The same procedures as described in 7.2.1 for Message Deposit in MCA-Profile-2 shall apply, despite that Message Centre shall send a mCMNewMsg invoke APDU towards the Served User PINX according to Message Centre Monitoring instead of a mwiActivate invoke APDU according to Message Waiting Indication. If the Served User owns more than one mailbox at the Message Centre, the Message Centre PINX shall identify the specific mailbox by sending a mIDMailboxID invoke APDU and shall send the mCMNewMsg invoke APDU after receipt of the mIDMailboxID return result APDU.

7.3 .2

M essage Centre Monito ring The Message Centre and the Served User shall use procedures as described in ECMA-347 for Message Centre Monitoring purposes. If a Served User owns more than one mailbox at a Message Centre: -

the Message Centre PINX shall identify the specific mailbox by sending a mIDMailboxID invoke APDU. On receipt of a mIDMailboxID return result APDU, the Message Centre PINX shall send the APDUs defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the latest mIDMailboxID invoke APDU;

the Served User PINX shall identify the specific mailbox by sending a mIDMailboxAuth invoke APDU. After sending of the mIDMailboxAuth return result APDU, the Message Centre PINX shall send the APDUs defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the latest mIDMailboxAuth invoke APDU.

If an APDU refers to a new mailbox, then a mIDMailboxID/mIDMailboxAuth invoke APDU shall be sent before this APDU and the APDUs defined in Message Centre Monitoring shall be sent after receipt of the mIDMailboxID/mIDMailboxAuth return result APDU. 7.3 .3

M essage Bro wsing The same procedures as described in Message Centre Monitoring (ECMA-347) shall apply. Optionally, the Message Centre may assist the Served User using announcements. If either the Message Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not support Simple Dialog, then the PINX supporting MCA-Profile-3 shall fall back to procedures described in 7.1.3. NOTE Using DTMF and announcements may also be required if Served Users access their mailbox from the Public Network (for example). For authentication purposes the Served User shall use Mailbox Identification, if available at the Served User PINX. If Mailbox Identification is not available at the Served User PINX, Simple Dialog may be used instead. If a Served User owns more than one mailbox at a Message Centre: -

the Message Centre PINX shall identify the specific mailbox by sending a mIDMailboxID invoke APDU. On receipt of a mIDMailboxID return result APDU, the Message Centre PINX shall send the

- 12 -

APDUs defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the latest mIDMailboxID invoke APDU; -

the Served User PINX shall identify the specific mailbox by sending a mIDMailboxAuth invoke APDU. After sending of a mIDMailboxAuth return result APDU, the Message Centre PINX shall send the APDUs defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the latest mIDMailboxAuth invoke APDU.

If an APDU refers to a new mailbox, then a mIDMailboxID/mIDMailboxAuth invoke APDU shall be sent before this APDU and the APDUs defined in ECMA-347 shall be sent after receipt of the mIDMailboxID/mIDMailboxAuth return result APDU. 7.3 .4

M essage Ret r ieva l The same procedures as described in 7.2.4 for Message Deposit in MCA-Profile-2 shall apply.

7.3 .5

M essage Cen t r e T ra n s f e r The same procedures as described in 7.2.5 for Message Centre Transfer in MCA-Profile-2 shall apply.

7.4

MCA-Profile-4 In addition to MCA-Profile-3, Make Call Request shall be supported by the Message Centre PINX and the Served User PINX. This allows a communication between the Message Centre PINX and the Served User PINX, which only requires a CISC (Call Independent Signalling Connection). A B-channel, required for message retrieval, can be allocated dynamically and on-demand using Make Call Request. A Message Centre PINX and a Served User PINX complying with MCA-Profile-4 shall be capable of using DTMF and announcements as described in 7.1. This provides interoperability if Simple Dialog is not implemented at the PINX where the Originator of a message is located. Provision of DTMF and announcements may offer a reduced functionality, if the Served Users access their mailbox from the public network (for example).

7.4 .1

M essage Depo sit The same procedures as described in 7.3.1 for Message Deposit in MCA-Profile-3 shall apply.

7.4 .2

M essage Centre Monito ring The same procedures as described in 7.3.2 for Message Centre Monitoring in MCA-Profile-3 shall apply.

7.4 .3

M essage Bro wsing In order to browse through new and/or retrieved messages the Served User shall establish or use an already existing call independent signalling connection to the Message Centre. For authentication purposes the Served User shall use Mailbox Identification, if available at the Served User PINX. If Mailbox Identification is not available at the Served User PINX, Simple Dialog may be used instead as specified in 7.3.3. The communication between Message Centre and Served User shall use Simple Dialog. The Message Centre shall indicate the available messages for the Served User using Message Centre Monitoring. The Served User shall indicate actions to be taken on a specific message by sending one or more keypad invoke APDUs to the Message Centre. Optionally, the Message Centre may assist the Served User using announcements. In order to provide such announcements the Message Centre shall request the Served User PINX to provide a User Information Channel using Make Call Request as described in 7.4.4. The call independent signalling connection shall be retained for the duration of the browsing session and may be retained for further communication between the Message Centre and the Served User (e.g. for Message Retrieval).

7.4 .4

M essage Ret r ieva l In order to retrieve a message the Served User shall establish or use an already existing call independent signalling connection to the Message Centre. If not already authenticated, Served Users may authenticate themselves to the Message Centre using Mailbox Identification or Simple Dialog as specified in 7.3.4. The Served User PINX responds to a request for message retrieval by sending an appropriate indication in a keypad invoke APDU as specified in Simple Dialog towards the Message Centre PINX.

- 13 -

In order to establish a B-Channel necessary for message retrieval, the Message Centre shall request the Served User PINX to provide a B-Channel using Make Call Request. The Message Centre PINX shall send a mcRequest invoke APDU to the Served User PINX. The mcRequest invoke APDU shall be provided with: •

element calltype set to a value appropriate for the message type of the message to be retrieved,

•

element destinationAddress set to the Party Number of the Message Centre PINX or the Party Number identifying the Served User's mailbox as defined for message deposit in 7.1.1.1,

•

element correlation in order to allow the correlation of the B-Channel connection to the call independent signalling connection used for communication between Message Centre and Served User.

Clearing of the B-channel connection is the responsibility of the Message Centre. The call independent signalling connection may be retained for further communication between the Message Centre and the Served User (e.g. for Message Browsing). 7.4 .5

7.4 .5.1

M essage Cen t r e T ra n s f e r For transfer using Call Transfer or Single Step Call Transfer the same procedures as described in 7.2.5 for MCA-Profile-2 shall apply. M essage Centre Transfer using Make Ca ll Request The Served User may request transfer (e.g. after browsing) to the Originator of a message or any other destination via Simple Dialog using a new or existing call independent signalling connection to the Message Centre. If Address Information of the Originator is available, the Message Centre PINX shall send a mcRequest invoke APDU to the Served User PINX. The mcRequest invoke APDU shall be provided with: •

element calltype set to an appropriate value,

•

element clearOrigCall shall be omitted implying retention of the call independent signalling connection,

•

element destinationAddress set to the Party Number of the Originator,

•

element correlation in order to allow the correlation of the call to the Originator with the call independent signalling connection used for communication between Message Centre and Served User.

After release of, or during, the requested call to the Originator the communication between the Message Centre and the Served User may continue using Simple Dialog and/or Message Centre Monitoring. A refresh of the Served User's display may be required due to implementation-specific scenarios. The call independent signalling connection may be retained for further communication between the Message Centre and the Served User.

- 14 -

- 15 -

Annex A (nor ma tiv e)

Requirements List (RL)

A.1

General Use of this Standard imposes requirements on the implementation that go beyond those of the base standards referred to by this Standard. These result in modifications to the requirements expressed in the PICS proformas for the base standards. This annex specifies the modifications (the Requirements List - RL) that apply to the status of the items affected in each PICS proforma, with consequently modified requirements on the answers to be provided. The status notation used in this annex is that defined in ISO/IEC 9646-7. In summary, the meaning of the notations is as follows: i

Irrelevant or out-of-scope - this capability is outside the scope of this profile and is not subject to conformance testing in this context.

Mandatory - the capability is required to be supported.

n/a

Not Applicable - in the given context, it is impossible to use the capability.

Optional - the capability may be supported or not.

o.i

qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer that identifies an unique group of related optional items and the logic of their selection, defined below the table.

eXcluded or prohibited - there is a requirement not to support this capability in this profile.

The Requirements List in this annex shall be used to restrict the permitted support answers in the corresponding PICS.

A.2

Relationship between RL and corresponding PICS proformas In the context of the profile specification contained in this Standard, PICS proformas of the base protocol standards contain tables in 3 categories. The 3 categories are: -

Those proforma tables where this profile does not restrict the permitted support answers;

Those proforma tables where this profile restricts the permitted support answers;

Those proforma tables that are not relevant to this profile.

The Requirements List consists of the tables falling into the second category, with an indication of the modified items in those tables.

- 16 -

A.3

Requirement List

A.3 .1

Tables for P rofile 1 Item

Question/Feature

Reference

Profile Status

P1.M

Behaviour as Message Centre PINX according to MCA-Profile-1

7.1

o.1

P1.S

Behaviour as Served User PINX according to MCA-Profile-1

7.1

o.1

A.3 .1.1 S uppo rt of S upp lementa ry S e rv ices Item

Question/Feature

Reference

Profile Status

P1.1

Support of SS-MWI at Message Centre PINX

ECMA-242

P1.M:m

P1.2

Support of SS-MWI at Served User PINX

ECMA-242

P1.S:m

P1.3

Support of SS-DIV at Message Centre PINX

ECMA-174

P1.M:m

P1.4

Support of SS-DIV at Served User PINX

ECMA-174

P1.S:m

P1.5

Support of SS-CT at Message Centre PINX

ECMA-178

P1.M:m

P1.6

Support of SS-CT at Served User PINX

ECMA-178

P1.S:m

Protocol Status

Profile Status

A.3 .1.2 S upp le me nta ry S e rv ic e M es sag e Wa it ing I nd icat ion Item number and references refer to annex A of ECMA-242. A.3 .1.2.1 Genera l Item

Question/Feature

Reference

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

o.1

P1.M:m

Behaviour as Message Centre PINX for interrogation of SS-MWI

A1:o

P1.M:o

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

o.1

P1.S:m

Behaviour as Served User PINX for interrogation of SS-MWI

A3:o

P1.S:o

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

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

- 17 -

A.3 .1.2.2 Pro cedures Item

Question/Feature

Reference

Protocol Status

Profile Status

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

6.2.1

A1:m

P1.M:m

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

6.2.2

A3:m

P1.S:m

Procedures at the Message Centre PINX for activation and deactivation

6.5.1

A1:m

P1.M:m

Procedures at the Message Centre PINX for interrogation

6.5.1

A2:m

Procedures at the Served User PINX for activation and deactivation

6.5.2

A3:m

P1.S:m

Procedures at the Served User PINX for interrogation

6.5.2

A4:m

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

6.6.1

A5:m

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

6.6.2

A6:m

Reference

Protocol Status

Profile Status

A.3 .1.2.3 Coding Item

Question/Feature

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

6.3.1

A1:m

P1.M:m

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

6.3.1

A3:m

P1.S:m

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

6.3.1

A1:m

P1.M:m

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

6.3.1

A3:m

P1.S:m

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

6.3.1

A4:m

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

6.3.1

A2:m

- 18 -

A.3 .1.2.4 Timers Item

Question/Feature

Reference

Protocol Status

Profile Status

Support of timer T1

6.9.1

A1:m

P1.M:m

Support of timer T2

6.9.2

A4:m

Protocol Status

Profile Status

A.3 .1.3 Supplementa ry Serv ic e Ca ll D iversio n Item numbers and references refer to annex A of ECMA-174. A.3 .1.3.1 Genera l Item

Question/Feature

Reference

Support of SS-CFU

o.1

Support of SS-CFB

o.1

Support of SS-CFNR

o.1

Support of SS-CDI

o.1

Support of SS-CDA

o.1

Behaviour as Originating PINX

o.2

Behaviour as Terminating PINX

o.2

Behaviour as Transit PINX

o.2

Behaviour as Incoming Gateway PINX

o.2

A10

Behaviour as Outgoing Gateway PINX

o.2

- 19 -

A.3 .1.3.2 Pro cedures Item

Question/Feature

Reference

Protocol Status

Profile Status

B1 B2 B3

Procedures at the Originating PINX Procedures at the Transit PINX Procedures at the Rerouteing PINX

6.5.1 6.5.2 6.5.4

A6:m A8:m c.1

i i P1.S:m

Procedures at the Served User PINX activation

6.5.3.1.1 6.5.3.2.1 6.5.3.1.2 6.5.3.2.2 6.5.3.1.3 6.5.3.2.3 6.5.3.1.4 6.5.3.2.4 6.5.3.1.5 6.5.3.2.5 6.5.5.1.1 6.5.5.2.1

A7:o

Procedures at the Served User PINX deactivation

A7:o

Procedures at the Served User PINX interrogation

A7:o

B7 B8

Procedures at the Served User PINX verification of diverted-to number Procedures at the Served User PINX invocation

A7:o

P1.S:o

A7:m

P1.S:m

Procedures at the Diverted-to PINX invocation

A7:m

P1.M:m

B10

Procedures at the Diverted-to PINX verification of diverted-to number

6.5.5.1.2 6.5.5.2.2

A7:o

P1.M:o

B11

Procedures at the Activating PINX

6.5.6

B12

Procedures at the Deactivating PINX

6.5.7

B13

Procedures at the Interrogation PINX

6.5.8

B14

Procedures at the Incoming Gateway PINX to public ISDN, diverting within the PISN

6.6.1.1

A9:m

B15

Procedures at the Incoming Gateway PINX, diverting within the public ISDN

6.6.1.2

A9:m

B16

Procedures at the Incoming Gateway PINX to public ISDN, partial rerouteing

6.6.1.3

A9:o

B17

Procedures at the Outgoing Gateway PINX to public ISDN, diverting within the PISN

6.6.2.1

A10:m

B18

Procedures at the Outgoing Gateway PINX. diverting within the public ISDN

6.6.2.2

A10:m

B19

Procedures at the Incoming Gateway PINX to another network (Non-ISDN)

6.7.1

A9:o

B20

Procedures at the Outgoing Gateway PINX to another network (Non-ISDN)

6.7.2

A10:o

c.1:

if A6 or A9 then mandatory else if A7 then optional else N/A

- 20 -

A.3 .1.3.3 Coding Item

Question/Feature

Reference

Protocol Status

Profile Status

Sending of redirectionName element in divertingLegInformation3 APDU

6.3.1

B9:o

P1.M:o

Receipt of redirectionName element in divertingLegInformation3 APDU

6.3.1

B1:o

Sending of redirectingName element in callRerouteing and divertingLegInformation2 APDUs Receipt of redirectingName element in callRerouteing and divertingLegInformation2 APDUs Sending of originalCalledName element in callRerouteing and divertingLegInformation2 APDUs Receipt of originalCalledName element in callRerouteing and divertingLegInformation2 APDUs Sending of activateDiversionQ invoke APDU and receipt of return result and return error APDUs

6.3.1

c.2

6.3.1

c.3

6.3.1

c.2

6.3.1

c.3

6.3.1

B11:m

Receipt of activateDiversionQ invoke APDU and sending of return result and return error APDUs

6.3.1

B4:m

Sending of deactivateDiversionQ invoke APDU and receipt of return result and return error APDUs

6.3.1

B12:m

C10

Receipt of deactivateDiversionQ invoke APDU and sending of return result and return error APDUs Sending of interrogateDiversionQ invoke APDU and receipt of return result and return error APDUs

6.3.1

B5:m

6.3.1

B13:m

Receipt of interrogateDiversionQ invoke APDU and sending of return result and return error APDUs Sending of checkRestriction invoke APDU and receipt of return result and return error APDUs

6.3.1

B6:m

6.3.1

B7:m

Receipt of checkRestriction invoke APDU and sending of return result and return error APDUs

6.3.1

B10:m

C11 C12

C13 C14

- 21 -

Item

Question/Feature

Reference

Protocol Status

Profile Status

C15

Sending of callRerouteing invoke APDU and receipt of return result and return error APDUs

6.3.1

B8:m

P1.S:m

C16

Receipt of callRerouteing invoke APDU and sending of return result and return error APDUs

6.3.1

B3:m

C17

Sending of divertingLegInformation1 invoke APDU

6.3.1

B3:m

C18

Receipt of divertingLegInformation1 invoke APDU

6.3.1

B1:m

C19

Sending of divertingLegInformation2 invoke APDU

6.3.1

B3:m

C20

Receipt of divertingLegInformation2 invoke APDU

6.3.1

B9:m

C21

Sending of divertingLegInformation3 invoke APDU

6.3.1

B9:m

C22

Receipt of divertingLegInformation3 invoke APDU

6.3.1

B1:m

C23

Sending of cfnrDivertedLegFailed invoke APDU

6.3.1

c.4

C24

Receipt of cfnrDivertedLegFailed invoke APDU

6.3.1

c.5

C25

Sending of Notification indicator containing "call is diverted" or embedded Redirection number information element Recognition of "call is diverted" notification and embedded Redirection number information element in received Notification information element

6.3.2.2

c.6

6.3.2.2

c.7

C26

c.2 c.3 c.4 c.5 c.6 c.7

if B3 or B8 then optional, else N/A if B3 or B9 then optional, else N/A if B3 and A3 then mandatory, else N/A if B8 and A3 then mandatory, else N/A if B18 or B20 then mandatory, else N/A if B1 or B14 or B19 then optional, else N/A

- 22 -

A.3 .1.3.4 Timers Item

Question/Feature

Reference

Protocol Status

Profile Status

D1 D2 D3 D4 D5

Support of timer T1 Support of timer T2 Support of timer T3 Support of timer T4 Support of timer T5

6.8.1 6.8.2 6.8.3 6.8.4 6.8.5

B8:m B11:m B12:m B13:m B7:m

B8:m i i i B7:m

- 23 -

A.3 .1.4 Supplementa ry S e rv ic e Ca ll Tran sf er Item numbers and references refer to annex A of ECMA-178. A.3 .1.4.1 Genera l Item

Question/Feature

A1 A2

Reference

Protocol Status

Profile Status

Support of SS-CT by join

Support of SS-CT by rerouteing

Reference

Protocol Status

Profile Status

A.3 .1.4.2 Pro cedures fo r SS-C T-Jo in Item

Question/Feature

Support of relevant ECMA-143 and ECMA-165 procedures

6.2

Signalling procedures at a Transferring PINX

6.5.1.1, 6.5.1.2

Signalling procedures at a Transferring PINX for interworking with a non-ISDN

6.7.2

Signalling procedures at a Primary PINX

6.5.2.1, 6.5.2.2, 6.5.5

Signalling procedures at a Secondary PINX

6.5.3.1, 6.5.3.2, 6.5.5

Behaviour as Gateway PINX to a public ISDN to support transfer of users in the ISDN by a user in the PISN

6.6.1.1

Behaviour as Gateway PINX to a public ISDN to support transfer of users in the PISN by a user in the ISDN

6.6.1.2

Behaviour as Gateway PINX to a non-ISDN to support transfer of users in the other network by a user in the PISN

6.7.1.1

Behaviour as Gateway PINX to a non-ISDN to support transfer of users in the PISN by a user in the other network

6.7.1.2

- 24 -

A .3 .1 .4 .3 A d d it io na l p ro ce du re s f o r S S- C T-R ero ute i ng Item

Question/Feature

Reference

Protocol Status

Profile Status

Signalling procedures at a Transferring PINX

6.5.1.3, 6.5.1.4

A2:m

Signalling procedures at a Primary PINX

6.5.2.3, 6.5.2.4, 6.5.5

A2:m

Signalling procedures at a Secondary PINX

6.5.3.3, 6.5.3.4, 6.5.5

A2:m

Behaviour as Gateway PINX to a public ISDN to support transfer of users in the ISDN by a user in the PISN (using transfer by rerouteing in the PISN)

6.6.1.1

Behaviour as Gateway PINX to a non-ISDN to support transfer of users in the other network by a user in the PISN (using transfer by rerouteing procedures)

6.7.1.1

Behaviour as Gateway PINX to a non-ISDN to support transfer of users in the PISN by a user in the other network (using transfer by rerouteing procedures)

6.7.1.3

- 25 -

A.3 .1.4.4 Coding Item

Question/Feature

Reference

Protocol Status

Profile Status

Sending of callTransferComplete invoke APDU

6.3

Sending of callTransferActive invoke APDU

6.3

Receipt of callTransferComplete invoke APDU

6.3

Receipt of callTransferActive invoke APDU

6.3

Sending of callTransferUpdate invoke APDU

6.3

Receipt of callTransferUpdate invoke APDU

6.3

Sending of subaddressTransfer invoke APDU

6.3

Receipt of subaddressTransfer invoke APDU

6.3

Sending of callTransferIdentify invoke APDU and receipt of return result and return error APDUs

6.3

A2:m

D10

Sending of callTransferInitiate invoke APDU and receipt of return result and return error APDUs

6.3

A2:m

D11

Sending of callTransferSetup invoke APDU and receipt of return result and return error APDUs

6.3

A2:m

D12

Receipt of callTransferIdentify invoke APDU and sending of return result and return error APDUs

6.3

A2:m

D13

Receipt of callTransferInitiate invoke APDU and sending of return result and return error APDUs

6.3

A2:m

D14

Receipt of callTransferSetup invoke ADPU and sending of return result and return error APDUs

6.3

A2:m

D15

Sending of callTransferAbandon invoke APDU

6.3

A2:m

D16

Receipt of callTransferAbandon invoke APDU

6.3

A2:m

- 26 -

A.3.2

Tables for Profile 2 Item

Question/Feature

Reference

Profile Status

P2.M

Behaviour as Message Centre PINX according to MCA-Profile-2

7.2

o.1

P2.S

Behaviour as Served User PINX according to MCA-Profile-2

7.2

o.1

A.3 .2.1 S uppo rt of S upp lementa ry S e rv ices Item

Question/Feature

Reference

Profile Status

P2.1

Support of SS-MWI at Message Centre PINX

ECMA-242

P2.M:m

P2.2

Support of SS-MWI at Served User PINX

ECMA-242

P2.S:m

P2.3

Support of SS-SD at Message Centre PINX

ECMA-311

P2.M:m

P2.4

Support of SS-SD at Served User PINX

ECMA-311

P2.S:m

P2.5

Support of SS-DIV at Message Centre PINX

ECMA-174

P2.M:m

P2.6

Support of SS-DIV at Served User PINX

ECMA-174

P2.S:m

P2.7

Support of SS-SSCT at Message Centre PINX

ECMA-300

P2.M:m

P2.8

Support of SS-SSCT at Served User PINX

ECMA-300

P2.S:o

P2.9

Support of SS-CT at Message Centre PINX

ECMA-178

P2.M:m

P2.10

Support of SS-CT at Served User PINX

ECMA-178

P2.S:m

Protocol Status

Profile Status

A.3 .2.2 S upp le me nta ry S e rv ic e M es sag e Wa it ing I nd icat ion As specified in A.3.1.2. A.3 .2.3 Supplementa ry Serv ic e Simple D ialog Item number and references refer to annex A of ECMA-311. A.3 .2.3.1 Genera l Item

Question/Feature

Reference

Behaviour as Client User PINX for SS-SD

o.1

P2.4:m

Behaviour as Server User PINX for SS-SD

o.1

P2.3:m

Behaviour as Incoming Gateway PINX for interworking with a public ISDN for SS-SD

Behaviour as Outgoing Gateway PINX for interworking with a public ISDN for SS-SD

- 27 -

A.3 .2.3.2 Pro cedures Item

Question/Feature

Reference

Protocol Status

Profile Status

Support of relevant ECMA-143 and ECMA-165 procedures at the Client User PINX

6.2.1

A1:m

Support of relevant ECMA-143 and ECMA-165 procedures at the Server User PINX

6.2.2

A2:m

Procedures at the Client User PINX for invocation and operation

6.5.1

A1:m

Procedures at the Server User PINX for invocation and operation

6.5.2

A2:m

Procedures at an Incoming Gateway PINX for interworking with a public ISDN for invocation and operation of SS-SD

6.6.1

A3:m

Procedures at an Outgoing Gateway PINX for interworking with a public ISDN for invocation and operation of SS-SD

6.6.2

A4:m

Reference

Protocol Status

Profile Status

A.3 .2.3.3 Coding Item

Question/Feature

Sending of display invoke APDU from the Server User PINX

6.3.1

A2:m

Receipt of display invoke APDU at the Client User PINX and sending of display return error APDU in case of an error indication

6.3.1

A1:m

Sending of keypad invoke APDU from the Client User PINX

6.3.1

A1:m

Receipt of keypad invoke APDU at the Server User PINX

6.3.1

A2:m

A.3 .2.4 Supplementa ry Serv ic e Ca ll D iversio n As specified in A.3.1.3. A.3 .2.5 Supplementa ry S e rv ic e Ca ll Tran sf er As specified in A.3.1.4.

- 28 -

A.3 .2.6 S upp lementa ry S e rv ice S ing le-St ep Ca ll Tra ns fer Item numbers and references refer to annex A of ECMA-300. A.3 .2.6.1 Genera l Item

Question/Feature

Reference

Protocol Status

Profile Status

Behaviour as a Transferring PINX

o.1

P2.M:m

Behaviour as a Rerouting PINX

o.1

Behaviour as a Transferred PINX

o.1

P2.S:m

Behaviour as a Transferred-To PINX

o.1

P2.M:m

Behaviour as Gateway PINX to a public ISDN for SS-SSCT

Behaviour as Gateway PINX to a non-ISDN for SS-SSCT

Reference

Protocol Status

Profile Status

A.3 .2.6.2 Pro cedures Item

Question/Feature

Support of relevant ECMA-143 and ECMA-165 procedures

6.2

Signalling procedures at a Transferring PINX

6.5.1

A1:m

Signalling procedures at a Rerouting PINX

6.5.2

A2:m

Signalling procedures at a Transferred PINX

6.5.3, 6.5.5

A3:m

Signalling procedures at a Transferred-To PINX

6.5.4, 6.5.5

A4:m

Interworking procedures to a public ISDN at a Transferred PINX

6.6.1.1

A5:o.2

Interworking procedures to a public ISDN at a Transferred-To PINX

6.6.1.2

A5:o.2

Interworking procedures to a non-ISDN at a Transferred PINX

6.7.1.1

A6:o.3

Interworking procedures to a non-ISDN at a Transferred-To PINX

6.7.1.2

A6:o.3

B10

Transfer occurs on alerting new call

6.5.1.1

A1:o.4

B11

Transfer occurs on active new call

6.5.1.1

A1:o.4

- 29 -

A.3 .2.6.3 Coding Item

Question/Feature

Reference

Protocol Status

Profile Status

Sending of ssctInitiate invoke APDU and receipt of return result and return error APDUs

6.3

A1:m

Receipt of ssctInitiate invoke APDU and sending of return result and return error APDUs

6.3

A2:m

Sending of ssctSetup invoke APDU

6.3

A2:m

Receipt of ssctSetup invoke APDU

6.3

A4:m

Sending of ssctPostDial invoke APDU

6.3

A2:o

Receipt of ssctPostDial invoke APDU

6.3

A3:m

Sending of ssctDigitInfo invoke APDU

6.3

A3:m

Receipt of ssctDigitInfo invoke APDU

6.3

A2:m

Sending of callTransferComplete invoke APDU

6.3

A2:m

C10

Receipt of callTransferComplete invoke APDU

6.3

A3:m

C11

Sending of callTransferActive invoke APDU

6.3

A2:m

C12

Receipt of callTransferActive invoke APDU

6.3

A3:m

C13

Sending of callTransferUpdate invoke APDU

6.3

c.1

C14

Receipt of callTransferUpdate invoke APDU

6.3

c.2

C15

Sending of subaddressTransfer invoke APDU

6.3

c.1

C16

Receipt of subaddressTransfer invoke APDU

6.3

c.2

Reference

Protocol Status

Profile Status

c.1: If (A3 or A4) then optional, else N/A c.2: If (A3 or A4) then mandatory, else N/A A.3 .2.6.4 Timers Item

Question/Feature

Timer T1

6.9.1

A1:m

Timer T2

6.9.2

A2:o

Timer T3

6.9.3

A2:m

- 30 -

A.3.3

Tables for Profile 3 Item

Question/Feature

Reference

Profile Status

P3.M

Behaviour as Message Centre PINX according to MCA-Profile-3

7.3

o.1

P3.S

Behaviour as Served User PINX according to MCA-Profile-3

7.3

o.1

A.3 .3.1 S uppo rt of S upp lementa ry S e rv ices Item

Question/Feature

Reference

Profile Status

P3.1

Support of SS-MWI at Message Centre PINX

ECMA-242

i (NOTE)

P3.2

Support of SS-MWI at Served User PINX

ECMA-242

i (NOTE)

P3.3

Support of SS-MCM at Message Centre PINX

ECMA-347

P3.M:m

P3.4

Support of SS-MCM at Served User PINX

ECMA-347

P3.S:m

P3.5

Support of SS-MID at Message Centre PINX

ECMA-347

P3.M:m

P3.6

Support of SS-MID at Served User PINX

ECMA-347

P3.S:o

P3.7

Support of SS-SD at Message Centre PINX

ECMA-311

P3.M:m

P3.8

Support of SS-SD at Served User PINX

ECMA-311

P3.S:m

P3.9

Support of SS-DIV at Message Centre PINX

ECMA-174

P3.M:m

P3.10

Support of SS-DIV at Served User PINX

ECMA-174

P3.S:m

P3.11

Support of SS-SSCT at Message Centre PINX

ECMA-300

P3.12

Support of SS-SSCT at Served User PINX

ECMA-300

P3.13

Support of SS-CT at Message Centre PINX

ECMA-178

P3.14

Support of SS-CT at Served User PINX

ECMA-178

Protocol Status

Profile Status

NOTE MWI is an inherent part of MCM. A.3 .3.2 Supplementa ry Serv ic e Simple D ialog As specified in A.3.2.3. A.3 .3.3 S upp le me nta ry S e rv ic e M es sag e Ce nt re Mon ito r ing Item numbers and references refer to annex A.3 of ECMA-347. A.3 .3.3.1 Genera l Item

Question/feature

Reference

Behaviour as a Message Centre PINX for SS-MCM

o.1

P3.M:m

Behaviour as a Served User PINX for SS-MCM

o.1

P3.S:m

- 31 -

A.3 .3.3.2 Pro cedures Item

Question/feature

Reference

Protocol Status

Profile Status

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

6.2.1

A1:m

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

6.2.2

A2:m

Procedures at the Message Centre PINX for activation and deactivation of monitoring messages for specific Message Types

6.5.1

A1:o

Procedures at the Message Centre PINX for interrogation of current monitoring configuration

6.5.1

A1:o

Procedures at the Message Centre PINX for the arrival of new messages

6.5.1

A1:m

Procedures at the Message Centre PINX for indicating no New Messages of a specific Message Type are available

6.5.1

A1:m

Procedures at the Message Centre PINX for an update of Message Centre information

6.5.1

A1:m

Procedures at the Message Centre PINX for an update request of Message Centre information

6.5.1

A1:m

Procedures at the Message Centre PINX for a mailbox-full indication

6.5.1

A1:o

B10

Procedures at the Served User PINX for activation and deactivation of monitoring messages for specific Message Types

6.5.2

A2:o

B11

Procedures at the Served User PINX for interrogation of current monitoring configuration

6.5.2

A2:o

B12

Procedures at the Served User PINX for the arrival of new messages

6.5.2

A2:m

B13

Procedures at the Served User PINX for indicating no New Messages of a specific Message Type are available

6.5.2

A2:m

B14

Procedures at the Served User PINX for an update of Message Centre information

6.5.2

A2:m

B15

Procedures at the Served User PINX for an update request of Message Centre information

6.5.2

A2:m

B16

Procedures at the Served User PINX for a mailbox-full indication

6.5.2

A2:o

- 32 -

A.3 .3.3.3 Coding Item

Question/feature

Reference

Protocol Status

Profile Status

sending of mCMNewMessage invoke APDU and receiving of mCMNewMessage return result or return error APDU

6.3.1

A1:m

receipt of mCMNewMessage invoke APDU and sending of mCMNewMessage return result or return error APDU

6.3.1

A2:m

sending of mCMNoNewMessage invoke APDU and receiving of mCMNoNewMessage return result or return error APDU

6.3.1

A1:m

receipt of mCMNoNewMessage invoke APDU and sending of mCMNoNewMessage return result or return error APDU

6.3.1

A2:m

sending of mCMUpdate invoke APDU and receiving of mCMUpdate return result or return error APDU

6.3.1

A1:m

receipt of mCMUpdate invoke APDU and sending of mCMUpdate return result or return error APDU

6.3.1

A2:m

receipt of mCMUpdateReq invoke APDU and sending of mCMUpdateReq return result or return error APDU

6.3.1

A1:m

sending of mCMUpdateReq invoke APDU and receiving of mCMUpdateReq return result or return error APDU

6.3.1

A2:m

receipt of mCMService invoke APDU and sending of mCMService return result or return error APDU

6.3.1

B3:m

C10

sending of mCMService invoke APDU and receiving of mCMService return result or return error APDU

6.3.1

B9:m

C11

receipt of mCMInterrogate invoke APDU and sending of mCMInterrogate return result or return error APDU

6.3.1

B4:m

C12

sending of mCMInterrogate invoke APDU and receiving of mCMInterrogate return result or return error APDU

6.3.1

B10:m

C13

sending of mCMailboxFull invoke APDU

6.3.1

B8:m

C14

receipt of mCMailboxFull invoke APDU

6.3.1

B14:m

- 33 -

A.3 .3.3.4 Timers Item

Question/feature

Reference

Protocol Status

Profile Status

Support of timer T1

6.9.1

A1:m

Support of timer T2

6.9.2

A2:m

Support of timer T3

6.9.3

A2:m

Protocol Status

Profile Status

A.3 .3.4 S upp le me nta ry S e rv ic e M es sag e Ce nt re I de ntif icat ion Item numbers and references refer to annex A.4 of ECMA-347. A.3 .3.4.1 Genera l Item

Question/feature

Reference

Behaviour as Message Centre PINX for SS-MID

o.1

P3.M:m

Behaviour as Served User PINX for SS-MID

o.1

P3.S:o

Reference

Protocol Status

Profile Status

A.3 .3.4.2 Pro cedures Item

Question/feature

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

7.2.1

A1:m

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

7.2.2

A2:m

Procedures at the Message Centre PINX for identification of Served User mailboxes

7.5.1

A1:o.2

Procedures at the Message Centre PINX for authentication of a Served User at his/her mailbox

7.5.1

A1:o.2

Procedures at the Served User PINX for identification of Served User mailboxes

7.5.2

A2:o.3

Procedures at the Served User PINX for authentication of a Served User at his/her mailbox

7.5.2

A2:o.3

- 34 -

A.3 .3.4.3 Coding Item

Question/feature

Reference

Protocol Status

Profile Status

sending of mIDMailboxID invoke APDU and receiving of mIDMailboxID return result or return error APDU

7.3.1

B3:m

receipt of mIDMailboxID invoke APDU and sending of mIDMailboxID return result or return error APDU

7.3.1

B5:m

receipt of mIDMailboxAuth invoke APDU and sending of mIDMailboxAuth return result or return error APDU

7.3.1

B4:m

sending of mIDMailboxAuth invoke APDU and receiving of mIDMailboxAuth return result or return error APDU

7.3.1

B6:m

A.3 .3.4.4 Timers Item

Question/feature

Reference

Protocol Status

Profile Status

Support of timer T1

7.9.1

B3:m

Support of timer T2

7.9.2

B6:m

A.3 .3.5 Supplementa ry Serv ic e Ca ll D iversio n As specified in A.3.1.3. A.3 .3.6 Supplementa ry S e rv ic e Ca ll Tran sf er As specified in A.3.1.4. A.3 .3.7 S upp lementa ry S e rv ice S ing le-St ep Ca ll Tra ns fer As specified in A.3.2.6.

- 35 -

A.3.4

Tables for Profile 4 Item

Question/Feature

Reference

Profile Status

P4.M

Behaviour as Message Centre PINX according to MCA-Profile-4

7.4

o.1

P4.S

Behaviour as Served User PINX according to MCA-Profile-4

7.4

o.1

A.3 .4.1 S uppo rt of S upp lementa ry S e rv ices Item

Question/Feature

Reference

Profile Status

P4.1

Support of SS-MWI at Message Centre PINX

ECMA-242

i (NOTE)

P4.2

Support of SS-MWI at Served User PINX

ECMA-242

i (NOTE)

P4.3

Support of SS-MCM at Message Centre PINX

ECMA-347

P4.M:m

P4.4

Support of SS-MCM at Served User PINX

ECMA-347

P4.S:m

P4.5

Support of SS-MID at Message Centre PINX

ECMA-347

P4.M:m

P4.6

Support of SS-MID at Served User PINX

ECMA-347

P4.S:o

P4.7

Support of SS-SD at Message Centre PINX

ECMA-311

P4.M:m

P4.8

Support of SS-SD at Served User PINX

ECMA-311

P4.S:m

P4.9

Support of SS-MCR at Message Centre PINX

ECMA-344

P4.M:m

P4.10

Support of SS-MCR at Served User PINX

ECMA-344

P4.S:m

P4.11

Support of SS-DIV at Message Centre PINX

ECMA-174

P4.M:m

P4.12

Support of SS-DIV at Served User PINX

ECMA-174

P4.S:m

P4.13

Support of SS-CT at Message Centre PINX

ECMA-178

P4.M:m

P4.14

Support of SS-CT at Served User PINX

ECMA-178

P4.S:m

P4.15

Support of SS-SSCT at Served User PINX

ECMA-300

P4.S:m

P4.16

Support of SS-SSCT at Message Centre PINX

ECMA-300

P4.M:m

NOTE MWI is an inherent part of MCM.

- 36 -

A.3 .4.2 Supplementa ry Serv ic e Simple D ialog As specified in A.3.2.3. A.3 .4.3 S upp le me nta ry S e rv ic e M es sag e Ce nt re Mon ito r ing As specified in A.3.3.3. A.3 .4.4 S upp le me nta ry S e rv ic e M es sag e Ce nt re I de ntif icat ion As specified in A.3.3.4. A.3 .4.5 S upp lementa ry S e rv ice Ma ke Ca ll R equ est Item number and references refer to annex A of ECMA-344. A.3 .4.5.1 Genera l Item

Question/Feature

Reference

Protocol Status

Profile Status

Behaviour as Requesting PINX for SS-MCR

o.1

P4.M:m

Behaviour as Co-operating PINX for SS-MCR

o.1

P4.S:m

Behaviour as Destination PINX for SS-MCR

o.1

P4.M:m

Reference

Protocol Status

Profile Status

A.3 .4.5.2 Pro cedures Item

Question/Feature

Support of relevant ECMA-143 and ECMA-165 procedures at the Requesting PINX

6.2.1

A1:m

Support of relevant ECMA-143 and ECMA-165 procedures at the Co-operating PINX

6.2.2

A2:m

Support of relevant ECMA-143 and ECMA-165 procedures at the Destination PINX

6.2.3

A3:m

Procedures at the Requesting PINX for invocation and operation

6.5.1

A1:m

Procedures at the Co-operating PINX for invocation and operation

6.5.2

A2:m

Procedures at the Destination PINX for invocation and operation

6.5.3

A3:m

- 37 -

A.3 .4.5.3 Coding Item

Question/Feature

Reference

Protocol Status

Profile Status

Sending of mCRequest invoke APDU to the Co-operating PINX

6.5.1

A1:m

Receipt of mCRequest return result APDU or mCRequest return error from the Co-operating PINX

6.5.1

A1:m

Receipt of mCRequest invoke APDU from the Requesting PINX

6.5.2

A2:m

Sending of mCRequest return result APDU or mCRequest return error APDU in case of an error indication

6.5.2

A2:m

Sending of mCAlerting invoke APDU to the Requesting PINX

6.5.2

A2:m

Receipt of mCAlerting invoke APDU from the Co-operating PINX

6.5.1

A1:m

Sending of mCInform invoke APDU to the Destination PINX

6.5.2

A2:m

Receipt of mCInform return error APDU from the Destination PINX

6.5.2

A2:m

Receipt of mCInform invoke APDU from the Co-operating PINX

6.5.3

A3:m

C10

Sending of mCInform return error APDU to the Co-operating PINX

6.5.3

A3:m

A.3 .4.5.4 Timers Item

Question/Feature

Reference

Protocol Status

Profile Status

Support of timer T1

6.9.1

A1:m

A.3 .4.6 Supplementa ry Serv ic e Ca ll D iversio n As specified in A.3.1.3. A.3 .4.7 Supplementa ry S e rv ic e Ca ll Tran sf er As specified in A.3.1.4. A.3 .4.8 S upp lementa ry S e rv ice S ing le-St ep Ca ll Tra ns fer As specified in A.3.2.6.

- 38 -

- 39 -

Annex B (nor ma tiv e)

Profile specific ICS proforma

B.1

General The layout and content of this annex is guided by ISO/IEC 9646-7. The supplier of a profile implementation that is claimed to conform to this Standard shall complete the Profile specific Implementation Conformance Statement (ICS) proforma contained in this annex. NOTE The supplier is also required to complete a copy of the PICS proforma provided in each of the protocol standards referred to by this Standard. A completed Profile specific ICS proforma is the ICS for the implementation in question. The ICS is a statement of which capabilities and options of the profile have been implemented. The ICS can have a number of uses, including use:

B.2 B.2.1

By the profile implementer, 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 ICS proforma;

By the 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 ICS);

By a protocol tester, as the basis for selecting appropriate test suites against which to assess the claim for conformance of the implementation.

Instruction for completing the ICS proforma General structure of the ICS proforma The ICS 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 either the base standard, or a specific clause in a base standard, or specifying the item in the main body of this Standard (if no base standard is listed in the reference column). 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 profile);

optional (the capability is not required for conformance to the profile but if the capability is implemented it is required to conform to the profile specification);

o.<n>

optional, but support of at least one of the group of options labelled by the same numeral <n> is required;

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

prohibited;

- 40 -

c.<cond> conditional requirement, depending on support for the item listed in condition <cond>. Answers to the questionnaire items are to be provided 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).

B.2.2

Additional Information Items of Additional information allow a supplier to provide further information intended to assist the interpretation of the ICS. It is not intended or expected that a large quantity will be supplied, and an ICS 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.

B.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 a 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.

- 41 -

B.3

ICS proforma for Profile 1

B.3.1

Implementation Identification

Supplier Contact point for queries about the ICS Implementation Name(s) and Version(s) (NOTE) Other information necessary for full identification, e.g. name(s) and version(s) for machines and/or operating systems; system name(s) Have any exception items been required?

No[ ] Yes[ ] (The answer Yes means that the implementation does not conform to this Standard)

Date of Statement

NOTE The terms "Name" and "Version" should be interpreted appropriately to correspond with a supplier’s terminology (e.g., Type, Series, Model).

B.3.2

General

Item

Question/Feature

Reference

Status

N/A

Support

P1.A1

Support of Message Centre Access at Message Centre PINX according to MCA-Profile-1

o.1

Yes [ ] No[ ]

P1.A2

Support of Message Centre Access at Served User PINX according to MCA-Profile-1

o.1

Yes [ ] No[ ]

- 42 -

B.3.3

Message Deposit

Item

Question/Feature

Reference

Status

N/A

Support

P1.B1

Direct Message Deposit using Called Party Number IE

7.1.1

P1.A1:o

[]

Yes [ ] No[ ]

P1.B2

Direct Message Deposit using DTMF and announcements

7.1.1

P1.A1:m

[]

Yes [ ]

P1.B3

Message Deposit after Diversion

7.1.1

P1.A1:m

[]

Yes [ ]

P1.B4

Message Deposit after Call Transfer using Called Party Number IE

7.1.1

P1.B5

Message Deposit after Call Transfer using DTMF and announcements

7.1.1

P1.A1:m

P1.B6

Invocation of Message Waiting Indication after Message Deposit

7.1.1

Reference

Status

7.1.2

Reference

Status

N/A

Support

[]

Yes [ ] No[ ]

B.3.4

[]

Yes [ ] m:Yes [ ]

Message Centre Monitoring

Item

Question/Feature

P1.C1

Message Centre Monitoring using Message Waiting Indication

B.3.5

Yes [ ] No[ ]

N/A

Support m:Yes [ ]

Message Browsing

Item

Question/Feature

P1.D1

User Authentication using DTMF and announcements

7.1.3

c.1

P1.D2

Message Browsing using DTMF and announcements

7.1.3

Reference

Status

7.1.4

Reference

Status

7.1.5

m:Yes [ ]

c.1: If P1.A1 then m, else o

B.3.6

Message Retrieval

Item

Question/Feature

P1.E1

Message Retrieval using DTMF and announcements

B.3.7

N/A

Support m:Yes [ ]

Message Centre Transfer

Item

Question/Feature

P1.F1

Message Centre Transfer using Call Transfer initiated using DTMF and announcements

N/A

Support m:Yes [ ]

- 43 -

B.4

ICS proforma for Profile 2

B.4.1

Implementation Identification

No[ ] Yes[ ] (The answer Yes means that the implementation does not conform to this Standard)

Date of Statement

NOTE The terms "Name" and "Version" should be interpreted appropriately to correspond with a supplier’s terminology (e.g., Type, Series, Model).

B.4.2

General

Item

Question/Feature

Reference

Status

N/A

Support

P2.A1

Support of Message Centre Access at Message Centre PINX according to MCA-Profile-2

o.1

Yes [ ] No[ ]

P2.A2

Support of Message Centre Access at Served User PINX according to MCA-Profile-2

o.1

Yes [ ] No[ ]

- 44 -

B.4.3

Message Deposit

Item

Question/Feature

Reference

Status

N/A

Support

P2.B1

Direct Message Deposit using Called Party Number IE

7.2.1

P2.A1:o

[]

Yes [ ] No[ ]

P2.B2

Direct Message Deposit using Simple Dialog

7.2.1

P2.A1:m

[]

m:Yes [ ]

P2.B3

Direct Message Deposit using DTMF and announcements

7.2.1

P2.A1:m

[]

m:Yes [ ]

P2.B4

Message Deposit after Diversion

7.2.1

P2.B5

Message Deposit after Call Transfer using Called Party Number IE

7.2.1

P2.A1:o

[]

Yes [ ] No[ ]

P2.B6

Message Deposit after Call Transfer using Simple Dialog

7.2.1

P2.A1:m

[]

m:Yes [ ]

P2.B7

Fall back to Message Deposit after Call Transfer using DTMF and announcements

7.2.1

P2.A1:m

[]

m:Yes [ ]

P2.B8

Message Deposit after Single Step Call Transfer

7.2.1

P2.A1:m

[]

m:Yes [ ]

P2.B9

Invocation of Message Waiting Indication after Message Deposit

7.2.1

Reference

Status

7.2.2

Reference

Status

N/A

Support

B.4.4

m:Yes [ ]

Message Centre Monitoring

Item

Question/Feature

P2.C1

Message Centre Monitoring using Message Waiting Indication

B.4.5

m:Yes [ ]

N/A

Support m:Yes [ ]

Message Browsing

Item

Question/Feature

P2.D1

User Authentication using Simple Dialog

7.2.3

c.1

[]

Yes [ ] No[ ]

P2.D2

Fall back to User Authentication using DTMF and announcements

7.2.3

P2.D1:m

[]

m:Yes [ ]

P2.D3

Message Browsing using Simple Dialog

7.2.3

m:Yes [ ]

P2.D4

Fall back to Message Browsing using DTMF and announcements

7.2.3

m:Yes [ ]

Reference

Status

c.1: If P2.A1 then m, else o

B.4.6

Message Retrieval

Item

Question/Feature

N/A

Support

P2.E1

Message Retrieval using Simple Dialog

7.2.4

m:Yes [ ]

P2.E2

Fall back to Message Retrieval using DTMF and announcements

7.2.4

m:Yes [ ]

- 45 -

B.4.7

Message Centre Transfer

Item

Question/Feature

Reference

Status

P2.F1

N/A

Support

Message Centre Transfer using Single Step Call Transfer initiated using Simple Dialog

7.2.5

m:Yes [ ]

P2.F2

Fall back to Message Centre Transfer using Single Step Call Transfer initiated using DTMF and announcements

7.2.5

m:Yes [ ]

P2.F3

Message Centre Transfer using Call Transfer initiated using Simple Dialog

7.2.5

m:Yes [ ]

P2.F4

Fall back to Message Centre Transfer using Call Transfer initiated using DTMF and announcements

7.2.5

m:Yes [ ]

- 46 -

B.5

ICS proforma for Profile 3

B.5.1

Implementation Identification

No[ ] Yes[ ] (The answer Yes means that the implementation does not conform to this Standard)

Date of Statement

NOTE The terms "Name" and "Version" should be interpreted appropriately to correspond with a supplier’s terminology (e.g., Type, Series, Model).

B.5.2

General

Item

Question/Feature

Reference

Status

N/A

Support

P3.A1

Support of Message Centre Access at Message Centre PINX according to MCA-Profile-3

o.1

Yes [ ] No[ ]

P3.A2

Support of Message Centre Access at Served User PINX according to MCA-Profile-3

o.1

Yes [ ] No[ ]

- 47 -

B.5.3

Message Deposit

Item

Question/Feature

Reference

Status

N/A

Support

P3.B1

Direct Message Deposit using Called Party Number IE

7.3.1

P3.A1:o

[]

Yes [ ] No[ ]

P3.B2

Direct Message Deposit using Simple Dialog

7.3.1

P3.A1:m

[]

m:Yes [ ]

P3.B3

Fall back to Direct Message Deposit using DTMF and announcements

7.3.1

P3.A1:m

[]

m:Yes [ ]

P3.B4

Message Deposit after Diversion

7.3.1

P3.B5

Message Deposit after Call Transfer using Called Party Number IE

7.3.1

P3.A1:o

[]

Yes [ ] No[ ]

P3.B6

Message Deposit after Call Transfer using Simple Dialog

7.3.1

P3.A1:m

[]

m:Yes [ ]

P3.B7

Fall back to Message Deposit after Call Transfer using DTMF and announcements

7.3.1

P3.A1:m

[]

m:Yes [ ]

P3.B8

Message Deposit after Single Step Call Transfer

7.3.1

m:Yes [ ]

P3.B9

Invocation of Message Centre Monitoring after Message Deposit

7.3.1

m:Yes [ ]

Reference

Status

B.5.4

m:Yes [ ]

Message Centre Monitoring

Item

Question/Feature

P3.C1

Message Centre Monitoring using Message Centre Monitoring

7.3.2

m:Yes [ ]

P3.C2

Identification of a Served User’s Mailbox using Mailbox Identification

7.3.2

Yes [ ] No[ ]

Reference

Status

N/A

Support

B.5.5

N/A

Support

Message Browsing

Item

Question/Feature

P3.D1

Served User Authentication using Mailbox Identification

7.3.3

c.1

[]

Yes [ ] No[ ]

P3.D2

Served User Authentication using Simple Dialog

7.3.3

P3.D1:m

[]

m:Yes [ ]

P3.D3

Fall back to User Authentication using DTMF and announcements

7.3.3

m:Yes [ ]

P3.D4

Message Browsing using Message Centre Monitoring

7.3.3

m:Yes [ ]

P3.D5

Fall back to Message Browsing using DTMF and announcements

7.3.3

m:Yes [ ]

c.1: If P3.A1 then m, else o

- 48 -

B.5.6

Message Retrieval

Item

Question/Feature

P3.E1 P3.E2

B.5.7

Reference

Status

N/A

Support

Message Retrieval using Simple Dialog

7.3.4

m:Yes [ ]

Fall back to Message Retrieval using DTMF and announcements

7.3.4

m:Yes [ ]

Reference

Status

Message Centre Transfer

Item

Question/Feature

N/A

Support

P3.F1

Message Centre Transfer using Single Step Call Transfer initiated using Simple Dialog

7.3.5

m:Yes [ ]

P3.F2

Fall back to Message Centre Transfer using Single Step Call Transfer initiated using DTMF and announcements

7.3.5

m:Yes [ ]

P3.F3

Message Centre Transfer using Call Transfer initiated using Simple Dialog

7.3.5

m:Yes [ ]

P3.F4

Fall back to Message Centre Transfer using Call Transfer initiated using DTMF and announcements

7.3.5

m:Yes [ ]

- 49 -

B.6

ICS proforma for Profile 4

B.6.1

Implementation Identification

No[ ] Yes[ ] (The answer Yes means that the implementation does not conform to this Standard)

Date of Statement

NOTE The terms "Name" and "Version" should be interpreted appropriately to correspond with a supplier’s terminology (e.g., Type, Series, Model).

B.6.2

General

Item

Question/Feature

Reference

Status

N/A

Support

P4.A1

Support of Message Centre Access at Message Centre PINX according to MCA-Profile-4

o.1

Yes [ ] No[ ]

P4.A2

Support of Message Centre Access at Served User PINX according to MCA-Profile-4

o.1

Yes [ ] No[ ]

- 50 -

B.6.3

Message Deposit

Item

Question/Feature

Reference

Status

N/A

Support

P4.B1

Direct Message Deposit using Called Party IE

7.4.1

P4.A1:o

[]

Yes [ ] No[ ]

P4.B2

Direct Message Deposit using Simple Dialog

7.4.1

P4.A1:m

[]

m:Yes [ ]

P4.B3

Fall back to Direct Message Deposit using DTMF and announcements

7.4.1

m:Yes [ ]

P4.B4

Message Deposit after Diversion

7.4.1

m:Yes [ ]

P4.B5

Message Deposit after Call Transfer using Called Party IE

7.4.1

Yes [ ] No[ ]

P4.B6

Message Deposit after Call Transfer using Simple Dialog

7.4.1

m:Yes [ ]

P4.B7

Message Deposit after Call Transfer using DTMF and announcements

7.4.1

m:Yes [ ]

P4.B8

Message Deposit after Single Step Call Transfer

7.4.1

m:Yes [ ]

P4.B9

Invocation of Message Centre Monitoring after Message Deposit

7.4.1

m:Yes [ ]

Reference

Status

7.4.2

Reference

Status

N/A

Support

B.6.4

Message Centre Monitoring

Item

Question/Feature

P4.C1

Monitoring of the Served User’s Mailbox using Message Centre Monitoring

B.6.5

N/A

Support m:Yes [ ]

Message Browsing

Item

Question/Feature

P4.D1

Served User Authentication using Mailbox Identification

7.4.3

c.1

[]

Yes [ ] No[ ]

P4.D2

Served User Authentication using Simple Dialog

7.4.3

c.1

[]

Yes [ ] No[ ]

P4.D3

Fall back to User Authentication using DTMF and announcements

7.4.3

P4.D2:m

[]

m:Yes [ ]

P4.D4

Message Browsing using Simple Dialog

7.4.3

m:Yes [ ]

P4.D5

Fall back to Message Browsing using DTMF and announcements

7.4.3

m:Yes [ ]

c.1: If P4.A1 then m, else o

- 51 -

B.6.6

Message Retrieval

Item

Question/Feature

P4.E1 P4.E2

B.6.7

Reference

Status

N/A

Support

Message Retrieval using Simple Dialog and Make Call Request

7.4.4

m:Yes [ ]

Fall back to Message Retrieval using DTMF and announcements

7.4.4

m:Yes [ ]

Reference

Status

Message Centre Transfer

Item

Question/Feature

N/A

P4.F1

Message Centre Transfer using Single Step Call Transfer initiated using Simple Dialog

7.4.5

m:Yes [ ]

P4.F2

Message Centre Transfer using Call Transfer initiated using Simple Dialog

7.4.5

m:Yes [ ]

P4.F3

Message Centre Transfer using Make Call Request initiated using Simple Dialog

7.4.5

P4.F4

Fall back to Message Centre Transfer using DTMF and announcements

7.4.5

[]

Support

Yes [ ] No[ ] m:Yes [ ]

- 52 -

- 53 -

Annex C ( infor ma tive)

Example Message Flows

C.1

Example Message Flows for Profile 1

C.1.1

Message Deposit after Diversion Figure C.1.1 shows the diversion of a Calling User (e.g. due to CFU) to the MWI Served User's mailbox and the transmission of a Message Waiting Indication for the MWI Served User. Calling User PINX

Served User PINX

Message Centre/ Diverted-to PINX

SETUP FACILITY reroute.inv SETUP divLegInfo2.inv FACILITY reroute.res CONNECT divLegInfo3.inv Basic Call DISCONNECT SETUP mwiActivate.inv CONNECT mwiActivate.res RELEASE

NOTE Clearing of the MWI-CISC is optional. Fig ure C .1.1 – Message depo sit aft er div ersion and t ransmissio n of a M essag e Wa it ing Indicat ion fo r t he MWI S erv ed Use r

- 54 -

C.1.2

Message retrieval Figure C.1.2 shows the retrieval of messages by the MWI Served User from the MWI Served User's mailbox and the clearing of the Message Waiting Indication for the MWI Served User. Served User PINX

Message Centre PINX SETUP CONNECT

Basic Call Communication using announcements and DTMF DISCONNECT

SETUP mwiDeactivate.inv CONNECT mwiDeactivate.res RELEASE

NOTE Clearing of the MWI-CISC is optional. Fig ure C .1.2 – Message R etrieva l and clea ring of Message Wa it ing Indicat io n

- 55 -

C.1.3

Message Centre Transfer Figure C.1.3 shows the transfer of the MWI Served User to, for example, the originator of a message in the MWI Served User's mailbox. Secondary PINX

Served User/Primary PINX

Message Centre/ Transferring PINX Basic Call

Communication using announcements and DTMF Served User indicates request for transfer SETUP ALERTING FACILITY ctComplete.inv FACILITY ctComplete.inv CONNECT FACILITY ctActive.inv Basic Call

F ig ur e C .1.3 – Ca ll Tran sf er in it iat ed by t he M es sag e Ce nt re P INX o n re qu est of th e Se rve d U s er

- 56 -

C.2

Example Message Flows for Profile 2

C.2.1

Message retrieval Figure C.2.1 shows the retrieval of messages by the MWI Served User from the MWI Served User's mailbox and the clearing of the Message Waiting Indication for the MWI Served User. The communication between the Served User and the Message Centre is done using Simple Dialog.

Served User PINX

Message Centre PINX SETUP CONNECT

Basic Call FACILITY display.inv indicating information for message retrieval

FACILITY keypad.inv indicating retrieval of a message Message Centre introduces message into the User-Channel

DISCONNECT SETUP mwiDeactivate.inv CONNECT mwiDeactivate.res RELEASE

NOTE Clearing of the MWI-CISC is optional. Fig ure C .2.1 – Message R etrieva l and dea ct ivat ion of M essag e Wa it ing Indicat ion

- 57 -

C.2.2

Message Centre Single Step Transfer Figure C.2.2 shows the transfer of the MWI Served User to, for example, the originator of a message in the MWI Served User's mailbox. The Served User initiates Single Step Call Transfer using Simple Dialog. In the example, transfer occurs on alerting of the new call.

Transferred-to PINX

Served User/Transferred PINX

Message Centre/ Transferring PINX

Basic Call FACILITY keypad.inv Served User indicates request for transfer

SETUP

FACILITY ssctInitiate.inv awaitConnect=False

ssctSetup.inv awaitConnect=False ALERTING

DISCONNECT ssctInitiate.res

CONNECT

Basic Call

F ig ure C .2.2 – S ing le St ep Call Tran sf er in it iat ed by t he M es sag e Cent re P INX o n r eq u e st o f t h e S e rve d U s er

- 58 -

C.3

Example Message Flows for Profile 3

C.3.1

Message Deposit after Diversion Figure C.3.1 shows the diversion of a Calling User (e.g. due to CFU) to the MCM Served User's mailbox and the transmission of a New Message Indication for the MCM Served User. Calling User PINX

Served User PINX

Message Centre/ Diverted-to PINX

SETUP FACILITY reroute.inv SETUP divLegInfo2.inv FACILITY reroute.res CONNECT divLegInfo3.inv Basic Call DISCONNECT SETUP mCMNewMsg.inv CONNECT mCMNewMsg.res RELEASE

Fig ure C .3.1 – Message depo sit aft er div ersion and t ransmissio n of a N e w M essag e Indication fo r t he MCM Serv ed User

- 59 -

C.3.2

Message Centre Monitoring Figure C.3.2 shows how the Served User authenticates and activates Message Centre Monitoring for a particular Message Type.

Message Centre PINX

Served User PINX SETUP

mIDMailboxAuth .inv

CONNECT mIDMailboxAuth .res FACILITY mCMService.inv (activateMCM, messageType)

FACILITY mCMService.res

Fig ure C .3.2 – Act iva t ion of M essag e C ent re Monito ring fo r a pa rt ic ula r M essag e Type aft er au th ent ication of t he Se rv ed Us er

- 60 -

C.3.3

Message Centre Browsing Figure C.3.3 shows an example message flow where the Served User owns several mailboxes at a Message Centre. The mailboxes are identified using Mailbox Identification before performing the update procedures for the various mailboxes according to Message Centre Monitoring. Served User PINX

Message Centre PINX SETUP mIDMailboxAuth .inv

CONNECT

mIDMailboxAuth .res

Basic Call FACILITY keypad.inv leading to changes due to e.g. deletion of messages in various mailboxes

FACILITY

mIDMailboxID.inv (Box1) FACILITY

Update for „Box1“

mIDMailboxID.res FACILITY mCMUpdate.inv FACILITY mCMUpdate.res FACILITY mCMUpdate.inv FACILITY mCMUpdate.res ... FACILITY

Update for „Box2“

mIDMailboxID.inv (Box2) FACILITY mIDMailboxID.res FACILITY mCMUpdate.inv FACILITY mCMUpdate.res ...

F ig ur e C .3.3 – Me ssage C ent re Bro ws ing wher e th e S e rve d U s er o wn s sev e ra l ma ilboxe s at th e M es sag e C ent re

- 61 -

C.4

Example Message Flows for Profile 4

C.4.1

Message retrieval The Served User establishes a CISC for Message Browsing purposes and indicates retrieval of a message to the Message Centre using Simple Dialog. Make Call Request is used to provide a B-Channel for retrieval of the message (see figure C.4.1). Afterwards, the communication between the Message Centre and the Served User may continue using the same CISC. Message Centre PINX

Served User PINX SETUP (1) CONNECT (1) CISC 1 FACILITY (1) keypad.inv

indicating message retrieval

FACILITY (1) mCRequest.inv SETUP (2) mCInform.inv CONNECT (2) Basic Call DISCONNECT(2) CISC 1 FACILITY (1) display.inv FACILITY (1) keypad.inv DISCONNECT (1)

Fig ure C .4.1 – Ret r ieva l of a messag e using M a k e C a l l R equ e st a nd S i mp le D ia lo g

- 62 -

C.4.2

Message Centre Transfer The Served User uses a CISC and indicates the request for transfer to, for example, the originator of a message in the Served User's mailbox using Simple Dialog. The Message Centre uses Make Call Request to establish the requested call (see figure C.4.2). Afterwards, the communication between the Message Centre and the Served User may continue using the same CISC.

Message Centre/ Requesting PINX

Served User/ Co-operating PINX

Destination PINX

CISC Connection FACILITY keypad.inv (indicating request for Transfer)

FACILITY

SETUP

mCRequest.inv

mCInform.inv CALL PROC

FACILITY

ALERTING

mCAlerting.inv FACILITY

CONNECT

mCRequest.rr Basic Call CISC Connection may still be used FACILITY keypad.inv FACILITY display.inv Fig ure C .4.2 – Message C ent re Transf er using Ma ke Ca ll R equest and Simple D ia log

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-345 — Private Integrated Services Network (PISN) – Use of QSIG for Message Centre Access (MCA) profile standard (June 2003)

Related documents