SIST ES 202 391-5 V1.3.1:2008

• Abstract:

  Update of ES 202 391 to become Parlay X 2.2, to cover maintenance updates.The present document is part 5 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).; The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs.; The present document specifies the Multimedia Messaging Web Service. The following are defined here:; • Name spaces.; • Sequence diagrams.; • Data definitions.; • Interface specification plus detailed method descriptions.; • Fault definitions.; • Service Policies.; • WSDL Description of the interfaces.

• Status: Published
• Publication Date: 15-Jul-2008
• ICS: 35.100.01 - Open systems interconnection in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 19-Jun-2008
• Due Date: 24-Aug-2008
• Completion Date: 16-Jul-2008
• Ref Project: ETSI ES 202 391-5 V1.3.1 (2008-05) - Open Service Access (OSA); Parlay X Web Services; Part 5: Multimedia Messaging (Parlay X 2)

SIST ES 202 391-5 V1.3.1:2008 is the SIST reference for an ETSI Standard in the Open Service Access (OSA) family. It specifies the Parlay X Web Services Multimedia Messaging service, so applications can send, receive, poll delivery status, and handle notifications through a standard web service interface instead of network-specific messaging protocols. The document is meant for application developers, service providers, and integrators who need the service interface, data types, faults, policies, and WSDL.

What does SIST ES 202 391-5 V1.3.1:2008 specify?

SIST ES 202 391-5 V1.3.1:2008 specifies Part 5 of the Stage 3 Parlay X 2 Web Services specification for OSA, focused on Multimedia Messaging. It defines the web service interfaces and supporting schema needed to expose messaging capabilities through OSA APIs.

The document is organized into scope, references, definitions and abbreviations, a detailed service description, namespaces, sequence diagrams, XML Schema data types, web service interface definitions, fault definitions, service policies, and annexes.

Annex	What it covers
Annex A	Normative WSDL for Multimedia Messaging
Annex B	Informative bibliography

What are the key requirements of SIST ES 202 391-5 V1.3.1:2008?

SIST ES 202 391-5 V1.3.1:2008 defines how an application sends multimedia messages, checks delivery, receives messages, and subscribes to notifications. In practice, that means the standard describes both the request/response messages and the service behavior around them.

• Clause 4 presents Multimedia Messaging as a network-neutral service that can map to SMS, EMS, MMS, IM, E-mail, and similar services. This matters because one application interface can be used across different messaging networks.
• Clause 5 assigns separate namespaces for SendMessage, ReceiveMessage, MessageNotification, MessageNotificationManager, and the XML schema data types. Implementers need these namespaces to build compatible WSDL and XML payloads.
• Clause 7 defines the core data types: DeliveryStatus, MessagePriority, DeliveryInformation, MessageReference, and MessageURI. These types are what the application reads back to determine message state, priority, and content location.
• Clause 8.1 defines sendMessage for one or more destination addresses, with optional sender address, subject, priority, charging information, and receipt request. The content is sent as attachments using SOAP Messages with Attachments, so the message body and files can travel together.
• Clause 8.1 also ties send behavior to faults and policies. Group addresses may be used only if group support is enabled, and unsupported delivery receipt notification returns SVC0283. That tells a buyer or integrator to check platform capabilities before relying on group delivery or receipt callbacks.
• Clause 8.1.2 defines getMessageDeliveryStatus as the polling method for delivery status, keyed by the request identifier returned from sendMessage. The service keeps status only for a limited time, so client systems need to poll before the retention interval expires.
• Clause 8.2 defines three receive paths: getReceivedMessages returns references to new messages, getMessageURIs returns local file URIs for the parts of a message, and getMessage returns the whole message as an attachment. This lets applications choose between lightweight message listing and full content retrieval.
• Clause 8.3 and 8.4 define asynchronous notification with notifyMessageReception, notifyMessageDeliveryReceipt, startMessageNotification, and stopMessageNotification. The notification setup uses a correlator and criteria matching, so applications can route incoming messages to the right endpoint and track each subscription.
• Clause 10 defines service policies for GroupSupport, NestedGroupSupport, ChargingSupported, StatusRetentionTime, and MessageRetentionTime. These policy values tell the application what the service can do and how long it will keep delivery status or received messages available.

What terms does SIST ES 202 391-5 V1.3.1:2008 define?

SIST ES 202 391-5 V1.3.1:2008 uses a small set of service terms that matter when you implement or test the interface.

• Open Service Access (OSA) - The architecture that exposes network functionality through open standardized interfaces.
• Multimedia Messaging Service (MMS) - The network messaging service covered by this part, including message send, receive, and delivery handling.
• MMS-C - The Multimedia Messaging Service Centre, shown in the service description as the network element that handles multimedia message processing.
• DeliveryStatus - The status enum used to report whether a message reached the network, reached the terminal, is waiting, is impossible to deliver, or cannot support delivery notification.
• MessagePriority - The priority enum used to classify messages as Default, Low, Normal, or High.
• MessageReference - The structure that carries the metadata for a received message, including sender, subject, priority, and optional stored message content.
• MessageURI - The structure that points to the message body text and attachment files through URIs.
• Whitespace - The character handling rule taken from RFC 2822 and used when matching notification criteria.

Who uses SIST ES 202 391-5 V1.3.1:2008?

Application developers use SIST ES 202 391-5 V1.3.1:2008 to build messaging functions into portals, mobile services, and enterprise applications. They use the send, receive, delivery status, and notification operations to avoid direct integration with network-specific protocols.

Network operators and Parlay X gateway providers use it to expose multimedia messaging capabilities through a standard web service layer. Platform and integration teams use it to map service policies, address handling, and attachments to the underlying messaging network.

QA and test teams use the sequence diagrams, data types, faults, and WSDL to verify interoperability. Buyers and solution architects use it to judge whether the service supports polling, asynchronous notifications, group addressing, charging, and message retention.

What changed in SIST ES 202 391-5 V1.3.1:2008 from the previous edition?

SIST ES 202 391-5 V1.3.1:2008 updates ES 202 391 to become Parlay X 2.2 and includes maintenance updates. The foreword also states that it forms part of the Parlay X 2.2 set of specifications and is equivalent to 3GPP TS 29.199-05 V6.8.0 (Release 6).

Which standards are used with SIST ES 202 391-5 V1.3.1:2008?

Standard	What it contributes
ETSI ES 202 391-1, Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2)	Base definitions, common framework, shared types, and the common service context used by this part
W3C Recommendation, XML Schema Part 2: Datatypes	The XML Schema datatypes used for xsd-based fields such as strings, URIs, and dateTime
W3C Note, SOAP Messages with Attachments	The attachment model used for message content and retrieval
IETF RFC 2822, Internet Message Format	The message-format reference used for the Whitespace definition
ETSI ES 202 391-4, Short Messaging	The related Parlay X messaging part for SMS-oriented services within the same family

What does the SIST ES 202 391-5 V1.3.1:2008 document contain?

SIST ES 202 391-5 V1.3.1:2008 contains a service overview, namespace assignments, two example sequence diagrams, XML Schema data type definitions, and detailed web service operations for sending and receiving multimedia messages. It also includes fault definitions and service policies that control group support, charging support, and retention times.

The interface material covers SendMessage, ReceiveMessage, MessageNotification, and MessageNotificationManager, including request and response messages and referenced faults. Annex A provides the normative WSDL package for the Multimedia Messaging interface, and Annex B lists the bibliography.

Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 5: Multimedia Messaging
(Parlay X 2)
�
2 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)

Reference
RES/TISPAN-01056-05-OSA
Keywords
API, OSA, 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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.9
6 Sequence diagrams.9
6.1 Send picture.9
6.2 Send WAP Push message.10
7 XML Schema data type definition .11
7.1 DeliveryStatus enumeration.11
7.2 MessagePriority enumeration.11
7.3 DeliveryInformation structure.12
7.4 MessageReference structure.12
7.5 MessageURI structure.12
8 Web Service interface definition.12
8.1 Interface: SendMessage.12
8.1.1 Operation: sendMessage.12
8.1.1.1 Input message: sendMessageRequest.13
8.1.1.2 Output message: sendMessageResponse.13
8.1.1.3 Referenced faults.13
8.1.2 Operation: getMessageDeliveryStatus.14
8.1.2.1 Input message: getMessageDeliveryStatusRequest .14
8.1.2.2 Output message: getMessageDeliveryStatusResponse .14
8.1.2.3 Referenced faults.14
8.2 Interface: ReceiveMessage.14
8.2.1 Operation: getReceivedMessages.14
8.2.1.1 Input message: getReceivedMessagesRequest.15
8.2.1.2 Output message: getReceivedMessagesResponse.15
8.2.1.3 Referenced faults.15
8.2.2 Operation: getMessageURIs.15
8.2.2.1 Input message: getMessageURIsRequest.15
8.2.2.2 Output message: getMessageURIsResponse.15
8.2.2.3 Referenced faults.15
8.2.3 Operation: getMessage.16
8.2.3.1 Input message: getMessageRequest .16
8.2.3.2 Output message: getMessageResponse.16
8.2.3.3 Referenced faults.16
8.3 Interface: MessageNotification.16
8.3.1 Operation: notifyMessageReception.16
8.3.1.1 Input message: notifyMessageReceptionRequest .16
8.3.1.2 Output message: notifyMessageReceptionResponse.17
8.3.1.3 Referenced faults.17
8.3.2 Operation: notifyMessageDeliveryReceipt.17
8.3.2.1 Input message: notifyMessageDeliveryReceiptRequest .17
8.3.2.2 Output message: notifyMessageDeliveryReceiptResponse .17
8.3.2.3 Referenced faults.17
8.4 Interface: MessageNotificationManager .17
8.4.1 Operation: startMessageNotification.18
ETSI
4 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
8.4.1.1 Input message: startMessageNotificationRequest.18
8.4.1.2 Output message: startMessageNotificationResponse.18
8.4.1.3 Referenced Faults.18
8.4.2 Operation: stopMessageNotification.18
8.4.2.1 Input message: stopMessageNotificationRequest .19
8.4.2.2 Output message: stopMessageNotificationResponse.19
8.4.2.3 Referenced Faults.19
9 Fault definitions.19
9.1 ServiceException.19
9.1.1 Void.19
9.1.2 SVC0283: Delivery Receipt Notification not supported.19
10 Service policies .19
Annex A (normative): WSDL for Multimedia Messaging.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
The present document is part 5 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-05 V6.8.0 (Release 6).
ETSI
6 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
1 Scope
The present document is part 5 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Messaging Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
[3] W3C Note (11 December 2000): "SOAP Messages with Attachments".
NOTE: Available at: http://www.w3.org/TR/SOAP-attachments.
[4] IETF RFC 2822: "Internet Message Format".
NOTE: Available at: http://www.ietf.org/rfc/rfc2822.txt
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] and the following apply:
Whitespace: See definition for CFWS as defined in RFC 2822 [4].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] and the following apply:
EMS Enhanced Messaging Service
IM Instant Messaging
MMS Multimedia Messaging Service
MMS-C Multimedia Messaging Service – Centre
OMA Open Mobile Alliance
SMS Short Message Service
WAP Wireless Application Protocol
4 Detailed service description
Currently, in order to programmatically receive and send Multimedia Messages, it is necessary to write applications
using specific protocols to access MMS functions provided by network elements (e.g. MMS-C). This approach requires
application developers to have a high degree of network expertise.
This contribution defines a Multimedia Messaging Web Service that can map to SMS, EMS, MMS, IM, E-mail, etc.
The choice is between defining one set of interfaces per messaging network or a single set common to all networks;
e.g. we could define sendMMS, sendEMS, sendSMS, etc., or just use sendMessage. Although the more specific the API
the easier it is to use, there are advantages to a single set of network-neutral APIs. These advantages include:
• improved service portability;
• lower complexity, by providing support for generic user terminal capabilities only.
For this version of the Parlay X 2 specification, we provide sets of interfaces for two messaging Web Services:
Short Messaging (part 4) and Multimedia Messaging (the present document), which provides generic messaging
features (including SMS).
Multimedia Messaging provides operations (see clause 8.1, SendMessage API) for sending a Multimedia message to
the network and a polling mechanism for monitoring the delivery status of a sent Multimedia message. It also provides
an asynchronous notification mechanism for delivery status (see clause 8.3, MessageNotification API).
Multimedia Messaging also allows an application to receive Multimedia messages. Both a polling (see clause 8.2,
ReceiveMessage API) and an asynchronous notification mechanism (see clause 8.3, MessageNotification API and
clause 8.4, MessageNotificationManager API) are available.
ETSI
8 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)
Figure 1 shows an example scenario using sendMessage and getMessageDeliveryStatus to send data to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to retrieve a
stock quote (1) and (2) and sends the current quote - sendMessage - using the Parlay X Interface (3) of the Multimedia
Messaging Web Service. After invocation, the Multimedia Message Web Service sends the message to an MMS-C
using the MM7 interface (4) for onward transmission (5) to the subscriber over the Mobile network.
Later, when the next quote is ready, the application checks to see - getMessageDeliveryStatus - if the previous quote
has been successfully delivered to the subscriber. If not, it may for instance perform an action (not shown) to provide a
credit for the previous message transmission. This way, the subscriber is only charged for a stock quote if it is delivered
on time.
Multimedia
Stock Quote
Message Web
Stock Quote MMSC -X
Web Service
Service 4
Web Service component
Parlay X I/F
MMS-C
MMSC
MM7 VASP
Interface
…… .
content1 =getStockQuote ()
….
Retrieve
user Profile
Mobile network
….
sendMessage( content )
messageId=
….
status= getMessageDeliveryStatus (messageId)
if status=Message_Waiting
….
fi
User
…
profile
content2 =getStockQuote ()
messageId= sendMessage ( content2 )

Figure 1: Multimedia Messaging Scenario
Alternatively this service could have been built using WAP Push features in the network.
Figure 2 shows an example scenario using sendMessage and getMessageDeliveryStatus to send a link to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to generate a
stock quote graph (1) and (2) and sends the current quote as a WAP Push link - sendMessage - using the Parlay X
Interface (3) of the Multimedia Messaging Web Service. After invocation, the Multimedia Message Web Service sends
the message to an SMS-C (4) for onward transmission (5) to the subscriber over the Mobile network. The subscriber
can then open the link and access his content.
ETSI
9 Final draft ETSI ES 202 391-5 V1.3.1 (2008-02)

Figure 2: WAP Push scenario
5 Namespaces
The SendMessage interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_5
The ReceiveMessage interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/receive/v2_5
The MessageNotification interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification/v2_4
The MessageNotificationManager interface uses
...

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 5: Multimedia Messaging
(Parlay X 2)
�
2 ETSI ES 202 391-5 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-05-OSA
Keywords
API, OSA, 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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 ES 202 391-5 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.9
6 Sequence diagrams.9
6.1 Send picture.9
6.2 Send WAP Push message.10
7 XML Schema data type definition .11
7.1 DeliveryStatus enumeration.11
7.2 MessagePriority enumeration.11
7.3 DeliveryInformation structure.12
7.4 MessageReference structure.12
7.5 MessageURI structure.12
8 Web Service interface definition.12
8.1 Interface: SendMessage.12
8.1.1 Operation: sendMessage.12
8.1.1.1 Input message: sendMessageRequest.13
8.1.1.2 Output message: sendMessageResponse.13
8.1.1.3 Referenced faults.13
8.1.2 Operation: getMessageDeliveryStatus.14
8.1.2.1 Input message: getMessageDeliveryStatusRequest .14
8.1.2.2 Output message: getMessageDeliveryStatusResponse .14
8.1.2.3 Referenced faults.14
8.2 Interface: ReceiveMessage.14
8.2.1 Operation: getReceivedMessages.14
8.2.1.1 Input message: getReceivedMessagesRequest.15
8.2.1.2 Output message: getReceivedMessagesResponse.15
8.2.1.3 Referenced faults.15
8.2.2 Operation: getMessageURIs.15
8.2.2.1 Input message: getMessageURIsRequest.15
8.2.2.2 Output message: getMessageURIsResponse.15
8.2.2.3 Referenced faults.15
8.2.3 Operation: getMessage.16
8.2.3.1 Input message: getMessageRequest .16
8.2.3.2 Output message: getMessageResponse.16
8.2.3.3 Referenced faults.16
8.3 Interface: MessageNotification.16
8.3.1 Operation: notifyMessageReception.16
8.3.1.1 Input message: notifyMessageReceptionRequest .16
8.3.1.2 Output message: notifyMessageReceptionResponse.17
8.3.1.3 Referenced faults.17
8.3.2 Operation: notifyMessageDeliveryReceipt.17
8.3.2.1 Input message: notifyMessageDeliveryReceiptRequest .17
8.3.2.2 Output message: notifyMessageDeliveryReceiptResponse .17
8.3.2.3 Referenced faults.17
8.4 Interface: MessageNotificationManager .17
8.4.1 Operation: startMessageNotification.18
ETSI
4 ETSI ES 202 391-5 V1.3.1 (2008-05)
8.4.1.1 Input message: startMessageNotificationRequest.18
8.4.1.2 Output message: startMessageNotificationResponse.18
8.4.1.3 Referenced Faults.18
8.4.2 Operation: stopMessageNotification.18
8.4.2.1 Input message: stopMessageNotificationRequest .19
8.4.2.2 Output message: stopMessageNotificationResponse.19
8.4.2.3 Referenced Faults.19
9 Fault definitions.19
9.1 ServiceException.19
9.1.1 Void.19
9.1.2 SVC0283: Delivery Receipt Notification not supported.19
10 Service policies .19
Annex A (normative): WSDL for Multimedia Messaging.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 ETSI ES 202 391-5 V1.3.1 (2008-05)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 5 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-05 V6.8.0 (Release 6).
ETSI
6 ETSI ES 202 391-5 V1.3.1 (2008-05)
1 Scope
The present document is part 5 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Messaging Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 ETSI ES 202 391-5 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
[3] W3C Note (11 December 2000): "SOAP Messages with Attachments".
NOTE: Available at: http://www.w3.org/TR/SOAP-attachments.
[4] IETF RFC 2822: "Internet Message Format".
NOTE: Available at: http://www.ietf.org/rfc/rfc2822.txt
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] and the following apply:
Whitespace: See definition for CFWS as defined in RFC 2822 [4].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] and the following apply:
EMS Enhanced Messaging Service
IM Instant Messaging
MMS Multimedia Messaging Service
MMS-C Multimedia Messaging Service – Centre
OMA Open Mobile Alliance
SMS Short Message Service
WAP Wireless Application Protocol
4 Detailed service description
Currently, in order to programmatically receive and send Multimedia Messages, it is necessary to write applications
using specific protocols to access MMS functions provided by network elements (e.g. MMS-C). This approach requires
application developers to have a high degree of network expertise.
This contribution defines a Multimedia Messaging Web Service that can map to SMS, EMS, MMS, IM, E-mail, etc.
The choice is between defining one set of interfaces per messaging network or a single set common to all networks;
e.g. we could define sendMMS, sendEMS, sendSMS, etc., or just use sendMessage. Although the more specific the API
the easier it is to use, there are advantages to a single set of network-neutral APIs. These advantages include:
• improved service portability;
• lower complexity, by providing support for generic user terminal capabilities only.
For this version of the Parlay X 2 specification, we provide sets of interfaces for two messaging Web Services:
Short Messaging (part 4) and Multimedia Messaging (the present document), which provides generic messaging
features (including SMS).
Multimedia Messaging provides operations (see clause 8.1, SendMessage API) for sending a Multimedia message to
the network and a polling mechanism for monitoring the delivery status of a sent Multimedia message. It also provides
an asynchronous notification mechanism for delivery status (see clause 8.3, MessageNotification API).
Multimedia Messaging also allows an application to receive Multimedia messages. Both a polling (see clause 8.2,
ReceiveMessage API) and an asynchronous notification mechanism (see clause 8.3, MessageNotification API and
clause 8.4, MessageNotificationManager API) are available.
ETSI
8 ETSI ES 202 391-5 V1.3.1 (2008-05)
Figure 1 shows an example scenario using sendMessage and getMessageDeliveryStatus to send data to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to retrieve a
stock quote (1) and (2) and sends the current quote - sendMessage - using the Parlay X Interface (3) of the Multimedia
Messaging Web Service. After invocation, the Multimedia Message Web Service sends the message to an MMS-C
using the MM7 interface (4) for onward transmission (5) to the subscriber over the Mobile network.
Later, when the next quote is ready, the application checks to see - getMessageDeliveryStatus - if the previous quote
has been successfully delivered to the subscriber. If not, it may for instance perform an action (not shown) to provide a
credit for the previous message transmission. This way, the subscriber is only charged for a stock quote if it is delivered
on time.
Multimedia
Stock Quote
Message Web
Stock Quote MMSC -X
Web Service
Service 4
Web Service component
Parlay X I/F
MMS-C
MMSC
MM7 VASP
Interface
…… .
content1 =get StockQuote ()
….
Retrieve
user Profile
Mobile network
….
content
messageId= sendMessage( )
….
status= getMessageDeliveryStatus (messageId)
if status=Message_Waiting
….
fi
User
…
profile
content2 =get StockQuote ()
messageId= sendMessage ( content2 )

Figure 1: Multimedia Messaging Scenario
Alternatively this service could have been built using WAP Push features in the network.
Figure 2 shows an example scenario using sendMessage and getMessageDeliveryStatus to send a link to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to generate a
stock quote graph (1) and (2) and sends the current quote as a WAP Push link - sendMessage - using the Parlay X
Interface (3) of the Multimedia Messaging Web Service. After invocation, the Multimedia Message Web Service sends
the message to an SMS-C (4) for onward transmission (5) to the subscriber over the Mobile network. The subscriber
can then open the link and access his content.
ETSI
9 ETSI ES 202 391-5 V1.3.1 (2008-05)

Figure 2: WAP Push scenario
5 Namespaces
The SendMessage interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_5
The ReceiveMessage interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/receive/v2_5
The MessageNotification interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/notification/v2_4
The MessageNotificationManager interface uses the namespace:
http://w
...

SLOVENSKI STANDARD
01-september-2008
2GSUWLGRVWRSGRVWRULWYH26$6SOHWQHVWRULWYH3DUOD\;GHO
9HþSUHGVWDYQRVWQRVSRURþDQMH3DUOD\;
Open Service Access (OSA) - Parlay X Web Services - Part 5: Multimedia Messaging
(Parlay X 2)
Ta slovenski standard je istoveten z: ES 202 391-5 Version 1.3.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 5: Multimedia Messaging
(Parlay X 2)
�
2 ETSI ES 202 391-5 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-05-OSA
Keywords
API, OSA, 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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 ES 202 391-5 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.9
6 Sequence diagrams.9
6.1 Send picture.9
6.2 Send WAP Push message.10
7 XML Schema data type definition .11
7.1 DeliveryStatus enumeration.11
7.2 MessagePriority enumeration.11
7.3 DeliveryInformation structure.12
7.4 MessageReference structure.12
7.5 MessageURI structure.12
8 Web Service interface definition.12
8.1 Interface: SendMessage.12
8.1.1 Operation: sendMessage.12
8.1.1.1 Input message: sendMessageRequest.13
8.1.1.2 Output message: sendMessageResponse.13
8.1.1.3 Referenced faults.13
8.1.2 Operation: getMessageDeliveryStatus.14
8.1.2.1 Input message: getMessageDeliveryStatusRequest .14
8.1.2.2 Output message: getMessageDeliveryStatusResponse .14
8.1.2.3 Referenced faults.14
8.2 Interface: ReceiveMessage.14
8.2.1 Operation: getReceivedMessages.14
8.2.1.1 Input message: getReceivedMessagesRequest.15
8.2.1.2 Output message: getReceivedMessagesResponse.15
8.2.1.3 Referenced faults.15
8.2.2 Operation: getMessageURIs.15
8.2.2.1 Input message: getMessageURIsRequest.15
8.2.2.2 Output message: getMessageURIsResponse.15
8.2.2.3 Referenced faults.15
8.2.3 Operation: getMessage.16
8.2.3.1 Input message: getMessageRequest .16
8.2.3.2 Output message: getMessageResponse.16
8.2.3.3 Referenced faults.16
8.3 Interface: MessageNotification.16
8.3.1 Operation: notifyMessageReception.16
8.3.1.1 Input message: notifyMessageReceptionRequest .16
8.3.1.2 Output message: notifyMessageReceptionResponse.17
8.3.1.3 Referenced faults.17
8.3.2 Operation: notifyMessageDeliveryReceipt.17
8.3.2.1 Input message: notifyMessageDeliveryReceiptRequest .17
8.3.2.2 Output message: notifyMessageDeliveryReceiptResponse .17
8.3.2.3 Referenced faults.17
8.4 Interface: MessageNotificationManager .17
8.4.1 Operation: startMessageNotification.18
ETSI
4 ETSI ES 202 391-5 V1.3.1 (2008-05)
8.4.1.1 Input message: startMessageNotificationRequest.18
8.4.1.2 Output message: startMessageNotificationResponse.18
8.4.1.3 Referenced Faults.18
8.4.2 Operation: stopMessageNotification.18
8.4.2.1 Input message: stopMessageNotificationRequest .19
8.4.2.2 Output message: stopMessageNotificationResponse.19
8.4.2.3 Referenced Faults.19
9 Fault definitions.19
9.1 ServiceException.19
9.1.1 Void.19
9.1.2 SVC0283: Delivery Receipt Notification not supported.19
10 Service policies .19
Annex A (normative): WSDL for Multimedia Messaging.20
Annex B (informative): Bibliography.21
History .22

ETSI
5 ETSI ES 202 391-5 V1.3.1 (2008-05)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 5 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-05 V6.8.0 (Release 6).
ETSI
6 ETSI ES 202 391-5 V1.3.1 (2008-05)
1 Scope
The present document is part 5 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Multimedia Messaging Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 ETSI ES 202 391-5 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
[3] W3C Note (11 December 2000): "SOAP Messages with Attachments".
NOTE: Available at: http://www.w3.org/TR/SOAP-attachments.
[4] IETF RFC 2822: "Internet Message Format".
NOTE: Available at: http://www.ietf.org/rfc/rfc2822.txt
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] and the following apply:
Whitespace: See definition for CFWS as defined in RFC 2822 [4].
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] and the following apply:
EMS Enhanced Messaging Service
IM Instant Messaging
MMS Multimedia Messaging Service
MMS-C Multimedia Messaging Service – Centre
OMA Open Mobile Alliance
SMS Short Message Service
WAP Wireless Application Protocol
4 Detailed service description
Currently, in order to programmatically receive and send Multimedia Messages, it is necessary to write applications
using specific protocols to access MMS functions provided by network elements (e.g. MMS-C). This approach requires
application developers to have a high degree of network expertise.
This contribution defines a Multimedia Messaging Web Service that can map to SMS, EMS, MMS, IM, E-mail, etc.
The choice is between defining one set of interfaces per messaging network or a single set common to all networks;
e.g. we could define sendMMS, sendEMS, sendSMS, etc., or just use sendMessage. Although the more specific the API
the easier it is to use, there are advantages to a single set of network-neutral APIs. These advantages include:
• improved service portability;
• lower complexity, by providing support for generic user terminal capabilities only.
For this version of the Parlay X 2 specification, we provide sets of interfaces for two messaging Web Services:
Short Messaging (part 4) and Multimedia Messaging (the present document), which provides generic messaging
features (including SMS).
Multimedia Messaging provides operations (see clause 8.1, SendMessage API) for sending a Multimedia message to
the network and a polling mechanism for monitoring the delivery status of a sent Multimedia message. It also provides
an asynchronous notification mechanism for delivery status (see clause 8.3, MessageNotification API).
Multimedia Messaging also allows an application to receive Multimedia messages. Both a polling (see clause 8.2,
ReceiveMessage API) and an asynchronous notification mechanism (see clause 8.3, MessageNotification API and
clause 8.4, MessageNotificationManager API) are available.
ETSI
8 ETSI ES 202 391-5 V1.3.1 (2008-05)
Figure 1 shows an example scenario using sendMessage and getMessageDeliveryStatus to send data to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to retrieve a
stock quote (1) and (2) and sends the current quote - sendMessage - using the Parlay X Interface (3) of the Multimedia
Messaging Web Service. After invocation, the Multimedia Message Web Service sends the message to an MMS-C
using the MM7 interface (4) for onward transmission (5) to the subscriber over the Mobile network.
Later, when the next quote is ready, the application checks to see - getMessageDeliveryStatus - if the previous quote
has been successfully delivered to the subscriber. If not, it may for instance perform an action (not shown) to provide a
credit for the previous message transmission. This way, the subscriber is only charged for a stock quote if it is delivered
on time.
Multimedia
Stock Quote
Message Web
Stock Quote MMSC -X
Web Service
Service 4
Web Service component
Parlay X I/F
MMS-C
MMSC
MM7 VASP
Interface
…… .
content1 =get StockQuote ()
….
Retrieve
user Profile
Mobile network
….
content
messageId= sendMessage( )
….
status= getMessageDeliveryStatus (messageId)
if status=Message_Waiting
….
fi
User
…
profile
content2 =get StockQuote ()
messageId= sendMessage ( content2 )

Figure 1: Multimedia Messaging Scenario
Alternatively this service could have been built using WAP Push features in the network.
Figure 2 shows an example scenario using sendMessage and getMessageDeliveryStatus to send a link to subscribers
and to determine if the data has been received by the subscriber. The application invokes a Web Service to generate a
stock quote graph (1) and (2) and sends the current quote as a WAP Push link - sendMessage - using the Parlay X
Interface (3) of the Multimedia Messaging Web Service. After invocation, the Multimedia Message Web Service sends
the message to an SMS-C (4) for onward transmission (5) to the subscriber over the Mobile network. The subscriber
can then open the link and access his content.
ETSI
9 ETSI ES 202 391-5 V1.3.1 (2008-05)

Figure 2: WAP Push scenario
5 Namespaces
The SendMessage interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/multimedia_messaging/send/v2_5
The ReceiveMessage
...