ETSI TS 129 199-8-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-8 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 8: Terminal status (3GPP TS 29.199-08 version 9.0.0 Release 9)floppy3ETSI ETSI T

2、S 129 199-8 V9.0.0 (2010-01)13GPP TS 29.199-08 version 9.0.0 Release 9Reference RTS/TSGC-0029199-08v900 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-8 V9.0.0 (2010-01)23GPP TS 29.199-08 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-8 V9.0.0 (2010-01)33GPP TS 29.199-08 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Ab

14、breviations . 7g34 Detailed service description . 7g35 Namespaces 7g36 Sequence diagrams . 8g36.1 Terminal status query . 8g36.2 Terminal status group query . 9g36.3 Terminal status notification 10g36.4 Terminal Status Notification with Check Immediate . 11g37 XML Schema data type definition . 13g37

15、.1 Status enumeration . 13g37.2 RetrievalStatus enumeration . 13g37.3 StatusData structure 13g37.4 StatusInformation structure 13g38 Web service interface definition . 14g38.1 Interface: TerminalStatus . 14g38.1.1 Operation: GetStatus. 14g38.1.1.1 Input message: GetStatusRequest . 14g38.1.1.2 Output

16、 message: GetStatusResponse 14g38.1.1.3 Referenced faults . 14g38.1.2 Operation: GetStatusForGroup . 15g38.1.2.1 Input message: GetStatusForGroupRequest 15g38.1.2.2 Output message: GetStatusForGroupResponse. 15g38.1.2.3 Referenced faults . 15g38.2 Interface: TerminalStatusNotificationManager 16g38.2

17、.1 Operation: StartNotification 16g38.2.1.1 Input message: StartNotificationRequest 16g38.2.1.2 Output message: StartNotificationResponse . 16g38.2.1.3 Referenced faults . 16g38.2.2 Operation: EndNotification . 17g38.2.2.1 Input message: EndNotificationRequest . 17g38.2.2.2 Output message: EndNotifi

18、cationResponse 17g38.2.2.3 Referenced faults . 17g38.3 Interface: TerminalNotification 18g38.3.1 Operation: StatusNotification . 18g38.3.1.1 Input message: StatusNotificationRequest 18g38.3.1.2 Output message: StatusNotificationResponse . 18g38.3.1.3 Referenced faults . 18g38.3.2 Operation: StatusEr

19、ror 18g38.3.2.1 Input message: StatusErrorRequest . 18g38.3.2.2 Output message: StatusErrorResponse 18g38.3.2.3 Referenced faults . 18g38.3.3 Operation: StatusEnd 19g3ETSI ETSI TS 129 199-8 V9.0.0 (2010-01)43GPP TS 29.199-08 version 9.0.0 Release 98.3.3.1 Input message: StatusEndRequest . 19g38.3.3.

20、2 Output message: StatusEndResponse 19g38.3.3.3 Referenced faults . 19g39 Fault definitions 20g39.1 Fault: PolicyException . 20g310 Service policies 20g3Annex A (normative): WSDL for Terminal Status . 21g3Annex B (informative): Description of Parlay X Web Services Part 8: Terminal Status for 3GPP2 c

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

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

23、25g3ETSI ETSI TS 129 199-8 V9.0.0 (2010-01)53GPP TS 29.199-08 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 Parl

24、ay 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 fo

25、llowing 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

26、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 d

27、ocument. Introduction The present document is part 8 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 call

28、“ 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 managemen

29、t“ 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“ Pa

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

31、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 Terminal Status W

32、eb Service aspects of the interface. All aspects of the Terminal Status 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 interfaces. The

33、 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 in this

34、 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 applies. In th

35、e 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 for the O

36、pen 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 3GPP TS 29

37、.199-1: “Open Service Access (OSA); Parlay X web services; Part 1: Common“. 3 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. ETSI ETSI TS 129 199-8 V9.0.0 (2010-01)73GPP TS 29.199-08 version 9.0.0 R

38、elease 93.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 apply. 4 Detailed service description Terminal Status provides access to the status of a terminal through: Request for the status of a terminal. Request for the status of a group of term

39、inals. Notification of a change in the status of a terminal. The status of a terminal can be expressed as reachable, unreachable or busy - however not all terminals distinguish a busy status, so applications should be able to adapt to what information is available (using the service properties to de

40、termine available information). When a request for a group of terminals is made, the response may contain a full or partial set of results. This allows the service to provide results based on a number of criteria including number of terminals for which the request is made and amount of time required

41、 to retrieve the information. This allows the requester to initiate additional requests for those terminals for which information was not provided. 5 Namespaces The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/terminal_status/v4_0 The TerminalStatus interface uses the

42、namespace: http:/www.csapi.org/wsdl/parlayx/terminal_status/v4_0 The TerminalStatusNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/terminal_status/notification_manager/v4_0 The TerminalStatusNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlay

43、x/terminal_status/notification/v4_0 The xsd namespace is used in the present document to refer to the XML Schema data types defined in XML Schema 5. The use of the name xsd is not semantically significant. ETSI ETSI TS 129 199-8 V9.0.0 (2010-01)83GPP TS 29.199-08 version 9.0.0 Release 96 Sequence di

44、agrams 6.1 Terminal status query Pattern: Request / Response. When an application is interested in determining the status of a terminal device, it may provide a terminal device address, and receive the status for the device requested. : Application : Terminal StatusgetStatusRetrieve terminal statusS

45、tatusETSI ETSI TS 129 199-8 V9.0.0 (2010-01)93GPP TS 29.199-08 version 9.0.0 Release 96.2 Terminal status group query Pattern: Request / Response. When an application is interested in determining the status of a set of terminal devices, it may provide an array of terminal device addresses, including

46、 network managed group addresses, and receive the status for the set of devices requested. : Application : Terminal StatusgetStatusForGroupRetrieve terminal statusStatus listProcess groupsETSI ETSI TS 129 199-8 V9.0.0 (2010-01)103GPP TS 29.199-08 version 9.0.0 Release 96.3 Terminal status notificati

47、on Pattern: Application Correlated Multiple Notification. An application can be notified of a change in the status of terminal devices. When the status of a terminal device changes, a notification message will be sent to the application. : Application : Notification Application: Notification Web Ser

48、vice: Terminal Status NotificationAt some later time, an event occurs to trigger the notificationAt some later time, the notification may be cancelledCreate correlation idstatusNotificationstartNotificationendNotificationETSI ETSI TS 129 199-8 V9.0.0 (2010-01)113GPP TS 29.199-08 version 9.0.0 Releas

49、e 96.4 Terminal Status Notification with Check Immediate In some applications, the terminal status notification will be used to watch for a specific status change. An example is a call when available service, where the terminal status is checked and determined to be not reachable or busy, and a notification is set up to notify the application when the terminal becomes reachable. Between the time that the original status determination and the time the notification is set up, the terminal status could change to reachab