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

Satellite Earth Stations and Systems (SES); GNSS based location systems; Part 1: Functional requirements

RTS/SES-00406

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 1: Functional requirements

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

Reference
RTS/SES-00406
Keywords
functional, GNSS, location, navigation, receiver,
requirements, 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-1 V1.2.1 (2017-03)
Contents
Intellectual Property Rights . 4
Foreword . 4
Introduction . 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 8
4 Context description . 9
4.1 Location based applications requirements . 9
4.1.1 Reminder of ETSI TR 103 183 content . 9
4.1.2 Common requirements . 9
4.1.3 Specific requirements . 10
4.2 Generic location-based application use case . 12
4.3 GNSS-based location systems . 14
5 Functional requirements for GNSS-based Location system. 15
5.1 Functional requirements outline . 15
5.2 Mandatory requirements . 15
5.2.1 Positioning techniques . 15
5.2.2 Location-related data delivery . 15
5.2.3 Location system policies . 16
5.3 Requirements for optional features . 16
5.3.1 Positioning techniques . 16
5.3.2 Location-related data content . 16
5.3.3 Location-related data delivery . 17
5.4 GBLS Functional requirements summary . 17
Annex A (informative): Common positioning techniques . 19
A.1 GNSS methods . 19
A.2 Assisted-GNSS methods . 19
A.3 Differential GNSS methods . 20
A.3.1 General . 20
A.3.2 D-GNSS . 20
A.3.3 RTK . 21
A.3.4 NRTK . 22
A.3.5 PPP . 23
A.4 Mixing GNSS and telecommunication positioning techniques . 24
A.4.1 Proximity sensing . 24
A.4.2 Multilateration . 24
A.4.3 Triangulation . 26
A.5 Multi-sensor positioning through GNSS or Assisted/Differential GNSS hybridization . 26
Annex B (informative): GBLS High level functional analysis . 28
History . 29

ETSI
4 ETSI TS 103 246-1 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 1 of a multi-part deliverable covering the GNSS based location systems, 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".
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.
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.
ETSI
5 ETSI TS 103 246-1 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 GNSS Based Location
Systems (GBLS) addressing the same applications.
The requirements herein are intended to address the growing use of complex location systems required for the provision
of location-based applications particularly for the mass-market (refer to ETSI TR 103 183 [i.1]).
The present document defines the functional requirements applicable to location systems, based on a summary of types
of applications relying on location-related data provided by location systems.
The present document can be considered as the Stage 1 characterization of location systems according to the ITU/3GPP
approach [i.2].
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.
Not applicable.
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] Recommendation ITU-T I.130: "Method for the characterization of telecommunication services
supported by an ISDN and network capabilities of an ISDN".
[i.3] IS-GPS-200D: "Revision D, Navstar GPS Space Segment/Navigation User Interfaces".
[i.4] IS-GPS-705D: "Navstar GPS Space Segment/User Segment L5 Interfaces".
ETSI
6 ETSI TS 103 246-1 V1.2.1 (2017-03)
[i.5] IS-GPS-800D: "Navstar GPS Space Segment/User Segment L1C Interfaces".
[i.6] European GNSS (Galileo) Open Service: "Signal In Space Interface Control Document", Issue 1.1.
[i.7] "Global Navigation Satellite System GLONASS Interface Control Document", Version 5.1.
[i.8] DTFA01-96-C-00025: "Specification for the Wide Area Augmentation System (WAAS)", US
Department of Transportation, Federal Aviation Administration.
[i.9] RTCA DO-229D: "Minimum Operational Performance Standards for Global Positioning
System/Satellite-Based Augmentation System Airborne Equipment", SBAS ICD Annex 1.
[i.10] IS-QZSS: "Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS",
Version 1.0.
[i.11] BDS-SIS-ICD-B1I-1.0: "BeiDou Navigation Satellite System Signal In Space Interface Control
Document Open Service Signal B1I (Version 1.0)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document the following terms and definitions apply:
Accumulated Delta Range (ADR): another term for carrier phase measurement
authentication: provision of assurance that the location-related data associated with a location target has been derived
from real and not falsified signals
availability: percentage of time when a location system is able to provide the required location-related data
carrier phase measurement: measure of the range between the satellite and receiver expressed in units of cycles of the
carrier frequency
continuity: likelihood that the location system functionality will be available during the complete duration of the
intended operation if the system is operational at the beginning of the operation
D-GNSS: technique aiming at enhancing position accuracy and integrity of a GNSS receiver by using differential
pseudorange corrections and "do not use flag" for faulty satellites delivered by a GNSS reference station located at a
known location
NOTE: In the present document, the term D-GNSS refer to conventional differential GNSS.
electromagnetic interference: any source of RF transmission that is within the frequency band used by a
communication link, which degrades the performance of this link
fraud: any kind of activity of a location-based application stakeholder aiming at jeopardizing the application objective
GNSS-based location system (GBLS): location system using GNSS as the primary source of positioning
GNSS only receiver: location receiver using GNSS as the unique source of positioning
integrity: measure of the trust in the accuracy of the location-related data provided by the location system and the
ability to provide timely and valid warnings to users when the location system does not fulfil the condition for intended
operation
NOTE: Integrity is expressed through the computation of a protection level. The Integrity function is designed to
deliver a warning (or alert) of any malfunction to users within a given period of time (time-to-alert).
Related to the Integrity concept, a Loss of Integrity event occurs when an unsafe condition (i.e. a
positioning error higher than the protection level) occurs without a warning to the users for a time longer
than the time-to-alert limit.
ETSI
7 ETSI TS 103 246-1 V1.2.1 (2017-03)
jamming: deliberate transmission of interference in order to disrupt communications
NOTE: In the present technical context, targeted communication signals are GNSS or telecommunication signals.
latency: measure of the time elapsed between the event triggering the determination of the location-related data for a
location target and the availability of the location-related data at the user interface
location-based application: application which is able to deliver a service to one or several users, built on the
processing of the location information (location-related data) related to one or several targets
location-related data: set of data associated with a given location target, containing one or several of the following
time-tagged information elements: target position, target motion indicators (velocity and acceleration), quality of
service indicators (estimates of the position accuracy, reliability or authenticity)
location system: system responsible for providing to a location based application the location-related data of one or
several location targets
location target: physical entity (mobile or stationary) whose position is the focus of the location related data to be built
by the location system
Precise Point Positioning (PPP): differential GNSS technique that uses a worldwide distributed network of reference
stations to provide, in quasi real time, a highly accurate geodetic positioning of a receiver
privacy: function of a location system that aims at ensuring that the location target user private information (identity,
bank accounts, etc.) and its location-related data cannot be accessed by a non-authorized third party
Protection Level (PL): upper bound to the position error such that: P(ε > PL) < I , where I is the Integrity risk and
risk risk
ε is the actual position error
NOTE: The protection level is provided by the location system, and with the integrity risk, is one of the two sub-
features of the integrity system. The protection level is computed both in the vertical and in the horizontal
position domain and it is based on conservative assumptions that can be made on the properties of the
GNSS sensor measurements, i.e. the measurement error can be bounded by a statistical model and the
probability of multiple simultaneous measurement errors can be neglected.
pseudorange: pseudo distance between a satellite and a navigation receiver computed by multiplying the propagation
delay determined by the receiver with the speed of light
NOTE: The prefix "pseudo" highlights the fact that the propagation delay accessible to the receiver encompasses
contributions (such as receiver local clock offset with respect to satellite time) which do not allow it to
determine directly the actual geometrical distance.
Pseudo Range Correction (PRC): simple difference between a pseudorange measured by a GNSS reference station,
set at a known location and the estimated range between the satellite and this known location
NOTE 1: The estimated range generally uses the computed satellite clock bias correction and may use the estimated
receiver clock bias correction.
NOTE 2: The Pseudo Range Correction represents an estimate of the total GNSS systematic error observed on one
satellite line-of-sight, comprising ionospheric delay, tropospheric delay and orbito-synchro residual error.
It can be directly used in a local area around the reference station to cancel most of the systematic errors.
quality of service: set of indicators that can accompany the location target's position/motion information and is
intended to reflect the quality of the information provided by the location system
NOTE: QoS indicators can include an accuracy estimate, a protection level statistic, the integrity risk, an
authentication flag.
Real Time Kinematic (RTK): particular Differential GNSS technique that provides, in real time, highly accurate
positioning of a target based on carrier phase measurements
NOTE 1: In the RTK context, the target is called the "rover", as opposed to the stationary reference station(s). RTK
makes use of the carrier phase measurements, both in the reference station and in the rover, and this
technique allows the ambiguities affecting these accurate measurements to be resolved.
ETSI
8 ETSI TS 103 246-1 V1.2.1 (2017-03)
NOTE 2: If the reference station is at an accurately known location, the rover can compute its accurate geodetic (or
absolute) location. Alternatively, if the reference station's geodetic location is only roughly known, RTK
can still provide high accuracy, but only on a relative and not absolute basis.
reference receiver: receiver placed at a known and surveyed position used for differential GNSS technique
NOTE: A reference receiver is an essential component of a reference station.
reference station: station placed at a known and surveyed position aiming at determining and sharing the systematic
errors of at least one GNSS constellation
rover: target or location target, mainly used in the context of Differential GNSS/RTK
security: function of a location system that aims at ensuring that the location-related data is safeguarded against
unapproved disclosure or usage inside or outside the location system, and that it is also provided in a secure and reliable
manner that ensures it is neither lost nor corrupted
spoofing: transmission of signals intended to deceive location processing into reporting false target data
target: See location target.
terminal: target or location target, mainly used in the context of Assisted GNSS
terminal-assisted: mode in which the terminal performs only the GNSS measurements (pseudoranges, pseudo Doppler,
etc.) and sends these measurements to a remote central facility where the position calculation takes place
NOTE: This calculation may possibly use additional measurements or data from other sources (GNSS server
assistance, differential GNSS services or non GNSS sensors etc.).
terminal-based: mode in which the terminal performs the GNSS measurements and calculates its own location
NOTE: This calculation may possibly use additional measurements or data from other sources (GNSS server
assistance, differential GNSS services or non GNSS sensors etc.)
time-to-alert: time from when an unsafe integrity condition occurs to when an alerting message reaches the user
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3GPP 3 Generation Partnership Project
ADAS Advanced Driver Assistance Systems
ADR Accumulated Delta Range
ADS-B Automatic Dependent Surveillance – Broadcast
A-SMGCS Advanced Surface Movement Guidance and Control System
ATC Air Traffic Control
CID Cell-ID OTD
D-GNSS Differential GNSS
E-CID Enhanced Cell-ID
EGNOS European Geostationary Navigation Overlay System
E-OTD Enhanced Observed Time Different
FKP Flachen Korrektur Parameter (German)
GAGAN GPS-Aided Geo-Augmented Navigation
GBLS GNSS-Based Location Systems
GEO Geostationary Earth Orbit
GLONASS Global Navigation Satellite System (Russian based system)
GNSS Global Navigation Satellite System
GPS Global Positioning System
GSM Global System for Mobile communications
INS Inertial Navigation Sensor
IT Information Technology
ITS Intelligent Transport Systems
LAD-GNSS Local Area Differential GNSS
LTE Long Term Evolution
ETSI
9 ETSI TS 103 246-1 V1.2.1 (2017-03)
M&C Monitoring and Control
MAC Master Auxiliary Correction
MMI Man-Machine Interface
MNO Mobile Network Operator
MSAS Multi-functional Satellite Augmentation System
NRTK Network RTK
OBU On-Board Unit
OSR Observation State Representation
OTDOA Observed Time Difference Of Arrival
PAYD Pay As You Drive
PL Protection Level
PPP Precise Point Positioning
PRC Pseudo-Range Correction
PVT Position, Velocity and Time
QoS Quality of Service
QZSS Quasi-Zenith Satellite System
RF Radio Frequency
RTCA Radio Technical Commission for Aeronautics
RTK Real Time Kinematic
SBAS Satellite Based Augmentation System
SNR Signal to Noise Ratio
SSR Space State Representation
UDRE User Differential Range Errors
UHF Ultra High Frequency
UMTS Universal Mobile Telecommunications System
UTDOA Uplink Time Difference of Arrival
VHF Very High Frequency
VRS Virtual Reference Station
WAAS Wide Area Augmentation System
WAD-GNSS Wide Area Differential GNSS
4 Context description
4.1 Location based applications requirements
4.1.1 Reminder of ETSI TR 103 183 content
ETSI TR 103 183 [i.1] provides a thorough inventory of the location based applications which is used as a reference in
the present document. The present clause summarizes the classification work which was conducted in order to identify
those applications driving the requirements.
These requirements were organized into two separate categories:
• Basic requirements common to all location-based applications.
• Additional specific requirements, only required by certain applications.
Examples of location based applications are given in table 4-1 (clause 4.2).
4.1.2 Common requirements
Based on ETSI TR 103 183 [i.1], the following requirements were identified as shared by all location-based
applications:
• Services remain available over a predefined service area.
• Management of multiple end users:
- The application shall be used by one or multiple end users.
ETSI
10 ETSI TS 103 246-1 V1.2.1 (2017-03)
• Management of the location targets:
- The application shall be able to cope with one or multiple location targets.
- The application shall be able to cope with location target(s) distributed arbitrarily over a predefined
service area.
- The application shall be able to cope with location target(s) with a priori unknown location-related
data.
• Service policy: the application shall implement mechanisms allowing the enforcement of service policy such
as:
- Privacy protection policy to protect the location target user identity (where relevant).
- Data protection policy to control access to information identified as sensitive (through confidentiality,
authentication and integrity mechanisms).
4.1.3 Specific requirements
Application classes were established in ETSI TR 103 183 [i.1] by gathering location-based applications having the same
differentiating requirement (s). An inventory of these requirements is summarized below in order to list the
requirements specific to a subset of applications.
• Location Based Charging
The objective is to charge a user based on the reported position. The main requirements are:
- Reliability of check point crossing detection: there is a risk that the user reported position triggers a
charging event when it is actually in a position that should be free of charge.
This risk is generally required to be very low.
- The service availability: the percentage of cases when the user actual position has to trigger a charging
event but the system is not properly informed. The service unavailability can be due to either an
erroneous reported position, or to the unavailability of the location information itself.
This service unavailability is generally required to be low.
NOTE 1: This type of location-related requirement is required for road user charging (road), on-street parking fee
pricing (road), waterways and harbours charging (maritime/multimodal), home zone billing, regulated
fleets in urban areas, etc.
• "Pay As You Drive" (PAYD) charging
The objective is to charge a user based on the distance travelled (e.g. for pay-per-use insurance). The challenge
is quite similar to the previous group, except that the useful information is the distance travelled rather than the
position itself.
The main driver is the accuracy of the travelled trajectory or distance in order to optimize the fee
collection.
NOTE 2: This type of location-related requirement is required for pay-per-use insurance (road), car rental pricing
(road), taxi service pricing (road), freight tolling (road), car-pooling (road), pay-as-you-pollute (road),
energy charging (train).
• Cooperative basic geo-positioning
The objective is to recover the position of one or several assets or vehicles, remotely or locally. The main
drivers are generally:
- The reported position accuracy: as far as fleet management or personal navigation is concerned, the
main objective is to obtain an accurate position estimate.
The required accuracy highly depends on the application: tens of meters for personal road navigation and
vehicle fleet management, meters for pedestrian personal navigation and city sightseeing.
ETSI
11 ETSI TS 103 246-1 V1.2.1 (2017-03)
- The service availability: position availability might not be as important as for other application (see
location based charging applications), but for example it is a clear challenge in case of car positioning in
urban area where high masking or shadowing, tunnels, signal multipath effects etc. all clearly can
produce degraded availability.
NOTE 3: This type of location-related requirement is required for fleet/asset/resource management, personal
navigation (pedestrian, road, multi-modal, airport vehicle management by A-SMGCS), traffic travel info,
city sightseeing, etc.
• Non-cooperative geo-positioning
This class of application encompasses applications for which one or several stakeholders (target itself, target
user, external actor) have an interest in fooling the application enabler by intentionally altering the location
target position.
The driver for this application class is the ability to detect fraud, by determining the authenticity of the
location-related data.
NOTE 4: This type of location-related requirement is required for some cases of fleet management (car rental),
location of stolen car (road), electronic tagging device for prisoners (multi-modal).
• Reliable geo-positioning
The common requirement for this class of application is to obtain a reliable position estimate for security,
safety or legal reasons. Such applications are often referred to as "liability-critical applications".
The main driver here is the reliability of the applicable figure of merit, which is dependent on the ability to
monitor the positioning performance with a (usually) high confidence level. The required performance
metrics are typically the target position error (horizontal or vertical), trajectory error (along track, cross track)
or time synchronization error.
Each application has its own tolerance regarding positioning performance. Thus, a properly monitored
performance exceeding the application tolerance causes service unavailability. Therefore, the reported
position accuracy is also an important driver.
NOTE 5: Both "non-cooperative geo-positioning" and "reliable geo-positioning" above rely on an assessment of the
confidence associated with the target position-related data. They are however treated separately:
"Non-cooperative geo-positioning" class only faces intentional position alteration aiming at luring
the location based application. Any position uncertainty due to non-intentional origins (GNSS
signal interference, multipath) is not covered.
"Reliable geo-positioning" class however covers all sources of position alteration, in order to bring
confidence in both position authenticity and accuracy.
NOTE 6: This type of location-related requirement is required for livestock transport tracking and tracing,
dangerous and hazardous cargo tracking and tracing, special (high value, sensitive, dual-use) goods traffic
tracking, perishable goods/food tracking and tracing. Reliable geo-positioning is also a specific
requirement for airport vehicle management systems.
• (Reliable) Vehicle movement sensing
Some applications require, in addition to the terminal position and/or trajectory, information related to its
movement: speed, acceleration, heading, gyration, etc.
The main driver is the accuracy of the motion sensor indicators (e.g. monitor the speed of a vehicle).
In addition, the ability to monitor the positioning performance (here positioning refers to movement
sensing) with a (usually) high confidence level may also be required (e.g. for legal speed enforcement).
NOTE 7: This type of location-related requirement is required for:
Liability critical applications: legal speed enforcement (road), accident reconstruction (road),
vehicle control assistance (ADAS) + collision warning (road), cold movement detector (train),
traffic management systems (train).
ETSI
12 ETSI TS 103 246-1 V1.2.1 (2017-03)
Non-liability critical applications: eco-driving and carbon emissions foot- printing (road), traffic
congestion reporting (road), airport vehicle management systems (A-SMGCS).
4.2 Generic location-based application use case
Table 4-1 lists the description of the different cases of location-based application, all extracted from the inventory made
in ETSI TR 103 183 [i.1] and summarized in clause 4.1. The case of airport vehicle management has been added in
version 2 of the present document.

ETSI
13 ETSI TS 103 246-1 V1.2.1 (2017-03)
Table 4-1: Example of location-based applications
Application End user Location Location system Application(s) Added value service
Target(s)
Road charging State/ Road Users Fleet of On-Board Units, equipped with Billing server collecting OBU/vehicles Possibility to apply road charges
Ministries of Vehicles positioning module and communication positions and deriving billing information. with limited infrastructure (i.e. off
transport means, distributed over the targeted road motorways).
users.
Vehicle or pedestrian Vehicle driver or Vehicle or Positioning module (using GNSS, inertial and Navigation application, embedded with the Ability to provide to user its
navigation pedestrian pedestrian odometer measurements). positioning module in a navigation position, surrounding points of
terminal, providing guidance information to interest and travel directions.
driver/pedestrian.
Airport vehicles Airport ground Airport vehicles Fleet of vehicles and specific assets with OBU A-SMGCS with positioning-guidance-and Reliable, accurate positioning
management handling and specific implementing positioning module and control application for ATC controllers and and identification of vehicles
operators or ground assets communication means (this can be an ADS-B vehicles drivers. and assets with movement
Airport ground transceiver). Airport server and fleet management parameters (heading, speed).
traffic ATC systems operated by airport handling
controllers or operators.
Vehicle driver
Precision farming Farmers Farming Local or network RTK solution, composed of Harvest scheduling, Farming logistics optimization,
vehicles at least a reference station and one or several or farming vehicles automation. or 24/7 unmanned harvesting.
positioning modules installed on the targets.
Ride sharing Car sharing Shared cars Fleet of On-Board Units, equipped with Centralized Car sharing application Simple and efficient car sharing.
aficionados positioning module and communications collecting OBU positions and building
means, distributed over participating cars. appropriate scheduling.
Transaction Trading company Synchronizatio GNSS sensors replicating GNSS time for Stock exchange trading, using replicated Accurate synchronization of
synchronization n module synchronization across wide areas. GNSS time as the source of trade orders.
synchronization.
House-arrest Penitentiary Prisoner under Monitoring wristlet, reporting position when Central server collecting alarms reported Geo-fencing.
monitoring authorities house-arrest prisoner steps out of constrained area. by wristlets. House-arrest remote monitoring.
Cellular Mobile Network Potential Monitoring centre aggregating information Visualization in MNO operation room. Improvement of network
Communication Operator sources of from GNSS receivers positioned on the performance through
infrastructure interference network base stations. identification of interference
monitoring sources.
Race monitoring and Race competitor Race vehicles Fleet of terminals, equipped with positioning MMI offered to race competitors (distress Competitor position quasi real-
safety system and Race (car, trucks module and communication means, distributed call trigger) and Application offered to race time monitoring, distress call
coordinator and over the race vehicles and coordinator in headquarters, for monitoring enabler.
motorcycles) Central location server, achieving terminal purposes.
M&C.
ETSI
14 ETSI TS 103 246-1 V1.2.1 (2017-03)
4.3 GNSS-based location systems
The present document provides the functional requirements applicable to GNSS-Based Location Systems (GBLS).
GBLS are defined as Location Systems using GNSS as a primary source of positioning. Hence, a GBLS shall support at
least one of the GNSS methods listed in clause A.1.
Optionally, it may support one or several of the following common positioning methods:
• assisted GNSS, further described in clause A.2;
• differential GNSS, further described in clause A.3;
• Proximity sensing, further described in clause A.4.1;
• Multilateration, further described in clause A.4.2;
• Triangulation, further described in clause A.4.3;
• multi-sensor positioning through GNSS hybridization, further described in clause A.5;
As presented in figure 4-1, the GBLS is in charge of generating the location-related data upon which the application or
added value service is built.
The GBLS may support a wide range of application end-user profiles: in-field users, headquarter users, supervisors, etc.
in fixed or mobile usage conditions.
The picture does not preclude any communication network architecture supporting the different logical interfaces
identified.
Figure 4-1
ETSI
15 ETSI TS 103 246-1 V1.2.1 (2017-03)
5 Functional requirements for GNSS-based Location
system
5.1 Functional requirements outline
Clauses 5.2 and 5.3 provide the functional requirements applicable to the GBLS. These requirements are derived from
location based application requirements inventoried in clause 4.1.
An outline of the derivation strategy is given within this section, and summarized in annex B (mapping between
location based applications requirements (common and specific) and GBLS functional requirements).
NOTE: This derivation strategy, also called functional analysis, is given for information only, since it is outside
the scope of the GBLS Technical Specifications.
Functional requirements are organized as follows:
• A set of mandatory requirements, which provide the specification any GBLS shall comply with, regardless of
the type of application served. These requirements are derived from the location based applications common
requirements given in clause 4.1.1.
• A set of requirements for optional features, required for some of the targeted application classes. These
requirements are derived from the location based applications "specific requirements" given in clause 4.1.2.
For each requirement, an introduction is given to identify the requirement origin.
The requirement itself is then worded and highlighted using the present formatting.
5.2 Mandatory requirements
5.2.1 Positioning techniques
The following mandatory requirements are applicable to any GBLS.
In order to support the location based application requirement over a wide variety of potential service areas (in terms of
characteristics such as size, location, obstacle density), it is mandatory that GBLS uses a GNSS positioning technique as
the main source of location-related data. It indeed offers the best technical trade-off matching the service area coverage
requirement.
The GBLS shall provide location-related data containing at least the location-target geographical position,
expressed in an explicit coordinate reference system, and the timestamp this position was sampled at, expressed
in an explicit reference timescale.
The GBLS shall determine the location-related data of the location target(s) through the use of at least one of the
GNSS methods listed in clause A.1.
5.2.2 Location-related data delivery
The following mandatory requirements are applicable to any GBLS.
In order to support the application requirement to deliver services to end-users, it is expected that the GBLS is not only
able to deliver the location-related data through a dedicated interface to an external entity (i.e. the application module),
but also that the location-related data delivery can be monitored and controlled by this external entity.
The GBLS shall implement an external interface conveying location-related data, and allowing the monitoring
and control of the data provisioning.
Furthermore, in case where the application serves multiple end users, the supporting GBLS is expected to be able to
process the incoming positioning requests based on a priority criteria. This is required in order to cope with the situation
where several end users require the sending of simultaneous positioning requests to the GBLS.
ETSI
16 ETSI TS 103 246-1 V1.2.1 (2017-03)
The GBLS shall be able to handle the incoming positioning requests based on priority criteria.
...