ETSI TS 129 199-5-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services P_1.pdf

1、 ETSI TS 129 199-5 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Parlay X web services;Part 5: Multimedia messaging (3GPP TS 29.199-05 version 9.0.0 Release 9)floppy3ETSI E

2、TSI TS 129 199-5 V9.0.0 (2010-01)13GPP TS 29.199-05 version 9.0.0 Release 9Reference RTS/TSGC-0029199-05v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis 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 bu

3、t 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 document may be made available in more than one electronic version or in print. In any case of existing or perceived

4、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 awa

5、re 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: ht

6、tp:/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 2010. All rights reserved. DECTT

7、M, 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 ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registe

8、red for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)23GPP TS 29.199-05 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially es

9、sential 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 not

10、ified 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 c

11、an be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GP

12、P). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be fou

13、nd under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)33GPP TS 29.199-05 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33

14、.2 Abbreviations . 7g34 Detailed service description . 7g35 Namespaces 9g36 Sequence diagrams . 10g36.1 Send picture 10g36.2 Send WAP push message . 11g37 XML schema data type definition 12g37.1 DeliveryStatus enumeration . 12g37.2 MessagePriority enumeration . 12g37.3 DeliveryInformation structure

15、12g37.4 MessageReference structure . 13g37.5 MessageURI structure 13g37.6 ScheduledDeliveryStatus enumeration . 13g37.7 ScheduledDeliveryInformation structure . 13g37.8 MessageFormat enumeration 14g38 Web Service interface definition 15g38.1 Interface: SendMessage 15g38.1.1 Operation: SendMessage 15

16、g38.1.1.1 Input message: SendMessageRequest . 16g38.1.1.2 Output message: SendMessageResponse 16g38.1.1.3 Referenced faults . 16g38.1.2 Operation: GetMessageDeliveryStatus . 18g38.1.2.1 Input message: GetMessageDeliveryStatusRequest 18g38.1.2.2 Output message: GetMessageDeliveryStatusResponse 18g38.

17、1.2.3 Referenced faults. 18g38.1.3 Operation: ScheduleMessage 19g38.1.3.1 Input message: ScheduleMessageRequest 19g38.1.3.2 Output message: ScheduleMessageResponse . 19g38.1.3.3 Referenced faults . 19g38.1.4 Operation: CancelScheduledMessage . 20g38.1.4.1 Input message: CancelScheduledMessageRequest

18、 . 20g38.1.4.2 Output message : CancelScheduledMessageResponse . 20g38.1.4.3 Referenced faults . 20g38.1.5 Operation: GetScheduledMessageStatus 21g38.1.5.1 Input message: GetScheduledMessageStatusRequest . 21g38.1.5.2 Output message: GetScheduledMessageStatusResponse 21g38.1.5.3 Referenced faults .

19、21g38.2 Interface: ReceiveMessage . 22g38.2.1 Operation: GetReceivedMessages 22g38.2.1.1 Input message: GetReceivedMessagesRequest . 22g38.2.1.2 Output message: GetReceivedMessagesResponse 22g38.2.1.3 Referenced faults . 22g38.2.2 Operation: GetMessageURIs 23g38.2.2.1 Input message: GetMessageURIsRe

20、quest . 23g38.2.2.2 Output message: GetMessageURIsResponse 23g3ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)43GPP TS 29.199-05 version 9.0.0 Release 98.2.2.3 Referenced faults . 23g38.2.3 Operation: GetMessage. 24g38.2.3.1 Input message: GetMessageRequest . 24g38.2.3.2 Output message: GetMessageResponse 2

21、4g38.2.3.3 Referenced faults . 24g38.3 Interface: MessageNotification 25g38.3.1 Operation: NotifyMessageReception 25g38.3.1.1 Input message: NotifyMessageReceptionRequest 25g38.3.1.2 Output message: NotifyMessageReceptionResponse . 25g38.3.1.3 Referenced faults . 25g38.3.2 Operation: NotifyMessageDe

22、liveryReceipt 26g38.3.2.1 Input message: NotifyMessageDeliveryReceiptRequest. 26g38.3.2.2 Output message: NotifyMessageDeliveryReceiptResponse . 26g38.3.2.3 Referenced faults . 26g38.4 Interface: MessageNotificationManager 26g38.4.1 Operation: StartMessageNotification 27g38.4.1.1 Input message: Star

23、tMessageNotificationRequest 27g38.4.1.2 Output message: StartMessageNotificationResponse . 27g38.4.1.3 Referenced Faults 27g38.4.2 Operation: StopMessageNotification 28g38.4.2.1 Input message: StopMessageNotificationRequest 28g38.4.2.2 Output message: StopMessageNotificationResponse . 28g38.4.2.3 Re

24、ferenced Faults 28g38.4.3 Operation: StartDeliveryReceiptNotification . 29g38.4.3.1 Input message: StartDeliveryReceiptNotificationRequest 29g38.4.3.2 Output message: StartDeliveryReceiptNotificationResponse . 29g38.4.3.3 Referenced Faults 29g38.4.4 Operation: StopDeliveryReceiptNotification 30g38.4

25、.4.1 Input message: StopDeliveryReceiptNotificationRequest 30g38.4.4.2 Output message: StopDeliveryReceiptNotificationResponse . 30g38.4.4.3 Referenced Faults 30g39 Fault definitions 31g39.1 ServiceException 31g39.1.1 Void 31g39.1.2 SVC0283: Delivery Receipt Notification not supported. 31g310 Servic

26、e policies 31g3Annex A (normative): WSDL for Multimedia Messaging 32g3Annex B (informative): Description of Parlay X Web Services Part 5: Multimedia messaging for 3GPP2 cdma2000 networks 33g3B.1 General Exceptions. 33g3B.2 Specific Exceptions 33g3B.2.1 Clause 1: Scope 33g3B.2.2 Clause 2: References

27、33g3B.2.3 Clause 3: Definitions and abbreviations . 33g3B.2.4 Clause 4: Detailed service description 33g3B.2.5 Clause 5: Namespaces 33g3B.2.6 Clause 6: Sequence diagrams . 34g3B.2.7 Clause 7: XML Schema data type definition 34g3B.2.8 Clause 8: Web Service interface definition 34g3B.2.9 Clause 9: Fau

28、lt definitions 34g3B.2.10 Clause 10: Service policies . 34g3B.2.11 Annex A (normative):WSDL for Multimedia Messaging 34g3Annex C (informative): Change history . 35g3History 36g3ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)53GPP TS 29.199-05 version 9.0.0 Release 9Foreword This Technical Specification has

29、been produced by the 3rdGeneration Partnership Project (3GPP). 3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay Group is pleased to see 3GPP acknowledge and publish the present document, and the Parlay Group looks forward to working wit

30、h the 3GPP community to improve future versions of the present document. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with

31、 an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for a

32、ll changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 5 of a multi-part deliverable covering the 3rdGeneration Partnership Project

33、; Technical Specification Group Core Network and Terminals; 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 manag

34、ement“ 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“ Part 15: “Message Broadcast“ Part 16: “Geocoding“ Part 17: “Application driven Quality of Service (QoS)“

35、 Part 18: “Device Capabilities and Configuration“ Part 19: “Multimedia streaming control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“ Part 22: “Policy“ ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)63GPP TS 29.199-05 version 9.0.0 Release 91 Scope The present document i

36、s Part 5 of the Stage 3 Parlay X 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 concepts and the functional

37、 architecture for the OSA are contained in 3GPP TS 23.198 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Multimedia Messaging Web Service aspects of the interface. All aspects of the Multimedia Messaging Web Service are defined here, these being: Na

38、me spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service policies. WSDL Description of the interfaces. The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. Maintenance of

39、up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publicati

40、on, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to th

41、e latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.101: “Servi

42、ce aspects; Service principles“. 5 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS 29.199-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common“. 7 W3C Note (11 December 2001): “SOAP Mess

43、ages with Attachments“. NOTE: Available at http:/www.w3.org/TR/SOAP-attachments. 8 3GPP TS 23.140 “Multimedia Messaging Service (MMS); Functional description; Stage 2“. 9 RFC2822: “Internet Message Format“. NOTE: Available at http:/www.ietf.org/rfc/rfc2822.txt ETSI ETSI TS 129 199-5 V9.0.0 (2010-01)

44、73GPP TS 29.199-05 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 6 apply. Additionally the following definition is needed: Whitespace: see definition for CFWS as defined in RFC2822

45、9. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 and the following apply: EMS Enhanced Messaging Service IM Instant Messaging MMS Multimedia Messaging Service MMS-C Multimedia Messaging Service - Centre SMS Short Message Service 4 Detailed

46、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 ap This clause describes Parlay X Web Service for

47、 sending and receiving Multimedia messages. The overall scope of this Web Service is to provide application developers primitives to handle Multimedia messages in a simple way. In fact, using Multimedia Messaging Web Service, application developers can invoke Multimedia Messaging functions without s

48、pecific Telco knowledge. This version of Multimedia Messaging Web Services provides generic messaging features that can support different messaging service types such as SMS, MMS, IM, E-mail etc. Multimedia Messaging provides operations (see clause 8.1, SendMessage API) for sending a Multimedia mess

49、age 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). In addition, a mechanism is provided to start and stop the notification of delivery receipts (see clause 8.4, MessageNotificationManager API). Multimedia Messaging also allows an application to receive Multimedia messages. Both a polling (see clause 8.2, ReceiveMessage API) and an asynchronous notifica