SKELETON - ETSI€¦ · Web viewNote: Throughout this document, the word “protocol” is used...

ETSI TS 103 246-4 V0.0.5 (2015-04)

Satellite Earth Stations and Systems (SES);GNSS-based Location Systems;

Part 4: Requirements for Location Data Exchange Protocols

<

ETSI

TECHNICAL SPECIFICATION

ReferenceDTS/SES-00348

KeywordsGNSS, location, MSS, navigation, performance,

receiver, satellite, system, terminal

ETSI

650 Route des LuciolesF-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88

Important notice

Individual copies of the present document can be downloaded from:http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at

http://portal.etsi.org/tb/status/status.asp

If you find errors in the present document, please send your comment to one of the following services:http://portal.etsi.org/chaircor/ETSI_support.asp

Copyright Notification

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute yyyy.All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

of the 3GPP Organizational Partners.GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

ETSI TS 103 246-4 V0.0.5 (2015-04)2

http://portal.etsi.org/chaircor/ETSI_support.asp

http://portal.etsi.org/tb/status/status.asp

http://www.etsi.org/

Contents

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)3

Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://ipr.etsi.org).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)4

ForewordThis Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and Systems (SES).

Modal verbs terminologyIn the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

IntroductionThe increasing proliferation of location-based services is based on several trends in user applications and devices; these include notably the widespread adoption of multi-functional smart-phones etc., and the wider adoption of tracking devices (e.g. in transport). This need for new and innovative location-based services is generating a need for increasingly complex location systems. These systems are designed to deliver location-related information for one or more targets to user applications.

The wide spectrum of technical features identified in [i.1] calls for a new and broader concept for location systems, taking into account hybrid solutions in which GNSS technologies are complemented with other technology sensors to improve robustness and the performance.

Hence a set of standards for GNSS-based Location Systems (GBLS) is defined as follows, of which the present document is part 4:

Part 1: ETSI TS 103 246-1: GNSS-based Location Systems; Part 1: Functional requirements [1]

Part 2: ETSI TS 103 246-2: GNSS-based Location Systems; Part 2: Reference Architecture [2]

Part 3: ETSI TS 103 246-3: GNSS-based Location Systems; Part 3: Performance Requirements [3]

Part 4: ETSI TS 103 246-4: GNSS-based Location Systems; Part 4: Requirements for Location Data Exchange Protocols

Part 5: ETSI TS 103 246-5: GNSS-based Location Systems; Part 5: Performance Test Specification [i.2].

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)5

http://portal.etsi.org/Help/editHelp!/Howtostart/ETSIDraftingRules.aspx

1 ScopeThis document defines the requirements for data elements that may need to be exchanged within the GBLS and externally to applications using the GBLS.

The document also specifies data exchange models for these data elements which may form the basis of protocols (or for modification of protocols) and which may be used for the exchange of location-related data within the GNSS-based Location System (GBLS), as well as between the GBLS and external application modules.

In particular, this document defines the procedures and messages associated with these data exchange models. For brevity, these GBLS data exchange models are referred to as “protocols” throughout this document.

The GBLS data exchange models are defined to be independent of their underlying transport mechanisms.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)6

2 References2.1 GeneralReferences are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents that are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity.

2.2 Normative referencesThe following referenced documents are necessary for the application of the present document.

[1] ETSI TS 103 246-1, “GNSS-based Location Systems; Part 1: Functional requirements ”

[2] ETSI TS 103 246-2, “GNSS-based Location Systems; Part 2: Reference architecture ”

[3] ETSI TS 103 246-3, “GNSS-based Location Systems; Part 3: Performance Requirements ”

[4] OMA-TS-MLP-V3.5: "Mobile Location Protocol”

[5] OMA-TS-LPPe-V2: "LPP Extensions Specification”

[6] 3GPP TS 36.355, “LTE Positioning Protocol (LPP)”

2.3 Informative referencesThe following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.

[i.1]ETSI TR 103 183: “Satellite Earth Stations and Systems (SES); Global Navigation Satellite Systems (GNSS)-based applications and standardisation needs”.

[i.2]ETSI TS 103 246-5, “GNSS-based Location Systems; Part 5: Performance Test Specification”

[i.3]ETSI TS 122 071: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Location Services (LCS); Service description; Stage 1

[i.4]OMA-TS-ULP-V3: "User Plane Location Protocol".

[i.5]OMA-AD-LOCSIP-V1: “Location in SIP/IP core Architecture”

[i.6] ETSI ES 201 915: Open Service Access (OSA); Application Programming Interface (API)

[i.7] 3GPP2 C.S0022-B “Position Determination Service for cdma2000 Spread Spectrum Systems”

[i.8] 3GPP TS 25.331: “Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC) Protocol specification”

[i.9] 3GPP TS 44.031: “Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS Protocol (RRLP)”

[i.10]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)7

http://docbox.etsi.org/Reference

3 Definitions, symbols and abbreviationsRJM: Definitions, symbols and abbreviations should be in Part 1 of this specification.

3.1 DefinitionsFor the purposes of the present document, the following terms and definitions apply:

3.2 SymbolsFor the purposes of the present document, the following symbols apply: ε generic symbol representing an error (position error, velocity error, acceleration error, etc)ε* generic symbol representing an error estimate.Lr Level of reliability

3.3 AbbreviationsFor the purposes of the present document, the following abbreviations apply:

LPPLPPe LTE Positioning Protocol Extensions.

LSEPLSIPLTE Long-Term EvolutionMLP Mobile Location ProtocolOMASLPULP”

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)8

4 Data Exchange Requirements4.1 ContextThe GBLS data that shall or may be exchanged is defined in [2] in general terms for two main cases:

1) externally to applications using the GBLS, and

2) internally between modules of the GBLS.

The specific requirements for this data are defined further in Clause 7 below.

In addition, data exchange models are defined herein as a basis for protocols that may be used to transfer the GBLS data.

Add explanation of need for data and optionality of protocols

The diagram below shows these defined protocol modelss and their relevant interfaces applied to the GNSS-based Location System (GBLS) and its functional entities as defined in [2], within an end-to-end system.

Note: Throughout this document, the word “protocol” is used for brevity, when defining a GBLS “data exchange model”. The specifications herein are of data exchange models that may form the basis of protocols, or of modifications to existing protocols.

ApplicationInterface Module

Sensor Management

(GNSS and other Sensors)

Sensor Management

(GNSS and other Sensors)

Core

Interface ToExternal Serviceprovider

On-boardLocalisation

Module

On-boardLocalisation

Module

CentralisedLocalisation

Module

Central ManagementModule

ApplicationInterface Module

AssistanceServer

Key:

MandatoryOptional

Positioning Module Central Facility

LSIP

GNSS & other external

Systems

GNSS-based Location System

LSEP LSEP

Application(s) Application(s)

LSIP

LSIPLSIP

LSIP

Core Interface

Figure 4-1: Use of LSEP and LSIP in the GBLS architecture

The protocols defined are:

LSEP (Location System External Protocol): between the GBLS and an external application module (requesting entity)

LSIP (Location System Internal Protocol): between internal components of the GBLS.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)9

rob mort, 21/05/15,

These protocols shall shall be used for the transfer the of location-related data between the above entities, and for other associated data (e.g. capability, assistance etc.) as defined in [2].

The Protocol definitions in the following clauses addresses the following aspects:

3) protocol procedures represented by a message sequence chart, together with identification of each message

4) message definitions from a semantic point of view i.e. the information they shall contain, and how this information is structured.

5) information elements within messages and a set of relationships between them.

The definitions does not cover:

message definitionsyntax from a syntax point of view. Thus, no encoding scheme or data representation is given.

other underlying transport mechanisms for the messages.

4.1.1 LSEP Sessions and TransactionsData delivery occurs via two different schemes.

1) Immediate and punctual data delivery; delivery is done once, after the application module sends a location-related data request.

2) triggered and repeated data delivery; the application module sends a location-related data request which contains configuration parameters. These parameters define:

the triggering event, which triggers data delivery to the application module. Such an event can be either an area event (mobile target enters, is inside, leaves, or is outside a given area) or a velocity event (mobile target velocity increases above, is above, decreases below, or is below a given velocity).

the reporting scheme (e.g. periodic).

4.1.2 LSIP Sessions and Transactions??????

4.2 Protocol Compatibility4.2.1 OverviewIn a practical GBLS implementation there are several candidates among standardised protocols for LSEP in next generation location systems including:

Protocol Plane Transport Protocol Network Protocol3GPP LPP [6], TIA-801 [i.7], RRC [i.8], RRLP [i.9] ControlOMA MLP [4] User XML/HTML TCP/IPOSA/PARLAY API [i.6] User TCP/IPOMA LOCSIP [i.5] User SIP TCP/IPOMA ULP [i.4] User TCP/IPOMA LPP/LPPe [5] User TCP/IPAlso several of these protocols combining their advantages may be used.

Some factors in the choice of location protocol for LSEP are:

Whether the GBLS (i.e. the Positioning Module) incorporates a mobile terminal connected to a telecommumications network for alternative positioning etc. (3GPP, LTE etc.)

the underlying transport protocol (SIP, html, TCP/IP, SMS) and whether the control (3G, 2G) or user plane (IP, etc.) will be used.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)10

4.2.2 LSEP (and MLP)From the description in 4.1, a significant level of compatibility exists between requirements for LSEP is based on the procedures, messages and elements of and OMA MLP [4]..

MLP is an application-level protocol intended for querying the position of wireless mobile terninalsa Mobile Location Service (MLS) Client (e.g. a GBLSn external aApplication) to obtain the related data position of a location target (e.g. mobile terninal, GBLS Positioning Module, etc.) from a Location Server (e.g. the GBLS).

MLP is defined at the application layer of the protocol stack and is independent of underlying network technology. , and serves as the interface between a Location Server and a Mobile Location Service Client.

The MLP specification has been designed with extensibility in mind, notably allowing the addition of new messages and of new parameters to existing messages. Therefore LSEP defines extensions to MLP including and any modifications or exceptions.

MLP is defined at the application layer of the protocol stack. Its messages are The MLP API is defined in based on XML and it is defined to be transported in HTTP or SOAP. Only mapping to HTTP is defined in present days. For security reasons Secure Socket Layer (SSL) or Transport Layer Security (TLS) cryptographic protocols can be used to carry HTTP (or HTTPS). Apart from HTTPS Mobile Location Protocol which uses authentication by user and password, the information is carried in header part of MLP message.

SUPL??

MLP Services are based on location services defined by 3GPP.

Therefore LSEP procedures, messages and elements are based on those of MLP. Annex A provides further information.

The following matrix defines the relationship between GBLS and MLP terminology.

Table 4-1: MLP/GBLSLSEP/MLP terminology relationships

MLP LSEPMLP

tTermDefinitionMLP interpretation TermLSEP

termDefinitionLSEP interpretation

MS Mobile Station Location Target See definition in [2] []MSID MS identifier MSID Identifier for location targetsMobile subscriber

Owner of the MS who has subscribed to a communication service.Target of the Location service

Location Target user

Optional and minor role in GBLS context.Target of the location service is the Location Target, rather than its user.

Location Server

The application communicates exclusively with the Location Server

GBLSLocation System

LSEP protocol covers interface with GBLS itself

MLS Client The application, seen as a client of the Mobile Location Service

Application Module

See definition in [2] []

LCS Client The application, seen as a client of the Location Service

Application Module

See definition in [2] []

Location Server

The Server which provides location data of the MS to the Client

GBLS Location Server

The Server which provides location data of the Location Target to the Application

4.2.3 LSIP (and LPPe)LSIP is based on the procedures, messages and elements of From the description in 4.1, a significant level of compatibility exists between requirements for LSIP and OMA LPPe [5].

LPPe is intended to provide transactions for location-related data between a SET and SLP, which . Iin the case of the GBLS these elements would correspond respectively to the Positioning Module and either the Central Facility or and external SLP respectively.

In the GBLS, LSIP is used for interfaces between all internal functional blocks and hence two main solutions are foreseen:

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)11

http://en.wikipedia.org/wiki/Transport_Layer_Security

http://en.wikipedia.org/wiki/Simple_Object_Access_Protocol

http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol

http://en.wikipedia.org/wiki/XML

http://en.wikipedia.org/wiki/Application_Programming_Interface

1. either a single server shall be implemented for communication with all blocks via relays through intermediate blocks, and the server shall provide all required GBLS data

2. or each interface shall implement a separate client-server model and the server shall provide the relevant subset of the GBLS data.

LPPe is based on 3GPP LPP [6], but in addition allows convergence of positioning protocols over both in the User Plane (rather than Controland Control Planes),, thus which removinges potential bandwidth limitations and allowings messaging for new positioning technologies improving accuracy, availability and integrity to be implemented improving accuracy, availability and integrity.

Therefore LSIP procedures, messages and elements are based on those of LPPe. Annex A provides further information.

4.2.4 LSEP/MLP and LSIP/LPPe Common RelationshipsThe relationships between LSEP and MLP, and between LSIP and LPPe respectively, have common features as follows:

LSEP/LSIP procedures are based on only the MLP/LPPe procedures, messages and elements that are relevant to GBLS services

LSEP/LSIP adapts or extends the data structure only of the relevant MLP/LPPe messages.

LSEP/LSIP data structure is defined using Document Type Definition (DTD) format. This shall not be interpreted as a requirement to use XML format for LSEP/LSIP implementation.

The origin of LSEP/LSIP data elements given herein is highlighted with the following colour code:

element message element inherited from MLP/LPPe, left unchanged.

element new message element defined for LSEP/LSIP.

element existing MLP/LPPe message element but updated for LSEP/LSIP (update concerns either its meaning, its attributes or its position in the structure)..

element existing MLP/LPPe message element considered not applicable for LSEP/LSIP.

[IMPORTANT NOTE TO BE DONE RELATED TO WORDINGS “target” AND “server”, specific to LPP(e) domain, and for which another meaning is used in GBLS contect].

[…]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)12

Protocol procedures

5 LSEP Requirements

The Location System External Protocol defines location-related data delivery over the interface between the GBLS (or Location System) and the External Application module that is requesting the service of the GBLS.

LSEP Sessions and Transactions

Data transactions shall use the service schemes as defined for MLP [4] as follows:

1) Standard Location Immediate Service

2) Emergency Location Immediate Service

3) Standard Location Reporting Service

4) Emergency Location Reporting Service

5) Triggered Location Reporting Service

6) Historic Location Immediate Service (HLIS)

Common Element Definitions]

7) Identity Element Definitions

8) Function Element Definitions

9) Location Element Definitions

10) Shape Element Definitions

11) Quality of Position Element Definitions

12) Network Parameters Element Definitions

13) Context Element Definitions

5.1 Standard Location Reporting ServiceThis is a standard service for requesting the location of one or more location target. The service is used when a single location response is required immediately (within a set time) or when .sync several asynchronous location responses can be returned (until a predefined timeout limit is reached).

The service consists of the following messages:

- Standard Location Immediate Request

- Standard Location Immediate Answer

- Standard Location Immediate Report

The service is identical to the corresponding one in MLP. Full definition can be found in [4].[4], clause 5.2.3.2..

To illustrate the correspondence with MLP described in clause //4.3.1 (LSEP and MLP), the message flow diagram is reproduced below with the vocabulary adapted to the GBLS context.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)13

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Context_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Network_Parameters_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Quality_of_Position_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Shape_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Location_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Function_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Identity_Element_Definitions

http://en.wikipedia.org/wiki/Mobile_Location_Protocol#Common_Element_Definitions:.5B2.5D

Figure 5-2 - Message Flow for the Standard Location Immediate Service

Messages definitions are given in clause //6.1 (LSEP Messages) below.

5.2 Triggered Location Reporting ServiceThe triggered location reporting service is used when an application module wants the position of one or several location targets to be tracked, based on the following potential triggers:

- The periodicity of reporting defined by an interval time

- A location target action

- A Change of Area

- A Velocity Event

- A Distance Event, that is based on the distances between the location target and one or more reference objects.

- An Equidistance Event, that is based on the distance travelled from the last report.

- An ALN event that is based on a location target entering, leaving or being within an ALN.

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

- Triggered Location Reporting Pause Report

- Triggered Location Reporting Query Request

- Triggered Location Reporting Query Answer

- Triggered Location Query Report

The service is identical to the corresponding one in MLP, with the following exception: analytic reports, a specific feature of the MLP v3.5, are not supported in LSEP. Full definition can be found in [4], clause 5.2.3.6..

To illustrate the correspondence with MLP described in clause //4.3.1 (LSEP and MLP), the message flow diagram is reproduced below with the vocabulary adapted to the GBLS context.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)14

Figure 5-3 - Message Flow for the Standard Location Immediate Service

Messages definitions are given in clause //6.1 (LSEP Messages) below.

5.3 General Error MessageWhen an application module attempts to invoke a service not defined in this specification, the GBLS SHOULD return a General Error Message.

The general error message is similar to the one described in MLP. Full definition can be found in [4], clause 5.2.3.7..

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)15

6 LSIP Requirements6.1 LSIP Sessions and Transactions??????

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)16

A summary of LSIP data required to be transferred for each of on the GBLS interfaces defined in [2] and for each type of LSIP procedures (Location information exchange and Assistance data exchange) is as follows:

Table 67-1: GBLS LSIP supported procedures

Interface ID

Support of Location information exchange Support of Assistance data exchange

Status Nature of data Status Nature of data

1(GNSS)

Yes PVT, heading (tbc), observables (PSR, ADR), RF samples+ uncertainty on PVT, heading, and observables

Yes A-GNSS assistance data (models (nav, GGTO, UTC), RT integ, diff corr, data bit assist, acq assist, almanac, aux. info)+ ultra-tight hybrid assistance (NCO commands)

2(Telco)

Yes As per LPP and LPPe “request / provide location info”(Nb : do they suit hybridization need ? yes, they already cover UE-assisted method, i.e. transmission of measurements to server)

Yes As per LPP and LPPs “request / provide assistance data”

3(INS)

Yes Gyro/accelero measurements (see clause Error: Reference source not found)

(make sure uncertainties are provided)

Yes I see only one thing : motion type estimate (pedestrian, vehicle,…) to allow sensor configuration/adaptation to category of motion..[tbc]

4(Magneto)

Yes magnetometer measurements (see clause Error: Reference source not found)

No

5(odom)

Yes odometer measurements (see clause Error: Reference source not found)

No

6(BFN)

Yes Estimation of the following jammer characteristics : direction of arrival, received power, frequency

Estimation of the following delayed signal (multipath) characteristics : direction of arrival, relative power, delay, carrier Doppler frequency

Yes GNSS constellations ephemeris, GNSS time,antenna attitude (to support DoA estimation)

7(map)

no Yes Map data seen as assistance data. (in that case, the “server” is the “map sensor block”)

8 Yes location information in line with “location-related data” defined in LSEP :Position (horizontal, vertical), velocity (linear/angular) acceleration (linear/angular), heading, timeQoS estimation : estimated accuracy of the above param.Integrity and Authentication parameters

No -[tbc]

9 All location data identified on I/F 8 All assistance data identified on the sensor I/F ( 1 to 7)

10 All location data present an interfaces 1 to 9 Yes All location data present an interfaces 1 to 9

8 Yes location information in line with “location-related data” defined in LSEP :

Position (horizontal, vertical), velocity (linear/angular) acceleration (linear/angular), heading, timeQoS estimation : estimated accuracy of the above param.Integrity and Authentication parameters

No -[tbc]

8bis see Interface 8 see Interface 8

9 All location data identified on I/F 8 Yes All assistance data identified on the sensor I/F ( 1 to 7)

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)17

6.2 Procedures related to Assistance data transferThe purpose of the procedures in this section is to enable a “target” entity to request assistance data from a “server” entity to assist in positioning, and to enable a “server” entity to transfer assistance data to a “target” entity in the absence of a request.

In the GBLS context, the assistance data can be conveyed on several interfaces, as illustrated in Table 6-1, whereas LPP and LPPe envision a single interface, between the “target” and the “server”. Due to this specificity, the roles of “target” and “server” can be endorsed by different GBLS components. The mapping of GBLS components to “server” and “target” roles defined by LPP and LPPe is given in Table 6-2 below.

Table 67-2: role of GBLS components Assistance data transfer

Framework Interface “Server” role “Target” roleLPP(informative)

n/a(informative)

E-SMLC (refer to Error: Referencesource not found)

(informative)

UE (refer to Error: Referencesource not found)

(informative)LSIP (GBLS) Interface 1 Localization Module GNSS sensorLSIP (GBLS) Interface 2 Localization Module Telecommunication moduleLSIP (GBLS) Interface 3 Localization Module Inertial Navigation SensorLSIP (GBLS) Interface 6 Localization Module Beam Forming AntennaLSIP (GBLS) Interface 7 Localization Module Map data baseLSIP (GBLS) Interface 9 Cenral Management module Localization Module

6.2.1 Assistance data transfer procedureThe “Assistance Data Transfer” procedure is shown in Figure 6-2. It is identical to the procedure with the same name from 3GPP TS 36.344. Refer to LPP [6] (clause 5.2.1) for full procedure description.

Figure 67-2: Assistance data transfer procedure (source LPP [6])

6.2.2 Assistance data delivery procedureThe “Assistance data delivery” procedure is shown in Figure 6-3. It is identical to the procedure with the same name from 3GPP TS 36.344. Refer to LPP [6] (clause 5.2.2) for full procedure description.

Figure 67-3: Assistance data delivery procedure (source LPP [6])

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)18

6.2.3 Periodic/Triggered assistance data transfer with updateThis procedure enables a “target” entity to request a “server” entity to send assistance data periodically either at defined intervals or when specific triggering criteria are met. The procedure also allows the “target” entity or the “server” entity to modify the type of assistance data and/or the periodicity and triggering criteria while the delivery procedure is on-going. The procedure shall not be combined with the support of any other assistance data and shall thus use LSIP transactions that are dedicated to starting, transferring or updating one specific type of Periodic/Triggered Assistance Data.

- Initiating and terminating the procedure

Figure 6-4 shows how a “Periodic/Triggered assistance data transfer with update” may be initiated and terminated. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.1) for full procedure description.

Figure 67-4: Periodic/Triggered Assistance Data transfer procedure with Update (source LPPe [5])

- Target Update

Figure 6-5 shows how the target may update an on-going a Periodic/Triggered Assistance Data Transfer that was started according to Figure 6-4 above. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.1) for full procedure description.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)19

Figure 67-5: Periodic/Triggered Assistance Data transfer procedure with target update (source LPPe [5])

- Server Update

Figure 6-6 shows how the target may update an on-going a Periodic/Triggered Assistance Data Transfer that was started according to Figure 6-4 above. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.1) for full procedure description.

Figure 67-6: Periodic/Triggered Assistance Data transfer procedure with server update (source LPPe [5])

6.2.4 Other procedure FFSSegmented assistance data transfer

Broadcast of assistance data

6.3 Procedures related to location information transfer The purpose of the procedures in this section is to enable a “server” entity to request location measurement data and/or a location estimate from a “target” entity, and to enable a “target” entity to transfer location measurement data and/or a location estimate to a “server” entity in the absence of a request.

In the GBLS context, the location information can be conveyed on several interfaces, as illustrated in Table 6-1, whereas LPP and LLPe envision a single interface, between the “target” and the “server”. Due to this specificity, the roles of “target” and “server” can be endorsed by different GBLS components. The mapping of GBLS components to “server” and “target” roles defined by LPP and LPPe is given in Table 6-3 below.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)20

Table 67-3: role of GBLS components in Location information transfer

Framework Interface “Server” role “Target” roleLPP(informative)

n/a(informative)

E-SMLC (refer to Error: Referencesource not found)

(informative)

UE (refer to Error: Referencesource not found)

(informative)LSIP (GBLS) Interface 1 Localization Module GNSS sensorLSIP (GBLS) Interface 2 Localization Module Telecommunication moduleLSIP (GBLS) Interface 3 Localization Module Inertial Navigation SensorLSIP (GBLS) Interface 4 Localization Module MagnetometerLSIP (GBLS) Interface 5 Localization Module OdometerLSIP (GBLS) Interface 6 Localization Module Beam Forming AntennaLSIP (GBLS) Interface 8 Application Module Interface Localization ModuleLSIP (GBLS) Interface 8bis Application Module Interface Central management moduleLSIP (GBLS) Interface 9 Cenral Management module Localization Module

6.3.1 Location information transfer procedureThe “Location information Transfer” procedure is shown in Figure 6-7. It is identical to the procedure with the same name from 3GPP TS 36.344. Refer to LPP [6] (clause 5.3.1) for full procedure description.

Figure 67-7: Location Information transfer procedure (source LPP [6])

6.3.2 Location information delivery procedureThe “Location information delivery” procedure is shown in Figure 6-8. It is identical to the procedure with the same name from 3GPP TS 36.344. Refer to LPP [6] (clause 5.3.2) for full procedure description.

Figure 67-8: Location Information delivery procedure (source LPP [6])

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)21

6.3.3 Periodic/Triggered location information transfer with updateThis procedure enables a “server” entity to request a “target” entity to send location information periodically either at defined intervals or when specific triggering criteria are met. The procedure also allows the “target” entity or the “server” entity to modify the type of location information and/or the periodicity and triggering criteria while the delivery procedure is on-going. The procedure shall not be combined with the support of any other location information and shall thus use LSIP transactions that are dedicated to starting, transferring or updating one specific type of Periodic/Triggered Location Information.

- Initiating and terminating the procedure

Figure 6-9 shows how a “Periodic/Triggered location information transfer with update” may be initiated and terminated. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.2) for full procedure description.

Figure 67-9: Periodic/Triggered Location Information transfer procedure with Update (source LPPe [5])

- Server update

Figure 6-10 shows how the server may update an on-going a Periodic/Triggered location information Transfer that was started according to Figure 6-9 above. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.2) for full procedure description.

Figure 67-10: Periodic/Triggered Location Information transfer procedure with server update (source LPPe [5])

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)22

- Target update

Figure 6-11 shows how the target may update an on-going a Periodic/Triggered location information Transfer that was started according to Figure 6-9 above. It is identical to the procedure with the same name from OMA LPPe v2.0. Refer to LPPe [5] (clause 5.2.2) for full procedure description.

Figure 67-11: Periodic/Triggered Location Information transfer procedure with target update (source LPPe [5])

6.3.4 Other procedure FFSSegmented location information transfer

Crowd sourcing

6.4 Error handling proceduresError handling procedures determine how a receiving entity (target device or location server) behaves in cases when it receives erroneous or unexpected data or detects that certain data are missing.

6.5 Abort procedures

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)23

7 Data Exchange Message Definition

7.1 LSEP MessagesThe message content necessary to implement the services described in clause //4.1 are described in the sections below.

7.1.1 Standard Location Immediate Request

<!ELEMENT slir ((msids | (msid, codeword?, gsm_net_param?, trans_id?)+), eqop?, req_infogeo_info?, time_synch?, loc_type?, prio?, pushaddr?, service_coverage?, MapRequest?, MotionStateRequest?, ReferencePoint? %extension.param;)>

<!ATTLIST slir ver CDATA #FIXED "3.5.0"res_type (SYNC | ASYNC) "SYNC">

The following rules apply to the message content and structure:

- usage of “req_info”: a location request shall contain the structure “req_info” which indicate the type of location-related data required by the application module to the location system.

- usage of “ReferencePoint”: Rules are defined in [4], clause 5.2.3.2.1, for relative location determination (horizontal position, altitude). The concept hereby defined extends to the following location-related data: relative velocity and relative acceleration.

As a consequence, if required data “req_info” concerns heading and/or time synchronisation, “ReferencePoint” shall not be present on the location request.

7.1.2 Standard Location Immediate AnswerSAME DTD AS OMA MLP

<!ELEMENT slia ((pos+ | req_id | (result, add_info?)) %extension.param;)><!ATTLIST slia

ver CDATA #FIXED "3.5.0">

In case of EMI localisation: location target identified “MSID” sent back by the GBLS to the client shall be set by the GBLS. It shall ensure that this identifier is unique all the along the GBLS lifecycle.

7.1.3 Standard Location Immediate Report

<!ELEMENT slirep (req_id, pos+ %extension.param;)><!ATTLIST slirep


ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)24

7.1.4 Triggered Location Reporting Request

<!ELEMENT tlrr (msids, interval?, start_time?, stop_time?, duration?, tlrr_event?, analytic_report?, qop?, req_infogeo_info?, time_synch?, pushaddr?, loc_type?, prio?, service_coverage?, MapRequest?, ReferencePoint? %extension.param;)>

<!ATTLIST tlrr ver CDATA #FIXED "3.5.0">

The following rules apply to the message content and structure:

- usage of “ReferencePoint”: refer to clause //6.1.1

7.1.5 Triggered Location Reporting Answer

<!ELEMENT tlra (((req_id, lcs_ref?) | (result, add_info?)) %extension.param;)>

<!ATTLIST tlra ver CDATA #FIXED "3.5.0">

7.1.6 Triggered Location Report

<!ELEMENT tlrep (req_id, lcs_ref?, trl_pos+, time_remaining? %extension.param;)>

<!ATTLIST tlrep ver CDATA #FIXED "3.5.0"More (YES | NO) "NO">

7.1.7 Triggered Location Reporting Stop Request

<!ELEMENT tlrsr ((msids | msid)?, req_id, lcs_ref? %extension.param;)><!ATTLIST tlrsr


7.1.8 Triggered Location Reporting Stop Answer

<!ELEMENT tlrsa ((((msids | msid)?, req_id) | (result, add_info?)) %extension.param;)>

<!ATTLIST tlrsa ver CDATA #FIXED "3.5.0">

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)25

7.1.9 Triggered Location Reporting Pause Report

<!ELEMENT tlrpr (msid, req_id, lcs_ref? %extension.param;)><!ATTLIST tlrpr

ver CDATA #FIXED "3.5.0"cause (PAUSE | RESUME) #REQUIRED>

7.1.10 Triggered Location Reporting Query Request

<!ELEMENT tlrqr (pushaddr? %extension.param;)><!ATTLIST tlrqr


7.1.11 Triggered Location Reporting Query Answer

<!ELEMENT tlrqa ((query_id | (result, add_info?)) %extension.param;)><!ATTLIST tlrqa


7.1.12 Triggered Location Query Report

<!ELEMENT tlqrep (query_id, trigger_data* %extension.param;)><!ATTLIST tlqrep

ver CDATA #FIXED "3.5.0"last (YES | NO) #REQUIRED>

7.1.13 General Error Message

<!ELEMENT gem (result, add_info?)><!ATTLIST gem


7.2 LSIP Messages editorial note :

Each of the 6 messages below (clause 6.2.1 to 6.2.6) is the result of :

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)26

- the concatenation of the LPP and LPPe information elements of the corresponding equivalent message (for instance : message “GBLS-RequestLocationInformation”, created in the frame of the present LSIP, contained IEs from message “RequestLocationInformation-r9-IEs” of LPP, and “OMA-LPPe-RequestLocationInformation” of LPPe)

- note that some LPP/LPPe IEs are modified in the present LSIP in order to adapt them to the GBLS framework. These are highlighted in blue

- it also contains new IEs, specific to GBLS framework, mainly to address the use of new sensors. They are highlighted in green.]

7.2.1 Request Location InformationThe RequestLocationInformation message is used by the “server” entity to request location-related data to “target” entity.

-- ASN1START GBLS-RequestLocationInformation::= SEQUENCE { commonIEsRequestLocationInformation CommonIEsRequestLocationInformation OPTIONAL,-- Need ON a-gnss-RequestLocationInformation A-GNSS-RequestLocationInformation OPTIONAL,-- Need ON otdoa-RequestLocationInformation OTDOA-RequestLocationInformation OPTIONAL,-- Need ON ecid-RequestLocationInformation ECID-RequestLocationInformation OPTIONAL,-- Need ON commonIEsRequestLocationInformation OMA-LPPe-CommonIEsRequestLocationInformation OPTIONAL, agnss-RequestLocationInformation OMA-LPPe-AGNSS-RequestLocationInformation OPTIONAL, otdoa-RequestLocationInformation OMA-LPPe-OTDOA-RequestLocationInformation OPTIONAL, eotd-RequestLocationInformation OMA-LPPe-EOTD-RequestLocationInformation OPTIONAL, otdoa-utra-RequestLocationInformation OMA-LPPe-OTDOA-UTRA-RequestLocationInformation OPTIONAL, ecid-lte-RequestLocationInformation OMA-LPPe-ECID-LTE-RequestLocationInformation OPTIONAL, ecid-gsm-RequestLocationInformation OMA-LPPe-ECID-GSM-RequestLocationInformation OPTIONAL, ecid-utra-RequestLocationInformation OMA-LPPe-ECID-UTRA-RequestLocationInformation OPTIONAL, wlan-ap-RequestLocationInformation OMA-LPPe-WLAN-AP-RequestLocationInformation OPTIONAL, ecid-wimax-RequestLocationInformation OMA-LPPe-ECID-WiMax-RequestLocationInformation OPTIONAL, sensor-RequestLocationInformation OMA-LPPe-Sensor-RequestLocationInformation OPTIONAL, srn-RequestLocationInformation OMA-LPPe-SRN-RequestLocationInformation OPTIONAL, irb-RequestLocationInformation OMA-LPPe-ver2-0-IRB-RequestLocationInformation OPTIONAL, pdr-RequestLocationInformation OMA-LPPe-ver2-0-PDR-RequestLocationInformation OPTIONAL, crowdsourcing-RequestLocationInformation OMA-LPPe-ver2-0-Crowdsourcing- RequestLocationInformation OPTIONAL inertialSensor-RequestLocationInformation GBLS-IntertialSensor-RequestLocationInformation OPTIONAL, magnetometer-RequestLocationInformation GBLS-Magnetometer-RequestLocationInformation OPTIONAL, odometer-RequestLocationInformation GBLS-Odometer-RequestLocationInformation OPTIONAL, bfn-RequestLocationInformation GBLS-BFN-RequestLocationInformation OPTIONAL,... }-- ASN1STOP

Descriptions of the GPLS-RequestLocationInformation individual components are given in section 8.2

7.2.2 Provide Location InformationThe ProvideLocationInformation message is used by a “target” entity to provide location-related data to a “server” entity.

-- ASN1START

GBLS-ProvideLocationInformation::= SEQUENCE { commonIEsProvideLocationInformation CommonIEsProvideLocationInformation OPTIONAL, a-gnss-ProvideLocationInformation A-GNSS-ProvideLocationInformation OPTIONAL, otdoa-ProvideLocationInformation OTDOA-ProvideLocationInformation OPTIONAL, ecid-ProvideLocationInformation ECID-ProvideLocationInformation OPTIONAL,

commonIEsProvideLocationInformation OMA-LPPe-CommonIEsProvideLocationInformation OPTIONAL,a-gnss-ProvideLocationInformation OMA-LPPe-AGNSS-ProvideLocationInformation OPTIONAL,otdoa-ProvideLocationInformation OMA-LPPe-OTDOA-ProvideLocationInformation OPTIONAL,eotd-ProvideLocationInformation OMA-LPPe-EOTD-ProvideLocationInformation OPTIONAL,otdoa-utra-ProvideLocationInformation OMA-LPPe-OTDOA-UTRA-ProvideLocationInformation OPTIONAL,ecid-lte-ProvideLocationInformation OMA-LPPe-ECID-LTE-ProvideLocationInformation OPTIONAL,ecid-gsm-ProvideLocationInformation OMA-LPPe-ECID-GSM-ProvideLocationInformation OPTIONAL,ecid-utra-ProvideLocationInformation OMA-LPPe-ECID-UTRA-ProvideLocationInformation OPTIONAL,wlan-ap-ProvideLocationInformastion OMA-LPPe-WLAN-AP-ProvideLocationInformation OPTIONAL,ecid-wimax-ProvideLocationInformastion OMA-LPPe-ECID-WiMax-ProvideLocationInformation OPTIONAL,sensor-ProvideLocationInformation OMA-LPPe-Sensor-ProvideLocationInformation OPTIONAL,srn-ProvideLocationInformation OMA-LPPe-SRN-ProvideLocationInformation OPTIONAL,irb-ProvideLocationInformation OMA-LPPe-ver2-0-IRB-ProvideLocationInformation OPTIONAL,pdr-ProvideLocationInformation OMA-LPPe-ver2-0-PDR-ProvideLocationInformation OPTIONAL,crowdsourcing-ProvideLocationInformation OMA-LPPe-ver2-0-Crowdsourcing-ProvideLocationInformation OPTIONAL,inertialSensor-ProvideLocationInformation GBLS-IntertialSensor-ProvideLocationInformation OPTIONAL,

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)27

magnetometer-ProvideLocationInformation GBLS-Magnetometer-ProvideLocationInformation OPTIONAL,odometer-ProvideLocationInformation GBLS-Odometer-ProvideLocationInformation OPTIONAL,bfn-ProvideLocationInformation GBLS-BFN-ProvideLocationInformation OPTIONAL,...

}

-- ASN1STOP

Descriptions of the GPLS-ProvideLocationInformation individual components are given in section 8.2

[tbd] [Editorial Note: add a few words on the OPTIONAL nature of each IEs.]

7.2.3 Request Assistance DataThe RequestAssistanceData message is used by the “target” entity to request assistance data from the “server” entity.

-- ASN1START

GBLS-RequestAssistanceData::= SEQUENCE {commonIEsRequestAssistanceData CommonIEsRequestAssistanceData OPTIONAL,a-gnss-RequestAssistanceData A-GNSS-RequestAssistanceData OPTIONAL,otdoa-RequestAssistanceData OTDOA-RequestAssistanceData OPTIONAL,commonIEsRequestAssistanceData OMA-LPPe-CommonIEsRequestAssistanceData OPTIONAL,agnss-RequestAssistanceData OMA-LPPe-AGNSS-RequestAssistanceData OPTIONAL,otdoa-RequestAssistanceData OMA-LPPe-OTDOA-RequestAssistanceData OPTIONAL,eotd-RequestAssistanceData OMA-LPPe-EOTD-RequestAssistanceData OPTIONAL,otdoa-utra-RequestAssistanceData OMA-LPPe-OTDOA-UTRA-RequestAssistanceData OPTIONAL,ecid-lte-RequestAssistanceData OMA-LPPe-ECID-LTE-RequestAssistanceData OPTIONAL,ecid-gsm-RequestAssistanceData OMA-LPPe-ECID-GSM-RequestAssistanceData OPTIONAL,ecid-utra-RequestAssistanceData OMA-LPPe-ECID-UTRA-RequestAssistanceData OPTIONAL,epdu-RequestAssistanceData EPDU-Sequence OPTIONAL,wlan-ap-RequestAssistanceData OMA-LPPe-WLAN-AP-RequestAssistanceData OPTIONAL,sensor-RequestAssistanceData OMA-LPPe-Sensor-RequestAssistanceData OPTIONAL,srn-RequestAssistanceData OMA-LPPe-SRN-RequestAssistanceData OPTIONAL,pdr-RequestAssistanceData OMA-LPPe-ver2-0-PDR-RequestAssistanceData OPTIONAL,irb-RequestAssistanceData OMA-LPPe-ver2-0-IRB-RequestAssistanceData OPTIONAL,inertialSensor-RequestAssistanceData GBLS-IntertialSensor-RequestAssistanceData OPTIONAL,magnetometer-ProvideAssistanceData GBLS-Magnetometer-RequestAssistanceData OPTIONAL,odometer-ProvideAssistanceData GBLS-Odometer-RequestAssistanceData OPTIONAL,bfn-ProvideAssistanceData GBLS-BFN-RequestAssistanceData OPTIONAL,

...}-- ASN1STOP

Descriptions of the GPLS-RequestAssistanceData individual components are given in section 8.2

7.2.4 Provide Assistance DataThe ProvideAssistanceData message is used by the “server” entity to provide assistance data to the “target” entity either in response to a request from the “target” entity or in an unsolicited manner.

-- ASN1START

GBLS-ProvideAssistanceData::= SEQUENCE {commonIEsProvideAssistanceData CommonIEsProvideAssistanceData OPTIONAL,-- Need ONa-gnss-ProvideAssistanceData A-GNSS-ProvideAssistanceData OPTIONAL,-- Need ONotdoa-ProvideAssistanceData OTDOA-ProvideAssistanceData OPTIONAL,-- Need ONcommonIEsProvideAssistanceData OMA-LPPe-CommonIEsProvideAssistanceData OPTIONAL,agnss-ProvideAssistanceData OMA-LPPe-AGNSS-ProvideAssistanceData OPTIONAL,otdoa-ProvideAssistanceData OMA-LPPe-OTDOA-ProvideAssistanceData OPTIONAL,eotd-ProvideAssistanceData OMA-LPPe-EOTD-ProvideAssistanceData OPTIONAL,otdoa-utra-ProvideAssistanceData OMA-LPPe-OTDOA-UTRA-ProvideAssistanceData OPTIONAL,ecid-lte-ProvideAssistanceData OMA-LPPe-ECID-LTE-ProvideAssistanceData OPTIONAL,ecid-gsm-ProvideAssistanceData OMA-LPPe-ECID-GSM-ProvideAssistanceData OPTIONAL,ecid-utra-ProvideAssistanceData OMA-LPPe-ECID-UTRA-ProvideAssistanceData OPTIONAL,epdu-ProvideAssistanceData EPDU-Sequence OPTIONALwlan-ap-ProvideAssistanceData OMA-LPPe-WLAN-AP-ProvideAssistanceData OPTIONAL,sensor-ProvideAssistanceData OMA-LPPe-Sensor-ProvideAssistanceData OPTIONAL,srn-ProvideAssistanceData OMA-LPPe-SRN-ProvideAssistanceData OPTIONAL,pdr-ProvideAssistanceData OMA-LPPe-ver2-0-PDR-ProvideAssistanceData OPTIONAL,irb-ProvideAssistanceData OMA-LPPe-ver2-0-IRB-ProvideAssistanceData OPTIONAL,inertialSensor-ProvideAssistanceData GBLS-IntertialSensor-ProvideAssistanceData OPTIONAL,magnetometer-ProvideAssistanceData GBLS-Magnetometer-ProvideAssistanceData OPTIONAL,odometer-ProvideAssistanceData GBLS-Odometer-ProvideAssistanceData OPTIONAL,bfn-ProvideAssistanceData GBLS-BFN-ProvideAssistanceData OPTIONAL,...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)28

-- ASN1STOP

Descriptions of the GPLS-ProvideAssistanceData individual components are given in section 8.2

7.2.5 AbortThe GBLS-Abort message carries a request to abort an on-going LSIP positioning procedure.

-- ASN1START

GBLS-abort ::= SEQUENCE {commonIEsAbort CommonIEsAbort OPTIONAL,-- Need ONcommonIEsAbort OMA-LPPe-CommonIEsAbort OPTIONAL,agnssAbort OMA-LPPe-AGNSS-Abort OPTIONAL,...,

}

-- ASN1STOP

Description of GBLS-abort components is given in section 8.2

7.2.6 ErrorThe GBLS-Error message carries information concerning a LSIP message that was received with errors.

-- ASN1START

GBLS-error ::= SEQUENCE {commonIEsError CommonIEsError OPTIONAL,-- Need ONcommonIEsError OMA-LPPe-CommonIEsError OPTIONAL,}

-- ASN1STOP

Description of GBLS-error components is given in section 8.2

8 Data Exchange Elements Definition8.1 LSEP Information Elements 8.1.1 OverviewElements composing the LSEP messages are defined in the following clauses, using DTD representation to keep consistency with content of clause //6.1 (LSEP messages).

Elements are defined from a semantic point of view only. As mentioned in introduction (refer to clause //4.1 (context)), this specification does not aim at providing normative content related to detailed syntax (variable type, encoding scheme, etc.), which is left up to protocol implementations. Some details corresponding to the detailed syntax are however provided in the sections below. These details are given under two possible scenarios:

- they either concern simple elements, such as Boolean or character string, whose content is easily identifiable (i.e. with a predefined/limited number of values). In such case, element syntax definition is provided in the normative clauses below (//7.1.2 to //7.1.34).

- for the other elements, no syntax definition is given. However, informative //annex A provides information derived from the elements definition, and which would contribute to the selection of a syntax in view of an implementation of LSEP. This information contains variable type, range and accuracy, all issued from technical constrains.

Semantic definition of LSEP elements used below but not listed in clauses //7.1.2 to //7.1.34 can be found in [4]. In such case, syntax proposed in [4] shall be ignored.

8.1.1.1 Identity elements

<!ELEMENT msids (((msid, codeword?, session?, trans_id?) | (msid_range,

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)29

UNKNOWN | OTHER)

<!ELEMENT pd (time, time_p, (shape | civicloc | (shape, civicloc) | relativelocation), MapData?, (alt, alt_qos?)?, (speed, vel_qos?)?, (direction, head_qos?)?, (accel, accel_qos?)?, lev_conf?, hor_qos?, qos_not_met?, qos_status?, MotionStateList?, (floor_number, floor_number_unc?)?)>

<!ELEMENT time_p (#PCDATA)><!ELEMENT alt_qos (alt_unc, lev_conf?, auth_flag?)><!ELEMENT vel_qos (vel_unc, lev_conf?, auth_flag?)><!ELEMENT head_qos (head_unc, lev_conf?, auth_flag?)><!ELEMENT accel (#PCDATA)><!ELEMENT accel_qos (accel_unc, lev_conf?, auth_flag?)><!ELEMENT hor_qos (lev_conf?, auth_flag?)><!ELEMENT alt_unc (#PCDATA)><!ELEMENT lev_conf (#PCDATA)><!ELEMENT vel_unc (#PCDATA)><!ELEMENT head_unc (#PCDATA)><!ELEMENT accel_unc (#PCDATA)><!ELEMENT auth_flag (#PCDATA)>

The following rules apply to the elements content and structure:

- usage of “req_info”: this element, which describes the location-related data required to the location system, shall contain at least the element “geo_info”, this in order to ensure that the coordinate reference system to be used for location-related data determination is defined in the any location request.

- usage of “req_emidata”: optional attribute req_emidata turns mandatory anytime the location request (slir or tlrr) identifies the location targets as being EMI sources (refer to clause //7.1.1.1 [identity elements]). It identifies the required EMI-related information.

- usage of “auth_req”: when this flag is set to “YES” for element “geo_info” (resp. “alt_info”, “vel_info”, “accel_info”, “head_info” and/or “time_synch”) in a location request (slir or tlrr), the optional element “auth_flag” under “hor_qos” (resp. “alt_qos”, “vel_qos”, “accel_qos”, “head_qos” and/or “synch_status”) in the subsequent answer or report(s) (slia, slir or tlrep) become mandatory.

- usage of “lev_conf “: a location request (slir, tlrr) can require a specific quality of position (defined in elements resp. eqop, qop).

3. - If optional element “h_conf_lev” (resp. “v_conf_lev” and/or “vel_conf_lev”) is present in such elements with attribute “conf_class” set to “ALERT”, it shall be interpreted as a request to the location system to implement integrity determination on the horizontal position (resp. vertical position and/or velocity). Integrity concept is defined in [3]. Element “h_conf_lev” (resp. “v_conf_lev” and/or “vel_conf_lev”) then defines the integrity risk required to be respected by the location system. Corresponding protection level determined by the GBLS is given as follows.

- for integrity of location target horizontal position, position shall be reported in the subsequent answer or report(s) through a “CircularArea” shape: protection level is given by the shape radius (element of the “CircularArea”). As a consequence, attribute “requested_positiondata” of element “geo_info” in the location request (slir or tlrr) shall have values “SHAPE” or “SHAPE_AND_CIVICLOC”.

- for integrity of location target vertical position , protection level shall be given by the element "alt_unc”

- for integrity of location target velocity, protection level shall be given by the element "vel_unc”

4. In addition, the element “lev_conf” under “hor_qos” (resp. “alt_qos” and/or “vel_qos”) in the subsequent answer or report(s) shall either be absent, or equal to the required integrity risk, i.e. “h_conf_lev” (resp. “v_conf_lev” and/or “vel_conf_lev”)

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)31

5. Finally, in case of an identified misleading information (i.e; causing mis-integrity), the GBLS shall inform the application module by sending element “h_int_alert” (resp. “v_int_alert” and/or “vel_int_alert”) under element “qos_status”.

6. - If optional element “h_conf_lev” (resp. “v_conf_lev”, “vel_conf_lev”) is present in such elements with attribute “conf_class” set to “INFO”, or element “accel_conf_lev” (resp. “head_conf_lev”, and/or “time_conf_lev”), it shall be interpreted as a request to the location system to provide an estimate of the horizontal position error (resp. vertical position error, velocity error, acceleration error, heading error and/or time synchronisation error).

- for horizontal position error estimation, the error estimate shall be reported in the subsequent answer or report(s) through a “CircularArea” shape: error estimate is given by the shape radius (element of the “CircularArea”). As a consequence, attribute “requested_positiondata” of element “geo_info” in the location request (slir or tlrr) shall have values “SHAPE” or “SHAPE_AND_CIVICLOC”.

- for other error estimation, the error estimate shall be given by the element “alt_unc” (resp. “vel_unc”, “accel_unc”, “head_unc” and/or “time_unc”)

7. Element “h_conf_lev” (resp. “v_conf_lev”, “vel_conf_lev”, “accel_conf_lev”, “head_conf_lev”, and/or “time_conf_lev”) is then the targeted level of reliability of the error estimate required to the location system. Level of reliability is defined as:

8. P( > *) <𝐿𝑟where P( > *) is the probability that the actual error exceeds the error estimate, and Lr is the level of reliability.

9. In case of necessity, the location system can provide an error estimate using a different level of reliability. In that case, element “lev_conf” under “hor_qos” (resp. “alt_qos”, “vel_qos”, “accel_qos”, “head_qos” and/or “synch_status”) in the subsequent answer or report(s) shall contain the confidence level achievable by the location system.

- usage of “ll_acc“, “hor_acc”, “alt_acc”, “vel_acc” and “time_acc”: when present in a location request (under element “eqop” or “qop”), these elements:

10. - indicate the level of accuracy expected by the application module. Value of attribute “qos_class” indicate the expected behavior of the location system in case the location-related data does not fulfill the required accuracy. Refer to clause //5.x (qos_class definition).

11. - preclude integrity determination by the location system.

8.1.1.4 Quality of Position elements

<!ELEMENT eqop (resp_req?, resp_timer?, (ll_acc | hor_acc | h_conf_lev)?, (alt_acc | v_conf_lev)?, (vel_acc | vel_conf_lev)?, accel_conf_lev?, head_conf_lev?, (time_acc | time_conf_lev)?,max_loc_age?, auth_lev?)>

<!ELEMENT qop ((ll_acc | hor_acc | h_conf_lev)?, (alt_acc | v_conf_lev)?, (vel_acc | vel_conf_lev)?, accel_conf_lev?, head_conf_lev?, (time_acc | time_conf_lev)?, auth_lev?)>

<!ELEMENT h_conf_lev (#PCDATA)><!ATTLIST h_conf_lev

conf_class ( INFO | ALERT ) ”INFO”><!ELEMENT v_conf_lev (#PCDATA)>

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)32

<!ATTLIST v_conf_levconf_class ( INFO | ALERT ) ”INFO”>

<!ELEMENT vel_acc (#PCDATA)><!ATTLIST vel_acc

qos_class (ASSURED | BEST_EFFORT) #IMPLIED><!ELEMENT vel_conf_lev (#PCDATA)><!ATTLIST vel_conf_lev

conf_class ( INFO | ALERT ) ”INFO”><!ELEMENT accel_conf_lev (#PCDATA)><!ELEMENT head_conf_lev (#PCDATA)><!ELEMENT time_acc (#PCDATA)><!ATTLIST time_acc

qos_class (ASSURED | BEST_EFFORT) #IMPLIED><!ELEMENT time_conf_lev (#PCDATA)>

<!ELEMENT auth_lev (pmd, pfa)><!ELEMENT pmd (#PCDATA)><!ELEMENT pfa (#PCDATA)>

<!ELEMENT qos_status (h_acc_not_met?, v_acc_not_met?, vel_acc_not_met?, time_acc_not_met?, h_int_alert?, v_int_alert?, vel_int_alert?, synch_status?)>

<!ELEMENT h_acc_not_met (#PCDATA)><!ELEMENT v_acc_not_met (#PCDATA)><!ELEMENT vel_acc_not_met (#PCDATA)><!ELEMENT time_acc_not_met (#PCDATA)><!ELEMENT h_int_alert (#PCDATA)><!ELEMENT v_int_alert (#PCDATA)><!ELEMENT vel_int_alert (#PCDATA)><!ELEMENT synch_status (time_unc?, lev_conf?, auth_flag?)><!ELEMENT time_unc (#PCDATA)>

The following rules apply to the elements content and structure:

- usage of “h_int_alert” (resp. “v_int_alert” and/or “vel_int_alert”): refer to clause //7.1.1.4 (location elements).

- usage of “h_acc_not_met” (resp “v_acc_not_met”, “vel_acc_not_met” and/or “time_acc_not_met”: refer to clause //7.1.1.4 (location elements)

8.1.2 accel

Definition:The acceleration of the location target, in m/s². When used for relative location, this parameter expresses the acceleration relative to the Reference Point.DTD type: ElementFormat: Signed decimal value, suggested accuracy 0.1 [tbc]Defined values: Admitted range: [-50; 50] [tbc]Default value: N/AExample in XML presentation:

<accel>2.5</accel>

Note: This element is present if required by element “req_info” in the corresponding location request.

8.1.3 accel_conf_lev

Definition:

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)33

This element is the level of reliability required by the application module regarding the acceleration accuracy estimate provided by the location system. It is expressed as log10(Level of reliability).

DTD type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<accel_conf_lev>-2</accel_conf_lev>

Note: When this element is present in a location request, it implicitely indicates that an estimate of the acceleration accuracy is required (this accuracy estimation being reliable with the required level of reliability). In the subsequent answer/report(s), the position information definition (element “pd”) shall contain element “accel_unc”, or an appropriate error message.

8.1.4 accel_info

Definition:If present, this element indicates that the acceleration information of the location target identified by MSID is requiredDTD type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

<accel_info />

Note: -

8.1.4.1 auth_req

Definition:Indicates if the location system is required to provide the related (parent) location-related data with associated authentication information.Type: AttributeFormat: BooleanDefined values: YES Authenticity of the location-related data shall be determined and

providedNO Authenticity of the location-related data shall not be determined and

providedDefault value: NOExample: < accel_info auth_req ="NO" />

Note: -

8.1.4.2 mot_type

Definition:Determines the type of motion required to be captured in the location-related data by the location system.Type: AttributeFormat: Char stringDefined values: LINEAR Linear indicators are required (linear speed, linear acceleration)

ANGULAR Angular indicators are required (angular speed, angular acceleration)Default value: LINEARExample: < accel_info mot_type ="ANGULAR" />

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)34

Note: -

8.1.5 accel_unc

Definition:Estimate of the acceleration uncertainty or error, in m/s²DTD type: ElementFormat: Positive decimal value, admitted accuracy 0.1 [tbc]Defined values: Admitted range: [0; 10] Default value:Example in XML presentation:

<accel_unc>1</accel_unc>

Note: Usage of this element is defined in clause //7.1.1.4 (location elements)

8.1.6 alt_info

Definition:If present, this element indicates that the altitude information (or vertical position) of the location target identified by MSID is requiredDTD type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

<alt_info />

Note: -

8.1.6.1 auth_req

Refer to clause //7.1.4.1 (auth_req under accel_info)

8.1.7 alt_unc

Definition:Estimate of the altitude uncertainty or error, in mDTD type: ElementFormat: Positive decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [0 ; 100] [tbc]Default value: -Example in XML presentation:

<alt_unc>0.5</alt_unc>

Note: Usage of this element, in particular regarding the integrity concept, is defined in clause //7.1.1.4 (location elements)

NOTE: element with the same name exists in OMA MLP [4]. In the LSEP context, the above definition supersedes the one given in [4].

8.1.8 auth_flag

Definition:

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)35

Defines the auuthentication status of a location-related data (horizontal or vertical position, velocity, acceleration, heading or time)DTD Type: ElementFormat: Char stringDefined values: NO Spoofing attempt is detected

YES Location-related data is authentic UNKNOWN Authentication procedure could not conclude

Default value: -Example in XML presentation:

<auth_flag>YES</auth_flag>

Note: -

8.1.9 geo_infoElement “geo_info” used in LSEP has the same definition as in OMA MLP [4].

In addition, in order to fit GBLS specific context, the attributes “auth_req” and “requested_emidata” are added to element “geo_info” (see clause //7.1.1.4 (location elements)).

8.1.9.1 auth_req


8.1.9.2 req_emidata

Definition:Used when location request concerns EMI sources. Determines the type of EMI information requested to the location system.DTD Type: AttributeFormat: Char stringDefined values: POS_ONLY Only positions of EMI sources are required

POS_AND_BW Both positions and signal bandwidth estimation are requiredDefault value: POS_ONLYExample in XML presentation:

< geo_info req_emidata ="POS_ONLY"></geoinfo>

Note: -

8.1.10 h_acc_not_met

Definition:Indication that the requested horizontal position QoS was not met, if needed.DTD Type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

-

Note: Only applicable if the request was for best effort class, i.e. a horizontal position estimate is returned (rather than an error) although the requested QoS requirement (given in ll_acc or hor_acc) could not be fulfilled.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)36

8.1.11 h_conf_lev

Definition:Depending on the value of attribute “conf_class”, it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the horizontal position error estimate. It is expressed as log10(Level of reliability) or log10(integrity risk).Both integrity risk and level of reliability are defined in clause // 7.1.1.4 (location elements):DTD Type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value:Example in XML presentation:

<h_conf_lev>-2</h_conf_lev>

Note: -

8.1.11.1 conf_class

Definition:This attributes determines whether the parent confidence level provided shall be interpreted as an integrity risk or a level of reliability.Both integrity risk and level of reliability are defined in clause // 7.1.1.4 (location elements):DTD Type: attributeFormat: Char stringDefined values: INFO Parent confidence level shall be intepreted as the level of reliability of

the required error estimate.ALERT Parent confidence level shall be intepreted as the integrity risk which

shall be used by the location system in its integrity determination processDefault value: [INFO]Example in XML presentation:

<h_conf_lev conf_class =”INFO”>-2</h_conf_lev>

Note: Value INFO shall be interpreted as a request to the location system to provide an horizontal position error estimate (resp. vertical position or velocity)Value ALERT shall be interpreted as a request to the location system to carry out integrity determination for horizontal position (resp. vertical position of velocity).

8.1.12 h_int_alert

Definition:Indication that the location system detects location-related data mis-integrity.DTD Type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

-

Note: Only applicable in case “conf_class” under “h_conf_lev” is set to “ALERT”.

8.1.13 head_conf_lev

Definition:

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)37

It represents the preferred level of reliability of the heading error estimate. It is expressed as log10(Level of reliability).Level of reliability is defined in clause // 7.1.1.4 (location elements):DTD Type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value:Example in XML presentation:

<head_conf_lev>-2</head_conf_lev>

Note: -

8.1.14 head_info

Definition:If present, this element indicates that the heading information of the location target identified by MSID is requiredDTD type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

<head_info />

Note: -

8.1.14.1 auth_req


8.1.15 head_unc

Definition:Estimate of the heading uncertainty or error, in degreesDTD type: ElementFormat: Positive decimal value, admitted accuracy 0.1 [tbc]Defined values: Admitted range: [0; 10] [tbc]Default value: -Example in XML presentation:

<head_unc>1</head_unc>


8.1.16 high_freq

Definition:Higher frequency of the bandwidth in which EMI that are subject to location-related data determination by the GBLS are transmitting. It is expressed in Hz.DTD type: ElementFormat: positive decimal value, admitted accuracy 1 [tbc]Defined values: Admitted range: [0; 2x109] [tbc]Default value: -Example in XML presentation:

<high_freq>1,6x109</high_freq>

Note: -

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)38

8.1.17 lev_conf

Definition:Confidence level associated to the location-related data provided by the locationsystem. It is expressed as log10(confidence level).Interpretation of data contained in “lev_conf” is provided in clause // 7.1.1.4 (location elements):DTD type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value:Example in XML presentation:


Note: In case location system executes location-related data integrity determination (i.e. “conf_class” is set to “ALERT”), “lev_conf” shall be equal to “h_conf_lev” (resp. “v_conf_lev” or “vel_conf_level”) given in the associated location request.In case location system provide location-related data error estimation (i.e. “conf_class” is set to “INFO”), “lev_conf” can have any value.

NOTE: element with the same name exists in OMA MLP [4]. In the LSEP context, the above definition supersedes the one given in [4].

8.1.18 low_freq

Definition:Lower frequency of the bandwidth in which EMI that are subject to location-related data determination by the GBLS are transmitting. It is expressed in Hz.DTD type: ElementFormat: positive decimal value, admitted accuracy 1 [tbc]Defined values: Admitted range: [0; 2x109] [tbc]Default value: -Example in XML presentation:

<low_freq>1,55x109</low_freq>

Note: -

8.1.19 pfa

Definition:This element is the probability of false-alarm applicable to the authentication function, , expressed as log10(Pfa)DTD type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<pfa>-5,49</pfa>

Note: -

8.1.20 pmd

Definition:

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)39

This element is the probability of mis-detection applicable to the authentication function, expressed as log10(Pmd)DTD type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<pmd>-5,49</pmd>

Note: -

8.1.21 time_acc

Definition:Accuracy of requested time synchronisation in micro seconds.DTD type: ElementFormat: Positive decimal value, admitted accuracy 0.001 [tbc]Defined values: Admitted range: [0; 10000] [tbc]Default value: -Example in XML presentation:

<time_acc>0.1</time_acc>

Note: -

8.1.22 time_acc_not_met

Definition:Indication that the requested time synchronisation QoS was not met, if needed.DTD Type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

-

Note: Only applicable if the request was for best effort class, i.e. a time synchronisation signal is provided (rather than an error) although the requested QoS requirement (given in time_acc) could not be fulfilled.

8.1.23 time_conf_lev

Definition:This element is the level of reliability required by the application module regarding the time synchronisation accuracy estimate provided by the location system. It is expressed as log10(Level of reliability).Level of reliability is defined in clause // 7.1.1.4 (location elements):DTD type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<time_conf_lev>-2</time_conf_lev>

Note: When this element is present in a location request, it implicitely indicates that an estimate of the time synchronisation accuracy is required (this accuracy estimation being reliable with the required level of reliability). In the subsequent answer/report(s), the position information definition (element “pd”) shall contain element “time_unc”, or an appropriate error message.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)40

8.1.24 time_p

Definition:In a location answer this element indicates the precise time when the positioning was performed.DTD type: ElementFormat: Char string, with time stamp accuracy down to micro-second level [tbc]Defined values: -Default value: -Example: <time_p>20141022142810630040</time_p>

Note:

8.1.25 time_unc

Definition:Estimate of the time synchronisation uncertainty or error, in µsDTD type: ElementFormat: Positive decimal value, admitted accuracy 0.001 [tbc]Defined values: Admitted range: [0; 10000] [tbc]Default value: -Example in XML presentation:

<time_unc>1</time_unc>


8.1.26 acc_not_met

Definition:Indication that the requested vertical position QoS was not met, if needed.DTD Type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

-

Note: Only applicable if the request was for best effort class, i.e. a vertical position estimate is returned (rather than an error) although the requested QoS requirement (given in alt_acc) could not be fulfilled.

8.1.27 v_conf_lev

Definition:Depending on the value of attribute “conf_class”, it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the vertical position error estimate. It is expressed as log10(Level of reliability) or log10(integrity risk).Both integrity risk and level of reliability are defined in clause // 7.1.1.4 (location elements):DTD Type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<v_conf_lev>-2</v_conf_lev>

Note: -

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)41

8.1.27.1 conf_class

Refer to clause //7.1.11.1 (conf_class under h_conf_lev)

8.1.28 v_int_alert


-

Note: Only applicable in case “conf_class” under “v_conf_lev” is set to “ALERT”.

8.1.29 vel_acc

Definition:Accuracy of requested velocity in m/s.DTD type: ElementFormat: Positive decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [0; 5] [tbc]Default value: -Example in XML presentation:

<vel_acc>1</vel_acc>

Note: -

8.1.30 vel_acc_not_met

Definition:Indication that the requested velocity QoS was not met, if needed.DTD Type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

-

Note: Only applicable if the request was for best effort class, i.e. a velocity estimate is provided (rather than an error) although the requested QoS requirement (given in vel_acc) could not be fulfilled.

8.1.31 vel_conf_lev

Definition:Depending on the value of attribute “conf_class”, it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the vertical position error estimate. It is expressed as log10(Level of reliability) or log10(integrity risk).Both integrity risk and level of reliability are defined in clause // 7.1.1.4 (location elements):

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)42

DTD Type: ElementFormat: Negative decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [-10; 0] [tbc]Default value: -Example in XML presentation:

<vel_conf_lev>-2</vel_conf_lev>

Note: -

8.1.31.1 conf_class

Refer to clause //7.1.11.1 (conf_class under h_conf_lev)

8.1.32 vel_info

Definition:If present, this element indicates that the velocity information of the location target identified by MSID is requiredDTD type: ElementFormat: VoidDefined values: -Default value: -Example in XML presentation:

<vel_info />

Note: -

8.1.32.1 auth_req


8.1.32.2 mot_type

Refer to clause //7.1.4.2 (mot_type under accel_info)

8.1.33 vel_int_alert


-

Note: Only applicable in case “conf_class” under “vel_conf_lev” is set to “ALERT”.

8.1.34 vel_unc

Definition:Estimate of the velocity uncertainty or error, in m/s

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)43

DTD type: ElementFormat: Positive decimal value, admitted accuracy 0.01 [tbc]Defined values: Admitted range: [0;5] [tbc] Default value: -Example in XML presentation:



8.1.35 Error codes

8.1.36 Provide Capabilities

8.1.37 Request Location Information

Attributes:

Type of reporting:o Event triggeredo Periodic

ID of mobile target(s) Type of location-related data:

o Positiono Speedo Accelerationo requested QoS:

Integrity (including required integrity risk) Authentication

8.2 LSIP Information Elements8.2.1 OverviewLSIP information elements (IEs) presented below are the information elements composing the LSIP messages describe in section 7.2 above.

8.2.2 Common Information ElementsThis section defines common IEs that are applicable to more than one LSIP positioning method.

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)44

8.2.2.1.1 Common IEs related to location information request

CommonIEsRequestLocationInformation

-- ASN1START

CommonIEsRequestLocationInformation ::= SEQUENCE {locationInformationType LocationInformationType,triggeredReporting TriggeredReportingCriteria OPTIONAL,-- Cond ECIDperiodicalReporting PeriodicalReportingCriteria OPTIONAL,-- Need ONadditionalInformation AdditionalInformation OPTIONAL,-- Need ONqos QoS OPTIONAL,-- Need ONenvironment Environment OPTIONAL,-- Need ONlocationCoordinateTypes LocationCoordinateTypes OPTIONAL,-- Need ONvelocityTypes VelocityTypes OPTIONAL,-- Need ONemiInventoryReq GBLS-EMISourceInventoryReq OPTIONALn-- Need ONlocatioTargetIdReq GBLS-LocationTargetIdReq OPTIONAL...

}

LocationInformationType ::= ENUMERATED {locationEstimateRequired,locationMeasurementsRequired,locationEstimatePreferred, locationMeasurementsPreferred,...

}

TriggeredReportingCriteria ::= SEQUENCE {ChangeArea XXdistanceEvent XXvelocityEvent XX

cellChange BOOLEAN,equidistanceEvent BOOLEAN,reportingDuration ReportingDuration,logicalTriggerCombination ENUMERATED {or, and, ...} OPTIONAL,...

}

ReportingDuration ::= INTEGER (0..255)

PeriodicalReportingCriteria ::= SEQUENCE {reportingAmount ENUMERATED {

ra1, ra2, ra4, ra8, ra16, ra32,ra64, ra-Infinity

} DEFAULT ra-Infinity,reportingInterval ENUMERATED {

noPeriodicalReporting, ri0-25,ri0-5, ri1, ri2, ri4, ri8, ri16, ri32, ri64

}}

AdditionalInformation ::= ENUMERATED {onlyReturnInformationRequested,mayReturnAditionalInformation,...

}

QoS ::= SEQUENCE {horizontalAccuracy HorizontalAccuracy OPTIONAL,-- Need ONverticalCoordinateRequest BOOLEAN,verticalAccuracy VerticalAccuracy OPTIONAL,-- Need ONresponseTime ResponseTime OPTIONAL,-- Need ONvelocityRequest BOOLEAN,velocityAccuracy VelocityAccuracy OPTIONAL,-- Need ONheadingRequest BOOLEAN,headingAccuracy HeadingAccuracy OPTIONAL,-- Need ONaccelerationRequest BOOLEAN,accelerationAccuracy AccelerationAccuracy, OPTIONAL,-- Need ONauthenticationReq GBLS-AuthenticationReq OPTIONEL, -- Need ON...

}

Environment ::= ENUMERATED {badArea,notBadArea,mixedArea,...

}

HorizontalAccuracy ::= SEQUENCE {accuracy INTEGER(0..127), OPTIONAL, --targetAccconfidence INTEGER(0..100),confidenceClass ENUMERATED { INFO,

ALERT, ...}qosClass ENUMERATED { ASSURED,

BEST_EFFORT, ...} OPTIONAL, --targetAcc

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)45

...}

VerticalAccuracy ::= SEQUENCE {accuracy INTEGER(0..127), OPTIONAL, --targetAccconfidence INTEGER(0..100), OPTIONAL, --accEstReqconfidenceClass ENUMERATED { INFO,

ALERT, ...} OPTIONAL, --accEstReq

Qos class ENUMERATED { ASSURED,BEST_EFFORT, ...} OPTIONAL, --targetAcc ...

}

ResponseTime ::= SEQUENCE {time INTEGER (1..128),...

}

VelocityAccuracy ::= SEQUENCE {accuracy INTEGER(0..127), OPTIONAL, --targetAccconfidence INTEGER(0..100), OPTIONAL, --accEstReqconfidenceClass ENUMERATED { INFO,

ALERT, ...} OPTIONAL, --accEstReqQos class ENUMERATED { ASSURED,

BEST_EFFORT, ...} OPTIONAL, --targetAcc...

}

HeadingAccuracy ::= SEQUENCE {accuracy INTEGER(0..127), OPTIONAL, --targetAccconfidence INTEGER(0..100), OPTIONAL, --accEstReqconfidenceClass ENUMERATED { INFO,

ALERT, ...} OPTIONAL, --accEstReqqos class ENUMERATED { ASSURED,

BEST_EFFORT, ...} OPTIONAL, --targetAcc...

}

AccelerationAccuracy ::= SEQUENCE {confidence INTEGER(0..100),...

}

GBLS-InventoryReq ::= SEQUENCE {frequenyBand GBLS-FrequencyBand,targetArea CHOICE {

circle Ellipsoid-PointWithUncertaintyCircle,ellipse EllipsoidPointWithUncertaintyEllipse,Polygon Polygon,...}

...}

GBLS-LocationTargetIdReq ::= SEQUENCE {[tbd]...

}

-- ASN1STOP

Conditional presence ExplanationECID The field is optionally present, need ON, if ECID is requested. Otherwise it is not present.targetAcc The field shall be absent in case field “confidence” and “confidenceClass” are specified in

the same “QoS” IE.accEstReq The field shall be absent in case field “accuracy” and “qos_class” are specified in the

same “QoS” IE..

CommonIEsRequestLocationInformation field descriptionslocationInformationTypeAs per 3GPP LPP [6]triggeredReporting[tbd]periodicalReportingAs per 3GPP LPP [6]additionalInformationAs per 3GPP LPP [6]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)46

CommonIEsRequestLocationInformation field descriptionsqos[tbd]

horizontalAccuracy : see table belowverticalAccuracy: see table belowvelocityAccuracy: see table belowheadingAccuracy: see table belowverticalCoordinateRequest: [tbd]responseTime: [tbd]velocityRequest: [tbd]headingRequest: [tbd]accelerationRequest: [tbd]accelerationAccuracy: [tbd]authenticationReq: [tbd]

The table below indicates how IE related to “xxAcuracy” are structured.

accuracy field

confidence field

confidenceClass field

qosClass field

Explanation

Case 1 present absent absent ASSURED Targeted measure accuracy is specified, and only measure complying with targeted accuracy shall be provided.

Case 2 present absent absent BEST EFFORT

Targeted measure accuracy is specified, and measure not complying with targeted accuracy shall be flagged in the subsequent answer (using IE “GBLS-QosIndicators”).

Case 3 absent present INFO absent Estimation of the measure accuracy is required. Accuracy estimate should comply with the required confidence level. In CL cannot be met, it shall be indicated in the subsequent answer (using IE “GBLS-ConfidenceLevels”).

Case 4 absent present ALERT absent Estimation of the measure accuracy is required. Accuracy estimate shall comply with the required confidence level. In case estimated accuracy cannot compy with the required CL it shall be reported in the subsequent answer to the “server” entity (using IE “GBLS-IntegrityAlerts”).

All other combinations shall not be used.

environmentAs per 3GPP LPP [6]locationCoordinateTypesAs per 3GPP LPP [6]velocityTypesAs per 3GPP LPP [6]emiInventoryReq[tbd]locationTargetIdReq[tbd][Editorial note : while locationTargetIdReq, in “Common location information request”, can cover a group of targets, the locationTargetId in “Common location information provide”points on a single target id.We indeed assume that the “common location information provide” message contains information for a single target, while the “request” message can contain information request related to several targets]

OMA-LPPe-CommonIEsRequestLocationInformation

-- ASN1START

OMA-LPPe-CommonIEsRequestLocationInformation ::= SEQUENCE {iP-Address-Request OMA-LPPe-IP-Address-Request OPTIONAL,locationInformationContainerRequest OMA-LPPe-LocationInformationContainerRequest OPTIONAL,requestPeriodicLocInfoWithUpdate OMA-LPPe-RequestPeriodicLocInfoWithUpdate OPTIONAL,

--Cond RequestPeriodicLocInfoWithUpdaterelativeLocationChange-Request OMA-LPPe-RelativeLocationChange-Request OPTIONAL,localPositionRequest OMA-LPPe-LocalPositionRequest OPTIONAL,

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)47

scheduledLocation-Request OMA-LPPe-ScheduledLocation-Request OPTIONAL,accessTypeRequest OMA-LPPe-AccessTypeRequest OPTIONAL,segmentedLIpreference ENUMERATED {useBasic, useResume, ...} OPTIONAL,segmentedLIResume OMA-LPPe-SegmentedLIResume OPTIONAL,

--Cond segmentedTransferResumelocationSourceReq OMA-LPPe-LocationSource OPTIONAL --Cond LocationSource...

}

OMA-LPPe-IP-Address-Request ::= SEQUENCE {...

}

OMA-LPPe-RequestPeriodicLocInfoWithUpdate ::= SEQUENCE {session-ID OCTET STRING (SIZE(4)),typeOfLocInfoRequest OMA-LPPe-TypeOfLocInfoRequest,...

}

OMA-LPPe-TypeOfLocInfoRequest ::= ENUMERATED {initialRequest,updateAndContinueIfUpdateFails,updateAndAbortIfUpdateFails,...

}

OMA-LPPe-RelativeLocationChange-Request ::= SEQUENCE {numberOfChanges INTEGER (1..5) OPTIONAL,...

}

OMA-LPPe-LocalPositionRequest ::= SEQUENCE {typeOfRequest ENUMERATED { localOptional, localMandatory, localOnly, ... },referencePointReq SEQUENCE (SIZE (1..8)) OF

OMA-LPPe-ReferencePointUniqueID OPTIONAL,...

}

OMA-LPPe-ScheduledLocation-Request ::= SEQUENCE {gnssTime GNSS-SystemTime OPTIONAL, --Cond AtLeastOnenetworkTime NetworkTime OPTIONAL, --Cond AtLeastOnerelativeTime INTEGER (1..1024) OPTIONAL, --Cond AtLeastOnewindowSize INTEGER (1..1024) OPTIONAL,...

}

OMA-LPPe-AccessTypeRequest ::= SEQUENCE {...

}

OMA-LPPe-SegmentedLIResume ::= SEQUENCE {segmentedLI-session-ID INTEGER (1..256),next-segment-number INTEGER (1..4096)}

OMA-LPPe-LocationSource ::= SEQUENCE {agnss NULL OPTIONAL,otdoa NULL OPTIONAL,eotd NULL OPTIONAL,otdoaUTRA NULL OPTIONAL,ecidLTE NULL OPTIONAL,ecidGSM NULL OPTIONAL,ecidUTRA NULL OPTIONAL,wlanAP NULL OPTIONAL,srn NULL OPTIONAL,sensors NULL OPTIONAL,inertialSensor NULL OPTIONAL,magnetometer NULL OPTIONAL,odometer NULL OPTIONAL,bfa NULL OPTIONAL,...

}

-- ASN1STOP

Conditional presence ExplanationRequestPeriodicLocInfoWithUpdate

As per OMA LPPe [5].

AtLeastOne As per OMA LPPe [5].segmentedTransferResume


ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)48

OMA-LPPe-CommonIEsRequestLocationInformation field descriptionsiP-Address-RequestAs per OMA LPPe [5].locationInformationContainerRequestAs per OMA LPPe [5].requestPeriodicLocInfoWithUpdateAs per OMA LPPe [5].

relativeLocationChange-RequestAs per OMA LPPe [5].localPositionRequestAs per OMA LPPe [5].scheduledLocation-RequestAs per OMA LPPe [5].accessTypeRequestAs per OMA LPPe [5].segmentedLIpreferenceAs per OMA LPPe [5].segmentedLIResumeAs per OMA LPPe [5].locationSourceReq[tbd].

8.2.2.1.2 Common IEs related to location information provision

CommonIEsProvideLocationInformation

-- ASN1START

CommonIEsProvideLocationInformation ::= SEQUENCE {locationEstimate LocationCoordinates OPTIONAL,velocityEstimate Velocity OPTIONAL,accelerationEstimate GBLS-Acceleration OPTIONAL,headingEstimate GBLS-Heading OPTIONAL,reportedQoS GBLS-ReportedQoS OPTIONAL,locationError LocationError OPTIONAL,alerts GBLS-IntegrityAlerts OPTIONAlocatioTargetId GBLS-LocationTargetId OPTIONAL...

}

LocationCoordinates ::= CHOICE {ellipsoidPoint Ellipsoid-Point,ellipsoidPointWithUncertaintyCircle Ellipsoid-PointWithUncertaintyCircle,ellipsoidPointWithUncertaintyEllipse EllipsoidPointWithUncertaintyEllipse,polygon Polygon,ellipsoidPointWithAltitude EllipsoidPointWithAltitude,ellipsoidPointWithAltitudeAndUncertaintyEllipsoid EllipsoidPointWithAltitudeAndUncertaintyEllipsoid,ellipsoidArc EllipsoidArc,...

}

Velocity ::= CHOICE {horizontalVelocity HorizontalVelocity,horizontalWithVerticalVelocity HorizontalWithVerticalVelocity,horizontalVelocityWithUncertainty HorizontalVelocityWithUncertainty,horizontalWithVerticalVelocityAndUncertainty HorizontalWithVerticalVelocityAndUncertainty,...

}

GBLS-Acceleration ::= CHOICE {acceleration INTEGER(0..[tbd])...

}

GBLS-Heading ::= CHOICE {heading INTEGER(0..[tbd])...

}

GBLS-ReportedQoS::= SEQUENCE {confidenceLevels GBLS-ConfidenceLevels OPTIONAL, -- clReporting

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)49

uncertaintyMeasures GBLS-UncertaintyMeasures OPTIONAL, -- uncerMeasuresReqqosIndicators GBLS-QosIndicators OPTIONAL, -- targetAccuracyReqauthenticationIndicators GBLS-AuthenticationIndicators OPTIONAL, -- authReq

}

LocationError ::= SEQUENCE {locationfailurecause LocationFailureCause,...

}

LocationFailureCause ::= ENUMERATED {undefined,requestedMethodNotSupported,positionMethodFailure, periodicLocationMeasurementsNotAvailable,...

}

GBLS-IntegrityAlerts ::= SEQUENCE {hplAlert HplALert OPTIONAL,vplAlert VplAlert OPTIONAL,velocityAlert VelocityALert OPTIONAL,headingAlert HeadingAlert OPTIONAL,...

}

HplALert ::= CHOICE {DoNotUse BOOLEAN,NotMonitored BOOLEAN,...

}

VplALert ::= CHOICE {DoNotUse BOOLEAN,NotMonitored BOOLEAN,...

}

VelocityALert ::= CHOICE {DoNotUse BOOLEAN,NotMonitored BOOLEAN,...

}

HeadingALert ::= CHOICE {DoNotUse BOOLEAN,NotMonitored BOOLEAN,...

}

GBLS-LocationTargetId ::= SEQUENCE {[tbd]...

}

-- ASN1STOP

Conditional presence ExplanationclReporting This field is mandatory present if the associated location information request requires for

one or several measure accuracy estimates (among horizontal position, vertical position, velocity, acceleration and heading), with “confidence class” set to “INFO”,It can be equal to the “confidence” set in the location information request, or lower in case the measure accuracy estimate computed cannot meet the required confidence level.

uncerMeasuresReq This field is mandatory present if the associated location information request requires for one or several measure accuracy estimates among acceleration and heading, with “confidence class” set to “INFO” or “ALERT”,

targetAccuracyReq This field is mandatory present if the associated location information request requires for a targeted accuracy for one or several measures (among horizontal position, vertical position, velocity and heading), with “qosclass” set to “BEST EFFORT”,

authReq This field is mandatory present if the associated location information request requires for one or several authenticated measures (among horizontal position, vertical position, velocity, acceleration and heading).

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)50

CommonIEsProvideLocationInformation field descriptionslocationEstimateAs per 3GPP LPP [6]velocityEstimateAs per 3GPP LPP [6]accelerationEstimate[tbd]headingEstimate[tbd]reportedQoS[tbd]

confidenceLevelsuncertaintyMeasuresqosIndicatorsauthenticationIndicators

locationErrorAs per 3GPP LPP [6]alerts[tbd]locationTargetId[tbd][Editorial note : while locationTargetIdReq, in “Common location information request”, can cover a group of targets, the locationTargetId in “Common location information provide”points on a single target id.We indeed assume that the “common location information provide” message contains information for a single target, while the “request” message can contain information request related to several targets]

OMA-LPPe-CommonIEsProvideLocationInformation

-- ASN1START

OMA-LPPe-CommonIEsProvideLocationInformation ::= SEQUENCE {highAccuracy3Dposition OMA-LPPe-HighAccuracy3Dposition OPTIONAL,

--Cond HighAccuracylocalPosition OMA-LPPe-LocalPosition OPTIONAL,highAccuracy3Dvelocity OMA-LPPe-HighAccuracy3Dvelocity OPTIONAL,

--Cond HighAccuracyiP-Address-List OMA-LPPe-IP-Address-List OPTIONAL,locationInformationContainer OMA-LPPe-LocationInformationContainer OPTIONAL,providePeriodicLocInfoWithUpdate OMA-LPPe-ProvidePeriodicLocInfowithUpdateOPTIONAL,

--Cond ProvidePeriodicLocInfoWithUpdaterelativeLocationChangeList OMA-LPPe-RelativeLocationChangeList OPTIONAL,scheduledLocation OMA-LPPe-ScheduledLocation OPTIONAL,

--Cond ScheduledLocationRequestedaccessTypes OMA-LPPe-AccessTypes OPTIONAL,segmentedLITransfer OMA-LPPe-SegmentedLITransfer OPTIONAL,

--Cond segmentedTransferWithResumelocationInformationTimeStamp OMA-LPPe-TimeStamp OPTIONAL,...,locationSource OMA-LPPe-LocationSource OPTIONAL --Cond LocationSource

}

OMA-LPPe-LocalPosition ::= SEQUENCE {referencePoint OMA-LPPe-ReferencePointUniqueID,subjectLocation OMA-LPPe-RelativeLocation OPTIONAL,...

}

OMA-LPPe-IP-Address-List ::= SEQUENCE (SIZE (1..maxIPAddress)) OF OMA-LPPe-IP-Address

maxIPAddress INTEGER ::= 5

OMA-LPPe-IP-Address ::= SEQUENCE {local-IP-Address CHOICE {

iPv4 BIT STRING (SIZE(32)),iPv6 BIT STRING (SIZE(128)),...},

bearer OMA-LPPe-Bearer,nat BOOLEAN OPTIONAL,...

}

OMA-LPPe-Bearer ::= ENUMERATED {unknown,gsm,

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)51

utran,lte,wlan,wimax,dsl,pktcable,other,...

}

OMA-LPPe-ProvidePeriodicLocInfowithUpdate ::= SEQUENCE {session-ID OCTET STRING (SIZE(4)),typeOfLocInfoProvide OMA-LPPe-TypeOfLocInfoProvide,...

}

OMA-LPPe-TypeOfLocInfoProvide ::= ENUMERATED {responseToInitialRequest,providePeriodicLocInfo,responseToServerUpdateRequest,targetUpdate,...

}

OMA-LPPe-RelativeLocationChangeList ::= SEQUENCE (SIZE (1..maxRelativeLocation)) OF OMA-LPPe-RelativeLocationChange

OMA-LPPe-RelativeLocationChange ::= SEQUENCE {relativeTime INTEGER (0..65535) OPTIONAL,transactionID INTEGER (0..255) OPTIONAL,relativeLocation OMA-LPPe-RelativeLocation,...

}

maxRelativeLocation INTEGER ::= 5

OMA-LPPe-ScheduledLocation ::= SEQUENCE {disposition ENUMERATED {withinWindow,

outsideWindowOrNoWindow,notSupportedDueToNoCapability,notSupportedDueToNoTimeReference,notSupportedDueToConflictWithAnotherRequest,notSupportedForOtherReasons,... },

actualWindow SEQUENCE {start INTEGER (-512..511),duration INTEGER (0..2047)

} OPTIONAL,...

}

OMA-LPPe-AccessTypes ::= SEQUENCE {accessTypeUnknown NULL OPTIONAL,fixedAccessTypes OMA-LPPe-FixedAccessTypes OPTIONAL,wirelessAccessTypes OMA-LPPe-WirelessAccessTypes OPTIONAL,...

}

OMA-LPPe-SegmentedLITransfer ::= SEQUENCE {segmentedLI-session-ID INTEGER (1..256),segment-number INTEGER (1..4096),...

}

OMA-LPPe-TimeStamp ::= CHOICE {gnssTime GNSS-SystemTime,networkTime NetworkTime,relativeTime INTEGER (0..1024),...

}

OMA-LPPe-LocationSource ::= SEQUENCE {agnss NULL OPTIONAL,otdoa NULL OPTIONAL,eotd NULL OPTIONAL,otdoaUTRA NULL OPTIONAL,ecidLTE NULL OPTIONAL,ecidGSM NULL OPTIONAL,ecidUTRA NULL OPTIONAL,wlanAP NULL OPTIONAL,srn NULL OPTIONAL,sensors NULL OPTIONAL,inertialSensor NULL OPTIONAL,magnetometer NULL OPTIONAL,odometer NULL OPTIONAL,bfa NULL OPTIONAL,...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)52

-- ASN1STOP

Conditional presence Explanation

HighAccuracy As per OMA LPPe [5].ProvidePeriodicLocInfoWithUpdate


ScheduledLocationRequested


segmentedTransferWithResume


LocationSource As per OMA LPPe [5].

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)53

OMA-LPPe-CommonIEsProvideLocationInformation field descriptionshighaccuracy3DpositionAs per OMA LPPe [5].localPositionAs per OMA LPPe [5].highaccuracy3DvelocityAs per OMA LPPe [5].iP-Address-ListAs per OMA LPPe [5].locationInformationContainerAs per OMA LPPe [5].providePeriodicLocInfoWithUpdateAs per OMA LPPe [5].relativeLocationChangeListAs per OMA LPPe [5].scheduledLocationAs per OMA LPPe [5].accessTypesAs per OMA LPPe [5].segmentedLITransferAs per OMA LPPe [5].referencePointAs per OMA LPPe [5].subjectLocationAs per OMA LPPe [5].local-IP-AddressAs per OMA LPPe [5].bearerAs per OMA LPPe [5].natAs per OMA LPPe [5].session-IDAs per OMA LPPe [5].

typeOfLocInfoProvideAs per OMA LPPe [5].

relativeTimeAs per OMA LPPe [5].transactionIDAs per OMA LPPe [5].relativeLocationAs per OMA LPPe [5].locationInformationTimestampAs per OMA LPPe [5].

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)54

OMA-LPPe-CommonIEsProvideLocationInformation field descriptionslocationSource[tbd]OMA says : This parameter indicates the positioning technologies involved in calculating a UE-based position estimate sent by the target to the server. The parameter is encoded as a bitmap and lists the following positioning technologies:

agnss: Assisted-GNSSotdoa: OTDOA on LTEeotd: E-OTD (GSM)otdoaUTRA: OTDOA on UTRAecidLTE: E-CID on LTEecidGSM: E-CID on GSMecidUTRA: E-CID on UTRAwlanAP: WLAN APsrn: SRNsensors: Sensors

If more than one positioning technology is indicated, the target calculated a final position result reported to the server by appropriately combining individual position results (hybrid positioning).

8.2.2.1.3 Common IEs related to assistance data provision

CommonIEsProvideAssistanceData

As per 3GPP LPP [6]

OMA-LPPe-CommonIEsProvideAssistanceData

As per OMA LPPe [5]

8.2.2.1.4 Common IEs related to assistance data request

CommonIEsRequestAssistanceData

As per 3GPP LPP [6]

OMA-LPPe-CommonIEsRequestAssistanceData

As per OMA LPPe [5]

8.2.2.1.5 Common IEs related to abort handling

CommonIEsAbort

As per 3GPP LPP [6]

OMA-LPPe-CommonIEsAbort

As per OMA LPPe [5]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)55

8.2.2.1.6 Common IEs related to error handling

CommonIEsError

As per 3GPP LPP [6]

OMA-LPPe-CommonIEsError

As per OMA LPPe [5]

8.2.2.2 Common Low Level IEs

LocationCoordinateTypes

As per 3GPP LPP [6]

VelocityTypes

As per 3GPP LPP [6]

Sensor Common CRM

[Reference OMA-LPPe-Orientation]

NoseThe nose Euler angle alpha is in the range [0 , 360] degrees

WingThe wing Euler angle beta is in the range [0, 180] degreesDownThe down Euler angle gamma is in the range [0, 360] degrees

GBLS-DirectionOfArrival

GBLS-DirectionOfArrival::= SEQUENCE {azimuth INTEGER (0..511),elevation INTEGER (0..127),}azimuthEstError INTEGER (0..[tbd]),elevationEstError INTEGER (0..[tbd]),

}

GBLS-DirectionOfArrival field descriptionsazimuth[tbd]NB : as defined in 3GPP LPP (in GNSS-AcquisitionAssistElement)elevation[tbd]NB : as defined in 3GPP LPP (in GNSS-AcquisitionAssistElement)azimuthEstError[tbd]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)56

GBLS-DirectionOfArrival field descriptionselevationEstError[tbd]

GBLS-ConfidenceLevels

-- ASN1START

GBLS-ConfidenceLevels::= SEQUENCE {horizontalCL INTEGER(0..tbd) OPTIONAL, -- CondverticalCL INTEGER(0..tbd) OPTIONAL, -- CondvelocityCL INTEGER(0..tbd) OPTIONAL, -- CondaccelerationCL INTEGER(0..tbd) OPTIONAL, -- CondheadingCL INTEGER(0..tbd) OPTIONAL, -- Cond

}

-- ASN1STOP

Conditional presence Explanationxxx [tbd]… …

GBLS-ConfidenceLevels field descriptionshorizontalCL[tbd]verticalCL[tbd]velocityCL[tbd]accelerationCL[tbd]headingCL[tbd]

GBLS-UncertaintyMeasures

-- ASN1START

GBLS-UncertaintyMeasures::= SEQUENCE {accelerationUncertainty INTEGER(0..tbd) OPTIONAL, -- CondheadingUncertainty INTEGER(0..tbd) OPTIONAL, -- Cond

}

-- ASN1STOP


GBLS-UncertaintyMeasures field descriptionsaccelerationUncertainty[tbd]headingUncertainty[tbd]

GBLS-QosIndicators

-- ASN1START

GBLS-QosIndicators::= SEQUENCE {horizontalAccuracyNotMet BOOLEANverticalAccuracyNotMet BOOLEANvelocityAccuracyNotMet BOOLEANheadingAccuracyNotMet BOOLEAN

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)57

-- ASN1STOP

GBLS-QosIndicators field descriptionshorizontalAccuracyNotMet[tbd]verticalAccuracyNotMet[tbd]velocityAccuracyNotMet [tbd]headingAccuracyNotMet [tbd]

GBLS-AuthenticationIndicators

-- ASN1START

GBLS-AuthenticationIndicators::= SEQUENCE {horPosAuthentication BOOLEAN OPTIONAL, -- CondverticalPositionsAuthentication BOOLEAN OPTIONAL, -- CondvelocityAuthentication BOOLEAN OPTIONAL, -- CondaccelerationAuthentication BOOLEAN OPTIONAL, -- CondheadingAuthentication BOOLEAN OPTIONAL, -- Cond

}

-- ASN1STOP


GBLS-AuthenticationIndicators field descriptionshorPosAuthentication[tbd]verticalPositionAuthentication [tbd]velocityAuthentication [tbd]accelerationAuthentication [tbd]headingAuthentication [tbd]

GBLS-AuthenticationReq

-- ASN1START

GBLS-AuthenticationReq::= SEQUENCE {authParameters AuthenticationParameters,horPosAuthenticationReq BOOLEANverticalPositionAuthenticationReq BOOLEANvelocityAuthenticationReq BOOLEANaccelerationAuthenticationReq BOOLEANheadingAuthenticationReq BOOLEAN

}

AuthenticationParameters::= SEQUENCE {pmd INTEGER(0..tbd),pfa INTEGER(0..tbd),...

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)58

GBLS-AuthenticationReq field descriptionsauthParameters[tbd]pmdpfahorPosAuthenticationReq [tbd]verticalPositionAuthenticationReq [tbd]velocityAuthenticationReq [tbd]accelerationAuthenticationReq [tbd]headingAuthenticationReq [tbd]

GBLS-DLLCommandAssistGenericProvide

[tbd]

GBLS-AGNSS-DLLCommandAssistCommonProvide

[tbd]

GBLS-dllCommandReqControlParameter

[tbd]

GBLS-dllCommandAssistGenericReq

[tbd]

GBLS-FrequencyBand

[tbd]

8.2.3 Positioning Method Information Elements

8.2.3.1 AGNSS Positioning

8.2.3.1.1 AGNSS Assistance Data

A-GNSS-ProvideAssistanceData

As per 3GPP LPP [6]

OMA-LPPe-AGNSS-ProvideAssistanceData

-- ASN1START

OMA-LPPe-AGNSS-ProvideAssistanceData ::= SEQUENCE {commonAssistData OMA-LPPe-AGNSS-CommonAssistData OPTIONAL,genericAssistData OMA-LPPe-AGNSS-GenericAssistData OPTIONAL,error OMA-LPPe-AGNSS-Error OPTIONAL,...

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)59

OMA-LPPe-AGNSS-CommonAssistData

-- ASN1START

OMA-LPPe-AGNSS-CommonAssistData::= SEQUENCE {ionosphericModel OMA-LPPe-AGNSS-IonosphericModel OPTIONAL,troposphereModel OMA-LPPe-AGNSS-TroposphereModel OPTIONAL,altitudeAssistance OMA-LPPe-AGNSS-AltitudeAssistanceList OPTIONAL,solarRadiation OMA-LPPe-AGNSS-SolarRadiation OPTIONAL,ccpAssistCommonProvide OMA-LPPe-AGNSS-CCPassistCommonProvide OPTIONAL,dllCommandAssistCommonProvide GBLS-AGNSS-DLLCommandAssistCommonProvide OPTIONAL,pllCommandAssistCommonProvide GBLS-AGNSS-PLLCommandAssistCommonProvide OPTIONAL,...

}

-- ASN1STOP

OMA-LPPe-AGNSS-CommonAssistanceDataReq field descriptionsionosphericModelAs per OMA LPPe [5]troposphereModelAs per OMA LPPe [5]altitudeAssistanceAs per OMA LPPe [5]solarRadiationAs per OMA LPPe [5]ccpAssistCommonProvideAs per OMA LPPe [5]dllCommandAssistCommonProvide[tbd]pllCommandAssistCommonProvide[tbd]

OMA-LPPe-AGNSS-GenericAssistData

-- ASN1START

OMA-LPPe-AGNSS-GenericAssistData ::= SEQUENCE (SIZE (1..16)) OF OMA-LPPe-AGNSS-GenericAssistDataElement

OMA-LPPe-AGNSS-GenericAssistDataElement ::= SEQUENCE {gnss-ID GNSS-ID,wideAreaIonoSurfacePerSVlist OMA-LPPe-AGNSS-WideAreaIonoSurfacePerSVlist OPTIONAL,mechanicsForAllSVs OMA-LPPe-AGNSS-MechanicsForAllSVs OPTIONAL, dcbsForAllSVs OMA-LPPe-AGNSS-DCBsForAllSVs OPTIONAL, navModelDegradationModel OMA-LPPe-AGNSS-NavModelDegradationModelList OPTIONAL,ccpAssistProvide OMA-LPPe-AGNSS-CCPassistGenericProvide OPTIONAL, --Cond CCPnavModelList OMA-LPPe-AGNSS-NavModelList OPTIONAL,dllCommandAssistProvide GBLS-AGNSS-DLLCommandAssistGenericProvide OPTIONAL, --Cond DLLpllCommandAssistProvide GBLS-AGNSS-PLLCommandAssistGenericProvide OPTIONAL, --Cond PLL...

}

-- ASN1STOP

Conditional presence ExplanationCCP The field is mandatory present, when providing continuous carrier phase assistance and

reference time is included in the IE AGNSS-CCPassistCommonProvide. Otherwise the field shall not be present.

DLL [tbd] [same as for CCP]PLL [tbd] [same as for CCP]

OMA-LPPe-AGNSS-GenericAssistData field descriptionsgnss-IDAs per OMA LPPe [5]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)60

OMA-LPPe-AGNSS-GenericAssistData field descriptionswideAreaIonoSurfacePerSVlistAs per OMA LPPe [5]mechanicsForAllSVsAs per OMA LPPe [5]dcbsForAllSVsAs per OMA LPPe [5]navModelDegradationModelAs per OMA LPPe [5]ccpAssistProvideAs per OMA LPPe [5]navModelListAs per OMA LPPe [5]dllCommandAssistProvide[tbd] pllCommandAssistProvide[tbd]

8.2.3.1.2 AGNSS Assistance Data Elements

OMA-LPPe-AGNSS-IonosphericModel

As per OMA LPPe [5]

OMA-LPPe-AGNSS-TroposphereModel

As per OMA LPPe [5]

OMA-LPPe-AGNSS-AltitudeAssistanceList

As per OMA LPPe [5]

OMA-LPPe-AGNSS-SolarRadiation

As per OMA LPPe [5]

OMA-LPPe-AGNSS-CCPassistCommonProvide

As per OMA LPPe [5]


-- ASN1START

GBLS-AGNSS-DLLCommandAssistCommonProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-AGNSS-PLLCommandAssistCommonProvide

-- ASN1START

GBLS-AGNSS-PLLCommandAssistCommonProvide::= SEQUENCE {xx xx xx...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)61

-- ASN1STOP

OMA-LPPe-AGNSS-WideAreaIonoSurfacePerSVlist

As per OMA LPPe [5]

OMA-LPPe-AGNSS-MechanicsForAllSVs

As per OMA LPPe [5]

OMA-LPPe-AGNSS-DCBsForAllSVs

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavModelDegradationModelList

As per OMA LPPe [5]

OMA-LPPe-AGNSS-CCPassistGenericProvide

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavModelList

As per OMA LPPe [5]

GBLS-AGNSS-DLLCommandAssistGenericProvide

-- ASN1START

GBLS-DLLCommandAssistGenericProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-AGNSS-PLLCommandAssistGenericProvide

-- ASN1START

GBLS-PLLCommandAssistGenericProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

8.2.3.1.3 AGNSS Assistance Data Request

A-GNSS-RequestAssistanceData

As per 3GPP LPP [6]

OMA-LPPe-AGNSS-RequestAssistanceData

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)62

-- ASN1START

OMA-LPPe-AGNSS-RequestAssistanceData::= SEQUENCE {commonAssistDataReq OMA-LPPe-AGNSS-CommonAssistanceDataReq OPTIONAL,genericAssistDataReq OMA-LPPe-AGNSS-GenericAssistanceDataReq OPTIONAL,...

}

-- ASN1STOP

OMA-LPPe-AGNSS-CommonAssistanceDataReq

-- ASN1START

OMA-LPPe-AGNSS-CommonAssistanceDataReq ::= SEQUENCE {ionosphericModelReq OMA-LPPe-AGNSS-IonosphericModelReq OPTIONAL,troposphereModelReq OMA-LPPe-AGNSS-TroposphereModelReq OPTIONAL,altitudeAssistanceReq OMA-LPPe-AGNSS-AltitudeAssistanceReq OPTIONAL,solarRadiationRequest OMA-LPPe-AGNSS-SolarRadiationReq OPTIONAL,ccpRequestControlParameters OMA-LPPe-AGNSS-CCPrequestControlParameters OPTIONAL,dllCommandReqControlParameter GBLS-AGNSS-dllCommandReqControlParameter OPTIONAL,pllCommandReqControlParameter GBLS-AGNSS-pllCommandReqControlParameter OPTIONAL,...

}

-- ASN1STOP

OMA-LPPe-AGNSS-CommonAssistanceDataReq field descriptionsionosphereModelReqAs per OMA LPPe [5]troposphereModelReqAs per OMA LPPe [5]altitudeAssistanceReqAs per OMA LPPe [5]solarRadiationReqAs per OMA LPPe [5]ccpRequestControlParametersAs per OMA LPPe [5]dllCommandReqControlParameter[tbd]pllCommandReqControlParameter[tbd]

OMA-LPPe-AGNSS-GenericAssistanceDataReq

-- ASN1START

OMA-LPPe-AGNSS-GenericAssistanceDataReq ::= SEQUENCE (SIZE (1..16)) OF OMA-LPPe-AGNSS-GenericAssistDataReqElement

OMA-LPPe-AGNSS-GenericAssistDataReqElement ::= SEQUENCE {gnss-ID GNSS-ID,waIonoSurfaceReq OMA-LPPe-AGNSS-WaIonoSurfaceRequest OPTIONAL, --Cond WAionomechanicsReq OMA-LPPe-AGNSS-MechanicsReq OPTIONAL,dcbReq OMA-LPPe-AGNSS-DCBreq OPTIONAL,navModelDegradationModelReq OMA-LPPe-AGNSS-NavModelDegradationModelReq OPTIONAL,ccpAssistGenericReq OMA-LPPe-AGNSS-CCPassistGenericReq OPTIONAL, --Cond CCPreqnavigationModelReq OMA-LPPe-AGNSS-NavigationModelReq OPTIONAL,dllCommandAssistGenericReq GBLS-AGNSS-dllCommandAssistGenericReq OPTIONAL, --Cond dllreqpllCommandAssistGenericReq GBLS-AGNSS-pllCommandAssistGenericReq OPTIONAL, --Cond pllreq...

}

-- ASN1STOP

Conditional presence ExplanationWAiono As per OMA LPPe [5]CCPreq As per OMA LPPe [5]dllreq [tbd]pllreq [tbd]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)63

OMA-LPPe-AGNSS-GenericAssistanceDataReq field descriptionswaIonoSurfaceReqAs per OMA LPPe [5]mechanicsReqAs per OMA LPPe [5]dcbReqAs per OMA LPPe [5]navModelDegradationModelReqAs per OMA LPPe [5]ccpAssistGenericReqAs per OMA LPPe [5]navigationModelReqAs per OMA LPPe [5]dllCommandAssistGenericReq[tbd]pllCommandAssistGenericReq[tbd]

8.2.3.1.4 AGNSS Assistance Data Elements

OMA-LPPe-AGNSS-IonosphericModel

As per OMA LPPe [5]

OMA-LPPe-AGNSS-TroposphereModel

As per OMA LPPe [5]

OMA-LPPe-AGNSS-AltitudeAssistanceList

As per OMA LPPe [5]

OMA-LPPe-AGNSS-SolarRadiation

As per OMA LPPe [5]

OMA-LPPe-AGNSS-CCPassistCommonProvide

As per OMA LPPe [5]


-- ASN1START

GBLS-AGNSS-DLLCommandAssistCommonProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-AGNSS-PLLCommandAssistCommonProvide

-- ASN1START

GBLS-AGNSS-PLLCommandAssistCommonProvide::= SEQUENCE {

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)64

xx xx xx...

}

-- ASN1STOP

OMA-LPPe-AGNSS-WideAreaIonoSurfacePerSVlist

As per OMA LPPe [5]

OMA-LPPe-AGNSS-MechanicsForAllSVs

As per OMA LPPe [5]

OMA-LPPe-AGNSS-DCBsForAllSVs

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavModelDegradationModelList

As per OMA LPPe [5]

OMA-LPPe-AGNSS-CCPassistGenericProvide

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavModelList

As per OMA LPPe [5]

GBLS-AGNSS-DLLCommandAssistGenericProvide

-- ASN1START

GBLS-DLLCommandAssistGenericProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-AGNSS-PLLCommandAssistGenericProvide

-- ASN1START

GBLS-PLLCommandAssistGenericProvide::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

8.2.3.1.5 AGNSS Assistance Data Request

A-GNSS-RequestAssistanceData

As per 3GPP LPP [6]

OMA-LPPe-AGNSS-RequestAssistanceData

-- ASN1START

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)65

OMA-LPPe-AGNSS-RequestAssistanceData::= SEQUENCE {commonAssistDataReq OMA-LPPe-AGNSS-CommonAssistanceDataReq OPTIONAL,genericAssistDataReq OMA-LPPe-AGNSS-GenericAssistanceDataReq OPTIONAL,...

}

-- ASN1STOP

OMA-LPPe-AGNSS-CommonAssistanceDataReq

-- ASN1START

OMA-LPPe-AGNSS-CommonAssistanceDataReq ::= SEQUENCE {ionosphericModelReq OMA-LPPe-AGNSS-IonosphericModelReq OPTIONAL,troposphereModelReq OMA-LPPe-AGNSS-TroposphereModelReq OPTIONAL,altitudeAssistanceReq OMA-LPPe-AGNSS-AltitudeAssistanceReq OPTIONAL,solarRadiationRequest OMA-LPPe-AGNSS-SolarRadiationReq OPTIONAL,ccpRequestControlParameters OMA-LPPe-AGNSS-CCPrequestControlParameters OPTIONAL,dllCommandReqControlParameter GBLS-AGNSS-dllCommandReqControlParameter OPTIONAL,pllCommandReqControlParameter GBLS-AGNSS-pllCommandReqControlParameter OPTIONAL,...

}

-- ASN1STOP

OMA-LPPe-AGNSS-CommonAssistanceDataReq field descriptionsionosphereModelReqAs per OMA LPPe [5]troposphereModelReqAs per OMA LPPe [5]altitudeAssistanceReqAs per OMA LPPe [5]solarRadiationReqAs per OMA LPPe [5]ccpRequestControlParametersAs per OMA LPPe [5]dllCommandReqControlParameter[tbd]pllCommandReqControlParameter[tbd]

OMA-LPPe-AGNSS-GenericAssistanceDataReq

-- ASN1START

OMA-LPPe-AGNSS-GenericAssistanceDataReq ::= SEQUENCE (SIZE (1..16)) OF OMA-LPPe-AGNSS-GenericAssistDataReqElement

OMA-LPPe-AGNSS-GenericAssistDataReqElement ::= SEQUENCE {gnss-ID GNSS-ID,waIonoSurfaceReq OMA-LPPe-AGNSS-WaIonoSurfaceRequest OPTIONAL, --Cond WAionomechanicsReq OMA-LPPe-AGNSS-MechanicsReq OPTIONAL,dcbReq OMA-LPPe-AGNSS-DCBreq OPTIONAL,navModelDegradationModelReq OMA-LPPe-AGNSS-NavModelDegradationModelReq OPTIONAL,ccpAssistGenericReq OMA-LPPe-AGNSS-CCPassistGenericReq OPTIONAL, --Cond CCPreqnavigationModelReq OMA-LPPe-AGNSS-NavigationModelReq OPTIONAL,dllCommandAssistGenericReq GBLS-AGNSS-dllCommandAssistGenericReq OPTIONAL, --Cond dllreqpllCommandAssistGenericReq GBLS-AGNSS-pllCommandAssistGenericReq OPTIONAL, --Cond pllreq...

}

-- ASN1STOP

Conditional presence ExplanationWAiono As per OMA LPPe [5]CCPreq As per OMA LPPe [5]dllreq [tbd]pllreq [tbd]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)66

OMA-LPPe-AGNSS-GenericAssistanceDataReq field descriptionswaIonoSurfaceReqAs per OMA LPPe [5]mechanicsReqAs per OMA LPPe [5]dcbReqAs per OMA LPPe [5]navModelDegradationModelReqAs per OMA LPPe [5]ccpAssistGenericReqAs per OMA LPPe [5]navigationModelReqAs per OMA LPPe [5]dllCommandAssistGenericReq[tbd]pllCommandAssistGenericReq[tbd]

8.2.3.1.6 AGNSS Assistance Data Request Elements

OMA-LPPe-AGNSS-IonosphericModelReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-TroposphereModelReq ,

As per OMA LPPe [5]

OMA-LPPe-AGNSS-AltitudeAssistanceReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-SolarRadiationReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-CCPrequestControlParameters,

As per OMA LPPe [5]

GBLS-dllCommandReqControlParameter

-- ASN1START

GBLS-AGNSS-dllCommandReqControlParameter::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-pllCommandReqControlParameter

-- ASN1START

GBLS-AGNSS-pllCommandReqControlParameter::= SEQUENCE {xx xx xx...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)67

-- ASN1STOP

OMA-LPPe-AGNSS-WaIonoSurfaceRequest

As per OMA LPPe [5]

OMA-LPPe-AGNSS-MechanicsReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-DCBreq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavModelDegradationModelReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS- CCPassistGenericReq

As per OMA LPPe [5]

OMA-LPPe-AGNSS-NavigationModelReq

As per OMA LPPe [5]

GBLS-dllCommandAssistGenericReq

-- ASN1START

GBLS-AGNSS-dllCommandAssistGenericReq ::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

GBLS-pllCommandAssistGenericReq

-- ASN1START

GBLS-AGNSS-pllCommandAssistGenericReq ::= SEQUENCE {xx xx xx...

}

-- ASN1STOP

8.2.3.1.7 AGNSS Location Information

A-GNSS-ProvideLocationInformation

As per 3GPP LPP [6]

OMA-LPPe-AGNSS-ProvideLocationInformation

-- ASN1START

OMA-LPPe-AGNSS-ProvideLocationInformation ::= SEQUENCE {

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)68

highAccuracyReferenceTime GNSS-SystemTime OPTIONAL, --Cond HighAccuracyhighAccuracyMeasurements OMA-LPPe-AGNSS-HAgnssProvide OPTIONAL,ionosphereMeasurements OMA-LPPe-AGNSS-IonosphereMeasurements OPTIONAL,localSurfaceMeasurements OMA-LPPe-AGNSS-LocalSurfaceMeasurements OPTIONAL,rfSamplingMeasurements GBLS-GNSS-RfSamples OPTIONAL,error OMA-LPPe-AGNSS-Error OPTIONAL,...

}

-- ASN1STOP

8.2.3.1.8 AGNSS Location Information elements

GNSS-SystemTime

As per OMA LPPe [5]

OMA-LPPe-AGNSS-HAgnssProvide,

As per OMA LPPe [5]

OMA-LPPe-AGNSS-IonosphereMeasurements,

As per OMA LPPe [5]

OMA-LPPe-AGNSS-LocalSurfaceMeasurements

As per OMA LPPe [5]

GBLS-GNSS-RfSamples

-- ASN1START

GBLS-GNSS-RfSamples ::= SEQUENCE {[tdb],...

}

-- ASN1STOP

8.2.3.1.9 AGNSS Location Information Request

A-GNSS-RequestLocationInformation

As per 3GPP LPP [6]

OMA-LPPe-AGNSS-RequestLocationInformation

-- ASN1START

OMA-LPPe-AGNSS-RequestLocationInformation ::= SEQUENCE {positioningInstructions OMA-LPPe-AGNSS-PositioningInstructions OPTIONAL,ionosphereMeasurementsReq BIT STRING {tecPerSV(0), zenithTEC(1) }(SIZE(1..8)) OPTIONAL,localSurfaceMeasurementReq OMA-LPPe-AGNSS-LocalSurfaceMeasurementReq OPTIONAL,...

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)69

OMA-LPPe-AGNSS-RequestLocationInformation field descriptionspositioningInstructions[tbd]ionosphereMeasurementsReqAs per OMA LPPe [5]localSurfaceMeasurementReqAs per OMA LPPe [5]

8.2.3.1.10 AGNSS Location Information Request elements

OMA-LPPe-AGNSS-PositioningInstructions

-- ASN1START

OMA-LPPe-AGNSS-PositioningInstructions ::= SEQUENCE {highAccuracyMethodRequested BOOLEAN,haGNSSreq OMA-LPPe-AGNSS-HAgnssRequestControlParameters OPTIONAL, --Cond HAgnssReqrfSamplesRequested BOOLEANrfSamplesParameters GBLS-RFSamplesControlParameters OPTIONAL, --Cond RFsampReq

...}

-- ASN1STOP

Conditional presence ExplanationHAgnssReq As per OMA LPPe [5]RDsampReq [tbd]

highAccuracyMethodRequestedAs per OMA LPPe [5]haGNSSreqAs per OMA LPPe [5]rfSamplesParameters[tbd]rfSamplesRequested[tbd]

GBLS-RFSamplesControlParameters

-- ASN1START

GBLS-RFSamplesControlParameters ::= SEQUENCE {[tbd] ,...

}

-- ASN1STOP

8.2.3.1.11 GNSS Timing Information

-- ASN1START

GNSS-ProvideTimingInformation ::= SEQUENCE {reportedTimingQoS ReportedTimingQoS OPTIONAL,timingError TimingError OPTIONAL,...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)70

ReportedTimingQoS::= SEQUENCE {TimingUncertainty INTEGER(0..[tbd]) OPTIONAL, -- timeUncertReqTimingCL INTEGER(0..100) OPTIONAL, -- timeCLReportingTimingAccuracyNotMet BOOLEAN OPTIONAL, -- timeTargetAccReqTimingAuthentication BOOLEAN OPTIONAL, -- timeAuthReq...

}

-- ASN1STOP

Conditional presence ExplanationtimeUncertReq This field is mandatory present if the associated timing information request requires for

time accuracy estimate.timeCLReporting This field is mandatory present if the associated timing information request requires for

time accuracy estimates.It can be equal to the “confidence” set in the timing information request, or lower in case the timing accuracy estimate computed cannot meet the required confidence level.

timeTargetAccReq This field is mandatory present if the associated timing information request requires for a targeted timing accuracy, with “qosclass” set to “BEST EFFORT”,

timeAuthReq This field is mandatory present if the associated timing information request requires for authenticated timing.

GNSS-ProvideTimingInformation field descriptionsreportedTimingQoS[tbd]TimingUncertaintyTimingCLTimingAccuracyNotMetTimingAuthentication

timingError[tbd]

8.2.3.1.12 GNSS Timing Information Request

-- ASN1START

GNSS-RequestTimingInformation ::= SEQUENCE {timingInformationType timingInformationType,timeTransferMethod ENUMERATED { pTPrequired,

pTPpreferred,iRIGBrequired,iRIGBpreferred,nTPrequired,nTPpreferred,sNTPrequired,sNTPpreferred,pPStimeTagingRequered,pPStimeTagingPreferred,

},timingQoS TimingQoS OPTIONAL,...

}

timingInformationType ::= SEQUENCE {gnss-Methods GNSS-ID-BitmapmultiFreqMeasReq BOOLEAN,assistanceAvailability BOOLEAN,timeAccuracyEstimate BOOLEAN...

}

TimingQoS ::= SEQUENCE {synchroAccuracy SynchroAccuracy OPTIONALsynchroAuthentication BOOLEAN,...

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)71

SynchroAccuracy n::= SEQUENCE {accuracy INTEGER(0..127), OPTIONALconfidence INTEGER(0..100), OPTIONALQos class ENUMERATED { ASSURED,

BEST_EFFORT, ...} OPTIONAL...

}

-- ASN1STOP

GNSS-RequestTimingInformation field descriptionstimingInformationType[tbd]timeTransferMethod[tbd]timingQoS[tbd]synchroAccuracy : see table belowsynchroAuthentication : [tbd]

The table below indicates how IE synchroAccuracy is structured :

accuracy field

confidence field

qosClass field

Explanation

Case 1 present absent ASSURED Targeted synchronization accuracy is specified, and only synchronization signal complying with targeted accuracy shall be provided.

Case 2 present absent BEST EFFORT

Targeted synchronization accuracy is specified, and synchronization signal not complying with targeted accuracy shall be flagged in the subsequent answer (using IE “GBLS-QosIndicators”).

Case 3 absent present absent Estimation of the measure accuracy is required. Accuracy estimate should comply with the required confidence level. In CL cannot be met, it shall be indicated in the subsequent answer (using IE “GBLS-ConfidenceLevels”).

8.2.3.1.13 AGNSS Error

OMA-LPPe-AGNSS-Error

-- ASN1START

OMA-LPPe-AGNSS-Error ::= CHOICE {agnss-locationServerErrorCauses OMA-LPPe-AGNSS-LocationServerErrorCauses,agnss-targetDeviceErrorCauses OMA-LPPe-AGNSS-TargetDeviceErrorCauses,...

}

-- ASN1STOP

[add in IE above new potential error message, for instance Timing Error]

8.2.3.1.14 AGNSS Abort

OMA-LPPe-AGNSS-Abort

As per OMA LPPe [5]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)72

8.2.3.2 Cellular Telecommunication signal-based positioning

8.2.3.2.1 OTDOA

8.2.3.2.2 OTDOA Provide Assistance Data

As per OMA LPPe [5]

Note: OMA-LPPe OTDOA includes references to 3GPP LPP OTDOA assistance data

8.2.3.2.3 OTDOA Request Assistance Data

As per OMA LPPe [5]

8.2.3.2.4 EOTD

As per OMA LPPe [5]

8.2.3.2.5 OTDOA-UTRA

As per OMA LPPe [5]

8.2.3.2.6 LTE Enhanced Cell ID Positioning

As per OMA LPPe [5]

8.2.3.2.7 GSM Enhanced Cell ID Positioning

As per OMA LPPe [5]

8.2.3.2.8 UTRA Enhanced Cell ID Positioning

As per OMA LPPe [5]

8.2.3.2.9 WLAN Enhanced Cell ID Positioning

As per OMA LPPe [5]

8.2.3.2.10 WiMax Enhanced Cell ID Positioning

As per OMA LPPe [5]

8.2.3.3 Inertial Sensor positioning

8.2.3.3.1 Inertial Sensor Assistance Data

GBLS-IntertialSensor-ProvideAssistanceData

-- ASN1START

GBLS-IntertialSensor-ProvideAssistanceData::= SEQUENCE {motionStateList OMA-LPPe-Sensor-MotionStateList OPTIONAL,sensorError OMA-LPPe-Sensor-Error OPTIONAL,

}

-- ASN1STOP

8.2.3.3.2 Inertial Sensor Assistance Data elements

OMA-LPPe-Sensor-MotionStateList

As per OMA LPPe [5]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)73

OMA-LPPe-Sensor-Error

As per OMA LPPe [5]

8.2.3.3.3 Inertial Sensor Assistance Data Request

GBLS-IntertialSensor-RequestAssistanceData

-- ASN1START

GBLS-IntertialSensor-RequestAssistanceData::= SEQUENCE {motionStateReq OMA-LPPe-Sensor-MotionStateRequest OPTIONAL, --Cond MotionSateReq

}

-- ASN1STOP

Conditional presence ExplanationMotionStateReq The field is mandatory present if the sensor requests for primary motion state measurements;

otherwise it is not present.

8.2.3.3.4 Inertial Sensor Assistance Data Request elements

OMA-LPPe-Sensor-MotionStateRequest

As per OMA LPPe [5]

8.2.3.3.5 Inertial Sensor Location Information Request

GBLS-IntertialSensor-RequestLocationInformation

-- ASN1START

GBLS-IntertialSensor-RequestLocationInformation::= SEQUENCE {sensorGyroInformationReq GBLS-GyroInformationRequest OPTIONALsensorAccelerometerInformationReq GBLS-AccelerometerInformationRequest OPTIONAL

}

-- ASN1STOP

8.2.3.3.6 Inertial Sensor Location Information Request elements

GBLS-GyroInformationRequest

-- ASN1START

GBLS-GyroInformationRequest::= SEQUENCE {gyroXReq BOOLEAN,gyroYReq BOOLEAN,gyroZReq BOOLEAN,

}

-- ASN1STOP

GBLS-AccelerometerInformationRequest

-- ASN1START

GBLS-AccelerometerInformationRequest::= SEQUENCE {AccelXReq BOOLEAN,AccelYReq BOOLEAN,AccelZReq BOOLEAN,

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)74

-- ASN1STOP

8.2.3.3.7 Inertial Sensor Location Information

GBLS-InertialSensor-ProvideLocationInformation

-- ASN1START

GBLS-InertialSensor-ProvideLocationInformation::= SEQUENCE {sensorCaseCRM OMA-LPPe-Orientation OPTIONALsensoBodyCRM OMA-LPPe-Orientation OPTIONALsensorGyroInformation GBLS-GyroInformation OPTIONALsensorAccelerometerInformation GBLS-AccelerometerInformation OPTIONAL

}

-- ASN1STOP

8.2.3.3.8 Inertial Sensor Location Information elements

GBLS-GyroInformation

-- ASN1START

GBLS-GyroInformation::= SEQUENCE {sensorGyroMeasurments GBLS-GyroMeasurementInformation OPTIONAL...

}

-- ASN1STOP

GBLS-GyroMeasurementInformation

-- ASN1START

GBLS-GyroMeasurementInformation::= SEQUENCE {SensorX INTEGER(-tbd..tbd) OPTIONAL CondSensorY INTEGER(-tbd..tbd) OPTIONAL CondSensorZ INTEGER(-tbd..tbd) OPTIONAL CondSensorErrEstX INTEGER(-tbd..tbd) OPTIONAL CondSensorErrEstY INTEGER(-tbd..tbd) OPTIONAL CondSensorErrEstZ INTEGER(-tbd..tbd) OPTIONAL Cond...

}

-- ASN1STOP

GBLS-AccelerometerInformation

-- ASN1START

GBLS-AccelerometerInformation::= SEQUENCE {sensorAccelerometerMeasurments GBLS-AccelerometerMeasurementInformation OPTIONAL...

}

-- ASN1STOP

GBLS-AccelerometerMeasurementInformation

-- ASN1START

GBLS-AccelerometerMeasurementInformation::= SEQUENCE {SensorX INTEGER(-tbd..tbd) OPTIONALSensorY INTEGER(-tbd..tbd) OPTIONALSensorZ INTEGER(-tbd..tbd) OPTIONALSensorErrEstX INTEGER(-tbd..tbd) OPTIONALSensorErrEstY INTEGER(-tbd..tbd) OPTIONALSensorErrEstZ INTEGER(-tbd..tbd) OPTIONAL...

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)75

OMA-LPPe-Orientation

As per OMA LPPe [5]

[NB : for sensorCaseCRM and sensoBodyCRM, refer to Error: Reference source not found.]

8.2.3.3.9 Inertial Sensor Error

OMA-LPPe-Sensor-Error

As per OMA LPPe [5]

8.2.3.4 Magnetometer positioning

8.2.3.4.1 Magnetometer Assistance Data

GBLS-Magnetometer-ProvideAssistanceData

-- ASN1START

GBLS-Magnetometer-ProvideAssistanceData::= SEQUENCE {magnetoTemperature GBLS-MagnetometerTemperature OPTIONAL Cond

}

-- ASN1STOP

8.2.3.4.2 Magnetometer Assistance Data elements

GBLS-MagnetometerTemperature

-- ASN1START

GBLS-MagnetometerTemperature::= SEQUENCE {temperature INTEGER (-64..63)temperatureUnit ENUMERATED{ celsius, kelvin, ... },

}

-- ASN1STOP

8.2.3.4.3 Magnetometer Assistance Data Request

GBLS-Magnetometer-RequestAssistanceData

-- ASN1START

GBLS-Magnetometer-RequestAssistanceData::= SEQUENCE {magnetoTemperatuReq GBLS-MagnetometerTemperatureRequest OPTIONAL

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)76

8.2.3.4.4 Magnetometer Assistance Data Request elements

GBLS-MagnetometerTemperatureRequest

-- ASN1START

GBLS-MagnetometerTemperatureRequest::= SEQUENCE {temperatureUnit ENUMERATED{ celsius, kelvin, ... }, OPTIONAL

}

-- ASN1STOP

8.2.3.4.5 Magnetometer Location Information

GBLS-Magnetometer-ProvideLocationInformation

-- ASN1START

GBLS-Magnetometer-ProvideLocationInformation::= SEQUENCE {sensorCaseCRM OMA-LPPe-Orientation OPTIONALsensoBodyCRM OMA-LPPe-Orientation OPTIONALsensorMagnetometerInformation GBLS-MagnetometerInformation OPTIONAL

}

-- ASN1STOP

8.2.3.4.6 Magnetometer Location Information elements

GBLS-MagnetometerInformation

-- ASN1START

GBLS-MagnetometerInformation::= SEQUENCE {sensorCaseCRM OMA-LPPe-Orientation OPTIONALsensoBodyCRM OMA-LPPe-Orientation OPTIONALsensorMagnetometerMeasurments GBLS-MagnetometerMeasurementInformation OPTIONAL...

}

-- ASN1STOP

GBLS-MagnetometerInformation field descriptions

GBLS-MagnetometerMeasurementInformation

-- ASN1START

GBLS-MagnetometerMeasurementInformation::= SEQUENCE {xMagField INTEGER(-tbd..tbd) OPTIONAL, CondyMagField INTEGER(-tbd..tbd) OPTIONAL, CondzMagField INTEGER(-tbd..tbd) OPTIONAL, Condheading INTEGER(-tbd..tbd) OPTIONAL, CondMagFieldStrength INTEGER(-tbd..tbd) OPTIONAL, CondxMagFieldErrEst INTEGER(-tbd..tbd) OPTIONAL, CondyMagFieldErrEst INTEGER(-tbd..tbd) OPTIONAL, CondzMagFieldErrEst INTEGER(-tbd..tbd) OPTIONAL, CondheadingErrEst INTEGER(-tbd..tbd) OPTIONAL, CondMagFieldStrengthErrEst INTEGER(-tbd..tbd) OPTIONAL, Cond

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)77

GBLS- MagnetometerMeasurementInformation field descriptions

8.2.3.4.7 Magnetometer Location Information Request

GBLS-Magnetometer-RequestLocationInformation

-- ASN1START

GBLS-Magnetometer-RequestLocationInformation::= SEQUENCE {magnetometerInformationType GBLS-MagnetometerInformationType OPTIONAL

}

-- ASN1STOP

8.2.3.4.8 Magnetometer Location Information Request elements

GBLS-MagnetometerInformationType

-- ASN1START

GBLS-MagnetometerInformationType::= SEQUENCE {xMagFieldReq BOOLEAN,yMagFieldReq BOOLEAN,zMagFieldReq BOOLEAN,headingReq BOOLEAN,MagFieldStrengthReq BOOLEAN,

}

-- ASN1STOP

8.2.3.5 Odometer positioning

8.2.3.5.1 Odometer Assistance Data

GBLS-Odometer-ProvideAssistanceData

-- ASN1START

GBLS-Odometer-ProvideAssistanceData::= SEQUENCE {wheeleInformation GBLS-WheeleInformation OPTIONAL Cond

}

-- ASN1STOP

8.2.3.5.2 Odometer Assistance Data Elements

GBLS-WheeleInformation

-- ASN1START

GBLS-WheeleInformation::= SEQUENCE {wheeleSize INTEGER (0..[tbd])sizeUnit ENUMERATED{ meter, inch, ... },

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)78

8.2.3.5.3 Odometer Assistance Data Request

GBLS-Odometer-RequestAssistanceData

-- ASN1START

GBLS-Odometer-RequestAssistanceData::= SEQUENCE {wheeleInformationReq GBLS-WheeleInformationReq OPTIONAL

}

-- ASN1STOP

8.2.3.5.4 Odometer Assistance Data Request elements

GBLS-WheeleInformationReq

-- ASN1START

GBLS-Wheele-InformationReq::= SEQUENCE {sizeUnit ENUMERATED{ meter, inch, ... }, OPTIONAL

}

-- ASN1STOP

8.2.3.5.5 Odometer Location Information

GBLS-Odometer-ProvideLocationInformation

-- ASN1START

GBLS-Odometer-ProvideLocationInformation::= SEQUENCE {travelledDistance INTEGER (0..[tbd]) OPTIONAL, Cond odomDistReqodomVelocity INTEGER (0..[tbd]) OPTIONAL, Cond odomVelReqreverseFlag BOOLEAN

}

-- ASN1STOP

Conditional presence ExplanationodomDistReq [tbd]odomVelReq [tbd]

GBLS-Odometer-ProvideLocationInformation field descriptionstravelledDistance[tbd]odomVelocity[tbd]reverseFlag[tbd]NB : mandatory present, since it accompanies the travelled distance and/of velocity information from the odometer

8.2.3.5.6 Odometer Location Information Request

GBLS-Odometer-RequestLocationInformation

-- ASN1START

GBLS-Odometer-RequestLocationInformation::= SEQUENCE {odometerInformationType SEQUENCE{

travelledDistanceReq BOOLEANodomVelocityReq BOOLEAN}

}

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)79

-- ASN1STOP

GBLS-Odometer-RequestLocationInformation field descriptionsodometerInformationType[tbd]travelledDistanceReq[tbd]odomVelocityReq[tbd]

8.2.3.6 Beam Forming Antenna Positioning

8.2.3.6.1 BFA Assistance Data

GBLS-BFN-ProvideAssistanceData

-- ASN1START

GBLS-BFN-ProvideAssistanceData::= SEQUENCE {inertialMeasurement GBLS-InertialAssistance OPTIONAL Need ONvelocityEstimate Velocity OPTIONAL Need ONheadingEstimate GBLS-Heading OPTIONAL Need ONgnss-NavigationModel GNSS-NavigationModel OPTIONAL Need ONgnss-Almanac GNSS-Almanac OPTIONAL Need ON

}

-- ASN1STOP

GBLS-BFN-ProvideAssistanceData field descriptionsinertialMeasurement[tbd]velocityEstimate[tbd]headingEstimate[tbd]gnss-NavigationModel[tbd]gnss-Almanac[tbd]

8.2.3.6.2 BFA Assistance Data elements

GBLS-InertialAssistance

-- ASN1START

GBLS-InertialAssistance::= SEQUENCE {sensorCaseCRM OMA-LPPe-Orientation OPTIONAL, CondsensoBodyCRM OMA-LPPe-Orientation OPTIONAL, CondsensorGyroInformation GBLS-GyroInformation OPTIONAL, CondsensorAccelerometerInformation GBLS-AccelerometerInformation OPTIONAL, Cond

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)80

Conditional presence ExplanationCond [tbd]Cond [tbd]Cond [tbd]Cond [tbd]

GBLS-InertialAssistance field descriptionssensorCaseCRM[tbd]sensoBodyCRM[tbd]sensorGyroInformation[tbd]sensorAccelerometerInformation[tbd]

GNSS-NavigationModel

As per 3GPP LPP [6]

GNSS-Almanac

As per 3GPP LPP [6]

8.2.3.6.3 BFA Assistance Data Request

-- ASN1START

GBLS-BFN-RequestAssistanceData::= SEQUENCE {inertialMeasurementReq GBLS-InertialAssistanceReq OPTIONAL -- Need ONvelocityEstimateReq BOOLEAN OPTIONAL -- Need ONheadingEstimateReq BOOLEAN OPTIONAL -- Need ONgnss-NavigationModelReq GNSS-NavigationModelReq OPTIONAL -- Need ONgnss-Alamanc GNSS-AlmanacReq OPTIONAL -- Need ON

}

-- ASN1STOP

GBLS-BFN-RequestAssistanceData field descriptionsinertialMeasurementReq[tbd]velocityEstimateReq[tbd]headingEstimateReq[tbd]gnss-NavigationModelReq[tbd]GNSS-AlmanacReq[tbd]

8.2.3.6.4 BFA Assistance Data Request elements

GBLS-InertialAssistanceReq

-- ASN1START

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)81

GBLS-InertialAssistanceReq::= SEQUENCE {sensorGyroInformationReq GBLS-GyroInformationRequest OPTIONAL -- Need ONsensorAccelerometerInformationReq GBLS-AccelerometerInformationRequest OPTIONAL -- Need ON

}

-- ASN1STOP

GBLS-InertialAssistanceReq field descriptionssensorGyroInformationReq[tbd]sensorAccelerometerInformationReq[tbd]

GNSS-NavigationModelReq

As per 3GPP LPP [6]

GNSS-AlmanacReq

As per 3GPP LPP [6]

8.2.3.6.5 BFA Location Information

-- ASN1START

GBLS-BFN-ProvideLocationInformation::= SEQUENCE {sensorBodyCRM OMA-LPPe-Orientation OPTIONALdetectedNbrOfJammers INTEGER (1.. maxNbrJammer) OPTIONALjammerList SEQUENCE (SIZE (1..maxNbrJammer) OF GBLS-JammerSignal OPTIONALdetectedNbrOfEchos INTEGER (1.. maxNbrEcho) OPTIONALmultipathList SEQUENCE (SIZE (1..maxNbrEcho) OF GBLS-EchoSignal OPTIONAL

}

maxNbrJammer INTEGER ::= [tbd]

maxNbrEcho INTEGER ::= [tbd]

-- ASN1STOP

GBLS-JammerSignal field descriptionssensorBodyCRM[tbd]detectedNbrOfJammers[tbd]jammerList[tbd]detectedNbrOfEchos[tbd]multipathList[tbd]maxNbrJammer[tbd]NB : absolute maximum number of jammer allowed by the data model definitionmaxNbrEcho[tbd]NB : absolute maximum number of jammer allowed by the data model definition

8.2.3.6.6 BFA Location Information elements

GBLS-JammerSignal

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)82

-- ASN1START

GBLS-JammerSignal::= SEQUENCE {receivedPower GBLS-JammingReceivedPower OPTIONALestimatedFrequency GBLS-JammingFrequency OPTIONALesimtaedBandwidth GBLS-JammingBandwidth OPTIONALjammerEstimatedDoA GBLS-DirectionOfArrival OPTIONAL

}

GBLS-JammingReceivedPower::= SEQUENCE {powerEstimate INTEGER (1..[tbd]) OPTIONALpowerEstError INTEGER (1..[tbd]) OPTIONAL

}

GBLS-JammingFrequency::= SEQUENCE {frequencyEstimate INTEGER (1..[tbd]) OPTIONALfrequencyEstError INTEGER (1..[tbd]) OPTIONAL

}

GBLS-JammingBandwidth::= SEQUENCE {bwEstimate INTEGER (1..[tbd]) OPTIONALbwEstError INTEGER (1..[tbd]) OPTIONAL

}

-- ASN1STOP

GBLS-JammerSignal field descriptionsreceivedPower[tbd]estimatedFrequency[tbd]estimatedBandwidth[tbd]jammerEstimatedDoA[tbd]powerEstimate[tbd]powerEstError[tbd]frequencyEstimate[tbd]frequencyEstError[tbd]bwEstimate[tbd]bwEstError[tbd]

GBLS-EchoSignal

-- ASN1START

GBLS-EchoSignal::= SEQUENCE {relativePower GBLS-EchoRelativePower OPTIONALdelay GBLS-EchoDelay OPTIONALcarrierDopplerFreq GBLS-EchoCarrierDopplerFreq OPTIONALechoEstimatedDoA GBLS-DirectionOfArrival OPTIONAL

}

GBLS-EchoRelativePower::= SEQUENCE {relativePowerEstimate INTEGER (1..[tbd]) OPTIONALrelativePowerEstError INTEGER (1..[tbd]) OPTIONAL

}

GBLS-EchoDelay::= SEQUENCE {delayEstimate INTEGER (1..[tbd]) OPTIONALdelayEstError INTEGER (1..[tbd]) OPTIONAL

}

GBLS-EchoCarrierDopplerFreq::= SEQUENCE {carDopFreqEstimate INTEGER (1..[tbd]) OPTIONALcarDopFreqEstError INTEGER (1..[tbd]) OPTIONAL

}

-- ASN1STOP

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)83

GBLS-JammerSignal field descriptionsrelativePower[tbd]delay[tbd]carrierDopplerFreq[tbd]echoEstimatedDoA[tbd]relativePowerEstimate[tbd]relativePowerEstError[tbd]delayEstimate[tbd]delayEstError[tbd]carDopFreqEstimate[tbd]carDopFreqEstError[tbd]

8.2.3.6.7 BFA Location Information Request

GBLS-BFN-RequestLocationInformation

-- ASN1START

GBLS-BFN-RequestLocationInformation::= SEQUENCE {jammerProcessingReq GBLS-JammerProcessingReqmultipathProcessingReq GBLS-MultipathProcessingReq...

}-- ASN1STOP

GBLS-JammerSignal field descriptionsjammerProcessingReq[tbd]multipathProcessingReq[tbd]

8.2.3.6.8 BFA Location Information Request elements

GBLS-JammerProcessingReq

-- ASN1START

GBLS-JammerProcessingReq::= SEQUENCE {requestedMaxNbrOfJammers INTEGER (1..[tbd]) OPTIONALrxPowerReq BOOLEANfrequencyReq BOOLEANbwReq BOOLEANdoAReq BOOLEAN...

}-- ASN1STOP

GBLS-MultipathProcessingReq

-- ASN1START

GBLS-MultipathProcessingReq::= SEQUENCE {requestedMaxNbrOfEchos INTEGER (1..[tbd]) OPTIONALrelPowerReq BOOLEANdelayReq BOOLEAN

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)84

carDopplerFreqReq BOOLEANdoAReq BOOLEAN...

}

-- ASN1STOP

8.2.3.7 Mapping Positioning

[FFS]

ETSI

ETSI TS 103 246-4 V0.0.5 (2015-04)85

Annex A (informative):Rationale for LSEP/MLP and LSIP/LPPe

A.1 Basis for LSEP/MLP Explain why MLP is the most appropriate protocol to start from

List the most relevant MLP procedures for LSEP

Explain the necessary changes to the MLP messages

A.2 Basis for LSIP/LPPe Explain why LPP/LPPe is the most appropriate protocol to start from

List the most relevant LPP/LPPe procedures for LSIP

Explain the necessary changes to the LPP/LPPe messages

Annex B (informative):LSEP elements technical characteristics

The table below provides information derived from the elements definition, and which would contribute to the selection of a syntax in view of an implementation of LSEP. This information contains variable type, range and accuracy, all issued from technical constrains.

ETSI

86 ETSI TS 103 246-4 V0.0.5 (2015-04)

Robert Mort, 08/02/15,

Normative??


Table A-1: LSEP elements characteristics

Name Unit Type Suggested accuracy

Admitted range Default values

accel m/s² signed decimal 0,1 [tbc] [-50 ; 50] [tbc] n/aaccel_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/aaccel_info - - - - -auth_req - boolean - [YES / NO] NOmot_type - char. string - [LINEAR, ANGULAR] [LINEAR]accel_unc m/s² positive decimal 0,1 [tbc] [0 ; 10] [tbc] n/aalt_info - - - - -alt_unc m positive decimal 0,01 [tbc] [0 ; 100] [tbc] auth_flag - char. string - [NO, YES, UNKNOWN] -req_emidata - char. string - [POS_ONLY,

POS_AND_BW][POS_ONLY]

h_acc_not_met - - - - -h_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/aconf_class - char. string - [INFO , ALERT] [INFO]h_int_alert - - - - -head_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/ahead_info - - - - -head_unc degree positive decimal 0,1 [tbc] [0 ; 10] [tbc] n/ahigh_freq Hz positive decimal 1 [tbc] [0 ; 2e9] [tbc] n/alev_conf - negative decimal 0,01 [tbc] [-10 ; 0] n/alow_frfeq Hz positive decimal 1 [tbc] [0 ; 2e9] [tbc] n/apfa - negative decimal 0,01 [tbc] [-10 ; 0] n/apmd - negative decimal 0,01 [tbc] [-10 ; 0] n/atime_acc µs positive decimal 0.001 [tbc] [0 ; 10000] [tbc] n/atime_acc_not_met

- - - - -

time_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/atime_p date char. String /

date1 µs [tbc] - n/a

time_unc µs positive decimal 0.001 [tbc] [0 ; 10000] [tbc] n/av_acc_not_met - - - - -v_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/av_int_alert - - - - -vel_acc m/s positive decimal 0,01 [tbc] [0 , 5] [tbd] n/avel_acc_not_met - - - - -vel_conf_lev - negative decimal 0,01 [tbc] [-10 ; 0] n/avel_info - - - - -vel_int_alert - - - - -vel_unc m/s positive decimal 0,01 [tbc] [0 , 5] [tbd] n/a

ETSI

87 ETSI TS 103 246-4 V0.0.5 (2015-04)


??

HistoryDocument history

V0.0.1 June 2014 First Draft

V0.0.2 August 2014 Update of Annex Headings and corrected scope, introduction etc.

V0.0.3 Jan 2015 New title and more content.

V0.0.4 Feb 2015 LSEP and MLP and LSIP an LPP/LPPe content

V0.0.5 April 2015 Edits following WG meeting and subsequent discussion

ETSI

88 ETSI TS 103 246-4 V0.0.5 (2015-04)

SKELETON - ETSI€¦ · Web viewNote: Throughout this document, the word “protocol” is used...

Documents

Transcript of SKELETON - ETSI€¦ · Web viewNote: Throughout this document, the word “protocol” is used...