1、 ETSI ES 202 504-16 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 16: Geocoding(Parlay X 3)floppy3 ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-16-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex -
2、 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 document m
3、ay 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 PDF ve
4、rsion 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/status.as
5、p 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 extend to
6、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 regi
7、stered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 D
8、etailed service description .7 5 Namespaces8 6 Sequence diagrams.9 6.1 Get address of terminal.9 6.2 Get address of terminal for group.10 6.3 Get terminal distance from address 10 7 XML Schema data type definition .11 7.1 Accuracy values .11 7.2 AddressInfo structure .11 7.3 AddressData structure 11
9、 7.4 DelayTolerance enumeration11 8 Web Service interface definition12 8.1 Interface: TerminalAddress12 8.1.1 Operation: getAddressOfTerminal12 8.1.1.1 Input message: getAddressOfTerminalRequest 12 8.1.1.2 Output message: getAddressOfTerminalResponse .12 8.1.1.3 Referenced Faults12 8.1.2 Operation:
10、getAddressOfTerminalForGroup13 8.1.2.1 Input message: getAddressOfTerminalForGroupRequest.13 8.1.2.2 Output message: getAddressOfTerminalForGroupResponse .13 8.1.2.3 Referenced faults.13 8.1.3 Operation: getTerminalDistanceFromAddress .14 8.1.3.1 Input message: GetTerminalDistanceFromAddressRequest
11、.14 8.1.3.2 Output message: GetTerminalDistanceFromAddressResponse14 8.1.3.3 Referenced faults.14 9 Fault definitions14 9.1 ServiceException14 9.1.1 SVC0200: Accuracy out of limit 14 9.1.2 SVC0370: No valid terminal number(s) .15 9.2 PolicyException .15 9.2.1 POL0230: Requested accuracy not supporte
12、d 15 9.2.2 POL0350: Too many terminal numbers15 10 Service policies 15 Annex A (normative): WSDL for Geocoding 16 Annex B (informative): Bibliography.17 History 18 ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document
13、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 to ETSI in respect of ETSI
14、 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 given as to the existence
15、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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protoc
16、ols for Advanced Networking (TISPAN). The present document is part 16 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web Services, as identified below: Part 1: “Common“; Part 2: “Third Party Call“; Part 3: “Call Notification“; Part 4: “Short Messaging“; Part 5: “Multimedi
17、a 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 Management“; Part 14: “Presence“; Part 15: “Message Broadcast“; Part 16: “G
18、eocoding“; 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“. ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 5 The present document has been defined jointly b
19、etween ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay X 3.0 set of specifications. The present document is equivalent to 3GPP TS 29.199-16 V7.1.2 (Release 7). ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 6 1 Scope The present document is part 16
20、 of the Stage 3 Parlay X 3 Web Services specification 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 present document specifies the Ge
21、ocoding Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service Policies. WSDL Description of the interfaces. 2 References References are either specific (identified by date o
22、f 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 thereof and only in the following cases: - if it is accepted that it will be possible to use a
23、ll 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 location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, inform
24、ation 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 should, as far as possible, remain valid for the expected life of the document. The reference s
25、hall 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 clause were valid at the time of publication ETSI cannot guarantee their long term validity.
26、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, the latest edition of the referenced document (including any amendments) applies. 1 W3C Recomm
27、endation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 7 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 ETSI ES 202 504-9: “Open Se
28、rvice Access (OSA); Parlay X Web Services; Part 9: Terminal Location (Parlay X 3)“. 4 ISO 3166: “Codes for the representation of names of countries and their subdivisions“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES
29、 202 504-1 2 and the following apply: address: Set of strings that represent 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 address means a location address except where otherwise n
30、oted. coordinates: latitude, longitude pair that identifies a point on the Earths surface geocoding: transformation of a description of a address, such as a place name, street address or postal code, into a normalized description of the location with a geographical coordinates location: specific set
31、 of coordinates reverse geocoding: transformation of a given location into a normalized description of address terminal number: string of decimal digits that uniquely identify a terminal NOTE: Address is a name that is used in both the Geocoding and Terminal Location Web Services. The former uses ad
32、dress 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 an address. 3.2 Abbreviations For the purposes of the present document, the ab
33、breviations defined in ES 202 504-1 2, ES 202 504-9 3 and the following apply: GMLC Gateway Mobile Location Center MLP Mobile Location Protocol MMS Multimedia Message MPC Mobile Positioning Center OMA Open Mobile Alliance OpenLS Open Location Services URI Uniform Resource Identifier XML Extensible M
34、arkup Language 4 Detailed service description While the Parlay X Terminal Location Web Service provides access to the geographical coordinates at which a terminal is located, the Geocoding Web Service provides an additional level of refinement, allowing the service developer to work with actual loca
35、tion addresses and the like: Request the location address of a terminal number. Request the location address of a group of terminals. ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 8 Request the distance of a terminal from a specific location address. When a request is made on behalf of a group of termina
36、ls, the response may be a full or a 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 retrieve the information. This allows the requestor to initiate additional
37、requests for those terminals for which information was not provided. Figure 1 shows the Geocoding Web Service architecture comprising Parlay X Application, Parlay X Gateway, Parlay Gateway, GMLC/MPC, Addressing server. OMA/MLP is used between the Parlay X Gateway and GMLC/MPC and OpenLS/XML is used
38、between the Parlay X Gateway and the Addressing server. If the subscriber asks for someones address or for group addresses, the Parlay X Application invokes the getAddressOfTerminal or getAddressOfTerminalForGroup operations of the Geocoding Web Service. The Parlay X gateway gets the geographical co
39、ordinates of the terminal from GMLC/MPC and then feeds the retrieved geographical coordinates to addressing server. Finally it obtains the location address. In the getTerminalDistanceFromAddress operation, the subscriber asks for the distance of a terminal from a specific address; the Parlay X Appli
40、cation 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 geographical coordinates of the terminal from GMLC/MPC. Finally it computes the distance between the two sets of geographical coordin
41、ates. 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 Gateway Mobility Parlay/OSA API OMA/MLP Figure 1: Geocoding Web Service architecture 5 Namespaces The Geocoding interface uses th
42、e namespace: http:/www.csapi.org/wsdl/parlayx/geocoding/terminal_address/v3_1 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/geocoding/v3_0 The xsd namespace is used in the present document to refer to the XML Schema data types defined in XML Schema 1. The use of the
43、 name xsd is not semantically significant. ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 9 6 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 number and desired accuracy, and receives the loca
44、tion address for the device requested. :Application Request address of terminal Retrieve address of terminal AddressInfo :Geocoding Web Service Figure 2: Get address of terminal operation ETSI ETSI ES 202 504-16 V1.1.1 (2008-05) 106.2 Get address of terminal for group Pattern: Request / Response. Fo
45、r an application to determine the addresses for a set of terminal devices, it provides an array of terminal numbers, and receives the location addresses for the set of devices requested. :Application Request address of terminal for group Retrieve address of terminal for group AddressData :Geocoding
46、Web Service Figure 3: Get address of terminal for group operation 6.3 Get terminal distance from address Pattern: Request / Response. For an application to determine the distance from terminal to address, it provides a terminal number and address, and receives the distance between location of termin
47、al and address. :Application Request terminal distance from address Retrieve location of terminal distance :Geocoding Web Service Retrieve location of address Calculate the distance between the location of terminal and address Figure 4: Get terminal distance from address operation ETSI ETSI ES 202 5
48、04-16 V1.1.1 (2008-05) 117 XML Schema data type definition 7.1 Accuracy values Two accuracy values used in the three operations are defined in clause 7 of ES 202 504-9 3. The “requested accuracy“ is the desired accuracy for the terminal location that will be used to generate the address and the “acc
49、eptable accuracy” sets a lower bound on accuracy. 7.2 AddressInfo structure Data structure of location address composed of country, state, district, city, street, house number, additional information, and zip/postal code. Element name Element type Optional Description country xsd:string Yes The country is identified by the ISO 3166 4 code state xsd:string Yes National subdivision name (e.g. state, province) district xsd:string Yes District name city xsd:string Yes City or township name street xsd:string Ye Street name hous
