1、 ETSI ES 202 504-15 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 15: Message Broadcast(Parlay X 3)floppy3 ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-15-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 504-15 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 Abbreviation
8、s .8 4 Detailed service description .8 5 Namespaces9 6 Sequence diagrams.10 6.1 Send broadcast message, get the status and cancel it .10 6.2 Broadcast Status Notification.11 7 XML Schema data type definition .12 7.1 BroadcastStatus Enumeration.12 7.2 RetrievalStatus Enumeration12 7.3 BroadcastStatus
9、Information Structure12 7.4 BroadcastStatusData Structure .13 7.5 LocationPoint Structure13 7.6 Circle Structure 13 7.7 Polygon Structure.13 7.8 AreaType Enumeration 13 7.9 BroadcastArea Union .14 7.10 MessagePriority Enumeration 14 8 Web Service interface definition14 8.1 Interface: SendBroadcastMe
10、ssage14 8.1.1 Operation: sendBroadcastMessage .14 8.1.1.1 Input message: sendBroadcastMessageRequest15 8.1.1.2 Output message: sendBroadcastMessageResponse.16 8.1.1.3 Referenced faults.16 8.1.2 Operation: getBroadcastStatus16 8.1.2.1 Input message: getBroadcastStatusRequest 18 8.1.2.2 Output message
11、: getBroadcastStatusResponse .18 8.1.2.3 Referenced faults.18 8.1.3 Operation: cancelBroadcastMessage 19 8.1.3.1 Input message: cancelBroadcastMessageRequest.19 8.1.3.2 Output message: cancelBroadcastMessageResponse19 8.1.3.3 Referenced faults.19 8.2 Interface: MessageBroadcastNotification.19 8.2.1
12、Operation: notifyBroadcastDeliveryReceipt.19 8.2.1.1 Input message: notifyBroadcastDeliveryReceiptRequest .20 8.2.1.2 Output message: notifyBroadcastDeliveryReceiptResponse 20 8.2.1.3 Referenced faults.20 8.3 Interface: MessageBroadcastNotificationManager 20 8.3.1 Operation: startDeliveryReceiptNoti
13、fication 21 8.3.1.1 Input message: startDeliveryReceiptNotificationRequest.21 8.3.1.2 Output message: startDeliveryReceiptNotificationResponse21 8.3.1.3 Referenced faults.21 8.3.2 Operation: stopDeliveryReceiptNotification 21 8.3.2.1 Input message: stopDeliveryReceiptNotificationRequest .21 8.3.2.2
14、Output message: stopDeliveryReceiptNotificationResponse21 ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 4 8.3.2.3 Referenced faults.22 9 Fault definitions22 9.1 ServiceException22 9.1.1 SVC0280: Message too long 22 9.1.2 SVC0283: Delivery Status Notification not supported.22 9.1.3 SVC0300: Broadcast Area
15、 not supported .22 9.1.4 SVC0301: Too high load situation .22 9.2 PolicyException .22 9.2.1 POL0330: Multiple areas not allowed 22 9.2.2 POL0331: Maximum Number of Areas exceeded23 9.2.3 POL0332: Too Many Broadcasts requested .23 9.2.4 POL0333: Min/Max Interval Violation 23 10 Service policies 23 An
16、nex A (normative): WSDL for Message Broadcast24 Annex B (informative): Bibliography.25 History 26 ETSI ETSI ES 202 504-15 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 thes
17、e 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
18、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
19、 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
20、 15 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 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“; Par
21、t 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)“;
22、 Part 18: “Device Capabilities and Configuration“; Part 19: “Multimedia Streaming Control“; Part 20: “Multimedia Multicast Session Management“. ETSI ETSI ES 202 504-15 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.
23、 The present document forms part of the Parlay X 3.0 set of specifications. The present document is equivalent to 3GPP TS 29.199-15 V7.2.0 (Release 7). ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 7 1 Scope The present document is part 15 of the Stage 3 Parlay X 3 Web Services specification for Open Ser
24、vice 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 Message Broadcast Web Service. The following are defined here: Name
25、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
26、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 purpo
27、ses 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 b
28、e 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 docume
29、nt 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 document
30、s 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“. NOT
31、E: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-15 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 041: “Digital cellular telecommunications system (Phase 2+); Universal Mo
32、bile Telecommunications System (UMTS); Technical realization of Cell Broadcast Service (CBS) (3GPP TS 23.041)“. 4 ETSI TS 123 032: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Universal Geographical Area Description (GAD) (3GPP TS 23.032)
33、“. 5 ETSI ES 202 504-9: “Open Service Access (OSA); Parlay X Web Services; Part 9: Terminal Location (Parlay X 3)“. 6 ETSI ES 202 504-4: “Open Service Access (OSA); Parlay X Web Services; Part 4: Short Messaging (Parlay X 3)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the p
34、resent document, the terms and definitions given in ES 202 504-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 202 504-1 2, ES 202 504-4 6 and the following apply. CBC Cell Broadcast Centre CBS Cell Broadcast Service 4 Detailed service description
35、 Message broadcast is functionality that allows an application to send messages to all the fixed or mobile terminals in a specified geographical area. Message broadcast provides operations for sending a broadcast message to the network and a polling mechanism for monitoring the delivery status of a
36、sent broadcast message. It also provides an asynchronous notification mechanism for broadcast delivery status. In addition, a mechanism is provided to start and stop the notification of delivery receipts. There are various use cases of using Message Broadcast Web Service including the commercial app
37、lication. This Web Service could be also used for non-commercial purposes as follows: To provide area-based public information such as weather, traffic and other information of common interest. To provide emergency information such as severe weather warnings (e.g. typhoon, tsunami), environmental ha
38、zards (e.g. chemical spills) and terrorism alerts. ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 9 Message BroadcastWeb Serviceg54g75g82g83g3g80g68g81g68g74g72g85SOAPShopping mallmobile networkfixednetworkMessaging Center(e.g., CBC)SMSSMSSMSSMSbrodcastCoupon( )area = setArea();msg = “2 hours, 20% discoun
39、t”;senderName = “GAP”;.sendBroadcastMessage(area, msg, senderName); Parlay X I/Fbuy something (offline)123Figure 1: Send Broadcast Message Scenario Figure 1 shows an advertising scenario using the Message Broadcast Web Service to broadcast messages describing shop discount offers inside, and in the
40、vicinity of, a shopping mall. A shop manager who wants to increase sales during a holiday period can make use of a message broadcast application. By using the application, the manager can set the targeted area, compose the sales message and identify the shop offering the discount (1). Then, the appl
41、ication uses the Parlay X interface to invoke the Message Broadcast Web Service operation (2). After invocation, the Message Broadcast Web Service sends a message delivery operation to the messaging centre, e.g. the CBC (3). Subsequently, the shop discount message is delivered to all the terminals w
42、ithin the targeted area. 5 Namespaces The SendBroadcastMessage interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/send/v3_1 The MessageBroadcastNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/notification/v3_1 The MessageBro
43、adcastNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/notification_manager/v3_0 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/message_broadcast/v3_1 The xsd namespace is used in the present document to refer to th
44、e XML Schema data types defined in XML Schema 1. The use of the name xsd is not semantically significant. ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 106 Sequence diagrams 6.1 Send broadcast message, get the status and cancel it Pattern: Request/Response, One way An application can send a broadcast mes
45、sage to a specific area and also poll for the delivery status from the Message Broadcast Web Service. If the application subsequently wishes to abort message broadcasting, it can send a cancellation request. :Application:Message Broadcastsend broadcast messagemessage identifierget the statusretrieve
46、 broadcast statusbroadcast status infocancel the previous requestFigure 2: Message Broadcast Operations ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 116.2 Broadcast Status Notification Pattern: Application Correlated Multiple Notification An application can request a message be broadcast to multiple are
47、as and, using a specified correlator parameter, can subsequently be notified of the broadcast delivery status for each area. :Application:Message Broadcastcreate correlatorsend broadcast messageto multiple areas:NotificationApplication:NotificationWeb ServiceSome times later, the completion of broad
48、casting triggers a status notification for each areastatus notificationstatus notificationstatus notificationFigure 3: Message Broadcast Status Notification ETSI ETSI ES 202 504-15 V1.1.1 (2008-05) 127 XML Schema data type definition 7.1 BroadcastStatus Enumeration List of possible broadcast deliver
49、y status values. Enumeration value Description MessageWaiting The message is still queued and not delivered to the network yet. Broadcasting has not commenced. Broadcasting Broadcasting is initiated and the network is still attempting to deliver messages: i.e. as many times as requested in the totalBroadcasts part of the sendBroadcastMessageRequest message. Broadcasted A final state that indicates broadcast requests were successfully delivered to network: i.e. as many times as requested. BroadcastImpossible Delivery of br
