1、 ETSI ES 202 504-4 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 4: Short Messaging(Parlay X 3)floppy3 ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-4-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex
2、 - 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 document
3、 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
4、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.
5、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 t
6、o 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 ETSI re
7、gistered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 7 2 References 7 2.1 Normative references .7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8 4
8、Detailed service description .8 5 Namespaces10 6 Sequence diagrams.10 6.1 Send SMS and report status10 7 XML Schema data type definition .11 7.1 DeliveryStatus enumeration .11 7.2 SmsFormat enumeration.11 7.3 DeliveryInformation structure 11 7.4 SmsMessage structure 11 7.5 ScheduledDeliveryStatus en
9、umeration.12 7.6 ScheduledDeliveryInformation structure .12 8 Web Service interface definition12 8.1 Interface: SendSms.12 8.1.1 Operation: sendSms 13 8.1.1.1 Input message: sendSmsRequest.13 8.1.1.2 Output message: sendSmsResponse13 8.1.1.3 Referenced faults.13 8.1.2 Operation: sendSmsLogo14 8.1.2.
10、1 Input message: sendSmsLogoRequest 14 8.1.2.2 Output message: sendSmsLogoResponse .14 8.1.2.3 Referenced faults.14 8.1.3 Operation: sendSmsRingtone14 8.1.3.1 Input message: sendSmsRingtoneRequest 15 8.1.3.2 Output message: sendSmsRingtoneResponse .15 8.1.3.3 Referenced faults.15 8.1.4 Operation: ge
11、tSmsDeliveryStatus.16 8.1.4.1 Input message: getSmsDeliveryStatusRequest16 8.1.4.2 Output message: getSmsDeliveryStatusResponse 16 8.1.4.3 Referenced faults.16 8.1.5 Operation: scheduleSms .16 8.1.5.1 Input message: scheduleSmsRequest 17 8.1.5.2 Output message: scheduleSmsResponse .17 8.1.5.3 Refere
12、nced faults.17 8.1.6 Operation: scheduleSmsLogo .17 8.1.6.1 Input message: scheduleSmsLogoRequest18 8.1.6.2 Output message: scheduleSmsLogoResponse.18 8.1.6.3 Referenced faults.18 8.1.7 Operation: scheduleSmsRingtone.18 8.1.7.1 Input message: scheduleSmsRingtoneRequest19 8.1.7.2 Output message: sche
13、duleSmsRingtoneResponse 19 8.1.7.3 Referenced faults.19 8.1.8 Operation: cancelScheduledSms.19 8.1.8.1 Input message: cancelScheduledSmsRequest .19 ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 4 8.1.8.2 Output message: cancelScheduledSmsResponse 20 8.1.8.3 Referenced faults.20 8.1.9 Operation: getSchedul
14、edSmsStatus 20 8.1.9.1 Input message: getScheduledSmsStatusRequest.20 8.1.9.2 Output message: getScheduledSmsStatusResponse20 8.1.9.3 Referenced faults.20 8.2 Interface: SmsNotification20 8.2.1 Operation: notifySmsReception20 8.2.1.1 Input message: notifySmsReceptionRequest 21 8.2.1.2 Output message
15、: notifySmsReceptionResponse .21 8.2.1.3 Referenced faults.21 8.2.2 Operation: notifySmsDeliveryReceipt21 8.2.2.1 Input message: notifySmsDeliveryReceiptRequest 22 8.2.2.2 Output message: notifySmsDeliveryReceiptResponse .22 8.2.2.3 Referenced faults.22 8.3 Interface: ReceiveSms22 8.3.1 Operation: g
16、etReceivedSms22 8.3.1.1 Input message: getReceivedSmsRequest 22 8.3.1.2 Output message: getReceivedSmsResponse .22 8.3.1.3 Referenced faults.22 8.4 Interface: SmsNotificationManager .23 8.4.1 Operation: startSmsNotification .23 8.4.1.1 Input message: startSmsNotificationRequest23 8.4.1.2 Output mess
17、age: startSmsNotificationResponse.23 8.4.1.3 Referenced faults.23 8.4.2 Operation: stopSmsNotification24 8.4.2.1 Input message: stopSmsNotificationRequest 24 8.4.2.2 Output message: stopSmsNotificationResponse .24 8.4.2.3 Referenced faults.24 8.4.3 Operation: startDeliveryReceiptNotification 24 8.4.
18、3.1 Input message: startDeliveryReceiptNotificationRequest.24 8.4.3.2 Output message: startDeliveryReceiptNotificationResponse24 8.4.3.3 Referenced faults.24 8.4.4 Operation: stopDeliveryReceiptNotification 25 8.4.4.1 Input message: stopDeliveryReceiptNotificationRequest .25 8.4.4.2 Output message:
19、stopDeliveryReceiptNotificationResponse25 8.4.4.3 Referenced faults.25 9 Fault definitions25 9.1 ServiceException25 9.1.1 SVC0280: Message too long 25 9.1.2 SVC0281: Unrecognized data format.25 9.1.3 Void 26 9.1.4 SVC0283: Delivery Receipt Notification not supported.26 10 Service policies 26 Annex A
20、 (normative): WSDL for Short Messaging27 Annex B (informative): Bibliography.28 History 29 ETSI ETSI ES 202 504-4 V1.1.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 essent
21、ial 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
22、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 ETS
23、I 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 4 of a
24、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: “Termi
25、nal 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 18: “
26、Device Capabilities and Configuration“; Part 19: “Multimedia Streaming Control“; Part 20: “Multimedia Multicast Session Management“. ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 6 The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present
27、 document forms part of the Parlay X 3.0 set of specifications. The present document is equivalent to 3GPP TS 29.199-04 V7.2.0 (Release 7). ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 7 1 Scope The present document is part 4 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (O
28、SA). 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 Short Messaging Web Service. The following are defined here: Name spaces. Sequence
29、 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. Fo
30、r 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 refer
31、ring 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. Pref
32、erably, 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
33、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 indispensa
34、ble 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:
35、 http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 8 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 ETSI TS 123 040: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommuni
36、cations System (UMTS); Technical realization of Short Message Service (SMS) (3GPP TS 23.040)“. 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 de
37、finitions given in ES 202 504-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 504-1 2 and the following apply: SMS Short Message Service SMS-C Short Message Servic
38、e-Centre 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 degree of network expertise. Alternativ
39、ely 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. Developers must have advanced telec
40、ommunication skills to use OSA interfaces. In this clause is described a Parlay X 3 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, using the SMS Web Service, applica
41、tion developers can invoke SMS functions without specific Telco knowledge. ShortMessaging provides operations (see clause 8.1, SendSms API) for sending an SMS message to the network and a polling mechanism for monitoring the delivery status of a sent SMS message. It also provide an asynchronous noti
42、fication mechanism for delivery status (see clause 8.2.2, SmsNotification API: notifySmsDeliveryReceipt operation). In addition, a mechanism is provided to start and stop the notification of delivery receipts (see clause 8.4, SmsNotificationManager API). ShortMessaging also allows an application to
43、receive SMS messages. Both a polling (see clause 8.3, ReceiveSms API) and an asynchronous notification mechanism (see clause 8.2.1, SmsNotification API: notifySmsReception operation and clause 8.4, SmsNotificationManager API) are available. Figure 1 shows a scenario using the SMS Web Service to send
44、 an SMS message from an application. The application invokes a Web Service to retrieve a weather forecast for a subscriber (1) and (2) and a Parlay X 3 Interface (3) to use the SMS Web Service operations (i.e. to send an SMS). After invocation, the SMS Web Service invokes a Parlay API method (4) usi
45、ng the Parlay/OSA SCS (Generic User Interaction) interface. This SCS handles the invocation and sends an UCP operation (5) to an SMS-C. Subsequently the weather forecast is delivered (6) to the subscriber. In an alternative scenario, the Parlay API interaction involving steps (4) and (5) could be re
46、placed with a direct interaction between the SMS Web Service and the Mobile network. ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 9 SMS-XcomponentParlay X I/FParlay GatewaySMS-CSMS-CSCS-SMSSCS-SMSParlay APIMobile networkYou havea new SMSWeather infoInfo meteoWeb ServiceWeb ServicegetMeteoInfo()Retrieveus
47、er Profile.SendSms (“Weather info”,)Userprofile123456Weather Info SMS WebServiceFigure 1: Send SMS Scenario Figure 2 shows a scenario using the SMS Web Service to deliver a received SMS message to an application. The application receives a Parlay X 3 Web Service invocation for an SMS sent by a subsc
48、riber (1) and (2). The SMS message contains the e-mail address of the person the user wishes to call. The application invokes a Parlay X Interface (3) to the Third Party Call Web Service in order to initiate the call (4). SMS-XcomponentSMS WebServiceParlay X I/FMobile networkCnotifySmsReception()Ret
49、rieveuser number.makeACall(“”,)Userprofile221SOAP3PC-XcomponentThird Party CallWeb ServiceParlay X I/FSOAP2343Figure 2: Receive SMS Scenario ETSI ETSI ES 202 504-4 V1.1.1 (2008-05) 105 Namespaces The SendSms interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/sms/send/v3_1 The ReceiveSms interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/sms/receive/v3_1 The SmsNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/sms/notification/v3_1 The SmsNotificationManag
