docbox.etsi.org€¦ · Web viewCold or Factory: The receiver is missing, or has inaccurate estimates of, its position, velocity, the time, or the visibility of any of the GPS satellites

TS 103 246 V0.1.21 (2014-065)

Satellite Earth Stations and Systems (SES); Global Navigation Satellite System (GNSS)-

based location systems; GNSS Location System Performance Requirements

<

TECHNICAL SPECIFICATIONTECHNICAL SPECIFICATION

ReferenceDTR/SES-00332

KeywordsGNSS, location, navigation, performance,

parameters, satellite, system, terminal

ETSI

650 Route des LuciolesF-06921 Sophia Antipolis Cedex - FRANCE

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

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

Important notice

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

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

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

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

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

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

Copyright Notification

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

© European Telecommunications Standards Institute yyyy.All rights reserved.

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

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

Important notice

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

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

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

ETSI

TS 103 246 V0.1.2 (2014-06)2

http://www.etsi.org/


http://www.etsi.org/

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


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

Copyright Notification

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

© European Telecommunications Standards Institute yyyy.All rights reserved.

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

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

ETSI

TS 103 246 V0.1.2 (2014-06)3


ContentsIntellectual Property Rights .................................................................................................................................6

Foreword .............................................................................................................................................................6

Introduction .........................................................................................................................................................6

1 Scope .........................................................................................................................................................7

2 References .................................................................................................................................................82.1 Normative references ...........................................................................................................................................82.2 Informative references .........................................................................................................................................8

3 Definitions, symbols and abbreviations ..................................................................................................103.1 Definitions .........................................................................................................................................................103.2 Symbols .............................................................................................................................................................113.3 Abbreviations .....................................................................................................................................................11

4 Location System Performance Features .................................................................................................144.1 General ...............................................................................................................................................................144.2 Horizontal Position Accuracy ............................................................................................................................144.3 Vertical Position Accuracy ................................................................................................................................144.4 Availability of Required Accuracy ....................................................................................................................144.5 GNSS Time Accuracy .......................................................................................................................................144.6 Time-to-First-Fix (TTFF) ..................................................................................................................................154.7 Position Authenticity .........................................................................................................................................154.8 EMI Localisation Accuracy ...............................................................................................................................154.9 Robustness to Interference .................................................................................................................................164.10 GNSS-Denied Accuracy ....................................................................................................................................164.11 GNSS Sensitivity ...............................................................................................................................................164.12 Position Integrity Protection Level ....................................................................................................................164.13 Position Integrity Time-to-Alert (TTA) .............................................................................................................164.14 Position Integrity Time-to-Recover-from-Alert) ...............................................................................................17

5 Performance Requirements .....................................................................................................................185.1 Horizontal Position Accuracy ............................................................................................................................185.1.1 Operational conditions .................................................................................................................................185.1.2 Use case: Moving Location Target ..........................................................................................................19185.1.2.1 Target movement ................................................................................................................................19185.1.2.2 Performance requirement .......................................................................................................................195.1.3 Use case: Static Location Target ..................................................................................................................215.1.3.1 Target position ........................................................................................................................................215.1.3.2 Performance requirement ...................................................................................................................22215.2 Vertical Position Accuracy ............................................................................................................................23225.2.1 Operational conditions .............................................................................................................................23225.2.2 Use case: Moving Location Target ..............................................................................................................235.2.2.1 Target movement ....................................................................................................................................235.2.2.2 Performance requirement ...................................................................................................................24235.2.3 Use case: Static Location Target ..............................................................................................................25245.2.3.1 Target position ....................................................................................................................................25245.2.3.2 Performance requirement ...................................................................................................................25245.3 Availability of Required Accuracy ................................................................................................................26255.4 GNSS Time Accuracy .......................................................................................................................................265.4.1 Operational conditions .................................................................................................................................265.4.2 Use case: Moving Target .........................................................................................................................27265.4.2.1 Target movement ................................................................................................................................27265.4.2.2 Performance requirement ...................................................................................................................27265.4.3 Use case: Static Target .............................................................................................................................28275.4.3.1 Target position ....................................................................................................................................28275.4.3.2 Performance requirement ...................................................................................................................28275.5 Time-to-First-Fix (TTFF) ..............................................................................................................................2928

ETSI

TS 103 246 V0.1.2 (2014-06)4

5.5.1 Operational conditions .............................................................................................................................29285.5.2 Use case: Moving Target .........................................................................................................................30295.5.2.1 Target movement ................................................................................................................................30295.5.2.2 Performance requirement ...................................................................................................................30295.5.3 Use case: Static Target .............................................................................................................................33315.5.3.1 Target position ....................................................................................................................................33315.5.3.2 Performance requirement ...................................................................................................................33315.6 Position Authenticity .....................................................................................................................................35345.6.1 Operational conditions .............................................................................................................................36355.6.2 Use case: Moving location target, fault free scenario ..............................................................................36355.6.2.1 Target movement ................................................................................................................................36355.6.2.2 Performance requirement ...................................................................................................................36355.6.3 Use case: Moving location target, faulty scenarios ......................................................................................365.6.3.1 Target movement ....................................................................................................................................365.6.3.2 Performance requirement ...................................................................................................................37365.6.4 Use case: Static Location Target Fault-free scenario ...............................................................................37395.6.4.1 Target position ....................................................................................................................................37395.6.4.2 Performance requirement ...................................................................................................................37395.6.5 Use case: Static Location Target Faulty scenarios ...................................................................................38405.6.5.1 Target position ....................................................................................................................................38405.6.5.2 Performance requirement ...................................................................................................................38405.7 EMI Localisation Accuracy ...........................................................................................................................38435.8 Robustness to Interference .............................................................................................................................38435.9 GNSS-Denied Accuracy ................................................................................................................................39445.9.1 Operational conditions .............................................................................................................................39445.9.1.1 Special masking conditions ................................................................................................................39445.9.2 Use case: Moving Target .........................................................................................................................40455.9.2.1 Target movement ................................................................................................................................40455.9.2.2 Performance requirement ...................................................................................................................40455.10 GNSS Sensitivity ...........................................................................................................................................42475.10.1 Operational conditions .............................................................................................................................42475.10.1.1 Special masking conditions ................................................................................................................43485.10.1.2 GNSS time initial estimate .................................................................................................................43485.10.2 Use case: Moving Target .........................................................................................................................43485.10.2.1 Target movement ................................................................................................................................43485.10.2.2 Performance requirement ...................................................................................................................43485.10.3 Use case: Static Target .............................................................................................................................44495.10.3.1 Target Position ...................................................................................................................................44495.10.3.2 Performance requirement ...................................................................................................................44495.11 Position Integrity Protection Level ................................................................................................................44495.12 Position Integrity Alarm Limit and TTA .......................................................................................................4449

Annex A (normative): Definition of Performance Metrics .....................................................4650A.1 Horizontal Position Accuracy ........................................................................................................................4650A.2 Vertical position accuracy .............................................................................................................................4650A.3 Availability of required accuracy ..................................................................................................................4751A.4 GNSS Time Accuracy ...................................................................................................................................4751A.5 Time-to-first-fix (TTFF) ................................................................................................................................4751A.6 Position Authenticity .....................................................................................................................................4852A.7 Direction of Arrival (DoA) Accuracy ...........................................................................................................4852A.8 PVT Degradation under interference sources ................................................................................................4852A.9 Recovery time of normal performance after termination of interference ......................................................4852A.10 GNSS sensitivity ............................................................................................................................................4852A.11 Position Integrity Protection Level ................................................................................................................4852

Annex B (normative): Applicable conditions .........................................................................5054B.1 General ...........................................................................................................................................................5054B.1.1 GNSS systems parameters .......................................................................................................................5054B.1.1.1 Systems constellation geometry and signal parameters .....................................................................5054B.1.1.2 GNSS System Time Offsets ...............................................................................................................5054B.1.2 SBAS systems parameters .......................................................................................................................5054B.1.3 Cellular systems parameters .....................................................................................................................5054

ETSI

TS 103 246 V0.1.2 (2014-06)5

B.2 Operational environments ..............................................................................................................................5155B.2.1 GNSS-related environment characteristics ..............................................................................................5155B.2.1.1 Sky Attenuation Conditions ...............................................................................................................5256B.2.1.2 Multipath ............................................................................................................................................5559B.2.1.3 Electro-magnetic Interference ............................................................................................................5660B.2.2 Additional environment characteristics ...................................................................................................5761B.2.2.1 Telecommunication beacon deployment ............................................................................................5761B.2.2.2 Interference source definition .............................................................................................................5862B.2.2.3 Magnetic conditions ...........................................................................................................................5862B.2.3 Operational environments definition .......................................................................................................5862B.3 Moving Target Scenario ................................................................................................................................5963

Annex C (normative): Threat Scenarios for Authenticity and Integrity Features ....................6064C.1 Authenticity Threat Scenarios .......................................................................................................................6064C.1.1 Threat scenarios .......................................................................................................................................6064C.1.1.1 Scenario pre-conditions ......................................................................................................................6064C.1.1.2 Scenarios chronology .........................................................................................................................6064C.1.1.3 Scenario parameters ...........................................................................................................................6064C.1.2 Threat scenarios for moving targets .........................................................................................................6367C.1.3 Threat scenarios for static targets .............................................................................................................6467C.2 Integrity threat scenarios ................................................................................................................................6468

Annex D (informative): Bibliography .....................................................................................6568

History ...........................................................................................................................................................6568

ETSI

TS 103 246 V0.1.2 (2014-06)6

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

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPR’s 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.

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

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

The wide spectrum of technical features identified in Error: Reference source not found calls for a new and broader concept for location systems, taking into account hybrid solutions in which GNSS technologies are complemented with other technology sensors to improve robustness and the performance.

Hence a set of standards for GNSS-based Location systems is defined as follows, of which the present document is part 3:

Part 1: ETSI TS 103 349: GNSS-based location systems; Functional requirements Error: Reference source not found

Part 2: ETSI TS 103 247: GNSS Location Systems Reference Architecture

Part 3: ETSI TS 103 246: GNSS Location System Performance RequirementsError: Reference source not found

Part 4: ETSI TS 103 248: Requirements for Location Data Exchange Protocols [i.2]

Part 5: ETSI TS 103 249: Test Specification for System Performance Metrics [i.3].

ETSI

TS 103 246 V0.1.2 (2014-06)7

1 ScopeThe present document addresses integrated location systems that combine Global Navigation Satellite Systems (GNSS), with other navigation technologies, as well as with telecommunication networks in order to enable location-based service delivery to users.

The requirements herein are intended to address the growing use of complex Location Systems needed for the expansion of location-based applications particularly for the mass-market. These types of application were identified in Error: Reference source not found.

This document first defines the type of Performance Features forexpected from Location Systems. These features are the key performance characteristics of the data service provided by the Location System to an external application module. It then defines the minimum performance requirements for these Performance Featureapplicable tos the location system.

The location system aims at providing location-related data for one or more targets operating in a range of environments.

The content of this document is based on the Location System reference architecture defined in Error: Reference source not found

ETSI

TS 103 246 V0.1.2 (2014-06)8

2 ReferencesReferences 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 http://docbox.etsi.org/Reference.

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

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

[1] Galileo OS Signal in Space ICD (OS SIS ICD), Draft 0, Galileo Joint Undertaking, May 23rd, 2006.

[2] IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006.

[3] IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, September 22, 2005.

[4] IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, September 4, 2008.

[5] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS.

[6] Global Navigation Satellite System GLONASS Interface Control Document.

[7] RTCA DO-229C. “Minimum Operational Performance Standards for Global Positioning System/Wide Area Augmentation System Airborne Equipment”. The Radio Technical Commission for Aeronautics. November 2001

[8] ETSI TS 103 247 "Satellite Earth Stations and Systems (SES); Global Navigation Satellite System (GNSS) based location systems; Reference Architecture”

[9][[8]] ETSI TS 103 349 “Satellite Earth Stations and Systems (SES); Global Navigation Satellite Systems (GNSS)-based location systems; Functional requirements”.

2.2

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

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

[i.2] ETSI TS 103 248: "Satellite Earth Stations and Systems (SES); GNSS based location systems; Requirements for the Location Data Exchange Protocols”

[i.3] ETSI TS 103 249: "Satellite Earth Stations and Systems (SES); GNSS based location systems; Test Specification for System Performance Metrics.”

[i.4] IEEE 802.11 for WiFi

[i.5] IEEE 802.15 for Wireless Personal Area Network (short range wireless)

[i.6] IEEE 802.15.1 for Bluetooth

[i.7] IEEE 802.15.4a for low rate WPAN

ETSI

TS 103 246 V0.1.2 (2014-06)9

http://docbox.etsi.org/Reference

[i.8] 3GPP TSXX;XXX for 2G



[i.11] [FFS] for 5G

3

ETSI

TS 103 246 V0.1.2 (2014-06)10

[3] Definitions, symbols and abbreviations3.1 DefinitionsThe following terms and definitions apply:

RJM: all to be reviewed below

Application module: entity in charge of retrieving from a Location system the Location-related data associated to one or more location targets and processing it in order to deliver to the application user the location based service it has been designed for.

NOTE: The application module can be located inside or outside a terminal.

Authentication: Authentication is the provision of assurance that the location-related data associated with a location target has been derived from real signals associated with the location target. By extension, authentication is one of the key performance features that can be required to a location system

Architecture: abstract representation of a communications system, in this case

NOTE: Three complementary types of architecture are defined:

Functionalrepresenting Architecture: the discrete functional elements of the system and the associated logical interfaces.

Physical (Network) Architecture: the discrete physical (network) elements of the system and the associated physical interfaces.

Protocol Architecture: the protocol stacks involved in the operation of the system and the associated peering relationships.

Availability: Availability measures percentage of time when a location system is able to provide the required location-related data. Note that the required location-related data might vary between location based applications. It may not only contain a required type of information (e.g. position and speed), but also a required quality of service (e.g. accuracy, protection level, authenticationauthenticity).

Class A:

Class B:

Class C:

Continuity: Likelihood that the navigation signal-in-space supports accuracy and integrity requirements for duration of intended operation. It guarantees that a user can start an operation during a given exposure period without an interruption of this operation and assuming that the service was available at beginning of the operation. Related to the Continuity concept, a Loss of Continuity occurs when the user is forced to abort an operation during a specified time interval after it has begun (the system predicts service was available at start of operation).

Continuity Risk is the probability of detected but unscheduled navigation interruption after initiation of an operation.

Electromagnetic Interference: Any source of RF transmission that is within the frequency band used by a communication link, and thatwhich degrades the performance of this link. Jamming is a particular case of electromagnetic interference, where an interfering radio signal is deliberately broadcast to disrupt the communicationcommunication.

Integrity: Integrity is a function of a location system that measures of the the trust that can be placed in the accuracy of the location-related data provided by the location system. In the present technical context, iIt is expressed through the computation of a protection level. The Integrity function includes the ability of the location system to provide timely and valid warnings to users when the system must not be used for the intended operation. Specifically, a location system is required to deliver a warning (an alert) of any malfunction (as a result of a set alert limit being exceeded) to users

ETSI

TS 103 246 V0.1.2 (2014-06)11

within a given period of time (time-to-alert). Related to the Integrity concept, a Loss of Integrity event occurs when an unsafe condition occurs without annunciation for a time longer than the time-to-alert limit. Integrity risk: the probability (per operation or per unit of time) that the system generates an unacceptable error without also providing a timely warning that the system’s outputs cannot be trusted.

The integrity risk is the probability that the actual error of the location-related data is larger than the protection level, in case of system availability (i.e. protection level lower than the alert limit).

Jamming: The deliberate transmission of interference to disrupt processing reception of wanted signals, which in this case are GNSS or telecommunication signals. N.B. Spoofing is considered to be a deceptive form of jamming.

Latency: The latency of a location system measures the time elapsed between the event triggering the determination of the location-related data for (a) location target(s) (i.e. location request from external client, external or internal event triggering location reporting), and the availability of the location-related data at the user interface.

Location-based application: An application that is able to deliver a location-based service to one or several users.

Location-based service: A service built on the processing of the Location-related data associated with one or several location targets

Location-related data: A set of data associated with a given location target, containing at least one or several of the following time-tagged information elements: target position, target motion indicators (velocity and acceleration), and Quality of Sservice indicators (estimates of the position accuracy, reliability or authenticity).

NOTE: This dataIt is the main output of a Location system.

Location system: The system responsible for providing to a location based application the Location-related data of one or several location targets.

Location system central facility: The centralized logical entity, inside a Location system, that manages the communication of the location-related data to the application module, which is the location system external client.

Location target: The physical entity on whose position the location system builds the location-related data, and with which the positioning module is attached. This entity may be mobile or stationary.

Positioning module: The logical entity inside a Location System providing the relevant measurements to the location system central facility (enabling it to determine the target’s location-related data) or directly providing the location target location-related data to the Application module. It is composed of a GNSS receiver and possibly additional sensors.

NOTE: The positioning module executes the measurements needed to determine its position, and implements part of the location determination functions. It embeds the group of sensors needed to execute these tasks. This group can include navigation sensors (GNSS, terrestrial beacons, Inertial, Odometers, etc.) It might be co-located with the location target or not.

Privacy: privacy is a 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 authorizised third party.

Protection level: the radius of a circle with its centre at the true location target position, which describes the limit of the error of the position data in the plane. In other words, The protection level (PL) is athe n upper bound to the position error such that: P(> PL) < Irisk, where Irisk is the Integrity risk and is the actual position error. 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.

Quality of service: The quality of service associated with a location-based service is a 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. QoS indicators can be an accuracy estimate, a protection level statistic, integrity risk, authenticationauthenticity flag.

Security: security is a 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.

ETSI

TS 103 246 V0.1.2 (2014-06)12

Spoofing: the transmission of signals intended to deceive location processing into reporting false target data (otherwise known as structural interference) e.g. meaconing.

radio interference intending to make a receiver produce false outputs

Time-to-alert: Time-to-alert is the time from when an unsafe integrity condition occurs to when an alerting message reaches the user

Time-to-first-fix: Time-To-First-Fix refers to the time needed by the receiver to perform the first position and time fix whose accuracy is lower than a defined accuracy limit, starting from the moment it is switched on.Vertical axis: axis locally defined for the location target, collinear to the zenith/nadir axis.

3.2 SymbolsFor the purposes of the present document, the following symbols apply:

Carrier phaseεAccel Error on sensor acceleration (from INS)εAtt Error on sensor attitude (from INS)εGyro Error on sensor gyroscopes (from INS)εPos Error on sensor position (from INS)εPos3D Uncertainty on sensor position (from GNSS)εV Error on sensor attitude (from INS)εV3D Uncertainty on sensor speed (from GNSS)d Carrier DopplerPGNSS Position estimate coming from GNSS sensorPINS Position estimate coming from the INSVGNSS Speed estimate coming from GNSS sensorVINS Speed estimate coming from the INS

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

All below to be reviewed

3GPP 3rd Generation Partnership ProjectADAS Advanced Driver Assistance SystemsA-GNSS Assisted GNSSAL Alarm LimitBTS Base station Transceiver SystemD-GNSS Dynamic GNSS DoOA Direction of ArrivalECEF Earth Centred, Earth FixedEDGE Enhanced Data for GSM EvolutionEGNOS European Geostationary Navigation Overlay SystemEMI Electro-Magnetic InterferenceFDAF Frequency Domain Adaptive FilteringFFS For Further StudyGCF Global Certification ForumGEO Geostationary Earth OrbitGIVE Grid Ionospheric Vertical ErrorGLONASS Global Navigation Satellite System (Russian based system)GNSS Global Navigation Satellite SystemGPRS General Packet Radio ServiceGPS Global Positioning SystemGSM Global System for Mobile communicationsHDOP Horizontal Dilution of PrecisionHPE Horizontal Positioning ErrorHPL Horizontal Protection Level

ETSI

TS 103 246 V0.1.2 (2014-06)13

IMU Inertial Measurement UnitINS Inertial Navigation Sensor IRS Inertial Reference SystemITS Intelligent Transport SystemsLCS LoCation ServicesLEO Low Earth OrbitLOS Line Of SightLTE Long-Term EvolutionMEMS Micro Electro-Mechanical SystemsMEXSAT Mexican Satellite SystemMI Mis-IntegrityMMI Man-Machine InterfaceMOPS Minimum Operational Performance SpecificationMP MultipathMPS Minimum Performance StandardMS Mobile StationNCO Numerically Controlled OscillatorNMR Network Measurement ResultsODTS Orbit Determination and Time SynchronisationOMA Open Mobile AllianceOTDOA Observed Time Difference of ArrivalPAYD Pay As You DrivePE Positioning ErrorPL Protection LevelPRN Pseudo-Random NoisePRS Public Regulated ServicesPVT Position, Velocity and TimePPP Precise Point PositioningQoS Quality of ServiceQZSS Quasi-Zenith Satellite SystemRAIM Receiver Autonomous Integrity MonitoringRF Radio FrequencyRMS Root Mean SquareRTCA Radio Technical Commission for AeronauticsRTK Real Time KinematicSBAS Satellite Based Augmentation SystemSCN Satellite Communications and Navigation (Working Group of TC-SES)SMLC Serving Mobile Location CentreSUPL Secure User Plane for LocationSV Satellite VehicleTBC To Be ConfirmedTBD To Be DefinedTC-SES Technical Committee Satellite Earth Stations and SystemsTSP Total Spoofing PowerTTA Time to AlarmTTFF Time-to-first-fixUDRE User Differential Range ErrorUERE User Equivalent Range ErrorUHF Ultra-High FrequencyUMTS Universal Mobile Telecommunications SystemVPL Vertical Protection LevelWAAS Wide Area Augmentation SystemWI-FI Wireless Fidelity

ETSI

TS 103 246 V0.1.2 (2014-06)14

4 Location System Performance Features4.1 GeneralA preliminary characterisation of location-based services is provided in Error: Reference source not found. These location-based services rely on Location Systems to collect location-related data for the location target.

In order to achieve the required level of service, some key characteristics are required from the informationThe location-related data delivered by GNSS-based the Location Ssystems is required to meet a number of requirements, in particularly in terms of regarding positioning performance. In thise present document, these requirements key performance characteristics are referred to as “Location System “Performance Features”.

These features are derived from the system performance requirements defined in [9].

These performance features, introduced in Error: Reference source not found, are general attributes and are describedfined in the sub-clausessection below. . Clause Error: Reference source not found then defines the requirements for each feature in terms of an associated set of performance metrics (i.e. measurement parameters) defines provides the performance values for these metrics and the conditions in which they applyto which the Location System shall comply in order to contribute to the location-based service.

Each metric for a Performance Feature is defined in sequence in Annex A as follows:

Performance Feature Performance Metrics Scenarios1) Horizontal Position Accuracy: A.12) Vertical Position Accuracy A.23) Availability of Required Accuracy A.34) G NSS Time Accuracy A.45) Time-to-first-fix A.56) Position Authenticity A.6 C.17) E MI Localisation Accuracy A.1, A.2, A.78) Robustness to Interference A.8, A.99) GNSS-Denied Accuracy A.1, A.2, A.410) GNSS Sensitivity A.1011) Position Integrity Protection Level A.11 C.212) Position Integrity Time-to-Alert (TTA) N/A13) Position Integrity Time-to-Recover-from-Alert N/A

NOTE: additional features are for further study (FFS); e.g. accuracy of speed and acceleration (horizontal and vertical).

4.2 Horizontal Position AccuracyThis Feature is the maximum error of ability of a Location System to report the horizontal position of athe Location target reported by the Location System is the most common performance feature.

It is required whenever the horizontal position is used as an input data by the application module to deliver the location-based services.

The requirements for this feature can range from relaxed constraints for personal navigation applications, to more stringent ones for liability- critical applications, such as road charging, dangerous cargo tracking.

ETSI

TS 103 246 V0.1.2 (2014-06)15

[4.3] The performance metric associated to this performance feature is the “Horizontal Position Accuracy”, defined in clause A.1 of Annex A.

[4.4] Is it noted that additional features are for further study (FFS); e.g. horizontal speed accuracy, and horizontal acceleration accuracy.

[4.5]

[4.6] Vertical Position AccuracyThis Feature is the maximum error of The ability of a Location System to report thea vertical position of a location target reported by the Location Systemis required any time the vertical position is used as an input data by the application module to deliver the location-based services.

This feature is applies usually needed when vertical guidance is required, for instance to allow ensure the positional coordinates provided tofor an emergency indoor caller to result in an “actionable location” for emergency response, especially in urban environments.

[4.7] The performance metric associated to this performance feature is the “Vertical Position Accuracy”, defined in clause A.2 of Annex A.

[4.8] Is it noted that additional features are for further study (FFS); e.g. vertical speed accuracy, and vertical acceleration accuracy.

[4.9]

[4.10] Availability of Required AccuracyThe availability of the required accuracy is the probability that the Location System is able to deliver horizontal and vertical (what about time etc. ???) to the application module location-related data with a determined level of accuracy.

[4.11] The feature itself is therefore the ability of the location system to guarantee a given level availability, using adequate measurements, computation and communication means.

[4.12] The performance metric associated to this performance feature is the “Availability of required accuracy” defined in clause A.3 of Annex A.

[4.13]

[4.14] Precise GNSS Time RestitutionAccuracy What about non-GNSS time accuracy???

This Feature is the maximum error of GNSS time provided by the Location System.

ETSI

TS 103 246 V0.1.2 (2014-06)16

Robert Mort, 28/08/14,


As part of the location-related data generated by the Location system, restituted GNSS time can be a driving parameter for the application module. Thus, aApplications requiring synchronizisation of assets distributed across wide geographical areas can use GNSS time as a time reference, for example, and synchronize all assets to this single source.

[4.15] The ability of the Location System to provide render accurately GNSS time is the performance feature required for such type of application, and is tracked under “Precise GNSS time restitution”.

[4.16] The performance metric associated to this performance feature is the “Restituted GNSS time accuracy” defined in clause A.4 of Annex A.

[4.17] Time-to-First-Fix (TTFF)The time-to-first-fixTTFF reflects is the time taken by the Location System to provide provide target (non-interferer??) position data to the application module the required location-related data, starting either from the reception of athe request, or from another triggering event (for instance for periodic or geo-dependant reporting).

The TTFF is commonly broken down into three more specific scenarios

Cold or Factory: The receiver is missing, or has inaccurate estimates of, its position, velocity, the time, or the visibility of any of the GPS satellites. As such, the receiver must systematically search for all possible satellites. After acquiring a satellite signal, the receiver can begin to obtain approximate information on all the other satellites, called the almanac. This almanac is transmitted repeatedly over 12.5 minutes. Almanac data can be received from any of the GPS satellites and is considered valid for up to 180 days. Manufacturers typically claim the factory TTFF to be 15 minutes.

Warm or Normal: The receiver has estimates of the current time within 20s, the current position within 100 kilometers, and its velocity within 25m/s, and it has valid almanac data. It must acquire each satellite signal and obtain that satellite's detailed orbital information, called ephemeris data. Each satellite broadcasts its ephemeris data every 30s, and is valid for up to four hours.

Hot or standby: The receiver has valid time, position, almanac, and ephemeris data, enabling a rapid acquisition of satellite signals. The time required of a receiver in this state to calculate a position fix may also be termed Time to Subsequent fix (TTSF)

The performance feature is therefore the ability of the Location System to provide the required data in a timely manner.

[4.18] The performance metric used to characterised this performance feature is the “time-to-first-fix” (TTFF) defined in clause A.5 of Annex A.

[4.19]

[4.20] Position AuthenticiatyionRF spoofing may affect the analysis of location target signals resulting in false position data.

Position Aauthenticityation gives a is the level of assurance that the data for a location target has been derived from real signals relating to the target.Location System ability to report a quality of service indicator characterizing the authenticity of the location-related data. This performance feature is typically required when a fraud threat exist in the frame of the application use case.

ETSI

TS 103 246 V0.1.2 (2014-06)17


is this a better definition?


http://en.wikipedia.org/wiki/GPS_signals#ephemeris

http://en.wikipedia.org/wiki/GPS_signals#Almanac

4.3 This indicator is made of a single Boolean flag, indicating if the position is authentic or not.

[4.21] The performance metric used to characterise this performance feature is the “Position authentication” defined in clause A.6 of Annex A.

[4.22]

[4.23] Interference EMI Localisation AccuracyRF interference sources (deliberate or accidental) are significant factors contributors into the overall performance of GNSS-based positioning services. For any service where increased monitoring of these sources is considered importanta driving function, the determination of these sources’ positions can be required fromby the associated Location System.

Therefore, the EMIInterference Localisation Accuracy performance feature is similar to regular position accuracy features (horizontal and vertical) defined above, but applied in the case where the location target is an interference source.

This performance feature therefore corresponds to the maximum error awith which bility of the Location System to identifiesy the origin of an interfering signal, through different technical enablers both at the Positioning Module and Central Facility.

The performance metrics used to characterise this performance feature are:

“Horizontal Position Accuracy”, defined in clause A.1 of Annex A.

“Vertical Position Accuracy”, defined in clause A.2 of Annex A.

“Direction of arrivalDoA accuracy”, defined in clause A.7 of Annex A.

NOTE: DoA data is useful if horizontal and/or vertical positions are not available.

The type of metric used to characterise the Location System performance depends on the way the location system implements this e feature. This is further described in clause Error: Reference source not found.

4.4[4.24] Robustness to InterferenceLocation Systems might be required to operate in constrained RF environments, in particular regarding in the GNSS frequency bands. The performance feature “robustness to interference” is the ability of the receiver to operate under interference conditions, and maintain an appropriate level of performance.

The performance metrics used to characterise this performance feature are:

the “PVT degradation under interference conditions source” defined in clause A.8 of Annex A.

the " recovery time of normal performance”, defined in clause A.9 of Annex A.

The type of metric used to characterise the Location System performance depends on the way the system implements the feature. This is further described in clause Error: Reference source not found

[4.25] GNSS- Denied AccuracySurvivalGNSS-Denied AccuracyThis refers to performance feature is the ability of the Location System to maintain an appropriate quality of the location-related data when the positioning terminal faces an outage in the GNSS signal reception.

ETSI

TS 103 246 V0.1.2 (2014-06)18

Such a feature is required for Location Systems operating in an environments where a number of “GNSS-denied” areas are present, and where which do not tolerate outage in service provision is not tolerable (for instance an automotive navigation device entering , which accommodates outage in tunnels).

The performance metrics used to characterise the Location System performance are:

“Horizontal Position Accuracy”, defined in clause A.1 of Annex A.

“Vertical Position Accuracy”, defined in clause A.2 of Annex A.

“Restituted GNSS time accuracy” defined in clause A.4 of Annex A.

4.5[4.26] GNSS Sensitivity“GNSS Sensitivity” refers to the performance feature is the minimum RF signal power at the receiver input required for a specified reliability of ability of the Location System to provide the required location-related data provision when eitherwhen:

1. GNSS signals are first acquired, or

2. GNSS tracking is in operation (e.g. received by the positioning module antenna suffers an attenuated propagation channel).

The latter is is typically applicable for Location Systems operating in urban or indoor environments, when GNSS signals can be significantly attenuated.

The performance metric used to characterise the Location System performance is the “GNSS sensitivity” defined in clause A.10 of Annex A.

4.6[4.27] Position Integrity Protection LevelPosition Integrity is a generic performance feature which is the ability of the Location System to measure the trust that can be placed in the accuracy of the location target position that is provides. In the present technical context

, itIt is expressed through the computation of a protection level associated to a predetermined integrity risk (as a function of the type end-user application) see [7].

4.7

[4.28] The performance feature Position Integrity Protection Level therefore represents the ability of the location system to compute the protection level related to the mobile target position.

[4.29] The performance metric used in order to characterise this performance feature is the “Position Integrity performance”, defined in clause A.11 of Annex A.

[4.30] Position Integrity Time-to-Alert (TTA)Position Integrity includes the ability of the Location System to provide timely and valid warnings to the application module thatwhen the location-related data must not be used for the intended location-based service. Such an alert isshall

ETSI

TS 103 246 V0.1.2 (2014-06)19

be generated in case of unsafe conditions, i.e. when the Protection Level provided by the Location System does not limit the position error with reliability consistent with Integrity risk.

The performance feature Position Integrity Time-to-Alert (TTA) therefore represents the ability of the location system to notify the application module of unsafe conditions within a required time delay.

4.8[4.31] Position Integrity Time-to-Recover-from-Alert)Similar to above???

5 The performance metric used in order to characterise this performance feature is the “Position Integrity performance”, defined in clause A.11 of Annex A.

[5]

ETSI

TS 103 246 V0.1.2 (2014-06)20

[6] Performance RequirementsThis clause defines the minimum performance requirements for each of the performance features defined in clause 4.

The definitions of performance metrics for these features are defined given in Annex A.

Annex B defines the applicable conditions for these performance requirements.

Annex C describes specific scenarios applicable to the performance features “position authenticationauthenticity”, and “Position integrity Protection level / Time to alarm”.

The Performance Features are defined in each case for a range of operating conditions such as:

1) location target environments:

rural,

urban,

suburban,

industrial.

2) Target motion types:

static

moving

3) terminal types (Class A, B, C - representing classes of robustness to interference)

4) fault-free/faulty conditions etc.

5.1[6.1]

[6.2] Horizontal Position AccuracyThe Horizontal Position data provided by the location system Location systems implementing performance feature “horizontal position accuracy” shall comply with the minimum performance requirements definedscribed in clauses Error: Reference source not found and Error: Reference source not found below.

5.1.1[6.2.1]

[6.2.2] Operational conditionsError: Reference source not found gives below provides the operational conditions used to define the minimum required performance for feature “Horizontal Position Accuracy”, and the masking parameters tuning applicable for each of them.

ETSI

TS 103 246 V0.1.2 (2014-06)21

Table 5-1: Environment applicability for “horizontal position accuracy”

Environment type Applicability Masking parameters

x1 x2 x3Open area Yes See Error:

Referencesource not found

Rural area Yes See Error: Referencesource not found

Suburban Yes See Error: Referencesource not found

Urban Yes See Error:Reference

source not foundAsymmetric area Yes See Error: Reference

source not foundIndustrial area Yes See Error: Reference

source not found

5.1.2[6.2.3]

[6.2.4] Use case: Moving Location Target

5.1.2.1[6.2.4.1] Target movement

The location target follows the trajectory described in clause B.3. The reference point {0;0;0} has coordinates expressed in [WGS84] system: longitude = [TBD], latitude = [tbd].

The trajectory parameters are provided in Error: Reference source not found below.:

Table 5-2: Mobile targetLocation target trajectory movement parameters

Trajectory parameter

Value

v1 25 km/hv2 100 km/hv3 100 km/hd1 250 mD2 250 m

Add columns for indoor and outdoor

Which class of terminal?

NOTE: the above values correspond with those of 3GPP [ref ]

5.1.2.2[6.2.4.2] Performance requirement

The location target horizontal position estimated by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the Classgrade of the location system (A, B, C)

the operational environment considered, as defined in clause B.2.3.

This performance shall be met when the trajectory is followed travelled in both directions.

ETSI

TS 103 246 V0.1.2 (2014-06)22

Table 5-3: performance requirement for Horizontal Pposition Accuracy, Open Area, Moving target

MetricMetric(as per clause 4.2)

Performance requirementMax position error – Open Area(m)

Class A Class B Class CMean errorvalue 0,2 0,5 8,4

Standard deviation [tbd] [tbd] [tbd]67th percentile 0,3 0,4 8,895th percentile 0,4 0,8 22,199th percentile 0,5 1,4 23,8

Mean cross track error - Mean value 0,1 0,2 4,8

Cross track error - 67th percentile 0,1 0,3 5,8Cross track error - 95th percentile 0,2 0,7 16,5Cross track error - 99th percentile 0,3 1,2 20

Mean along track error - Mean value 0,2 0,3 5,4

Along track error - 67th percentile 0,3 0,3 6,4Along track error - 95th percentile 0,4 0,5 21,9Along track error - 99th percentile 0,5 1 22,4

Table 5-4: performance requirement for Horizontal Position Accuracy, Rural Area, Moving target


Performance requirementMax position error (m) – Rural Area

Class A Class B Class CMean value 0,4 1 9,6

Standard deviation [tbd] [tbd] [tbd]67th percentile 0,5 1,1 12,295th percentile 0,9 2,1 1999th percentile 1,1 2,8 22,7

Cross track error - Mean value 0,3 0,6 5,3Cross track error - 67th percentile 0,3 0,8 6,5Cross track error - 95th percentile 0,8 1,8 13,7Cross track error - 99th percentile 1,1 2,4 16,7

Along track error - Mean value 0,2 0,4 6,6Along track error - 67th percentile 0,3 0,5 10,1Along track error - 95th percentile 0,6 1 18,1Along track error - 99th percentile 0,8 1,5 18,7

Table 5-5: performance requirement for Horizontal position Accuracy, Suburban Area, Moving target


Performance requirementMax position error (m) – Suburban Area

Class A Class B Class CMean value 0,49,3 1,5 9,3

Standard deviation [tbd][tbd] [tbd] [tbd]67th percentile 0,410,4 1,5 10,495th percentile 0,715,1 5 15,199th percentile 0,921,5 8,1 21,5

Cross track error - Mean value 0,25,1 1,1 5,1Cross track error - 67th percentile 0,26,6 1 6,6Cross track error - 95th percentile 0,512,4 4,3 12,4Cross track error - 99th percentile 0,819,2 7,4 19,2

Along track error - Mean value 0,36,5 0,7 6,5Along track error - 67th percentile 0,38,4 0,6 8,4Along track error - 95th percentile 0,614,6 2,5 14,6Along track error - 99th percentile 0,715,1 4,8 15,1

ETSI

TS 103 246 V0.1.2 (2014-06)23

Table 5-6: performance requirement for Horizontal position Accuracy, Urban Area, Moving target


Performance requirementMax position error (m) – Urban Area

Class A Class B Class CMean value 1,6 24,2 40,8

Standard deviation [tbd] [tbd] [tbd]67th percentile 0,8 29,2 52,595th percentile 9,3 49,9 75,399th percentile 19 62,9 98,7

Cross track error - Mean value 1 15,2 26,9Cross track error - 67th percentile 0,6 18,8 37,9Cross track error - 95th percentile 3,7 42,6 59Cross track error - 99th percentile 13,8 51,4 66,9

Along track error - Mean value 1,1 15,4 21,9Along track error - 67th percentile 0,5 19,2 25,6Along track error - 95th percentile 6,2 44,3 68,3Along track error - 99th percentile 14,6 56,3 90,4

Table 5-7: performance requirement for Horizontal position Accuracy, Asymmetric Area, Moving target


Performance requirementMax position error (m) – Asymmetric Area


Standard deviation [tbd] [tbd] [tbd]67th percentile 0,5 13,6 45,495th percentile 1 38 7999th percentile 1,2 54,9 99,5

Cross track error - Mean value 0,3 10,2 15,3Cross track error - 67th percentile 0,4 11,4 19,3Cross track error - 95th percentile 0,8 32,4 59Cross track error - 99th percentile 1,1 50,4 77,3

Along track error - Mean value 0,3 5,1 21,4Along track error - 67th percentile 0,3 5,6 33,6Along track error - 95th percentile 0,6 18,3 68,1Along track error - 99th percentile 0,9 28,3 92

Table 5-8: performance requirement for Horizontal position Accuracy, Industrial Area, Moving target


Performance requirementMax position error (m) – Industrial Area


Standard deviation [tbd] [tbd] [tbd]67th percentile 0,8 5 75,295th percentile 1,7 23,2 96,799th percentile 2,4 44,1 100,2

Cross track error - Mean value 0,5 5,1 33,6Cross track error - 67th percentile 0,6 3,7 46,5Cross track error - 95th percentile 1,6 19,2 77Cross track error - 99th percentile 2,2 40,9 81,8

Along track error - Mean value 0,4 2,7 38,3Along track error - 67th percentile 0,5 2,1 62Along track error - 95th percentile 1 10,9 84,6Along track error - 99th percentile 1,4 22,1 88,5

ETSI

TS 103 246 V0.1.2 (2014-06)24


Check std dev vs. mean

5.1.3[6.2.5] Use case: Static Location Target

5.1.3.1[6.2.5.1] Target position

The location target is located in coordinates expressed in WGS84 [tbc] system: longitude = [tbd], latitude = [tbd].


The location target position estimated by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the gradeClass of the location system.


Table 5-9: performance requirement for Horizontal positionPosition Accuracy, Open area, Static target

MetricMetric(as per clause

4.2)

Performance requirementMax position error (m)Class A Class B Class C

Mean value [tbd] [tbd] [tbd]Standard deviation [tbd] [tbd] [tbd]

67th percentile [tbd] [tbd] [tbd]95th percentile [tbd] [tbd] [tbd]99th percentile [tbd] [tbd] [tbd]

Table 5-10: performance requirement for Horizontal positionPosition Accuracy, Rural Area, Static target


Performance requirementMax position error (m) – Rural Area

Class A Class B Class CMean value [tbd] [tbd] [tbd]

Standard deviation [tbd] [tbd] [tbd]67th percentile [tbd] [tbd] [tbd]95th percentile [tbd] [tbd] [tbd]99th percentile [tbd] [tbd] [tbd]

Table 5-11: performance requirement for Horizontal positionPosition Accuracy, Suburban Area, Static target


Performance requirementMax position error (m) – Suburban Area



Table 5-12: performance requirement for Horizontal positionPosition Accuracy, Urban Area, Static target


Performance requirementMax position error (m) – Urban Area



ETSI

TS 103 246 V0.1.2 (2014-06)25

Table 5-13: performance requirement for Horizontal positionPosition Accuracy, Asymmetric Area, Static target


Performance requirementMax position error (m) – Asymmetric Area



Table 5-14: performance requirement for Horizontal positionPosition Accuracy, Industrial Area, Static target


Performance requirementMax position error (m) – Industrial Area



5.2[6.3] Vertical Position AccuracyThe system provides Vertical Position data that shall comply with the requirements defined in the sub-clauses below.

5.2.1Operational conditionsError: Reference source not found to Error: Reference source not found below provide the operational conditions used to define the minimum required performance for feature “Vertical Position Accuracy”, and the masking parameters tuning applicable for each of them.

Table 5-15: Environment applicability for “vertical position accuracy”

Environment type Applicability Masking parametersto be used








source not found

5.2.2[6.3.1] Use case: Moving Location Target


The location target follows the trajectory described in clause B.3. The reference point {0;0;0} has coordinates expressed in [WGS84] system: longitude = [tbd], latitude = [tbd].

The trajectory parameters are provided in Error: Reference source not found below.

ETSI

TS 103 246 V0.1.2 (2014-06)26


Clarify x values

Table 5-16: Mobile targetLocation target movement parameters


Value



The location target vertical position estimated by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the gradeClass of the location system


This performance shall be met when the trajectory is travelled in both directions.

Table 5-17 Performance requirement for vertical positionPosition Accuracy, open area, moving location target


Performance requirementMax position error (m) – open area



Table 5-18 Performance requirement for vertical positionPosition Accuracy, rural area, moving location target


Performance requirementMax position error (m) – rural Area



Table 5-19 Performance requirement for vertical positionPosition Accuracy, suburban area, moving location target


Performance requirementMax position error (m) – suburban area



ETSI

TS 103 246 V0.1.2 (2014-06)27

Table 5-20 Performance requirement for vertical positionPosition Accuracy, urban area, moving location target


Performance requirementMax position error (m) – urban area



Table 5-21 Performance requirement for vertical positionPosition Accuracy, asymmetric area, moving location target


Performance requirementMax position error (m) – asymmetric area



Table 5-22 Performance requirement for vertical positionPosition Accuracy, industrial area, moving location target


Performance requirementMax position error (m) – industrial area



5.2.3[6.3.2] Use case: Static Location Target


The location target is located in coordinates expressed in WGS84 [TBC] system: longitude = [TBD], latitude = [TBD].





ETSI

TS 103 246 V0.1.2 (2014-06)28

Table 5-23 Performance requirement for Vertical position accuracy, Open Area, Static location target


Performance requirementMax position error (m) – Open Area



Table 5-24 Performance requirement for vertical positionPosition Accuracy, rural area, static location target


Performance requirementMax position error (m) – rural Area



Table 5-25 Performance requirement for vertical positionPosition Accuracy, suburban area, static location target


Performance requirementMax position error (m) – suburban area



Table 5-26 Performance requirement for vertical positionPosition Accuracy, urban area, static location target


Performance requirementMax position error (m) – urban area



Table 5-27 Performance requirement for Vertical positionPosition Accuracy, asymmetric area, static location target


Performance requirementMax position error (m) – asymmetric area



ETSI

TS 103 246 V0.1.2 (2014-06)29

Table 5-28 Performance requirement for vertical positionPosition Accuracy, industrial area, static location target


Performance requirementMax position error (m) – industrial area



5.3[6.4] Availability of Required Accuracy[TBD]

accuracy of which parameters??

Level of accuracy??

[6.5] Precise GNSS Time RestitutionAccuracyThe GNSS time accuracy is the difference between the true GNSS time (as implemented in the GNSS system timing facility) and the time restituted by the GNSS processor based on the PVT solution.

5.3.1

[6.5.1] Operational conditionsGNSS signals are defined as per clause B.1.2.

The operational environment of the location system in fault-free conditions is defined as follows:

Table 5-29 Environment applicability for feature “precise GNSS time restitutionAccuracy”







source not foundAssymetricAsymmetric

areaYes See Error: Reference


source not found

5.3.2[6.5.2] Use case: Moving Target


The location target follows the trajectory described in clause B.3. The reference point {0;0;0} has coordinates expressed in [WGS84] system: longitude = [TBD], latitude = [TBD].

ETSI

TS 103 246 V0.1.2 (2014-06)30


Table 5-30: Mobile targetLocation target movement parameter


Value



The time restituted by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the class of the location system

the operational environment, as defined in clause B.2.3.

This performance shall be met when the trajectory is travelled both ways.

Table 5-31 Performance requirement for Precise GNSS time restitutionAccuracyopen area, moving Location target

Metric(as per clause 4.2)

Performance requirementMaximum time error (s)


95th percentile [tbd] [tbd] [tbd]

Table 5-32 Performance requirement for Precise GNSS time restitutionAccuracyrural area, moving Location target





Table 5-33 Performance requirement for Precise GNSS time restitutionAccuracysuburban area, moving Location target





Table 5-34 Performance requirement for Precise GNSS time restitutionAccuracyurban area, moving Location target





ETSI

TS 103 246 V0.1.2 (2014-06)31

Table 5-35 Performance requirement for Precise GNSS time restitutionAccuracyasymmetric area, moving Location target





Table 5-36 Performance requirement for Precise GNSS time restitutionAccuracyindustrial area, moving Location target


4.2)




5.3.3[6.5.3] Use case: Static Target







Table 5-37 Performance requirement for Precise GNSS time restitutionAccuracyopen area, static location target


4.2)


Class ALow grade

Class BMedium

grade

Class CHigh grade

Mean value [tbd] [tbd] [tbd]95th percentile [tbd] [tbd] [tbd]

Table 5-38 Performance requirement for Precise GNSS time restitutionAccuracyrural area, static location target


4.2)




Table 5-39 Performance requirement for Precise GNSS time restitutionAccuracysuburban area, static location target


4.2)




ETSI

TS 103 246 V0.1.2 (2014-06)32

Table 5-40 Performance requirement for Precise GNSS time restitutionAccuracyurban area, static location target


4.2)




Table 5-41 Performance requirement for Precise GNSS time restitutionAccuracyasymmetric area, static location target


4.2)




Table 5-42 Performance requirement for Precise GNSS time restitutionAccuracyindustrial area, static location target


4.2)




5.4[6.6] Time-to-First-Fix (TTFF)5.4.1[6.6.1] Operational conditionsGNSS signals defined as per clause B.1.2.

The operational environment, applicable for the location system performance requirements in fault-free conditions are defined as follows:

Table 5-43 Environment applicability for feature “Time-to-first-fix”









source not found

ETSI

TS 103 246 V0.1.2 (2014-06)33



The location target follows the trajectory described in clause B.3. The reference point {0;0;0} has coordinates expressed in [WGS84] system: longitude = [TBD], latitude = [TBD].




Value



The time-to-first-fixTTFF achieved by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the class of the location system



Table 5-45 Performance requirement for Time-to-first-fixTTFFopen area, moving location target


Performance requirement – Open AreaClass A Class B Class C

Time-to-first-fix Max TTFF[secondss]Mean value [tbd] 2.5 [tbd]

Standard deviation [tbd] 0.4 [tbd]67th percentile [tbd] 2.7 [tbd]95th percentile [tbd] 3.3 [tbd]99th percentile [tbd] 3.8 [tbd]

Minimum Value [tbd] 1.8 [tbd]Maximum Value [tbd] 3.8 [tbd]Horizontal Position Error Max Horizontal Position Error [metersm]

Mean value [tbd] 5.6 [tbd]Standard deviation [tbd] 4.3 [tbd]

67th percentile [tbd] 5.9 [tbd]95th percentile [tbd] 12.1 [tbd]99th percentile [tbd] 26.2 [tbd]

ETSI

TS 103 246 V0.1.2 (2014-06)34

Table 5-46 Performance requirement for Time-to-first-fixTTFFrural area, moving location target


Performance requirement – rural AreaClass A Class B Class C

Time To First FixMax TTFF [secondss]Mean value [tbd] 2.7 [tbd]





Table 5-47 Performance requirement for Time-to-first-fixTTFFsuburban area, moving location target


Performance requirement – suburban AreaClass A Class B Class C






Table 5-48 Performance requirement for Time-to-first-fixTTFFUrban area, moving location target


Performance requirement – urban AreaClass A Class B Class C

Time-to-first-fix Max TTFF[secondss]Mean value [tbd] 4.4 [tbd]





ETSI

TS 103 246 V0.1.2 (2014-06)35

Table 5-49 Performance requirement for Time-to-first-fixTTFFasymmetric area, moving location target


Performance requirement – asymmetric areaClass A Class B Class C






Table 5-50 Performance requirement for Time-to-first-fixTTFFindustrial area, moving location target


Performance requirement – industrial areaClass A Class B Class C

Time-to-first-fix Max TTFF[secondss]Mean value [tbd] [tbd] [tbd]


Minimum Value [tbd] [tbd] [tbd]Maximum Value [tbd] [tbd] [tbd]Horizontal Position Error Max Horizontal Position Error [metersm]


67th percentile [tbd] [tbd] [tbd]95th percentile [tbd] [tbd] [tbd]99th percentile [tbd] [tbd] [tbd]Mean value [tbd] [tbd] [tbd]

5.4.3[6.6.3] Use case: Static Target




The time-to-first-fixTTFF achieved by the location system shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:

the class of the location system.


ETSI

TS 103 246 V0.1.2 (2014-06)36

Table 5-51 Performance requirement for Time-to-first-fixTTFFopen area, static location target


Performance requirement – Open AreaClass A Class B Class C






Table 5-52 Performance requirement for Time-to-first-fixTTFFrural area, static location target


Performance requirement – rural AreaClass A Class B Class C






ETSI

TS 103 246 V0.1.2 (2014-06)37

Table 5-53 Performance requirement for Time-to-first-fixTTFFsuburban area, static location target


Performance requirement – suburban Area

Class A Class B Class CTime-to-first-fix Max TTFF[secondss]


67th percentile [tbd] [tbd] [tbd]95th percentile [tbd] [tbd] [tbd]99th percentile [tbd] [tbd] [tbd]




Table 5-54 Performance requirement for Time-to-first-fixTTFFUrban area, static location target


Performance requirement – urban AreaClass A Class B Class C






ETSI

TS 103 246 V0.1.2 (2014-06)38

Table 5-55 Performance requirement for Time-to-first-fixTTFFasymmetric area, static location target








Table 5-56 Performance requirement for Time-to-first-fixTTFFindustrial area, static location target








[6.7] Position AuthenticationAuthenticityLocation systems implementing functions which are able to authenticate the estimated positions shall comply with the performance requirements described in clauses below.

Location systems authenticate the estimated positions by means of specific algorithms that detect, and possibly mitigate, the presence of structured RF interference (i.e.: RF spoofing). The performance of a the location system can be evaluated in terms of:

Probability of detection PD : which is the probability that the location system detects false GNSS signals, given that there is a RF spoofing attack;

Probability of false alarm PFA : which is the probability that the location system detects false GNSS signals, given that there is not a RF spoofing attack. This feature is defined in terms of a false alarm probability - what alarms, specified how?????

The performance specification is organizised as follows:

ETSI

TS 103 246 V0.1.2 (2014-06)39

Marco Pini, 28/08/14,

Here, add a reference to TS – Reference Architecture –section 7.1.13

Two main use cases are considered: static location target, and moving location target;

For each of these two use cases, the requirements cover:

- Fault-free scenario, where no structured interfering signals are considered. Location system performance

are measured through as PFA ; a probability of false alarm

- Faulty scenarios, where elementary structured interfering signals are considered. Location system

performance are is measured through PD . the probability of detection of such structured interfering signals.

5.4.4[6.7.1] Operational conditionsGNSS signals defined as per clause B.1.2.

The operational environments, applicable for the location system performance requirements is the Open Area (see the related parameters in Table 5-95), either in in fault-free and faulty scenarios conditions . are defined in Error: Reference source not found below.

Table 5-57 Environment applicability for feature “position authenticationauthenticity”









source not found

5.4.5[6.7.2] Use case: Moving location target, fault free scenario

[6.7.2.1] Location Ttarget movement

The location target follows the trajectory described in clause C.1.1.3B.3. The reference point {0;0;0} has coordinates expressed in [WGS84] system: longitude = 7.0528 deg[TBD], latitude = [TBD]43.6169 deg.

The location target moves on a straight trajectory at a uniform speed, equal to 50 km/h. parameters are provided in Error: Reference source not found below.

Table 5-58: Mobile targetLocation target movement parameters


Value



The probability of false alarm false alarm probability achieved by the location system “position authenticationauthenticity” function shall meet the level specified in Error: Reference source not found Table 5-59

ETSI

TS 103 246 V0.1.2 (2014-06)40


What alarm?


For Position Authenticity there is a specific Annex that define the threat scenario. This include a location target movement trajectory Annex C 1.1.3.4. This was present since the first version of the document and seems reasonable. Therefore, Annex B.3 should not apply here.

below, depending on the Class of the location system. Such performance shall be met when the trajectory is travelled both ways. :




Table 5-59: AuthenticationAuthenticity False Alarm performance

Environment type

Maximum False Alarm probabilityClass A Class B Class C

Open area 210- 3 0 [TBC]

10- 2 0 [TBC] 0.10 [TBC]

Rural area 0 [TBC] 0 [TBC] 0 [TBC]Suburban 0 [TBC] 0 [TBC] 0 [TBC]

Urban 0 [TBC] 0 [TBC] 0 [TBC]Asymmetric area 0 [TBC] 0 [TBC] 0 [TBC]

Industrial area 0 [TBC] 0 [TBC] 0 [TBC]

In addition to the requirements above, the latency to provide authenticity shall not exceed [TBD]5 seconds.

5.4.6[6.7.3] Use case: Moving location target, faulty scenarios

[6.7.3.1] Location Ttarget movement

Dynamic parameters of the location target are reported in Annex C.1.1.3.4.


The location system shall meet the following performance requirements in terms of probability of detection of RF spoofing attack.

For a given spoofing scenario (see the list of threat scenarios in Table 5-97), Table 5-67 indicates:

the associated value of TSP; the value of the error induced by the RF spoofing attack that the location system shall be able to detect. The

type of error depends on the model corresponding to the spoofing scenario (see Table 5-97); the probability of detection as a function of the Class of the location system. The location system shall meet the following performance requirements in terms of spoofing attempt detection

performance.For a given spoofing scenario, the indicated TSP and error values are the TSP and error (jump or drift depending of the applicable model in the scenario) values that the location system shall be able to detect. This required ability is given as a function of:the gradeClass of the location systemthe operational environment considered, as defined in clause B.2.3.

ETSI

TS 103 246 V0.1.2 (2014-06)41

Table 5-60: Probability of detection performance, open area, moving location target

Spoofing scenario

TSP [dBW

]Minimum TSP

Minimum Error

Performance requirement – open areaClass A Class B Class C

M-1 [tbd]-143.5 0.5510-6

s[tbd] 0.85[tbd] 0.75[tbd] 0.68[tbd]

[tbd]-142.5 0.6610-6 s [tbd] 0.92[tbd] 0.85[tbd] 0.8[tbd]

-141.5[tbd] 0.7510-6 s [tbd] 0.98[tbd] 0.95[tbd] 0.9[tbd]

M-2 -147.5[tbd] 170 m[tbd] 0.85[tbd] 0.75[tbd] 0.68[tbd]-146.5[tbd] 200 m[tbd] 0.92[tbd] 0.85[tbd] 0.8[tbd]-145.5[tbd] 228 m[tbd] 0.98[tbd] 0.95[tbd] 0.9[tbd]

M-3 -147.5[tbd] 57 m[tbd] 0.85[tbd] 0.75[tbd] 0.68[tbd]-146.5[tbd] 70 m[tbd] 0.92[tbd] 0.85[tbd] 0.8[tbd]-145.5[tbd] 78 m[tbd] 0.98[tbd] 0.95[tbd] 0.9[tbd]

M-4 [tbd] [tbd] [tbd] [tbd] [tbd][tbd] [tbd] [tbd] [tbd] [tbd][tbd] [tbd] [tbd] [tbd] [tbd]


Table 5-61: Probability of detection, rural area, moving location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – rural areaClass A Class B Class C







ETSI

TS 103 246 V0.1.2 (2014-06)42

Table 5-62: Probability of detection, suburban area, moving location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – suburban areaClass A Class B Class C







Table 5-63: Probability of detection, urban area, moving location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – urban areaClass A Class B Class C







ETSI

TS 103 246 V0.1.2 (2014-06)43

Table 5-64: Probability of detection, asymmetric area, moving location target

Spoofing scenario

Minimum TSP

Minimum Error








Table 5-65: Detection performance, industrial area, moving location target

Spoofing scenario

Minimum TSP

Minimum Error








In addition to the requirements above, the latency to provide authenticity shall not exceed [TBC]5 seconds.

5.4.7[6.7.4] Use case: Static Location Target Fault-free scenario


The location target is located in a static position, with reference coordinates expressed in [WGS84] system: longitude = 7.0528 deg, latitude = 43.6169 degWGS84 [TBC] system: longitude = [TBD], latitude = [TBD].

ETSI

TS 103 246 V0.1.2 (2014-06)44

[6.7.4.2] Performance requirement

The probability of false alarm probability achieved by the location system “position authenticationauthenticity” function shall meet the level specified in Error: Reference source not foundError: Reference source not found Table 5-66 below, depending on the Class of the location system. :



Table 5-66: AuthenticationAuthenticity False Alarm performance

Environment type

Maximum False Alarm probabilityClass A Class B Class C

Open area 510- 4 0 [TBC]

210- 3 0 [TBC]

10- 2 0 [TBC]

Rural area 0 [TBC] 0 [TBC] 0 [TBC]Suburban 0 [TBC] 0 [TBC] 0 [TBC]

Urban 0 [TBC] 0 [TBC] 0 [TBC]Asymmetric area 0 [TBC] 0 [TBC] 0 [TBC]

Industrial area 0 [TBC] 0 [TBC] 0 [TBC]

In addition to the requirements above, the latency to provide authenticity shall not exceed [TBD]5 seconds.

5.4.8[6.7.5] Use case: Static Location Target Faulty scenarios


The location target is located in a static position, with reference coordinates expressed in [WGS84] system: longitude = 7.0528 deg, latitude = 43.6169 deg.



The location system shall meet the following performance requirements in terms of probability of detection of RF spoofing attackattempt detection performance.

For a given spoofing scenario, Table 5-67 indicates:

the associated value of TSP; the value of the error induced by the RF spoofing attack that the location system shall be able to detect. The

type of error depends on the model corresponding to the spoofing scenario (see Table 5-98) the probability of detection as a function of the Class of the location system.

the indicated TSP and error values are the TSP and error (jump or drift depending of the applicable model in the scenario) values that the location system shall be able to detect. This required ability is given as a function of:



ETSI

TS 103 246 V0.1.2 (2014-06)45

Table 5-67: Probability of detection performance, open area, static location target

Spoofing scenario

Minimum TSP

[dBW]

Minimum Error

Performance requirement – open areaClass A Class B Class C

S-1 [tbd] [tbd] [tbd] [tbd] [tbd][tbd] [tbd] [tbd] [tbd] [tbd][tbd] [tbd] [tbd] [tbd] [tbd]


S-3 -156.09[tbd]

0.4810-6

s[tbd] 0.90[tbd] 0.75[tbd] 0.63[tbd]

-154.46[tbd]

0.5810-6 s [tbd] 0.95[tbd] 0.90[tbd] 0.85[tbd]

-153.5[tbd] 0.6810-6 s [tbd] 0.98[tbd] 0.97[tbd] 0.95[tbd]

S-4 [tbd]-156.09 [tbd]145 m 0.90[tbd] 0.75[tbd] [tbd]0.63

-154.46[tbd] 175 m[tbd] 0.95[tbd] 0.90[tbd] [tbd]0.85

-153.5[tbd] 205 m[tbd] 0.98[tbd] 0.97[tbd] [tbd]0.95S-5 -

156.09[tbd] 40 m[tbd] 0.90[tbd] 0.75[tbd] 0.63[tbd]

-154.46[tbd] 48 m[tbd] 0.95[tbd] 0.90[tbd] 0.85[tbd]

-153.5[tbd] 56 m[tbd] 0.98[tbd] 0.97[tbd] 0.95[tbd]

Table 5-68: Probability of detection, rural area, static location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – rural areaClass A Class B Class C








ETSI

TS 103 246 V0.1.2 (2014-06)46

Table 5-69: Probability of detection, suburban area, static location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – suburban areaClass A Class B Class C








Table 5-70: Probability of detection, urban area, static location target

Spoofing scenario

Minimum TSP

Minimum Error

Performance requirement – urban areaClass A Class B Class C








ETSI

TS 103 246 V0.1.2 (2014-06)47

Table 5-71: Probability of detection, asymmetric area, static location target

Spoofing scenario

Minimum TSP

Minimum Error









Table 5-72: Detection performance, industrial area, static location target

Spoofing scenario

Minimum TSP

Minimum Error









In addition to the requirements above, the latency to provide authenticity shall not exceed [TBC]5 seconds.

[6.8] EMIInterference LocalisationLocalisation AccuracySee 5.24.

ETSI

TS 103 246 V0.1.2 (2014-06)48

Paolo Crosta, 28/08/14,

It is not clear the localisation: if it is just for scenario definition and performance, then it is misleading since it could be referred to source detection and localization.We should define scenarios and performance at antenna input and then consider different test cases at antenna level (with std antennas / smart antennas) and receiver level (interference rejection algos) .Another difference is within intentional and unintentional: maybe jamming could be considered under spoofing section.

Performance requirements for this feature rely on the interference conditions defined in Annex B.2.2.2

[TBD]

5.5[6.9] Robustness to InterferenceJamming is considered here

[TBD]

[6.10] GNSS DeniedGNSS-Denied AccuracySurvivalGNSS-Denied Accuracy is defined as the maximum position errors when the positioning terminal faces an outage in the GNSS signal reception.

5.5.1Operational conditionsError: Reference source not found below provides the operational conditions used to define the required performance for feature “GNSS deniedGNSS-Denied Accuracysurvival”, and the masking parameters tuning applicable for each of them.

Table 5-73: Environment applicability for feature “GNSS deniedGNSS-Denied Accuracysurvival”


Open area Yes SpecialRural area Yes SpecialSuburban Yes Special

Urban Yes SpecialAsymmetric area Yes Special

Industrial area Yes Special

The specific masking conditions to be used are defined in clause below.

5.5.1.1[6.10.1.1] Special masking conditions

For Indoor: Modify + add table

In order to measure the ability of a location system to maintain the mobile targetlocation target position determination within GNSS deniedGNSS-Denied environments, it proposed to use the operational environments defined in clause B.2.3, the trajectory defined in B.3, but to remove all GNSS and telecommunications-derived (TELCO) signals over a portion of the trajectory, as described in the graph below.

ETSI

TS 103 246 V0.1.2 (2014-06)49

Figure B-1. Sky conditionsSky attenuation conditions definition method.




The trajectory parameters are in Error: Reference source not found below.



Value



No time error requirements – see 4.10 ??

The location target position estimated by the location system after crossing the covered area (i.e. in point A6 or A15 according to the way the trajectory is travelled) shall meet the accuracy specified in Error: Reference source not found to Error: Reference source not found below, depending on:



This performance shall be met when the trajectory is travelled in reverse directions.

ETSI

TS 103 246 V0.1.2 (2014-06)50


Table 5-75: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Open Area


Requirements for Max position error position error (m) after covered area crossing – Open Area

Class A Class B Class C

Horizontal Position error

Mean value [tbd] [tbd] [tbd]Std value [tbd] [tbd] [tbd]Max value [tbd] [tbd] [tbd]

Cross track errorMean value [tbd] [tbd] [tbd]Std value [tbd] [tbd] [tbd]Max value [tbd] [tbd] [tbd]

Along track errorMean value [tbd] [tbd] [tbd]Std value [tbd] [tbd] [tbd]Max value [tbd] [tbd] [tbd]

Vertical Position error


Table 5-76: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Rural Area


Requirements for Max position error position error (m) after covered area crossing – rural area








Table 5-77: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Suburban Area


Requirements for Max position error position error (m) after covered area crossing covered area – suburban area








ETSI

TS 103 246 V0.1.2 (2014-06)51

Table 5-78: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Urban Area


Requirements for Max position error position error (m) after covered area crossing – urban area








Table 5-79: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Asymmetric Area


Requirements for Max position error position error (m) after covered area crossing – asymmetric area








Table 5-80: performance requirement for GNSS deniedGNSS-Denied survivalAccuracy, Industrial Area


Requirements for Max position error error (m)after covered area crossing – industrial area








5.6[6.11] GNSS SensitivityGNSS Sensitivity is the minimum RF signal power at the receiver input required for a specified reliability of correct :

1. a cquisition

2. tracking.

ETSI

TS 103 246 V0.1.2 (2014-06)52

Tracking only below??

5.6.1Operational conditionsError: Reference source not found below provides the operational conditions used to define the required performance for feature “GNSS sensitivity”, and the masking parameters tuning applicable for each of them.

Table 5-81: Environment applicability for “GNSS sensitivity”


Open area Yes SpecialRural area No -Suburban No -

Urban No -Asymmetric area Yes Special

Industrial area No -

The specific masking conditions to be used are defined in clause below.

5.6.1.1[6.11.1.1] Special masking conditions

In order to measure the ability of a location system to provide the required location-related data when the received GNSS signals power is low, it is proposed to:

consider use cases corresponding to the operational environment:

- “open Area”

- and “asymmetric area”

and to determine the maximum masking values tolerated by the location system, i.e. allowing the provision of the required location-related data

5.6.1.2[6.11.1.2] GNSS time initial estimate

Open area conditions correspond to fine estimate, asymmetric conditions correspond to coarse estimate

[TBD]







Value


ETSI

TS 103 246 V0.1.2 (2014-06)53



The location system sensitivity, expressed as the maximum tolerable masking parameters applied to the positioning module, shall meet the minimum performance specified in Error: Reference source not found and Error: Reference source not found, depending on:


the operational environment considered, as defined in clause Error: Reference source not found.

This performance shall be met when the trajectory is travelled in reverse directions.

Table 5-83: performance requirement for GNSS sensitivity, Open area (fine time assistance)

Metric(as per clause

4.2)

minimum RF signal power at the receiver inputRequirements for GSS sensitivity (dBW)

Class A Class B Class Cx1 (dB) [tbd] [tbd] [tbd]x2 (dB) [tbd] [tbd] [tbd]x3 (dB) [tbd] [tbd] [tbd]

Table 5-84: performance requirement for GNSS sensitivity, asymmetric area (coarse time assistance)

Metric(as per clause

4.2)

minimum RF signal power at the receiver input (dBW)Requirements for GSS sensitivity

Class A Class B Class Cx1 (dB) [tbd] [tbd] [tbd]x2 (dB) [tbd] [tbd] [tbd]x3 (dB) [tbd] [tbd] [tbd]

5.6.3[6.11.3] Use case: Static Target[TBD]

5.6.3.1[6.11.3.1] Target Position

[TBD]


[TBD]

5.7[6.12] Position Integrity Protection Level [TBD]

The following parameters define theNOTE: failure modes of GNSS systems :are considered in C.2

ETSI

TS 103 246 V0.1.2 (2014-06)54

Predicted MI Failure TypeBlock I, II, IIA Predicted MI Probability

Assigned Test Range

Assigned MI Failure

Probability

1 Ramp 0.01 m/s 2×10-7/hour/SV Ramp 0.01-0.05 m/s 1×10-6/hour/SV



4 Ramp 1 m/s 10×10-7/hour/SV Ramp 0.75-2.5 m/s 3.5×10-6/hour/SV

5 Ramp 5 m/s 12×10-7/hour/SV Ramp 2.5-5.0 m/s 4.1×10-6/hour/SV

6 Step 300 m 1×10-7/hour/SV Step 300-700 m 1×10-6/hour/SV

7 Step 3000 m 34×10-7/hour/SV Step 700-3000 m N/A

5.8[6.13] Position Integrity Alarm Limit and TTA[TBD]

ETSI

TS 103 246 V0.1.2 (2014-06)55

[Annex A] Annex A (normative): Definition of Performance MetricsThis Annexsection defines how performance shall be determined for each Performance Featureparameter. Each Metric defined in the sub-clauses below corresponds to a Feature defined in clause 4 and consists of a set of one or more parameters.

A.1 Horizontal Position Accuracy

The horizontal position accuracy is computed using the projection of the position error on the horizontal plane containing the locationmobile target true position (i.e. 2-dimensional projection).

The metrics used in order to statistically characterise this accuracy areis composed of the following quantities:

Mean value of the horizontal position error computed over a specified time interval.

Standard deviation of the horizontal position error computed over a specified time interval.

67th, 95th and 99th percentiles of the horizontal position error distribution computed over a specified time interval.

These metrics are defined as follows.

Let p be the true position of the mobile location target

Let be the position estimates collected over a specified time interval (N samples), projected on the local horizontal plane containing the mobile location target true position

i is the positioning error vector, defined as i = p - {p*}i . Note that this vector is contained in the local horizontal plane.

The mean value is defined as:

The standard deviation is defined as:

The percentiles, noted x (i.e. respectively 6795 99 ) is defined as the smallest error verifying:

In addition to the above, when the use case considers a moving mobile targetlocation target, the following metrics apply:

o Along-track error

o Across-track error

Diagram to be added for illustration

A.2 Vertical position accuracyThe vertical position accuracy is computed using the projection of the position error on the vertical axis containing the mobile targetlocation target true position.

ETSI

TS 103 246 V0.1.2 (2014-06)56

The metrics used in order to statistically characterise this accuracy is composed of the following quantities:

Mean value of the vertical position error computed over a specified time interval.

Standard deviation of the vertical position error computed over a specified time interval.

67th, 95th and 99th percentiles of the vertical position error distribution computed over a specified time interval.

These metrics are defined as follows.

Let p be the true position of the mobile targetlocation target

Let be the position estimates collected over a specified time interval (N samples), projected on the local vertical axis containing the mobile targetlocation target true position

i is the positioning error vector, defined as i = p - {p*}i . Note that this vector is contained in the local vertical axis.

The mean value is defined as:

The standard deviation is defined as:

The percentiles, noted x (i.e. respectively 6795 99 ) is defined as the smallest error verifying:

A.3 Availability of required accuracyThe availability is expressed as the percentage of time the required location-related information is available, over a predefined time windows (e.g.: 1 hour). Consequently, in order to be properly characterised, the following information shall be provided:

The availability rate, expressed in percent.

A description of the required location-related datainformation, including required quality of service.

The required quality of service can include an maximum required accuracy indicator and a , Protection Level an integer position, an authenticated position, etc.

[A.4] Restituted GNSS Time AccuracyThe restituted GNSS time accuracyGNSS time accuracy is the difference, measured in seconds, between the true GNSS time (as implemented in the GNSS system timing facility) and the GNSS time restituted by the GNSS sensor processor based on the PVT solution.

The metrics used in order to statistically characterise this accuracy is composed of the following quantities:

Mean value of the restituted GNSS time error computed over a specified time interval.

Standard deviation of the restituted GNSS time error computed over a specified time interval.

67th, 95th and 99th percentiles of the restituted GNSS time error computed over a specified time interval.

ETSI

TS 103 246 V0.1.2 (2014-06)57


Align with 5.4

A.4[A.5] Time-to-first-fix (TTFF)The time-to-first-fix is the time elapsed between from the time the location request is triggered by the location system (i.e. either from external immediate request, or following a location report trigger), toand the time the position responseanswer is delivered to the location system external interface.

The metrics used in order to statistically characterise this quantity areis composed of the following quantities:

and maximum values of the TTFF computed over a specified number of trials.

m Mean value of the TTFF computed over a specified number of trials.

s Standard deviation of the TTFF computed over a specified number of trials.

67th, 95th and 99th percentiles of the TTFF computed over a specified number of trials.

[A.6] Position AuthenticityationThe authenticity performance is characterised by the ability of the system to identify accurately spoofing attempts cases. accurately.

For position authenticity, the metrics to be used are therefore:

Probability of missed-detection in case of spoofing attempt (threat scenario)

Probability of false alarm in case of no spoofing is attempted (fault free scenario)

Mean time to provide position authenticity (latency)

NOTE: Position Continuity is considered in A.11 and Position Availability under A.3.

A.5[A.7] Direction of Arrival (DoA) Accuracy The direction of arrivalDoA accuracy is the error between the actual DoAdirection of arrival of a signal coming from a given interference source, and the DoA of this same signal estimated by the location system.

The metrics used in order to statistically characterise this quantity areis composed of the following quantities:

Mean value of the DoA error computed over a specified time interval.

Standard deviation of the DoA error computed over a specified time interval.

67th, 95th and 99th percentiles of the DoA error computed over a specified time interval.

[A.8] PVT Degradation under interference sourcesPVT degradation is measured as increase of the position, speed (and time???) estimation error caused by interference sources.

[A.9] Recovery time of normal performance after termination of pulse interference

Considers recovery after front-end saturation.

Includes Pulse, CW and wideband.

ETSI

TS 103 246 V0.1.2 (2014-06)58


Is this relevant?


Clarify text to define how performance is defined

A.6 [TBD][A.10] “GNSS sensitivity”Include acquisition and tracking sensitivity, reference 3GPP.

A.7 [TBD][A.11] Position Integrity Protection LevelperformanceThe integrity performance is characterised by: a pair protection level / integrity risk.

As far as position integrity is concerned, the metrics to be used are therefore:

The position protection level (PPL) expressed in meteres

The integrity risk, expressed as the probability that the actual position accuracy exceeds the position protection level under fault-free and faulty modes.

ETSI

TS 103 246 V0.1.2 (2014-06)59

[Annex B] Annex B (normative): Applicable conditionsThis section describes the conditions applicable to the definition of the minimum performance requirements given in clause Error: Reference source not found. These conditions concern:

the external systems with which location systems interacts. References towards relevant interface control documents are given

the operational environments applicable to the location system performance specification.

the moving target scenario description, applicable to most of the performance specified.

[B.1] B.1 General[B.1.1] B.1.1 GNSS systems parameters

[B.1.1.1] B.1.1.1 Systems constellation geometry and signal parameters

Error: Reference source not found below provides the reference documents applicable in the frame of the present performance specification. They provide for each system:

the constellation geometry to be used

signal parameters to be used, in particular the signal modulation parameters, and the minimum received power on ground in nominal conditions.

Table 5-85 – GNSS Constellations parameters

GNSS system System/User interface description

Number of visible satellites [Note 1]

HDOP range

GPS L1C/A [2] Variable 1.6 to 2.5 [tbc]GALILEO OS [1] Variable 1.6 to 2.5 [tbc]GALILEO E5A Variable 1.6 to 2.5 [tbc]

GLONASS [6] Variable 1.6 to 2.5 [tbc]GPS L5 [Note 2] [3] Variable 1.6 to 2.5 [tbc]

GPS L1C [Note 2] [4] Variable 1.6 to 2.5 [tbc]Beidou [x] Variable 1.6 to 2.5 [tbc]

Note 1: Number of satellites for testing will be defined in the Test Specification

Note 2: Single frequency use considered at present

[B.1.1.2] B.1.1.2 GNSS System Time Offsets

If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than [TBC].

[B.1.2] B.1.2 SBAS systems parameters

ETSI

TS 103 246 V0.1.2 (2014-06)60

[B.1.3] B.1.3 Cellular systems parameters

find a parameter equivalent to HDOP range to fix network properties. See 3GPP specs.

Some location systems rely on only cellular/wifi/bluetooth/DVB for positioning. The following list of standards is applicable for the definition of interfaces with external communication systems.

IEEE 802.11 for WiFi

IEEE 802.15 for Wireless Personal Area Network (short range wireless)

- IEEE 802.15.1 for Bluetooth

- IEEE 802.15.4a for low rate WPAN

3GPP TSXX;XXX for 2G



[FFS] for 5G

[B.2] B.2 Operational environmentsOperational environments for performance specifications in clause 5 are defined in clause B.2.3 of the present annex.

These environments are defined by a list of characteristics:

characteristics of GNSS sensor performance, which are described in clause B.2.1.

characteristics of other sensors performance, which are described in clause B.2.2.

A.1.1[B.2.1]

[B.2.2] B.2.1 GNSS-related environment characteristics

The following characteristics are related to the reception conditions of the GNSS signals.

These reception conditions concerns:

GNSS signals masking or attenuation from a terminal perspective, due to obstacles (buildings, walls, trees, windows, vehicles, etc) located on the signal propagation path. This is referred to as “sky conditionssky attenuation conditions” in the rest of the document

Existence of undesired GNSS signals echoes at terminal antenna input, caused by specular or diffuse reflections, and affecting the performance of the navigation solution. This is referred to as “multipath” in the rest of the document.

Presence of electro-magnetic interference sources in the terminal vicinity, causing an observable increase of noise in the terminal RF chain processing. This is referred to as “interference” in the rest of the document.

NOTE: the above phenomena are considered local contributors to GNSS signals quality. GNSS signal characteristics prior to being affected by these conditions (i.e. ignoring contribution of terminal vicinity, such as direction of arrival (and hence HDOP), received signal power) are assumed to be in line with Interface Control Documents of each of the considered GNSSs (see [1], [2], [3], [4], [5], and [6][6])

ETSI

TS 103 246 V0.1.2 (2014-06)61

[B.2.2.1] B.2.1.1 Sky Attenuation Conditions

Applicable sSky conditions are proposed to be defined as follows.

Figure 5-1 - Sky conditions definition method.

Figure 5-2 - Sky attenuation conditions

A sky plot provides:

the area of the sky above the receiver being affected by total signal masking. When Satellite azimuth and elevation coordinates (from terminal point of view) falls into these area, GNSS signal is considered blocked.

the area of the sky above the receiver being affected by partial signal masking. When Satellite azimuth and elevation coordinates (from terminal point of view) falls into these area, GNSS signal is considered attenuated. The amount of this attenuation is defined for each operational environment.

NOTE: several distinct areas can be defined for a single operational environment.

Typical sky conditionssky attenuation conditions are defined here below

Remove elevation from all. Replace by table simplifying all.

ETSI

TS 103 246 V0.1.2 (2014-06)62

Figure 5-3 - Open Sky plot. Table 5-86 – Open sky definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

Background Area out of Zone A

Figure 5-4 – Light masking plot. Table 5-87 – Light masking definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

B 5 - 30 210 – 330

C 5 - 30 30 - 150

Background Area out of Zones A, B, C

ETSI

TS 103 246 V0.1.2 (2014-06)63


Make x values clear

Figure 5-5 – Dense masking plot Table 5-88 – Dense masking definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

B 5 – 20 210 – 330

C 5 – 20 30 - 150

D 20 – 40 30 - 150

E 20 – 40 210 – 330

Background Area out of Zones A, B, C, D, E

Figure 5-6 – Urban canyon plot. Table 5-89 – Urban canyon definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

B 5 – 60 210 - 330

C 5 – 60 30 - 150


ETSI

TS 103 246 V0.1.2 (2014-06)64

Figure 5-7 – Asymmetric visibility plot Table 5-90 – Asymmetric visibility definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

B 5 - 60 30 – 150

C 10 – 60 230 - 310


[B.2.2.2] B.2.1.2 Multipath

Is a more realistic model is available?

The multipath model applicable to the performance specification is described below.

Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GNSS signal are defined in Error: Reference source not found.

Table 5-91 – Multipath model components

Initial relative Delay [m]

Carrier Doppler frequency of tap [Hz]

Code Doppler frequency of tap [Hz]

Relative mean Power [dB]

0 Fd Fd / N 0X Fd - 0.1 (Fd-0.1) /N Y

NOTE: Discrete Doppler frequency is used for each tap.

X, Y and N depend on the GNSS signal type. In addition, Y depends on the intensity of multipath faced in the operational environments. N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate.

The initial carrier phase difference between taps shall be randomly selected between 0 and 2. The initial value shall have uniform random distribution.

Error: Reference source not found below provides the parameters values of 3 levels of multipath intensity, from low to high. Parameter “k” in Error: Reference source not found is the GLONASS frequency channel number.

ETSI

TS 103 246 V0.1.2 (2014-06)65

Table 5-92 – Multipath model parameters

Multipath level Low Med HighSystem Signals X [m] Y [dB] Y [dB] Y [dB]

GalileoE1 125 [tbd] -4.5 [tbd]

E5a 15 [tbd] -6 [tbd]E5b 15 [tbd] -6 [tbd]

GPS/Modernizised GPS

L1 C/A 150 [tbd] -6 [tbd]L1C 125 [tbd] -4.5 [tbd]L2C 150 [tbd] -6 [tbd]L5 15 [tbd] -6 [tbd]

GLONASS G1 275 [tbd] -12.5 [tbd]G2 275 [tbd] -12.5 [tbd]

Table 5-93 – Ratio between Carrier Frequency and Chip Rate

System Signals N

GalileoE1 1540

E5a 115E5b 118

GPS/Modernizised GPS

L1 C/A 1540L1C 1540L2C 1200L5 115

GLONASS G1 3135.03 + k 1.10G2 2438.36 + k 0.86

[B.2.2.3] B.2.1.3 Electro-magnetic Interference

The EMI model applicable to the performance specification is described below.

Interference conditions are modelled by the total noisetotal noise power density after correlation correlationN X , Ic

, . It is derived from the interference source spectral characteristics according to the following formula:

N X , Ic =∫

f c−BW X

2

f c +BW X

2 N I ( f )⋅PG X ( f )⋅df

where

X stands for considered GNSS signal (e.g. Galileo E5a, GPS L1C …)

f c is the carrier frequency of the considered GNSS signal X

BW X is the GNSS sensor filtering bandwidth of the considered GNSS signal X

N I ( f ) is the external noise power density at the antenna level,

PG X (f ) is the spreading gain enabled by the receiver correlator while processing signal X

In the frame of this technical specification, three levels of impact of the interference environments are considered, from low to high.

ETSI

TS 103 246 V0.1.2 (2014-06)66

Table 5-94 – Interference levels

EMI level NILow -200 dBW/HzMedium -195 dBW/HzHigh -185 dBW/Hz

[B.2.3] B.2.2 Additional environment characteristics

Further to the above environment characteristics, addition characteristics are defined. They are relevant to the specification of performance for system embedding technical enablers other than GNSS sensor.

[B.2.3.1] B.2.2.1 Telecommunication beacons deployment

According to [7][7], location systems might embed telecommunication sensors which enable the provision of measurements participating to the navigation solution. This sub clause defines additional environmental characteristics relevant to this type of sensors.

Depending on the claimed compatibility of the location system under test, the beacon deployment(s) applicable to the present performance specification shall be as follows (one or several clauses applicable). Applicability is defined in [i.3]. [test TS].

B.2.2.1.1 Cellular telecommunications base stations characteristics and deployment

Relevant standard reference, providing the Base Station (BS) signal specification is provided in clause B.1.3.

B.2.2.1.1.1 Base stations deployment height

[TBD]

B.2.2.1.1.2 Base stations deployment density

[TBD]

B.2.2.1.2 Wi-Fi access points characteristics and deployment


B.2.2.1.2.1 Access points deployment height

[TBD]

B.2.2.1.2.2 Access points deployment density

[TBD]

B.2.2.1.3 Blue-tooth transmitters characteristics and deployment


[TBD]

ETSI

TS 103 246 V0.1.2 (2014-06)67

B.2.2.1.4 DVB transmitters characteristics and deployment

Relevant standard reference, providing the Base Station (BS) signal specification, is provided in clause B.1.3.

B.2.2.1.4.1 Transmitters deployment height

[TBD]

B.2.2.1.4.2 Transmitters deployment density

[TBD]

B.2.2.1.5 Microcell (5G) transmitters characteristics and deployment

For further study.

[B.2.3.2] B.2.2.2 Interference source definition

list the interference sources considered for “EMI robustness” and “EMI Localisation Accuracy”, for which the simplistic model of section B.2.1.3 is not suited

interference characteristics to be specified: received power, frequency, spectral shape (tbc), temporal shape (tbc).

[TBD]

[B.2.3.3] B.2.2.3 Magnetic conditions

[TBD]

[B.2.4] B.2.3 Operational environments definition

Error: Reference source not found below list operational environments used in the minimum performance specification in clause Error: Reference source not found.

Include assumption of antenna gain (0dBi)

Note: Environments applicable to users are defined in section 5.

ETSI

TS 103 246 V0.1.2 (2014-06)68


Table 5-95 – Operational environments definition

Operational environment

typeMasking conditions Multipath

LevelInterference

levelMagnetic

conditions

Telco beacons

distributionPolar plot Zone Atten

Open Area Open sky

x1 0 dB

Null Null NominalRural

distributionx2[tbd]

(total)

Rural AreaLight

masking

x1 0 dB

Low Low NominalRural

distributionx2 Totalx3 10 dB

Suburban Area

Dense masking

x1 0 dB

Medium Low NominalSuburban distribution

x2 Totalx3 Total

Urban AreaUrban

Canyonx1 0 dB

High Medium DegradedUrban

distributionx2 Total

Asymmetric Area

Asymmetric visibility

x1 15 dB

High Medium DegradedUrban

distributionx2 Totalx3 Total

Industrial Area

Dense masking

x1 0 dB

High High DegradedSuburban distribution

x2 Totalx3 Total

Refer to parameters above

[B.3] B.3 Moving Target Scenario descriptionThe diagram below describes a reference trajectory used in clause 5.

Point {0;0;0} is used as reference of the local coordinate system (X,Y), defining local horizontal plane.

Remove distances in figures to make generic trajectories

Figure 5-8 – Mobile targetLocation target trajectory

The diagram below provides the mobile targetlocation target speed profile, when travelling trajectory above.

ETSI

TS 103 246 V0.1.2 (2014-06)69

Figure 5-9 – Mobile targetLocation target speed profile

Specific value of parameters d1, D2, v1, v2 and v3 are defined for each Pperformance Featurespecification included in the clause Error: Reference source not found.

Annex B (normative):Threat Scenarios for Authenticity and Integrity Features

B.1[B.4] Authenticity Threat ScenariosThis clause describes the threat scenarios used for the definition of the performance requirements for authenticity features.

B.1.1[B.4.1] Threat scenariosAll the threat scenarios define spoofing attempts to the GNSS sensor of the positioning module. Such spoofing attempts broadcast intentional RF interference, with a structure similar to authentic GNSS signals, in order to deceive the GNSS sensor into estimating erroneous pseudo-ranges and computing false PVTs.

B.1.1.1[B.4.1.1] Scenario pre-conditions

The following pre-conditions apply to the location system:

location-related data of the location target are available;

all tracked GNSS signals are authentic.

B.1.1.2[B.4.1.2] Scenarios chronology

All the considered scenarios follow the sequence of events depicted in Figure 5-10:

ETSI

TS 103 246 V0.1.2 (2014-06)70

Figure 5-10 - Sequence of events associated to the threat scenarios

Where:

T0 is the time instant associated to the start of the scenario;

Ts is the time instant associated to the threat, while J indicated the time elapsed between T0 and the occurrence of the threat.

Te is the time instant associated to the end of the scenario, while S indicates the time elapsed between T s and the end of the scenario.

B.1.1.3[B.4.1.3] Scenario parameters

The scenarios are defined by the following list of parameters:

A attack classification: it defines classes of spoofing attempts, based on the method used to force the GNSS sensor to track the counterfeit GNSS signals.;

Total Spoofing Power (TSP): it is the signal power of the sum of counterfeit GNSS signals, received at the GNSS sensor antenna, which is assumed isotropic.

mMisleading information category: it determines the type of misleading information based on the impact of the spoofing attack to the data at the output of the GNSS sensor.

Total Spoofing Power (TSP): it is the signal power of the sum of counterfeit GNSS signals, received at the GNSS sensor antenna, which is assumed isotropic.

target movement: if the target moves, it provides the its trajectory and dynamics.

The following sub-clause defines each of these parameters.

C.1.1.3.1 Attack classifications

Two main classes of attacks are identified based on the method used to force the GNSS sensor to track the fake false GNSS signals. Several spoofed PRNs can be generated. For both classes it is considered that the spoofed GNSS signal(s) is (are) radiated from a single antenna.

Direct spoofed GNSS signal introduction

In this method, the counterfeit GNSS signals are generated and radiated towards the GNSS sensor without considering ation of the overall context (i.e.: GNSS constellation geometry, current GNSS time, and GNSS sensor position) sensor position, authentic PRN visibility).

In this case, in order to force the GNSS sensor to track spoofed PRNs, a signal outage of the authentic GNSS signals should be induced between T0 and Ts (e.g.: through a jamming attack that breaks the tracking of authentic signals). At Ts, the counterfeit false GNSS signals are radiated towards the GNSS sensor, and the power received by the GNSS sensor is in line with the TSP specified.

Shadowed spoofed GNSS signal introduction

ETSI

TS 103 246 V0.1.2 (2014-06)71

In this method, the counterfeit GNSS signals are generated and radiated towards the GNSS sensor in a way that the correlation peak associated to the counterfeit PRN rises in the shadow of the correlation peak of real PRN. Varying the relative delay between the authentic and counterfeit PRNs and increasing the power of the counterfeit GNSS signals, the GNSS sensor is forced to loloseses the tracking of the authentic PRN and synchronises its local code with the counterfeit PRN. Therefore, it means that GNSS constellation geometry, current GNSS time, and GNSS sensor position are known by the spoofing source in order to estimate the authentic PRN code delay and Doppler frequency at the target GNSS sensor. The counterfeit PRN is a false copy of PRN actually in view at the moment of the attack.

The Figure 5-11 illustrates this concept on the correlation domain, where the correlation peaks associated to authentic signals are green, correlation peaks due to counterfeit signals are in purple and the composite correlation peaks are in blue.

Figure 5-11 - Effects of introduction of shadowed Sspoofing on PRN signals

NOTE: Therefore, it means that GNSS constellation geometry, current GNSS time, and GNSS sensor position are known from the spoofing source in order to estimate the authentic PRN code delay and Doppler frequency, and that the counterfeit PRN is a false copy of PRN actually in view at the moment of the attack.

C.1.1.3.2 Total spoofing power

The total spoofing power (TSP) is the signal power of to the sum of counterfeit GNSS signals, received at the GNSS sensor antenna, which is assumed isotropic so that all signals are weighted equally.

It is defined as:

∑❑

❑❑

❑❑❑

where pis is the power of the ith counterfeit PRN, generated by the spoofing device.

The TSP is variable for each scenario, and used as a metric to measure the location system authenticationauthenticity performance.

C.1.1.3.3 Misleading information category

The spoofing attacks can cause three types of misleading information at GNSS sensor:

ETSI

TS 103 246 V0.1.2 (2014-06)72

erroneous PSR measurement;

erroneous time estimates;

erroneous estimates of the position (for both static of moving scenario).

The following error models, namely ramp and unit step and ramp functions multiplied by constant coefficients, are used for each of the above misleading information.

Figure 5-12 - Threat scenario error models

These models are applied for each type of misleading information according to Table 5-96 below, where:

a is a constant coefficient that multiply the unit step function, starting at T s;

b is a constant coefficient that multiply the ramp function, starting at T s ;

Table 5-96 - Misleading information model parameters

Misleading information

Error unit a unit b unit

PSR measurement

m m m/s

time estimates s s s/sposition

estimates (1)m m m/s

NOTE (1): The position error is measured on the across track axis.

The models parameters, either for the unit step function and the ramp, (jump and drift) are variable for each scenario, and used as a metric to measure the location system authenticationauthenticity performance.

C.1.1.3.4 Location target movement

For use cases where the location target is moving, the following trajectory shall be used.

ETSI

TS 103 246 V0.1.2 (2014-06)73

Figure 5-13 - Threat scenario trajectory

Point A is crossed at T0, point B is crossed at Te. The location target speed shall be uniform and equal to 50 km/h on the entire trajectory (see B.3).

B.1.2[B.4.2] Threat scenarios for moving targetsThe threat scenarios listed in Table 5-97 are defined for moving targets. Trajectory defined in clause C.1.1.3.4 applies.

Pre-conditions defined in clause C.1.1.1 apply.

Trajectory defined in clause C.1.1.3.4 applies.

Table 5-97 - Threat scenario for moving target

Scenario identifier

Attack class

Number of spoofed

PRNs

TSP range(dBW)


category

Error model

Model value range

M-1 Shadow All( 1 ) P [-144.5 -140.5][tbd]

Estimated Time Time estimates

RampRamp

[2 20] ns/s( 2 ) [tbd] s/s

M-2 Shadow 41 [-148.5 -144.5][tbd]

PSR measuremen

tPSR measurement

RampRamp

[3.5 6.5] m/s[tbd] m/s

M-3 Shadow 4P [-148.5 -144.5][tbd]

Estimated Position Position

estimates

RampRamp

[1 7.5] m/s( 2 ) [tbd] m/s

M-4 DirectDirect

[4 12]( 3 ) P [-142.5 -137.7][tbd]

Estimated Time Position

estimates

Unit step functio

nUnit step function

[5 60] s[tbd] m

M-5 DirectDirect

[4 12](1) P [-142.5 -137,7][tbd]

Estimated PositionPosition

estimates

Unit step functionRamp

[0.1 10] km[tbd] m/s

M-65 DirectDirect

[4 12]( 3 ) P [-142.5 -137.7][tbd]

Estimated Position Time

estimates

Unit step functionRamp

[0.1 10] km [tbd] s/s

Note (1): The number of spoofed PRNs is equal to the number of the satellites in view;

Note (2): The model value ranges for the estimated time and position assume HDOP compliant with Table 5-85

Note (3): At least 4 PRNs of those in view should be spoofed to perform the M-4 and M-5 spoofing attacks;

Number (P) of the spoofed PRNs P is [TBD].

ETSI

TS 103 246 V0.1.2 (2014-06)74


As measured from data set available at University of Texas

B.1.3[B.4.3] Threat scenarios for static targetsThe threat scenarios listed in Table 5-98 are defined for static targets.

Pre-conditions defined in clause C.1.1.1 apply.

Table 5-98 - Threat scenario for static target

Scenario identifier

Attack class

Number of spoofed

PRNs

TSP range(dBW)


category

Error model

Model value range

S-1 Direct [4 12](1) [-142.5 -137.7] Estimated Time

Unit step function

[5 60] s

S-2 Direct [4 12](1) [-142.5 -137.7] Estimated Position

Unit step function

[0.1 10] km

S-3 Shadow All( 2 ) [-158.5 -153,5] Estimated Time

Ramp [2 20] ns/s( 3 )

S-4 Shadow 1 [-158.5 -153,5] PSR measurement

Ramp [3.5 6.5] m/s

S-5 Shadow 1 [-158.5 -153,5] Estimated Position

Ramp [1 7.5] m/s( 3 )

Note (1): At least 4 PRNs of those in view should be spoofed to perform the S-1 and S-2 spoofing attacks;

Note (2): The number of spoofed PRNs is equal to the number of the satellites in view;

Note (3): The model value ranges for the estimated time and position assume HDOP compliant with Table 5-85.

[B.5] C.2 Integrity threat scenariosFor failure modes of GNSS systems see DO-208

ETSI

TS 103 246 V0.1.2 (2014-06)75

[Annex C] Annex <X> (informative): BibliographyThe annex entitled "Bibliography" is optional.

It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the document itself (see clause 12.2 of the EDRs http://portal.etsi.org/edithelp/Files/other/EDRs_navigator.chm).

It shall not include references mentioned in the document.

HistoryDocument history

V0.0.5 April 2014 Modified and commented by STF 474

V0.0.6 May 2014 Inputs from TAS etc.

V0.0.7 May 2014 Previous Annex 5 reinstated and renamed, and further corrections

V0.1.1 May 2014 Stable draft for Milestone A

V0.1.2 June 2014 Updates following comments from SCN9

ETSI

TS 103 246 V0.1.2 (2014-06)76

http://portal.etsi.org/edithelp/Files/other/EDRs_navigator.chm