LIF TS 101 v3.0.0

Location Inter-operability Forum (LIF) Mobile Location Protocol LIF TS 101 Specification Version 3.0.0

Page 1 (92) 6 June 2002

LIF DELIVERABLE COPYRIGHT NOTICE AND DISCLAIMER COPYRIGHT LOCATION INTEROPERABILITY FORUM LTD. 2001,2002 Implementation of all or part of this LIF Deliverable may require licenses under or in respect of intellectual property rights including, without limitation, patent rights of a third party (who may or may not be a LIF Member). Neither Location Interoperability Forum Ltd. nor Location Interoperability Forum nor any of its members is responsible, and shall not be held responsible, in any manner for identifying or failing to identify any or all such third party intellectual property rights.

Mobile Location Protocol Specification

Abstract The purpose of this specification is to define a simple and secure access method that allows Internet applications to query location information from a wireless network, irrespective of its underlying air interface technologies and positioning methods. This specification covers the core of a Mobile Location Protocol that can be used by a location-based application to request MS location information from a location server (GMLC/MPC or other entity in the wireless network). This specification has been prepared by LIF to provide a simple and secure API (Application Programmers Interface) to the location server, but that also could be used for other kinds of location servers and entities in the wireless network. The API is based on existing and well-known Internet technologies as HTTP, SSL/TLS and XML, in order to facilitate the development of location-based applications.


Page 2 (92) 6 June 2002

Contents 1 2 2.1 2.2 3 3.1 3.2 3.3 4 4.1 4.2 4.3 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20 5.21 5.22 5.23 5.24 5.25 5.26 5.27 5.28 5.29 5.30 5.31 5.32 5.33 5.34 Revision History ............................................................................. 5 Introduction..................................................................................... 6 Abbreviations.................................................................................. 6 Notational Conventions and Generic Grammar ............................. 6 General........................................................................................... 8 Overview ........................................................................................ 8 MLP structure ................................................................................. 8 MLP extension mechanism .......................................................... 12 Mobile Location Service Definitions ............................................. 14 Transport Protocol Layer Definitions ............................................ 14 Element Layer Definitions ............................................................ 14 Service Layer Definitions.............................................................. 18 Elements and attributes in DTD ................................................... 35 add_info........................................................................................ 35 alt.................................................................................................. 35 alt_acc .......................................................................................... 35 angle............................................................................................. 36 angularUnit ................................................................................... 36 Box ............................................................................................... 37 cc.................................................................................................. 38 cellid ............................................................................................. 38 CircularArcArea ............................................................................ 39 CircularArea ................................................................................. 40 code.............................................................................................. 40 codeSpace ................................................................................... 41 codeword...................................................................................... 41 distanceUnit.................................................................................. 41 direction........................................................................................ 42 edition........................................................................................... 42 EllipticalArea................................................................................. 43 eme_event.................................................................................... 43 esrd .............................................................................................. 44 esrk............................................................................................... 45 GeometryCollection...................................................................... 46 hor_acc......................................................................................... 46 id................................................................................................... 47 inRadius ....................................................................................... 47 interval.......................................................................................... 47 lac................................................................................................. 48 lev_conf ........................................................................................ 48 LinearRing .................................................................................... 49 LineString ..................................................................................... 50 ll_acc ............................................................................................ 51 lmsi ............................................................................................... 51 loc_type ........................................................................................ 51 max_loc_age ................................................................................ 52 mcc............................................................................................... 52


Page 3 (92) 6 June 2002

5.35 5.36 5.37 5.38 5.39 5.40 5.41 5.42 5.43 5.44 5.45 5.46 5.47 5.48 5.49 5.50 5.51 5.52 5.53 5.54 5.55 5.56 5.57 5.58 5.59 5.60 5.61 5.62 5.63 5.64 5.65 5.66 5.67 5.68 5.69 5.70 5.71 5.72 5.73 5.74 5.75 6 6.1 7 7.1 7.2 8 8.1 8.2 8.3

mnc............................................................................................... 53 ms_action ..................................................................................... 53 msid.............................................................................................. 54 MultiLineString.............................................................................. 55 MultiPoint...................................................................................... 56 MultiPolygons ............................................................................... 56 ndc................................................................................................ 57 nmr ............................................................................................... 57 radius............................................................................................ 57 startAngle ..................................................................................... 58 stopAngle ..................................................................................... 58 Point ............................................................................................. 58 Polygon ........................................................................................ 59 prio ............................................................................................... 60 pwd............................................................................................... 60 outRadius ..................................................................................... 61 req_id ........................................................................................... 61 resp_req ....................................................................................... 61 resp_timer .................................................................................... 62 result............................................................................................. 62 semiMajor..................................................................................... 63 semiMinor..................................................................................... 63 serviceid ....................................................................................... 64 requestmode ................................................................................ 64 session ......................................................................................... 65 sessionid ...................................................................................... 65 speed............................................................................................ 66 start_time...................................................................................... 66 stop_time...................................................................................... 67 subclient ....................................................................................... 68 ta .................................................................................................. 68 time............................................................................................... 69 time_remaining............................................................................. 69 trl_pos........................................................................................... 70 url ................................................................................................. 70 vlrno.............................................................................................. 71 vmscno ......................................................................................... 71 X ................................................................................................... 71 Y ................................................................................................... 72 Z ................................................................................................... 72 Service attributes.......................................................................... 73 Result codes................................................................................. 74 Result codes................................................................................. 74 References ................................................................................... 76 References (Normative) ............................................................... 76 References (Informative) .............................................................. 76 Appendix A (informative): Adaptation to 3GPP LCS .................... 78 Version mapping between 3GPP TS23.271 and this specification78 The terminology mapping table with 3GPP LCS Specifications ... 78 The corresponding terms used for the location procedures in 3GPP LCS Definition .............................................................................. 79


Page 4 (92) 6 June 2002

8.4 9 9.1 9.2 10 10.1 10.2 10.3 10.4 10.5

Error Mapping (informative).......................................................... 80 Appendix B - HTTP Mapping........................................................ 81 Location Services using HTTP ..................................................... 81 Request and Response Encapsulation ........................................ 82 Appendix C: Geographic Information ........................................... 86 Coordinate Reference systems (Informative) ............................... 86 Coordinate Reference System Transformations (Informative) ..... 88 Methodology for defining CRSs and transformations in this protocol (Normative)................................................................................... 88 Supported coordinate systems and datum ................................... 88 Shapes representing a geographical position .............................. 89


Page 5 (92) 6 June 2002

1

Revision History1.0 1.1 1.1.1 1.1.2 2.0.0 2.1.0 2.2.0 2.2.1 2.3.0 3.0.0 23-Jan-2001 26-Jan-2001 5-Nov-2001 17-Nov-2001 20-Nov-2001 10-Mar-2002 02-Apr-2002 16-Apr-2002 15-May-2002 06-Jun-2002 Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Sanjiv Bhatt, Motorola Motorola, Nokia, Ericsson contribution to LIF Updated after review in MLP adhoc committee in LIF #2 meeting Updated after SIG#6 meeting Updated after SIG#7 meeting Final version (public release) Updated after SIG#8 meeting Updated after SIG#9 meeting Updated before public review Updated after SIG#10 meeting Final changes


Page 6 (92) 6 June 2002

2

IntroductionThe 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. The MLP serves as the interface between a Location Server and a Location Services (LCS) Client. This specification defines the core set of operations that a Location Server should be able to perform.

2.1

AbbreviationsANSI DTD GMLC GMT HTTP HTTPS LCS MLC MLP MPC MS MSID SSL TLS URI URL UTM WGS XML American National Standards Institute Document Type Definition Gateway Mobile Location Center Greenwich Mean Time Hypertext Transfer Protocol HTTP Secure Location Services Mobile Location Center Mobile Location Protocol Mobile Positioning Center Mobile Station Mobile Station Identifier Secure Socket Layer Transport Layer Security Uniform Resource Identifier Uniform Resource Locator Universal Transverse Mercator World Geodetic System Extensible Markup Language

2.2

Notational Conventions and Generic GrammarThe following rules are used throughout this specification to describe basic parsing constructs. ANSI X3.4-1986 defines the US-ASCII coded character set, see ref. [5]CR LF SP = = =

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.


Page 7 (92) 6 June 2002

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


Page 8 (92) 6 June 2002

33.1

GeneralOverviewThe 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 location-based application.

Wireless Network

request (MLP)

Locationbased application

Location Server

response (MLP)

Possible realizations 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 most 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.

3.2

MLP structureIn our heterogeneous world, different devices may support different means of communication. A ubiquitous protocol for location services should support different transport mechanisms. In MLP, the transport protocol is separated from the XML content. The following diagram shows a layered view of MLP.


Page 9 (92) 6 June 2002

Basic MLP ServicesSLIS ELI SLRS ELRS TLRS SLI ELIS Basic Basic Common Elements Element

Advanced MLP Services Svc1 Svc2 SvcnAdvanced Common Elements Advanced Common Elements

Other MLP Services

Service Layer

Element Layer

Core Location Elements

Transport Layer

Transport Layer Mapping (HTTP, WSP, SOAP, )

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_SHAPE.DTD MLP_QOP.DTD MLP_GSM_NET.DTD MLP_CTXT Identify Element Definitions Function Element Definitions Location 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.


Page 10 (92) 6 June 2002

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 sub-layer. 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.


Page 11 (92) 6 June 2002

ServiceStandard Location Immediate Service

DescriptionThis 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

Emergency Location Immediate Service

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). This service consists of the following messages: Emergency Location Immediate Request Emergency Location Immediate Answer

Standard 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 application and its address are specified by MS or defined in the location server. This service consists of the following message: Standard Location Report

Emergency Location Reporting Service

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 application and its address are defined in the location server. This service consists of the following message: Emergency Location Report

Triggered Location Reporting Service

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


Page 12 (92) 6 June 2002

3.3

MLP extension mechanismThe 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. 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 Parameter extension mechanism allows 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. In order to use the extension, the extension DTD has to be explicitly referenced in the XML document. The Location Server may ignore any extension that is not recognized and process the message as if the extension is not available. Example 1: Message extension (truckco_data)> #FIXED "x.y.z">

... ...


Page 13 (92) 6 June 2002

Example 2: Parameter extension (#PCDATA)>

... ... ...


Page 14 (92) 6 June 2002

44.1

Mobile Location Service DefinitionsTransport Protocol Layer DefinitionsMLP can be implemented using various transport mechanism as stated in section 3.2. The following mappings are specified for MLP: Mapping HTTP Section Appendix B - HTTP Mapping

4.24.2.1

Element Layer DefinitionsIdentity Element Definitions "MSISDN" "ASC"> (start_msid, stop_msid)> (((msid, codeword?, session?) | (msid_range, codeword*))+)> (#PCDATA)> (#PCDATA)> "NA"> (#PCDATA)> "NA"> (#PCDATA)> #REQUIRED> (msid)> (msid)>

#REQUIRED> ( ms_action)> EMPTY> #REQUIRED> (#PCDATA)> EMPTY> "CURRENT"> EMPTY> "NORMAL"> (url, id?, pwd?)> (#PCDATA)>


Page 15 (92) 6 June 2002

"0000"> (#PCDATA)> "0000"> (#PCDATA)> (#PCDATA)>

4.2.3

Location Element Definitions (msid, (pd | poserr), esrd?, esrk?)> (msid, (pd | poserr))> #REQUIRED> (time, shape, (alt, alt_acc?)?, speed?, direction?, lev_conf?)> (result, add_info?, time)> (#PCDATA)> (#PCDATA)> #REQUIRED> (#PCDATA)> "0000"> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (#PCDATA)> (CoordinateReferenceSystem)> (Identifier)> (code, codeSpace, edition)> (#PCDATA)> (#PCDATA)> (#PCDATA)>

Examples of geo_info encoding. The encoding for WGS84 is: 4326 EPSG 6.1

The encoding for the Transverse Mercator coordinate system based on the OSGB1936 is: 27700 EPSG 6.1

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"


Page 16 (92) 6 June 2002

4.2.4

Shape Element Definitions (#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)> (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)> (shape+)> #IMPLIED #IMPLIED> (LineString+)> #IMPLIED #IMPLIED> (Point+)> #IMPLIED #IMPLIED> ((Polygon| Box | CircularArea | CircularArcArea | EllipticalArea)+)> #IMPLIED #IMPLIED>


Page 17 (92) 6 June 2002

4.2.5

Quality of Position Element Definitions ((ll_acc | hor_acc)?, alt_acc?)> (#PCDATA)> (#PCDATA)> (#PCDATA)> EMPTY> "DELAY_TOL"> (#PCDATA)>

4.2.6

Network Parameters Element Definitions (mcc, mnc, lac, cellid)> (vmscid | vlrid | (vmscid, vlrid))> (cc?, ndc?, vmscno)> (cc?, ndc?, vlrno)> (#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

4.2.7

Context Element Definitions (#PCDATA)> (#PCDATA)> (id, serviceid?)> (#PCDATA)> (#PCDATA)> EMPTY> "PASSIVE"> (id, pwd?, serviceid?)> "NO">


Page 18 (92) 6 June 2002

4.3

Service Layer DefinitionsEach message may have two main parts, namely a context or header part and a body part. The body part consists of the request/answer and is described in sections 4.3.2 - 4.3.7. The context or header part consists of the information that identifies the client as defined in section 4.3.1.

4.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 initial 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"). On the other hand requestor is indicating 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. 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 will need to "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 will need to continue to "login" for subsequent transactions. The LCS Client can opt to 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 one and the use of a sessionid, here would allow the security of the LCS Client to be breached.


Page 19 (92) 6 June 2002

4.3.1.1

Context DTD #FIXED "3.0.0">

Example 1: ASP as Initiator theasp thepwd 0005 thelastasp 0007 theoriginalasp 0003

Example 2: MS as Initiator theasp thepwd 0005 461018765710


Page 20 (92) 6 June 2002

4.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 the all responses from the network. If the Location Server supports it the LCS Client can define how to receive the location responses, either at a time with the response of 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 following message flow encapsulates this service:LCS Client Location Server

standard location immediate request

standard location immediate answer

standard location immediate report

If (needed)

4.3.2.1

Standard Location Immediate Request DTD ((msids | (msid, codeword?, gsm_net_param)+), eqop?, geo_info?, loc_type?, prio?, pushaddr? %extension.param;)> #FIXED "3.0.0" "SYNC">


Page 21 (92) 6 June 2002

Example 93.10.0.250 461018765710 461018765712 441728922342 461018765720 461018765728 1000 4004 EPSG 6.1

4.3.2.2

Standard Location Immediate Answer DTD ((pos+ | req_id | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">

Example 1: Successful positioning of multiple subscribers 461011334411 20020623134453 301628.312


Page 22 (92) 6 June 2002

451533.431 240 461018765710 20020623134454 301228.302 865633.863 570 461018765711 20020623110205 781234.322 762162.823 15 461018765712 QOP NOT ATTAINABLE 20020623134454

Example 2: Service not supported SERVICE NOT SUPPORTED 'slir' is not supported by the location server

4.3.2.3

Standard Location Immediate Report DTD (req_id, pos+ %extension.param;)> #FIXED "3.0.0">


Page 23 (92) 6 June 2002

Example 25267 10:A1:45::23:B7:89 20020813010423 35 03 28.244N 135 47 08.711E 15


Page 24 (92) 6 June 2002

4.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. The service consists of the following messages: Emergency Location Immediate Request Emergency Location Immediate Answer

The following message flow encapsulates this service:LCS Client Location Server

emergency location immediate request

emergency location immediate answer

4.3.3.1

Emergency Location Immediate Request DTD ((msids | (msid, gsm_net_param)+), qop?, geo_info?, loc_type? %extension.param;)> #FIXED "3.0.0">

Example 520002-51-431172-6-06 4004 EPSG 6.1


Page 25 (92) 6 June 2002

4.3.3.2

Emergency Location Immediate Answer DTD ((eme_pos+ | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">

Example 520002-51-431172-6-06 20020623134453 N301628.312 -451533.431 15 7839298236


Page 26 (92) 6 June 2002

4.3.4

Standard Location Reporting Service When a mobile subscriber wants an LCS client to receive the MS location a standard location report is generated. The LCS Client that the location report should be sent to is specified by MS or defined within the Location Server. The service consists of the following message: Standard Location Report The following message flow encapsulates this service:LCS Client standard location report Location Server

4.3.4.1

Standard Location Report DTD (pos+ %extension.param;)> #FIXED "3.0.0">

Example 461011678298 20020813010423 301628.312 451533.431 15


Page 27 (92) 6 June 2002

4.3.5

Emergency Location Reporting Service If the wireless network spontaneously initiates a positioning when 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 is defined within the location server. Data as required geographical format and address to application is also defined within the location server. The service consists of the following message: Emergency Location Report The following message flow encapsulates this service:LCS Client emergency location report Location Server

4.3.5.1

Emergency Location Report DTD (eme_event %extension.param;)> #FIXED "3.0.0">

Example 461011678298 20020623010003 301628.312 451533.431 15


Page 28 (92) 6 June 2002

4.3.6

Triggered Location Reporting Service The triggered location reporting service is used when an application wants the position of the list of MS to be tracked. The triggers could be: The periodicity time defined by an interval An MS action, defined as the event "UE available" in 3GPP TS 23.271 rel. 4 [ref. 11].

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 following message flow 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


Page 29 (92) 6 June 2002

Note:

It is the intention that Triggered services will support entering or leaving an area in future releases. An area may be defined as a specified geographical area, a city or locale, a country or a network. Other triggers that may be supported are specific events not yet defined, such a subscriber being in proximity to a friend in a FriendFinder application. Other events are FFS within 3GPP and are targeted for rel. 6.

4.3.6.1

Triggered Location Reporting Request DTD (msids, interval?, start_time?, stop_time?, tlrr_event?, qop?, geo_info?, pushaddr?, loc_type?, prio? %extension.param;)> #FIXED "3.0.0">

The following rules apply to the use of start_time, stop_time, interval and tlrr_event: TLRR with interval is interpreted as a request for periodic location reports, and TLRR with tlrr_event is interpreted as a request for a location report on the occurrence of a specific event. interval and tlrr_event can be combined. When neither interval nor tlrr_event is specified in TLRR, Location Server MUST reject the request with an error indication 106 to the client. If no START_TIME is specified reporting starts immediately. If no STOP_TIME is specified the reporting will 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 START_TIME is older than current time the Location Server MUST reject the request with an error indication 110 to the client. If STOP_TIME is older than current time the Location Server MUST reject the request with an error indication 110 to the client. If STOP_TIME is earlier than START_TIME the implementation MUST reject the request with an error indication 110 to the client. If STOP_TIME is equal to START_TIME the Location Server MUST return a single location report to the client at the specified time. Any interval specified MUST be ignored.


Page 30 (92) 6 June 2002

Example 1: TLRR for periodic location reports during a specified period 461011678298 00003000 20021003112700 20021003152700 100 4326 EPSG 6.1 http://location.application.com

Example 2: TLRR for single location report at a specified time. stop_time is specified equal to start_time. 461011678298 00003000 20021003112700 20021003112700 100 4004 EPSG 6.1 http://location.application.com


Page 31 (92) 6 June 2002

Example 3: TLRR for a location report on the occurrence of a MS_AVAIL event after a specified time. 461011678298 20021003112700 100 4326 EPSG 6.1 http://location.application.com

4.3.6.2

Triggered Location Reporting Answer DTD ((req_id | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">

Example 1: TLRA if corresponding TLRR was successful 25293

Example 2: TLRA if corresponding TLRR was in error UNKNOWN SUBSCRIBER


Page 32 (92) 6 June 2002

4.3.6.3

Triggered Location Report DTD (req_id, trl_pos+, time_remaining? %extension.param;)> #FIXED "3.0.0">

Example 25267 461011678298 20020813010423 35 35 24.139N 139 35 24.754E 15 00010000

4.3.6.4

Triggered Location Reporting Stop Request DTD (req_id %extension.param;)> #FIXED "3.0.0">

Example 25293


Page 33 (92) 6 June 2002

4.3.6.5

Triggered Location Reporting Stop Answer DTD ((req_id | (result, add_info?)) %extension.param;)> #FIXED "3.0.0">

Example 25293


Page 34 (92) 6 June 2002

4.3.7

General Error Message Definition When an LCS client attempts to invoke a service not defined in this specification, the location server will 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 showed that it may not be familiar with the proper set of MLP services. So additional error indications may be described in the different transport layer mappings. #FIXED "3.0.0"> SYSTEM "MLP_LOC_300.DTD">

SERVICE NOT SUPPORTED The server does not support a service named 'skir'


Page 35 (92) 6 June 2002

5

Elements and attributes in DTD

5.1Description:

add_info

A text string containing additional information about a certain result. Type: Format: Defined values: Default value: Example: Note: Element Char string EVENT

5.2Description:

alt

The altitude of the MS in meters in respect of the ellipsoid which is used to be define the coordinates Type: Format: Defined values: Default value: Example: Element Char String [+|-] [0-9]+ 1200

Note: This element is present if altitude is possible to attain by the used positioning method.

5.3Description:

alt_acc

Accuracy of altitude in meters Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 200


Page 36 (92) 6 June 2002

5.4Description:

angle

Specifies the angle (in angularUnit) of rotation of an ellipse measured clockwise from north Type: Format: Defined values: Default value: Example: Note: Element Char String 24.30

5.5Description:

angularUnit

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 will be used. Type: Format: Defined values: Default value: Example: Note:. Element Char String Degrees Radians Degrees Degrees


Page 37 (92) 6 June 2002

5.6Description:

Box

The Box element is used to encode extents Type: Format: Defined values: Default value: Example: 301628.312 451533.431 311628.312 461533.431 Note: Element

5.6.1Description:

gid

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.. Type: Format: Defined values: Default value: Example: Note:.This attribute is optional and is on all shape elements attribute Char String


Page 38 (92) 6 June 2002

5.6.2Description:

srsName

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 the same as in the CoordinateReferenceSystem.. Type: Format: Defined values: Default value: Example: www.epsg.org/#4326 attribute Char String

Note:.This attribute is optional and is on all shape elements. If the srsName is not included the WGS84 CRS is assumed.

5.7Description:

cc

Specifies the country code. Type: Format: Defined values: Default value: Example: Note: Element Char String 1-3 digits e.g. 355 for Albania 355

5.8Description:

cellid

Identifies the Cell Identity Type: Format: Defined values: Default value: Example: Note: Element Char String 0-65535 546


Page 39 (92) 6 June 2002

5.9Description:

CircularArcArea

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. Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 280 360 5 240 Note:

5.9.1

gid See section 0.

5.9.2

srsName see section 0.


Page 40 (92) 6 June 2002

5.10Description:

CircularArea

The set of points on the ellipsoid, which are at a distance from the point of origin less than or equal to r. Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 240 Note:

5.10.1

gid See section 0.

5.10.2

srsName See section 0.

5.11Description:

code

This is the unique identifier for the Coordinate ReferenceSystem as used by the authority cited in codeSpace Type: Format: Defined values: Default value: Example: Note: . 4326 Element Char String


Page 41 (92) 6 June 2002

5.12Description:

codeSpace

The codeSpace is the authority which is responsible for the definition of the coordinate reference systems. Type: Format: Defined values: Default value: Example: Note:. www.epsg.org/... www.epsg.org Element Char String

5.13Description:

codeword

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. Type: Format: Defined values: Default value: Example: Element Char String 0918a7cb

Note: An error shall be returned if the number of codewords is not equal to the number of msid in an msid_range.

5.14Description:

distanceUnit

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 will be used. Type: Format: Defined values: Default value: Example: meter surveyfoot Element Char String

Note:.- values are defined by the CRS authority


Page 42 (92) 6 June 2002

5.15Description:

direction

Specifies the direction, in degrees, that a positioned MS is moving in. Type: Format: Defined values: Default value: Example: Element Char String

0-360120

Note: This element is present if direction is possible to attain by the used positioning method.

5.16Description:

edition

The edition defines which version of the CRS database defined by the codeSpace authority is used.. Type: Format: Defined values: Default value: Example: Note:. 6.0 Element Char String


Page 43 (92) 6 June 2002

5.17Description:

EllipticalArea

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. Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 240 150 275 degrees Note:

5.17.1

gid See section 0.

5.17.2


5.18Description:

eme_event

Specifies the events that initiated the positioning of the MS at an emergency call. Type: Format: Defined values: Default value: Example: Note: Element


Page 44 (92) 6 June 2002

5.18.1Description:

eme_trigger

Specifies the trigger that initiated the positioning of the MS at an emergency call. Type: Format: Defined values: Default value: Example: Note: Attribute Char string EME_ORG EME_REL An emergency service user originated an emergency call An emergency service user released an emergency call

5.19Description:

esrd

This element specifies Emergency Services Routing Digits (ESRD). Type: Format: Defined values: Default value: Example: Note: Element Char string 761287612582

5.19.1Description:

type

Defines the origin of the ESRD Type: Format: Defined values: Attribute Char string NA Indicates that the ERSD is defined as the North American ESRD (NA-ERSD). 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 Default value: Example: NA 12345678

Note: Currently only NA is specified. It is expected that other origins will be specified in the future


Page 45 (92) 6 June 2002

5.20Description:

esrk

This element specifies the Services Routing Key (ESRK). Type: Format: Defined values: Default value: Example: Note: Element Char string 928273633343

5.20.1Description:

type

Defines the origin of the ESRK Type: Format: Defined values: Attribute Char string NA Indicates that the ERSK is defined as the North American ESRK (NA-ERSK). 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 NAESRK 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. Default value: Example: NA 12345678

Note: Currently only NA is specified. It is expected that other origins will be specified in the future


Page 46 (92) 6 June 2002

5.21Description:

GeometryCollection

A collection of shapes. Type: Format: Defined values: Default value: Example: Element Char String ... Note:

5.21.1

gid See section 0.

5.21.2


5.22Description:

hor_acc

Requested horizontal accuracy in meters Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 200


Page 47 (92) 6 June 2002

5.23

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. Type: Element Format: Char string Defined values: Default value: TheTruckCompany Example: Note: - This element is implementation specific.

5.24Description:

inRadius

The inner radius is the geodesic distance (in distannceUnit) between center of the circle (that the arc is a part of) and arc closest to the center Type: Format: Defined values: Default value: Example: Element Char String [0-9]+ 100

Note: If the inner radius is 0 (zero) the area described represents a circle sector.

5.25Description:

interval

Specifies the interval between two responses in case of a TLRR that indicates timer controlled, periodic responses. Type: Format: Element Char string The interval is expressed as ddhhmmss where: String dd hh mm ss Defined values: Default value: Example: Note: 00010000 Description Number of days between responses Number of hours between responses Number of minutes between responses Number of seconds between responses


Page 48 (92) 6 June 2002

5.26Description:

lac

Identifies the Location Area Code Type: Format: Defined values: Default value: Example: Element Char String 1-65535 234

Note: - Location Area Code (LAC) which is a fixed length code (of 2 octets) identifying a location area within 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

5.27Description:

lev_conf

This parameter indicates the probability in percent that the MS is located in the position area that is returned. Type: Format: Defined values: Default value: Example: Note: Element Char String 0-100 80


Page 49 (92) 6 June 2002

5.28Description:

LinearRing

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. Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 401628.312 481533.431 332628.312 461533.431 301628.312 451533.431 Note:

5.28.1

gid See section 0.

5.28.2



Page 50 (92) 6 June 2002

5.29Description:

LineString

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. Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 401628.312 481533.431 332628.312 461533.431 Note:

5.29.1

gid See section 0.

5.29.2



Page 51 (92) 6 June 2002

5.30Description:

ll_acc

Longitude and latitude accuracy in seconds. Type: Format: Defined values: Default value: Example: Note: Element Char String 7.5

5.31Description:

lmsi

A local identity allocated by the VLR to a given subscriber for internal management of data in the VLR as defined in 29.002 Type: Format: Defined values: Default value: Example: Element Char String 2344512344565

Note: - The LMSI consists of 4 octets

5.32Description:

loc_type

Defines the type of location requested. Type: Format: Defined values: Default value: Example: Note: Element Void


Page 52 (92) 6 June 2002

5.32.1

type

Description: Defines the type of location requested Type: Format: Defined values: Attribute Char string CURRENT LAST After a location attempt has successfully delivered a location estimate, the location estimate is known as the current location at that point in time. The current location estimate is generally stored in the network until replaced by a later location estimate and is known as the last known location. The last known location may be distinct from the initial location., i.e. more recent. If a location attempt has successfully delivered, the current location is returned. Otherwise the last known location stored in the network is returned. In an originating emergency call, the location estimate at the commencement of the call set-up is known as the initial location.

CURRENT_OR_LAST INITIAL Default value: Example: Note: -

CURRENT

5.33

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. Type: Format: Defined values: Default value: Example: Note: Element Char string Maximum number of seconds (must be >= 0) Implementation specific. 3600

5.34Description:

mcc

Specifies the mobile country code (MCC). Type: Format: Defined values: Default value: Example: Note: Element Char String

3 digits, e.g. 234 for the UK234


Page 53 (92) 6 June 2002

5.35

mnc

Description: Specifies the mobile network code. Type: Format: Defined values: Default value: Example: Note: Element Char string Up to 3 digits e.g. 15 for Vodafone 215

5.36Description:

ms_action

Specifies the trigger that initiated the positioning of the MS. Type: Format: Defined values: Default value: Example: Note: Element Void

5.36.1Description:

type

Specifies the trigger that initiated the positioning of the MS. Type: Format: Defined values: Attribute Char string MS_AVAIL The positioning is triggered by the MS available notification when the MS regains radio connection with the network if the connection was previously lost. For more information refer to 3GPP TS 23.271 rel. 4.

Default value: Example: Note: -


Page 54 (92) 6 June 2002

5.37Description:

msid

This element represents an identifier of a mobile subscriber Type: Format: Defined values: Default value: Example: Element Char string 460703057640

Note: - When appropriate the MSID type format should confirm to the full standardised international representation of the MSID type, without any additional unspecified characters or spaces. As an example the GSM/3GPP identifiers should conform to the 3GPP CN TS 23.003, 'Numbering, Addressing and Identification' specification.

5.37.1Description:

type

Type of identifier for the mobile subscriber Type: Format: Defined values: Attribute Char string MSISDN IMSI IMEI MIN MDN EME_MSID ASID IPV4 OPE_ID IPV6 SESSID MSISDN Mobile Station International ISDN Number International Mobile Subscriber Identity International Mobile station Equipment Identity Mobile Identification Number Mobile Directory Number Emergency MSID Anonymous Subscriber Identity Mobile station IP address (Version 4) Operator specific Identity Mobile station IP address (Version 6) Session identifier relating to the user, which may be anonymous



Page 55 (92) 6 June 2002

5.37.2Description:

enc

Type of encoding for MSID identifier for the mobile subscriber Type: Format: Defined values: Attribute Char string ASC CRP Normal textual format Encrypted format: In some countries the Network Operator (where is placed the Location Server) isn't allowed to send to a LCS client the private information of an MS like MSISDN. The Network Operator can send out to LCS client the Encrypted MSID, since only the Network Operator is the only entity able to decode this information, the LCS client will be never able to break the privacy of the MS.


ASC

5.38Description:

MultiLineString

A collection of line strings. Type: Format: Defined values: Default value: Example: Element Char String ... Note:

5.38.1

gid See section 0.

5.38.2



Page 56 (92) 6 June 2002

5.39Description:

MultiPoint

A collection of points. Type: Format: Defined values: Default value: Example: Element Char String ... Note:

5.39.1

gid See section 0.

5.39.2


5.40Description:

MultiPolygons

A collection of polygons. Type: Format: Defined values: Default value: Example: Element Char String ... Note:

5.40.1

gid See section 0.


Page 57 (92) 6 June 2002

5.40.2


5.41Description:

ndc

Specifies the network destination code. Type: Format: Defined values: Default value: Example: Note: Element Char string Up to 4 digits e.g. 7785 for Vodafone 215

5.42Description:

nmr

Network specific measurement result for the target MS. Type: Format: Defined values: Default value: Example: Note: Measurement Results are encoded as 34 hexadecimal characters representing, 17 binary octets, in accordance with the Measurement Result information element described within GSM 04.18. Element Char string

For examples see relevant standards documents.-

5.43Description:

radius

The uncertainty radius is the radius (in distanceUnit) of the uncertainty; this is the geodesic distance between the arc and the position point. Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 850


Page 58 (92) 6 June 2002

5.44Description:

startAngle

The start angle is the angle (in angularUnit) between North and the first defined radius. Type: Format: Defined values: Default value: Example: Note: Element Char string 60

5.45Description:

stopAngle

The stop angle is the angle (in angularUnit) between the first and second defined radius. Type: Format: Defined values: Default value: Example: Note: Element Char string 180

5.46Description:

Point

A geographic 2D coordinate Type: Format: Defined values: Default value: Example: Element Char String 301628.312 451533.431 Note:


Page 59 (92) 6 June 2002

5.46.1

gid See section 0.

5.46.2


5.47Description:

Polygon

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. Type: Format: Defined values: Default value: Example: Element Char String ... Note:

5.47.1

gid See section 0.

5.47.2



Page 60 (92) 6 June 2002

5.48Description:

prio

Defines the priority of a location request Type: Format: Defined values: Default value: Example: Note: Element Void

5.48.1

type

Description: Defines the priority of a location request Type: Format: Defined values: Default value: Example: Note: Attribute Char string NORMAL The request is handled with normal priority HIGH The request is handled with high priority NORMAL

5.49Description:

pwd

The password for the registered user performing a location request. In an answer the string represents the password for a location server. Type: Format: Defined values: Default value: Example: Note: the5pwd Element Char string


Page 61 (92) 6 June 2002

5.50Description:

outRadius

The radius of a circle furthest away from the position in a CircularArcArea. The value is in the distanceUnit Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 120

5.51Description:

req_id

Unique identification of a request Type: Element Char string 435.23.01

Format: Defined values: Default value: Example:Note: -

5.52Description:

resp_req

This attribute represents response time requirement. Type: Format: Defined values: Default value: Example: Note: Element Void


Page 62 (92) 6 June 2002

5.52.1Description:

type

This attribute represents response time requirement Type: Format: Defined values: Attribute Char String NO_DELAY LOW_DELAY DELAY_TOL Default value: Example: DELAY_TOL No delay: The server should immediately return any location estimate that it currently has. Low delay: Fulfilment of the response time requirement takes precedence over fulfilment of the accuracy requirement. Delay tolerant: Fulfilment of the accuracy requirement takes precedence over fulfilment of the response time requirement.

Note: - The interpretation of these parameters is defined in 3GPP specifications 22.071 and 29.002. The use of this element together with resp_timer is for further study.

5.53Description:

resp_timer

Defines a timer for the response time within which the current location should be obtained and returned to the LCS Client. Type: Format: Defined values: Default value: Example: Element Char String Maximum number of seconds (must be >= 0) The default value is defined in the location server and will be implementation specific 45

Note: - The use of this element together with resp_reg is for further study

5.54Description:

result

A text string indicating the result of the request or an individual positioning Type: Format: Defined values: Default value: Example: Note: Element Char string See chapter 6.1 OK


Page 63 (92) 6 June 2002

5.54.1Description:

resid

This attribute represents a numeric representation of a result message Type: Format: Defined values: Attribute Char String [0-9]+ See chapter 6.1 Default value: Example: Note: OK

5.55Description:

semiMajor

Specifies the length (in distanceUnit) of the semi-major axis of an ellipse. Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 560

5.56Description:

semiMinor

Specifies the length (in distanceUnit) of the semi-minor axis of an ellipse. Type: Format: Defined values: Default value: Example: Note: Element Char String [0-9]+ 560


Page 64 (92) 6 June 2002

5.57Description:

serviceid

Specifies an id that is used by an entity to identify the service or application that is accessing the network. Type: Format: Defined values: Default value: Example: Note: Element Char String 0005

5.58Description:

requestmode

Defines the type of the service that has been requested by the ASP. Type: Format: Defined values: Default value: Example: Note: Element Void

5.58.1

type

Description: Defines the type of the service that has been requested by the ASP Type: Format: Defined values: Attribute Char string PASSIVE The service is one that is not directly initiated by the user. ACTIVE The service is one that the user is initiating personally. SESSION The Service is one that has an established session with the user PASSIVE

Default value: Example: Note: The default value is set to PASSIVE, as this is likely to be the one that is most restrictively defined by the user.


Page 65 (92) 6 June 2002

5.59Description:

session

This element should be presented in location request when the LCS Client is making 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. Type: Format: Defined values: Default value: Example: Element Char String 447073100177

Note: This information may be required for privacy validation of the location request by the VMSC, SGSN or MSC server

5.59.1

type

Description: Defines the type of the session that is established between the User Equipment and LCS Client Type: Format: Defined values: Default value: Example: Note: Attribute Char string APN Access Point Name. DIAL The number dialed by the user to access the LCS client.

5.60Description:

sessionid

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. In an answer it 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. Type: Format: Defined values: Default value: Example: Note: Element Char String 34eg6.876.76h4


Page 66 (92) 6 June 2002

5.61Description:

speed

The speed of the MS in m/s. Type: Format: Defined values: Default value: Example: Element Char String [0-9]+ 23

Note: This element is present if speed is possible to attain by the used positioning method.

5.62Description:

start_time

This element defines the absolute start time in a range of times. Type: Format: Element Char String The time is expressed as yyyyMMddhhmmss where: String yyyy MM dd hh mm ss Defined values: Default value: Example: Note: 20010630142810 Description Year Month Day Hours Minutes Seconds


Page 67 (92) 6 June 2002

5.62.1Description:

utc_off

Specifies the UTC offset in hours and minutes. Positive values indicate time zones east of Greenwich. Type: Format: Defined values: Default value: Example: Attribute Char string [+|-] ?0000-1400 20020813010423

Note: utc_off is specified as 'HHMM', where 'HH' can range between 0-14 and 'MM' between '0-59'. All other values shall result in error 105, 'Format error'.

5.63Description:

stop_time

This element defines the absolute stop time in a range of times. Type: Format: Element Char String The time is expressed as yyyyMMddhhmmss where: String yyyy MM dd hh mm ss Defined values: Default value: Example: Note: 20020630142810 Description Year Month Day Hours Minutes Seconds

5.63.1

utc_off See section 5.62.1


Page 68 (92) 6 June 2002

5.64Description:

subclient

Identifies the ASPs, resellers and portals in the chain of service providers between the network and the end-user Type: Format: Defined values: Default value: Example: Element -

TheASP 0006

Note: -

5.64.1Description:

last_client

Identifies whether the SUBCLIENT is the last one in the chain or not Type: Format: Defined values: Default value: Example: Note: Attribute Char String YES NO NO This is the last client the one that the end-user is actually communicating with This is not the last client

5.65Description:

ta

This Radio Access Network element that can arguably be used to offer enhanced positioning. (Timing Advance) Type: Format: Defined values: Default value: Example: Element Char string

0-630 3

Note: Further Information regarding this element can be found in the relevant GSM Specifications


Page 69 (92) 6 June 2002

5.66Description:

time

In a location answer this element indicates the time when the positioning was performed. Type: Format: Element Char String The time is expressed as yyyyMMddhhmmss where: String yyyy MM dd hh mm ss Defined values: Default value: Example: Note: 20010630142810 Description Year Month Day Hours Minutes Seconds

5.66.1

utc_off See section 5.62.1

5.67Description:

time_remaining

Defines the time remaining until the location server terminates the current triggered location service. The time for which 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 s stop time is defined or where the stop time exceeds the allowed value by the location server involved. Type: Format: Element Char String The time is expressed as ddhhmmss where: String dd hh mm ss Defined values: Default value: Example: Note: The default value is defined in the location server 00010000 Description Day Hours Minutes Seconds


Page 70 (92) 6 June 2002

5.68Description:

trl_pos

Specifies the position of the MS at a triggered location report. Type: Format: Defined values: Default value: Example: Element 4711 SYSTEM FAILURE 20011127104532 Note: -

5.68.1Description:

trl_trigger

Specifies the trigger that initiated the positioning of the MS at a triggered location report. Type: Format: Defined values: Default value: Example: Note: Attribute Char string PERIODIC MS_AVAIL The positioning is triggered when the periodical timer expired The positioning is triggered by the MS presence notification

5.69Description:

url

Specifies the location to which a response to a TLRR or an asynchronous SLIR should be sent to Type: Format: Defined values: Default value: Example: Element Char string http://location.client.com/Response/

Note: - URL is part of pushaddr element which may also contain id and pwd. These elements are used by the LCS Client to inform the Location Server what credentials to use when pushing a location report to the LCS Client in case of an asynchronous service.


Page 71 (92) 6 June 2002

5.70Description:

vlrno

Uniquely specifies a VLR within a network. Type: Format: Defined values: Default value: Example: Note: Element Char String In GSM this is the Global Title address. The Global Title is in the same format as an E.164 number. 1541154871

5.71Description:

vmscno

Uniquely specifies a VMSC within a network. Type: Format: Defined values: Default value: Example: Note: Element Char String In GSM this is the Global Title address. The Global Title is in the same format as an E.164 number. 1541154871

5.72Description:

X

The first ordinate in a coordinate system Type: Format: Defined values: Default value: Example: Note: Element Char string 33498.23


Page 72 (92) 6 June 2002

5.73Description:

Y

Second ordinate in a coordinate.system. This is optional if it is a linear coordinate system. Type: Format: Defined values: Default value: Example: Note: Element Char string 33498.23

5.74Description:

Z

third ordinate in a coordinate.system. This is optional if it is a 2D coordinate system. Type: Format: Defined values: Default value: Example: Note: Element Char string 33498.23


Page 73 (92) 6 June 2002

5.755.75.1Description:

Service attributesres_type

Defines a response type at the Standard Location Immediate Service. This attribute applies to the Standard Immediate Location Request message. Type: Format: Defined values: Attribute Char string SYNC ASYNC SYNC An LCS Client requests to receive the location response in one response An LCS Client request to receive the location responses one by one using some connections initiated by the location Server


5.75.2Description:

ver

Defines the version of the location protocol. This attribute is valid for ALL messages Type: Format: Defined values: Default value: Example: Note: Element Char string [0-9].[0-9].[0-9]


Page 74 (92) 6 June 2002

66.1

Result codesResult codesThis 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 Note: 99 199 299 499 599 Location server specific errors Request specific errors Network specific errors Reserved for future use Vendor specific errors

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.Description No error occurred while processing the request. The request can not be handled because of a general problem in the location server or the underlying network. An unspecified error used in case none of the other errors applies. 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. The request can not be handled due to congestion in the location server. The request can not be handled due to congestion in the mobile network. 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. 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 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

Resid 0 1 2

Slogan OK SYSTEM FAILURE UNSPECIFIED ERROR

3 4 5 6 101 102 103 104 105 106 107 108 109 110 111

UNAUTHORIZED APPLICATION UNKNOWN SUBSCRIBER ABSENT SUBSCRIBER POSITION METHOD FAILURE CONGESTION IN LOCATION SERVER CONGESTION IN MOBILE NETWORK UNSUPPORTED VERSION TOO MANY POSITION ITEMS FORMAT ERROR SYNTAX ERROR PROTOCOL ELEMENT NOT SUPPORTED SERVICE NOT SUPPORTED PROTOCOL ELEMENT ATTRIBUTE NOT SUPPORTED INVALID PROTOCOL ELEMENT VALUE INVALID PROTOCOL ELEMENT ATTRIBUTE


Page 75 (92) 6 June 2002

VALUE 112 113 201 202 PROTOCOL ELEMENT VALUE NOT SUPPORTED PROTOCOL ELEMENT ATTRIBUTE VALUE NOT SUPPORTED QOP NOT ATTAINABLE POSITIONING NOT ALLOWED

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 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 location request is disallowed by local regulatory requirements. The location server is not completely configured to be able to calculate a position. Vendor specific errors

204 207 500 599

DISALLOWED BY LOCAL REGULATIONS MISCONFIGURATION OF LOCATION SERVER


Page 76 (92) 6 June 2002

7

ReferencesReferences are either specific (identified by date of publication, edition number, version number, etc.) or non-specific: For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies.

7.1

References (Normative)[1] Hypertext Transfer Protocol HTTP/1.1 RFC 2616, June 1999 Available at http://www.ietf.org The TLS Protocol Version 1.0 RFC 2246, January 1999 Available at http://www.ietf.org Extensible Markup Language (XML) 1.0 W3C Recommendation: REC-xml-20001006 Available at http://www.w3c.org Internet Assigned Numbers Authority (IANA) http://www.iana.org/ US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986.

[2]

[3]

[4] [5]

7.2

References (Informative)[6] [7] [8] [9] [10] [11] GSM 02.71: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Service description; Stage 1". GSM 03.71: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Functional description; Stage 2". GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". 3GPP TS 22.071: "Location Services (LCS); Service description, Stage 1". 3GPP TS 23.171: "Functional stage 2 description of location services in UMTS" 3GPP TS 23.271: "Functional stage 2 description of LCS"


Page 77 (92) 6 June 2002

[12] [13] [14] [15] [16] [17] [18] [19]

3GPP TS 23.032: " Universal Geographical Area Description (GAD)" 3GPP TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". 3GPP TS 29.198-6 "Open Service Access (OSA) Application Programming Interface (API); Part 6: Mobility" Parlay API 2.1 Mobility Interfaces v1.1.1. Available on the Parlay web-site at http://www.parlay.org 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 at the public OGC document repository 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 available at http://www.opengis.org/techno/discussions/01-014r5.pdf OpenGIS Consortium Impementation Specification: Geography Markup Language V 2.0 available at http://www.opengis.net/gml/01029/GML2.html OpenGIS Consortium Abstract Specification Topic 1 Feature Geometry : 010101 at the public document repository http://www.opengis.org/techno/abstract/01-101.pdf.

[20]

[21]

[22]


Page 78 (92) 6 June 2002

88.1

Appendix A (informative): Adaptation to 3GPP LCSVersion mapping between 3GPP TS23.271 and this specificationThe following table shows the version number of this specification (LIF TS101) 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 Note: Conforming version number of LIF TS101 Version 3

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.

8.2

The terminology mapping table with 3GPP LCS SpecificationsThe following is a list of the terms in MLP used differently from the ones defined for 3GPP:

Term MLPLocation Server MS (Mobile Station) MSID (Mobile Station Identifier) MPC (Mobile Positioning Centre)

3GPPLCS Server UE Identification of the target UE

Notes

There is no term applicable to 3GPP.


Page 79 (92) 6 June 2002

8.3

The corresponding terms used for the location procedures in 3GPP LCS DefinitionThe following is a list of terms defined in MLP corresponding to the 3GPP LCS definition in TS23.271 for the location procedures.

Location procedures defined in 3GPP(23.271)Circuit Switched Mobile Terminating Location Request CS-MT-LR CS-MT-LR without HLR Query applicable to North America Emergency Calls only Packet Switched Mobile Terminating Location Request PS-MT-LR Network Induced Location Request NI-LR Packet Switched Network Induced Location Request PS-NI-LR LCS Service Request LCS Service Response LCS Service Request LCS Service Response LCS Service Request LCS Service Response Location Information

Services defined in MLPStandard Location Immediate Request Standard Location Immediate Answer Emergency Location Immediate Request Emergency Location Immediate Answer Standard Location Immediate Request Standard Location Immediate Answer Emergency Location Report

Location Information LCS Service Request

Emergenc

LIF TS 101 v3.0.0

Documents

Transcript of LIF TS 101 v3.0.0