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

《ETSI TS 129 199-15-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services _1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 199-15-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services _1.pdf（33页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 129 199-15 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 15: Message broadcast (3GPP TS 29.199-15 version 9.0.0 Release 9)floppy3ETSI ET

2、SI TS 129 199-15 V9.0.0 (2010-01)13GPP TS 29.199-15 version 9.0.0 Release 9Reference RTS/TSGC-0029199-15v900 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-15 V9.0.0 (2010-01)23GPP TS 29.199-15 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially e

9、ssential 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 no

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

11、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. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3G

12、PP). 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 fo

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

14、33.2 Abbreviations . 7g34 Detailed service description . 8g35 Namespaces 9g36 Sequence Diagrams 10g36.1 Send broadcast message, get the status and cancel it . 10g36.2 Broadcast Status Notification . 11g37 XML Schema data type definition . 12g37.1 BroadcastStatus Enumeration . 12g37.2 Void 12g37.3 Br

15、oadcastStatusInformation Structure 12g37.4 BroadcastStatusData Structure . 12g37.5 LocationPoint Structure 13g37.6 Circle Structure 13g37.7 Polygon Structure . 13g37.8 AreaType Enumeration 13g37.9 BroadcastArea Union . 13g37.10 MessagePriority Enumeration 14g38 Web Service interface definition 15g38

16、.1 Interface: SendBroadcastMessage 15g38.1.1 Operation: sendBroadcastMessage . 15g38.1.1.1 Input message: sendBroadcastMessageRequest 16g38.1.1.2 Output message : sendBroadcastMessageResponse 16g38.1.1.3 Referenced faults . 16g38.1.2 Operation: getBroadcastStatus 17g38.1.2.1 Input message: getBroadc

17、astStatusRequest 19g38.1.2.2 Output message : getBroadcastStatusResponse 19g38.1.2.3 Referenced faults . 19g38.1.3 Operation: cancelBroadcastMessage 21g38.1.3.1 Input message: cancelBroadcastMessageRequest . 21g38.1.3.2 Output message : cancelBroadcastMessageResponse . 21g38.1.3.3 Referenced faults

18、. 21g38.2 Interface: MessageBroadcastNotification . 22g38.2.1 Operation: notifyBroadcastDeliveryReceipt . 22g38.2.1.1 Input message: notifyBroadcastDeliveryReceiptRequest . 23g38.2.1.2 Output message : notifyBroadcastDeliveryReceiptResponse . 23g38.2.1.3 Referenced faults . 23g38.3 Interface: Messag

19、eBroadcastNotificationManager 23g38.3.1 Operation: startDeliveryReceiptNotification 24g38.3.1.1 Input message: startDeliveryReceiptNotificationRequest . 24g38.3.1.2 Output message: startDeliveryReceiptNotificationResponse 24g38.3.1.3 Referenced faults . 24g38.3.2 Operation: stopDeliveryReceiptNotifi

20、cation 25g3ETSI ETSI TS 129 199-15 V9.0.0 (2010-01)43GPP TS 29.199-15 version 9.0.0 Release 98.3.2.1 Input message: stopDeliveryReceiptNotificationRequest . 25g38.3.2.2 Output message: stopDeliveryReceiptNotificationResponse 25g38.3.2.3 Referenced faults . 25g39 Fault definitions 26g39.1 ServiceExce

21、ption 26g39.1.1 SVC0280: Message too long 26g39.1.2 SVC0283: Delivery Status Notification not supported . 26g39.1.3 SVC0300: Broadcast Area not supported . 26g39.1.4 SVC0301: Too high load situation . 26g39.2 PolicyException . 26g39.2.1 POL0330: Multiple areas not allowed 26g39.2.2 POL0331: Maximum

22、Number of Areas exceeded 26g39.2.3 POL0332: Too Many Broadcasts requested . 26g39.2.4 POL0333: Min/Max Interval Violation 27g310 Service policies 27g3Annex A (normative): WSDL for Message Broadcast 28g3Annex B (informative): Description of Parlay X Web Services Part 15: Message Broadcast for 3GPP2 c

23、dma2000 networks 29g3B.1 General Exceptions. 29g3B.2 Specific Exceptions 29g3B.2.1 Clause 1: Scope 29g3B.2.2 Clause 2: References 29g3B.2.3 Clause 3: Definitions and abbreviations . 29g3B.2.4 Clause 4: Detailed service description 29g3B.2.5 Clause 5: Namespaces 29g3B.2.6 Clause 6: Sequence diagrams

24、. 30g3B.2.7 Clause 7: XML Schema data type definition 30g3B.2.8 Clause 8: Web Service interface definition 30g3B.2.9 Clause 9: Fault definitions 30g3B.2.10 Clause 10: Service policies . 30g3B.2.11 Annex A (normative):WSDL for Message Broadcast 30g3Annex C (informative): Change history . 31g3History

25、32g3ETSI ETSI TS 129 199-15 V9.0.0 (2010-01)53GPP TS 29.199-15 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). 3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Par

26、lay Group is pleased to see 3GPP acknowledge and publish the present document, and the Parlay Group looks forward to working with 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 f

27、ollowing formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with 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

28、 to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all 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

29、document. Introduction The present document is part 15 of a multi-part deliverable covering the 3rdGeneration Partnership Project; 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 ca

30、ll“ 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 call“ Part 12: “Multimedia conference“ Part 13: “Address list managem

31、ent“ Part 14: “Presence“ Part 15: “Message Broadcast“ Part 16: “Geocoding“ Part 17: “Application driven Quality of Service (QoS)“ Part 18: “Device Capabilities and Configuration“ Part 19: “Multimedia streaming control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“

32、Part 22: “Policy“ ETSI ETSI TS 129 199-15 V9.0.0 (2010-01)63GPP TS 29.199-15 version 9.0.0 Release 91 Scope The present document is Part 15 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application develop

33、ers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional 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 Message Broad

34、cast Web Service aspects of the interface. All aspects of the Message Broadcast Web Service are defined here, these being: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service policies. WSDL description of the interfa

35、ces. 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 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

36、 in this text, constitute provisions of the present document. References are either specific (identified by date of publication, 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 applie

37、s. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the 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 f

38、or 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; 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 3G

39、PP TS 29.199-1: “Open Service Access (OSA); Parlay X web services; Part 1: Common“. 7 3GPP TS 23.041: “Technical realization of Cell Broadcast Service (CBS)“. 8 3GPP TS 23.032: “Universal Geographical Area Description (GAD)“. ETSI ETSI TS 129 199-15 V9.0.0 (2010-01)73GPP TS 29.199-15 version 9.0.0 R

40、elease 99 3GPP TS 29.199-9: “Open Service Access (OSA); Parlay X web services; Part 9: Terminal location“. 10 3GPP TS 29.199-4: “Open Service Access (OSA); Parlay X web services; Part 4: Short messaging“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the t

41、erms and definitions given in 3GPP TR 21.905 1 and 3GPP TS 29.199-1 6 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1, 3GPP TS 29.199-1 6, 3GPP TS 29.199-4 10 and the following apply: CBC Cell Broadcast Centre CBS Cell Broadcast Service

42、ETSI ETSI TS 129 199-15 V9.0.0 (2010-01)83GPP TS 29.199-15 version 9.0.0 Release 94 Detailed service description Message broadcast is a functionality that allows an application to send messages to all the fixed or mobile terminals in a specified geographical area. Message broadcast provides operatio

43、ns for sending a broadcast message to the network and a polling mechanism for monitoring the delivery status of a 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

44、delivery receipts. There are various use cases of using Message Broadcast Web Service including the commercial application. This Web Service could be also used for non-commercial purpose as follows: To provide area-based public information like weather, traffic and other commonly-interested informat

45、ion. To provide emergency information like severe weather warning(e.g. typhoon, tsunami), environments hazards(e.g. chemical spills) and terrorism information. Message BroadcastWeb ServiceShop managerSOAPShopping mallmobile networkfixednetworkMessaging Center(e.g., CBC)SMSSMSSMSSMSbrodcastCoupon( )a

46、rea = setArea();msg = “2 hours, 20% discount”;senderName = “GAP”;.sendBroadcastMessage(area, msg, senderName); Parlay X I/Fbuy something (offline)123Figure 4.1: Send Broadcast Message Scenario Figure 4.1 shows an advertising scenario using Message Broadcast Web Service to broadcast discount message

47、around and within the shopping mall area. A shop manager who wants to increase sales in a holiday can make use of a message broadcast application. By using the application, he can set the targeted area and write a message and the senders name to be contacted (1). Then, the application invokes a Parl

48、ay X interface to use Message Broadcast Web Service operation(2). After invocation, the Message Broadcast Web Service sends a message delivery operation to messaging centre (e.g. CBC) (3). Subsequently, the message on discount information is delivered to all the terminals within the targeted area. E

49、TSI ETSI TS 129 199-15 V9.0.0 (2010-01)93GPP TS 29.199-15 version 9.0.0 Release 95 Namespaces The SendBroadcastMessage interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/send/v4_0 The MessageBroadcastNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/notification/ v4_0 The MessageBroadcastNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/message_broadcast/notification_manager/ v4_0 The data types are defin