ETSI TR 102 397-9-1-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 9 Terminal Location Mapping Sub-part 1 Mapping to Mobility User Location.pdf

《ETSI TR 102 397-9-1-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 9 Terminal Location Mapping Sub-part 1 Mapping to Mobility User Location.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 102 397-9-1-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 9 Terminal Location Mapping Sub-part 1 Mapping to Mobility User Location.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 102 397-9-1 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 9: Terminal Location Mapping;Sub-part 1: Mapping to Mobility User LocationETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-09-01-OSA Keywords

2、 API, OSA, service 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 lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the pre

3、sent 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 difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case

4、 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 that the document may be subject to revision or change of status. Information on the current status of this and

5、 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:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorize

6、d by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members

7、. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI 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. ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 3 Contents Intellectual Propert

8、y Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Mapping description.6 5 Sequence diagrams.7 5.1 Single address query.7 5.2 Group query7 5.3 Notification.8 5.4 Periodic notification .9 6 Detailed mapping information9 6.1 Operatio

9、ns 9 6.1.1 getLocation .9 6.1.1.1 Mapping to IpUserLocation.extendedLocationReportReq10 6.1.1.2 Mapping to TpLocationRequest.10 6.1.1.3 Mapping from IpAppUserLocation.extendedLocationReportRes11 6.1.1.4 Mapping from TpUIExtendedDataSet.11 6.1.1.5 Mapping from IpAppUserLocation.extendedLocationReport

10、Err12 6.1.1.6 Alternative mapping to IpUserLocation.locationReportReq 12 6.1.1.7 Alternative mapping from IpAppUserLocation.locationReportRes.12 6.1.1.8 Alternative mapping from IpAppUserLocation.locationReportErr.13 6.1.2 getLocationForGroup13 6.1.2.1 Mapping to IpUserLocation.extendedLocationRepor

11、tReq14 6.1.2.2 Mapping from IpAppUserLocation.extendedLocationReportRes14 6.1.2.3 Mapping from IpAppUserLocation.extendedLocationReportErr15 6.1.2.4 Alternative mapping to IpUserLocation.locationReportReq 15 6.1.2.5 Alternative mapping from IpAppUserLocation.locationReportRes.15 6.1.2.6 Alternative

12、mapping from IpAppUserLocation.locationReportErr.16 6.1.3 getTerminalDistance.17 6.1.3.1 Mapping to IpUserLocation.extendedLocationReportReq17 6.1.3.2 Mapping to TpLocationRequest.18 6.1.3.3 Mapping from IpAppUserLocation.extendedLocationReportRes18 6.1.3.4 Mapping from IpAppUserLocation.extendedLoc

13、ationReportErr19 6.1.3.5 Alternative mapping to IpUserLocation.locationReportReq 19 6.1.3.6 Alternative mapping from IpAppUserLocation.locationReportRes.19 6.1.3.7 Alternative mapping from IpAppUserLocation.locationReportErr.20 6.1.4 startGeographicalNotification, locationNotification, locationError

14、20 6.1.4.1 Mapping toIpTriggeredUserLocation.triggeredLocationReportingStartReq 21 6.1.4.2 Mapping to TpLocationTriggerSet .22 6.1.4.3 Mapping to IpUserLocation.extendedLocationReportReq22 6.1.4.4 Mapping to IpTriggeredUserLocation.triggeredLocationReportingStop.23 6.1.4.5 Mapping from IpAppTriggere

15、dUserLocation.triggeredLocationReport .23 6.1.4.6 Mapping from IpAppTriggeredUserLocation.triggeredLocation ReportErr 24 6.1.4.7 Mapping from IpAppUserLocation.extendedLocationReportRes24 6.1.4.8 Mapping from IpAppUserLocation.extendedLocationReportErr25 6.1.4.9 Alternative mapping to IpUserLocation

16、.locationReportReq 25 6.1.4.10 Alternative mapping from IpAppUserLocation.locationReportRes.26 6.1.4.11 Alternative mapping from IpAppUserLocation.locationReportErr.27 6.1.5 startPeriodicNotification, locationNotification, locationError27 ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 4 6.1.5.1 Mapping t

17、o IpUserLocation.periodicLocationReportingStartReq.28 6.1.5.2 Mapping to IpUserLocation.periodicLocationReportingStop28 6.1.5.3 Mapping from IpAppUserLocation.periodicLocationReport.29 6.1.5.4 Mapping from IpAppUserLocation.periodicLocationReportErr30 6.1.6 endNotification .30 6.1.6.1 Mapping to IpT

18、riggeredUserLocation.triggeredLocationReporting Stop30 6.1.6.2 Mapping to IpUserLocation.periodicLocationReportingStop30 6.1.7 locationEnd.31 6.2 Exceptions 31 6.2.1 Mapping from TpMobilityError 31 6.2.2 Mapping from Parlay/OSA Method Exceptions .31 7 Additional notes .31 History 32 ETSI ETSI TR 102

19、 397-9-1 V1.1.1 (2005-08) 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 non-members, and can be found in ETSI SR 000

20、 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/home.asp). Pursuant to the ETSI IPR Polic

21、y, 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 the present document. Foreword This Techn

22、ical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 9, sub-part 1 of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X Web Service

23、s to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal

24、Status Mapping“; Part 9: “Terminal Location Mapping“; Sub-part 1: “Mapping to Mobility User Location“; Sub-part 2: “Mapping to Mobility User Location CAMEL“; Part 10: “Call Handling Mapping“; Part 11: “Audio Call Mapping“; Part 12: “Multimedia Conference Mapping“; Part 14: “Presence Mapping“. NOTE:

25、Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 5 and the Parlay/OSA APIs. If a mapping is developed, it will become part 13 of this series. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP.

26、ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 6 1 Scope The present document specifies the mapping of the Parlay X Terminal Location Web Service to the Mobility User Location Service Capability Feature (SCF). The Parlay X Web Services provide powerful yet simple, highly abstracted, imaginative, telecomm

27、unications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables application developers to make use of network functionality through an

28、open standardized interface, i.e. the Parlay/OSA APIs. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 ETSI TR 121 905: “Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May

29、 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 ETSI TR 102 397-1: “ Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs; Part 1: Common Mapping“. 4 ISO 6709: “Standard representation of latitude, longitude a

30、nd altitude for geographic point locations“. 5 ETSI ES 202 391-13: “Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 102 397-1 3 apply.

31、3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Terminal Location capability can be implemented with Parlay/OSA Mobility User Location. It is applicable to ETSI OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Rel

32、eases 4 to 6. ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 7 5 Sequence diagrams 5.1 Single address query Application Terminal Location IpAppUserLocation IpUser Location getLocationRequest “forward event” “new” extendedLocationReportReq() extendedLocationReportRes() getLocationResponse Figure 1 5.2 Gro

33、up query Application Terminal Location IpAppUserLocation IpUser Location getLocationForGroupRequest “forward event” “new” extendedLocationReportRes() extendedLocationReportRes() getLocationForGroupResponse Figure 2 ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 8 5.3 Notification In the following sequenc

34、e diagram, the yellow highlighted sub-sequence represents optional actions initiated by the Terminal Location web service, if the checkImmediate flag in the startGeographicalNotificationRequest message is enabled. locationNotificationRequest locationNotificationResponse“forward event“ locationNotifi

35、cationResponselocationNotificationRequest Application Terminal Location IpAppTriggered UserLocationIpTriggered UserLocationstartGeographicalNotificationRequest “new“ triggeredLocationReportingStartReq () extendedlocationReportRes ()locationNotificationRequest startGeographicalNotificationResponse lo

36、cationNotificationResponse“forward event“ triggeredLocationReport () locationNotificationRequest locationNotificationResponseendNotificationRequest triggeredLocationReportingStop () endNotificationResponse extendedlocationReportReq () “forward event“ triggeredLocationReport () IpApp User Location Ip

37、User Location “new“Figure 3 ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 9 5.4 Periodic notification Application Terminal LocationIpAppUserLocationIpUser LocationstartPeriodicNotificationRequest “new“periodicLocationReportingStartReq () locationNotificationRequest startPeriodicNotificationResponse loca

38、tionNotificationResponse“forward event“ periodicLocationReport () locationNotificationRequest locationNotificationResponse endNotificationRequest periodicLocationReportingStop () endNotificationResponse “forward event“ periodicLocationReport ()Figure 4 6 Detailed mapping information 6.1 Operations 6

39、.1.1 getLocation The sequence diagram in clause 5.1 illustrate the flow for this operation. A synchronous service from the Parlay X clients point of view is mapped onto an asynchronous service from the Parlay clients point of view. It is mapped to the following Parlay/OSA methods: IpUserLocation.ext

40、endedLocationReportReq; IpAppUserLocation.extendedLocationReportRes; IpAppUserLocation.extendedLocationReportErr. ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 10As shown in clause 5.1, an alternative mapping is possible where underlying network capabilities may be limited; for example altitude location

41、 information is not available. This mapping is to the following Parlay/OSA methods: IpUserLocation.locationReportReq; IpAppUserLocation.locationReportRes; IpAppUserLocation.locationReportErr. 6.1.1.1 Mapping to IpUserLocation.extendedLocationReportReq The IpUserLocation.extendedLocationReportReq met

42、hod is invoked with the following parameters. Name Type Comment appLocation IpAppUserLocationRef Not mapped . Reference to callback (internal). users TpAddressSet Specifies a single address, which is constructed based on the URI provided in the address part of the getLocationRequest message, mapped

43、as described in TR 102 397-1 3. request TpLocationRequest Specifies among others the requested location type, accuracy, response time and priority. See the discussion in clause 6.1.1.2 for mapping details. The acceptableAccuracy part of the getLocationRequest message is not mapped to the IpUserLocat

44、ion.extendedLocationReportReq method. Instead is is used to filter location information contained in the IpAppUserLocation.extendedLocationReportRes method, as described in clause 6.1.1.3. The result from IpUserLocation.extendedLocationReportReq is of type TpAssignmentID and is used internally to co

45、rrelate the callbacks. It is not mapped to the Parlay X interface. Parlay exceptions thrown by IpUserLocation.extendedLocationReportReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.2 Mapping to TpLocationRequest The request parameter is constructed as follows. Name Type Comment

46、RequestedAccuracy TpFloat Requested accuracy in meters. It is constructed using the value of the requestedAccuracy part. RequestedResponseTime TpLocationResponseTime Not mapped. Requested response time as a classified requirement or as an absolute timer. Assigned any of the supported values: P_M_NO_

47、DELAY, P_M_LOW_DELAY, P_M_DELAY_TOLERANT or P_M_USE_TIMER_VALUE . AltitudeRequested TpBoolean Altitude request flag. It is constructed using the value of the the web service policy AltitudeSometimesAvailable. Type TpLocationType Not mapped. The kind of location that is requested. Assigned either of

48、the following values: P_M_CURRENT or P_M_CURRENT_OR_LAST_KNOWN. Priority TpLocationPriority Not mapped. Priority of location request. Assigned any of the supported values: P_M_NORMAL or P_M_HIGH. RequestedLocation Method TpString Not mapped. The kind of location method that is requested. Assigned an

49、y of the supported values: “Time of Arrival“, “Timing Advance“, “GPS“, “User Data Lookup“ or “Any Time Interrogation“. ETSI ETSI TR 102 397-9-1 V1.1.1 (2005-08) 116.1.1.3 Mapping from IpAppUserLocation.extendedLocationReportRes The IpAppUserLocation.extendedLocationReportRes method is invoked with the following parameters. Name Type Comment assignmentId TpAssignmentID Not mapped. The value provide in the result from IpUserLocation.extendedLocationReportReq. locations TpUserLocation ExtendedSet Specifies the location of a