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

1、 ETSI TR 102 397-9-2 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 2: Mapping to Mobility User Location CAMELETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-09-02-OSA Ke

2、ywords 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 t

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

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

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

6、horized 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 M

7、embers. 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-2 V1.1.1 (2005-08) 3 Contents Intellectual P

8、roperty Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .5 4 Mapping description.5 5 Sequence diagrams.6 5.1 Single address query.6 5.2 Group query6 5.3 Periodic notification .7 6 Detailed mapping information7 6.1 Operations 7 6.1.1 ge

9、tLocation .7 6.1.1.1 Mapping to IpUserLocationCamel.locationReportReq.8 6.1.1.2 Mapping from IpAppUserLocationCamel.locationReportRes.8 6.1.1.3 Mapping from IpAppUserLocationCamel.locationReportErr.9 6.1.2 getLocationForGroup9 6.1.2.1 Mapping to IpUserLocationCamel.locationReportReq.10 6.1.2.2 Mappi

10、ng from IpAppUserLocationCamel.locationReportRes.10 6.1.2.3 Mapping from IpAppUserLocationCamel.locationReportErr.12 6.1.3 getTerminalDistance.12 6.1.3.1 Mapping to IpUserLocationCamel.locationReportReq.12 6.1.3.2 Mapping from IpAppUserLocationCamel.locationReportRes.12 6.1.3.3 Mapping from IpAppUse

11、rLocationCamel.locationReportErr.13 6.1.4 startGeographicalNotification, locationNotification, locationError13 6.1.5 startPeriodicNotification, locationNotification, locationError13 6.1.5.1 Mapping to IpUserLocationCamel.periodicLocationReportingStartReq.14 6.1.5.2 Mapping to IpUserLocationCamel.per

12、iodicLocationReportingStop 14 6.1.5.3 Mapping from IpAppUserLocationCamel.periodicLocationReport.15 6.1.5.4 Mapping from IpAppUserLocationCamel.periodicLocationReportErr.16 6.1.6 endNotification .16 6.1.6.1 Mapping to IpUserLocationCamel.periodicLocationReportingStop 16 6.1.7 locationEnd.16 6.2 Exce

13、ptions 17 6.2.1 Mapping from TpMobilityError 17 6.2.2 Mapping from Parlay/OSA Method Exceptions .17 7 Additional notes .17 History 18 ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETS

14、I. 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 to ETSI in respect of ETSI standards“, which is availab

15、le 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 given as to the existence of other IPRs not referenced

16、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 Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networkin

17、g (TISPAN). The present document is part 9, sub-part 2, of a multi-part deliverable providing an informative mapping of Parlay X Web Services to the Parlay Open Service Access (OSA) APIs and, where applicable, to IMS, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“;

18、 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 Status Mapping“; Part 9: “Terminal Location Mapping“; Sub-part 1: “Mapping to Mobility User Location“; S

19、ub-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: Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 5 and the P

20、arlay/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. ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 5 1 Scope The present document specifies the mapping of the Pa

21、rlay X Terminal Location Web Service to the Mobility User Location CAMEL Service Capability Feature (SCF). The Parlay X Web Services provide powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the IT community can both quickly comprehend

22、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 open standardized interface, i.e. the Parlay/OSA APIs. 2 References For the purposes of this Techn

23、ical 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 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-

24、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 and altitude for geographic point locations“. 5 ETSI ES 202 391-13: “Open Service Access (OSA); Parl

25、ay 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. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 102 397-1

26、 3 apply. 4 Mapping description The Terminal Location capability can be implemented with Parlay/OSA Mobility User Location CAMEL. It is applicable to ETSI OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Releases 4.x/5.x/6.x. ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 6 5 Sequence diagrams 5.1 Single

27、 address query Application Terminal Location IpAppUserLocation Camel IpUser Location Camel getLocationRequest “forward event” “new” locationReportReq() locationReportRes() getLocationResponse Figure 1 5.2 Group query Application Terminal Location IpAppUserLocation Camel IpUser Location Camel getLoca

28、tionForGroupRequest “forward event“ “new“ locationReportRes() locationReportRes() getLocationForGroupResponse Figure 2 ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 7 5.3 Periodic notification Application Terminal Location IpAppUserLocationCamel IpUser LocationCamel startPeriodicNotificationRequest “new

29、“ periodicLocationReportingStartReq () locationNotificationRequest startPeriodicNotificationResponse locationNotificationResponse periodicLocationReport () locationNotificationRequest locationNotificationResponse endNotificationRequest periodicLocationReportingStop () endNotificationResponse “forwar

30、d event“ periodicLocationReport () “forward event“ Figure 3 6 Detailed mapping information 6.1 Operations 6.1.1 getLocation The sequence diagram in clause 5.1 illustrates the flow for this operation. A synchronous service from the Parlay X clients point of view is mapped onto an asynchronous service

31、 from the Parlay clients point of view. It is mapped to the following Parlay/OSA methods: IpUserLocationCamel.locationReportReq; IpAppUserLocationCamel.locationReportRes; IpAppUserLocationCamel.locationReportErr. ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 8 6.1.1.1 Mapping to IpUserLocationCamel.loca

32、tionReportReq The IpUserLocationCamel.locationReportReq method is invoked with the following parameters. Name Type Comment appLocationCamel IpAppUserLocation CamelRef Not mapped. Reference to callback (internal). users TpAddressSet Specifies a single address, which is constructed based on the URI pr

33、ovided in the address part of the getLocationRequest message, mapped as described in TR 102 397-1 3. The requestedAccuracy part of the getLocationRequest message is not mapped to the IpUserLocationCamel.locationReportReq method. The acceptableAccuracy part of the getLocationRequest message is not ma

34、pped to the IpUserLocationCamel.locationReportReq method. Instead is is used to filter geographic location information contained in the IpAppUserLocationCamel.locationReportRes method, as described in clause 6.1.1.2. The result from IpUserLocationCamel.locationReportReq is of type TpAssignmentID and

35、 is used internally to correlate the callbacks. It is not mapped to the Parlay X interface. Parlay exceptions thrown by IpUserLocationCamel.locationReportReq are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.2 Mapping from IpAppUserLocationCamel.locationReportRes The IpAppUserLocatio

36、nCamel.locationReportRes method is invoked with the following parameters. Name Type Comment assignmentId TpAssignmentID Not mapped. The value provide in the result from IpUserLocationCamel.locationReportReq. locations TpUserLocation CamelSet Specifies the location of a single user. If the location d

37、ata is valid, then it is mapped to the result part of the getLocationResponse message, which is a LocationInfo structure. If the location data is invalid, a Parlay X exception is raised. Determining the validity of the location data is described below. ETSI ETSI TR 102 397-9-2 V1.1.1 (2005-08) 9 The

38、 TpUserLocationCamel structure is mapped to the LocationInfo structure, or a Parlay X exception, as follows. Name Type Comment TpUserLocation Camel: StatusCode TpMobilityError If this element value is other than P_M_OK, then the location retrieval attempt has failed and the element error value is ma

39、pped to a Parlay X exception as defined in clause 6.2. TpUserLocation Camel: UserID TpAddress This element is mapped to the LocationInfo:Address element, but only if the StatusCode element value is P_M_OK. All other elements of The TpUserLocationCamel structure are defined only if the StatusCode ele

40、ment value is P_M_OK. TpUserLocation Camel: Geographical PositionPresent TpUserLocation Camel: Geographical Position TpBoolean TpGeographical Position For GeographicalPositionPresent (of type TpBoolean): If the value is “False“, then the location retrieval attempt has failed and the Parlay X excepti

41、on SVC0001: Service error is returned. If the value is “True“, then the GeographicalPosition element is present. It specifies a position and an area of uncertainty. It is mapped to the elements of LocationInfo as follows: Longitude maps to Longitude Latitude maps to Latitude TypeOfUncertaintyShape a

42、nd all other related elements of the GeographicalPosition field map to Accuracy. However, if the mapped Accuracy value is greater than the value of the acceptableAccuracy part of the original getLocationRequest message, then the Parlay X exception SVC0200: Accuracy out of limit is returned instead.

43、TpUserLocation Camel: TimestampPresent TpUserLocation Camel: Timestamp TpBoolean TpDateAndTime If the TimestampPresent element value is “False“, then the Timestamp element is not present. If the TimestampPresent element value is “True“, then the Timestamp element maps to LocationInfo:Timestamp. TpUs

44、erLocation Camel: all other elements Tp All other elements of TpUserLocationCamel are Camel-specific and are not mapped to the LocationInfo structure. Note that there is no mapping to the LocationInfo:Altitude element of the result part of the getLocationResponse message. 6.1.1.3 Mapping from IpAppU

45、serLocationCamel.locationReportErr The IpAppUserLocationCamel.locationReportErr method is invoked with the following parameters. Name Type Comment assignmentId TpAssignmentID Not mapped. The value provide in the result from IpUserLocationCamel.locationReportReq. cause TpMobilityError diagnostic TpMo

46、bilityDiagnostic Specifies the error and additional information that led to the failure. The error value/information is mapped to a Parlay X exception as defined in clause 6.2. 6.1.2 getLocationForGroup The sequence diagrams in clause 5.2 illustrates the flow for this operation. ETSI ETSI TR 102 397

47、-9-2 V1.1.1 (2005-08) 10A 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: IpUserLocationCamel.locationReportReq; IpAppUserLocationCamel.locationReportRes; IpApp

48、UserLocationCamel.locationReportErr. 6.1.2.1 Mapping to IpUserLocationCamel.locationReportReq The IpUserLocationCamel.locationReportReq method is invoked with the following parameters. Name Type Comment appLocationCamel IpAppUserLocation CamelRef Not mapped . Reference to callback (internal). users

49、TpAddressSet Specifies multiple addresses. Each address is constructed based on the URI provided in the addresses part of the getLocationForGroupRequest message, mapped as described in TR 102 397-1 3. The requestedAccuracy part of the getLocationForGroupRequest message is not mapped to the IpUserLocationCamel.locationReportReq method. The acceptableAccuracy part of the getLocationForGroupRequest message is not mapped to the IpUserLocationCamel.locationReportReq method. Instead is is used to filter geographic location inform