ETSI TS 103 246-4 V1.2.1 (2017-03)

Satellite Earth Stations and Systems (SES); GNSS based location systems; Part 4: Requirements for location data exchange protocols

RTS/SES-00409

General Information

• Status: Published
• Publication Date: 05-Mar-2017
• Technical Committee: SES SCN - Satellite Communications and Navigation
• Current Stage: 12 - Completion
• Due Date: 01-Mar-2017
• Completion Date: 06-Mar-2017
• Mandate: M/496

Standards Content (Sample)

TECHNICAL SPECIFICATION
Satellite Earth Stations and Systems (SES);
GNSS based location systems;
Part 4: Requirements for location data exchange protocols

2 ETSI TS 103 246-4 V1.2.1 (2017-03)

Reference
RTS/SES-00409
Keywords
GNSS, location, MSS, navigation, performance,
receiver, satellite, system, terminal
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP 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
3 ETSI TS 103 246-4 V1.2.1 (2017-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
Introduction . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Data Exchange Requirements . 9
4.1 Context . 9
4.2 Protocol Choice and Compatibility . 11
4.2.1 LSEP (MLP) . 11
4.2.2 LSIP (LPPe) . 11
4.2.2.1 General . 11
4.2.2.2 LSIP Data Exchange Requirements . 11
4.2.2.3 Additional LSIP IEs for GBLS using differential GNSS positioning methods . 15
4.2.3 EPDD (RTCM104) . 16
4.2.3 LSEP/MLP and LSIP/LPPe Terminology . 16
5 LSEP Requirements . 16
5.1 LSEP Services and Procedures . 16
5.2 Extension of MLP for LSEP. 17
5.3 LSEP Data Exchange Message Definition . 18
6 LSIP Requirements . . 18
6.1 LSIP Services and Procedures . 18
6.2 Extension of LPPe/LPP for LSIP . 19
6.3 LSIP Data Exchange Message Definition . 19
6.3.1 General . 19
6.3.2 IE Extensions of LPP/LPPe for LSIP . 19
6.3.2.1 Message Extensions . 19
6.3.2.2 LPPe data type imports . 20
6.3.3 LSIP Extension Messages . 21
6.3.3.1 Request Assistance Data . 21
6.3.3.2 Provide Assistance Data . 21
6.3.3.3 Request Location Information . 21
6.3.3.4 Provide Location Information . 21
7 LSEP Element Definitions . 22
7.1 Overview . 22
7.2 LSEP Child Elements . 22
7.2.1 Identity elements . 22
7.2.2 Location elements . 22
7.2.3 Quality of Position elements . 24
7.3 LSEP Sub-Child Elements . 25
7.3.1 accel . 25
7.3.2 accel_conf_lev . 25
7.3.3 accel_unc . 25
7.3.4 accel_req . 25
7.3.5 auth_flag . 26
7.3.6 auth_req . 26
7.3.7 conf_class . 26
ETSI
4 ETSI TS 103 246-4 V1.2.1 (2017-03)
7.3.8 emidata_req. 26
7.3.9 h_acc . 27
7.3.10 h_acc_not_met . 27
7.3.11 h_conf_lev . 27
7.3.12 h_int_alert . 27
7.3.13 head_conf_lev . 28
7.3.14 head_req . 28
7.3.15 head_unc . 28
7.3.16 LSEP-msids . 28
7.3.17 v_acc . 28
7.3.18 v_acc_not_met . 29
7.3.19 v_conf_lev . 29
7.3.20 v_unc . 29
7.3.21 v_req . 29
7.3.22 vel_acc . 30
7.3.23 vel_acc_not_met . 30
7.3.24 vel_conf_lev . 30
7.3.25 vel_unc . 30
7.3.26 vel_req . 30
8 LSIP Information Elements . 31
8.1 LSIP Common Positioning IEs . 31
8.1.1 General . 31
8.1.2 LSIP-CommonIEsRequestLocationInformation . 31
8.1.3 LSIP-CommonIEsProvideLocationInformation . 33
8.2 LSIP Common Low-Level IEs . 35
8.2.1 General . 35
8.2.2 LSIP-ConfidenceLevels . 35
8.2.3 LSIP-ErrorMeasurements . 35
8.2.4 LSIP-QosIndicators . 35
8.3 Specific Positioning Method IEs . 36
8.3.1 General . 36
8.3.2 GNSS Positioning . 36
8.3.2.1 LSIP-GNSS-RequestLocationInformation . 36
8.3.2.2 LSIP-GNSS-ProvideLocationInformation . 36
8.3.3 Odometer positioning . 37
8.3.3.1 LSIP-Odometer-RequestAssistanceData . 37
8.3.3.2 LSIP-Odometer-ProvideAssistanceData . 37
8.3.3.3 LSIP-Odometer-RequestLocationInformation . 37
8.3.3.4 LSIP-Odometer-ProvideLocationInformation . 38
8.3.4 Beam Forming Network Positioning . 38
8.3.4.1 LSIP-BFN-RequestLocationInformation . 38
8.3.4.2 LSIP-BFN-ProvideLocationInformation. 38
8.3.4.3 LSIP-JammerSignal . 39
8.3.5 Mapping Positioning . 39
9 DGNSS information elements . 39
9.1 General . 39
9.2 Case of conventional DGNSS . 40
9.3 Case of RTK . 40
9.4 NRTK . 41
9.5 PPP . 44
Annex A (informative): Rationale for LSEP/MLP and LSIP/LPPe . 45
A.1 Basis for LSEP/MLP . 45
A.2 Basis for LSIP/LPPe . 45
A.3 LSIP Implementation Cases . 45
A.4 LSIP Procedure examples for GBLS Interface 10 . 47
A.4.1 "Mobile-centric" Assistance data provisioning . 47
A.4.2 "Network-centric" Location Information provisioning . 48
ETSI
5 ETSI TS 103 246-4 V1.2.1 (2017-03)
Annex B (informative): Bibliography . 49
History . 50

ETSI
6 ETSI TS 103 246-4 V1.2.1 (2017-03)
Intellectual Property Rights
IPRs 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 (https://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.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and
Systems (SES).
The present document is part 4 of a multi-part deliverable covering GNSS-based Location Systems (GBLS), as
identified in part 1 [1].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "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.
Introduction
The increasing expansion of location-based applications aims to satisfy more and more complex and diversified user
requirements: this is highlighted for example by the widespread adoption of multi-functional smart-phones or by the
ever wider adoption of tracking devices (e.g. in transport), etc. This requirement for new and innovative location-based
applications is generating a requirement for increasingly complex location systems.
The wide spectrum of location-based applications identified in ETSI TR 103 183 [i.1] calls for a new and broader
concept for location systems, taking into account solutions in which GNSS technologies are complemented with other
technologies to improve robustness and performance. The notion of GNSS-based location systems is introduced and
defined in the present document.
Additional clauses and information related to the implementation in GNSS-based location systems of the various
differential GNSS technologies, namely D-GNSS, RTK and PPP are also included in order to facilitate the use of this
set of standards by manufacturers and service providers.

ETSI
7 ETSI TS 103 246-4 V1.2.1 (2017-03)
1 Scope
This multi-part deliverable addresses integrated GNSS based location systems (GBLS) that combine Global Navigation
Satellite Systems (GNSS), with other navigation technologies, as well as with telecommunication networks in order to
deliver location-based services to users. As a consequence the present document is not applicable to GNSS only
receivers.
This multi-part deliverable proposes a list of functional and performance requirements and related test procedures. For
each performance requirement, different classes are defined allowing the benchmark of different GBLS addressing the
same applications.
The present document defines the requirements for data elements that may need to be exchanged within the GBLS and
externally to applications using the GBLS.
The present 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
complex GBLS, as well as between the GBLS and external applications.
The present document defines the procedures and messages associated with these data exchange models.
The GBLS data exchange models are defined to be independent of their underlying transport mechanisms. Nevertheless,
on certain GBLS interfaces, transport protocols are recommended.
2 References
2.1 Normative references
References 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 which are not found to be publicly available in the expected location might be found at
https://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.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 103 246-1: "Satellite Earth Stations and Systems (SES); GNSS based location systems;
Part 1: Functional requirements".
[2] ETSI TS 103 246-2: "Satellite Earth Stations and Systems (SES); GNSS based location systems;
Part 2: Reference Architecture".
[3] ETSI TS 103 246-3: "Satellite Earth Stations and Systems (SES); GNSS based location systems;
Part 3: Performance requirements".
[4] OMA-TS-MLP-V3.1: "Mobile Location Protocol".
[5] OMA-TS-LPPe-V2.0: "LPP Extensions Specification".
[6] ETSI TS 136 355: "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning
Protocol (LPP) (3GPP TS 36.355)".
[7] RTCM 10402.3: "Recommended Standards for Differential GNSS (Global Navigation Satellite
Systems) Service".
[8] RTCM 10403.2: " Differential GNSS (Global Navigation Satellite Systems) Services".
ETSI
8 ETSI TS 103 246-4 V1.2.1 (2017-03)
2.2 Informative references
References 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.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The 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] OMA-TS-ULP-V3: "User Plane Location Protocol".
[i.3] OMA-AD-LOCSIP-V1: "Location in SIP/IP core Architecture".
[i.4] ETSI ES 201 915: "Open Service Access (OSA); Application Programming Interface (API)".
[i.5] 3GPP2 C.S0022-B: "Position Determination Service for cdma2000 Spread Spectrum Systems".
[i.6] ETSI TS 125 331: "Universal Mobile Telecommunications System (UMTS); Radio Resource
Control (RRC); Protocol specification (3GPP TS 25.331)".
[i.7] ETSI TS 144 031: "Digital cellular telecommunications system (Phase 2+); Location Services
(LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC) Radio Resource LCS
Protocol (RRLP) (3GPP TS 44.031)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI TS 103 246-1 [1] apply.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
API Application Programming Interface
ASN Abstract Syntax Notation
BFN Beam Forming Network
CL Confidence Level
CNR Carrier-to-Noise Ratio
DGNSS  Differential GNSS
D-GNSS Differential GNSS
DoA Direction of Arrival
DTD Document Type Definition
ECID Enhanced Cell ID
EMI ElectroMagnetic Interference
EOTD Enhanced Observed Time Difference
EPDD External Protocol for Differential Data
EPDU Extension Protocol Data Unit
E-SMLC Enhanced Mobile Location Centre
FFS For Further Study
FKP Flächen Korrekctur Parameter (German)
GBLS GNSS Based Location System
GGTO GPS-Galileo Time Offset
ETSI
9 ETSI TS 103 246-4 V1.2.1 (2017-03)
GNSS Global Navigation Satellite Systems
GPS Global Positioning System
GSM Global System for Mobile Communications
HTTP HyperText Transfer Protocol
HTTPS HTTP Secure
IE Information Element
IMSI International Mobile Station Identifier
INS Inertial Navigation Sensor
LCS Location Services
LOCSIP LOCation in SIP
LPP LTE Positioning Protocol
LPPe LTE Positioning Protocol Extensions
LSEP Location System External Protocol
LSIP Location System Internal Protocol
LTE Long-Term Evolution
MAC Master Auxiliary Corrections
MLP Mobile Location Protocol
MLS Mobile Location System
MS Mobile Station
MSID Mobile Station Identifier
NRTK Network RTK
OMA Open Mobile Alliance
OTDOA Observed Time Difference of Arrival
PPP Precise Point Positioning
PVT Position Velocity Time
QoS Quality of Service
RF Radio Frequency
RRC Radio Resource Control
RRLP Radio Resource Location services (LCS) Protocol
RT Real-Time
RTCM Radio Technical Commission for Maritime Services
RTK Real Time Kinematic
SET SUPL Enabled Terminal
SIP Session Initiation Protocol
SLP Server Location Provider
SMLC Serving Mobile Location Centre
SOAP Simple Object Access Protocol
SRN Short Range Node
SSL Secure Socket Layer
TCP/IP Transmission Control Protocol over Internet Protocol
TLS Transport Layer Security
UE User Equipment
ULP User-plane Location Protocol
UMTS Universal Mobile Telecommunications System
UTC Coordinated Universal Time
UTRA UMTS Terrestrial Radio Access
WLAN Wireless Local Area Network
XML Extensible Markup Language
4 Data Exchange Requirements
4.1 Context
The GBLS data that shall or may be exchanged is defined in ETSI TS 103 246-2 [2] in general terms for two main
mandatory cases and one optional case:
1) externally to applications using the GBLS (mandatory);
ETSI
10 ETSI TS 103 246-4 V1.2.1 (2017-03)
2) externally to external DGNSS service provider (optional, required when external DGNSS services are used as
defined in ETSI TS 103 246-2 [2]);
3) internally between modules of the GBLS (mandatory).
When the DGNSS service provision is an internal service, the GNSS differential data will be included in the data
exchanges of the type "internally between modules of the GBLS".
The specific requirements for this data are defined further in clauses 5, 6 and 7.
In addition, data exchange models are defined herein as a basis for protocols that may be used to transfer the GBLS
data.
Figure 4.1 shows these defined protocol models and their relevant interfaces applied to the GNSS-based Location
System (GBLS) and its functional entities as defined in ETSI TS 103 246-2 [2], within an end-to-end system.
NOTE: Throughout the present 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.
Data Exchange with Data Exchange with
external Service external Service
Provider Provider
EP DD EP DD
Target Positioning Module Central Facility
Position Calculation Module
On-Board
Sensor
Centralised
Central
Position
Management
Position
Management
Core Core
Calculation
LSIP
Calculation
Module
Interface Interface
(GNSS and other
Module
Module
Sensors)
LSIP LSIP
Core
Core
Interface
Interface LSIP LSIP
Application Interface
Application Interface
Module Module
L SEP L SEP
Data Exchange with Data Exchange with
Mandatory
Location-based Location-based
Optional
Application(s) Application(s)
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 (requesting
entity).
• LSIP (Location System Internal Protocol): between internal components of the GBLS.
• EPDD (External Protocol for Differential Data) as an optional protocol for differential GNSS data
exchanged with external Differential Service provider.
The two first protocols shall transfer the location-related data defined in ETSI TS 103 246-2 [2].
ETSI
11 ETSI TS 103 246-4 V1.2.1 (2017-03)
The third protocol is reserved for differential GNSS data transfer, if required, and therefore remains an option.
The Protocol definitions in clauses 4.2.1 to 4.2.4 address the following aspects:
1) protocol procedures;
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 do not cover:
• Message syntax. Thus no encoding scheme or data representation is given.
• Underlying transport mechanisms for the messages.
4.2 Protocol Choice and Compatibility
4.2.1 LSEP (MLP)
LSEP is based on the procedures, messages and elements of OMA MLP [4]. Annex A provides a rationale for this
choice.
MLP is intended for a Mobile Location Service (MLS) Client (e.g. a GBLS external application) to obtain the related
data of a location target (e.g. mobile terminal, GBLS Positioning Module, etc.) from a Location Server (e.g. the GBLS).
MLP is defined at the application layer of the protocol stack. Its messages are defined in XML and it is intended to be
transported over HTTP or other protocols (e.g. SOAP). For security reasons Secure Socket Layer (SSL) or Transport
Layer Security (TLS) cryptographic protocols can be used to carry HTTP (or HTTPS).
4.2.2 LSIP (LPPe)
4.2.2.1 General
LSIP is defined as an extension to LPP and relies also on the procedures, messages and elements of LPPe [5]. Annex A
provides a rationale for this choice.
As LPPe is also defined as an extension to, and relies on the main elements of, LPP [6] then LSIP is in effect based on
both of these protocols.
LPPe is intended to provide transactions for location-related data in a client-server model, and specifically between a
SET and SLP ("target" and "server" in LPPe). However LPPe allows many of its messages to be transacted in reversed
mode also.
In the GBLS, LSIP is defined for interfaces between all internal functional blocks. clause A.3 describes implementation
options.
LSIP as defined herein defines the global set of necessary location-related data required for the overall functioning of
the GBLS as defined in ETSI TS 103 246-2 [2].
In addition, when the GBLS requires to internally implement a differential GNSS service (either a local service with
one reference station or a network of service), some specific differential data encapsulated in the LSIP should be
considered.
4.2.2.2 LSIP Data Exchange Requirements
A summary of additional data for LSIP (i.e. not included in LPPe) requiring to be transferred over the GBLS interfaces
defined in ETSI TS 103 246-2 [2] is shown in table 4.1 (defined for each type of LSIP procedure: Location information
exchange and Assistance data exchange).
ETSI
12 ETSI TS 103 246-4 V1.2.1 (2017-03)
Table 4.1: Extension data for LSIP procedures
Interface Location information exchange Assistance or differential data exchange
LSIP-Specific data LSIP-Specific data
1 observables (Pseudo-range, Accumulated Doppler A-GNSS assistance data (models (nav, GGTO, UTC),
(GNSS) Range), RF samples, + error on PVT and RT integ, diff corr, data bit assist, acq assist, almanac,
observables. aux. info).
2 N/A. N/A.
(Telco)
3 Gyro/accelerometer measurements + error N/A.
(INS) estimates.
4 Magnetic field + error estimates. Temperature (for calibration).
(Magneto)
5 speed, distance, + error estimates. Wheel diameter.
(odom)
6 Body orientation, jammer characteristics: number, N/A.
(BFN) power, direction of arrival (DoA).
7 FFS. N/A.
(map)
8 location information consistent with "location-related N/A.
data" defined in LSEP:
• Position (horizontal, vertical), velocity
(linear/angular) acceleration (linear/angular),
heading.
• QoS estimation (estimated accuracy of the
above params).
• Integrity and Authentication parameters.
9 All location data identified on I/F 10. All assistance data from Assistance Server
D-GNSS differential data according to the D-GNSS
method.
10 All location-related data above from sensor All location data present an interfaces 1 to 8.
interfaces (1 to 6), and dedicated to central D-GNSS differential data according to the D-GNSS
processing (in centralized position calculation method and architecture.
module).
Additionally, any "processed" location information
from the On-Board position calculation Module, and
needing to be forwarded to the Central Facility.

For memory, the architecture level 3with the corresponding interfaces in ETSI TS 103 246-2 [2] is described as follow.
ETSI
13 ETSI TS 103 246-4 V1.2.1 (2017-03)

Figure 4.2: GBLS detailed architecture
Table 4.2 shows the data to be made available for GBLS external interface (i.e. for an application) and which should
therefore be consistent with LSEP data elements. The relevant source protocols and the LSIP extension IEs are also
shown.
ETSI
14 ETSI TS 103 246-4 V1.2.1 (2017-03)
Table 4.2: LSIP/LPP IEs for GBLS external interfaces (Application)
with applicable protocol extensions
Elementary information LSIP/LPP Data type Request Provide Protocol
Hybridised Location-related data (i.e. as final products)
Time LocInfo x x LPP
HorPos LocInfo x x LPP
VertPos LocInfo x x LPP
Velocity LocInfo x x LPP
Acceleration LocInfo x x LPPe
Heading LocInfo x x LPPe
Detected no. of jammers LocInfo x x LSIP
Jammer ID LocInfo x LSIP
Jammer Power LocInfo x x LSIP
Jammer DoA LocInfo x x LSIP
Hybrid type/Location source Locinfo x x LPPe
Hybridised QoS indicators (i.e. as final products)
Time unc LocInfo x x LPP
HorPos ConfLev LocInfo x x LPP
HorPos unc LocInfo x x LPP
HorPos qos class LocInfo x LSIP
HorPos unc not met LocInfo x LSIP
int. alert (HorPos) LocInfo x LSIP
Vertpos ConfLev LocInfo x x LPP
Vertpos unc LocInfo x x LPP
Vertpos qos class LocInfo x LPP
Vertpos unc not met LocInfo x LSIP
int. alert (Vertpos) LocInfo x LSIP
Authentication LocInfo x x LSIP
Velocity ConfLev LocInfo x x LSIP
Velocity unc LocInfo x x LPP
Velocity qos class LocInfo x LPP
Velocity unc not met LocInfo x LSIP
int. alert (Velocity) LocInfo x LSIP
Accel ConfLev LocInfo x x LSIP
Accel unc LocInfo x x LSIP
Accel unc not met LocInfo x LSIP
Heading ConfLev LocInfo x x LSIP
Heading ConfClass LocInfo x x LSIP
Heading unc LocInfo x LSIP
Heading qos class LocInfo x LSIP
Heading unc not met LocInfo x LSIP
int. alert (Heading) LocInfo x LSIP

Table 4.3 summarizes the LSIP/LPPe IEs for GBLS internal sensor interfaces, and identifies particularly the new IEs
needed in LSIP.
ETSI
15 ETSI TS 103 246-4 V1.2.1 (2017-03)
Table 4.3: LSIP/LPP IEs for GBLS internal sensor interfaces (with applicable protocol extensions)
LSIP/LPP Req Prov Prot
Elementary information Data type uest ide ocol
Control parameters; needed to implement the internal GBLS reporting scheme
Event trigger req LocInfo x LSIP
GNSS
GNSS RF samples LocInfo x x LSIP
GNSS measurements (timestamped pseudo range, carrier phase measurements,
Doppler, measurement Status, Loss of Lock indicator, C/N0) Locinfo x LSIP
Telco
OTDOA, EOTD, OTDOA-UTRA, LTE, LTE ECID, GSM ECID, UTRA ECID, WLAN, WiMax, SRN
Existing  LPPe
Internal INS data
Existing  LPPe
Magnetometer
Existing  LPPe
Odometer
Wheel size Locinfo x x LSIP
Travelled distance LocInfo x x LSIP
Speed LocInfo x x LSIP
BFN
maxNbrofjammers LocInfo x LSIP
detected no. of jammers LocInfo x LSIP
jammer ID LocInfo x LSIP
jammer Power LocInfo x x LSIP
jammer DoA LocInfo x x LSIP
Map
FFS x x LSIP
4.2.2.3 Additional LSIP IEs for GBLS using differential GNSS positioning methods
The present standard should consider a maximal compatibility with RTCM standards [7] and RTCM 10403.2 [8] and
should thus consider RTCM messages as new extension to the LPPe.
The RTCM message exchanges will essentially depends on the DGNSS methods and also with the architecture but
generalities can be put here:
• RTCM 10402.3 standard [7] is applicable for conventional D-GNSS positioning method, while RTCM
10403.2 standard [8] is applicable for RTK, NRTK and PPP differential positioning methods.
• In the case of a D-GNSS or RTK architecture, where the reference station can be considered as one unique
local infrastructure (possibly monitored by the integrity monitoring station), the reference station is the
provider of its corrections (conventional D-GNSS) or measurements (RTK) under RTCM messages format to
the localization module in charge of the location target positioning (either on board or in the central facility).
In parallel, the reference station provides its surveyed location, antenna features, etc. If this station is internally
operated, the central facility localization module should prepare and format the RTCM messages from the
reference sensor measurements and provides them to the localization module in charge of the location target
positioning (either on board or in the central facility).
• The rover GNSS sensor is the provider of its measurements and raw ephemeris to the localization module
(either on board or in the central facility).
• In the case of a network of reference stations (NRTK, PPP), the central management module is the provider of
the GNSS differential data under RTCM message format to the localization module in charge of the location
target positioning (either on board or in the central facility).
More details about IE are provided in clause 8.
ETSI
16 ETSI TS 103 246-4 V1.2.1 (2017-03)
4.2.3 EPDD (RTCM104)
In the particular case where GBLS shall take benefits from differential GNSS services as provided by external
differential service provider, to meet its requirements, the GBLS protocol EPDD should preferably conform to the
existing external GNSS service provider data protocols.
Since the existing GNSS service provider generally conform to the RTCM 104 standards, the GBLS EPDD should
directly meet the requirements of the RTCM 10402.3 standard [7] for the conventional DGNSS positioning method or
the RTCM 10403.2 standard [8] for the RTK, NRTK and PPP positioning methods.
The data exchanges will take place in the positioning module in GBLS (either embedded or central facility according to
the implementation).
This RTCM standard is mainly oriented so that the DGNSS service provider broadcast the required differential data,
and the main protocol will thus simply consists to receive the selected broadcast stream, corresponding to the service
subscription instructions. One exception exists for NRTK/VRS which foresees just a possibility for the subscriber to
send a message (containing its coarse location) towards the differential service provider in order for it to receive
dedicated data. More details about IE are provided in clause 9.
4.2.3 LSEP/MLP and LSIP/LPPe Terminology
Table 4.4 defines the correspondence between GBLS and 3GPP/OMA MLP/LPPe terminology.
Table 4.4: MLP/LPPe and LSEP/LSIP terminology relationships
MLP/LPPe LSEP/LSIP
Term Definition Term Definition
MS Mobile Station Location Target See definition in ETSI TS 103 246-2 [2]
Positioning Module
MSID MS identifier MSID Identifier for location targets
Mobile Owner of the MS who has subscribed Location Target user Optional and minor role in GBLS context.
subscriber to a communication service. Target of the location service is the Location
Target of the Location service Target, rather than its user
MLS Client The application, seen as a client of the Application See definition in ETSI TS 103 246-2 [2]
Mobile Location Service
LCS Client The application, seen as a client of the Application See definition in ETSI TS 103 246-2 [2]
Location Service
Loca
...