Oma TS MLP V3 - 2 20110719 A

Mobile Location Protocol 3.
2
Approved Version 3.2 19 Jul 2011
Open Mobile Alliance OMA-TS-MLP-V3_2-20110719-A
2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
[OMA-Template-Spec-20050101-I]
OMA-TS-MLP-V3_2-20051124-C
Page 2 (128)
Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the OMA IPR Declarations list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form. NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPRS REPRESENTED ON THE OMA IPR DECLARATIONS LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL. THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.
OMA-TS-MLP-V3_2-20051124-C
Page 3 (128)
Contents
1. 2. SCOPE ................................................................................................................................................................................ 7 REFERENCES .................................................................................................................................................................. 8 2.1 NORMATIVE REFERENCES .......................................................................................................................................... 8 2.2 INFORMATIVE REFERENCES ....................................................................................................................................... 8 3. TERMINOLOGY AND CONVENTIONS .................................................................................................................... 10 3.1 CONVENTIONS ........................................................................................................................................................... 10 3.2 DEFINITIONS .............................................................................................................................................................. 10 3.3 ABBREVIATIONS ........................................................................................................................................................ 11 4. INTRODUCTION ........................................................................................................................................................... 12 5. MOBILE LOCATION PROTOCOL............................................................................................................................. 13 5.1 OVERVIEW ................................................................................................................................................................. 13 5.1.1 MLP structure .................................................................................................................................................... 13 5.1.2 MLP extension mechanism ................................................................................................................................ 15 5.2 MOBILE LOCATION SERVICE DEFINITIONS ............................................................................................................. 16 5.2.1 Transport Protocol Layer Definitions ................................................................................................................ 16 5.2.2 Element Layer Definitions ................................................................................................................................. 17 5.2.3 Service Layer Definitions .................................................................................................................................. 27 5.3 ELEMENTS AND ATTRIBUTES IN DTD ....................................................................................................................... 53 5.3.1 add_info ............................................................................................................................................................. 53 5.3.2 alt ....................................................................................................................................................................... 54 5.3.3 alt_acc ................................................................................................................................................................ 54 5.3.4 alt_unc................................................................................................................................................................ 54 5.3.5 angle ................................................................................................................................................................... 55 5.3.6 angularUnit ........................................................................................................................................................ 56 5.3.7 Box ..................................................................................................................................................................... 56 5.3.8 cc ........................................................................................................................................................................ 57 5.3.9 cellid .................................................................................................................................................................. 57 5.3.10 change_area ....................................................................................................................................................... 57 5.3.11 CircularArcArea................................................................................................................................................. 59 5.3.12 CircularArea....................................................................................................................................................... 59 5.3.13 code .................................................................................................................................................................... 60 5.3.14 codeSpace .......................................................................................................................................................... 60 5.3.15 codeword............................................................................................................................................................ 60 5.3.16 distanceUnit ....................................................................................................................................................... 61 5.3.17 direction ............................................................................................................................................................. 61 5.3.18 duration .............................................................................................................................................................. 61 5.3.19 edition ................................................................................................................................................................ 62 5.3.20 EllipticalArea ..................................................................................................................................................... 62 5.3.21 eme_event .......................................................................................................................................................... 63 5.3.22 eme_pos ............................................................................................................................................................. 63 5.3.23 esrd ..................................................................................................................................................................... 64 5.3.24 esrk ..................................................................................................................................................................... 65 5.3.25 hor_acc ............................................................................................................................................................... 66 5.3.26 id ........................................................................................................................................................................ 66 5.3.27 imsi .................................................................................................................................................................... 66 5.3.28 inRadius ............................................................................................................................................................. 67 5.3.29 interval ............................................................................................................................................................... 67 5.3.30 lac....................................................................................................................................................................... 67 5.3.31 lcs_ref ................................................................................................................................................................ 68 5.3.32 lev_conf ............................................................................................................................................................. 68 5.3.33 LinearRing ......................................................................................................................................................... 68 5.3.34 LineString .......................................................................................................................................................... 69
OMA-TS-MLP-V3_2-20051124-C
Page 4 (128)
5.3.35 ll_acc .................................................................................................................................................................. 70 5.3.36 lmsi .................................................................................................................................................................... 71 5.3.37 loc_type .............................................................................................................................................................. 71 5.3.38 max_loc_age ...................................................................................................................................................... 72 5.3.39 mcc ..................................................................................................................................................................... 72 5.3.40 mnc .................................................................................................................................................................... 72 5.3.41 ms_action ........................................................................................................................................................... 73 5.3.42 msid.................................................................................................................................................................... 73 5.3.43 MultiLineString ................................................................................................................................................. 75 5.3.44 MultiPoint .......................................................................................................................................................... 75 5.3.45 MultiPolygons .................................................................................................................................................... 76 5.3.46 name_area .......................................................................................................................................................... 76 5.3.47 ndc...................................................................................................................................................................... 76 5.3.48 nmr ..................................................................................................................................................................... 77 5.3.49 no_of_reports ..................................................................................................................................................... 77 5.3.50 plmn ................................................................................................................................................................... 77 5.3.51 qos_not_met ....................................................................................................................................................... 77 5.3.52 radius.................................................................................................................................................................. 78 5.3.53 startAngle ........................................................................................................................................................... 78 5.3.54 stopAngle ........................................................................................................................................................... 78 5.3.55 Point ................................................................................................................................................................... 79 5.3.56 Polygon .............................................................................................................................................................. 79 5.3.57 prio ..................................................................................................................................................................... 80 5.3.58 pwd .................................................................................................................................................................... 80 5.3.59 outRadius ........................................................................................................................................................... 81 5.3.60 pos ...................................................................................................................................................................... 81 5.3.61 requestor............................................................................................................................................................. 81 5.3.62 req_id ................................................................................................................................................................. 82 5.3.63 resp_req.............................................................................................................................................................. 82 5.3.64 resp_timer .......................................................................................................................................................... 84 5.3.65 result .................................................................................................................................................................. 84 5.3.66 semiMajor .......................................................................................................................................................... 85 5.3.67 semiMinor .......................................................................................................................................................... 85 5.3.68 serviceid ............................................................................................................................................................. 86 5.3.69 requestmode ....................................................................................................................................................... 86 5.3.70 session ................................................................................................................................................................ 87 5.3.71 sessionid ............................................................................................................................................................. 87 5.3.72 speed .................................................................................................................................................................. 88 5.3.73 start_time ........................................................................................................................................................... 88 5.3.74 stop_time............................................................................................................................................................ 89 5.3.75 subclient ............................................................................................................................................................. 89 5.3.76 ta ........................................................................................................................................................................ 90 5.3.77 target_area.......................................................................................................................................................... 90 5.3.78 time .................................................................................................................................................................... 90 5.3.79 time_remaining .................................................................................................................................................. 91 5.3.80 trans_id .............................................................................................................................................................. 91 5.3.81 trl_pos ................................................................................................................................................................ 92 5.3.82 url ....................................................................................................................................................................... 93 5.3.83 vlrno ................................................................................................................................................................... 93 5.3.84 vmscno ............................................................................................................................................................... 94 5.3.85 X ........................................................................................................................................................................ 94 5.3.86 Y ........................................................................................................................................................................ 94 5.3.87 Z ......................................................................................................................................................................... 95 5.3.88 Service attributes................................................................................................................................................ 95 5.4 RESULT CODES .......................................................................................................................................................... 96 5.4.1 Result codes ....................................................................................................................................................... 96 5.5 ADAPTATION TO 3GPP LCS (INFORMATIVE) .......................................................................................................... 98
OMA-TS-MLP-V3_2-20051124-C
Page 5 (128)
5.5.1 Version mapping between 3GPP TS23.271 and this specification .................................................................... 98 5.5.2 The terminology mapping table with 3GPP LCS Specifications ....................................................................... 98 5.5.3 The corresponding terms used for the location procedures in 3GPP LCS Definition ........................................ 98 5.5.4 Error Mapping (Informative) ............................................................................................................................. 99 5.6 HTTP MAPPING ...................................................................................................................................................... 100 5.6.1 Location Services using HTTP ........................................................................................................................ 100 5.6.2 Request and Response Encapsulation .............................................................................................................. 101 5.7 GEOGRAPHIC INFORMATION .................................................................................................................................. 106 5.7.1 Coordinate Reference systems (Informative)................................................................................................... 106 5.7.2 Coordinate Reference System Transformations (Informative) ........................................................................ 108 5.7.3 Methodology for defining CRSs and transformations in this protocol (Informative) ...................................... 108 5.7.4 Supported coordinate systems and datum (Normative) ................................................................................... 108 5.7.5 Shapes representing a geographical position (Informative) ............................................................................. 108 APPENDIX A. CHANGE HISTORY (INFORMATIVE) ............................................................................................ 112 A.1 APPROVED VERSION HISTORY ............................................................................................................................... 112 APPENDIX B. STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) ................................................... 113 B.1 SCR FOR CLIENT .................................................................................................................................................... 113 B.1.1 SERVICE INITIATION DTD ........................................................................................................................................ 113 B.1.2 SERVICE RESULT DTD .............................................................................................................................................. 113 B.1.3 HEADER...................................................................................................................................................................... 114 B.1.4 STANDARD LOCATION IMMEDIATE REQUEST .......................................................................................................... 114 B.1.5 STANDARD LOCATION IMMEDIATE ANSWER ........................................................................................................... 114 B.1.6 STANDARD LOCATION IMMEDIATE REPORT ............................................................................................................ 114 B.1.7 EMERGENCY LOCATION IMMEDIATE REQUEST....................................................................................................... 114 B.1.8 EMERGENCY LOCATION IMMEDIATE ANSWER ........................................................................................................ 115 B.1.9 EMERGENCY LOCATION IMMEDIATE REPORT......................................................................................................... 115 B.1.10 STANDARD LOCATION REPORT .............................................................................................................................. 115 B.1.11 STANDARD LOCATION REPORT ANSWER ............................................................................................................... 115 B.1.12 EMERGENCY LOCATION REPORT ........................................................................................................................... 116 B.1.13 TRIGGERED LOCATION REPORTING REQUEST ...................................................................................................... 116 B.1.14 TRIGGERED LOCATION REPORTING ANSWER ....................................................................................................... 116 B.1.15 TRIGGERED LOCATION REPORT ............................................................................................................................. 116 B.1.16 TRIGGERED LOCATION REPORTING STOP REQUEST............................................................................................. 117 B.1.17 TRIGGERED LOCATION REPORTING STOP ANSWER .............................................................................................. 117 B.1.18 SUPPORT FOR IDENTITY ELEMENTS ....................................................................................................................... 117 B.1.19 SUPPORT FOR FUNCTION ELEMENTS ...................................................................................................................... 117 B.1.20 SUPPORT FOR LOCATION ELEMENTS ..................................................................................................................... 118 B.1.21 SUPPORT FOR RESULT ELEMENTS .......................................................................................................................... 118 B.1.22 SUPPORT FOR SHAPE ELEMENTS ............................................................................................................................ 118 B.1.23 SUPPORT FOR QUALITY OF POSITION ELEMENTS .................................................................................................. 119 B.1.24 SUPPORT FOR NETWORK PARAMETERS ELEMENTS .............................................................................................. 119 B.1.25 SUPPORT FOR CONTEXT ELEMENTS ....................................................................................................................... 120 B.1.26 SERVICE ATTRIBUTES .............................................................................................................................................. 120 B.1.27 TRANSPORT MECHANISMS....................................................................................................................................... 120 B.1.28 SERVICES ................................................................................................................................................................. 120 B.2 SCR FOR SERVER .................................................................................................................................................... 121 B.2.1 SERVICE INITIATION DTD ........................................................................................................................................ 121 B.2.2 SERVICE RESULT DTD .............................................................................................................................................. 121 B.2.3 HEADER...................................................................................................................................................................... 121 B.2.4 STANDARD LOCATION IMMEDIATE REQUEST .......................................................................................................... 122 B.2.5 STANDARD LOCATION IMMEDIATE ANSWER ........................................................................................................... 122 B.2.6 STANDARD LOCATION IMMEDIATE REPORT ............................................................................................................ 122 B.2.7 EMERGENCY LOCATION IMMEDIATE REQUEST....................................................................................................... 122 B.2.8 EMERGENCY LOCATION IMMEDIATE ANSWER ........................................................................................................ 123 B.2.9 EMERGENCY LOCATION IMMEDIATE REPORT......................................................................................................... 123 B.2.10 STANDARD LOCATION REPORT .............................................................................................................................. 123
OMA-TS-MLP-V3_2-20051124-C
Page 6 (128)
B.2.11 STANDARD LOCATION REPORT ANSWER ............................................................................................................... 123 B.2.12 EMERGENCY LOCATION REPORT ........................................................................................................................... 123 B.2.13 TRIGGERED LOCATION REPORTING REQUEST ...................................................................................................... 124 B.2.14 TRIGGERED LOCATION REPORTING ANSWER ....................................................................................................... 124 B.2.15 TRIGGERED LOCATION REPORT ............................................................................................................................. 124 B.2.16 TRIGGERED LOCATION REPORTING STOP REQUEST............................................................................................. 124 B.2.17 TRIGGERED LOCATION REPORTING STOP ANSWER .............................................................................................. 125 B.2.18 SUPPORT FOR IDENTITY ELEMENTS ....................................................................................................................... 125 B.2.19 SUPPORT FOR FUNCTION ELEMENTS ...................................................................................................................... 125 B.2.20 SUPPORT FOR LOCATION ELEMENTS ..................................................................................................................... 126 B.2.21 SUPPORT FOR RESULT ELEMENTS .......................................................................................................................... 126 B.2.22 SUPPORT FOR SHAPE ELEMENTS ............................................................................................................................ 126 B.2.23 SUPPORT FOR QUALITY OF POSITION ELEMENTS .................................................................................................. 127 B.2.24 SUPPORT FOR NETWORK PARAMETERS ELEMENTS .............................................................................................. 127 B.2.25 SUPPORT FOR CONTEXT ELEMENTS ....................................................................................................................... 127 B.2.26 SERVICE ATTRIBUTES .............................................................................................................................................. 128 B.2.27 TRANSPORT MECHANISMS....................................................................................................................................... 128 B.2.28 SERVICES ................................................................................................................................................................. 128
Figures
Figure 1: MLP in the context of the LCS Architecture ........................................................................................................ 13 Figure 2: MLP Structure ........................................................................................................................................................ 13 Figure 3: Message Flow for the Standard Location Immediate Service ............................................................................. 30 Figure 4: Message Flow for the Emergency Location Immediate Service .......................................................................... 35 Figure 5: Message flow for the Standard Location Reporting Service ............................................................................... 38 Figure 6: Message Flow for the Emergency Location Reporting Service ........................................................................... 41 Figure 7: Message Flow for the Triggered Location Reporting Service ............................................................................. 43 Figure 8: HTTP sequence for MLP request/response pairs ............................................................................................... 105 Figure 9: HTTP sequence for MLP reports ........................................................................................................................ 105 Figure 10: HTTP sequence for MLP Standard Location Reporting Service. .................................................................. 106 Figure 11: HTTP sequence for the General Error Message .............................................................................................. 106 Figure 12: Ellipsoid Coordinates .......................................................................................................................................... 107 Figure 13: Ellipsoid point with uncertainty circle .............................................................................................................. 109 Figure 14: Ellipsoid point with uncertainty ellipse ............................................................................................................. 110 Figure 15: Ellipsoid point with uncertainty arc .................................................................................................................. 110
OMA-TS-MLP-V3_2-20051124-C
Page 7 (128)
1. Scope
The Mobile Location Protocol (MLP) is an application-level protocol for getting the position of mobile stations (mobile phones, wireless personal digital assistants, etc.) independent of underlying network technology, i.e. independent of location derivation technology and bearer as described in [MLS AD]. The MLP serves as the interface between a Location Server and a MLS Client. This specification defines the core set of operations that a Location Server should be able to perform.
OMA-TS-MLP-V3_2-20051124-C
Page 8 (128)
2. References
2.1 Normative References
OMA Mobile Location Service Architecture. Open Mobile Alliance. OMA-AD-MLS-V1_0, URL: http://www.openmobilealliance.org/ [IOPPROC] [22.071] [23.271] [RFC2119] [RFC2616] [RFC2246] [XML-1.0] [IANA] [ASCII] OMA Interoperability Policy and Process", Version 1.10, Open Mobile AllianceTM. OMAIOP-Process-V1_10, URL: http://www.openmobilealliance.org/ 3GPP TS 22.071 Release 6: "Location Services (LCS); Service description, Stage 1". URL: http://www.3gpp.org/ftp/Specs/latest/Rel-6/22_series/ 3GPP TS 23.271 Release 6: "Functional stage 2 description of LCS" URL: http://www.3gpp.org/ftp/Specs/latest/Rel-6/23_series/ Key words for use in RFCs to Indicate Requirement Levels, IETF, S. Bradner. March 1997. URL: http://www.ietf.org/rfc/rfc2119.txt "Hypertext Transfer Protocol HTTP/1.1", IETF, R. Fielding, et al, June 1999. URL: http://www.ietf.org/rfc/rfc2616.txt "The TLS Protocol Version 1.0", IETF, T. Dierks, et al, January 1999. URL: http://www.ietf.org/rfc/rfc2246.txt "Extensible Markup Language (XML) 1.0" W3C Recommendation: URL: http://www.w3.org/TR/2000/REC-xml-20001006 Internet Assigned Numbers Authority (IANA) URL: http://www.iana.org/ US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986. [MLS AD]
2.2
[23.032] [04.18]
Informative References
3GPP TS 23.032: " Universal Geographical Area Description (GAD)" URL:http://www.3gpp.org/ftp/Specs/latest/Rel-5/23_series/ GSM 04.18: " Technical Specification Group GSM/EDGE Radio Access Network; Mobile radio interface layer 3 specification, Radio Resource Control Protocol" URL:http://www.3gpp.org/ftp/Specs/latest/R1999/04_series/ 3GPP TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". URL:http://www.3gpp.org/ftp/Specs/latest/Rel6/29_series/ 3GPP TS 23.003: "Numbering, Addressing and Identification" URL:http://www.3gpp.org/ftp/Specs/latest/Rel-6/23_series/ ITU-T E.164: "The international public telecommunication numbering plan TR-45 J-STD-036 "Enhanced Wireless 9-1-1 Phase 2 Document" IS-41D: " Cellular Radiotelecommunications Intersystem Operations", June 1997 OpenGIS Consortium Abstract Specification Topic 2: 01-063R2 URL: http://www.opengis.org/techno/abstract/02-102.pdf. OpenGIS Consortium Recommendation Paper 01-014r5: Recommended Definition Data for Coordinate Reference Systems and Coordinate Transformations URL: http://www.opengis.org/techno/discussions/01-014r5.pdf
[29.002]
[23.003] [E164] [J-STD-036] [IS-41D] [AST] [CRS]
OMA-TS-MLP-V3_2-20051124-C
Page 9 (128)
[GML]
OpenGIS Consortium Implementation Specification: Geography Markup Language V 2.0 URL: http://www.opengis.net/gml/01-029/GML2.html OpenGIS Consortium Abstract Specification Topic 1 Feature Geometry : 010101 URL: http://www.opengis.org/techno/abstract/01-101.pdf. RFC 796: "Address mapping", IETF, J. Postel, September 1981, URL: http://www.ietf.org/rfc/rfc796.txt RFC 3513: "Internet Protocol Version 6 (IPv6) Addressing Architecture", IETF, R. Hinden and S. Deering, April 2003, URL: http://www.ietf.org/rfc/rfc3513.txt 3GPP TS 05.10, "Radio subsystem synchronization", URL:http://www.3gpp.org/ftp/Specs/latest/R1999/05_series/ ITU CCIR Recommendation "ITU-R-TF.460-4"
[GEO] [RFC796] [RFC3513] [05.10] [UTC]
OMA-TS-MLP-V3_2-20051124-C
Page 10 (128)
3. Terminology and Conventions

3.1 Conventions
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated to be informative.
Notational Conventions and Generic Grammar
The following rules are used throughout this specification to describe basic parsing constructs. ANSI X3.4-1986 defines the US-ASCII coded character set, see [ASCII] CR LF SP = <US-ASCII CR, carriage return (13)> = <US-ASCII LF, linefeed (10)> = <US-ASCII SP, space (32)>
A set of characters enclosed in brackets ([...]) is a one-character expression that matches any of the characters in that set, e.g., "[lcs]" matches either an "l", "c", or "s". A range of characters is indicated with a dash, e.g., "[a-z]" matches any lower-case letter. The one-character expression can be followed by an interval operator, for example [a-zA-Z]{min,max} in which case the one-character expression is repeated at least min and at most max times, e.g., "[a-zA-Z]{2,4}" matches for example the strings "at", "Good", and "biG".
DTD Syntax Notation
The table below describes the special characters and separators used in the DTDs defining the different services.
Character + * ? (...) | ,
Meaning One or more occurrence Zero or more occurrences Optional A group of expressions to be matched together OR...as in, "this or that" Strictly ordered. Like an AND
3.2
Le
Definitions
Reference point between MLS Client and Location Server. See also [23.271] Software and/or hardware entity offering location capabilities. The entity being located. Parameter in GSM network used by the MS to advance its timings of transmissions to the Base Station so as to compensate for propagation delay. This parameter can also be used to estimate the distance between the MS and the Base Station.
Location Server Target Timing Advance
OMA-TS-MLP-V3_2-20051124-C
Page 11 (128)
3.3
A-GPS ANSI DTD E-OTD GMLC GMT GPS HTTP HTTPS LCS MLC MLP MPC MS MSID MSISDN OTDOA SSL TLS U-TDOA URI URL UTM WAP WGS XML
Abbreviations
Assisted GPS American National Standards Institute Document Type Definition Enhanced Observed Time Difference (E-OTD) Gateway Mobile Location Center Greenwich Mean Time Global Positioning System Hypertext Transfer Protocol HTTP Secure Location Services Mobile Location Center Mobile Location Protocol Mobile Positioning Center Mobile Station Mobile Station Identifier Mobile Station ISDN Observed Time Difference of Arrival Secure Socket Layer Transport Layer Security Uplink Time Difference of Arrival Uniform Resource Identifier Uniform Resource Locator Universal Transverse Mercator Wireless Application Protocol World Geodetic System Extensible Markup Language
OMA-TS-MLP-V3_2-20051124-C
Page 12 (128)
4. Introduction
The Mobile Location Protocol (MLP) is an application-level protocol for getting the position of mobile stations (mobile phones, wireless personal digital assistants, etc.) independent of underlying network technology, i.e. independent of location derivation technology and bearer. The MLP serves as the interface between a Location Server and a MLS (Mobile Location Service) Client. This specification defines the core set of operations that a Location Server should be able to perform. The purpose of this specification is to specify the detailed technical specification of the interface between a Location Server and a MLS Client described in [MLS AD]. In the 3GPP context, this specification will be an instantiation of the detailed technical specifications for the Le reference point as defined in [23.271].
OMA-TS-MLP-V3_2-20051124-C
Page 13 (128)
5. Mobile Location Protocol

5.1 Overview
The Mobile Location Protocol (MLP) is an application-level protocol for querying the position of mobile stations independent of underlying network technology. The MLP serves as the interface between a Location Server and a locationbased application (cf. Figure 1).
Wireless Network
request (MLP)
Locationbased application
response (MLP)
Location Server
Figure 1: MLP in the context of the LCS Architecture Possible realisations of a Location Server are the GMLC, which is the location server defined in GSM and UMTS, and the MPC, which is defined in ANSI standards. Since the location server should be seen as a logical entity, other implementations are possible. In the scenarios (except where explicitly mentioned) an LCS client initiates the dialogue by sending a query to the location server and the server responds to the query.
5.1.1
MLP structure
Different devices may support different means of communication. A ubiquitous protocol for location services should support different transport mechanisms.
Basic MLP Services

SLIS ELI SLRS ELRS TLRS SLI ELIS
Advanced MLP Services Svc1 Svc2 Svcn

Advanced Common Elements Advanced Common Elements
Other MLP Services
Service Layer
Basic Basic Common Elements Element Common s
Element Layer
Core Location Elements
Transport Layer
Transport Layer Mapping (HTTP, WSP, SOAP, )
Figure 2: MLP Structure In MLP, the transport protocol is separated from the XML content. Figure 2 shows a layered view of MLP.
OMA-TS-MLP-V3_2-20051124-C
Page 14 (128)
On the lowest level, the transport protocol defines how XML content is transported. Possible MLP transport protocols include HTTP, WSP, SOAP and others. The Element Layer defines all common elements used by the services in the service layer. Currently MLP defines the following set of DTDs making up the element layer of MLP: MLP_ID.DTD MLP_FUNC.DTD MLP_LOC.DTD MLP_RES.DTD MLP_SHAPE.DTD MLP_QOP.DTD MLP_GSM_NET.DTD MLP_CTXT.DTD Identify Element Definitions Function Element Definitions Location Element Definitions Result Element Definitions Shape Element Definitions Quality of Position Element Definitions GSM Network Parameters Element Definitions Context Element Definitions
The Service Layer defines the actual services offered by the MLP framework. Basic MLP Services are based on location services defined by 3GPP, and are defined by this specification. The "Advanced MLP Services" and "Other MLP Services" are additional services that either will be specified in other specifications or are specified by other fora that conform to the MLP framework. Note: The boxes representing services in the Service Layer may contain more than one message. E.g. SLIS (Standard Location Immediate Service) consists of slir (Standard Location Immediate Request), slia (Standard Location Immediate Answer) and slirep (Standard Location Immediate Report) messages. Messages for each service are listed in the table below.
The Service Layer is divided into two sub-layers. The topmost defines the services mentioned in the previous paragraph. The lower sub-layer holds common elements, which are specific for that group of services. If an element is common to more than one group of services then that element is defined in the element layer. The present specification specifies no element sublayer. There are a number of different possible types of location services. Each implementation of location server can select which services it wants/needs to support. The services are described in the table below.
Service Standard Location Immediate Service
Emergency Location Immediate Service
Description This is a standard query service with support for a large set of parameters. This service is used when a (single) location response is required immediately (within a set time) or the request may be served by several asynchronous location responses (until a predefined timeout limit is reached). This service consists of the following messages: - Standard Location Immediate Request - Standard Location Immediate Answer - Standard Location Immediate Report This is a service used especially for querying of the location of a mobile subscriber that has initiated an emergency call. The response to this service is required immediately (within a set time) or the request may be served by several asynchronous location responses. This service consists of the following messages: - Emergency Location Immediate Request - Emergency Location Immediate Answer - Emergency Location Immediate Report
OMA-TS-MLP-V3_2-20051124-C
Page 15 (128)
Standard Location Reporting Service
Emergency Location Reporting Service
Triggered Location Reporting Service
This is a service that is used when a mobile subscriber wants an LCS Client to receive the MS location. The position is sent to the LCS Client from the location server. Which LCS application and its address are specified by the MS or defined in the location server. This service consists of the following message: - Standard Location Report - Standard Location Report Answer This is a service that is used when the wireless network automatically initiates the positioning at an emergency call. The position and related data is then sent to the emergency application from the location server. Which LCS application and its address are defined in the location server. This service consists of the following message: - Emergency Location Report This is a service used when the mobile subscribers location should be reported at a specific time interval or on the occurrence of a specific event. This service consists of the following messages: - Triggered Location Reporting Request - Triggered Location Reporting Answer - Triggered Location Report - Triggered Location Reporting Stop Request - Triggered Location Reporting Stop Answer
5.1.2
MLP extension mechanism
The MLP specification has been designed with extensibility in mind. Examples of design principles employed to achieve this include: Separate DTDs for definitions that are common to all messages, e.g. client address and shapes, so they can be re-used. A message extension mechanism allowing the addition of new messages (specific for the HTTP mapping). This mechanism works by specifying an entity parameter, '%extension;', referring to an extension DTD. The extension DTD MUST contain another entity parameter, '%extension.message', containing the definition of the extension as a string together with the actual parameters being added A parameter extension mechanism allowing the addition of new parameters to existing messages. This mechanism works by specifying an entity parameter, '%extension;', referring to an extension DTD. The extension DTD MUST contain another entity parameter, %extension.param, containing the definition of the extension as a string together with the actual messages being added. Each extension parameters SHOULD have a vendor specific prefix in order to guarantee their uniqueness. Element names defined in MLP SHALL NOT be reused with a different definition.
In order to use the extension, the extension DTD has to be explicitly referenced in the XML document. The Location Server SHOULD ignore any extension that is not recognized and process the message as if the extension is not available. Example 1: Message extension
 <!ENTITY <!ELEMENT <!ATTLIST % extension.message truckco_message truckco_message ver CDATA "| truckco_message"> (truckco_data)> #FIXED "x.y.z">
OMA-TS-MLP-V3_2-20051124-C
Page 16 (128)
<?xml version = "1.0" ?> <!DOCTYPE svc_init SYSTEM "MLP_SVC_INIT_320.DTD " [ <!ENTITY % extension SYSTEM "http://www.truckco.com/truckco_MLP_extension.dtd"> %extension; ]> <svc_init ver="3.2.0"> <hdr ver="3.2.0"> ... </hdr> <truckco_message ver="x.y.z"> <truckco_data> ... </truckco_data> </truckco_message> </svc_init>
Example 2: Parameter extension (note that trucko_codeword is given with a vendor specific prefix as the element codeword has a different definition than in MLP)
 <!ENTITY <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST % extension.param trucko_extension truck_no trucko_codeword trucko_codeword type ( long | short) ", truckco_extension"> (truck_no, trucko_codeword)> (#PCDATA)> (#PCDATA)> #REQUIRED>
<?xml version = "1.0" ?> <!DOCTYPE svc_init SYSTEM "MLP_SVC_INIT_320.DTD" [ <!ENTITY % extension SYSTEM "http://www.truckco.com/truckco_MLP_extension.dtd"> %extension; ]> <svc_init ver="3.2.0"> <hdr ver="3.2.0"> ... </hdr> <slir ver="3.2.0"> ... <truckco_extension> <truck_no>KLM4583</truck_no> <trucko_codeword type=short>6547</trucko_codeword> </truckco_extension> </slir> </svc_init>
5.2
5.2.1
Mobile Location Service Definitions

Transport Protocol Layer Definitions
MLP can be implemented using various transport mechanism as stated in section 3.2. The following mappings are specified for MLP:
Mapping HTTP
Section 5.6 HTTP Mapping
OMA-TS-MLP-V3_2-20051124-C
Page 17 (128)
5.2.2
5.2.2.1
Element Layer Definitions

Identity Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_xxx PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_xxx> ... </svc_xxx> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT <!ATTLIST msid msid type (MSISDN | IMSI | IMEI | MIN | MDN | EME_MSID | ASID | OPE_ID | IPV4 | IPV6 | SESSID | SIP_URI |TEL_URL) enc (ASC | CRP) msid_range msids (#PCDATA)> "MSISDN"
<!ELEMENT <!ELEMENT
<!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ELEMENT
codeword esrd esrd type (NA) esrk esrk type (NA) session session type (APN | DIAL) start_msid stop_msid trans_id
"ASC"> (start_msid, stop_msid)> (((msid, codeword?, session?, trans_id?) | (msid_range, codeword*))+)> (#PCDATA)> (#PCDATA)> "NA"> (#PCDATA)> "NA"> (#PCDATA)> #REQUIRED> (msid)> (msid)> (#PCDATA)>
Note: same.
The type attributes of the msid elements that form the start_msid and stop_msid elements MUST be the
OMA-TS-MLP-V3_2-20051124-C
Page 18 (128)
5.2.2.2
Function Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ -->
<!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST
<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ELEMENT
eme_event eme_event eme_trigger (EME_ORG | EME_REL) tlrr_event ms_action ms_action type (MS_AVAIL) change_area change_area type (MS_ENTERING | MS_LEAVING | MS_WITHIN_AREA) loc_estimates (TRUE | FALSE) target_area no_of_reports name_area plmn interval loc_type loc_type type (CURRENT | LAST |CURRENT_OR_LAST | LAST_OR_CURRENT | INITIAL) prio prio type (NORMAL | HIGH) pushaddr req_id start_time start_time utc_off CDATA stop_time stop_time utc_off CDATA duration url time_remaining
(eme_pos+)> #REQUIRED> (ms_action | change_area)> EMPTY> #REQUIRED> (target_area, no_of_reports?)> #REQUIRED #REQUIRED> (shape | cc | plmn | name_area)> (#PCDATA)> (#PCDATA)> (mcc, mnc)> (#PCDATA)> EMPTY> "CURRENT"> EMPTY> "NORMAL"> (url, id?, pwd?)> (#PCDATA)> (#PCDATA)> "0000"> (#PCDATA)> "0000"> (#PCDATA)> (#PCDATA)> (#PCDATA)>
OMA-TS-MLP-V3_2-20051124-C
Page 19 (128)
<!ELEMENT
lcs_ref
(#PCDATA)>
OMA-TS-MLP-V3_2-20051124-C
Page 20 (128)
5.2.2.3
Location Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_xxx PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_xxx> ... </svc_xxx> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ -->
<!ELEMENT <!ATTLIST
pos pos pos_method (CELL | OTDOA | GPS | A-GPS | E-OTD | U-TDOA | AFLT | EFLT | UNKNOWN | OTHER) eme_pos eme_pos pos_method (CELL | OTDOA | GPS | | U-TDOA | AFLT | EFLT | UNKNOWN trl_pos trl_pos trl_trigger (PERIODIC | MS_AVAIL pos_method (CELL | OTDOA | GPS | | U-TDOA | AFLT | EFLT | UNKNOWN pd
(msid, (pd | poserr), gsm_net_param?, trans_id?)> #IMPLIED> (msid, (pd | poserr), esrd?, esrk?, trans_id?)> #IMPLIED> (msid, (pd | poserr | time))> | CHANGE_AREA) A-GPS | E-OTD | OTHER) #REQUIRED #IMPLIED> (time, shape, (alt, alt_unc?)?, speed?, direction?, lev_conf?, qos_not_met?)> (result, add_info?, time)> (#PCDATA)> "0000"> (#PCDATA)> (#PCDATA)>
<!ELEMENT <!ATTLIST
A-GPS | E-OTD | OTHER)
<!ELEMENT <!ATTLIST
<!ELEMENT
<!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT
poserr time time utc_off CDATA alt alt_unc
<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT
qos_not_met direction speed lev_conf geo_info CoordinateReferenceSystem Identifier code codeSpace
EMPTY> (#PCDATA)> (#PCDATA)> (#PCDATA)> (CoordinateReferenceSystem)> (Identifier)> (code, codeSpace, edition)> (#PCDATA)> (#PCDATA)>
OMA-TS-MLP-V3_2-20051124-C
Page 21 (128)
<!ELEMENT <!ELEMENT
edition service_coverage
(#PCDATA)> ((cc, ndc*)+)> SYSTEM "MLP_RES_300.DTD">
<!ENTITY % mlp_res.dtd %mlp_res.dtd;
OMA-TS-MLP-V3_2-20051124-C
Page 22 (128)
Examples of geo_info encoding. The encoding for WGS84 is:

<CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem>
The encoding for the Transverse Mercator coordinate system based on the OSGB1936 is:
<CoordinateReferenceSystem> <Identifier> <code>27700</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem>
Note that the GML V2.1.1 Implementation Specification is limited to use of only well-known CRSs, so this XML is currently abbreviated by a single attribute name and value: srsName=http://www.opengis.net/gml/srs/epsg.xml#4326 Note also that GML uses crsName instead of srsName.
5.2.2.4
Result Element Definitions
 <!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT <!ELEMENT <!ATTLIST add_info result result resid CDATA (#PCDATA)> (#PCDATA)> #REQUIRED>
OMA-TS-MLP-V3_2-20051124-C
Page 23 (128)
5.2.2.5
Shape Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT shape (Point | LineString | Polygon | Box | CircularArea | CircularArcArea | EllipticalArea | MultiLineString | MultiPoint | MultiPolygon| LinearRing)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (X, Y?, Z?)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (coord)> #IMPLIED #IMPLIED> (coord, coord+)> #IMPLIED #IMPLIED> (coord, coord)> #IMPLIED #IMPLIED> (coord, coord, coord, coord*)> #IMPLIED #IMPLIED> (outerBoundaryIs, innerBoundaryIs*)> #IMPLIED #IMPLIED> (LinearRing)>
<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST
distanceUnit angularUnit angle coord X Y Z Point Point gid ID srsName CDATA LineString LineString gid ID srsName CDATA Box Box gid ID srsName CDATA LinearRing LinearRing gid ID srsName CDATA Polygon Polygon gid ID srsName CDATA outerBoundaryIs
<!ELEMENT
OMA-TS-MLP-V3_2-20051124-C
Page 24 (128)
<!ELEMENT <!ELEMENT
innerBoundaryIs CircularArcArea
(LinearRing)> (coord, inRadius, outRadius, startAngle, stopAngle, angularUnit?, distanceUnit?)> #IMPLIED #IMPLIED> (coord, radius, distanceUnit?)> #IMPLIED #IMPLIED> (coord, angle, semiMajor, semiMinor, angularUnit?, distanceUnit?)> #IMPLIED #IMPLIED> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (LineString+)> #IMPLIED #IMPLIED> (Point+)> #IMPLIED #IMPLIED> ((Polygon| Box | CircularArea | CircularArcArea | EllipticalArea)+)> #IMPLIED #IMPLIED>
<!ATTLIST
<!ELEMENT <!ATTLIST
<!ELEMENT
CircularArcArea gid ID srsName CDATA CircularArea CircularArea gid ID srsName CDATA EllipticalArea
<!ATTLIST
<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST
<!ELEMENT <!ATTLIST
<!ELEMENT
EllipticalArea gid ID srsName CDATA inRadius outRadius radius semiMajor semiMinor startAngle stopAngle MultiLineString MultiLineString gid ID srsName CDATA MultiPoint MultiPoint gid ID srsName CDATA MultiPolygon
<!ATTLIST
MultiPolygon gid ID srsName CDATA
Note also that GML uses crsName instead of srsName.
OMA-TS-MLP-V3_2-20051124-C
Page 25 (128)
5.2.2.6
Quality of Position Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT eqop (resp_req?, resp_timer?, (ll_acc | hor_acc)?, alt_acc?, max_loc_age?)> ((ll_acc | hor_acc)?, alt_acc?)> (#PCDATA)> #IMPLIED> (#PCDATA)> #IMPLIED> (#PCDATA)> #IMPLIED> (#PCDATA)> EMPTY> "DELAY_TOL"> (#PCDATA)>
<!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT
qop ll_acc ll_acc qos_class (ASSURED | BEST_EFFORT) hor_acc hor_acc qos_class (ASSURED | BEST_EFFORT) alt_acc alt_acc qos_class (ASSURED | BEST_EFFORT) max_loc_age resp_req resp_req type (NO_DELAY | LOW_DELAY | DELAY_TOL) resp_timer
OMA-TS-MLP-V3_2-20051124-C
Page 26 (128)
5.2.2.7
Network Parameters Element Definitions
 <!-MLP V3.1 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_xxx PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_xxx> ... </svc_xxx> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT gsm_net_param cgi neid vmscid vlrid nmr mcc mnc ndc cc vmscno vlrno lac cellid ta lmsi imsi (cgi?, neid?, nmr?, ta?, lmsi?, imsi?)> (mcc, mnc, lac, cellid)> (vlrid | (vmscid, vlrid?))> (cc?, ndc?, vmscno)> (cc?, ndc?, vlrno)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)>
Note: The above table corresponds to GSM specific network element identifiers and network parameters. This information may be considered operator sensitive
OMA-TS-MLP-V3_2-20051124-C
Page 27 (128)
5.2.2.8
Context Element Definitions
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_xxx PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_xxx> ... </svc_xxx> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT client <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST sessionid id requestor requestor type (MSISDN | NAME | E-MAIL | URL | SIPURL | IMS | MDN | ASID) pwd serviceid requestmode requestmode type (ACTIVE | PASSIVE) subclient subclient last_client (YES | NO)
(id, pwd?, serviceid?, requestmode?)> (#PCDATA)> (#PCDATA)> (id, serviceid?)> "MSISDN"> (#PCDATA)> (#PCDATA)> EMPTY> "PASSIVE"> (id, pwd?, serviceid?)> "NO">
<!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST
5.2.3
Service Layer Definitions
Each message MAY have a header part and SHALL have a body part. The body part consists of the request/answer and is described in sections 5.2.3.2- 5.2.3.7. The context or header part consists of the information that identifies the client as defined in section 5.2.3.1.
5.2.3.1
Header Components
The subclient elements (if present) identify the ASPs, resellers and portals in the chain of service providers between the network and the end-user. The distinction between client and subclient elements is that the client element identifies the provider of the service that the Location Server has the main relationship with, whereas the subclient elements identify the chain of other service providers up to the end-user. The final service provider in the chain is identified as such (last_client="YES"). The requestor is indicates the initiator of the location request, so in this context besides an ASP it could also be an MS subscriber who is asking the position of another target MS. The identity of the requestor may be an MSISDN or any other identifier identifying the initiator of the location request.
OMA-TS-MLP-V3_2-20051124-C
Page 28 (128)
The serviceid element can be present in client, subclient and requestor elements. If the Location Server supports serviceid element for privacy checking procedure it SHALL use the serviceid element received in the client element. The Location Server MAY check that all serviceid element received in a location request are consistent and MAY reject a request if not. The sessionid element is used to represent the current session between the LCS Client and the Location Server. It MAY be used to replace the id and pwd elements, used in the context by the LCS Client to "login" to the Location Server, for the transactions that make up a session. For the first transaction of the session the LCS Client SHALL "login" as usual. The Location Server MAY optionally return the sessionid in the response to this first transaction. If the Location Server does not return a sessionid the LCS Client SHALL continue to "login" for subsequent transactions. The LCS Client MAY ignore the sessionid if desired and continue to "login" for subsequent transactions. The Location Server will decide the policy to be used to determine how the sessionid will be created and maintained. For example, the Location Server may determine the session as being just the transactions pertaining to a single service/MSID combination this being restrictive and hence secure whilst still being useable, or the Location Server may allow the session to apply to a number of transactions between the Location Server and LCS Client. The Location Server may also allow the sessionid to be used for a particular period of time. The Location Server may also decide to return a different sessionid on each response, which the LCS Client will then use on the next transaction of the session. The sessionid cannot be used instead of the req_id as this latter id refers to a set of reports that have been requested to be delivered from the Location Server to the LCS Client and do not form part of an existing LCS Client to Location Server connection. These reports are delivered by the Location Server "logging in" to the LCS Client for each delivery and the use of a sessionid, would allow the security of the LCS Client to be breached.
5.2.3.1.1
Header DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_xxx PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_xxx> ... </svc_xxx> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT <!ATTLIST hdr hdr ver CDATA ((sessionid | (client , sessionid?)), subclient*, requestor?)> #FIXED "3.2.0">
Example 1: ASP as Initiator

<hdr ver="3.2.0"> <client> <id>theasp</id> <pwd>thepwd</pwd> <serviceid>0005</serviceid> <requestmode type="PASSIVE"/> </client> <subclient last_client="YES">
OMA-TS-MLP-V3_2-20051124-C
Page 29 (128)
<id>thelastasp</id> <serviceid>0005</serviceid> </subclient> <requestor> <id>theoriginalasp</id> <serviceid>0005</serviceid> </requestor> </hdr>
OMA-TS-MLP-V3_2-20051124-C
Page 30 (128)
Example 2: MS as Initiator
<hdr ver="3.2.0"> <client> <id>theasp</id> <pwd>thepwd</pwd> <serviceid>0005</serviceid> <requestmode type="ACTIVE"/> </client> <requestor> <id>461018765710</id> </requestor> </hdr>
5.2.3.2
Standard Location Immediate Service
This is a standard service for requesting the location of one or more Mobile Subscribers. The service is used when a location response is required immediately (within a set time). When a lot of positioning reports are requested, it may take an unacceptably long time to get all the responses from the network. If the Location Server supports it the LCS Client can define how to receive the location responses, either at the time of the response to the request, or individually using one or more connections initiated by the Location Server. The extended service supports a number of different formats for describing the location of the mobile subscriber. It has also support for requesting a certain Quality of Service, Type of location and priority. The service consists of the following messages: Standard Location Immediate Request Standard Location Immediate Answer Standard Location Immediate Report
The Standard Location Immediate Service SHALL consist of a Standard Location Immediate Request followed by one Standard Location Immediate Answer and zero, one or more OPTIONAL Standard Location Immediate Reports. The following message flow as depicted in Figure 3 encapsulates this service:
LCS Client standard location immediate request Location Server
standard location immediate answer
standard location immediate report
Figure 3: Message Flow for the Standard Location Immediate Service Note: Multiple Standard Location Immediate Reports can occur when the location information for multiple targets was requested and the results are reported back to the client in individual reports. An individual report may contain the result of one or more targets.
If (needed)
OMA-TS-MLP-V3_2-20051124-C
Page 31 (128)
5.2.3.2.1
Standard Location Immediate Request DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT % extension.param slir ""> ((msids | (msid, codeword?, gsm_net_param, trans_id?)+), eqop?, geo_info?, loc_type?, prio?, pushaddr?, service_coverage? %extension.param;)> #FIXED "3.2.0" "SYNC">
<!ATTLIST
slir ver CDATA res_type (SYNC | ASYNC)
Example
<slir ver="3.2.0" res_type="SYNC"> <msids> <msid type="IPV4">93.10.0.250</msid> <msid_range> <start_msid> <msid>461018765710</msid> </start_msid> <stop_msid> <msid>461018765712</msid> </stop_msid> </msid_range> <msid type="ASID">441728922342</msid> <msid_range> <start_msid> <msid>461018765720</msid> </start_msid> <stop_msid> <msid>461018765728</msid> </stop_msid> </msid_range> </msids> <eqop> <resp_req type="LOW_DELAY" /> <hor_acc>1000</hor_acc> </eqop> <geo_info> <CoordinateReferenceSystem> <Identifier>
OMA-TS-MLP-V3_2-20051124-C
Page 32 (128)
<code>4004</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <loc_type type="CURRENT_OR_LAST" /> <prio type="HIGH" /> </slir>
5.2.3.2.2
Standard Location Immediate Answer DTD
 <!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param slia slia ver CDATA ""> ((pos+ | req_id | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">
Example 1: Successful positioning of multiple subscribers

<slia ver="3.0.0" > <pos> <msid>461011334411</msid> <pd> <time utc_off="+0200">20020623134453</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 16 28.308N</X> <Y>45 15 33.444E</Y> </coord> <radius>240</radius> </CircularArea> </shape> </pd> </pos> <pos> <msid>461018765710</msid> <pd> <time utc_off="+0300">20020623134454</time>
OMA-TS-MLP-V3_2-20051124-C
Page 33 (128)
<shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 12 28.296N</X> <Y>86 56 33.864E</Y> </coord> <radius>570</radius> </CircularArea> </shape> </pd> </pos> <pos> <msid>461018765711</msid> <pd> <time utc_off="+0300">20020623110205</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>78 12 34.308N</X> <Y>76 22 2.82E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </pos> <pos> <msid>461018765712</msid> <poserr> <result resid="10">QOP NOT ATTAINABLE</result> <time>20020623134454</time> </poserr> </pos> </slia>
Example 2: Service not supported

<slia ver="3.0.0" > <result resid="108">SERVICE NOT SUPPORTED</result> <add_info>'slir' is not supported by the location server</add_info> </slia>
5.2.3.2.3
Standard Location Immediate Report DTD

OMA-TS-MLP-V3_2-20051124-C
Page 34 (128)
<!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param slirep slirep ver CDATA ""> (req_id, pos+ %extension.param;)> #FIXED "3.0.0">
Example
<slirep ver="3.0.0"> <req_id>25267</req_id> <pos> <msid type="IPV6">10:A1:45::23:B7:89</msid> <pd> <time utc_off="+0300">20020813010423</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>35 03 28.244N</X> <Y>135 47 08.711E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </pos> </slirep>
5.2.3.3
Emergency Location Immediate Service
The emergency location immediate service is used to retrieve the position of a mobile subscriber that is involved in an emergency call or have initiated an emergency service in some other way. When there is a chance that one location fix may block a location fix which takes a shorter time (eg A-GPS fix and a Cell-ID based fix) then if the Location Server supports it the LCS Client can define how to receive the location responses individually using one or more connections initiated by the Location Server. The service consists of the following messages: Emergency Location Immediate Request Emergency Location Immediate Answer Emergency Location Immediate Report
OMA-TS-MLP-V3_2-20051124-C
Page 35 (128)
The Emergency Location Immediate Service SHALL consist of a Emergency Location Immediate Request followed by one Emergency Location Immediate Answer and zero, one or more OPTIONAL Emergency Location Immediate Reports. The following message flow as depicted in Figure 4 encapsulates this service:
LCS Client emergency location immediate request Location Server
emergency location immediate answer
emergency location immediate report
Figure 4: Message Flow for the Emergency Location Immediate Service Note: Multiple Emergency Location Immediate Reports can occur when the location information for multiple targets was requested and the results are reported back to the client in individual reports. An individual report may contain the result of one or more targets.
If (needed)
5.2.3.3.1
Emergency Location Immediate Request DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param eme_lir eme_lir ver CDATA res_type (SYNC | ASYNC) ""> ((msids | (msid, gsm_net_param, trans_id?, esrd?, esrk?)+), eqop?, geo_info?, loc_type? , pushaddr? %extension.param;)> #FIXED "3.2.0" "SYNC">
OMA-TS-MLP-V3_2-20051124-C
Page 36 (128)
Example 1
<eme_lir ver="3.2.0"> <msids> <msid type="EME_MSID">520002-51-431172-6-06</msid> </msids> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4325</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <loc_type type="CURRENT_OR_LAST" /> </eme_lir>
Example 2
<eme_lir ver="3.2.0" res_type=ASYNC> <msids> <msid type="EME_MSID">520002-51-431172-6-06</msid> </msids> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <loc_type type="CURRENT_OR_LAST" /> <pushaddr> <url>http://location.application.com</url> </pushaddr> </eme_lir>
5.2.3.3.2
Emergency Location Immediate Answer DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ -->
OMA-TS-MLP-V3_2-20051124-C
Page 37 (128)
<!ENTITY <!ELEMENT <!ATTLIST
% extension.param eme_lia eme_lia ver CDATA
""> ((eme_pos+ | req_id | (result, add_info?)) %extension.param;)> #FIXED "3.2.0">
Example
<eme_lia ver="3.2.0"> <eme_pos> <msid type="EME_MSID">520002-51-431172-6-06</msid> <pd> <time utc_off="+0300">20020623134453</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 24 43.53N</X> <Y>45 28 09.534W</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> <esrk>7839298236</esrk> </eme_pos> </eme_lia>
5.2.3.3.3
Emergency Location Immediate Report DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param eme_lirep eme_lirep ver CDATA ""> (req_id, (eme_pos+ | (result, add_info?)) %extension.param;)> #FIXED "3.2.0">
OMA-TS-MLP-V3_2-20051124-C
Page 38 (128)
Example
<eme_lirep ver="3.2.0"> <req_id>25687</req_id> <eme_pos> <msid type="EME_MSID">520002-51-431172-6-06</msid> <pd> <time utc_off="+0300">20020623134453</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 24 43.53N</X> <Y>45 28 09.534W</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> <esrk>7839298236</esrk> </eme_pos> </eme_lirep>
5.2.3.4
Standard Location Reporting Service
When a mobile subscriber wants an LCS client to receive the MS location, e.g. by initiating a MO-LR procedure according to [23.271], a standard location report is generated. The LCS Client that the location report should be sent to SHALL be specified by the MS or defined within the Location Server. The service consists of the following message: Standard Location Report Standard Location Report Answer
The Standard Location Reporting Service SHALL consist of one Standard Location Report followed by one Standard Location Report Answer. The following message flow as depicted in Figure 5 encapsulates this service:
LCS Client standard location report
Location Server
Standard location report answer
Figure 5: Message flow for the Standard Location Reporting Service
5.2.3.4.1
Standard Location Report DTD

OMA-TS-MLP-V3_2-20051124-C
Page 39 (128)
<!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param slrep slrep ver CDATA ""> (pos+ %extension.param;)> #FIXED "3.0.0">
Example
<slrep ver="3.0.0"> <pos> <msid>461011678298</msid> <pd> <time>20020813010423</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 45 35.41N</X> <Y>45 32 55.02E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </pos> </slrep>
5.2.3.4.2 Standard Location Report Answer DTD

OMA-TS-MLP-V3_2-20051124-C
Page 40 (128)
<!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/useterms.html --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param slra slra ver CDATA ""> ((result, add_info?) %extension.param;)> #FIXED "3.2.0">
Example 1: SLRA in case the handling of corresponding SLREP was successful

<slra ver="3.2.0"> <result resid="0">OK</result> </slra>
Example 2: SLRA in case the handling of corresponding SLREP was in error

<slra ver="3.2.0"> <result resid="4">UNKNOWN SUBSCRIBER</result> <add_info> the subscriber is not registered in the LCS Client</add_info> </slra>
5.2.3.5
Emergency Location Reporting Service
If the wireless network initiates a positioning because a user initiates or releases an emergency call, an emergency location report is generated. The application(s) that the emergency location report should be sent to SHALL be defined within the location server. Data as required geographical format and address to application SHALL also be defined within the location server. The service consists of the following message: Emergency Location Report
The Emergency Location Reporting Service SHALL consist one Emergency Location Report. The following message flow as depicted in Figure 6 encapsulates this service:
OMA-TS-MLP-V3_2-20051124-C
Page 41 (128)
LCS Client emergency location report
Location Server
Figure 6: Message Flow for the Emergency Location Reporting Service
OMA-TS-MLP-V3_2-20051124-C
Page 42 (128)
5.2.3.5.1
Emergency Location Report DTD
 <!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param emerep emerep ver CDATA ""> (eme_event %extension.param;)> #FIXED "3.0.0">
Example
<emerep ver="3.0.0"> <eme_event eme_trigger="EME_ORG"> <eme_pos> <msid>461011678298</msid> <pd> <time utc_off="+0300">20020623010003</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>30 27 45.3N</X> <Y>45 25 50.78E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </eme_pos> </eme_event> </emerep>
5.2.3.6
Triggered Location Reporting Service
The triggered location reporting service is used when an application wants the position of several MSs to be tracked. The triggers could be: The periodicity of reporting defined by an interval time An MS action, defined as the event "UE available" in 3GPP [23.271]. A Change of Area, defined as the event change of area in 3GPP [23.271].
OMA-TS-MLP-V3_2-20051124-C
Page 43 (128)
The report will be triggered when one of the pre-defined MSs actions occurred or the time interval elapses. The service consists of the following messages: - Triggered Location Reporting Request - Triggered Location Reporting Answer - Triggered Location Report - Triggered Location Reporting Stop Request - Triggered Location Reporting Stop Answer The Triggered Location Reporting Service SHALL consist of a Triggered Location Reporting Request followed by one Triggered Location Reporting Answer and zero, one or more OPTIONAL Triggered Location Reports. The Triggered Location Reporting Service MAY also include a Triggered Location Reporting Stop Request that, then SHALL be followed by one Triggered Location Reporting Stop Answer. Additionally a Triggered Location Reporting Stop Answer MAY be sent without preceeding Triggered Location Reporting Stop Request. The following message flow as depicted in Figure 7 encapsulates this service:
LCS Client triggered location reporting request triggered location reporting answer Location Server
triggered location report
triggered location report
triggered location reporting stop request triggered location reporting stop answer
Figure 7: Message Flow for the Triggered Location Reporting Service Note: If the network unilaterally decides to terminate the location reporting, the stop reporting information SHALL be carried in a tlrep. The cancellation of triggered location reporting request could be initiated by the Location Server itself for some reasons such as privacy profile update. In this case a tlrsa MAY be sent without a preceding trlsr.
OMA-TS-MLP-V3_2-20051124-C
Page 44 (128)
5.2.3.6.1
Triggered Location Reporting Request DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT % extension.param tlrr ""> (msids, interval?, start_time?, stop_time?, duration?, tlrr_event?, qop?, geo_info?, pushaddr?, loc_type?, prio?, service_coverage? %extension.param;)> #FIXED "3.2.0">
<!ATTLIST
tlrr ver CDATA
The following rules apply to the use of start_time, stop_time, interval , duration and tlrr_event: TLRR with interval SHALL be interpreted as a request for periodic location reports, and TLRR with tlrr_event SHALL be interpreted as a request for a location report on the occurrence of a specific event. interval and tlrr_event MAY be combined for combined periodic / MS_AVAIL event based location request. When neither interval nor tlrr_event is specified in TLRR, the Location Server MUST reject the request with an error indication 106 to the client. If no START_TIME is specified reporting SHALL start immediately. If no STOP_TIME is specified the reporting SHOULD occur until explicitly canceled with Triggered Location Stop Request or a time out occurs (depending on system configuration). Timeout MAY be reported to the LCS client by 'time_remaining' in triggered location report. If STOP_TIME and Duration are both presented in one request, the Location Server MUST reject the request with an error indication 110 to the client. If START_TIME is older than the current time then the Location Server MUST reject the request with an error indication 110 to the client. If STOP_TIME is older than then current time then the Location Server MUST reject the request with an error indication 110 to the client. If STOP_TIME is earlier than START_TIME then the implementation MUST reject the request with an error indication 110 to the client. If STOP_TIME is equal to START_TIME then the Location Server MUST return a single location report to the client at the specified time. Any interval specified MUST be ignored. If Duration is specified as zero the Location Server MUST return a single location report to the client at the specified time. Any interval specified MUST be ignored.
OMA-TS-MLP-V3_2-20051124-C
Page 45 (128)
The (optional) parameter 'service_coverage' is only allowed for plain periodic requests, i.e. not for event-related requests like MS_Available triggers or area triggers. Example 1: TLRR for periodic location reports during a period specified by start_time and stop_time
<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <interval>00003000</interval> <start_time utc_off="+0300">20021003112700</start_time> <stop_time utc_off="+0300">20021003152700</stop_time> <qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" /> </tlrr>
Example 2: TLRR for single location report at a specified time. stop_time is specified equal to start_time.
<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <interval>00003000</interval> <start_time utc_off="+0300">20021003112700</start_time> <stop_time utc_off="+0300">20021003112700</stop_time> <qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4004</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" /> </tlrr>
Example 3: TLRR for a location report on the occurrence of a MS_AVAIL event after a specified time.
<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <start_time utc_off="+0300">20021003112700</start_time> <tlrr_event> <ms_action type="MS_AVAIL"/> </tlrr_event>
OMA-TS-MLP-V3_2-20051124-C
Page 46 (128)
<qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" /> </tlrr>
Example 4: TLRR for periodic location reports from current time and lasting for a specified period
<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <interval>00003000</interval> <duration>00009000</duration> <qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" />
</tlrr>
Example 5: TLRR for a change_area report on the occurrence of a MS_ENTERING event

<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <tlrr_event> <change_area type="MS_ENTERING" loc_estimates="TRUE"> <target_area> <name_area>Seoul</name_area> </target_area> </change_area> </tlrr_event> <qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier>
OMA-TS-MLP-V3_2-20051124-C
Page 47 (128)
</CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" /> </tlrr>
Example 6: TLRR for a change_area report on the occurrence of a MS_WITHIN_AREA within a geographical area.
<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <tlrr_event> <change_area type="MS_WITHIN_AREA" loc_estimates="FALSE"> <target_area> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>35 35 24.139N</X> <Y>139 35 24.754E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </target_area> <no_of_reports>10</no_of_reports> </change_area> </tlrr_event> <pushaddr> <url>http://location.application.com</url> </pushaddr> </tlrr>
Example 7: TLRR for combined periodic / MS_AVAIL event

<tlrr ver="3.2.0"> <msids> <msid>461011678298</msid> </msids> <interval>00003000</interval> <duration>00009000</duration> <tlrr_event> <ms_action type="MS_AVAIL"/> </tlrr_event> <qop> <hor_acc>100</hor_acc> </qop> <geo_info> <CoordinateReferenceSystem> <Identifier> <code>4326</code> <codeSpace>EPSG</codeSpace> <edition>6.1</edition> </Identifier> </CoordinateReferenceSystem> </geo_info> <pushaddr> <url>http://location.application.com</url> </pushaddr> <loc_type type="CURRENT" /> <prio type="HIGH" /> </tlrr>
OMA-TS-MLP-V3_2-20051124-C
Page 48 (128)
5.2.3.6.2
Triggered Location Reporting Answer DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param tlra tlra ver CDATA ""> (((req_id, lcs_ref?) | (result, add_info?)) %extension.param;)> #FIXED "3.2.0">
The (optional) parameter 'lcs_ref' shall be sent to the LCS Client in case the Requesting Location Server receives it from Home Location Server. Example 1: TLRA if corresponding TLRR was successful
<tlra ver="3.2.0"> <req_id>25293</req_id> <lcs_ref>50</lcs_ref> </tlra>
Example 2: TLRA if corresponding TLRR was in error

<tlra ver="3.2.0"> <result resid="4">UNKNOWN SUBSCRIBER</result> </tlra>
OMA-TS-MLP-V3_2-20051124-C
Page 49 (128)
5.2.3.6.3
Triggered Location Report DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param tlrep tlrep ver CDATA ""> (req_id, lcs_ref?, trl_pos+, time_remaining? %extension.param;)> #FIXED "3.2.0">
The (optional) parameter 'lcs_ref' shall be sent to the LCS Client in case the Requesting Location Server receives it from Home Location Server. Example 1: Successful positioning of periodic location report
<tlrep ver="3.2.0"> <req_id>25267</req_id> <lcs_ref>50</lcs_ref> <trl_pos trl_trigger="PERIODIC"> <msid>461011678298</msid> <pd> <time utc_off="+0300">20020813010423</time> <shape> <CircularArea srsName="www.epsg.org#4326"> <coord> <X>35 35 24.139N</X> <Y>139 35 24.754E</Y> </coord> <radius>15</radius> </CircularArea> </shape> </pd> </trl_pos> <time_remaining>00010000</time_remaining> </tlrep>
Example 2: Cancellation of triggered location report

<tlrep ver="3.2.0"> <req_id>25267</req_id> <lcs_ref>50</lcs_ref>
OMA-TS-MLP-V3_2-20051124-C
Page 50 (128)
<trl_pos trl_trigger="PERIODIC"> <msid>461011678298</msid> <poserr> <result resid="114"> CANCELLATION OF TRIGGERED LOCATION REQUEST</result> <time utc_off="+0200">20041007110237</time> </poserr> </trl_pos> </tlrep>
OMA-TS-MLP-V3_2-20051124-C
Page 51 (128)
5.2.3.6.4
Triggered Location Reporting Stop Request DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param tlrsr tlrsr ver CDATA ""> (req_id, lcs_ref? %extension.param;)> #FIXED "3.2.0">
Example
<tlrsr ver="3.2.0"> <req_id>25293</req_id> <lcs_ref>50</lcs_ref> </tlrsr>
OMA-TS-MLP-V3_2-20051124-C
Page 52 (128)
5.2.3.6.5
Triggered Location Reporting Stop Answer DTD
 <!-MLP V3.0 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.param tlrsa tlrsa ver CDATA ""> ((req_id | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">
Example
<tlrsa ver="3.0.0"> <req_id>25293</req_id> </tlrsa>
5.2.3.7
General Error Message Definition
When an LCS client attempts to invoke a service not defined in this specification, the location server SHOULD return a General Error Message. Sending a general error message (GEM) is no proper solution by itself because it can not always be expected that the client will understand this (MLP) response message, since - by sending an invalid request - the client shows that it may not be familiar with the proper set of MLP services. So additional error indications MAY be described in the appropriate transport layer mappings.
 <!-MLP V3.1 Document Type Definition Copyright Open Mobile Alliance Ltd., 2002 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE gem PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}"
OMA-TS-MLP-V3_2-20051124-C
Page 53 (128)
[<?oma-{ref}-ver supported-versions="{versions}"?>]> <gem> ... </gem> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ELEMENT <!ATTLIST gem gem ver CDATA (result, add_info?)> #FIXED "3.1.0"> SYSTEM "MLP_RES_300.DTD">
<!ENTITY % mlp_res.dtd %mlp_res.dtd;
Example
<gem ver="3.1.0"> <result resid="108">SERVICE NOT SUPPORTED</result> <add_info> The server does not support a service named 'skir' </add_info> </gem>
5.3
5.3.1
Elements and attributes in DTD

add_info
Description: A text string containing additional information about a certain result. Element Type: Char string Format: Defined values: Default value: <add_info>EVENT</add_info> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 54 (128)
5.3.2
alt
Description: The altitude of the MS in meters in respect of the ellipsoid which is used to be define the coordinates Element Type: Char String Format: [+|-]?[0-9]+ Defined values: Default value: <alt>1200</alt> Example: This element is present if altitude is possible to attain by the used positioning method. Note:
5.3.3
alt_acc
Description: Accuracy of requested altitude in meters Element Type: Char String Format: [0-9]+ Defined values: Default value: <alt_acc>200</alt_acc> Example: Note:
5.3.3.1
qos_class
Description: defines the degree of adherence by the Location Service to the quality of another quality of service parameter. In the MLP context this refers to the XML parent element, i.e alt_acc, hoc_acc, or ll_acc, resp. Type: Format: Defined values: Attribute Char string ASSURED
BEST_EFFORT
defines the most stringent requirement on the accuracy achieved for a location request. If a location estimate obtained does not fulfil the alt_acc requirements, then it shall be discarded and an appropriate error cause sent. defines the least stringent requirement on the QoS achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, it should still be returned but with an appropriate indication that the requested QoS was not met. If no location estimate is obtained, an appropriate error cause is sent..
Default value: Example: Note:
<alt_acc qos_class="BEST_EFFORT">200</alt_acc>
For details see 3GPP TS 23.271, v6.8.0, clause 6.5.1
5.3.4
alt_unc
OMA-TS-MLP-V3_2-20051124-C
Page 55 (128)
Description: Uncertainty of altitude estimate in meters Element Type: Char String Format: [0-9]+ Defined values: Default value: <alt_unc>200</alt_unc> Example: Note:
5.3.5
angle
Description: Specifies the angle (in angularUnit) of rotation of an ellipse measured clockwise from north Element Type: Char String Format: Defined values: Default value: <angle>24.30</angle> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 56 (128)
5.3.6
angularUnit
Description: The angularUnit defines the unit for any angular value used in the shape description. For example the startAngle value in the CircularArcArea will be defined by this unit. If this unit is not included in a shape definition the angular unit defined in the CRS SHALL be used. Element Type: Char String Format: Degrees Defined values: Radians Degrees Default value: <angularUnit>Degrees</angularUnit> Example: Note:.
5.3.7
Box
Description: The Box element is used to encode extents Element Type: Format: Defined values: Default value: <Box srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 <Y>45 25 </coord> <coord> <X>31 27 <Y>46 25 </coord> </Box> 45.3N</X> 52.9E</Y>
45.3N</X> 52.9E</Y>
Note:
5.3.7.1
gid
Description: The gid is of XML attribute type ID and is used for references to elements within a single XML document. It allows XML technologies such as XPointer and xref to be used.. Attribute Type: Char String Format: Defined values: Default value: <Box srsName="www.epsg.org#4326" gid="some_thing"> Example: This attribute is optional and is on all shape elements Note:
OMA-TS-MLP-V3_2-20051124-C
Page 57 (128)
5.3.7.2
srsName
Description: srsName is a short hand method of defining the CoordinateReferenceSystem. It is a URI datatype that contains the codeSpace and code values, which are defined in the same way as in the CoordinateReferenceSystem. Attribute Type: Char String Format: Defined values: www.epsg.org/#4326 Default value: <Box srsName="www.epsg.org/#4326"> Example: This attribute is optional and is on all shape elements. If the srsName is not included the Note: WGS84 CRS SHOULD be assumed.
5.3.8
cc
Description: Specifies the country code. Element Type: Char String Format: 1-3 digits e.g. 355 for Albania Defined values: Default value: <cc>355</cc> Example: Note:
5.3.9
cellid
Description: Identifies the Cell Identity Element Type: Char String Format: 0-65535 Defined values: Default value: <cellid>546</cellid> Example: Note:
5.3.10
change_area
Description: Specifies the event that initiated the positioning of the MS Element Type: Format:
OMA-TS-MLP-V3_2-20051124-C
Page 58 (128)
Defined values: Default value: Example:
<change_area type=MS_ENTERING> <target_area> <name_area>Seoul</name_area> </targer_area> </change_area>
Note:
5.3.9.1 type
Description: Specifies the trigger that initiated the positioning of the MS Attribute Type: Char string Format: MS_ENTERING Defined values: MS_LEAVING MS_WITHIN_AREA Default value: <change_area type=MS_ENTERING> Example: Note:
5.3.9.2. loc_estimates
Description: Specifies whether location estimates is required or not Attribute Type: Char string Format: TRUE Defined values: FALSE Default value: <change_area loc_estimates=TRUE> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 59 (128)
5.3.11
CircularArcArea
Description: An arc is defined by a point of origin with one offset angle and one uncertainty angle plus one inner radius and one uncertainty radius. Element Type: Format: Defined values: Default value: <CircularArcArea srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 45.3N</X> <Y>45 25 52.9E</Y> </coord> <inRadius>280</inRadius> <outRadius>360</outRadius> <startAngle>5</startAngle> <stopAngle>240</stopAngle> </CircularArcArea>
Note:
5.3.11.1
gid
See section 5.3.7.1.
5.3.11.2
srsName
5.3.12
CircularArea
Description: The set of points on the ellipsoid, which are at a distance from the point of origin less than or equal to r. Element Type: Format: Defined values: Default value: <CircularArea srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 45.3N </X> <Y>45 25 52.9E</Y> </coord> <radius>240</radius> </CircularArea>
Note:
5.3.12.1
gid

OMA-TS-MLP-V3_2-20051124-C
Page 60 (128)
5.3.12.2
srsName
5.3.13
code
Description: This is the unique identifier for the Coordinate ReferenceSystem as used by the authority cited in codeSpace Element Type: Char String Format: Defined values: Default value: <code>4326</code> Example: . Note:
5.3.14
codeSpace
Description: The codeSpace is the authority, which is responsible for the definition of the coordinate reference systems. Element Type: Char String Format: Defined values: www.epsg.org/... Default value: <codeSpace>www.epsg.org</codeSpace> Example: Note:
5.3.15
codeword
Description: Codeword is an access code defined per MS, used to protect location information of MS against unwanted location request. Only location requests with the correct codeword of a target MS are accepted. Element Type: Char String Format: Defined values: Default value: <codeword>0918a7cb</codeword> Example: An error SHALL be returned if the number of codewords is not equal to the number of msid in Note: an msid_range.
OMA-TS-MLP-V3_2-20051124-C
Page 61 (128)
5.3.16
distanceUnit
Description: The distanceUnit defines the linear unit for any distance used in the shape description. For example the radius value in the CircularArea will be defined by this unit. If this unit is not included in a shape definition the distance unit defined in the CRS SHOULD be used. Element Type: Char String Format: Defined values: meter Default value: <distanceUnit>surveyfoot</distanceUnit> Example: values are defined by the CRS authority Note:
5.3.17
direction
Description: Specifies the direction of movement (in degrees) of a positioned MS Element Type: Char String Format: 0-360 Defined values: Default value: <direction>120</direction> Example: This element is present if direction is possible to attain by the used positioning method. Note:
5.3.18
duration
Description: A string defining the time range of triggered location reporting service. Element Type: Char String Format: The time is expressed as ddhhmmss where: String Description dd Day hh Hours mm Minutes ss Seconds Defined values: Default value: Example: Note:
<duration>00001000</duration>
OMA-TS-MLP-V3_2-20051124-C
Page 62 (128)
5.3.19
edition
Description: The edition defines which version of the CRS database defined by the codeSpace authority is used.. Element Type: Char String Format: Defined values: Default value: <edition>6.0</edition> Example: Note:
5.3.20
EllipticalArea
Description: A set of points on the ellipsoid, which fall within or on the boundary of an ellipse. This ellipse has a semi-major axis of length r1 oriented at angle A (0 to 180) measured clockwise from north and a semi-minor axis of length r2. Element Type: Format: Defined values: Default value: <EllipticalArea srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 45.3N</X> <Y>45 25 52.9E</Y> </coord> <angle>240</angle> <semiMajor>275</semiMajor> <semiMinor>150</semiMinor> <angularUnit>degrees</angularUnit> </EllipticalArea>
Note:
5.3.20.1
gid
5.3.20.2
srsName
OMA-TS-MLP-V3_2-20051124-C
Page 63 (128)
5.3.21
eme_event
Description: Specifies the events that initiated the positioning of the MS at an emergency call. Element Type: Format: Defined values: Default value: <eme_event eme_trigger="EME_ORG"> Example: Note:
5.3.21.1
eme_trigger
Description: Specifies the trigger that initiated the positioning of the MS at an emergency call. Attribute Type: Char string Format: EME_ORG An emergency service user originated an emergency call Defined values: EME_REL An emergency service user released an emergency call Default value: <eme_event eme_trigger="EME_ORG"> Example: Note:
5.3.22
eme_pos
Description: Specifies the position of the MS in an emergency location service response. Element Type: Format: Defined values: Default value: <eme_pos pos_method=A-GPS> Example:
<msid>4711</msid> <poserr> <result resid="1">SYSTEM FAILURE</result> <time utc_off="0200">20040617144558</time> </poserr> </eme_pos>
Note:
5.3.22.1
Description:
pos_method
OMA-TS-MLP-V3_2-20051124-C
Page 64 (128)
Specifies the positioning method used to obtain the associated location estimate Attribute Type: Char string Format: CELL Cell coverage based positioning method Defined values: OTDOA Observed Time Difference of Arrival (OTDOA) positioning method GPS Global Positioning System (GPS) based positioning method A-GPS Assisted GPS based positioning method E-OTD Enhanced Observed Time Difference (E-OTD) positioning method U-TDOA Uplink Time Difference of Arrival (U-TDOA) positioning method AFLT Advanced Forward Link Triangulation positioning method EFLT Enhanced Forward Link Triangulation positioning method UNKNOWN Unknown positioning method OTHER Any other positioning method Default value: <eme_pos pos_method="A-GPS"> </eme_pos> Example: The list of current values reflects the status quo described in 3GPP TS 23.271, V6.7.0, sect. 4.3 Note: (plus A-GPS) and TIA-801. New values may be added as soon as the need arises.
5.3.23
esrd
Description: This element specifies Emergency Services Routing Digits (ESRD). Element Type: Char string Format: Defined values: Default value: <esrd>761287612582</esrd> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 65 (128)
5.3.23.1
type
Description: Defines the origin of the ESRD Attribute Type: Char string Format: NA Defined values:
Indicates that the ERSD is defined as the North American ESRD (NAERSD).NA-ESRD is a telephone number in the North American Numbering Plan that can be used to identify a North American emergency services provider and its associated Location Services client. The NA-ESRD also identifies the base station, cell site or sector from which a North American emergency call originates
NA
<esrd type="NA">12345678</ersd>
Currently only NA is specified. It is expected that other origins will be specified in the future
5.3.24
esrk
Description: This element specifies the Services Routing Key (ESRK). Element Type: Char string Format: Defined values: Default value: <esrk>928273633343</esrk> Example: Note:
5.3.24.1
type
Description: Defines the origin of the ESRK Attribute Type: Char string Format: NA Defined values:
Indicates that the ERSK is defined as the North American ESRK (NAERSK).NA-ESRK is a telephone number in the North American Numbering Plan that is assigned to an emergency services call for the duration of the call. The NA-ESRK is used to identify (e.g. route to) both the emergency services provider and the switch currently serving the emergency caller. During the lifetime of an emergency services call, the NA-ESRK also identifies the calling subscriber.
NA
<esrk type="NA">12345678</ersk>
Currently only NA is specified. It is expected that other origins will be specified in the future
OMA-TS-MLP-V3_2-20051124-C
Page 66 (128)
5.3.25
hor_acc
Description: Horizontal accuracy in meters Element Type: Char String Format: [0-9]+ Defined values: Default value: <hor_acc>200</hor_acc> Example: Note:
5.3.24.1 qos_class
see section 5.3.3.1
5.3.26
id
Description: A string defining the name of a registered user performing a location request. In an answer the string represents the name of a location server. Element Type: Char string Format: Defined values: Default value: <id>TheTruckCompany</id> Example: This element is implementation specific. Note:
5.3.27
imsi
Description: The International Mobile Subscriber Identity number as specified in 3GPP TS 23.003 and ITU-T E212 Recommendation. Element Type: Char String Format: Defined values: Default value: <imsi>123456789012345</imsi> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 67 (128)
5.3.28
inRadius
Description: The inner radius is the geodesic distance (in distannceUnit) between the center of the circle (that the arc is a part of) and the arc closest to the center Element Type: Char String Format: [0-9]+ Defined values: Default value: <inRadius>100</inRadius> Example: If the inner radius is 0 (zero) the area described represents a sector of a circle. Note:
5.3.29
interval
Description: Specifies the interval between two responses in case of a TLRR indicating timer controlled, periodic responses. Element Type: Char string Format: The interval is expressed as ddhhmmss where: String Description dd Number of days between responses hh Number of hours between responses mm Number of minutes between responses ss Number of seconds between responses Defined values: Default value: <interval>00010000</interval> Example: Note:
5.3.30
lac
Description: Identifies the Location Area Code Element Type: Char String Format: 1-65535 Defined values: Default value: <lac>234</lac> Example: Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within Note: a GSM PLMN. This part of the location area identification can be coded using a full hexadecimal representation, except for the following reserved hexadecimal values: 0000, and FFFE
OMA-TS-MLP-V3_2-20051124-C
Page 68 (128)
5.3.31
lcs_ref
Description: The LDR reference number received from Home Location Server. For more information see [23.271] Element Type: Char String Format: Two decimal digits, 00-64 Defined values: Default value: <lcs_ref>50</lcs_ref> Example: Lcs_ref SHALL be sent in the triggered location reporting request with change of area event or Note: MS_AVAIL event and combined triggered location reporting request with periodic event / MS_AVAIL event request case. The LDR reference number is received as one octet and shall be encoded to the decimal numbers 00 to 64.
5.3.32
lev_conf
Description: This parameter indicates the probability in percent that the MS is located in the position area that is returned. Element Type: Char String Format: 0-100 Defined values: Default value: <lev_conf>80</lev_conf> Example: Note:
5.3.33
LinearRing
Description: A linear ring is a closed, simple piece-wise linear path which is defined by a list of coordinates that are assumed to be connected by straight-line segments. Element Type: Format: Defined values: Default value: <LinearRing srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 <Y>45 25 </coord> <coord> <X>40 27 <Y>48 25 </coord> <coord> <X>33 27 <Y>46 25 </coord> 45.3N</X> 52.9E</Y>
45.3N</X> 52.9E</Y>
45.3N</X> 52.9E</Y>
OMA-TS-MLP-V3_2-20051124-C
Page 69 (128)
<coord> <X>30 27 45.3N</X> <Y>45 25 52.9E</Y> </coord> </LinearRing>
Note:
5.3.33.1
gid
5.3.33.2
srsName
5.3.34
LineString
Description: A line string is a piece-wise linear path which is defined by a list of coordinates that are assumed to be connected by straight-line segments. Element Type: Format: Defined values: Default value: <LineString srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 45.3N</X> <Y>48 25 52.9E</Y> </coord> <coord> <X>40 27 45.3N</X> <Y>48 25 52.9E</Y> </coord> <coord> <X>33 27 45.3N</X> <Y>48 25 52.9E</Y> </coord> </LineString>
Note:
5.3.34.1
gid
5.3.34.2
srsName
OMA-TS-MLP-V3_2-20051124-C
Page 70 (128)
5.3.35
ll_acc
Description: Longitude and latitude accuracy in seconds. Element Type: Char String Format: Defined values: Default value: <ll_acc>7.5</ll_acc> Example: Note:
5.3.34.1 qos_class
see section 5.3.3.1
OMA-TS-MLP-V3_2-20051124-C
Page 71 (128)
5.3.36
lmsi
Description: A local identity allocated by the VLR to a given subscriber for internal management of data in the VLR as defined in [29.002] Element Type: Char String Format: Defined values: Default value: <lmsi>234</lmsi> Example: The LMSI consists of 4 octets Note:
5.3.37
loc_type
Description: Defines the type of location requested. Element Type: Void Format: Defined values: Default value: <loc_type type="INITIAL" /> Example: Note:
5.3.37.1
type
Description: Defines the type of location requested Attribute Type: Char string Format: CURRENT Defined values:
LAST
LAST_OR_CURRENT
CURRENT_OR_LAST
After a location attempt has successfully delivered a location estimate and its associated time stamp, the location estimate and time stamp is known as the current location at that point in time. The current location estimate and its associated time stamp is generally stored in the network and is known as the last known location until replaced by a later location estimate and a new time stamp.The last known location may be distinct from the initial location, i.e., more recent. If the last known location is stored in the network and if this location satisfies the Quality of Service requested by the locationbased application the last known location is returned, otherwise the current location is returned. If a location attempt has successfully delivered a current location, it is returned. Otherwise if the last known location stored in the network satisfies the requested Quality of service the last known location is returned.
OMA-TS-MLP-V3_2-20051124-C
Page 72 (128)
INITIAL
In an originating emergency call, the location estimate and the associated time stamp at the commencement of the call set-up is known as the initial location.
CURRENT
<loc_type type="INITIAL" />
5.3.38
max_loc_age
Description: This states the maximum allowable age in seconds of a location sent as a response to a location request. This location information may have been cached somewhere in the system from a previous location update. Element Type: Char string Format: Maximum number of seconds (must be >= 0) Defined values: Implementation specific. Default value: <max_loc_age>3600</max_loc_age> Example: Note:
5.3.39
mcc
Description: Specifies the mobile country code (MCC). Element Type: Char String Format: 3 digits, e.g. 234 for the UK Defined values: Default value: <mcc>234</mcc> Example: Note:
5.3.40
mnc
Description: Specifies the mobile network code. Element Type: Char string Format: 2 - 3 digits e.g. 15 for Vodafone Defined values: Default value: <mnc>215</mnc> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 73 (128)
5.3.41
ms_action
Description: Specifies the trigger that initiated the positioning of the MS. Element Type: Void Format: Defined values: Default value: <ms_action type="MS_AVAIL" /> Example: Note:
5.3.41.1
type
Description: Specifies the trigger that initiated the positioning of the MS. Attribute Type: Char string Format: MS_AVAIL The positioning is triggered by the MS available notification when the Defined values: MS regains radio connection with the network if the connection was previously lost. For more information refer to 3GPP [23.271]. Default value: <ms_action type="MS_AVAIL" /> Example: Note:
5.3.42
msid
Description: This element represents an identifier of a mobile subscriber Element Type: Char string Format: Defined values: Default value: <msid>460703057640</msid> Example: When appropriate the MSID type format SHOULD confirm to the full standardised Note: international representation of the MSID type, without any additional unspecified characters or spaces. As an example the GSM/3GPP identifiers SHOULD conform to 3GPP [23.003]
OMA-TS-MLP-V3_2-20051124-C
Page 74 (128)
5.3.42.1
type
Description: Type of identifier for the mobile subscriber Attribute Type: Char string Format: MSISDN Defined values: IMSI IMEI MIN MDN EME_MSID ASID IPV4 OPE_ID IPV6 SESSID SIP_URI TEL_URL MSISDN
<msid type="IMSI">
Mobile Station International ISDN Number [23.003] International Mobile Subscriber Identity [23.003], [J-STD-036] International Mobile station Equipment Identity [23.003] Mobile Identification Number [IS-41D] Mobile Directory Number [IS-41D] Emergency MSID Anonymous Subscriber Identity Mobile station IP address (Version 4) [RFC796] Operator specific Identity Mobile station IP address (Version 6) [RFC3513] Session identifier relating to the user, which MAY be anonymous IMS Public User Identity (Session Initiation Protocol Uniform Resource Identifier) [RFC 3261] Telephone Uniform Resource Locator [RFC 2806]
5.3.42.2
enc
Description: Type of encoding of MSID identifier for the mobile subscriber Attribute Type: Char string Format: ASC Normal textual format Defined values: CRP Encrypted format: Can be used to protect target privacy by only proving the LCS client with an Encrypted MSID ASC Default value: <msid type="IMSI" enc="ASC"> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 75 (128)
5.3.43
MultiLineString
Description: A collection of line strings. Element Type: Format: Defined values: Default value: <MultiLineString srsName="www.epsg.org#4326" gid="some_thing"> Example:
<LineString> ... </LineString> </MultiLineString>
Note:
5.3.43.1
gid
5.3.43.2
srsName
see section 5.3.7.2.
5.3.44
MultiPoint
Description: A collection of points. Element Type: Format: Defined values: Default value: <MultiPoint srsName="www.epsg.org#4326" gid="some_thing"> Example:
<Point> ... </Point> </MultiPoint>
Note:
5.3.44.1
gid
5.3.44.2
srsName
OMA-TS-MLP-V3_2-20051124-C
Page 76 (128)
5.3.45
MultiPolygons
Description: A collection of polygons. Element Type: Format: Defined values: Default value: <MultiPolygon srsName="www.epsg.org#4326" gid="some_thing"> Example:
<Polygon> ... </Polygon> </MultiPolygon>
Note:
5.3.45.1
gid
5.3.45.2
see section 0.
srsName
5.3.46
name_area
Description: Specify the geopolitical name of area in change_area event. Element Type: Char string Format: Defined values: Default value: <name_area>Seoul</name_area> Example: Note:
5.3.47
ndc
Description: Specifies the national destination code. Element Type: Char string Format: Variable length depending upon the requirements of the destination country. Defined values: Default value: <ndc>215</ndc> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 77 (128)
5.3.48
nmr
Description: Network specific measurement result for the target MS. Element Type: Char string Format: For examples see relevant standards documents. Defined values: Default value: Example: Measurement Results are encoded as 34 hexadecimal characters representing, 17 binary octets, Note: in accordance with the Measurement Result information element described in [04.18].
5.3.49
no_of_reports
Description: Specify the maximum number of reports for a TLRR request. Element Type: Char String Format: [1-9]+ Defined values: 1 Default value: <no_of_reports>5</no_of_reports> Example: Note:
5.3.50
plmn
Description: A unique identity of Public Land Mobile Network as defined in [23.003]. Element Type: Char String Format: Defined values: Default value: <plmn> Example:
<mcc>234</mcc> <mnc>215</mnc> </plmn>
Note:
5.3.51
qos_not_met
Description: Indication that the requested QoS was not met, if needed. Element Type: Void Format: Defined values:
OMA-TS-MLP-V3_2-20051124-C
Page 78 (128)
Default value: Example: Note: Only applicable if the request was for best effort class, i.e. a location estimate is returned (rather than an error) although the requested QoS requirement could not be fulfilled.
5.3.52
radius
Description: The uncertainty radius is the radius (in distanceUnit) of the uncertainty; this is the geodesic distance between the arc and the position point. Element Type: Char String Format: [0-9]+ Defined values: Default value: <radius>850</radius> Example: Note:
5.3.53
startAngle
Description: The start angle is the angle (in angularUnit) between North and the first defined radius. Element Type: Char string Format: Defined values: 0-359 Default value: <startAngle>60</startAngle> Example: Note:
5.3.54
stopAngle
Description: The stop angle is the angle (in angularUnit) between the first and second defined radius. Element Type: Char string Format: Defined values: 1-360 Default value: <stopAngle>180</stopAngle> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 79 (128)
5.3.55
Point
Description: A geographic coordinate Element Type: Format: Defined values: Default value: <Point srsName="www.epsg.org#4326" gid="some_thing"> Example:
<coord> <X>30 27 45.3N</X> <Y>45 25 52.9E</Y> </coord> </Point>
Note:
5.3.55.1
gid
5.3.55.2
srsName
5.3.56
Polygon
Description: A connected surface. Any pair of points in the polygon can be connected to one another by a path. The boundary of the Polygon is a set of LinearRings. We distinguish the outer (exterior) boundary and the inner (interior) boundaries; the LinearRings of the interior boundary cannot cross one another and cannot be contained within one another. Element Type: Format: Defined values: Default value: <Polygon srsName="www.epsg.org#4326" gid="some_thing"> Example:
<outerBoundaryIs> ... </outerBoundaryIs > </Polygon>
Note:
5.3.56.1
gid
OMA-TS-MLP-V3_2-20051124-C
Page 80 (128)
5.3.56.2
srsName
5.3.57
prio
Description: Defines the priority of a location request Element Type: Void Format: Defined values: Default value: <prio /> Example: Note:
5.3.57.1
type
Description: Defines the priority of a location request Attribute Type: Char string Format: NORMAL The request is handled with normal priority Defined values: HIGH The request is handled with high priority NORMAL Default value: <prio type="HIGH" /> Example: Note:
5.3.58
pwd
Description: The password for the registered user performing a location request. In this answer the string represents the password for a location server. Element Type: Char string Format: Defined values: Default value: <pwd>the5pwd</pwd> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 81 (128)
5.3.59
outRadius
Description: The radius of a circle furthest away from the position in a CircularArcArea. The value is in the distanceUnit Element Type: Char String Format: [0-9]+ Defined values: Default value: <outRadius>120</outRadius> Example: Note:
5.3.60
pos
Description: Specifies the position of the MS in an immediate location service response. Element Type: Format: Defined values: Default value: <pos> Example:
<msid>4711</msid> <poserr> <result resid="1">SYSTEM FAILURE</result> <time utc_off="0200">20040617143232</time> </poserr> </pos>
Note:
5.3.60.1
pos_method
see section 5.3.22.1
5.3.61
requestor
Description: This element describes the originating entity which has requested the location of the target MS from the MLS client. Type: Format: Defined values: Default value: Example: Element Compound n/a
<requestor> <id>08154711</id> </requestor>
OMA-TS-MLP-V3_2-20051124-C
Page 82 (128)
Note:
5.3.61.1
type
Description: This attribute represents the type of the requestor identifier Attribute Type: Char String Format: Logical name NAME Defined values: MSISDN E-MAIL URL SIPURL IMS MDN ASID Default value: Example: MSISDN
<requestor type="SIPURL"> <id>sip:+1-212-555-1212:1234@gateway.com;user=phone</id> <serviceid>4711</serviceid> </requestor>
MSISDN E-mail address URL SIP URL IP multimedia subsystem public identity MDN ASID
Note:
References to the definition and the format of each of these types can be found in [23.271],
5.3.62
req_id
Description: Unique identification of a request Element Type: Char string Format: Defined values: Default value: <req_id>435.23.01</req_id> Example: Note:
5.3.63
resp_req
Description: This attribute represents the response time required. Element Type: Void Format:
OMA-TS-MLP-V3_2-20051124-C
Page 83 (128)
Defined values: Default value: Example: Note:
<resp_req type="NO_DELAY" />
OMA-TS-MLP-V3_2-20051124-C
Page 84 (128)
5.3.63.1
type
Description: This attribute represents the response time required Attribute Type: Char String Format: NO_DELAY No delay: The server SHOULD immediately return any location estimate Defined values: that it currently has. LOW_DELAY Low delay: Fulfilment of the response time requirement takes precedence over fulfilment of the accuracy requirement. DELAY_TOL Delay tolerant: Fulfilment of the accuracy requirement takes precedence over fulfilment of the response time requirement. DELAY_TOL Default value: <resp_req /> Example: The interpretation of these parameters is defined in 3GPP [22.071] and [29.002]. When this Note: parameter is used with the resp_timer, the resp_timer will take presedence.over this parameter.
5.3.64
resp_timer
Description: Defines a timer for the response time within which the current location SHOULD be obtained and returned to the LCS Client. Element Type: Char String Format: Maximum number of seconds (must be >= 0) Defined values: The default value is defined in the location server and will be implementation specific Default value: <resp_timer>45</resp_timer> Example: When this parameter is used with the resp_req, this parameter will take presedence.over the Note: resp_req.
5.3.65
result
Description: A text string indicating the result of the request or an individual positioning Element Type: Char string Format: See section 5.4 "Result codes" Defined values: Default value: <result resid=0>OK</result> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 85 (128)
5.3.65.1
resid
Description: This attribute represents a numeric representation of a result message Attribute Type: Char String Format: [0-9]+ Defined values: Default value: <result resid=0>OK</result> Example: See section 5.4. Note:
5.3.66
semiMajor
Description: Specifies the length (in distanceUnit) of the semi-major axis of an ellipse. Element Type: Char String Format: [0-9]+ Defined values: Default value: <semiMajor>560</semiMajor> Example: Note:
5.3.67
semiMinor
Description: Specifies the length (in distanceUnit) of the semi-minor axis of an ellipse. Element Type: Char String Format: [0-9]+ Defined values: Default value: <semiMinor>560</semiMinor> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 86 (128)
5.3.68
serviceid
Description: Specifies an id that is used by an entity to identify the service or application that is accessing the network. Element Type: Char String Format: Defined values: Default value: <serviceid>0005</serviceid> Example: Note:
5.3.69
requestmode
Description: Defines the type of the service that has been requested by the ASP. Element Type: Void Format: Defined values: Default value: <requestmode type="ACTIVE"/> Example: If the request mode is ACTIVE, the session element is included in msids of location request. Note: The session element can be used as a credential by the Location Server or underlying network to verify that the request is actually ACTIVE. One example of this can be that the network verifies the number the target has dialed that is presented by the MLS Client in the session element. The session element is either the number called by the UE for a call related location request or the APN on which the UE established the session for a session related location request according to [23.271]. The LCS Client determines whether the LCS service request is call/session related or not.
5.3.69.1
type
Description: Defines the type of the service that has been requested by the ASP Attribute Type: Char string Format: PASSIVE The service is one that is not directly initiated by the user. Defined values: ACTIVE The service is one that the user is initiating personally. Default value: Example: Note: PASSIVE
<requestmode type="ACTIVE" />
The default value is set to PASSIVE, as this is likely to be the one that is most restrictively defined by the user.
OMA-TS-MLP-V3_2-20051124-C
Page 87 (128)
5.3.70
session
Description: This element SHOULD be presented in the location request when the LCS Client has an active session with the User Equipment, this will be either the number called by the UE or the APN on which the UE established the session. Element Type: Char String Format: Defined values: Default value: <session type=DIAL>447073100177</session> Example: According to [23.271], for a call related location request, the LCS Client includes the LCS Note: Client's called party number, as dialled by the target mobile user, in the LCS service request. For a session related location request, the LCS Client includes the APN-NI of the LCS Client, as used by the target UE, in the LCS service request. It means that it is up to the LCS Client whether the LCS service request is call/session related or not.
5.3.70.1
type
Description: Defines the type of session that is established between the User Equipment and LCS Client Attribute Type: Char string Format: APN Access Point Name. Defined values: DIAL The number dialed by the user to access the LCS client. Default value: <session type="DIAL">447073100177</session> Example: Note:
5.3.71
sessionid
Description: Specifies an id that can be used by an entity to support privacy mechanisms, a sessionid may replace the need to use an ID and PWD to use the location services. In a request when a client and sessionid are present together the session id may indicate the number dialed by the end user to access the service or the APN through which the original session was established that initiated the service. The response indicates the sessionid that the entity can use on subsequent requests. In this casethe sessionid could be a generated alphanumeric string and can be time-limited. Element Type: Char String Format: Defined values: Default value: <sessionid>34eg6.876.76h4</sessionid> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 88 (128)
5.3.72
speed
Description: The speed of the MS in m/s. Element Type: Char String Format: [0-9]+ Defined values: Default value: <speed>23</speed> Example: This element is present if speed is possible to attain by the used positioning method. Note:
5.3.73
start_time
Description: This element defines the absolute start time in a time range. Element Type: Char String Format: The time is expressed as yyyyMMddhhmmss where: String Description yyyy Year MM Month dd Day hh Hours mm Minutes ss Seconds Defined values: Default value: Example: Note:
<start_time>20010630142810</start_time>
5.3.73.1
utc_off
Description: Specifies the UTC [UTC] offset in hours and minutes. Positive values indicate time zones east of Greenwich. Attribute Type: Char string Format: [+|-]?0000-1400 Defined values: Default value: <start_time utc_off="+0200">20020813010423</start_time> Example: utc_off is specified as 'HHMM', where 'HH' can range between 0-14 and 'MM' between '0-59'. Note: All other values shall result in error 105, 'Format error'.
OMA-TS-MLP-V3_2-20051124-C
Page 89 (128)
5.3.74
stop_time
Description: This element defines the absolute stop time in a time range. Element Type: Char String Format: The time is expressed as yyyyMMddhhmmss where: String Description yyyy Year MM Month dd Day hh Hours mm Minutes ss Seconds Defined values: Default value: Example: Note:
<stop_time>20020630142810</stop_time>
5.3.74.1
utc_off
See section 5.3.73.1
5.3.75
subclient
Description: Identifies the ASPs, resellers and portals in the chain of service providers between the network and the end-user Element Type: Format: Defined values: Default value: <subclient last_client="NO"> Example:
<id>TheASP</id> <serviceid>0006</serviceid> </subclient>
Note:
OMA-TS-MLP-V3_2-20051124-C
Page 90 (128)
5.3.75.1
last_client
Description: Identifies whether the SUBCLIENT is the last one in the chain or not Attribute Type: Char String Format: YES This is the last client the one that the end-user is actually Defined values: communicating with NO This is not the last client NO Default value: <subclient last_client="YES"> Example: Note:
5.3.76
ta
Description: This Radio Access Network element that can be used to offer enhanced positioning. (Timing Advance) Element Type: Char string Format: 0-63 Defined values: 0 Default value: <ta>3</ta> Example: Further Information regarding this element can be found in the relevant GSM Specifications Note: [05.10]
5.3.77
target_area
Description: Specify the target area in change_area event. Element Type: Format: Defined values: Default value: <target_area> Example: Note:
<name_area>Seoul</name_area> </target_area>
5.3.78
time
Description: In a location answer this element indicates the time when the positioning was performed. Element Type:
OMA-TS-MLP-V3_2-20051124-C
Page 91 (128)
Format:
Char String The time is expressed as yyyyMMddhhmmss where: String Description yyyy Year MM Month dd Day hh Hours mm Minutes ss Seconds
Defined values: Default value: Example: Note:
<time>20010630142810</time>
5.3.78.1
utc_off
5.3.79
time_remaining
Description: Defines the time remaining until the location server terminates the current triggered location service. The time when the service is valid is either specified by the client using start time and stop time, or is a network operator specific default value where no stop time is defined or where the stop time exceeds the allowed value by the location server involved. Element Type: Char String Format: The time is expressed as ddhhmmss where: String Description dd Day hh Hours mm Minutes ss Seconds Defined values: Default value: Example: Note: The default value is defined in the location server
<time_remaining>00010000</time_remaining>
5.3.80
trans_id
Description: An identifier originally provided by the client so it can associate responses to the original request Element Type:
OMA-TS-MLP-V3_2-20051124-C
Page 92 (128)
Format: Defined values: Default value: Example: Note:
Char string None None

<trans_id>uk999call04112417544312</trans_id>
trans_id is used to distinguish between multiple location requests of the same target. This implementation is not supported when a range of MSIDs are requested by the client
5.3.81
trl_pos
Description: Specifies the position of the MS at a triggered location report. Element Type: Format: Defined values: Default value: <tlr_pos trl_trigger="PERIODIC"> Example:
<msid>4711</msid> <poserr> <result resid="1">SYSTEM FAILURE</result> <time utc_off="0100">20011127104532</time> </poserr> </trl_pos>
Note:
5.3.81.1
trl_trigger
Description: Specifies the trigger that initiated the positioning of the MS at a triggered location report. Attribute Type: Char string Format: PERIODIC The positioning is triggered when the periodical timer expired Defined values: MS_AVAIL The positioning is triggered by the MS presence notification CHANGE_AREA The positioning is triggered by the mobility event of the location of MS Default value: <tlr_pos trl_trigger="PERIODIC"> Example: Note:
5.3.81.2
pos_method
OMA-TS-MLP-V3_2-20051124-C
Page 93 (128)
5.3.82
url
Description: Specifies the location to which a response to a TLRR, an asynchronous SLIR or an asynchronous eme_lir should be sent to Element Type: Char string Format: Defined values: Default value: <url>http://location.client.com/Response/</url> Example: URL is part of pushaddr element which may also contain id and pwd. These elements are used Note: by the LCS Client to inform the Location Server what credentials to use when pushing a location report to the LCS Client in the case of an asynchronous service.
5.3.83
vlrno
Description: Uniquely specifies a VLR within a network. Element Type: Char String Format: In GSM this is the Global Title address. The Global Title is in the same format as an E.164 Defined values: number. Default value: <vlrno>1541154871</vlrno> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 94 (128)
5.3.84
vmscno
Description: Uniquely specifies a VMSC within a network. Element Type: Char String Format: In GSM this is the Global Title address. The Global Title is in the same format as an E.164 Defined values: number. Default value: <vmscno>1541154871</vmscno> Example: Note:
5.3.85
Description: The first ordinate in a coordinate system Element Type: Char string Format: Defined values: Default value: <X>30 27 45.3N</X> Example: Note: For the default WGS84 CRS the presentation format is Degrees Minutes Seconds Hemisphere (DMSH), with fields separated by a space character and with leading zeros added to any minute or second values less than 10. Note that in the WGS84 CRS 'X' denotes the latitude of a position.
5.3.86
Description: Second ordinate in a coordinate.system. This is optional if it is a linear coordinate system. Element Type: Char string Format: Defined values: Default value: <Y>45 25 52.9E</Y> Example: For the default WGS84 CRS the presentation format is Degrees Minutes Seconds Hemisphere Note: (DMSH), with fields separated by a space character and with leading zeros added to any minute or second values less than 10. Note that in the WGS84 CRS 'Y' denotes the longitude of a position.
OMA-TS-MLP-V3_2-20051124-C
Page 95 (128)
5.3.87
Description: third ordinate in a coordinate system which has at least three ordinates Element Type: Char string Format: Defined values: Default value: <Z>498</Z> Example: The default Coordinate Reference System WGS84 (#4326 of the EPSG database) uses an Note: "Ellipsoidal 2D Coordinate System". This means for a potential altitude value the parameter 'alt' (cf. 5.3.2 of MLP) is used.
5.3.88
5.3.88.1
Service attributes
res_type
Description: Defines a response type at the Standard Location and Emergency Immediate Service. This attribute applies to the Standard Immediate Location Request message and the Emergency Immediate Location Request message. Attribute Type: Char string Format: SYNC A LCS Client requests to receive the location response in one response Defined values: ASYNC A LCS Client allows to receive the location responses in pieces using several consecutive connections initiated by the location Server SYNC Default value: <slir ver="3.2.0" res_type="SYNC"> Example: Note:
5.3.88.2
ver
Description: Defines the version of the location protocol. This attribute is valid for ALL messages Element Type: Char string Format: [1-9]+[0-9]*.[0-9]+.[0-9]+ Defined values: Default value: <slia ver="3.0.0"> Example: Note:
OMA-TS-MLP-V3_2-20051124-C
Page 96 (128)
5.4
5.4.1
Result codes
Result codes
This table defines the result codes that indicate the result of the request or individual positioning. The error codes are divided in ranges: 0 100 200 300 500 600 99 199 299 499 599 699 Location server specific errors Request specific errors Network specific errors Reserved for future use Vendor specific errors MLS Client specific errors
Note: For privacy reasons it might be needed to not report certain specific errors. In this case it is up to the implementation or configuration of the location server which errors will be reported.
Resid 0 1 2
Slogan OK SYSTEM FAILURE UNSPECIFIED ERROR
UNAUTHORIZED APPLICATION
4 5 6 7 101
UNKNOWN SUBSCRIBER ABSENT SUBSCRIBER POSITION METHOD FAILURE TIMEOUT CONGESTION IN LOCATION SERVER UNSUPPORTED VERSION TOO MANY POSITION ITEMS FORMAT ERROR SYNTAX ERROR PROTOCOL ELEMENT NOT SUPPORTED
Description No error occurred while processing the request. The request can not be handled because of a general problem in the location server. An unspecified error used in case none of the other errors apply. This can also be used in case privacy issues prevent certain errors from being presented The requesting location-based application is not allowed to access the location server or a wrong password has been supplied. Unknown subscriber. The user is unknown, i.e. no such subscription exists. Absent subscriber. The user is currently not reachable. Position method failure. The location service failed to obtain the users position. Timer expiry for the requested event trigger The request can not be handled due to congestion in the location server. The Location server does not support the indicated protocol version. Too many position items have been specified in the request. A protocol element in the request has invalid format. The invalid element is indicated in ADD_INFO. The position request has invalid syntax. Details may be indicated in ADD_INFO. A protocol element specified in the position request is not supported by the Location Server, or the position result is not supported by the LCS Client. The element is indicated in ADD_INFO. The requested service is not supported in the Location Server. The service is indicated in ADD_INFO. A protocol element attribute is not supported in the Location
103 104 105 106 107
108 109
SERVICE NOT SUPPORTED PROTOCOL ELEMENT ATTRIBUTE
OMA-TS-MLP-V3_2-20051124-C
Page 97 (128)
110 111 112
NOT SUPPORTED INVALID PROTOCOL ELEMENT VALUE INVALID PROTOCOL ELEMENT ATTRIBUTE VALUE PROTOCOL ELEMENT VALUE NOT SUPPORTED PROTOCOL ELEMENT ATTRIBUTE VALUE NOT SUPPORTED CANCELLATION OF TRIGGERED LOCATION REQUEST QOP NOT ATTAINABLE POSITIONING NOT ALLOWED
113
114 201 202
Server. The attribute is indicated in ADD_INFO. A protocol element in the request has an invalid value. The element is indicated in ADD_INFO. A protocol element attribute in the request has a wrong value. The element is indicated in ADD_INFO. A specific value of a protocol element is not supported in the Location Server. The element and value are indicated in ADD_INFO. A specific value of a protocol element attribute is not supported in the Location Server. The attribute and value are indicated in ADD_INFO. The requested triggered location report is cancelled The requested QoP cannot be provided. The subscriber does not allow the application to position him/her for whatever reason (privacy settings in location server, LCS privacy class). The request can not be handled due to congestion in the mobile network. The location request is disallowed by local regulatory requirements. The location server is not completely configured to be able to calculate a position. The triggered Location Request has been aborted due to that target has moved to another MSC/SGSN. This result code shall only be used towards The Home Location Server. Restrictions: - This code SHALL only be used in RLP. - This result code shall only be used towards The Home Location Server. Vendor specific errors The MLS Client does not support the standard location report service. An error occurred in the MLS Client. The standard location report was not accepted by the MLS Client The subscriber in the Standard Location Report is not valid to the MLS Client The service identity in the Standard Location Report is not valid to the MLS Client
203 204 207 208
CONGESTION IN MOBILE NETWORK DISALLOWED BY LOCAL REGULATIONS MISCONFIGURATION OF LOCATION SERVER TARGET MOVED TO NEW MSC/SGSN
500 -599 601 602 603 604 STANDARD LOCATION REPORT SERVICE NOT SUPPORTED MLS CLIENT ERROR STANDARD LOCATION REPORT SERVICE NOT ACCEPTED SUBSCRIBER IN IN STANDARD LOCATION REPORT SERVICE NOT VALID INVALID SERVICE ID IN STANDARD LOCATION REPORT SERVICE
605
OMA-TS-MLP-V3_2-20051124-C
Page 98 (128)
5.5
5.5.1
Adaptation to 3GPP LCS (Informative)

Version mapping between 3GPP TS23.271 and this specification
The following table shows the version number of this specification ( OMA-TS-MLP-V3_2) fully conforming to a certain version of 3GPP TS23.271, i.e. the version of this specification for the correct reference in a certain version of the 3GPP specification.
3GPP TS23.271 version number Release 5 Release 6 Note:
Conforming version number of OMA-LOC_MLP_Spec-V3_2 Version 3.1 Version 3.2
In case there are versions not appearing in this table, it should be interpreted that such update did not affect the other specification. That is, the version number not appearing in the table should apply to the conformance mapping for the closest smaller version number in the table.
5.5.2
The terminology mapping table with 3GPP LCS Specifications
The following is a list of the terms in MLP used differently from the ones defined for 3GPP:
Term MLP Location Server MS (Mobile Station) MSID (Mobile Station Identifier) MPC (Mobile Positioning Centre) 3GPP LCS Server UE Identification of the target UE
Notes
There is no term applicable to 3GPP.
5.5.3
The corresponding terms used for the location procedures in 3GPP LCS Definition
The following is a list of terms defined in MLP corresponding to the 3GPP LCS definition [23.271] for the location procedures.
Location procedures defined in 3GPP[23.271] Circuit Switched Mobile LCS Service Request Terminating Location Request CS-MT-LR LCS Service Response CS-MT-LR without HLR Query applicable to North America Emergency Calls only Packet Switched Mobile Terminating Location Request PS-MT-LR LCS Service Request LCS Service Response LCS Service Request LCS Service Response
Services defined in MLP Standard Location Immediate Request Standard Location Immediate Answer Emergency Location Immediate Request Emergency Location Immediate Answer Standard Location Immediate Request Standard Location Immediate Answer
OMA-TS-MLP-V3_2-20051124-C
Page 99 (128)
Location procedures defined in 3GPP[23.271] Network Induced Location Request Location Information NI-LR Packet Switched Network Induced Location Information Location Request PS-NI-LR Mobile Terminating Deferred LCS Service Request Location Request LCS Service Response(Provide Subscriber Location ack) LCS Service Response(Subscriber Location Report) Combined Periodical/Deferred LCS Service Request Mobile Terminating Location Request LCS Service Response(Provide Subscriber Location ack) LCS Service Response(Subscriber Location Report) Cancellation of a Deferred Location LCS Cancel Service Request Request LCS Cancel Service Response Mobile Originating Location Request, Circuit Switched CS-MO-LR Mobile Originating Location Request, Packet Switched PS-MO-LR Location Information Location Information Ack Location Information Location Information Ack
Services defined in MLP Emergency Location Report Emergency Location Report
Triggered Location Reporting Request Triggered Location Reporting Answer Triggered Location Report Triggered Location Reporting Request Triggered Location Reporting Answer Triggered Location Report Triggered Location Reporting Stop Request Triggered Location Reporting Stop Answer Standard Location Report Standard Location Report Answer Standard Location Report Standard Location Report Answer
5.5.4
Error Mapping (Informative)
The following list provides a mapping between the errors defined for LCS in MAP (see [29.002]) and MLP (see section 5.4)
MAP error Unknown subscriber Unidentified Subscriber Absent Subscriber System failure Facility Not Supported Unexpected Data Value Data missing Unauthorised LCS Client with detailed reason Position method failure with detailed reason. Illegal Subscriber Illegal Equipment Unauthorized requesting network
MLP resid 4 4 5 1 6 1 1 3 6 2 2 2
OMA-TS-MLP-V3_2-20051124-C
Page 100 (128)
5.6
HTTP Mapping
This section describes how to use MLP over the HTTP transport mechanism using "HTTP/1.1". HTTP is a request/response protocol involving a server and a client. In the context of MLP, the client is referred to as the LCS Client and the server is the Location Server (GMLC/MPC). For more information about HTTP, refer to [RFC2616] and http://www.w3.org. The Location Server MAY provide two socket ports for operation, one for encryption with SSL/TLS and one without. The reason for having one insecure port is that encryption can consume resources, and if the client is in a secure domain there might not be a need for encryption. Applications residing in an insecure domain, i.e. on the Internet, may use the secure port to ensure the security and privacy of the location information. For further information about SSL/TLS see [RFC2246]. Four port numbers have been selected and proposed as standard ports for location servers implementing MLP. These ports are registered with IANA (Internet Assigned Numbers Authority, see [IANA]). The four port numbers are: lif-mlp lif-mlp lif-mlp-s lif-mlp-s 9210/tcp 9210/udp 9211/tcp 9211/udp LIF Mobile Locn Protocol LIF Mobile Locn Protocol LIF Mobile Locn Secure LIF Mobile Locn Secure
A Location Server MAY choose to introduce any other socket based or HTTP transparent technology for secure transfers. Any such technology SHALL be provided over a different port than the four mentioned above.
5.6.1
Location Services using HTTP
An LCS Client SHALL request a Location Service by issuing an HTTP POST request towards the Location Server. For more information about HTTP POST, see [RFC2616]. The request line syntax is shown below. Request-line = POST SP path SP HTTP/1.1 CRLF
The request MUST include the entity-header Content-length field as part of the request. The message body of the request SHALL include the XML formatted request and SHALL have the length specified by the LCS Client in the Content-length field. If the request is a triggered request the result SHALL be delivered to the LCS client through an HTTP POST operation issued by the Location Server. This implies that the LCS client MUST be able to receive HTTP POST requests and give a valid response. All Location Services are invoked by sending a request using HTTP POST to a certain URI. An example of an URI is shown below. http:// location-server.example.com:9210/LocationQueryService/ The response to the invocation of a Location Service SHALL be returned using an HTTP response. If the LCS client requests standard location of asynchronous mode, triggered reporting of location, the Location Server SHALL return the report by performing an HTTP POST operation towards the client. The client must specify the URI that the answer should be posted to. This is done in the service request or by having it in the LCS client profile that can be stored in the Location Server. The report SHALL be included in the message body and the Content-length entity SHALL be set to the length of the answer. When an LCS client attempts to invoke a service request that is not defined in this specification, the Location Server SHALL return a General Error Message (GEM) in a HTTP '404' error reponse: Status-Line= HTTP/1.1 SP 404 SP Not Found CRLF
OMA-TS-MLP-V3_2-20051124-C
Page 101 (128)
5.6.2
Request and Response Encapsulation
A request SHALL have a header part and a body part. A response MAY have a header part and SHALL have a body part. To be able to make a location request with a single XML document the header and the body are encapsulated in the same service initiation DTD. The context header holds the authentication and authorization data pertinent to a particular location request. The body part is described in the sections 5.2.3.2- 5.2.3.6.
OMA-TS-MLP-V3_2-20051124-C
Page 102 (128)
5.6.2.1
Service Initiation DTD
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_init PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_init> ... </svc_init> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT <!ATTLIST % extension.message svc_init svc_init ver CDATA ""> (hdr, (slir | eme_lir | tlrr | tlrsr %extension.message;))> #FIXED "3.2.0"> SYSTEM "MLP_CTXT_320.DTD"> SYSTEM "MLP_ID_320.DTD"> SYSTEM "MLP_FUNC_320.DTD"> SYSTEM "MLP_QOP_320.DTD"> SYSTEM "MLP_LOC_320.DTD"> SYSTEM "MLP_SHAPE_320.DTD"> SYSTEM "MLP_GSM_NET_310.DTD"> SYSTEM "MLP_HDR_320.DTD"> SYSTEM "MLP_SLIR_320.DTD"> SYSTEM "MLP_EME_LIR_320.DTD"> SYSTEM "MLP_TLRR_320.DTD"> SYSTEM "MLP_TLRSR_320.DTD">
<!ENTITY % mlp_ctxt.dtd %mlp_ctxt.dtd; <!ENTITY % mlp_id.dtd %mlp_id.dtd; <!ENTITY % mlp_func.dtd %mlp_func.dtd; <!ENTITY % mlp_qop.dtd %mlp_qop.dtd; <!ENTITY % mlp_loc.dtd %mlp_loc.dtd; <!ENTITY % mlp_shape.dtd %mlp_shape.dtd; <!ENTITY % mlp_gsm_net_param.dtd %mlp_gsm_net_param.dtd; <!ENTITY % mlp_hdr.dtd %mlp_hdr.dtd; <!ENTITY % mlp_slir.dtd %mlp_slir.dtd; <!ENTITY % mlp_eme_lir.dtd %mlp_eme_lir.dtd; <!ENTITY % mlp_tlrr.dtd %mlp_tlrr.dtd; <!ENTITY % mlp_tlrsr.dtd %mlp_tlrsr.dtd;
OMA-TS-MLP-V3_2-20051124-C
Page 103 (128)
Example
<?xml version="1.0" ?> <!DOCTYPE svc_init SYSTEM "MLP_SVC_INIT_320.DTD"> <svc_init ver="3.2.0"> <hdr ver="3.2.0"> ... </hdr> <slir ver="3.2.0">> ... </slir </svc_init>
5.6.2.2
Service Result DTD
OMA-TS-MLP-V3_2-20051124-C
Page 104 (128)
 <!-MLP V3.2 Document Type Definition Copyright Open Mobile Alliance Ltd., 2005 All rights reserved MLP is an XML language. Typical usage: <?xml version="1.0"?> <!DOCTYPE svc_result PUBLIC "-//OMA//DTD {abbrev x.y}//EN" "http://www.openmobilealliance.org/DTD/{filename}" [<?oma-{ref}-ver supported-versions="{versions}"?>]> <svc_result> ... </svc_result}> Terms and conditions of use are available from the Open Mobile Alliance Ltd. web site at http://www.openmobilealliance.org/ --> <!ENTITY <!ELEMENT % extension.message svc_result ""> (hdr?, (slia | slirep | slrep | slra | eme_lia | emerep | eme_lirep | tlra | tlrep | tlrsa %extension.message;))>
<!ATTLIST
svc_result ver CDATA
#FIXED "3.2.0">
<!ENTITY % mlp_ctxt.dtd SYSTEM "MLP_CTXT_320.DTD"> %mlp_ctxt.dtd; <!ENTITY % mlp_id.dtd SYSTEM "MLP_ID_320.DTD"> %mlp_id.dtd; <!ENTITY % mlp_func.dtd SYSTEM "MLP_FUNC_320.DTD"> %mlp_func.dtd; <!ENTITY % mlp_qop.dtd SYSTEM "MLP_QOP_320.DTD"> %mlp_qop.dtd; <!ENTITY % mlp_loc.dtd SYSTEM "MLP_LOC_320.DTD"> %mlp_loc.dtd; <!ENTITY % mlp_shape.dtd SYSTEM "MLP_SHAPE_320.DTD"> %mlp_shape.dtd; <!ENTITY % mlp_gsm_net_param.dtd SYSTEM "MLP_GSM_NET_310.DTD"> %mlp_gsm_net_param.dtd; <!ENTITY % mlp_slra.dtd SYSTEM "MLP_SLRA_320.DTD"> %mlp_slra.dtd; <!ENTITY % mlp_hdr.dtd SYSTEM "MLP_HDR_320.DTD"> %mlp_hdr.dtd; <!ENTITY % mlp_slia.dtd SYSTEM "MLP_SLIA_300.DTD"> %mlp_slia.dtd; <!ENTITY % mlp_slirep.dtd SYSTEM "MLP_SLIREP_300.DTD"> %mlp_slirep.dtd; <!ENTITY % mlp_slrep.dtd SYSTEM "MLP_SLREP_300.DTD"> %mlp_slrep.dtd; <!ENTITY % mlp_eme_lia.dtd SYSTEM "MLP_EME_LIA_320.DTD"> %mlp_eme_lia.dtd; <!ENTITY % mlp_eme_lirep.dtd SYSTEM "MLP_EME_LIREP_320.DTD"> %mlp_eme_lirep.dtd; <!ENTITY % mlp_emerep.dtd SYSTEM "MLP_EMEREP_300.DTD"> %mlp_emerep.dtd; <!ENTITY % mlp_tlra.dtd SYSTEM "MLP_TLRA_320.DTD"> %mlp_tlra.dtd; <!ENTITY % mlp_tlrep.dtd SYSTEM "MLP_TLREP_320.DTD"> 2011 Open Mobile %mlp_tlrep.dtd; Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance SYSTEM "MLP_TLRSA_300.DTD"> document. Ltd. under the terms as stated in this <!ENTITY % mlp_tlrsa.dtd %mlp_tlrsa.dtd;
OMA-TS-MLP-V3_2-20051124-C
Page 105 (128)
Example
<?xml version="1.0" ?> <!DOCTYPE svc_result SYSTEM "MLP_SVC_RESULT_320.DTD"> <svc_result ver="3.2.0"> <slia ver="3.0.0"> ... </slia> </svc_result>
5.6.2.3
Message Sequence Diagram
The following HTTP sequence (cf. Figure 8) is used for all the defined service requests/responses in MLP.
LCS Client Location Server
HTTP POST (Service Initiation(hdr, body))
HTTP Response (Service Result(hdr?, body))
Figure 8: HTTP sequence for MLP request/response pairs The following HTTP sequence diagram (cf. Figure 9) is used for all defined reports in MLP except for Standard Location Report.
HTTP POST (Service Result(hdr, body))
HTTP Response ()
Figure 9: HTTP sequence for MLP reports
OMA-TS-MLP-V3_2-20051124-C
Page 106 (128)
The following HTTP sequence diagram (cf. Figure 10) is used for the report and answer in Standard Location Reporting Service.
HTTP POST (Service Result(hdr, body))
HTTP Response (Service Result(hdr, body))
Figure 10: HTTP sequence for MLP Standard Location Reporting Service. The following HTTP sequence diagram (cf. Figure 11) is used in the case of a General Error Message.
HTTP POST (Unknown Request)
HTTP Error Response (GEM)
Figure 11: HTTP sequence for the General Error Message
5.7
5.7.1
Geographic Information
Coordinate Reference systems (Informative)
The study of determining the relative positions on or close to the surface of the earth is a complex science, referred to as geodesy. A complete definition of Coordinate Reference systems is not within the scope of this standard. This section includes a brief overview of the subject. For more details see the OpenGIS Consortium Abstract Specification Topic 2 [AST].
5.7.1.1
The Geoid, ellipsoids and datums
The Geoid is a physically realizable surface defined by the set of points with equal gravity potential approximately at the Mean Sea Level. While this surface is measurable it is not easy to define mathematically. In order to use known mathematics, the Geoid is approximated by an ellipsoid (spheroid). There are many ellipsoids, each defined to best approximate some part of the Geoid. These ellipsoids are defined by an ellipse that is rotated about the major axis. There are many methods for defining an ellipse, the most common used in Geodesy the length of the semi-major axis and the flattening. This defines a mathematical ellipsoid for calculations. it does not provide enough information to locate the ellipsoid with respect to the Geoid or other ellipsoids. To locate the ellipsoid in space a datum is defined. Some of the common ellipsoids are WGS84, Bessel1841, Clark 1866. A datum is the ellipsoid with it's position in space. The position is defined by the origin and orientation of the ellipsoid with respect to the Geoid. Different datums locate latitude, longitude at different positions in space. For example ellipsoids Samboja, CH1903 and Stockholm are each based on Bessel1841, the National Geodetic Network and World Geodetic System 1984 are based on WGS84.
OMA-TS-MLP-V3_2-20051124-C
Page 107 (128)
5.7.1.2
Coordinate systems
A coordinate system is the link between the datum and the coordinate values. It defines all of the information about the axes system that defines the values. The names of the axes, their units (formats), the order of ordinates ((Easting, Northing) versus (Northing, Easting)) and the angle between the axes are defined by the coordinate system.
5.7.1.2.1
Cartesian coordinate systems
A Cartesian coordinate system is defined by values of (x,y,(z)). x is the distance from the x-axis, y is the distance from the yaxis, z the distance from the z-axis.The axis are orthogonal to each other. The unit used for x, y, z are a distance unit, such as meter. These coordinate systems are used for flat 'planar' descriptions of points. In general they are used over small areas where a projection method has been used to minimize distortions of the geography in the area.
5.7.1.2.2
Ellipsoid coordinates
More global geographic calculations need to take the surface of the earth into account. So we need a second coordinate system that describes each position relative to other points and lines on the earths surface. Each point can then be described as set of values (longitude, latitude) or (longitude, latitude, altitude) giving a point on the ellipsoid or relative to the ellipsoid we choose to describe the earth (cf. Figure 12). The longitude tells us how far east we have to move on the equator from the null-meridian, the latitude tells us how far north to move from the equator and the altitude tells us how far above the ellipsoid to go to finally reach the location. Negative values direct us to go in the opposite direction.
Figure 12: Ellipsoid Coordinates
5.7.1.3
Coordinate Reference Systems
The two coordinate reference systems relevant to this protocol are Geographic 2D Coordinate Reference Systems and Projected Coordinate Reference Systems. Geographic 2D Coordinate Reference Systems describe locations on the ellipsoid. They are used for large national or continental geodetic networks. In particular GPS uses the Geographic 2D Coordinate Reference System WGS84. This uses the World Geodetic System 1984 based on the WGS84 ellipsoid. The coordinate axes have units of decimal degrees (or DMSH) with ordinate order (Northing, Easting). This Coordinate Reference System is the default for all basic MLP service requests and responses. A GMLC is only required to support WGS84. The GMLC geographies that are defined with altitude are modeled in this protocol as geographies in a Geographic 2D CRS with a separate altitude element, not as a Geographic 3D CRS. The geographies are planar and carrying a constant z value is not desirable.
OMA-TS-MLP-V3_2-20051124-C
Page 108 (128)
There are several ways to convert ellipsoid coordinates to 2 dimensional cartesian coordinates. These are called projection methods. Each method is designed to minimize some type of distortion in the mapping for the ellipsoid to the 2D Cartesian coordinate system. Projected Coordinate Reference Systems are used for map display, to allow Cartesian mathematics and for Advanced Location Services.
5.7.2
Coordinate Reference System Transformations (Informative)
A transformation is used to define a point in one CRS into the appropriate values in a second CRS. When the datums are the same, the transformation can frequently be defined by equations. A transformation from one datum to another is usually done with a least squares approximation. Transformation equations are available in from several places, transformation services are also available.
5.7.3
Methodology for defining CRSs and transformations in this protocol (Informative)
The MLP protocol defines the CRS by citing an authority and the unique reference identifier for the CRS defined by this authority. This leaves the definition of many CRS used over the world to be defined by a group of geodesy experts. This methodology is used by the OpenGIS Consortium and the ISO TC 211 working group for well-known CRS. The encoding used is from the OpenGIS Consortium Recommendation Paper 01-014r5: Recommended Definition Data for Coordinate Reference Systems and Coordinate Transformations [CRS]. The MLP protocol may use the {EPSG} authority as an example. Support of other authority is for further study. This database is defined by a Microsoft Access database which can be found at www.epsg.org. An xml version of this database will be available at http://www.opengis.net/gml/srs/epsg.xml in the future. The default WGS84 CRS is defined to be 4326 by the EPSG authority. Other examples are 326xx define the UTM xx N zones. EPSG recommends that real numbers are used for internal data processing but that for interfacing with human beings the preferred representation be degree, minute, second, hemisphere (DMSH). For geographic coordinate reference systems with coordinate systems in degrees. Where the value is held in several fields, as for example in DMSH representation, various symbols, words or character strings are in use as field identifiers and separators. For DMSH representation EPSG recommends that the degree, minute and second units are indicated through the suffixed symbols ' " (ASCII character codes 186, 39 and 34) respectively, for example 3545'09.18"N, 6545'09.18"W. Spaces are excluded from the separator and for minute and second values under 10 leading zeroes are included.
5.7.4 5.7.5
Supported coordinate systems and datum (Normative) Shapes representing a geographical position (Informative)
All MLP implementations MUST support at least the WGS84 Coordinate Reference System.
There are a number of shapes used to represent a geographic area that describes where a mobile subscriber is located. There are additional shapes that are required for advanced MLP services. The standards bodies for geographic data for advanced MLP services such as routing, geocoding, coordinate conversion, and map display are the Location Interoperability Forum, the OpenGIS Consortium and the ISO TC211 working group. The current public XML specification defining geography from these groups is GML V211 [GML]. These two groups work together and are working towards a GML V3 with additional geometry and topology types. The geometry required for the MLP is the GMLV211 with additional polygon types with boundaries that contain circles, ellipses or circular arcs. GML V3 will define the linear curves segments to allow these polygons to be defined. These boundaries will be defined as special cases of polygons, using the given interpolation methods. The following geographies are defined in this protocol. The relevant OGC Abstract Specification is Topic 1 [GEO].
OMA-TS-MLP-V3_2-20051124-C
Page 109 (128)
5.7.5.1
Ellipsoid point
This a point on the ellipsoid and is modeled as a point in a Geographic 2D Coordinate Reference Systems.
5.7.5.2
Ellipsoid point with uncertainty circle
An ellipsoid point with uncertainty circle is characterized by the coordinates of an ellipsoid point (the origin) and a radius, r (cf. Figure 13). It describes the set of points on the ellipsoid, which are at a distance from the point of origin less than or equal to r. This shape can be used to indicate points on the Earth surface, or near the Earth surface. This shape is a special case of a polygon with no interior boundaries. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy.
Figure 13: Ellipsoid point with uncertainty circle
5.7.5.3
-
Ellipsoid point with uncertainty ellipse
The shape of an "ellipsoid point with uncertainty ellipse" is characterized by the following (cf. Figure 14): The coordinates of an ellipsoid point (the origin) The distances r1 and r2 The angle of orientation A
It describes formally the set of points on the ellipsoid, which fall within or on the boundary of an ellipse. This ellipse has a semi-major axis of length r1 oriented at angle A (0 to 180) measured clockwise from north and a semi-minor axis of length r2. The distances being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points, as shown in figure below. As for the ellipsoid point, this can be used to indicate points on the Earths surface, or near the Earths surface, of same latitude and longitude. This shape is a special case of a polygon with no interior boundaries. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy, but the geometrical contributions to uncertainty can be quantified.
OMA-TS-MLP-V3_2-20051124-C
Page 110 (128)
North
angle, A semi-major axis, r1
semi-minor axis, r2
Figure 14: Ellipsoid point with uncertainty ellipse
5.7.5.4
-
Ellipsoid point with uncertainty arc
The shape of an "ellipsoid point with uncertainty arc" is characterized by the following (cf. Figure 15): The coordinates of an ellipsoid point (the origin) The inner radius(r1) and uncertainty radius(r2), The offset angle () and included angle ()
An arc is defined by a point of origin with one offset angle and one uncertainty angle plus one inner radius and one uncertainty radius. In this case the striped area describes the actual arc area. The smaller arc defines the inner radius(r1) and the difference between inner and the outer arc defines the uncertainty radius(r2). This shape is a special case of a polygon with no interior boundaries.
North 0?
r1 r2
Figure 15: Ellipsoid point with uncertainty arc
5.7.5.5
Polygon
A Polygon is a connected surface. Any pair of points in the polygon can be connected to one another by a path. The boundary of the Polygon is a set of LinearRings. We distinguish the outer (exterior) boundary and the inner (interior) boundaries; the
OMA-TS-MLP-V3_2-20051124-C
Page 111 (128)
LinearRings of the interior boundary cannot cross one another and cannot be contained within one another. There must be at most one exterior boundary and zero or more interior boundary elements. The ordering of LinearRings and whether they form clockwise or anti-clockwise paths is not important. The minimum number of points allowed in a LinearRing is 3. A LinearRing is a closed, simple piece-wise linear path which is defined by a list of coordinates that are assumed to be connected by straight line segments. The last coordinate must be coincident with the first coordinate and at least four coordinates are required (the three to define a ring plus the fourth duplicated one). This geometry is only used in the construction of a Polygon. For basic MLP services polygons are the number of interior bondaries MUST be 0. Also to conform to [23.032] the maximum number of points allowed in an exterior boundary is 15. The points shall be connected in the order that they are given. The described area is situated to the right of the exterior boundaries and left of the interior boundaries with the downward direction being toward the Earths center and the forward direction being from a point to the next.
Note:
This definition does not permit connecting lines greater than roughly 20 000 km. If such a need arises, the polygon can be described by adding an intermediate point.
Computation of geodesic lines is not simple. Approximations leading to a maximum distance between the computed line and the geodesic line of less than 3 meters are acceptable.
5.7.5.6
LineString
A LineString is a piece-wise linear path defined by a list of coordinates that are assumed to be connected by straight line segments. A closed path is indicated by having coincident first and last coordinates. At least two coordinates are required.
5.7.5.7
Box
The Box element is used to encode extents. Each <Box> element encloses a sequence of two <coord> elements containing exactly two coordinate tuples; the first of these is constructed from the minimum values measured along all axes, and the second is constructed from the maximum values measured along all axes
5.7.5.8
Geometries Collections
These are geometry objects that contain 2 or more primitive geometry objects. These collections can either be homogenous, a set of points, or heterogeneous, a point, circularArea and a LineString. Geometry collections are not valid for the basic MLP services.
OMA-TS-MLP-V3_2-20051124-C
Page 112 (128)
Appendix A. Change History

A.1 Approved Version History
Reference
OMA-TS-MLP-V3_2
(Informative)
Description
No prior version or- No previous version within OMA
Date
19 Jul 2011
OMA-TS-MLP-V3_2-20051124-C
Page 113 (128)
Appendix B. Static Conformance Requirements

The notation used in this appendix is specified in [IOPPROC].
(Normative)
B.1
SCR for Client

Item Function Reference Status Requirement
B.1.1 Service Initiation DTD

MLP-A-C-001 MLP-A-C-002 MLP-A-C-003 MLP-A-C-004 MLP-A-C-005 MLP-A-C-006 MLP-A-C-007 Service Initiation Header Standard Location Immediate Request Emergency Location Immediate Request Triggered Location Reporting Request Triggered Location Reporting Stop Request Extension Message 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 M M O O O O O MLP-A-C-002 AND MLP-A-C-003 MLP-B-C-003 AND MLP-B-C-004 MLP-B-C-007 MLP-B-C-010 AND MLP-B-C-011 AND MLP-B-C-012 MLP-B-C-012
B.1.2 Service Result DTD

MLP-B-C-001 MLP-B-C-002 MLP-B-C-003 MLP-B-C-004 MLP-B-C-005 MLP-B-C-006 MLP-B-C-007 MLP-B-C-008 MLP-B-C-009 MLP-B-C-010 MLP-B-C-011 MLP-B-C-012 MLP-B-C-013
Service Result Header Standard Location Immediate Answer Standard Location Immediate Report Standard Location Report Standard Location Report Answer Emergency Location Immediate Answer Emergency Location Immediate Report Emergency Location Report Triggered Location Reporting Answer Triggered Location Report Triggered Location Reporting Stop Answer Extension Message
5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2
M O O O O O O O O O O O O
MLP-B-C-002 AND MLP-B-C-003
MLP-B-C-007
MLP-B-C-011 MLP-B-C-010
OMA-TS-MLP-V3_2-20051124-C
Page 114 (128)
B.1.3 Header
MLP-C-C-001 MLP-C-C-002 MLP-C-C-003 MLP-C-C-004
client sessionid subclient requestor
5.2.3.1 5.2.3.1 5.2.3.1 5.2.3.1
M O O O
B.1.4 Standard Location Immediate Request

MLP-D-C-001 MLP-D-C-002 MLP-D-C-003 MLP-D-C-004 MLP-D-C-005 MLP-D-C-006 MLP-D-C-007 MLP-D-C-008 MLP-D-C-009 MLP-D-C-010 MLP-D-C-011 MLP-D-C-012
msids msid codeword gsm_net_param trans_id eqop geo_info loc_type prio pushaddr service_coverage extension parameter
5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1
O M O O O O O O O O O O
B.1.5 Standard Location Immediate Answer

MLP-E-C-001 MLP-E-C-002 MLP-E-C-003 MLP-E-C-004 MLP-E-C-005
pos req_id result add_info extension parameter
5.2.3.2.2 5.2.3.2.2 5.2.3.2.2 5.2.3.2.2 5.2.3.2.2
M O M O O
B.1.6 Standard Location Immediate Report

MLP-F-C-001 MLP-F-C-002 MLP-F-C-003
req_id pos extension parameter
5.2.3.2.3 5.2.3.2.3 5.2.3.2.3
M M O
MLP-E-C-002
B.1.7 Emergency Location Immediate Request

MLP-G-C-001 MLP-G-C-002
msids msid
5.2.3.3.1 5.2.3.3.1
O M
OMA-TS-MLP-V3_2-20051124-C
Page 115 (128)
Item
Function
Reference
Status
Requirement
MLP-G-C-003 MLP-G-C-004 MLP-G-C-005 MLP-G-C-006 MLP-G-C-007 MLP-G-C-008 MLP-G-C-009 MLP-G-C-010 MLP-G-C-011
gsm_net_param trans_id esrd esrk eqop geo_info loc_type pushaddr extension parameter
5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1
O O O O O O O O O
B.1.8 Emergency Location Immediate Answer

MLP-H-C-001 MLP-H-C-002 MLP-H-C-003 MLP-H-C-004 MLP-H-C-005
eme_pos req_id result add_info extension parameter
5.2.3.3.2 5.2.3.3.2 5.2.3.3.2 5.2.3.3.2 5.2.3.3.2
M O M O O
B.1.9 Emergency Location Immediate Report

MLP-I-C-001 MLP-I-C-002 MLP-I-C-003 MLP-I-C-004 MLP-I-C-005
req_id eme_pos result add_info extension parameter
5.2.3.3.3 5.2.3.3.3 5.2.3.3.3 5.2.3.3.3 5.2.3.3.3
M M M O O
MLP-H-C-002
B.1.10 Standard Location Report

MLP-J-C-001 MLP-J-C-002
pos extension parameter
5.2.3.4.1 5.2.3.4.1
M O
B.1.11 Standard Location Report Answer

MLP-K-C-001 MLP-K-C-002 MLP-K-C-003
result add_info extension parameter
5.2.3.4.2 5.2.3.4.2 5.2.3.4.2
M O O
OMA-TS-MLP-V3_2-20051124-C
Page 116 (128)
B.1.12 Emergency Location Report

MLP-L-C-001 MLP-L-C-002
eme_event extension parameter
5.2.3.5.1 5.2.3.5.1
M O
B.1.13 Triggered Location Reporting Request

MLP-M-C-001 MLP-M-C-002 MLP-M-C-003 MLP-M-C-004 MLP-M-C-005 MLP-M-C-006 MLP-M-C-007 MLP-M-C-008 MLP-M-C-009 MLP-M-C-010 MLP-M-C-011 MLP-M-C-012 MLP-M-C-013
msids interval start_time stop_time duration tlrr_event qop geo_info pushaddr loc_type prio service_coverage extension parameter
5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1
B.1.14 Triggered Location Reporting Answer

MLP-N-C-001 MLP-N-C-002 MLP-N-C-003 MLP-N-C-004 MLP-N-C-005
req_id result add_info extension parameter lcs_ref
5.2.3.6.2 5.2.3.6.2 5.2.3.6.2 5.2.3.6.2 5.2.3.6.2
M M O O O
B.1.15 Triggered Location Report

MLP-O-C-001 MLP-O-C-002 MLP-O-C-003 MLP-O-C-004 MLP-N-C-005
req_id trl_pos time_remaining extension parameter lcs_ref
5.2.3.6.3 5.2.3.6.3 5.2.3.6.3 5.2.3.6.3 5.2.3.6.3
M M O O O
OMA-TS-MLP-V3_2-20051124-C
Page 117 (128)
B.1.16 Triggered Location Reporting Stop Request

MLP-P-C-001 MLP-P-C-002 MLP-P-C-003
req_id extension parameter lcs_ref
5.2.3.6.4 5.2.3.6.4 5.2.3.6.4
M O O
B.1.17 Triggered Location Reporting Stop Answer

MLP-Q-C-001 MLP-Q-C-002 MLP-Q-C-003 MLP-Q-C-004
req_id result add_info extension parameter
5.2.3.6.5 5.2.3.6.5 5.2.3.6.5 5.2.3.6.5
M M O O
B.1.18 Support for Identity Elements

MLP-R-C-001 MLP-R-C-002 MLP-R-C-003 MLP-R-C-004 MLP-R-C-005 MLP-R-C-006 MLP-R-C-007 MLP-R-C-008 MLP-R-C-009 MLP-R-C-010
msid msid_range msids codeword esrd esrk session start_msid stop_msid trans_id
5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1
M O O O O O O O O O
B.1.19 Support for Function Elements

MLP-S-C-001 MLP-S-C-002 MLP-S-C-003 MLP-S-C-004 MLP-S-C-005 MLP-S-C-006 MLP-S-C-007 MLP-S-C-008 MLP-S-C-009 MLP-S-C-010 MLP-S-C-011 MLP-S-C-012 MLP-S-C-013
eme_event tlrr_event ms_action change_area target_area no_of_reports name_area plmn interval loc_type prio pushaddr req_id
5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2
O O O O O O O O O O O O O
OMA-TS-MLP-V3_2-20051124-C
Page 118 (128)
Item
Function
Reference
Status
Requirement
MLP-S-C-014 MLP-S-C-015 MLP-S-C-016 MLP-S-C-017 MLP-S-C-018 MLP-S-C-019
start_time stop_time duration url time_remaining lcs_ref
5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2
O O O O O O
B.1.20 Support for Location Elements

MLP-T-C-001 MLP-T-C-002 MLP-T-C-003 MLP-T-C-004 MLP-T-C-005 MLP-T-C-006 MLP-T-C-007 MLP-T-C-008 MLP-T-C-009 MLP-T-C-010 MLP-T-C-011 MLP-T-C-012 MLP-T-C-013 MLP-T-C-014 MLP-T-C-015 MLP-T-C-016 MLP-T-C-017 MLP-T-C-018 MLP-T-C-019
pos eme_pos trl_pos pd poser time alt alt_unc qos_not_met direction speed lev_conf geo_info coordinateReferenceSystem identifier code codeSpace edition service_coverage
5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3
M O O M M M O O O O O O O O O O O O O
B.1.21 Support for Result Elements

MLP-U-C-001 MLP-U-C-002
add_info result
5.2.2.4 5.2.2.4
O M
B.1.22 Support for Shape Elements

MLP-V-C-001
shape
5.2.2.5
MLP-V-C-002 OR MLP-V-C-003 OR MLP-V-C-004 OR MLP-V-C005 OR MLP-V-C-006 OR MLP-VC-007 OR MLP-V-C-008 OR MLPV-C-009 OR MLP-V-C-010 OR MLP-V-C-011
OMA-TS-MLP-V3_2-20051124-C
Page 119 (128)
Item
Function
Reference
Status
Requirement
MLP-V-C-002 MLP-V-C-003 MLP-V-C-004 MLP-V-C-005 MLP-V-C-006 MLP-V-C-007 MLP-V-C-008 MLP-V-C-009 MLP-V-C-010 MLP-V-C-011
Point LineString Box LinearRing Polygon CircularArcArea EllipticalArea MultiLineString MultiPoint MultiPolygon
5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5
O O O O O O O O O O
B.1.23 Support for Quality of Position Elements

MLP-W-C-001 MLP-W-C-002 MLP-W-C-003 MLP-W-C-004 MLP-W-C-005 MLP-W-C-006 MLP-W-C-007 MLP-W-C-008
eqop qop ll_acc hor_acc max_loc_age resp_req resp_timer alt_acc
5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6
O O O O O O O O
B.1.24 Support for Network Parameters Elements

MLP-X-C-001 MLP-X-C-002 MLP-X-C-003 MLP-X-C-004 MLP-X-S-005 MLP-X-C-006 MLP-X-C-007 MLP-X-C-008 MLP-X-C-009 MLP-X-C-010 MLP-X-C-011 MLP-X-C-012 MLP-X-C-013 MLP-X-C-014 MLP-X-C-015 MLP-X-C-016 MLP-X-C-017
gsm_net_param cgi neid vmscid vlrid nmr mcc mnc ndc cc vmscno vlrno lac cellid ta lmsi imsi
5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.27 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7
O O O O O O O O O O O O O O O O O
MLP-X-C-004 OR MLP-X-C-005
OMA-TS-MLP-V3_2-20051124-C
Page 120 (128)
B.1.25 Support for Context Elements

MLP-Y-C-001 MLP-Y-C-002 MLP-Y-C-003 MLP-Y-C-004 MLP-Y-C-005 MLP-Y-C-006 MLP-Y-C-007 MLP-Y-C-008
client sessionid id requestor pwd serviceid requestmode subclient
5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8
M O M O O O O O
B.1.26 Service attributes

MLP-Z-C-001 MLP-Z-C-002
res_type ver
5.3.86 5.3.86
O M
B.1.27 Transport mechanisms

MLP-AA-C-001 MLP-AA-C-002 MLP-AA-C-003 MLP-AA-C-004
Support of HTTP mapping Support of port 9210 Support of port 9211 Support of transfer over other port
5.2.1, 5.6 5.6 5.6 5.6
M O O O
B.1.28 Services
MLP-AB-C-001 MLP-AB-C-002 MLP-AB-C-003 MLP-AB-C-004 MLP-AB-C-005
Standard Location Immediate Service Emergency Location Immediate Service Standard Location Reporting Service Emergency Location Reporting Service Triggered Location Reporting Service
5.2.3.2 5.2.3.3 5.2.3.4 5.2.3.5 5.2.3.6
M O O O O
MLP-A-C-003 AND MLP-B-C-003 AND MLP-B-C-004 MLP-A-C-004 AND MLP-B-C-007 MLP-B-C-005 AND MLP-B-C-006 MLP-B-C-009 MLP-A-C-005 AND MLP-A-C-006 AND MLP-B-C-010 AND MLP-BC-011 AND MLP-B-C-012
OMA-TS-MLP-V3_2-20051124-C
Page 121 (128)
B.2
SCR for Server

B.2.1 Service Initiation DTD

MLP-A-S-001 MLP-A-S-002 MLP-A-S-003 MLP-A-S-004 MLP-A-S-005 MLP-A-S-006 MLP-A-S-007 Service Initiation Header Standard Location Immediate Request Emergency Location Immediate Request Triggered Location Reporting Request Triggered Location Reporting Stop Request Extension Message 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 5.6.2.1 M M M O O O O MLP-A-S-002 AND MLP-A-S-003 MLP-B-S-003 AND MLP-B-S-004 MLP-B-S-007 MLP-B-S-010 AND MLP-B-S-011 AND MLP-B-S-012 MLP-B-S-012
B.2.2 Service Result DTD

MLP-B-S-001
Service Result
5.6.2.2
MLP-B-S-002 AND MLP-B-S-003 AND MLP-B-S-004 AND MLP-BS-005
MLP-B-S-002 MLP-B-S-003 MLP-B-S-004 MLP-B-S-005 MLP-B-S-006 MLP-B-S-007 MLP-B-S-008 MLP-B-S-009 MLP-B-S-010 MLP-B-S-011 MLP-B-S-012 MLP-B-S-013
Header Standard Location Immediate Answer Standard Location Immediate Report Standard Location Report Standard Location Report Answer Emergency Location Immediate Answer Emergency Location Immediate Report Emergency Location Report Triggered Location Reporting Answer Triggered Location Report Triggered Location Reporting Stop Answer Extension Message
5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2 5.6.2.2
O M O O O O O O O O O O MLP-B-S-011 MLP-B-S-010 MLP-B-S-007
B.2.3 Header
Item Function Reference Status Requirement 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
OMA-TS-MLP-V3_2-20051124-C
Page 122 (128)
Item
Function
Reference
Status
Requirement
MLP-C-S-001 MLP-C-S-002 MLP-C-S-003 MLP-C-S-004
client sessionid subclient requestor
5.2.3.1 5.2.3.1 5.2.3.1 5.2.3.1
M O O O
B.2.4 Standard Location Immediate Request

MLP-D-S-001 MLP-D-S-002 MLP-D-S-003 MLP-D-S-004 MLP-D-S-005 MLP-D-S-006 MLP-D-S-007 MLP-D-S-008 MLP-D-S-009 MLP-D-S-010 MLP-D-S-011 MLP-D-S-012
msids msid codeword gsm_net_param trans_id eqop geo_info loc_type prio pushaddr service_coverage extension parameter
5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1 5.2.3.2.1
O M O O O O O O O O O O
B.2.5 Standard Location Immediate Answer

MLP-E-S-001 MLP-E-S-002 MLP-E-S-003 MLP-E-S-004 MLP-E-S-005
pos req_id result add_info extension parameter
5.2.3.2.2 5.2.3.2.2 5.2.3.2.2 5.2.3.2.2 5.2.3.2.2
M O M O O
B.2.6 Standard Location Immediate Report

MLP-F-S-001 MLP-F-S-002 MLP-F-S-003
req_id pos extension parameter
5.2.3.2.3 5.2.3.2.3 5.2.3.2.3
M M O
MLP-E-S-002
B.2.7 Emergency Location Immediate Request

MLP-G-S-001 MLP-G-S-002 MLP-G-S-003 MLP-G-S-004
msids msid gsm_net_param trans_id
5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1
O M O O
OMA-TS-MLP-V3_2-20051124-C
Page 123 (128)
Item
Function
Reference
Status
Requirement
MLP-G-S-005 MLP-G-S-006 MLP-G-S-007 MLP-G-S-008 MLP-G-S-009 MLP-G-S-010 MLP-G-S-011
esrd esrk eqop geo_info loc_type pushaddr extension parameter
5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1 5.2.3.3.1
O O O O O O O
B.2.8 Emergency Location Immediate Answer

MLP-H-S-001 MLP-H-S-002 MLP-H-S-003 MLP-H-S-004 MLP-H-S-005
eme_pos req_id result add_info extension parameter
5.2.3.3.2 5.2.3.3.2 5.2.3.3.2 5.2.3.3.2 5.2.3.3.2
M O M O O
B.2.9 Emergency Location Immediate Report

MLP-I-S-001 MLP-I-S-002 MLP-I-S-003 MLP-I-S-004 MLP-I-S-005
req_id eme_pos result add_info extension parameter
5.2.3.3.3 5.2.3.3.3 5.2.3.3.3 5.2.3.3.3 5.2.3.3.3
M M M O O
MLP-H-S-002
B.2.10 Standard Location Report

MLP-J-S-001 MLP-J-S-002
pos extension parameter
5.2.3.4.1 5.2.3.4.1
M O
B.2.11 Standard Location Report Answer

MLP-K-S-001 MLP-K-S-002 MLP-K-S-003
result add_info extension parameter
5.2.3.4.2 5.2.3.4.2 5.2.3.4.2
M O O
B.2.12 Emergency Location Report

MLP-L-S-001
eme_event
5.2.3.5.1
OMA-TS-MLP-V3_2-20051124-C
Page 124 (128)
Item
Function
Reference
Status
Requirement
MLP-L-S-002
extension parameter
5.2.3.5.1
B.2.13 Triggered Location Reporting Request

MLP-M-S-001 MLP-M-S-002 MLP-M-S-003 MLP-M-S-004 MLP-M-S-005 MLP-M-S-006 MLP-M-S-007 MLP-M-S-008 MLP-M-S-009 MLP-M-S-010 MLP-M-S-011 MLP-M-S-012 MLP-M-S-013
msids interval start_time stop_time duration tlrr_event qop geo_info pushaddr loc_type prio service_coverage extension parameter
5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1 5.2.3.6.1
B.2.14 Triggered Location Reporting Answer

MLP-N-S-001 MLP-N-S-002 MLP-N-S-003 MLP-N-S-004 MLP-N-S-005
req_id result add_info extension parameter lcs_ref
5.2.3.6.2 5.2.3.6.2 5.2.3.6.2 5.2.3.6.2 5.2.3.6.2
M M O O O
B.2.15 Triggered Location Report

MLP-O-S-001 MLP-O-S-002 MLP-O-S-003 MLP-O-S-004 MLP-O-S-005
req_id trl_pos time_remaining extension parameter lcs_ref
5.2.3.6.3 5.2.3.6.3 5.2.3.6.3 5.2.3.6.3 5.2.3.6.3
M M O O O
B.2.16 Triggered Location Reporting Stop Request

MLP-P-S-001 MLP-P-S-002 MLP-P-S-003
req_id extension parameter lcs_ref
5.2.3.6.4 5.2.3.6.4 5.2.3.6.4
M O O
OMA-TS-MLP-V3_2-20051124-C
Page 125 (128)
B.2.17 Triggered Location Reporting Stop Answer

MLP-Q-S-001 MLP-Q-S-002 MLP-Q-S-003 MLP-Q-S-004
req_id result add_info extension parameter
5.2.3.6.5 5.2.3.6.5 5.2.3.6.5 5.2.3.6.5
M M O O
B.2.18 Support for Identity Elements

MLP-R-S-001 MLP-R-S-002 MLP-R-S-003 MLP-R-S-004 MLP-R-S-005 MLP-R-S-006 MLP-R-S-007 MLP-R-S-008 MLP-R-S-009 MLP-R-S-010
msid msid_range msids codeword esrd esrk session start_msid stop_msid trans_id
5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1 5.2.2.1
M O O O O O O O O O
B.2.19 Support for Function Elements

MLP-S-S-001 MLP-S-S-002 MLP-S-S-003 MLP-S-S-004 MLP-S-S-005 MLP-S-S-006 MLP-S-S-007 MLP-S-S-008 MLP-S-S-009 MLP-S-S-010 MLP-S-S-011 MLP-S-S-012 MLP-S-S-013 MLP-S-S-014 MLP-S-S-015 MLP-S-S-016 MLP-S-S-017 MLP-S-S-018 MLP-S-S-019
eme_event tlrr_event ms_action change_area target_area no_of_reports name_area plmn interval loc_type prio pushaddr req_id start_time stop_time duration url time_remaining lcs_ref
5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2 5.2.2.2
O O O O O O O O O O O O O O O O O O O
OMA-TS-MLP-V3_2-20051124-C
Page 126 (128)
B.2.20 Support for Location Elements

MLP-T-S-001 MLP-T-S-002 MLP-T-S-003 MLP-T-S-004 MLP-T-S-005 MLP-T-S-006 MLP-T-S-007 MLP-T-S-008 MLP-T-S-009 MLP-T-S-010 MLP-T-S-011 MLP-T-S-012 MLP-T-S-013 MLP-T-S-014 MLP-T-S-015 MLP-T-S-016 MLP-T-S-017 MLP-T-S-018 MLP-T-S-019
pos eme_pos trl_pos pd poser time alt alt_unc qos_not_met direction speed lev_conf geo_info coordinateReferenceSystem identifier code codeSpace edition service_coverage
5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3 5.2.2.3
M O O M M M O O O O O O O O O O O O O
B.2.21 Support for Result Elements

MLP-U-S-001 MLP-U-S-002
add_info result
5.2.2.4 5.2.2.4
O M
B.2.22 Support for Shape Elements

MLP-V-S-001
shape
5.2.2.5
MLP-V-S-002 OR MLP-V-S-003 OR MLP-V-S-004 OR MLP-V-S005 OR MLP-V-S-006 OR MLP-VS-007 OR MLP-V-S-008 OR MLPV-S-009 OR MLP-V-S-010 OR MLP-V-S-011
MLP-V-S-002 MLP-V-S-003 MLP-V-S-004 MLP-V-S-005 MLP-V-S-006 MLP-V-S-007 MLP-V-S-008
Point LineString Box LinearRing Polygon CircularArcArea EllipticalArea
5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5 5.2.2.5
O O O O O O O
OMA-TS-MLP-V3_2-20051124-C
Page 127 (128)
Item
Function
Reference
Status
Requirement
MLP-V-S-009 MLP-V-S-010 MLP-V-S-011
MultiLineString MultiPoint MultiPolygon
5.2.2.5 5.2.2.5 5.2.2.5
O O O
B.2.23 Support for Quality of Position Elements

MLP-W-S-001 MLP-W-S-002 MLP-W-S-003 MLP-W-S-004 MLP-W-S-005 MLP-W-S-006 MLP-W-S-007 MLP-W-S-008
eqop qop ll_acc hor_acc max_loc_age resp_req resp_timer alt_acc
5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6 5.2.2.6
O O O O O O O O
B.2.24 Support for Network Parameters Elements

MLP-X-S-001 MLP-X-S-002 MLP-X-S-003 MLP-X-S-004 MLP-X-S-005 MLP-X-S-006 MLP-X-S-007 MLP-X-S-008 MLP-X-S-009 MLP-X-S-010 MLP-X-S-011 MLP-X-S-012 MLP-X-S-013 MLP-X-S-014 MLP-X-S-015 MLP-X-S-016 MLP-X-S-017
gsm_net_param cgi neid vmscid vlrid nmr mcc mnc ndc cc vmscno vlrno lac cellid ta lmsi imsi
5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.27 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7 5.2.2.7
O O O O O O O O O O O O O O O O O
MLP-X-S-004 OR MLP-X-S-005
B.2.25 Support for Context Elements

MLP-Y-S-001 MLP-Y-S-002 MLP-Y-S-003 MLP-Y-S-004
client sessionid id requestor
5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8
M O O O
OMA-TS-MLP-V3_2-20051124-C
Page 128 (128)
Item
Function
Reference
Status
Requirement
MLP-Y-S-005 MLP-Y-S-006 MLP-Y-S-007 MLP-Y-S-008
pwd serviceid requestmode subclient
5.2.2.8 5.2.2.8 5.2.2.8 5.2.2.8
O O O O
B.2.26 Service attributes

MLP-Z-S-001 MLP-Z-S-002
res_type ver
5.3.86 5.3.86
M M
B.2.27 Transport mechanisms

MLP-AA-S-001 MLP-AA-S-002 MLP-AA-S-003 MLP-AA-S-004
Support of HTTP mapping Support of port 9210 Support of port 9211 Support of transfer over other port
5.2.1, 5.6 5.6 5.6 5.6
M O O O
B.2.28 Services
MLP-AB-S-001 MLP-AB-S-002 MLP-AB-S-003 MLP-AB-S-004 MLP-AB-S-005
Standard Location Immediate Service Emergency Location Immediate Service Standard Location Reporting Service Emergency Location Reporting Service Triggered Location Reporting Service
5.2.3.2 5.2.3.3 5.2.3.4 5.2.3.5 5.2.3.6
M O O O O
MLP-A-S-003 AND MLP-B-S-003 MLP-A-S-004 AND MLP-B-S-004 MLP-B-S-005 AND MLP-B-S-006 MLP-B-S-009 MLP-A-S-005 AND MLP-A-S-006 AND MLP-B-S-010 AND MLP-BS-011 AND MLP-B-S-012

Oma TS MLP V3 - 2 20110719 A

Uploaded by

Copyright:

Available Formats

Oma TS MLP V3 - 2 20110719 A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oma TS MLP V3 - 2 20110719 A

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What services does this document specify?

What services does this document specify?

Mobile Location Protocol 3.

Open Mobile Alliance OMA-TS-MLP-V3_2-20110719-A

[23.003] [E164] [J-STD-036] [IS-41D] [AST] [CRS]

[GEO] [RFC796] [RFC3513] [05.10] [UTC]

3. Terminology and Conventions

DTD Syntax Notation

Location Server Target Timing Advance

5. Mobile Location Protocol

Basic MLP Services

Advanced MLP Services Svc1 Svc2 Svcn

Other MLP Services

Basic Basic Common Elements Element Common s

Core Location Elements

Transport Layer Mapping (HTTP, WSP, SOAP, )

Service Standard Location Immediate Service

Emergency Location Immediate Service

Standard Location Reporting Service

Emergency Location Reporting Service

Triggered Location Reporting Service

MLP extension mechanism

Mobile Location Service Definitions

Section 5.6 HTTP Mapping

Element Layer Definitions

Function Element Definitions

<!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST

<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST

Location Element Definitions

A-GPS | E-OTD | OTHER)

<!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ELEMENT

poserr time time utc_off CDATA alt alt_unc

<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT

qos_not_met direction speed lev_conf geo_info CoordinateReferenceSystem Identifier code codeSpace

(#PCDATA)> ((cc, ndc*)+)> SYSTEM "MLP_RES_300.DTD">

<!ENTITY % mlp_res.dtd %mlp_res.dtd;

Examples of geo_info encoding. The encoding for WGS84 is:

Result Element Definitions

Shape Element Definitions

<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST

<!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST

MultiPolygon gid ID srsName CDATA

Note also that GML uses crsName instead of srsName.

Quality of Position Element Definitions

Network Parameters Element Definitions

Context Element Definitions

<!ELEMENT <!ELEMENT <!ELEMENT <!ATTLIST <!ELEMENT <!ATTLIST

Service Layer Definitions

Example 1: ASP as Initiator

<id>thelastasp</id> <serviceid>0005</serviceid> </subclient> <requestor> <id>theoriginalasp</id> <serviceid>0005</serviceid> </requestor> </hdr>

Standard Location Immediate Service

standard location immediate answer

standard location immediate report

Standard Location Immediate Request DTD

slir ver CDATA res_type (SYNC | ASYNC)

Standard Location Immediate Answer DTD

Example 1: Successful positioning of multiple subscribers