1、 ETSI ES 202 391-5 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 5: Multimedia Messaging(Parlay X 2)floppy3 ETSI ETSI ES 202 391-5 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-05-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis
2、 Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present do
3、cument 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 th
4、e 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/s
5、tatus.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 ex
6、tend to reproduction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of E
7、TSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 391-5 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations
8、 .7 4 Detailed service description .7 5 Namespaces9 6 Sequence diagrams.9 6.1 Send picture9 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
9、7.5 MessageURI structure 12 8 Web Service interface definition12 8.1 Interface: SendMessage12 8.1.1 Operation: sendMessage .12 8.1.1.1 Input message: sendMessageRequest13 8.1.1.2 Output message: sendMessageResponse.13 8.1.1.3 Referenced faults.13 8.1.2 Operation: getMessageDeliveryStatus14 8.1.2.1 I
10、nput 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: getReceivedMessagesRequest15 8.2.1.2 Output message: getReceived
11、MessagesResponse.15 8.2.1.3 Referenced faults.15 8.2.2 Operation: getMessageURIs .15 8.2.2.1 Input message: getMessageURIsRequest15 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 Outpu
12、t 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 Operat
13、ion: 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 ETSI ES 202
14、391-5 V1.3.1 (2008-05) 4 8.4.1.1 Input message: startMessageNotificationRequest.18 8.4.1.2 Output message: startMessageNotificationResponse18 8.4.1.3 Referenced Faults18 8.4.2 Operation: stopMessageNotification 18 8.4.2.1 Input message: stopMessageNotificationRequest .19 8.4.2.2 Output message: stop
15、MessageNotificationResponse 19 8.4.2.3 Referenced Faults19 9 Fault definitions19 9.1 ServiceException19 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 Messaging20 Annex B (informative): Bibliography.21 Histo
16、ry 22 ETSI ETSI ES 202 391-5 V1.3.1 (2008-05) 5 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
17、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 t
18、o 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.
19、 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
20、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 C
21、all“; 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 do
22、cument is equivalent to 3GPP TS 29.199-05 V6.8.0 (Release 6). ETSI ETSI ES 202 391-5 V1.3.1 (2008-05) 6 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 de
23、velopers 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
24、 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 r
25、eference 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 a
26、re 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
27、 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 lowe
28、r 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, on
29、ly 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 ETSI ES 202 391
30、-5 V1.3.1 (2008-05) 7 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: Ava
31、ilable 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 p
32、urposes 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 Applicati
33、on 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
34、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, sendE
35、MS, 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
36、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 cla
37、use 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 Messagi
38、ng 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 ETSI ES 202 391-5 V1.3.1 (2008-05)
39、 8 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 - u
40、sing 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 appl
41、ication 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
42、if it is delivered on time. MMSC -XcomponentMultimediaMessage WebServiceParlay X I/FMMSCMMS-CMM7 VASPInterfaceMobile networkStock QuoteWeb ServiceStock QuoteWeb Service content1 =get StockQuote ()Retrieveuser Profile.messageId= sendMessage( content1).status= getMessageDeliveryStatus (messageId)if st
43、atus=Message_Waiting.ficontent2 =get StockQuote ()messageId= sendMessage ( content2 )Userprofile123456Figure 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 getMessageDe
44、liveryStatus 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 Multim
45、edia 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 ETSI ES 202 391-5 V1.3.1 (2008-05) 9 Figure 2:
46、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
47、namespace: http:/www.csapi.org/wsdl/parlayx/multimedia_messaging/notification/v2_4 The MessageNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/multimedia_messaging/notification_manager/v2_6 The data types are defined in the namespace: http:/www.csapi.org/schema/parl
48、ayx/multimedia_messaging/v2_4 The “xsd“ namespace is used in the present document to refer to the XML Schema data types defined in XML Schema 1. The use of the name “xsd“ is not semantically significant. 6 Sequence diagrams 6.1 Send picture With the advent of picture capable phones, the exchange of
49、photos to mobile phones is becoming more common place. This sequence diagram shows an application where a person can send a picture from an online photo album to a mobile phone. ETSI ETSI ES 202 391-5 V1.3.1 (2008-05) 10: End User : Online Photo Album: Send MMS Web ServiceUser logs onUser selects photo to sendUser fills in send informationSend multimedia messageMessage identifierGet message statusStatusAcknowledgement pageShort waitFigure 3 6.2 Send WAP Push message For phones capable of receiving WAP Push messages, link
