SIST-TS ETSI/TS 102 254 V1.1.1:2005

• Abstract:

  Stage 1 & 2 of MCM

• Status: Published
• Publication Date: 28-Feb-2005
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Mar-2005
• Due Date: 01-Mar-2005
• Completion Date: 01-Mar-2005
• Ref Project: ETSI TS 102 254 V1.1.1 (2003-08) - Private Integrated Services Network (PISN); Specification, functional model and information flows; Message Centre Monitoring and Mailbox Identification supplementary service

This is the Slovenian standard identical to ETSI TS 102 254 V1.1.1, a Technical Specification for Private Integrated Services Network (PISN) supplementary services. It specifies the Message Centre Monitoring (SS-MCM) and Mailbox Identification (SS-MID) services, so implementers can support mailbox status monitoring, mailbox selection, and mailbox authentication in PISN environments.

What does SIST-TS ETSI/TS 102 254 V1.1.1:2005 specify?

SIST-TS ETSI/TS 102 254 V1.1.1:2005 specifies two PISN supplementary services: SS-MCM and SS-MID. SS-MCM lets a Served User receive status information and status changes for messages stored in a mailbox, while SS-MID lets a Message Centre identify a specific mailbox and lets a Served User authenticate at that mailbox.

The document is organized into:

• clauses 1 to 3 for scope, conformance, and normative references
• clause 4 for definitions
• clause 5 for acronyms
• clauses 6 and 7 for the stage 1 specifications of SS-MCM and SS-MID
• clauses 8 and 9 for the stage 2 specifications of SS-MCM and SS-MID
• a history section at the end

The scope also makes clear that the document is about supplementary services related to, but not limited by, basic PISN services. It does not cover the procedures for how a Served User accesses messages in the Message Centre or how a message is left in the mailbox.

What are the key requirements of SIST-TS ETSI/TS 102 254 V1.1.1:2005?

SS-MCM: monitoring message status in a mailbox

SS-MCM is the service that informs a Served User about new messages and about changes such as retrieval or deletion. Clause 6 says the service can be provided or withdrawn by arrangement with the service provider, or made generally available.

A practical point is that SS-MCM uses a default configuration defined by the service provider. That default determines which Message Types are monitored and whether the user receives complete information or compressed information. In practice, this means service operators need a clear default policy for each mailbox type.

The Served User can change the configuration for individual Message Types by activating, deactivating, or interrogating monitoring. Clause 6 also allows resetting everything back to the default configuration. This matters because monitoring can be tailored to speech, fax, email, or other Message Types instead of applying one blanket setting.

SS-MCM message indications and updates

When a new message arrives, the Message Centre sends an indication that includes the Message Type and may include the Message Centre address. Depending on the selected presentation style, the indication can carry compressed information or complete information about the message. Compressed information is mandatory, while complete information is optional.

Clause 6 also requires update procedures when the number of new and/or retrieved messages changes after retrieval or deletion. The Message Centre sends updated information by Message Type, and the update can use complete information, compressed information, or a mix of both according to the current configuration. For users, this means the mailbox view is refreshed after message handling, not only at first arrival.

The Served User can also request an update at any time for all Message Types or for a specific one. In addition, the Message Centre may send a Mailbox-full indication when storage capacity or a threshold is reached. That helps operators and users handle mailbox limits before further messages are lost or delayed.

SS-MID: identifying and authenticating a mailbox

SS-MID supports cases where one Served User has more than one mailbox in the same Message Centre. Clause 7 lets the Message Centre identify a specific mailbox using the Message Centre address, optionally the Served User name, and a mailbox identity.

SS-MID also supports authentication at a specific mailbox. The Served User sends the Message Centre address, optional mailbox identity, optional name, and an authentication string such as a password. In practice, this is the mechanism that ties access to the correct mailbox when the same user has multiple mailboxes or message-type-specific storage.

If the mailbox identity is invalid, or if the password check fails, the service returns an error indication. Clause 7 also states that if SS-MID authentication services fail, the activation, deactivation, interrogation, and update request services of SS-MCM shall not be executed. That makes SS-MID a gatekeeper for protected mailbox monitoring functions.

Stage 2 functional model and information flows

Clauses 8 and 9 define the stage 2 model with three Functional Entities: FE1, FE2, and FE3. FE1 is the Message Centre's control entity, FE2 is the Served User's control entity, and FE3 is the Served User Agent. The model is built around the relationships ra and rb between those entities.

For SS-MCM, the information flows include MCM_ServiceChange, MCM_Interrogate, MCM_NewMessage, MCM_NoNewMessage, MCM_UpdateInfo, MCM_UpdateReq, and MCM_Mailbox_full. For SS-MID, the main flows are MID_MailboxID and MID_MailboxAuth. In practice, these flows tell implementers what messages must pass between the Message Centre, user control, and terminal functions.

Interactions and deployment rules

Clause 6 and clause 7 both list interactions with many other PISN supplementary services and additional network features, including SS-MWI. The document states that SS-MCM is based on SS-MWI and includes its entire functionality, so compatibility with SS-MWI is guaranteed. This is important when extending an existing message waiting implementation to richer mailbox monitoring.

What terms does SIST-TS ETSI/TS 102 254 V1.1.1:2005 define?

• Mailbox - A logical entity in a Message Centre that stores messages for one specific Served User.
• Message Centre (MC) - The network entity that manages mailboxes and provides status information about messages stored there.
• Message Status - The state of a stored message, either New Message or Retrieved Message.
• New Message - A message stored in a mailbox that the Served User has not yet retrieved.
• Retrieved Message - A message the Served User has already retrieved but not deleted.
• Message Waiting Signal (MWS) - A terminal signal, such as a lamp, tone, or display string, used to draw attention to a new message.
• Served User - The owner of a mailbox at a Message Centre, who receives indications about status changes.

Who uses SIST-TS ETSI/TS 102 254 V1.1.1:2005?

This standard is used by PISN service providers, network and switch vendors, and terminal implementers that support mailbox-based messaging services. It is relevant to engineers who design signaling and service logic, to quality managers who verify service behavior, and to buyers who need message monitoring and mailbox identification in a private telecommunication network.

It also matters for interoperability work between Message Centres, user terminals, and systems that already implement SS-MWI. Typical tasks include defining default service behavior, mapping service logic to functional entities, handling authentication, and checking how message notifications behave when messages are retrieved, deleted, or newly stored.

Which standards are used with SIST-TS ETSI/TS 102 254 V1.1.1:2005?

• ETSI ETS 300 387 - gives the method used to specify basic and supplementary services in stages.
• ECMA-142 - provides the PISN circuit-mode 64 kbit/s bearer service context and the basic telecommunication service reference used by this document.
• ECMA-241 - defines Message Waiting Indication (MWISD), which SS-MCM builds on and fully includes.
• ITU-T Recommendation I.112 - supplies terms such as service and signalling.
• ITU-T Recommendation I.210 - gives the principles for describing telecommunication services supported by an ISDN.
• ITU-T Recommendation Z.100 - provides Specification and Description Language (SDL), which the document uses for the behavior figures.
• ECMA-133 - defines the PISN reference configuration for PINX, used for the network context and physical allocation of functional entities.

What does the SIST-TS ETSI/TS 102 254 V1.1.1:2005 document contain?

The document contains stage 1 and stage 2 specifications for SS-MCM and SS-MID, including service descriptions, procedures, interactions, and functional models. It also includes detailed definitions of the information flows used between the Message Centre, the Served User control entity, and the Served User Agent.

For SS-MCM, the document provides SDL figures for activation, deactivation, interrogation, new-message handling, update handling, update requests, and mailbox-full indications. For SS-MID, it provides SDL figures for mailbox identification and authentication.

The content also includes tables that describe the information carried in each flow, such as the data elements for service change, interrogation, message indication, update information, and mailbox authentication. These tables are the main design reference for implementers who need to code signaling, test message content, or validate protocol behavior.

The final sections map the functional entities to physical equipment and describe interworking considerations with other networks that support a compatible service.

SLOVENSKI STANDARD
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,616SHFLILNDFLMDIXQNFLMVNLPRGHO
LQLQIRUPDFLMVNLSUHWRNL'RSROQLOQDVWRULWHYQDG]RUVSRURþLOQHJDFHQWUDLQ
LGHQWLILNDFLMDSRãWQHJDSUHGDOD
Private Integrated Services Network (PISN); Specification, functional model and
information flows; Message Centre Monitoring and Mailbox Identification supplementary
service
Ta slovenski standard je istoveten z: TS 102 254 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Private Integrated Services Network (PISN);
Specification, functional model and information flows;
Message Centre Monitoring and
Mailbox Identification supplementary service

2 ETSI TS 102 254 V1.1.1 (2003-08)

Reference
DTS/ECMA-00229
Keywords
PISN, stage 1, stage 2, supplementary service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 254 V1.1.1 (2003-08)
Contents
Intellectual Property Rights.7
Foreword.7
Brief History.7
1 Scope.8
2 Conformance.8
3 References (normative).8
4 Definitions.9
4.1 External definitions.9
4.2 Other definitions.9
4.2.1 Address Header.9
4.2.2 Complete Information.9
4.2.3 Compressed Information.9
4.2.4 Deleted Messages.9
4.2.5 Mailbox.9
4.2.6 Message Centre (MC).10
4.2.7 Message Status.10
4.2.8 Message Type.10
4.2.9 Message Waiting Signal (MWS) .10
4.2.10 New Message.10
4.2.11 Originator.10
4.2.12 Originator address.10
4.2.13 Retrieved Message.10
4.2.14 Served User.10
5 List of acronyms.11
6 SS-MCM stage 1 specification.12
6.1 Description.12
6.1.1 General description.12
6.1.2 Qualifications on applicability to telecommunication services.12
6.2 Procedures.12
6.2.1 Provision/withdrawal.12
6.2.2 Normal procedures.12
6.2.2.1 Activation, deactivation and interrogation .12
6.2.2.2 Invocation and operation.13
6.2.2.2.1 Incoming New Message.13
6.2.2.2.2 Update of Message Centre Information.14
6.2.2.2.3 Update request from the Served User.15
6.2.2.2.4 Mailbox - full indication.15
6.2.3 Exceptional procedures.15
6.2.3.1 Activation, deactivation and interrogation .15
6.2.3.2 Invocation and operation.16
6.3 Interactions with other Supplementary Services/Additional Network Features.16
6.3.1 Calling Line Identification Presentation (SS-CLIP) .16
6.3.2 Connected Line Identification Presentation (SS-COLP) .16
6.3.3 Calling/Connected Line Identification Restriction (SS-CLIR).16
6.3.4 Calling Name Identification Presentation (SS-CNIP).16
6.3.5 Calling/Connected Name Identification Restriction (SS-CNIR) .16
6.3.6 Connected Name Identification Presentation (SS-CONP).16
6.3.7 Call Forwarding Unconditional (SS-CFU) .16
6.3.8 Call Forwarding Busy (SS-CFB).16
6.3.9 Call Forwarding No Reply (SS-CFNR).17
6.3.10 Path Replacement (ANF-PR).17
6.3.11 Call Transfer (SS-CT).17
ETSI
4 ETSI TS 102 254 V1.1.1 (2003-08)
6.3.12 Call Deflection (SS-CD).17
6.3.13 Completion of Calls to Busy Subscribers (SS-CCBS).17
6.3.14 Completion of Calls on No Reply (SS-CCNR).17
6.3.15 Call Offer (SS-CO) .17
6.3.16 Do Not Disturb (SS-DND) .17
6.3.17 Do Not Disturb Override (SS-DNDO).17
6.3.18 Call Intrusion (SS-CI).17
6.3.19 Advice of Charge (SS-AOC) .17
6.3.20 Recall (SS-RE).17
6.3.21 Call Interception (SS-CINT).17
6.3.22 Transit Counter (ANF-TC) .17
6.3.23 Route Restriction Class (ANF-RRC).18
6.3.24 Message Waiting Indication (SS-MWI) .18
6.3.25 Wireless Terminal Location Registration (SS-WTLR).18
6.3.26 Wireless Terminal Incoming Call (SS-WTMI).18
6.3.27 Wireless Terminal Outgoing Call (SS-WTMO) .18
6.3.28 Wireless Terminal Authentication of a WTM User (SS-WTAT) .18
6.3.29 Wireless Terminal Authentication of the PISN (SS-WTAN) .18
6.3.30 Common Information (SS-CMN).18
6.3.31 Call Priority Interruption (Protection) (SS-CPI(P)) .18
6.3.32 Private User Mobility Incoming Call (ANF-PUMI).18
6.3.33 Private User Mobility Outgoing Call (ANF-PUMO).18
6.3.34 Private User Mobility Registration (SS-PUMR).18
6.3.35 Single Step Call Transfer (SS-SSCT) .18
6.3.36 Simple Dialog (SS-SD).19
6.3.37 Call Identification and Call Linkage (ANF-CIDL).19
6.3.38 Short Message Service (SS-SMS) .19
6.3.39 Make Call Request (SS-MCR).19
6.3.40 Mailbox Identification (SS-MID) .19
6.4 Interworking considerations.19
6.5 Overall SDL.19
7 SS-MID stage 1 specification.22
7.1 Description.22
7.1.1 General description.22
7.1.2 Qualifications on applicability to telecommunication services.22
7.2 Procedures.22
7.2.1 Provision / withdrawal.22
7.2.2 Normal procedures.22
7.2.2.1 Activation, deactivation and interrogation .22
7.2.2.2 Invocation and operation.22
7.2.2.2.1 Identification.22
7.2.2.2.2 Authentication.22
7.2.3 Exceptional procedures.23
7.2.3.1 Activation, deactivation and interrogation .23
7.2.3.2 Invocation and operation.23
7.3 Interactions with other Supplementary Services / Additional Network Features.23
7.3.1 Calling Line Identification Presentation (SS-CLIP) .23
7.3.2 Connected Line Identification Presentation (SS-COLP) .23
7.3.3 Calling/Connected Line Identification Restriction (SS-CLIR).23
7.3.4 Calling Name Identification Presentation (SS-CNIP).23
7.3.5 Calling/Connected Name Identification Restriction (SS-CNIR) .23
7.3.6 Connected Name Identification Presentation (SS-CONP).23
7.3.7 Call Forwarding Unconditional (SS-CFU) .23
7.3.8 Call Forwarding Busy (SS-CFB).24
7.3.9 Call Forwarding No Reply (SS-CFNR).24
7.3.10 Path Replacement (ANF-PR).24
7.3.11 Call Transfer (SS-CT).24
7.3.12 Call Deflection (SS-CD).24
7.3.13 Completion of Calls to Busy Subscribers (SS-CCBS).24
7.3.14 Completion of Calls on No Reply (SS-CCNR).24
7.3.15 Call Offer (SS-CO) .24
ETSI
5 ETSI TS 102 254 V1.1.1 (2003-08)
7.3.16 Do Not Disturb (SS-DND) .24
7.3.17 Do Not Disturb Override (SS-DNDO).24
7.3.18 Call Intrusion (SS-CI).24
7.3.19 Advice of Charge (SS-AOC) .24
7.3.20 Recall (SS-RE).24
7.3.21 Call Interception (SS-CINT).24
7.3.22 Transit Counter (ANF-TC) .25
7.3.23 Route Restriction Class (ANF-RRC).25
7.3.24 Message Waiting Indication (SS-MWI) .25
7.3.25 Wireless Terminal Location Registration (SS-WTLR).25
7.3.26 Wireless Terminal Incoming Call (SS-WTMI).25
7.3.27 Wireless Terminal Outgoing Call (SS-WTMO) .25
7.3.28 Wireless Terminal Authentication of a WTM User (SS-WTAT) .25
7.3.29 Wireless Terminal Authentication of the PISN (SS-WTAN) .25
7.3.30 Common Information (SS-CMN).25
7.3.31 Call Priority Interruption (Protection) (SS-CPI(P)) .25
7.3.32 Private User Mobility Incoming Call (ANF-PUMI).25
7.3.33 Private User Mobility Outgoing Call (ANF-PUMO).25
7.3.34 Private User Mobility Registration (SS-PUMR).25
7.3.35 Single Step Call Transfer (SS-SSCT) .25
7.3.36 Simple Dialog (SS-SD).26
7.3.37 Call Identification and Call Linkage (ANF-CIDL).26
7.3.38 Short Message Service (SS-SMS) .26
7.3.39 Make Call Request (SS-MCR).26
7.3.40 Message Centre Monitoring (SS-MCM).26
7.4 Interworking considerations.26
7.5 Overall SDL.26
8 SS-MCM stage 2 specification.28
8.1 Functional model.28
8.1.1 Functional model description.28
8.1.2 Description of Functional Entities .28
8.1.2.1 Message Centre's control entity, FE1.28
8.1.2.2 Served User's control entity, FE2.28
8.1.2.3 Served User Agent, FE3.29
8.2 Information flows.29
8.2.1 Definition of information flows.29
8.2.1.1 MCM_ServiceChange.29
8.2.1.2 MCM_Interrogate.30
8.2.1.3 MCM_NewMessage.30
8.2.1.4 MCM_NoNewMessage.31
8.2.1.5 MCM_UpdateInfo.31
8.2.1.6 MCM_UpdateReq.32
8.2.1.7 MCM_Mailbox_full.33
8.2.3 Information flow sequences.33
8.2.3.1 Service Change procedures of SS-MCM .34
8.2.3.2 Interrogation procedure of SS-MCM .34
8.2.3.3 Transmission of a NewMessage Indication.35
8.2.3.4 Transmission of a NoNewMessage Indication.35
8.2.3.5 Transmission of Update Information .36
8.2.3.6 Transmission of an Update Request.36
8.2.3.7 Transmission of a Mailbox-full indication.37
8.3 Functional Entity actions.37
8.3.1 Functional Entity actions of FE1 .37
8.3.2 Functional Entity actions of FE2 .37
8.3.3 Functional Entity actions of FE3 .38
8.4 Functional Entity behaviour .38
8.4.1 Behaviour of FE1.39
8.4.2 Behaviour of FE2.45
8.4.3 Behaviour of FE3.51
8.5 Allocation of Functional Entities to physical equipment.54
8.6 Interworking considerations.55
ETSI
6 ETSI TS 102 254 V1.1.1 (2003-08)
9 SS-MID stage 2 specification.55
9.1 Functional model.55
9.1.1 Functional model description.55
9.1.2 Description of Functional Entities .55
9.1.2.1 Message Centre's control entity, FE1.55
9.1.2.2 Served User's control entity, FE2.55
9.1.2.3 Served User Agent, FE3.56
9.2 Information flows.56
9.2.1 Definition of information flows.56
9.2.1.1 MID_MailboxID.56
9.2.1.2 MID_MailboxAuth.56
9.2.2 Information flow sequences.57
9.2.2.1 Mailbox identification.57
9.2.2.2 Mailbox authentication.58
9.3 Functional Entity actions.58
9.3.1 Functional Entity actions of FE1 .58
9.3.2 Functional Entity actions of FE2 .58
9.3.3 Functional Entity actions of FE3 .58
9.4 Functional Entity behaviour .58
9.4.1 Behaviour of FE1.59
9.4.2 Behaviour of FE2.61
9.4.3 Behaviour of FE3.63
9.5 Allocation of Functional Entities to physical equipment.64
9.6 Interworking considerations.64
History .65

ETSI
7 ETSI TS 102 254 V1.1.1 (2003-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ECMA on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
Brief History
The present document 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-00229.
The present document specifies the Message Centre Monitoring and Mailbox Identification supplementary service.
SS-MCM is based on SS-MWI and includes its entire functionality. The interoperability with SS-MWI is guaranteed.
Compared to SS-MWI, SS-MCM offers an enhanced functionality for monitoring status changes of messages stored in
the Served User's Mailbox as follows:
• individual activation and deactivation for the monitoring of messages of different Message Type(s) within the
Mailbox as well as interrogation of the actual SS-MCM configuration;
• retrieval of information about all messages (i.e. new and retrieved messages) in the mailbox independent of the
Message Status;
• request of detailed updated information about messages stored in the mailbox at every time.
The present document is based upon the practical experience of ECMA member companies and the results of their
active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national
standardization bodies. It represents a pragmatic and widely based consensus.
ETSI
8 ETSI TS 102 254 V1.1.1 (2003-08)
1 Scope
The present document specifies supplementary service Message Centre Monitoring/Mailbox Identification (SS-
MCM/MID), which is related, but not limited, to various basic services supported by Private Integrated Services
Networks (PISNs). Basic services are specified in ECMA-142 [2].
The supplementary service MCM enables a Served User to get informed by a Message Centre about the status and
status changes of messages stored in that Served Users Mailbox.
The supplementary service MID enables a Message Centre to identify a specific mailbox of a Served User in case that
the Served User has more than one Mailbox within the Message Centre. In addition SS-MID enables a Served User to
authenticate himself/herself at a specific Mailbox located within the Message Centre.
Service specifications are produced in three stages, according to the method described in ETS 300 387 [1]. The present
document contains the stage 1 and stage 2 specifications of SS-MCM/MID. The stage 1 specification (see clauses 6
and 7) specifies the supplementary service as seen by users of PISNs. The stage 2 specification (see clauses 8 and 9)
specifies the functional entities involved in the supplementary service and the information flows between them.
2 Conformance
In order to conform to the present document, a stage 3 standard shall specify signalling protocols and equipment
behaviour that are capable of being used in a PISN which supports the supplementary service specified in the present
document. This means that, to claim conformance, a stage 3 standard is required to be adequate for the support of those
aspects of clauses 6 and 7 (stage 1) and clauses 8 and 9 (stage 2) which are relevant to the interface or equipment to
which the stage 3 standard applies.
3 References (normative)
The following standards contain provisions which, through reference in this text, constitute provisions of the present
document. All standards are subject to revision, and parties to agreements based on the present document 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.
[1] ETSI ETS 300 387: "Private Telecommunication Network (PTN); Method for the specification of
basic and supplementary services".
[2] ECMA-142: "Private Integrated Services Network (PISN) - Circuit-mode 64 kbit/s Bearer
Services - Service Description, Functional Capabilities and Information Flows (International
Standard ISO/IEC 11574)".
[3] ECMA-241: " Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Message Waiting Indication Supplementary Service (MWISD), (International
Standard ISO/IEC 15505)".
[4] ITU-T Recommendation I.112: "Vocabulary of terms for ISDNs".
[5] ITU-T Recommendation I.210: "Principles of telecommunication services supported by an ISDN
and the means to describe them".
[6] ITU-T Recommendation Z.100: "Specification and Description Language (SDL)".
[7] ECMA-133: "Private Integrated Services Network (PISN) - Reference Configuration for PISN
Exchanges (PINX) (International Standard ISO/IEC 11579-1)".
ETSI
9 ETSI TS 102 254 V1.1.1 (2003-08)
4 Definitions
For the purposes of the present document, the following terms and definitions apply.
4.1 External definitions
The present document uses the following terms terms and definitions given in other documents:
Private Integrated services Network eXchange (PINX): See ECMA-133 [7].
Private Integrated Services Network (PISN): See ECMA-133 [7].
service: See ITU-T Recommendation I.112 [4].
signalling: See ITU-T Recommendation I.112 [4].
Supplementary Service (SS): See ITU-T Recommendation I.210 [5].
telecommunication service: See ECMA-142 [2].
user: See ECMA-142 [2].
4.2 Other definitions
4.2.1 Address Header
The Address Header includes Originator address information and, optionally, the receiving time stamp and the priority
of one specific message.
4.2.2 Complete Information
A complete list of Address Headers of either all New or all Retrieved Messages of one specific Message Type in a
Mailbox.
4.2.3 Compressed Information
Includes the number of either all New or all Retrieved Messages of one specific Message Type. Optionally, in the
compressed information the Originator address, the priority level and the time stamp of the highest priority message can
be included. If there is more than one message of the highest priority the optional information shall be related to the
latest received highest priority message.
4.2.4 Deleted Messages
A message of any Message Type which was previously stored in the Mailbox but which is not available anymore due to
deletion by the Served User.
4.2.5 Mailbox
A logical entity within a Message Centre which stores all messages (New Messages and Retrieved Messages) of one or
more Message Types for one specific Served User who is registered at the Message Centre.
ETSI
10 ETSI TS 102 254 V1.1.1 (2003-08)
4.2.6 Message Centre (MC)
The entity within the network which administrates Mailboxes for Served Users. The MC provides the Served User with
information:
• about each incoming New Message in the Served User's Mailbox, and
• about Message Status changes (e.g. due to retrieval or deletion) in the Served User's Mailbox,
• by means of Complete or Compressed Information for New and Retrieved Messages. This information is
provided by update procedures.
4.2.7 Message Status
Describes whether a stored message at the Served User's Mailbox is a New Message or a Retrieved Message.
4.2.8 Message Type
The type of a message stored at the MC. A Message Type indicates either the telecommunication service (e.g. speech,
3,1 kHz audio, etc.) that is needed to retrieve a specific message via a PISN or the general type of a message that might
not be directly retrieved by means of a PISN (e.g. email or video).
4.2.9 Message Waiting Signal (MWS)
Any type of signal presented to a Served User's terminal that is useful to draw a Served User's attention to the arrival of
a New Message in the Served User's Mailbox.
NOTE: The indication may be a lamp, special tone, display string etc. The technical realization of the Message
Waiting Signal is outside the scope of the present document.
4.2.10 New Message
A message of any Message Type, which is stored in a Mailbox. The Served User has not yet retrieved the message.
4.2.11 Originator
The user who has left a message at the Served User's Mailbox.
4.2.12 Originator address
Address information (i.e. Party Number) of the originator.
4.2.13 Retrieved Message
A message of any type, which is stored in a Mailbox. The Served User has already retrieved but not deleted the message
(i.e. the message is no longer a New Message).
4.2.14 Served User
The owner of a specific Mailbox at a Message Centre. The Served User receives an indication about status changes of
the messages in the Served User's Mailbox from the Message Centre.
ETSI
11 ETSI TS 102 254 V1.1.1 (2003-08)
5 List of acronyms
For the purposes of the present document the following acronyms apply:
ANF-CIDL Call Identification and Call Linkage
ANF-PR Path Replacement
ANF-PUMI Private User Mobility Incoming Call
ANF-PUMO Private User Mobility Outgoing Call
ANF-RRC Route Restriction Class
ANF-TC Transit Counter
FE Functional Entity
ISDN Integrated Services Digital Network
MC Message Centre
MCM Message Centre Monitoring
MID Mailbox IDentification
MWI Message Waiting Indication
PINX Private Integrated services Network eXchange
PISN Private Integrated Services Network
SDL Specification and Description Language
SS Supplementary Service
SS-AOC Advice of C
...