1、 ETSI ES 202 391-9 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 9: Terminal Location(Parlay X 2)floppy3 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-09-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ce
2、dex - 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 docum
3、ent 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 P
4、DF 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/stat
5、us.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 exten
6、d 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 ETSI
7、 registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7
8、 4 Detailed service description .7 5 Namespaces7 6 Sequence diagrams.8 6.1 Terminal location query .8 6.2 Terminal location group query .9 6.3 Terminal location notification 10 6.4 Terminal location notification with check immediate 11 6.5 Terminal location periodic notification 12 7 XML Schema data
9、 type definition .13 7.1 Latitude and Longitude values .13 7.2 Accuracy values .13 7.3 EnteringLeavingCriteria enumeration 14 7.4 LocationInfo structure 14 7.5 RetrievalStatus enumeration.14 7.6 LocationData structure .14 7.7 DelayTolerance enumeration15 8 Web Service interface definition15 8.1 Inte
10、rface: TerminalLocation.15 8.1.1 Operation: getLocation .15 8.1.1.1 Input message: getLocationRequest15 8.1.1.2 Output message: getLocationResponse.15 8.1.1.3 Referenced faults.16 8.1.2 Operation: getTerminalDistance.16 8.1.2.1 Input message: getTerminalDistanceRequest .16 8.1.2.2 Output message: ge
11、tTerminalDistanceResponse 16 8.1.2.3 Referenced faults.16 8.1.3 Operation: getLocationForGroup17 8.1.3.1 Input message: getLocationForGroupRequest 17 8.1.3.2 Output message: getLocationForGroupResponse .17 8.1.3.3 Referenced faults.17 8.2 Interface: TerminalLocationNotificationManager17 8.2.1 Operat
12、ion: startGeographicalNotification.18 8.2.1.1 Input message: startGeographicalNotificationRequest .18 8.2.1.2 Output message: startGeographicalNotificationResponse 18 8.2.1.3 Referenced faults.19 8.2.2 Operation: startPeriodicNotification.19 8.2.2.1 Input message: startPeriodicNotificationRequest19
13、8.2.2.2 Output message: startPeriodicNotificationResponse 19 8.2.2.3 Referenced faults.20 8.2.3 Operation: endNotification .20 8.2.3.1 Input message: endNotificationRequest20 8.2.3.2 Output message: endNotificationResponse.20 8.2.3.3 Referenced faults.20 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 4 8.3
14、 Interface: TerminalLocationNotification21 8.3.1 Operation: locationNotification 21 8.3.1.1 Input message: locationNotificationRequest.21 8.3.1.2 Output message: locationNotificationResponse21 8.3.1.3 Referenced faults.21 8.3.2 Operation: locationError.21 8.3.2.1 Input message: locationErrorRequest2
15、1 8.3.2.2 Output message: locationErrorResponse.21 8.3.2.3 Referenced faults.21 8.3.3 Operation: locationEnd .21 8.3.3.1 Input message: locationEndRequest22 8.3.3.2 Output message: locationEndResponse.22 8.3.3.3 Referenced faults.22 9 Fault definitions22 9.1 ServiceException22 9.1.1 SVC0200: Accurac
16、y out of limit 22 9.2 PolicyException .22 9.2.1 POL0230: Requested accuracy not supported 22 9.2.2 POL0231: Geographic notification not available .22 9.2.3 POL0232: Periodic notification not available.22 10 Service policies 23 Annex A (normative): WSDL for Terminal Location 24 Annex B (informative):
17、 Bibliography.25 History 26 ETSI ETSI ES 202 391-9 V1.3.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 essential IPRs, if any, is publicly available for ETSI members and no
18、n-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 are available on the ETSI Web server (http:/webapp.etsi.org/IPR
19、/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 ETSI Web server) which are, or may be, or may become, essential to
20、 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 9 of a multi-part deliverable covering Open Service Access (OSA); Parl
21、ay 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: “Terminal Status“; Part 9: “Terminal Location“; Part 10: “Call Handli
22、ng“; Part 11: “Audio Call“; Part 12: “Multimedia Conference“; Part 13: “Address List Management“; Part 14: “Presence“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay X 2.2 set of specific
23、ations. The present document is equivalent to 3GPP TS 29.199-09 V6.5.0 (Release 6). ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 6 1 Scope The present document is part 9 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that
24、enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Common aspects of the Parlay X 2 Web Services. The following are defined here: Name spaces. Data definitions. Fault definitions. WSDL Desc
25、ription of the interfaces. 2 References References are either specific (identified by date of publication and/or edition number or version number) or 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 th
26、ereof 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 referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected locatio
27、n might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference sho
28、uld, 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 network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this c
29、lause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, th
30、e latest edition of the referenced document (including any amendments) applies. 1 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 2 ETSI ES 202 391-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Co
31、mmon (Parlay X 2)“. 3 ISO 6709: “Standard representation of latitude, longitude and altitude for geographic point locations“. ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202
32、391-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 202 391-1 2 apply. 4 Detailed service description Terminal Location provides access to the location of a terminal through: Request for the location of a terminal. Request for the location of a gr
33、oup of terminals. Notification of a change in the location of a terminal. Notification of terminal location on a periodic basis. Location is expressed through a latitude, longitude, altitude and accuracy. When a request for a group of terminals is made, the response may contain a full or partial set
34、 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 to retrieve the information. This allows the requester to initiate additional requests for those terminals for which informati
35、on was not provided. 5 Namespaces The Terminal Location interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/terminal_location/v2_3 The TerminalLocationNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/terminal_location/notification_manager/v2_4 The Termina
36、lLocationNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/terminal_location/notification/v2_2 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/terminal_location/v2_2 The “xsd“ namespace is used in the present document to refer to the XML Sche
37、ma data types defined in XML Schema 1. The use of the name “xsd“ is not semantically significant. ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 8 6 Sequence diagrams 6.1 Terminal location query Pattern: Request / Response. For an application to determine the location of a terminal device, it provides a te
38、rminal device address and desired accuracy, and receives the location for the device requested. : Application : Terminal Location Web ServiceRequest terminal locationRetrieve locationLocation dataFigure 1 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 9 6.2 Terminal location group query Pattern: Request /
39、Response. When an application requires the locations of a set of terminal devices, it may provide an array of terminal device addresses, including network managed group addresses, and receive the location data for the set of devices requested. : Application : Terminal Location Web ServiceRequest ter
40、minal location for groupRetrieve locationsLocation dataProcess groupsFigure 2 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 106.3 Terminal location notification Pattern: Application Correlated Multiple Notification. An application can be notified of a terminal device entering or leaving a geographical are
41、a. When a matching event occurs; a notification message will be sent to the application. : Application : Notification Application: Notification Web Service: Terminal Location Web ServiceAt some later time, an event occurs to trigger the notificationAt some later time, the notification may be cancell
42、edCreate correlation idNotification with correlatorCreate notification with correlatorCancel notification with correlatorFigure 3 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 116.4 Terminal location notification with check immediate In some applications, the terminal location notification will be used to
43、 watch for a specific location change. An example is a “call when present“ service, where the terminal location is checked and determined to be outside the target area, and a notification is set up to notify the application when the terminal enters the target area. Between the time of the original l
44、ocation determination and the time the notification is set up, the terminal could move into the target area, thus the notification on entry into the target area would not be sent. Using the check immediate flag, after the notification is established, the terminal location will be determined, and if
45、the terminal is in the target area, then a notification will be sent immediately. The following sequence diagram shows this scenario. : Application : Terminal Location Web Service: Notification Application: Terminal Location Notification: Notification Web ServiceGet locationLocationCreate correlator
46、Start geographical notification with check immediateSet up notificationCheck terminal locationLocation notificationApply count to notificationStatus endVoidFigure 4 ETSI ETSI ES 202 391-9 V1.3.1 (2008-05) 12This sequence shows: The Enterprise Application checks the location of a terminal, and receiv
47、es its location (in this scenario determining that the terminal is outside the target area). The Enterprise Application generates a correlator, and starts a notification with criteria defined to notify the Enterprise Web Service when the terminal enters the target area and the check immediate flag s
48、et to true. Sets up the notification to monitor terminal location. Check the current location of the terminal, and determine if the terminal lies inside the target area. In this case, the terminal is in the target area, and a notification is delivered to the Enterprise Web Service. The count of noti
49、fications is incremented and compared to the notification count limit. In this case, a single notification was requested, and the end notification message is sent. The startGeographicalNotification operation completes. This scenario includes the full set of interactions in one sequence, which also shows that the notifications can be received concurrent with the creation of the notification. 6.5 Terminal location periodic notification Pattern: Application Correlated Multiple Notification. An application can be notified of
