1、 ETSI TS 129 199-16 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 16: Geocoding (3GPP TS 29.199-16 version 9.0.0 Release 9)floppy3 ETSI ETSI TS 1
2、29 199-16 V9.0.0 (2010-01)13GPP TS 29.199-16 version 9.0.0 Release 9Reference RTS/TSGC-0029199-16v900 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 l
3、ucratif 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 differe
4、nce 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 that
5、 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:/por
6、tal.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, PLUG
7、TESTSTM, 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 for
8、 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-16 V9.0.0 (2010-01)23GPP TS 29.199-16 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potentially essentia
9、l 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). Th
12、e 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 und
13、er http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)33GPP TS 29.199-16 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Ab
14、breviations . 7g34 Detailed service description . 7g35 Namespaces 9g36 Sequence diagrams . 10g36.1 Get address of terminal . 10g36.2 Get address of terminal for group . 11g36.3 Get terminal distance from address 11g37 XML Schema data type definition . 12g37.1 Accuracy values . 12g37.2 AddressInfo st
15、ructure . 12g37.3 AddressData structure 12g37.4 DelayTolerance enumeration 12g38 Web service interface definition . 13g38.1 Interface: TerminalAddress 13g38.1.1 Operation: getAddressOfTerminal 13g38.1.1.1 Input message: getAddressOfTerminalRequest 13g38.1.1.2 Output message: getAddressOfTerminalResp
16、onse . 13g38.1.1.3 Referenced Faults 13g38.1.2 Operation: getAddressOfTerminalForGroup 15g38.1.2.1 Input message: getAddressOfTerminalForGroupRequest. 15g38.1.2.2 Output message: getAddressOfTerminalForGroupResponse . 15g38.1.2.3 Referenced faults . 15g38.1.3 Operation: GetTerminalDistanceFromAddres
17、s 16g38.1.3.1 Input message: GetTerminalDistanceFromAddressRequest . 16g38.1.3.2 Output message: GetTerminalDistanceFromAddressResponse 16g38.1.3.3 Referenced faults. 16g39 Fault definitions 17g39.1 Fault: ServiceException . 17g39.1.1 SVC0200: Accuracy out of limit. . 17g39.1.2 SVC0370: No valid ter
18、minal number(s) . 17g39.2 Fault: PolicyException . 17g39.2.1 POL0230: Requested accuracy not supported 17g39.2.2 POL0350: Too many terminal numbers 17g310 Service policies 17g3Annex A (normative): WSDL for Geocoding 18g3Annex B (informative): Bibliography . 19g3ETSI ETSI TS 129 199-16 V9.0.0 (2010-0
19、1)43GPP TS 29.199-16 version 9.0.0 Release 9Annex C (informative): Description of Parlay X Web Services Part 16: Geocoding for 3GPP2 cdma2000 networks . 20g3C.1 General Exceptions. 20g3C.2 Specific Exceptions 20g3C.2.1 Clause 1: Scope 20g3C.2.2 Clause 2: References 20g3C.2.3 Clause 3: Definitions an
20、d abbreviations . 20g3C.2.4 Clause 4: Detailed service description 20g3C.2.5 Clause 5: Namespaces 20g3C.2.6 Clause 6: Sequence diagrams . 21g3C.2.7 Clause 7: XML Schema data type definition 21g3C.2.8 Clause 8: Web Service interface definition 21g3C.2.9 Clause 9: Fault definitions 21g3C.2.10 Clause 1
21、0: Service policies . 21g3C.2.11 Annex A (normative):WSDL for Geocoding . 21g3Annex D (informative): Change history . 22g3History 23g3ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)53GPP TS 29.199-16 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partner
22、ship Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following 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 increa
23、se in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented 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
24、, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 16 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specification Group Core Network and Te
25、rminals; Open Service Access (OSA); Parlay 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
26、location“ Part 10: “Call handling“ Part 11: “Audio call“ Part 12: “Multimedia conference“ Part 13: “Address list management“ Part 14: “Presence“ Part 15: “Message Broadcast“ Part 16: “Geocoding“ Part 17: “Application driven Quality of Service (QoS)“ Part 18: “Device Capabilities and Configuration“ P
27、art 19: “Multimedia streaming control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“ Part 22: “Policy“ ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)63GPP TS 29.199-16 version 9.0.0 Release 91 Scope The present document is Part 16 of the Stage 3 Parlay X Web Services spe
28、cification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers 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 T
29、S 23.198 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Geocoding Web Service aspects of the interface. All aspects of the Geocoding Web Service are defined here, these being: Name spaces Sequence diagrams Data definitions Interface specification pl
30、us detailed method descriptions Fault definitions Service policies WSDL Description of the interfaces 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 O
31、MA in June 2008. 2 References The following documents contain provisions which, through reference 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 refe
32、rence, subsequent revisions do not apply. For a non-specific reference, the latest version applies. 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.
33、 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.127: “Service requirement for 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 3GPP TS 29.199-1: “Open Service Access (OSA
34、); Parlay X web services; Part 1: Common“. 6 3GPP TS 29.199-9: “Open Service Access (OSA); Parlay X web services; Part 9: Terminal location“. ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)73GPP TS 29.199-16 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the pres
35、ent document, the terms and definitions given in 3GPP TS 29.199-1 5 and the following apply. address: set of strings that represent an address information for a geographical place It consists of the country, state, district, city, street, house number and zip/postal code. In this specification, the
36、address means a location address except where otherwise noted. coordinates: latitude, longitude pair that identifies a point on the Earths surface geocoding: transformation a description of a address, such as a place name, street address or postal code, into a normalized description of the location
37、with a geographical coordinates location: specific set of coordinates reverse geocoding: transformation a given location into a normalized description of address terminal number: string of decimal digits that terminal is uniquely indicated and located NOTE: Address is a name that is used in both Geo
38、coding SCF and Terminal Location SCF. The former uses address in the customary sense of a location address, while the latter uses it in the sense of a terminal identifier represented as a URI string. So terminal number is a better name for what Parlay X Terminal Location calls address, and address a
39、s Geocoding SCF typically define it. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 5, 3GPP TS 29.199-9 6 and the following apply: GMLC Gateway Mobile Location Center MLP Mobile Location Protocol MMS Multimedia Message MPC Mobile Positioning C
40、enter OMA Open Mobile Alliance OpenLS Open Location Services URI Uniform Resource Identifier XML Extensible Markup Language 4 Detailed service description Where the Parlay X Terminal Location Web Service provides access to the geographical coordinates at which a terminal is located, the Geocoding We
41、b Service provides access to an additional level of refinement, allowing the service developer to work with actual location addresses and the like: Request the location address of a terminal number. Request the location address of a group of terminals. Request the distance of a terminal from a speci
42、fic location address. When a request is made on behalf of a group of terminals, the response may be 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 to r
43、etrieve the information. This allows the requestor to initiate additional requests for those terminals for which information was not provided. ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)83GPP TS 29.199-16 version 9.0.0 Release 9Figure 4.1 shows the Geocoding Web Service architecture composed of Parlay
44、X Application, Parlay X Gateway, Parlay Gateway, GMLC/MPC, Addressing server. OMA/MLP is used between Parlay X Gateway and GMLC/MPC and OpenLS/XML is used between Parlay X Gateway and Addressing server. In the getAddressOfTerminal and getAddressOfTerminalForGroup operations, if subscriber asks someo
45、nes address or group addresses, Parlay X Application calls the Geocoding Web Service. Parlay X gateway gets the geographical coordinates of terminal number from GMLC/MPC and then feeds the retrieved geographical coordinates to addressing server. Finally it gets the location address. In the getTermin
46、alDistanceFromAddress operation, the subscriber asks for the distance of a terminal from a specific address; the Parlay X Application calls the Geocoding Web Service. The Parlay X gateway gets the geographical coordinates of the address from an addressing server. The Parlay X gateway gets the geogra
47、phical coordinates of the terminal from GMLC/MPC. Finally it computes the distance between the two sets of geographical coordinates. Parlay X Application GMLC /MPC Mobile network Parlay X API Parlay X Application Addressing Server OpenLS/XML Geocoding Web Service Parlay X Gateway SOAP SOAP Parlay Ga
48、teway Mobility Parlay/OSA API OMA/MLP Figure 4.1: Geocoding Web Service architecture ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)93GPP TS 29.199-16 version 9.0.0 Release 95 Namespaces The Geocoding interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/geocoding/terminal_address/v4_0 The data ty
49、pes are defined in the namespace: http:/www.csapi.org/schema/parlayx/geocoding/v4_0 The xsd namespace is used in the present document to refer to the XML Schema data types defined in XML Schema (3GPP TS 29.199-1 5). The use of the name xsd is not semantically significant. ETSI ETSI TS 129 199-16 V9.0.0 (2010-01)103GPP TS 29.199-16 version 9.0.0 Release 96 Sequence diagrams 6.1 Get address of terminal Pattern: Request / Response. For an application to determine the address of terminal device, it provides a terminal num
