ISO/IEC 20117:2004

INTERNATIONAL ISO/IEC
STANDARD 20117
First edition
2004-05-15
Information technology —
Telecommunications and information
exchange between systems — Private
Integrated Services Network — Inter-
exchange signalling protocol — Message
centre monitoring and mailbox
identification supplementary services
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseau privé à intégration de
services — Protocole de signalisation d'échange — Services
supplémentaires de surveillance du centre du message et
d'identification de boîte aux lettres

Reference number
©
ISO/IEC 2004
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2004
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2004 – All rights reserved

Contents Page
Foreword. v
Introduction . vi
1 Scope. 1
2 Conformance . 1
3 Normative references . 2
4 Terms and definitions. 3
4.1 External definitions. 3
4.2 Other definitions . 3
5 Acronyms. 4
6 Signalling protocol for the support of SS-MCM. 4
6.1 SS-MCM description . 4
6.2 SS-MCM operational requirements . 4
6.3 SS-MCM coding requirements. 5
6.4 SS-MCM state definitions. 13
6.5 SS-MCM signalling procedures . 13
6.6 SS-MCM impact of interworking with public ISDNs . 20
6.7 SS-MCM impact of interworking with non-ISDNs . 21
6.8 Protocol interactions between SS-MCM and other supplementary services and ANFs . 21
6.9 SS-MCM parameter values (timers). 24
7 Signalling protocol for the support of SS-MID. 25
7.1 SS-MID description . 25
7.2 SS-MID operational requirements . 25
7.3 SS-MID coding requirements. 26
7.4 SS-MID state definitions. 28
7.5 SS-MID signalling procedures . 29
7.6 SS-MID impact of interworking with public ISDNs . 31
7.7 SS-MID impact of interworking with non-ISDNs . 31
7.8 Protocol interactions between SS-MID and other supplementary services and ANFs . 31
7.9 SS-MID parameter values (timers). 34
Annex A (normative) Protocol Implementation Conformance Statement (PICS) Proforma . 35
A.1 Introduction . 35
A.2 Instructions for completing the PICS proforma. 35
A.3 PICS proforma for SS-MCM. 37
A.4 PICS proforma for SS-MID. 41
Annex B (informative) Examples of Message Sequences. 44
B.1 Example message sequence for SS-MCM. 45
B.2 Example message sequences for interworking between for SS-MCM and SS-MWI. 53
B.3 Example message sequence for SS-MID. 62
Annex C (informative) Specification and Description Language (SDL) Representation of
Procedures . 64
C.1 SDL representation of SS-MCM at the Message Centre PINX. 65
C.2 SDL representation of SS-MCM at the Served User PINX. 72
C.3 SDL representation of SS-MID at the Message Centre PINX. 79
C.4 SDL representation of SS-MID at the Served User PINX. 82
© ISO/IEC 2004 – All rights reserved iii

Annex D (informative) List of Message Types .84
D.1 Telephony Type Messages.84
D.2 Data Type Messages .84
D.3 Combination of Messages.85
D.4 Additional Message Types .85

iv © ISO/IEC 2004 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 20117 was prepared by ECMA (as ECMA-347) and was adopted, under a special “fast-track
procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval
by national bodies of ISO and IEC.
© ISO/IEC 2004 – All rights reserved v

Introduction
This International Standard is one of a series defining services and signalling protocols applicable to Private
Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms
to the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC.
This International Standard specifies the signalling protocol for use at the Q reference point in support of the
Message Centre Monitoring supplementary service as well as the Mailbox Identification supplementary
service. The protocol defined in this International Standard forms part of the PSS1 protocol (informally known
as QSIG).
SS-MCM is based on SS-MWI and includes its entire functionality. The interoperability with SS-MWI is
therefore 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.
This International Standard is based upon the practical experience of ECMA member companies and the
results of their active and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other
international and national standardization bodies. It represents a pragmatic and widely based consensus.

vi © ISO/IEC 2004 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 20117:2004(E)

Information technology — Telecommunications and information
exchange between systems — Private Integrated Services
Network — Inter-exchange signalling protocol — Message
centre monitoring and mailbox identification supplementary
services
1 Scope
This International Standard specifies the signalling protocol for the support of the Message Centre Monitoring
supplementary service (SS-MCM) as well as the Mailbox Identification supplementary service (SS-MID) at the
Q reference point between Private Integrated services Network eXchanges (PINXs) connected together within
a Private Integrated Services Network (PISN).
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 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 Messages Centre.
The Q reference point is defined in ISO/IEC 11579-1.
Service specifications are produced in three stages and according to the method specified in ETS 300 387.
This International Standard contains the stage 3 specification for the Q reference point and satisfies the
requirements identified by the stage 1 and stage 2 specifications in ISO/IEC 20116.
The signalling protocol for SS-MCM and SS-MID uses certain aspects of the generic procedures for the
control of supplementary services specified in ISO/IEC 11582.
This International Standard also specifies additional signalling protocol requirements for the support of
interactions at the Q reference point between SS-MCM as well as SS-MID and other supplementary services
and ANFs.
NOTE Additional interactions that have no impact on the signalling protocol at the Q reference point can be found in
the relevant stage 1 specifications.
2 Conformance
In order to conform to this International Standard, a PINX shall satisfy the requirements identified in the
Protocol Implementation Conformance Statement (PICS) proforma in Annex A.
Conformance to this International Standard includes conforming to those clauses that specify protocol
interactions between SS-MCM as well as SS-MID and other supplementary services and ANFs for which
signalling protocols at the Q reference point are supported in accordance with the stage 3 standards
concerned.
© ISO/IEC 2004 – All rights reserved 1

3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 11572:2000, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Circuit mode bearer services — Inter-exchange signalling
procedures and protocol
ISO/IEC 11574:2000, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Circuit-mode 64 kbit/s bearer services — Service
description, functional capabilities and information flows
ISO/IEC 11579-1:1994, Information technology — Telecommunications and information exchange between
systems — Private integrated services network — Part 1: Reference configuration for PISN Exchanges (PINX)
ISO/IEC 11582:2002, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Generic functional protocol for the support of
supplementary services — Inter-exchange signalling procedures and protocol
ISO/IEC 13873:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call Diversion
supplementary services
ISO/IEC 15505:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Message Waiting Indication supplementary service
ISO/IEC 15506:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Message Waiting
Indication supplementary service
ISO/IEC 20116:2004, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Message centre monitoring and mailbox identification supplementary services
ISO 8601:2000, Data elements and interchange formats — Information interchange — Representation of
dates and times
ETS 300 387:1994, Private Telecommunication Network (PTN); Method for the specification of basic and
supplementary services
ITU-T Rec. I.112:1993, Vocabulary of terms for ISDNs
ITU-T Rec. I.210:1993, Principles of telecommunication services supported by an ISDN and the means to
describe them
ITU-T Rec. Q.950:2000, Digital Subscriber Signalling System No. 1 (DSS 1) — Supplementary services
protocols, structure and general principles
ITU-T Rec. Z.100:1999, Specification and Description Language
2 © ISO/IEC 2004 – All rights reserved

4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1 External definitions
This International Standard uses the following terms defined in other documents:
 Address Header (ISO/IEC 20116)
 Application Protocol Data Unit (APDU) (ISO/IEC 11582)
 Call-Independent (ISO/IEC 11582)
 Complete Information (ISO/IEC 20116)
 Compressed Information (ISO/IEC 20116)
 Gateway PINX (ISO/IEC 11582)
 Mailbox (ISO/IEC 20116)
 Message Centre (MC) (ISO/IEC 20116)
 Message Status (ISO/IEC 20116)
 Message Type (ISO/IEC 20116)
 Message Waiting Signal (ISO/IEC 20116)
 New Message (ISO/IEC 20116)
 Originating PINX (ISO/IEC 11582)
 Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
 Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
 Retrieved Message (ISO/IEC 20116)
 Served User (ISO/IEC 20116)
 Signalling (ITU-T Rec. I.112)
 Supplementary Service (ITU-T Rec. I.210)
 Supplementary Service Control Entity (ISO/IEC 11582)
 Terminating PINX (ISO/IEC 11582)
 Transit PINX (ISO/IEC 11582)
4.2 Other definitions
4.2.1
Message Centre PINX
The PINX where the Message Centre is located.
© ISO/IEC 2004 – All rights reserved 3

4.2.2
Served User PINX
The PINX where the Served User is located.
5 Acronyms
ANF Additional Network Feature
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation One
ISDN Integrated Services Digital Network
MCM Message Centre Monitoring
MID Mailbox Identification
NFE Network Facility Extension
PICS Protocol Implementation Conformance Statement
PINX Private Integrated services Network eXchange
PISN Private Integrated Services Network
SDL Specification and Description Language
SS Supplementary Service
6 Signalling protocol for the support of SS-MCM
6.1 SS-MCM description
The supplementary service MCM enables a Message Centre to inform a registered Served User about the
status and status changes of messages stored in the Served User’s Mailbox. This can be due to the arrival of
New Messages or due to the change of the Message Status of stored messages (e.g. retrieval or deletion of
messages). Additionally the Served User can request the current status of the messages in the Mailbox from
the Message Centre.
If there are new messages for the Served User stored in the mailbox, a Message Waiting Signal may be set at
the Served User’s terminal.
Additionally a Served User might activate, deactivate or interrogate Message Centre Monitoring individually for
the different Message Types.
6.2 SS-MCM operational requirements
6.2.1 Requirements on a Message Centre PINX
Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release
procedures, as specified in ISO/IEC 11572, shall apply.
Generic procedures for call-independent control (connection-oriented) of supplementary services, as specified
in ISO/IEC 11582 for an Originating PINX and for a Terminating PINX, shall apply.
4 © ISO/IEC 2004 – All rights reserved

6.2.2 Requirements on a Served User PINX
Call establishment procedures for the incoming and outgoing side of an inter-PINX link and call release
procedures, as specified in ISO/IEC 11572, shall apply.
Generic procedures for call-independent control (connection-oriented) of supplementary services, as specified
in ISO/IEC 11582 for a Terminating PINX and for an Originating PINX, shall apply.
6.2.3 Requirements on a Transit PINX
Basic Call procedures, specified in ISO/IEC 11572 for a Transit PINX, shall apply.
Generic procedures for call-independent control (connection-oriented) of supplementary services, as specified
in ISO/IEC 11582 for a Transit PINX, shall apply.
6.3 SS-MCM coding requirements
6.3.1 Operations
The operations defined in Abstract Syntax Notation One (ASN.1) in Table 1 shall apply.
NOTE The coding includes the operations as defined in SS-MWI (ISO/IEC 15506) but with the new operations
names of SS-MCM.
The following operations are identical in SS-MCM and SS-MWI:
SS-MCM operations SS-MWI operations
mCMNewMsg ÅÆ mWIActivate
mCMNoNewMsg ÅÆ mWIDeactivate
ÅÆ
mCMUpdateReq mWIInterrogate
Table 1 — Operations in support of SS-MCM
SS-MCM-Operations-asn1-97
{iso (1) identified-organization (3) icd-ecma (0012) standard (0)
qsig-message-centre-monitoring (347)
message-centre-monitoring-operations-asn1-97 (1)}

DEFINITIONS EXPLICIT TAGS ::=
BEGIN
IMPORTS      OPERATION, ERROR FROM
Remote-Operations-Information-Objects
{joint-iso-itu-t remote-operations (4) informationObjects (5)
version1 (0)}
EXTENSION, Extension{} FROM
Manufacturer-specific-service-extension-class-asn1-97
{iso standard pss1-generic-procedures (11582)
msi-class-asn1-97 (11)}
© ISO/IEC 2004 – All rights reserved 5

Table 1 — Operations in support of SS-MCM (continued)
basicServiceNotProvided, userNotSubscribed, invalidServedUserNr
FROM General-Error-List
{itu-t (0) recommendation (0) q (17) 950 (950)
general-error-list (1)}
PresentedAddressUnscreened, PartyNumber FROM
Addressing-Data-Elements-asn1-97
{iso standard pss1-generic-procedures (11582)
addressing-data-elements-asn1-97 (20)}
Name FROM Name-Operations-asn1-97
{iso standard pss1-name (13868) name-operations-asn1-97 (1)}
;
MCM-Operations  OPERATION ::= {
mCMNewMsg |
mCMNoNewMsg |
mCMUpdate |
mCMUpdateReq |
mCMService |
mCMInterrogate |
mCMailboxFull }
mCMNewMsg    OPERATION ::= {
ARGUMENT   MCMNewMsgArg
RESULT    MCMDummyRes
ERRORS    {userNotSubscribed |
invalidServedUserNr |
basicServiceNotProvided |
unspecified}
CODE     local: 80} -- same code as for mWIActivate in SS-MWI

mCMNoNewMsg   OPERATION ::= {
ARGUMENT   MCMNoNewMsgArg
RESULT    MCMDummyRes
ERRORS    {userNotSubscribed |
invalidServedUserNr |
basicServiceNotProvided |
unspecified}
CODE     local: 81} -- same code as for mWIDeactivate in SS-
MWI
mCMUpdate    OPERATION ::= {
ARGUMENT   MCMUpdateArg
RESULT    MCMDummyRes
ERRORS    {userNotSubscribed |
invalidServedUserNr |
unspecified}
CODE     local: 115}
6 © ISO/IEC 2004 – All rights reserved

Table 1 — Operations in support of SS-MCM (continued)
mCMUpdateReq   OPERATION ::= {
ARGUMENT   MCMUpdateReqArg
RESULT    MCMUpdateReqRes
ERRORS    {userNotSubscribed |
invalidServedUserNr |
basicServiceNotProvided |
unspecified}
CODE     local: 82}
-- same code as for mWIInterrogate in SS-MWI

mCMService     OPERATION  ::= {
ARGUMENT    MCMServiceArg
RESULT     MCMDummyRes
ERRORS     {userNotSubscribed |
invalidServedUserNr |
basicServiceNotProvided |
mCMModeNotProvided |
unspecified}
CODE      local: 116}
mCMInterrogate   OPERATION  ::= {
ARGUMENT    MCMInterrogateArg
RESULT     MCMInterrogateRes
ERRORS     {userNotSubscribed |
invalidServedUserNr |
basicServiceNotProvided |
mCMModeNotProvided |
unspecified}
CODE      local: 117}
mCMailboxFull    OPERATION  ::= {
ARGUMENT    MCMailboxFullArg
RETURN RESULT  FALSE
ALWAYS RESPONDS FALSE
CODE      local: 118}
MCMailboxFullArg ::= SEQUENCE
{
partyInfo      PartyInfo,
mailboxFullFor   MailboxFullFor,
extensions     MCMExtensions  OPTIONAL,
...
}
MailboxFullFor  ::= SEQUENCE OF MailboxFullPar

MailboxFullPar  ::= SEQUENCE
{
messageType     MessageType,
capacityReached   INTEGER (0.100) OPTIONAL
-- percentage of storage capacity already used
}
© ISO/IEC 2004 – All rights reserved 7

Table 1 — Operations in support of SS-MCM (continued)
MCMServiceArg   ::= SEQUENCE
{
partyInfo     PartyInfo,
mCMChange     MCMChange,
extensions    MCMExtensions  OPTIONAL,
...
}
MCMChange     ::= CHOICE
{
activateMCM     [1] IMPLICIT SEQUENCE OF MCMServiceInfo,
deactivateMCM    [2] IMPLICIT SEQUENCE OF MessageType,
setToDefaultValues NULL
}
MCMServiceInfo   ::= SEQUENCE
{
messageType     MessageType,
mCMModeNew     [1] IMPLICIT MCMMode  OPTIONAL,
mCMModeRetrieved  [2] IMPLICIT MCMMode  OPTIONAL
}
MCMInterrogateArg ::= SEQUENCE
{
partyInfo      PartyInfo,
interrogateInfo   SEQUENCE OF MessageType,
extensions     MCMExtensions  OPTIONAL,
...
}
MCMInterrogateRes ::= SEQUENCE
{
interrogateResult  SEQUENCE OF MCMServiceInfo,
extensions     MCMExtensions  OPTIONAL,
...
}
MCMNewMsgArg    ::= SEQUENCE
{
servedUserNr     PartyNumber,
specificMessageType MessageType,
msgCentreId     MsgCentreId         OPTIONAL,
nrOfMessages     [3] IMPLICIT NrOfMessages  OPTIONAL,
originatingNr    [4] PartyNumber       OPTIONAL,
timestamp      TimeStamp          OPTIONAL,
priority       [5] IMPLICIT INTEGER (0.9) OPTIONAL,
argumentExt  CHOICE {
extension      [6] IMPLICIT Extension{{MCMExtSet}},
multipleExtension  [7] IMPLICIT SEQUENCE OF
Extension{{MCMExtSet}}
} OPTIONAL
}
8 © ISO/IEC 2004 – All rights reserved

Table 1 — Operations in support of SS-MCM (continued)
MCMNoNewMsgArg   ::= SEQUENCE
{
servedUserNr      PartyNumber,
specificMessageType  MessageType,
msgCentreId      MsgCentreId     OPTIONAL,
argumentExt      CHOICE {
extension      [3] IMPLICIT Extension{{MCMExtSet}},
multipleExtension  [4] IMPLICIT SEQUENCE OF
Extension{{MCMExtSet}}
} OPTIONAL
}
MCMUpdateArg   ::= SEQUENCE
{
partyInfo       PartyInfo,
messageType      MessageType,
updateInfo       UpdateInfo,
moreInfoFollows    BOOLEAN DEFAULT FALSE,
extensions       MCMExtensions    OPTIONAL,
...
}
MCMUpdateReqArg ::= SEQUENCE
{
servedUserNr     PartyNumber,
specificMessageType  MessageType,
msgCentreId      MsgCentreId     OPTIONAL,
argumentExt      CHOICE {
extension       [3] IMPLICIT Extension{{MCMExtSet}},
multipleExtension   [4] IMPLICIT SEQUENCE OF
Extension{{MCMExtSet}}
} OPTIONAL
}
MCMUpdateReqRes ::= SEQUENCE SIZE (1.10) OF MCMUpdateReqResElt

MCMUpdateReqResElt ::= SEQUENCE
{
specificMessageType  MessageType,
msgCentreId      MsgCentreId         OPTIONAL,
nrOfMessages      [3] IMPLICIT NrOfMessages  OPTIONAL,
originatingNr     [4] PartyNumber       OPTIONAL,
timestamp       TimeStamp          OPTIONAL,
priority        [5] IMPLICIT INTEGER (0.9) OPTIONAL,
argumentExt      CHOICE {
extension      [6] IMPLICIT
Extension{{MCMExtSet}},
multipleExtension  [7] IMPLICIT SEQUENCE OF
Extension{{MCMExtSet}}
} OPTIONAL
}
© ISO/IEC 2004 – All rights reserved 9

Table 1 — Operations in support of SS-MCM (continued)
MCMMode    ::= INTEGER
{
compressed   (0),
complete    (1)
}
MCMDummyRes  ::= MCMExtensions

PartyInfo ::= SEQUENCE
{
servedUserNr    PartyNumber,
messageCentreID   MsgCentreId
}
UpdateInfo   ::= CHOICE
{
newMsgInfoOnly     [1] MessageInfo,
retrievedMsgInfoOnly  [2] MessageInfo,
allMsgInfo       AllMsgInfo
}
AllMsgInfo   ::= SEQUENCE
{
newMsgInfo     MessageInfo,
retrievedMsgInfo  MessageInfo
}
MessageInfo  ::= CHOICE
{
completeInfo    [1] IMPLICIT CompleteInfo,
compressedInfo   [2] IMPLICIT CompressedInfo,
noMsgsOfMsgType   NULL
}
CompleteInfo  ::= SEQUENCE OF AddressHeader

AddressHeader ::= SEQUENCE
{
originatorNr    PartyNumber,
timeStamp      [1] IMPLICIT TimeStamp    OPTIONAL,
priority      [2] IMPLICIT Priority    OPTIONAL
}
CompressedInfo  ::= SEQUENCE
{
nrOfMessages    NrOfMessages,
lastTimeStamp    TimeStamp     OPTIONAL,
highestPriority   Priority     OPTIONAL
}
NrOfMessages   ::= INTEGER (0.65535)
10 © ISO/IEC 2004 – All rights reserved

Table 1 — Operations in support of SS-MCM (continued)
Priority     ::= INTEGER (0.9)   -- the value 0 means the highest priority
-- and 9 the lowest
MsgCentreId    ::= CHOICE
{
integer     [0] IMPLICIT INTEGER (0.65535),
partyNumber   [1] PartyNumber,
numericString  [2] IMPLICIT NumericString (SIZE(1.10))
}
TimeStamp     ::= GeneralizedTime (SIZE (12.19))
-- a VisibleString containing:
--  - the (local) date in 8 digits (YYYYMMDD),
--  - followed by (local) time of day in 4 or 6 digits (HHMM[SS]),
--  - optionally followed by the letter "Z" or
--   by a local time differential in 5 digits ("+"HHMM or "-"HHMM);
--   this date and time representation follows ISO 8601
-- Examples:   1) 19970621194530, meaning 21 June 1997, 19:45:30;
--         2) 19970621194530Z, meaning the same as 1);
--         3) 19970621194530-0500, meaning the same as 1),
--          5 hours retarded in relation to UTC time

MessageType    ::= ENUMERATED
{
-- Note: for the following message type see also Annex D.4
allServices          (0),
-- Note: for the following message types see also Annex D.1
-- For compatibility among vendors, speech is recommended for
-- voice mail indications
speech             (1),
unrestrictedDigitalInformation (2),
audio3100Hz           (3),
telephony           (32),
teletex            (33),
telefaxGroup4Class1      (34),
videotextSyntaxBased      (35),
videotelephony         (36),
telefaxGroup2-3        (37),
reservedNotUsed1        (38),
reservedNotUsed2        (39),
reservedNotUsed3        (40),
reservedNotUsed4        (41),
reservedNotUsed5        (42),
-- Note: for the following message types see also Annex D.2
email             (51),
video             (52),
fileTransfer          (53),
shortMessageService      (54),
-- Note: for the following message types see also Annex D.3
speechAndVideo         (55),
speechAndFax          (56),
speechAndEmail         (57),
videoAndFax          (58),
videoAndEmail         (59),
faxAndEmail          (60),
speechVideoAndFax       (61),
© ISO/IEC 2004 – All rights reserved 11

Table 1 — Operations in support of SS-MCM (concluded)
speechVideoAndEmail      (62),
speechFaxAndEmail       (63),
videoFaxAndEmail        (64),
speechVideoFaxAndEmail     (65),
-- Note: for the following message types see also Annex D.4
multimediaUnknown       (66),
serviceUnknown         (67),
futureReserve1         (68),
futureReserve2         (69),
futureReserve3         (70),
futureReserve4         (71),
futureReserve5         (72),
futureReserve6         (73),
futureReserve7         (74),
futureReserve8         (75)
}
MCMExtensions  ::= CHOICE
{
none        NULL,
extension     [1] IMPLICIT Extension {{MCMExtSet}},
multipleExtension [2] IMPLICIT SEQUENCE OF
Extension {{ MCMExtSet }}
}
mCMModeNotProvided   ERROR  ::= {
CODE    local 1037}
unspecified      ERROR ::= {
PARAMETER  Extension{{MCMExtSet}}
CODE    local 1008}
MCMExtSet   EXTENSION ::= {.}

END    -- of SS-MCM-Operations-asn1-97

6.3.2 Information elements
6.3.2.1 Facility information element
The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with
ISO/IEC 11582.
When conveying the invoke APDU of operations defined in 6.3.1, the destination Entity data element of the
NFE shall contain the value endPINX.
When conveying the mCMailboxFull invoke APDU defined in 6.3.1, the interpretation APDU shall be set to
discardAnyUnrecognisedInvokePDU. When conveying any other invoke APDU of operations defined in 6.3.1,
the interpretation APDU shall either be omitted or have the value rejectAnyUnrecognisedInvokePdu.
6.3.2.2 Other information elements
Any other information element shall be coded in accordance with ISO/IEC 11582.
12 © ISO/IEC 2004 – All rights reserved

6.3.3 Messages
The Facility information element shall be conveyed in messages as specified in Clause 10 of ISO/IEC 11582.
6.4 SS-MCM state definitions
6.4.1 States at the Message Centre PINX
The procedures for the Message Centre PINX are written in terms of the following conceptual states existing
within the SS-MCM Supplementary Service Control entity in that PINX.
6.4.1.1 State MCM-MC-idle
SS-MCM is not operating.
6.4.1.2 State MCM-MC-wait
The invoke APDU of one of the following operations has been sent: mCMNewMsg, mCMNoNewMsg and
mCMUpdate operation. The Message Centre PINX is waiting for the corresponding response.
6.4.2 States at the Served User PINX
The procedures for the Served User PINX are written in terms of the following conceptual states existing
within the SS-MCM Supplementary Service Control entity in that PINX.
6.4.2.1 State MCM-SU-idle
SS-MCM is not operating.
6.4.2.2 State MCM-SU-wait
The invoke APDU of one of the following operations has been sent: mCMService, mCMInterrogate or
mCMUpdateReq operation. The Served User PINX is waiting for the corresponding response.
6.4.2.3 State MCM-SU-update
The invoke APDU of the operation mCMUpdate has been received with value “moreInfoFollows” set to TRUE.
The Served User PINX is waiting for the consecutive mCMUpdate invoke APDU.
6.5 SS-MCM signalling procedures
For the exchange of the SS-MCM APDUs a call independent signalling connection shall be used between the
Message Centre PINX and the Served User PINX. If no such connection exists the sender of the invoke
APDU of the operations defined in 6.3.1 (either the Message Centre PINX or the Served User PINX) shall
establish a call independent signalling connection as specified in 7.3 of ISO/IEC 11582. The corresponding
return result or return error APDU shall use the same Call Reference as the invoke APDU. Call clearing is the
responsibility of the sender who has established the call independent signalling connection. This may occur on
receipt of a return result, return error or reject APDU. Alternatively, the signalling connection may be retained
for other applications, if appropriate.
Examples of message sequences are shown in Clause B.1 of Annex B.
6.5.1 Actions at the Message Centre PINX
The SDL representation of procedures at the Message Centre PINX is shown in Clause C.1 of Annex C.
© ISO/IEC 2004 – All rights reserved 13

6.5.1.1 Normal procedures
6.5.1.1.1 Activation, deactivation and interrogation
SS-MCM shall be available in a default configuration as arranged by the service provider. Within the default
configuration an activation (i.e. re-activation after a previous deactivation or change of actual parameters)
and/or deactivation of the monitoring of messages of specific Message Types can be done. Therefore, in
general, upon receipt of a mCMService invoke APDU the Message Centre PINX shall check if the request (i.e.
activation or deactivation of Me
...