ETSI TS 103 246-4 V1.1.1 (2016-01)

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

DTS/SES-00348

General Information

• Status: Published
• Publication Date: 28-Jan-2016
• Technical Committee: SES SCN - Satellite Communications and Navigation
• Current Stage: 12 - Completion
• Due Date: 29-Jan-2016
• Completion Date: 29-Jan-2016
• 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.1.1 (2016-01)

Reference
DTS/SES-00348
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
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:
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 2016.
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.1.1 (2016-01)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Data Exchange Requirements . 8
4.1 Context . 8
4.2 Protocol Choice and Compatibility . 9
4.2.1 LSEP (MLP) . 9
4.2.2 LSIP (LPPe) . 10
4.2.2.1 General . 10
4.2.2.2 LSIP Data Exchange Requirements . 10
4.2.3 LSEP/MLP and LSIP/LPPe Terminology . 12
5 LSEP Requirements . 13
5.1 LSEP Services and Procedures . 13
5.2 Extension of MLP for LSEP. 14
5.3 LSEP Data Exchange Message Definition . 14
6 LSIP Requirements . . 15
6.1 LSIP Services and Procedures . 15
6.2 Extension of LPPe/LPP for LSIP . 15
6.3 LSIP Data Exchange Message Definition . 16
6.3.1 General . 16
6.3.2 IE Extensions of LPP/LPPe for LSIP . 16
6.3.2.1 Message Extensions . 16
6.3.2.2 LPPe data type imports . 16
6.3.3 LSIP Extension Messages . 17
6.3.3.1 Request Assistance Data . 17
6.3.3.2 Provide Assistance Data . 17
6.3.3.3 Request Location Information . 17
6.3.3.4 Provide Location Information . 18
7 LSEP Element Definitions . 18
7.1 Overview . 18
7.2 LSEP Child Elements . 18
7.2.1 Identity elements . 18
7.2.2 Location elements . 18
7.2.3 Quality of Position elements . 20
7.3 LSEP Sub-Child Elements . 21
7.3.1 accel . 21
7.3.2 accel_conf_lev . 21
7.3.3 accel_unc . 21
7.3.4 accel_req . 21
7.3.5 auth_flag . 22
7.3.6 auth_req . 22
7.3.7 conf_class . 22
7.3.8 emidata_req. 22
7.3.9 h_acc . 23
ETSI
4 ETSI TS 103 246-4 V1.1.1 (2016-01)
7.3.10 h_acc_not_met . 23
7.3.11 h_conf_lev . 23
7.3.12 h_int_alert . 23
7.3.13 head_conf_lev . 23
7.3.14 head_req . 24
7.3.15 head_unc . 24
7.3.16 LSEP-msids . 24
7.3.17 v_acc . 24
7.3.18 v_acc_not_met . 24
7.3.19 v_conf_lev . 25
7.3.20 v_unc . 25
7.3.21 v_req . 25
7.3.22 vel_acc . 25
7.3.23 vel_acc_not_met . 25
7.3.24 vel_conf_lev . 26
7.3.25 vel_unc . 26
7.3.26 vel_req . 26
8 LSIP Information Elements . 26
8.1 LSIP Common Positioning IEs . 26
8.1.1 General . 26
8.1.2 LSIP-CommonIEsRequestLocationInformation . 26
8.1.3 LSIP-CommonIEsProvideLocationInformation . 28
8.2 LSIP Common Low-Level IEs . 30
8.2.1 General . 30
8.2.2 LSIP-ConfidenceLevels . 30
8.2.3 LSIP-ErrorMeasurements . 31
8.2.4 LSIP-QosIndicators . 31
8.3 Specific Positioning Method IEs . 31
8.3.1 General . 31
8.3.2 GNSS Positioning . 32
8.3.2.1 LSIP-GNSS-RequestLocationInformation . 32
8.3.2.2 LSIP-GNSS-ProvideLocationInformation . 32
8.3.3 Odometer positioning . 32
8.3.3.1 LSIP-Odometer-RequestAssistanceData . 32
8.3.3.2 LSIP-Odometer-ProvideAssistanceData . 33
8.3.3.3 LSIP-Odometer-RequestLocationInformation . 33
8.3.3.4 LSIP-Odometer-ProvideLocationInformation . 33
8.3.4 Beam Forming Network Positioning . 34
8.3.4.1 LSIP-BFN-RequestLocationInformation . 34
8.3.4.2 LSIP-BFN-ProvideLocationInformation. 34
8.3.4.3 LSIP-JammerSignal . 34
8.3.5 Mapping Positioning . 35
Annex A (informative): Rationale for LSEP/MLP and LSIP/LPPe . 36
A.1 Basis for LSEP/MLP . 36
A.2 Basis for LSIP/LPPe . 36
A.3 LSIP Implementation Cases . 36
A.4 LSIP Procedure examples for GBLS Interface 10 . 38
A.4.1 "Mobile-centric" Assistance data provisioning . 38
A.4.2 "Network-centric" Location Information provisioning . 39
Annex B (informative): Bibliography . 40
History . 41

ETSI
5 ETSI TS 103 246-4 V1.1.1 (2016-01)
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 below:
Part 1: Functional requirements;
Part 2: Reference Architecture;
Part 3: Performance requirements;
Part 4: Requirements for location data exchange protocols;
Part 5: Performance Test Specification.
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 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 ETSI TR 103 183 [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.
ETSI
6 ETSI TS 103 246-4 V1.1.1 (2016-01)
1 Scope
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 the
GNSS-based Location System (GBLS), as well as between the GBLS and external applications.
In particular, 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
reference document (including any amendments) applies.
Referenced documents which 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.
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.5: "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)".
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
reference 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".
ETSI
7 ETSI TS 103 246-4 V1.1.1 (2016-01)
[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
DoA Direction of Arrival
DTD Document Type Definition
ECID Enhanced Cell ID
EMI ElectroMagnetic Interference
EOTD Enhanced Observed Time Difference
EPDU Extension Protocol Data Unit
EPDU External Protocol Data Unit
E-SMLC Enhanced Mobile Location Centre
FFS For Further Study
GBLS GNSS Based Location System
GGTO GPS-Galileo Time Offset
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
MLP Mobile Location Protocol
MLS Mobile Location System
MS Mobile Station
MSID Mobile Station Identifier
OMA Open Mobile Alliance
OTDOA Observed Time Difference of Arrival
PVT Position Velocity Time
ETSI
8 ETSI TS 103 246-4 V1.1.1 (2016-01)
QoS Quality of Service
RF Radio Frequency
RRC Radio Resource Control
RRLP Radio Resource Location services (LCS) Protocol
RT Real-Time
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
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 clauses 5 and 6.
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.
ETSI
9 ETSI TS 103 246-4 V1.1.1 (2016-01)
GNSS-based Location System
Positioning Module
Central Facility
Central Management
Centralised
On-board
On-board Module
Localisation
Localisation
Localisation
Core Interface
GNSS & Sensor
Module
Sensor Core
Module
Module Assistance
other external Management
Management
Interface
Systems Server To
External
(GNSS and
(GNSS and
LSIP LSIP LSIP
Service
other Sensors)
other Sensors)
provider
LSIP
LSIP
Application Application
Interface Module
Interface Module
Key:
Mandatory LSEP LSEP
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.
These protocols shall transfer the location-related data defined in ETSI TS 103 246-2 [2].
The Protocol definitions in the following clauses address the following aspects:
1) protocol procedures;
3) message definitions from a semantic point of view i.e. the information they shall contain, and how this
information is structured;
4) 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).
ETSI
10 ETSI TS 103 246-4 V1.1.1 (2016-01)
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. Annex A3 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].
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).
Table 4.1: Extension data for LSIP procedures
Interface Location information exchange Assistance 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 identified on the sensors I/F
(1 to 7).
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
processing (in centralized localization module).
Additionally, any "processed" location information
from the On-Board Localization Module, and
needing to be forwarded to the Central Facility.
ETSI
11 ETSI TS 103 246-4 V1.1.1 (2016-01)
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.
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
12 ETSI TS 103 246-4 V1.1.1 (2016-01)
Table 4.3: LSIP/LPP IEs for GBLS internal sensor interfaces (with applicable protocol extensions)
Elementary information LSIP/LPP Data type Request Provide Protocol
Control parameters; needed to implement the internal GBLS reporting scheme
Event trigger req LocInfo x LSIP
GNSS
GNSS RF samples LocInfo x 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.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
Location The server which provides location GBLS Location The Server which provides location data of
Server data of the MS to the Client (normal Server the Location Target to the Application, and
mode) the assistance data to the Location target or
or LPPe client (reversed mode) Positioning Module
or LPPe client (reversed mode)
Target LPPe client (normal mode) Location Target See definition in ETSI TS 103 246-2 [2] or
(LPPe) or LPPe server (reversed mode) Positioning Module LPPe server (reversed mode)

ETSI
13 ETSI TS 103 246-4 V1.1.1 (2016-01)
5 LSEP Requirements
5.1 LSEP Services and Procedures
LSEP data transactions (i.e. between the GBLS and an external application) shall use the service schemes as defined for
MLP [4] including the messages as follows:
1) Standard Location Immediate Service consisting:
- Standard Location Immediate Request.
- Standard Location Immediate Answer.
- Standard Location Immediate Report.
2) Emergency Location Immediate Service:
- Emergency Location Immediate Request.
- Emergency Location Immediate Answer.
- Emergency Location Immediate Report.
3) Standard Location Reporting Service:
- Standard Location Report.
- Standard Location Report Answer.
4) Emergency Location Reporting Service.
- Emergency Location Report.
5) Triggered Location Reporting Service:
- 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.
6) Historic Location Immediate Service:
- Historic Location Immediate Request.
- Historic Location Immediate Answer.
- Historic Location Immediate Report.
LSEP services shall be identical to those in MLP, except: when an LSEP client (application) attempts to invoke a
service not defined in the present document, the GBLS shall return a General Error Message. The General Error
Message is equivalent to that described in MLP (see clause 5 of OMA-TS-MLP-V3.5 [4]).
The extension Elements (parameters) of MLP services for LSEP are defined in clause 6.3.
ETSI
14 ETSI TS 103 246-4 V1.1.1 (2016-01)
5.2 Extension of MLP for LSEP
The MLP specification has been designed with extensibility in mind. Design principles employed to achieve this
include:
• Separate DTDs for definitions that are common to all messages, e.g. client address and shapes, so they can be
re-used.
• A parameter (Element) extension mechanism allowing the addition of new parameters to existing messages.
This mechanism works by specifying an entity parameter, '%extension;', referring to an extension DTD. The
extension DTD shall contain another entity parameter, '%extension.param', containing the definition of the
extension as a string together with the actual messages being added.
In order to use the extension, the extension DTD shall be explicitly referenced in the XML document.
Duplication of information sent in MLP Request messages using LSEP should be avoided by external entities.
LSEP messages shall take precedence over any contradictory information (from MLP) received by the GBLS.
The GBLS shall avoid sending any contradictory information via LSEP and MLP messages in an MLP Answer or
Report.
NOTE: To make LSEP more universally accepted may require a new version of MLP to be defined incorporating
LSEP extensions.
5.3 LSEP Data Exchange Message Definition
The LSEP Element (parameter) extensions to MLP messages are shown in table 5.1.
Table 5.1: LSEP Element extensions for MLP messages
MLP Message LSEP parameter extensions
Standard Location Immediate Request LSEP_msids
LSEP_eqop
LSEP_req_info
Standard Location Immediate Answer LSEP_pd
Standard Location Immediate Report LSEP_pd
Emergency Location Immediate Request LSEP_eqop
Triggered Location Reporting Request LSEP_msids
LSEP_qop
LSEP_req_info
Triggered Location Report LSEP_pd
Triggered Location Reporting Stop Request LSEP_msids
Triggered Location Reporting Stop Answer LSEP_msids
Historic Location Immediate Request LSEP_qop

For definition of these elements see clause 7.
LSEP messages shall take precedence over any contradictory information (e.g. from MLP) received by the GBLS.
Duplication of information sent in MLP-based messages using LSEP shall be avoided by the GBLS and should be
avoided by external entities.
ETSI
15 ETSI TS 103 246-4 V1.1.1 (2016-01)
6 LSIP Requirements
6.1 LSIP Services and Procedures
LSIP data transactions (i.e. between internal modules of the GBLS) shall use the service schemes as defined for LPPem,
see OMA-TS-LPPe [5] as follows:
1) LPP Provide/Request Capabilities (plus LPPe reversed mode).
2) LPP Provide/Request Assistance Data.
3) LPP Provide/Request Location Information (plus LPPe reversed mode).
4) LPP Abort.
5) LPP Error.
6) LPPe Periodic/Triggered Assistance Data Transfer with Update.
7) LPPe Periodic/Triggered Location Information Transfer with Update.
8) LPPe Segmented Assistance Data Transfer.
9) LPPe Segmented Location Information Transfer.
10) LPPe Broadcast of Assistance Data.
11) LPPe Crowdsourcing.
LSIP services shall be identical to those defined for LPPe. However the Information Elements of these services will be
extended for the GBLS as defined in clauses 6.2 and 6.3.
6.2 Extension of LPPe/LPP for LSIP
LSIP (and LPPe) makes use of the option included in LPP messages to define extensions to these messages by means of
the EPDU container. Within this EPDU, the Identifier may be defined as follows:
• EPDU-ID:   2
• EPDU Defining entity ETSI Technical Committee SES
• Method name  GBLS LSIP
• Reference   LSIP
NOTE 1: This EPDU will need to be submitted to 3GPP.
LSIP specifies an extension to the LPP Provide/Request Assistance Data and Location Information messages above.
LSIP messages shall take precedence over any contradictory information (e.g. from LPPe/LPP) received by the GBLS.
LSIP extensions are defined to include LPPe extensions. Duplication of information sent in LPP-based messages using
LPPe and LSIP shall be avoided by the GBLS and should be avoided by external entities. When encoding the
LSIP/LPP/LPPe message, the LSIP extension for the message shall be parsed first, and LPPe extensions secondly, and
the resulting ASN.1-coded binary stream included in the EPDU-Body of the EPDU in the appropriate message.
NOTE 2: To make LSIP more universally accepted may require a new LPP (or LPPe) version to be defined
combining LSIP and LPPe extensions.
ETSI
16 ETSI TS 103 246-4 V1.1.1 (2016-01)
6.3 LSIP Data Exchange Message Definition
6.3.1 General
LSIP re-uses the message and data definitions from LPP/LPPe. In addition the contents of each LSIP IE extension to
LPP messages are specified in clauses 6.3.2 and 6.3.3, using ASN.1 to specify the syntax and using tables, when
needed, to provide information on the fields and parameters in the message. The information elements carried within the
message extensions are specified as IE's in clause 8.
NOTE: Where the IEs of LSIP messages are optional, only the IEs needed may be issued.
6.3.2 IE Extensions of LPP/LPPe for LSIP
6.3.2.1 Me
...