ETSI TS 129 199-4-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-4 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 4: Short messaging (3GPP TS 29.199-04 version 9.0.0 Release 9)floppy3ETSI ETSI T

2、S 129 199-4 V9.0.0 (2010-01)13GPP TS 29.199-04 version 9.0.0 Release 9Reference RTS/TSGC-0029199-04v900 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 but non

3、 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 diffe

4、rence 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 th

5、at 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:/p

6、ortal.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. DECTTM, PL

7、UGTESTSTM, 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 registered f

8、or 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-4 V9.0.0 (2010-01)23GPP TS 29.199-04 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially essenti

9、al 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

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

11、 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 (3GPP). T

12、he 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 found un

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

14、breviations . 8g34 Detailed service description . 8g35 Namespaces 10g36 Sequence Diagrams 11g36.1 Send SMS and report status 11g37 XML Schema data type definition . 12g37.1 DeliveryStatus enumeration . 12g37.2 SmsFormat enumeration . 12g37.3 DeliveryInformation structure 12g37.4 SmsMessage structure

15、 12g37.5 ScheduledDeliveryStatus enumeration . 13g37.6 ScheduledDeliveryInformation structure . 13g38 Web Service interface definition 14g38.1 Interface: SendSms . 14g38.1.1 Operation: SendSms . 15g38.1.1.1 Input message: SendSmsRequest 15g38.1.1.2 Output message : SendSmsResponse 15g38.1.1.3 Refere

16、nced faults . 15g38.1.2 Operation: SendSmsLogo . 16g38.1.2.1 Input message: SendSmsLogoRequest 16g38.1.2.2 Output message: SendSmsLogoResponse . 16g38.1.2.3 Referenced faults . 16g38.1.3 Operation: SendSmsRingtone . 17g38.1.3.1 Input message: SendSmsRingtoneRequest . 17g38.1.3.2 Output message: Send

17、SmsRingtoneResponse 17g38.1.3.3 Referenced faults. 17g38.1.4 Operation: GetSmsDeliveryStatus 18g38.1.4.1 Input message: GetSmsDeliveryStatusRequest . 18g38.1.4.2 Output message : GetSmsDeliveryStatusResponse . 18g38.1.4.3 Referenced faults . 18g38.1.5 Operation: ScheduleSms . 19g38.1.5.1 Input messa

18、ge: ScheduleSmsRequest . 19g38.1.5.2 Output message : ScheduleSmsResponse . 19g38.1.5.3 Referenced faults. 19g38.1.6 Operation: ScheduleSmsLogo 20g38.1.6.1 Input message: ScheduleSmsLogoRequest . 20g38.1.6.2 Output message: ScheduleSmsLogoResponse 20g38.1.6.3 Referenced faults. 20g38.1.7 Operation:

19、ScheduleSmsRingtone 21g38.1.7.1 Input message: ScheduleSmsRingtoneRequest . 21g38.1.7.2 Output message: ScheduleSmsRingtoneResponse 21g38.1.7.3 Referenced faults . 21g3ETSI ETSI TS 129 199-4 V9.0.0 (2010-01)43GPP TS 29.199-04 version 9.0.0 Release 98.1.8 Operation: CancelScheduledSms 22g38.1.8.1 Inp

20、ut message: CancelScheduledSmsRequest 22g38.1.8.2 Output message : CancelScheduledSmsResponse 22g38.1.8.3 Referenced faults . 22g38.1.9 Operation: GetScheduledSmsStatus . 23g38.1.9.1 Input message: GetScheduledSmsStatusRequest 23g38.1.9.2 Output message : GetScheduledSmsStatusResponse 23g38.1.9.3 Re

21、ferenced faults . 23g38.2 Interface: SmsNotification 24g38.2.1 Operation: NotifySmsReception . 24g38.2.1.1 Input message: NotifySmsReceptionRequest . 24g38.2.1.2 Output message : NotifySmsReceptionResponse . 24g38.2.1.3 Referenced faults . 24g38.2.2 Operation: NotifySmsDeliveryReceipt . 25g38.2.2.1

22、Input message: NotifySmsDeliveryReceiptRequest 25g38.2.2.2 Output message: NotifySmsDeliveryReceiptResponse. 25g38.2.2.3 Referenced faults . 25g38.3 Interface: ReceiveSms 26g38.3.1 Operation: GetReceivedSms . 26g38.3.1.1 Input message: GetReceivedSmsRequest . 26g38.3.1.2 Output message : GetReceived

23、SmsResponse . 26g38.3.1.3 Referenced faults. 26g38.4 Interface: SmsNotificationManager . 27g38.4.1 Operation: StartSmsNotification. 27g38.4.1.1 Input message: StartSmsNotificationRequest . 27g38.4.1.2 Output message: StartSmsNotificationResponse 27g38.4.1.3 Referenced Faults 27g38.4.2 Operation: Sto

24、pSmsNotification . 28g38.4.2.1 Input message: StopSmsNotificationRequest . 28g38.4.2.2 Output message: StopSmsNotificationResponse 28g38.4.2.3 Referenced Faults 28g38.4.3 Operation: StartDeliveryReceiptNotification . 29g38.4.3.1 Input message: StartDeliveryReceiptNotificationRequest 29g38.4.3.2 Outp

25、ut message: StartDeliveryReceiptNotificationResponse . 29g38.4.3.3 Referenced Faults 29g38.4.4 Operation: StopDeliveryReceiptNotification 30g38.4.4.1 Input message: StopDeliveryReceiptNotificationRequest 30g38.4.4.2 Output message: StopDeliveryReceiptNotificationResponse . 30g38.4.4.3 Referenced Fau

26、lts 30g39 Fault definitions 31g39.1 ServiceException 31g39.1.1 SVC0280: Message too long 31g39.1.2 SVC0281: Unrecognized data format . 31g39.1.3 Void 31g39.1.4 SVC0283: Delivery Receipt Notification not supported. 31g310 Service policies 31g3Annex A (normative): WSDL for Short Messaging 33g3Annex B

27、(informative): Description of Parlay X Web Services Part 4: Short messaging for 3GPP2 cdma2000 networks 34g3B.1 General Exceptions. 34g3B.2 Specific Exceptions 34g3B.2.1 Clause 1: Scope 34g3B.2.2 Clause 2: References 34g3B.2.3 Clause 3: Definitions and abbreviations . 34g3B.2.4 Clause 4: Detailed se

28、rvice description 34g3B.2.5 Clause 5: Namespaces 34g3B.2.6 Clause 6: Sequence diagrams . 35g3ETSI ETSI TS 129 199-4 V9.0.0 (2010-01)53GPP TS 29.199-04 version 9.0.0 Release 9B.2.7 Clause 7: XML Schema data type definition 35g3B.2.8 Clause 8: Web Service interface definition 35g3B.2.9 Clause 9: Fault

29、 definitions 35g3B.2.10 Clause 10: Service policies . 35g3B.2.11 Annex A (normative):WSDL for Short Messaging 35g3Annex B (informative): Change history . 36g3History 37g3ETSI ETSI TS 129 199-4 V9.0.0 (2010-01)63GPP TS 29.199-04 version 9.0.0 Release 9Foreword This Technical Specification has been pr

30、oduced 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 with the 3

31、GPP 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 an ide

32、ntifying 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 all chan

33、ges 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 4 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Techn

34、ical 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 management“

35、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)“ Part 1

36、8: “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-4 V9.0.0 (2010-01)73GPP TS 29.199-04 version 9.0.0 Release 91 Scope The present document is Part

37、4 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 archit

38、ecture 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 Short Messaging Web Service aspects of the interface. All aspects of the Short Messaging Web Service are defined here, these being: Name spaces. Sequen

39、ce 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 up to 3GPP Rel-8

40、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 publication, edition numbe

41、r, 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 the latest version

42、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: “Service aspects; Servi

43、ce 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 3GPP TS 23.040: “Technical realization of Short Message

44、Service (SMS)“. 8 RFC2822: “Internet Message Format“. NOTE: Available at htpp:/www.ietf.org/rfc/rfc2822.txt ETSI ETSI TS 129 199-4 V9.0.0 (2010-01)83GPP TS 29.199-04 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definit

45、ions given in 3GPP TS 29.199-1 6 apply. Additionally the following definition is needed: Whitespace: see definition for CFWS as defined in RFC2822 8. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 and the following apply: SMS Short Message S

46、ervice SMS-C Short Message Service - Center 4 Detailed service description Currently, in order to programmatically receive and send SMS it is necessary to write applications using specific protocols to access SMS functions provided by network elements (e.g. SMS-C). This approach requires a high degr

47、ee of network expertise. Alternatively it is possible to use the Parlay/OSA approach, invoking standard interfaces (e.g. User Interaction or Messaging Service Interfaces) to gain access to SMS capabilities, but these interfaces are usually perceived to be quite complex by IT application developers.

48、Developers must have advanced telecommunication skills to use OSA interfaces. In this clause is described a Parlay X Web Service, for sending and receiving SMS messages. The overall scope of this Web Service is to provide to application developers primitives to handle SMS in a simple way. In fact, u

49、sing the SMS Web Service, application developers can invoke SMS functions without specific Telco knowledge. ShortMessaging provides operations (see clause 8.1, Send SMS API) for sending a SMS message to the network and a polling mechanism for monitoring the delivery status of a sent SMS message. It also provides an asynchronous notification mechanism for delivery status (see clause 8.2, SmsNotification API). In addition, a mechanism is provided to start and stop the notification of delivery receipts (see clause 8.4, SmsNotificat