skeleton · web viewtrajectory parameter value v 1 25 km/h v 2 100 km/h v 3 100 km/h d 1 250 m d 2...

TS 103 246 V0.11.33 (2014-09)

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.3 (2014-09)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 Organisational Partners.GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

ETSI

TS 103 246 V0.1.3 (2014-09)3


Contents

ETSI

TS 103 246 V0.1.3 (2014-09)4

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 [i.1] calls for a new and broader concept for location systems, taking into account hybrid solutions in which GNSS technologies are complemented with other technology sensors to improve robustness and the performance.

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

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

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

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.3 (2014-09)5

1 ScopeThis document firstly defines the Performance Features for the data provided by the GNSS-based Location System to an external application module. This document It then defines the performance requirements for these Performance Features .Features.

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

ETSI

TS 103 246 V0.1.3 (2014-09)6

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] ETSI TS 103 349 “Satellite Earth Stations and Systems (SES); Global Navigation Satellite Systems (GNSS)-based location systems; Functional requirements”.

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

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


ETSI

TS 103 246 V0.1.3 (2014-09)7

http://docbox.etsi.org/Reference


[i.11] [FFS] for 5G

ETSI

TS 103 246 V0.1.3 (2014-09)8

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

RJM: all to be reviewed below

Architecture: abstract representation of a communications system, in this case representing functional elements of the system and associated logical interfaces.

Availability: 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, authenticity).

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 that degrades the performance of this link. Jamming is a particular case of electromagnetic interference, where an interfering radio signal is deliberately broadcast to disrupt communication.

Integrity: a measure of the trust in the accuracy of the location-related data provided by the location system. It 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 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.

Jamming: The deliberate transmission of interference to disrupt processing 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 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 Service indicators (estimates of the position accuracy, reliability or authenticity).

ETSI

TS 103 246 V0.1.3 (2014-09)9

NOTE: This data 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 target: The physical entity on whose position the location system builds the location-related data. This entity may be mobile or stationary.

Privacy: 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 authorised 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 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: 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, authenticity flag.

Security: 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.

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

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

Time-to-first-fix: refers to the time needed by the receiver to perform the first position 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 INSPFA

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

All below to be reviewed

3GPP 3rd Generation Partnership Project

ETSI

TS 103 246 V0.1.3 (2014-09)10

ADAS Advanced Driver Assistance SystemsA-GNSS Assisted GNSSAL Alarm LimitBTS Base station Transceiver SystemD-GNSS Dynamic GNSS DoA 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 LevelIMU 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 Centre

ETSI

TS 103 246 V0.1.3 (2014-09)11

SUPL 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

PPD Personal Privacy Device

ETSI

TS 103 246 V0.1.3 (2014-09)12

4 Location System Performance Features4.1 GeneralThe location-related data delivered by GNSS-based Location Systems is required to meet a number of requirements, particularly in terms of positioning performance. In this document, these requirements are referred to as “Performance Features”.

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

These performance features encompass severalare general attributes and are described in the sub-clauses below. Clause 5Error: 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 the performance values for these metrics and the conditions in which they apply.

The specific performance metrics for these features are defined in Annex A.

The applicable conditions for the performance requirements are defined in Annex B.

Specific scenarios applicable to some performance features are defined in. Annex C.

The relationships of the

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

Performance Feature Performance Metrics Applicable ConditionsScenarios

Specific Scenarios

Horizontal Position Accuracy: A.1 B.1, B.2

Vertical Position Accuracy A.2 B.1, B.2

Availability of Required Accuracy A.3GNSS Time Accuracy A.34 B.1, B.2

Time-to-first-fix A.45 B.1, B.2

Position Authenticity A.56 B.1C.1 C.1

EMI Localisation Accuracy A.1, A.2, A.7Robustness to Interference A.86,, A.79 B.2

GNSS-Denied Accuracy A.1, A.2, A.4GNSS Sensitivity A.810 B.2

Position Integrity Protection Level A.911 B.2C.2 C.2

Position Integrity Time-to-Alert (TTA) N/APosition Integrity Time-to-Recover-from-Alert N/A

NOTE: additional features are for further study (FFS); other features identified but considered out of scope at present are:

Availability of Required Accuracy

EMI Localisation Accuracy

GNSS-Denied Accuracy

Position Integrity Time-to-Alert (TTA)

Position Integrity Time-to-Recover-from-Alert

e.g. Accuracy of speed and acceleration (horizontal and vertical).

ETSI

TS 103 246 V0.1.3 (2014-09)13

4.2 Performance Features4.2.1 Horizontal Position AccuracyThis Feature is the maximum error of the horizontal position of a Location target reported by the Location System.

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.

4.2.2[4.2.1] Vertical Position AccuracyThis Feature is the maximum error of the vertical position of a location target reported by the Location System.

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

[4.2.2] Availability of Required Accuracy

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

[4.2.4] GNSS Time Accuracy The 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.

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

Applications requiring synchronisation of assets distributed across wide geographical areas can use GNSS time as a reference, for example.

4.2.3[4.2.5] Time-to-First-Fix (TTFF)The TTFF is the time taken by the Location System to provide target (non-interferer??) position data starting either from the reception of a 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)

Different Classes of Rx.

4.2.4[4.2.6] Position AuthenticityRF spoofing may affect the analysis of location target signals resulting in false position data.

Position Authenticity gives a level of assurance that the data for a location target has been derived from real signals relating to the target.

ETSI

TS 103 246 V0.1.3 (2014-09)14

Robert Mort, 29/09/14,


is this a better definition?

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

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

[4.2.7] EMI Localisation Accuracy

[4.2.8] RF interference sources (deliberate or accidental) are significant factors in the overall performance of GNSS-based positioning services. For any service where increased monitoring of these sources is considered important, the determination of these sources’ positions can be required from the Location System.

[4.2.9] Therefore, EMI Localisation Accuracy is similar to position accuracy (horizontal and vertical) defined above, but applied where the location target is an interference source.

[4.2.10] This performance feature therefore corresponds to the maximum error with which the Location System identifies the origin of an interfering signal.

[4.2.11] The performance metrics used to characterise this performance feature are:

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

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

[4.2.14] “DoA accuracy”, defined in clause A.7 of Annex A.

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

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

[4.2.17]

[4.2.18] Robustness to InterferenceLocation Systems might be required to operate in constrained RF environments, in particular 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” 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

GNSS-Denied Accuracy

GNSS-Denied Accuracy refers to the ability of the Location System to maintain an appropriate quality of location-related data when the positioning terminal faces an outage in the GNSS signal reception.

ETSI

TS 103 246 V0.1.3 (2014-09)15

Such a feature is required for environments where a number of “GNSS-denied” areas are present, and where outage in service provision is not tolerable (for instance an automotive navigation device entering 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.

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

4.2.5[4.2.19] GNSS SensitivityGNSS Sensitivity refers to the minimum RF signal power at the receiver input required for a specified reliability of location-related data provision when either:

GNSS signals are first acquired, or

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

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

4.2.6[4.2.20] Position Integrity Protection LevelPosition Integrity is the ability of the Location System to measure the trust that can be placed in the accuracy of the location target position.

It 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].

ETSI

TS 103 246 V0.1.3 (2014-09)16

5

[6] Position Integrity Time-to-Alert (TTA)

[7] Position Integrity includes the ability of the Location System to provide timely and valid warnings that the location-related data must not be used for the intended location-based service. Such an alert is 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.

[8] 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.

[9] Position Integrity Time-to-Recover-from-Alert)

[10] Similar to above???

ETSI

TS 103 246 V0.1.3 (2014-09)17

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

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

Annex B defines the applicable conditions for these performance requirements.

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

The Performance Features are defined in each case for a range of operating conditions, where applicable, includingsuch as:

1. location target environments:

Open area

U rural,

urban,

suburban,

Asymmetric area

2. industrial.

[2.] Target motion types:

static

moving

[3.] GNSS receiver terminal types (Class A, B, C - representing classes of robustness to interference)

[4.] clear signal (non-interfered) or signal interference fault-free/faulty conditions etc.

These ranges of environments and receiver types have been chosen as the most representative of those commonly encountered today.

5.1[11.1] Horizontal Position AccuracyThe Horizontal Position data provided by the location system shall comply with the performance requirements defined for moving and static location target cases in the sub-clauses in clauses Error: Reference source not found and Error: Reference source not found below.

Operational conditionsLocation Target Environments are all those defined in Annex B.2.

ETSI

TS 103 246 V0.1.3 (2014-09)18

Error: Reference source not found gives the operational conditions used to define the performance and the masking parameters applicable for each of them.

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

ETSI

TS 103 246 V0.1.3 (2014-09)19

[11.1.1] Environment type

[11.1.2] Applicability

[11.1.3] Masking parameters

[11.1.4]

[11.1.7] x1

[11.1.8] x2

[11.1.9] x3

[11.1.10] Open area

[11.1.11] Yes

[11.1.12] See Error: Reference source not found

[11.1.13]

[11.1.14] Rural area

[11.1.15] Yes


[11.1.17] Suburban

[11.1.18] Yes


[11.1.20] Urban

[11.1.21] Yes

[11.1.22] See Error: Reference source not foun

[11.1.23]

ETSI

TS 103 246 V0.1.3 (2014-09)20

[11.1.24] Asymmetric area

[11.1.25] Yes


[11.1.27] Industrial area

[11.1.28] Yes


[11.1.30]

[11.1.31] Use case: Moving Location Target

5.1.1.1[11.1.31.1] Target movement

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

The trajectory parameters are:

Table 5-2: Location target trajectory 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.1.2[11.1.31.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 Class 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 in both directions.

ETSI

TS 103 246 V0.1.3 (2014-09)21

Table 5-3: Horizontal Position Accuracy, Open Area, Moving target

Metric Max position error (m)Class A Class B Class C

Mean error 0,2 0,5 8,4Standard 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 0,1 0,2 4,8Cross 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 0,2 0,3 5,4Along 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: Horizontal Position Accuracy, Rural Area, Moving target

Metric Max position error (m) – Rural Area

Class A Class B Class C

Mean value 0,4 1 9,6

Standard deviation [tbd] [tbd] [tbd]

67th percentile 0,5 1,1 12,2

95th percentile 0,9 2,1 19


Cross track error - Mean value 0,3 0,6 5,3

Cross track error - 67th percentile 0,3 0,8 6,5



Along track error - Mean value 0,2 0,4 6,6

Along track error - 67th

percentile 0,3 0,5 10,1


percentile 0,6 1 18,1



ETSI

TS 103 246 V0.1.3 (2014-09)22

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

Metric Max position error (m) – Suburban Area


Mean value 0,4 1,5 9,3



95th percentile 0,7 5 15,1


Cross track error - Mean value 0,2 1,1 5,1

Cross track error - 67th percentile 0,2 1 6,6



Along track error - Mean value 0,3 0,7 6,5







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

Metric Max position error (m) – Urban AreaClass A Class B Class C

Mean value 1,6 24,2 40,8Standard 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

ETSI

TS 103 246 V0.1.3 (2014-09)23

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

Metric Max position error (m) – Asymmetric AreaClass A Class B Class C

Mean value 0,5 12,1 31,7Standard 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

ETSI

TS 103 246 V0.1.3 (2014-09)24

[11.1.32] Table 5-8: Horizontal position Accuracy, Industrial Area, Moving target

ETSI

TS 103 246 V0.1.3 (2014-09)25

[11.1.33] Metric [11.1.34] Max position error (m) – Industrial Area

[11.1.36] Class A

[11.1.37] Class B

[11.1.38] Class C

[11.1.39] Mean value [11.1.40] 0,7

[11.1.41] 6,5

[11.1.42] 57,6

[11.1.43] Standard deviation

[11.1.44] [tbd]

[11.1.45] [tbd]

[11.1.46] [tbd]

[11.1.47] 67th percentile

[11.1.48] 0,8

[11.1.49] 5 [11.1.50] 75,2


[11.1.52] 1,7

[11.1.53] 23,2

[11.1.54] 96,7


[11.1.56] 2,4

[11.1.57] 44,1

[11.1.58] 100,2

[11.1.59] Cross track error - Mean value

[11.1.60] 0,5

[11.1.61] 5,1

[11.1.62] 33,6

[11.1.63] Cross track error - 67th percentile

[11.1.64] 0,6

[11.1.65] 3,7

[11.1.66] 46,5


[11.1.68] 1,6

[11.1.69] 19,2 [11.1.70] 77


[11.1.72] 2,2

[11.1.73] 40,9

[11.1.74] 81,8

[11.1.75] Along track error - Mean value

[11.1.76] 0,4

[11.1.77] 2,7

[11.1.78] 38,3

[11.1.79] Along track error - 67th

[11.1.80] 0 [11.1.81] 2 [11.1.82] 62

ETSI

TS 103 246 V0.1.3 (2014-09)26


Check std dev vs. mean

[11.1.33] Metric [11.1.34] Max position error (m) – Industrial Area

percentile ,5 ,1

[11.1.83] Along track error - 95th percentile

[11.1.84] 1 [11.1.85] 10,9

[11.1.86] 84,6

[11.1.87] Along track error - 99th percentile

[11.1.88] 1,4

[11.1.89] 22,1

[11.1.90] 88,5

[11.1.91]

[11.1.92] Use case: Static Location Target

5.1.1.3[11.1.92.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 Class of the location system.


Table 5-9: Horizontal Position Accuracy, Open area, Static target


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]

ETSI

TS 103 246 V0.1.3 (2014-09)27

Table 5-10: Horizontal Position Accuracy, Rural Area, Static target

Metric Max position error (m) – Rural Area


Mean value [tbd] [tbd] [tbd]


67th percentile [tbd] [tbd] [tbd]



Table 5-11: Horizontal Position Accuracy, Suburban Area, Static target

Metric Max position error (m) – Suburban Area







Table 5-12: Horizontal Position Accuracy, Urban Area, Static target




Table 5-13: Horizontal Position Accuracy, Asymmetric Area, Static target

Metric Max position error (m) – Asymmetric AreaClass A Class B Class C



ETSI

TS 103 246 V0.1.3 (2014-09)28

[11.2] Table 5-14: Horizontal Position Accuracy, Industrial Area, Static target

[11.3] Metric [11.4] Max position error (m) – Industrial Area

[11.6] Class A

[11.7] Class B

[11.8] Class C

[11.9] Mean value [11.10] [tbd]

[11.11] [tbd]

[11.12] [tbd]

[11.13] Standard deviation

[11.14] [tbd]

[11.15] [tbd]

[11.16] [tbd]

[11.17] 67th percentile

[11.18] [tbd]

[11.19] [tbd]

[11.20] [tbd]


[11.22] [tbd]

[11.23] [tbd]

[11.24] [tbd]


[11.26] [tbd]

[11.27] [tbd]

[11.28] [tbd]

[11.29]

[11.30] Vertical Position AccuracyThe system provides Vertical Position data provided by the location system that shall comply with the requirements defined for moving and static location target cases in the sub-clauses below.

Location Target Environments are all those defined in Annex B.2.

ETSI

TS 103 246 V0.1.3 (2014-09)29

5.1.2

[11.30.1] Operational conditions

[11.30.2] Error: 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.

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

ETSI

TS 103 246 V0.1.3 (2014-09)30




[11.30.7] to be used

[11.30.10] x1

[11.30.11] x2

[11.30.12] x3

[11.30.13] Open area

[11.30.14] Yes


[11.30.16]


[11.30.18] Yes


[11.30.20] Suburban

[11.30.21] Yes


[11.30.23] Urban

[11.30.24] Yes

[11.30.25] See Error: Reference source

[11.30.26]

ETSI

TS 103 246 V0.1.3 (2014-09)31


Clarify x values


[11.30.28] Yes



[11.30.31] Yes


[11.30.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].

The trajectory parameters are provided in tError: Reference source not found he table below.

Table 5-16: Location 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 Class of the location system


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

ETSI

TS 103 246 V0.1.3 (2014-09)32

Table 5-17 vertical Position Accuracy, open area, moving location target

Metric Max position error (m) – open areaClass A Class B Class C



Table 5-18 vertical Position Accuracy, rural area, moving location target

Metric Max position error (m) – rural Area







Table 5-19 vertical Position Accuracy, suburban area, moving location target

Metric Max position error (m) – suburban area







Table 5-20 vertical Position Accuracy, urban area, moving location target

Metric Max position error (m) – urban areaClass A Class B Class C



Table 5-21 vertical Position Accuracy, asymmetric area, moving location target

Metric Max position error (m) – asymmetric areaClass A Class B Class C



ETSI

TS 103 246 V0.1.3 (2014-09)33

[11.30.35] Table 5-22 vertical Position Accuracy, industrial area, moving location target

[11.30.36] Metric [11.30.37] Max position error (m) – industrial area

[11.30.39] Class A

[11.30.40] Class B

[11.30.41] Class C

[11.30.42] Mean value

[11.30.43] [tbd]

[11.30.44] [tbd]

[11.30.45] [tbd]

[11.30.46] Standard deviation

[11.30.47] [tbd]

[11.30.48] [tbd]

[11.30.49] [tbd]


[11.30.51] [tbd]

[11.30.52] [tbd]

[11.30.53] [tbd]


[11.30.55] [tbd]

[11.30.56] [tbd]

[11.30.57] [tbd]


[11.30.59] [tbd]

[11.30.60] [tbd]

[11.30.61] [tbd]

[11.30.62]

[11.30.63]



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:



ETSI

TS 103 246 V0.1.3 (2014-09)34

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

Metric Max position error (m) – Open AreaClass A Class B Class C



Table 5-24 vertical Position Accuracy, rural area, static location target

Metric Max position error (m) – rural Area







Table 5-25 vertical Position Accuracy, suburban area, static location target

Metric Max position error (m) – suburban area







Table 5-26 vertical Position Accuracy, urban area, static location target

Metric Max position error (m) – urban areaClass A Class B Class C



Table 5-27 Vertical Position Accuracy, asymmetric area, static location target

Metric Max position error (m) – asymmetric areaClass A Class B Class C



ETSI

TS 103 246 V0.1.3 (2014-09)35

[11.31] Table 5-28 vertical Position Accuracy, industrial area, static location target

[11.32] Metric [11.33] Max position error (m) – industrial area

[11.35] Class A

[11.36] Class B

[11.37] Class C

[11.38] Mean value

[11.39] [tbd]

[11.40] [tbd]

[11.41] [tbd]

[11.42] Standard deviation

[11.43] [tbd]

[11.44] [tbd]

[11.45] [tbd]


[11.47] [tbd]

[11.48] [tbd]

[11.49] [tbd]


[11.51] [tbd]

[11.52] [tbd]

[11.53] [tbd]


[11.55] [tbd]

[11.56] [tbd]

[11.57] [tbd]

[11.58]

[11.59]

[11.60] Availability of Required Accuracy

[11.61] [TBD]

[11.62] accuracy of which parameters??

[11.63] Level of accuracy??

[11.64] GNSS Time AccuracyThe GNSS Time provided by the location system shall comply with the performance requirements defined for moving and static location target cases in the sub-clauses below.

ETSI

TS 103 246 V0.1.3 (2014-09)36

The 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.Location Target Environments are all those defined in Annex B.2.

ETSI

TS 103 246 V0.1.3 (2014-09)37

5.1.4

[11.64.1] Operational conditions

[11.64.2] GNSS signals are defined as per clause B.1.2.

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

[11.64.4] Table 5-29 Environment applicability for “GNSS time Accuracy”

ETSI

TS 103 246 V0.1.3 (2014-09)38




[11.64.8]

[11.64.11] x1

[11.64.12] x2

[11.64.13] x3


[11.64.15] Yes


[11.64.17]


[11.64.19] Yes


[11.64.21] Suburban

[11.64.22] Yes


[11.64.24] Urban

[11.64.25] Yes

[11.64.26] See Error: Reference source not

[11.64.27]

ETSI

TS 103 246 V0.1.3 (2014-09)39


[11.64.29] Yes



[11.64.32] Yes


[11.64.34]



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 the table Error: Reference source not found below.

Table 5-30: Location 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 GNSS time Accuracyopen area, moving Location target

Metric Maximum time error (s)Class A Class B Class C

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

ETSI

TS 103 246 V0.1.3 (2014-09)40

Table 5-32 GNSS time Accuracyrural area, moving Location target

Metric Maximum time error (s)




Table 5-33 GNSS time Accuracysuburban area, moving Location target





Table 5-34 GNSS time Accuracyurban area, moving Location target



Table 5-35 GNSS time Accuracyasymmetric area, moving Location target



ETSI

TS 103 246 V0.1.3 (2014-09)41

[11.64.36] Table 5-36 GNSS time Accuracyindustrial area, moving Location target

[11.64.37] Metric

[11.64.38] Maximum time error (s)

[11.64.40] Class A

[11.64.41] Class B

[11.64.42] Class C

[11.64.43] Mean value

[11.64.44] [tbd]

[11.64.45] [tbd]

[11.64.46] [tbd]


[11.64.48] [tbd]

[11.64.49] [tbd]

[11.64.50] [tbd]

[11.64.51]





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:



Table 5-37 GNSS time Accuracyopen area, static location target



Table 5-38 GNSS time Accuracyrural area, static location target





ETSI

TS 103 246 V0.1.3 (2014-09)42

Table 5-39 GNSS time Accuracysuburban area, static location target





Table 5-40 GNSS time Accuracyurban area, static location target



Table 5-41 GNSS time Accuracyasymmetric area, static location target



[11.65] Table 5-42 GNSS time Accuracyindustrial area, static location target

[11.66] Metric

[11.67] Maximum time error (s)

[11.69] Class A

[11.70] Class B

[11.71] Class C

[11.72] Mean value

[11.73] [tbd]

[11.74] [tbd]

[11.75] [tbd]


[11.77] [tbd]

[11.78] [tbd]

[11.79] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)43

[11.80]

[11.81] Time-to-First-Fix (TTFF)Operational conditions

Applicable GNSS signals are defined inas per Annexclause B.1.

Location Target Environments are all those defined in Annex B.2.

.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”


[11.81.2] Yes


[11.81.4]

[11.81.5] Use case: Moving Target


The location target follows the trajectory described in Annex 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 the table Error: Reference source not found below.



Value



The TTFF 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


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

ETSI

TS 103 246 V0.1.3 (2014-09)44

Paolo Crosta, 29/09/14,

I didn't write this sentence and I don't understand it. Please explain or I'll remove it

Table 5-45 TTFFopen area, moving location target

Metric Performance requirement – Open AreaClass A Class B Class C

Max TTFF[s]Mean value 1.55[tbd] 2.5 [tbd]

Standard deviation 0.12[tbd] 0.4 [tbd]67th percentile 1.56[tbd] 2.7 [tbd]95th percentile 1.62[tbd] 3.3 [tbd]99th percentile 2.21[tbd] 3.8 [tbd]

Minimum Value 1.36[tbd] 1.8 [tbd]Maximum Value 2.27[tbd] 3.8 [tbd]

Max Horizontal Position Error [m]Mean value 6.40[tbd] 5.6 [tbd]


Table 5-46 TTFFrural area, moving location target

Metric Performance requirement – rural Area


Max TTFF [s]

Mean value [tbd] 2.7 [tbd]

Standard deviation [tbd] 0.4 [tbd]

67th percentile [tbd] 2.7 [tbd]



Minimum Value [tbd] 2.0 [tbd]

Maximum Value [tbd] 5.6 [tbd]

Max Horizontal Position Error [m]






ETSI

TS 103 246 V0.1.3 (2014-09)45

Table 5-47 TTFFsuburban area, moving location target

Metric Performance requirement – suburban Area


Max TTFF [s]






Minimum Value [tbd] 1.8 [tbd]

Maximum Value [tbd] 3.7 [tbd]







Table 5-48 TTFFUrban area, moving location target without interference

Metric Performance requirement – urban AreaClass A Class B Class C

Max TTFF[s]Mean value 1.47[tbd] 4.4 [tbd]





ETSI

TS 103 246 V0.1.3 (2014-09)46

Table 5-49 TTFFUrban area, moving location target with interference (medium level: -9 dB)

Metric Performance requirement – urban AreaClass A Class B Class C

Max TTFF[s]Mean value 3.81 3.24 [tbd]

Standard deviation 11.25 0.85 [tbd]67th percentile 2.34 3.33 [tbd]95th percentile 5.30 4.83 [tbd]99th percentile 81.28 6.52 [tbd]

Minimum Value 1.18 2.36 [tbd]Maximum Value 81.28 6.52 [tbd]

Max Horizontal Position Error [m]Mean value 30.55 22.95 [tbd]

Standard deviation 37.40 15.22 [tbd]67th percentile 32.50 28.80 [tbd]95th percentile 62.39 56.26 [tbd]99th percentile 236.00 69.28 [tbd]

Table 5-50 TTFFasymmetric area, moving location target without interference

Metric Performance requirement – asymmetric areaClass A Class B Class C

Max TTFF [s]Mean value 1.50 [tbd] 5.4 [tbd]





Table 5-51 TTFFasymmetric area, moving location target with interference (high-medium level: - 18.59 dB)


Max TTFF [s]Mean value 10.49 [tbd]

Standard deviation 6.59 [tbd]67th percentile 13.42 [tbd]95th percentile 21.50 [tbd]99th percentile 27.25 [tbd]

Minimum Value 1.20 [tbd]Maximum Value 27.25 [tbd]

Max Horizontal Position Error [m]Mean value 32.99 [tbd]


Table 5-52 TTFFindustrial area, moving location target

ETSI

TS 103 246 V0.1.3 (2014-09)47


ADD results for URBAN ASYMMETRIC AND INDUSTRIAL WITH INTERFERENCE

Metric Performance requirement – industrial area


Max TTFF[s]






Minimum Value [tbd] [tbd] [tbd]

Maximum Value [tbd] [tbd] [tbd]








5.1.5[11.81.6] Use case: Static Target


The location target is located in coordinates expressed in WGS84 [TBC] system: longitude = 4° 25′ 00″ E, latitude = 52° 12′ 00″ N.[TBD], latitude = [TBD].

ETSI

TS 103 246 V0.1.3 (2014-09)48


Comment PC: to verify if it is relevant for all the cases or just asymmetric (it needs additional tests)


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

the class of the location system.


Table 5-53 TTFFopen area, static location target

Metric Performance requirement – Open AreaClass A Class B Class C

Max TTFF[s]Mean value 1.55[tbd] 2.5[tbd] [tbd]

Standard deviation 0.12[tbd] 0.4[tbd] [tbd]67th percentile 1.56[tbd] 2.7[tbd] [tbd]95th percentile 1.62[tbd] 3.3[tbd] [tbd]99th percentile 2.21[tbd] 3.8[tbd] [tbd]

Minimum Value 1.36[tbd] 1.8[tbd] [tbd]Maximum Value 2.27[tbd] 3.8[tbd] [tbd]

Max Horizontal Position Error [m]Mean value 6.40[tbd] 5.6[tbd] [tbd]



ETSI

TS 103 246 V0.1.3 (2014-09)49

Table 5-54 TTFFrural area, static location target

Metric Performance requirement – rural Area


Max TTFF[s]















ETSI

TS 103 246 V0.1.3 (2014-09)50

Table 5-55 TTFFsuburban area, static location target

Metric Performance requirement – suburban Area


Max TTFF[s]















Table 5-56 TTFFUrban area, static location target

Metric(as per clause 4.2)

Performance requirement – urban AreaClass A Class B Class C



Minimum Value 1.17[tbd] 2.43[tbd] [tbd]Maximum Value 3.32[tbd] 5.87[tbd] [tbd]

Max Horizontal Position Error [m]Mean value 17.06[tbd] 29.4[tbd] [tbd]



ETSI

TS 103 246 V0.1.3 (2014-09)51

Table 5-57 TTFFasymmetric area, static location target



Standard deviation 1.73[tbd] 1.73[tbd] [tbd]67th percentile 1.37[tbd] [tbd] [tbd]95th percentile 7.35[tbd] [tbd] [tbd]99th percentile 9.14[tbd] [tbd] [tbd]

Minimum Value 1.28[tbd] [tbd] [tbd]Maximum Value 9.14[tbd] [tbd] [tbd]

Max Horizontal Position Error [m]Mean value 37.58[tbd] [tbd] [tbd]

Standard deviation 18.68[tbd] [tbd] [tbd]67th percentile 39.07[tbd] [tbd] [tbd]95th percentile 69.65[tbd] [tbd] [tbd]99th percentile 127.23[tbd] [tbd] [tbd]


Table 5-58 TTFFindustrial area, static location target

Metric Performance requirement – industrial area


Max TTFF[s]















ETSI

TS 103 246 V0.1.3 (2014-09)52

5.2[11.82] Position AuthenticityLocation systems which are able to authenticate estimated positions shall comply with the performance requirements described in clauses below.

This feature is defined in terms of a false alarm probability - what alarms, specified how?????

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, see [8]). The performance of the location system can be evaluated in terms of:

Probability of detection (PD ): the probability that the location system detects false GNSS signals during an RF spoofing attack;

Probability of false alarm (PFA ): the probability that the location system detects false GNSS signals with no RF spoofing attack.

The performance specification is organised as follows:

Two main use cases are considered: 1) moving location target and static location target, 2) static location target. and moving location target

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

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

performance are is measured by PFA ;

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

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

5.2.1[11.82.1] Operational conditionsApplicable GNSS signals are 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 Annex B.2), either in clear or interference scenarios.

ETSI

TS 103 246 V0.1.3 (2014-09)53

5.2.2 in fault-free conditions are defined in Error: Reference source not found below.

[11.82.2] Table 5-59 Environment applicability for feature “position authenticity”

ETSI

TS 103 246 V0.1.3 (2014-09)54




[11.82.6]

[11.82.9] x1

[11.82.10] x2

[11.82.11] x3


[11.82.13] Yes


[11.82.15]


[11.82.17] Yes


[11.82.19] Suburban

[11.82.20] Yes


[11.82.22] Urban

[11.82.23] Yes

[11.82.24] See Error: Reference source

[11.82.25]

ETSI

TS 103 246 V0.1.3 (2014-09)55


[11.82.27] Yes



[11.82.30] Yes


[11.82.32]

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

Target movement

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

The location target moves on a straight trajectory at a uniform speed, equal to 50 km/h.

5.2.2.1 Clear ScenarioThe trajectory parameters are provided in Error: Reference source not found below.

Table 5-60: Location target movement parameters


Value

v1 25 km/h

v2 100 km/h

v3 100 km/h

d1 250 m

D2 250 m

Performance requirement

The f PFA alse alarm probability achieved by the location system “position authenticity” function shall meet the level specified in Error: Reference source not found the table below, depending on:

the cClass of the location system.

ETSI

TS 103 246 V0.1.3 (2014-09)56


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

Table 5-61: PFA requirementAuthenticity 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 5[TBD] seconds.

[11.82.33.1] Use case: Moving location target, Interference faulty Scenarios

Target 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 PD .

spoofing attempt detection performance.

For a given spoofinginterference scenario (see Table 5-102), the table below 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 interference scenario;

the PD 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.3 (2014-09)57

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

SpoofingInterference scenario

Minimum TSP

[dBW]

Minimum Error Minimum PD Performance requirement – open

areaClass A Class B Class C

M-1 -143.5[tbd] 0.5510-6

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

-142.5[tbd] 0.6610-6 s [tbd] 0.92[tbd] 0.85[tbd] 0.8[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]

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

S Minimu Minimu Performance requirement – rural area


M [tbd] [tbd] [tbd] [tbd] [tbd]

[tbd] [tbd] [tbd] [tbd] [tbd]

















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

S Minimu Minimu Performance requirement – suburban area

ETSI

TS 103 246 V0.1.3 (2014-09)58

poofing scenario

m TSP m Error




















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

S Minimu Minimu Performance requirement – urban area







ETSI

TS 103 246 V0.1.3 (2014-09)59














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

S Minimu Minimu Performance requirement – asymmetric area


















ETSI

TS 103 246 V0.1.3 (2014-09)60

-6



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

S Minimu Minimu Performance requirement – industrial area




















Note 1: Scenarios M-4 and M-5 are FFS.

Note:

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

5.2.3[11.82.34] Use case: Static Location Target The location target is static with reference coordinates expressed in WGS84 system: longitude = 7.0528 deg, latitude = 43.6169 deg..

5.2.3.1 Clear Fault-free scenario

Target position

ETSI

TS 103 246 V0.1.3 (2014-09)61



The false alarm probability achieved by the location system “position authenticity” function shall meet the level specified in the table Error: Reference source not foundError: Reference source not found below, depending on:

the cClass of the location system.


Table 5-68: Authenticity False Alarm performance

Environment type Maximum False Alarm probability


Open area 510-4 0 [TBC]

210-3 0 [TBC]

10-2 0 [TBC]

Rural area 0 0 0

Suburban 0 0 0

Urban 0 0 0

Asymmetric area 0 0 0

Industrial area 0 0 0

Note: In addition to the requirements above, the latency to provide authenticity shall not exceed 5 seconds.

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

[11.82.34.1] Use case: Static Location Target InterferenceFaulty scenarios

Target position



The location system shall meet the following performance requirements in terms of spoofing attempt detection performance.

For a given spoofinginterference 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 isshall be able to detect. This required ability is given as a function of:



ETSI

TS 103 246 V0.1.3 (2014-09)62

Table 5-69: ProbabiliPD ty of detection performance, open area, static location target

SpoofingInterference scenario

Minimum TSP

Minimum Error Minimum PD Performance requirement – open

areaClass A Class B Class C

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]


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

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

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

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



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

S Minimu Minimu Performance requirement – rural area


S [tbd] [tbd] [tbd] [tbd] [tbd]



















ETSI

TS 103 246 V0.1.3 (2014-09)63

-7



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

S Minimu Minimu Performance requirement – suburban area























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

S Minimu Minimu Performance requirement – urban area




ETSI

TS 103 246 V0.1.3 (2014-09)64




















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

S Minimu Minimu Performance requirement – asymmetric area












ETSI

TS 103 246 V0.1.3 (2014-09)65

-4












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

S Minimu Minimu Performance requirement – industrial area




















ETSI

TS 103 246 V0.1.3 (2014-09)66




Note 1: Scenarios S-1 and S-2 are FFS.

Note 2: In addition to the requirements above, the latency to provide authenticity shall not exceed 5 seconds.

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

[11.83] EMI Localisation Accuracy

[11.84] See 4.2.8.

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

[11.86]

[11.87]

[11.88] Robustness to InterferenceWhat happened to:

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

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

Jamming is considered here

The performance parameters which characterise the robustness to interference are the following:

Position fix availability as a function either of the jammer distance or the signal power ratio between jamming- signal to-and GNSS signal power ratio (J/S)

Position fix accuracy (3D)

The robustness to interference is assessed by considering:

OPEN SKY condition (vehicular motion)

the interference sources as defined in Error: Reference source not foundXXXX

Two Jamming cases are specified with 10 and 20 MHz FM deviation. with

5.2.4Case 1: 20 MHz FM deviation in the FM modulation

ETSI

TS 103 246 V0.1.3 (2014-09)67


Horizontal error only?



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.

Metric Performance requirement – suburban AreaClass A Class B Class C

maximum J/S (dB)maximum J/S

83 dB [tbd]

minimum Jammer distance (m)minimum Jammer distance

28 m



[11.88.1] Case 2: 10 MHz FM deviation in the FM modulation

Metric Performance requirement – suburban AreaClass A Class B Class C

maximum J/S (dB) 64 dB [tbd]minimum Jammer distance (m) 87 m



Notes:

1. the position error is a 3D position error computed for all the J/S cases lower than the identified maximum J/S

[2.] the jammer bandwidth seems to play a role in the receiver impact: it looks like the same interference but with a narrower BW affects more to the Rx. After the RX filter (limited bandwidth) the continuous FM modulated signal results as pulsed interference that is active only when the instantaneous frequency of the jammer is within the receiver bandwidth. The jammer case J#2 results then in a higher duty cycle.

[3.] This kind of jammer does not impact GLONASS satellites because the frequency range is around 1598.0625-1605.375 MHz +/- 0.511 MHz. A similar problem could be for Beidou receivers. In order to affect impact also this constellation also, the Jammer frequency deviation should be increased to 40 MHz.

2.[4.] 0 dBi antenna vs beamforming (4 elements with CRPA)

ETSI

TS 103 246 V0.1.3 (2014-09)68

[11.89] GNSS-Denied Accuracy

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

[11.91] Operational conditions

[11.92] Error: Reference source not found below provides the operational conditions used to define the required performance for GNSS-Denied Accuracy, and the masking parameters tuning applicable for each of them.

[11.93]

[11.94] Table 5-75: Environment applicability for feature GNSS-Denied Accuracy

ETSI

TS 103 246 V0.1.3 (2014-09)69

[11.95] Environment type

[11.96] Applicability

[11.97] Masking parameters

[11.98]

[11.99] Open area

[11.100] Yes

[11.101] Special

[11.102] Rural area

[11.103] Yes

[11.104] Special

[11.105] Suburban

[11.106] Yes

[11.107] Special

[11.108] Urban

[11.109] Yes

[11.110] Special

[11.111] Asymmetric area

[11.112] Yes

[11.113] Special

[11.114] Industrial area

[11.115] Yes

[11.116] Special

ETSI

TS 103 246 V0.1.3 (2014-09)70

[11.117]

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

[11.119] Special masking conditions

[11.120] For Indoor: Modify + add table

[11.121] In order to measure the ability of a location system to maintain the location target position determination within GNSS-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.

[11.122] Figure B-1. Sky attenuation conditions definition method.

[11.123]

[11.124]

[11.125] Use case: Moving Target

[11.126] Target movement

[11.127] 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.3 (2014-09)71

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

[11.129] Table 5-76: Location target movement parameter

ETSI

TS 103 246 V0.1.3 (2014-09)72

[11.130] Traje

ctory parameter

[11.131] Value

[11.132] v1

[11.133] 25 km/h

[11.134] v2

[11.135] 100

km/h

[11.136] v3

[11.137] 100

km/h

[11.138] d1

[11.139] 250 m

[11.140] D2

[11.141] 250 m

ETSI

TS 103 246 V0.1.3 (2014-09)73

[11.142]

[11.143] Performance requirement

[11.144] No time error requirements – see 4.10 ??

[11.145] 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:

[11.146] the Class of the location system

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

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

[11.149] Table 5-77: GNSS-Denied Accuracy, Open Area

ETSI

TS 103 246 V0.1.3 (2014-09)74

[11.150] Metric [11.151] Max position error (m) after covered area crossing – Open Area

[11.153] Class A

[11.154] Class B

[11.155] Class C

[11.156]

[11.157] Horizont

al Position error

[11.158] Mean value [11.159] [tbd] [11.160] [tbd] [11.161] [tbd

]

[11.163] Std value [11.164] [tbd] [11.165] [tbd] [11.166] [tbd

]

[11.168] Max value [11.169] [tbd] [11.170] [tbd] [11.171] [tbd

]

[11.172]

[11.173] Cross

track error


]


]


]

[11.188]

[11.189] Along

track error


]


]


]

[11.204] [11.206] Mean value

[11.207] [tbd] [11.208] [tbd] [11.209] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)75

[11.150] Metric [11.151] Max position error (m) after covered area crossing – Open Area

[11.205] Vertical

Position error


]


]

ETSI

TS 103 246 V0.1.3 (2014-09)76

[11.220]

[11.221] Table 5-78: GNSS-Denied Accuracy, Rural Area

ETSI

TS 103 246 V0.1.3 (2014-09)77

[11.222] Metric [11.223] Max position error (m) after covered area crossing – rural area

[11.225] Class A

[11.226] Class B

[11.227] Class C

[11.228]

[11.229] Horizont

al Position error


]


]


]

[11.244]

[11.245] Cross

track error


]


]


]

[11.260]

[11.261] Along

track error


]


]


]

[11.276] [11.278] Mean value

[11.279] [tbd] [11.280] [tbd] [11.281] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)78

[11.222] Metric [11.223] Max position error (m) after covered area crossing – rural area

[11.277] Vertical

Position error


]


]

ETSI

TS 103 246 V0.1.3 (2014-09)79

[11.292]

[11.293] Table 5-79: GNSS-Denied Accuracy, Suburban Area

ETSI

TS 103 246 V0.1.3 (2014-09)80

[11.294] Metric [11.295] Max position error (m) after crossing covered area – suburban area

[11.297] Class A

[11.298] Class B

[11.299] Class C

[11.300]

[11.301] Horizont

al Position error


]


]


]

[11.316]

[11.317] Cross

track error


]


]


]

[11.332]

[11.333] Along

track error


]


]


]

[11.348] [11.350] Mean value

[11.351] [tbd] [11.352] [tbd] [11.353] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)81

[11.294] Metric [11.295] Max position error (m) after crossing covered area – suburban area

[11.349] Vertical

Position error


]


]

ETSI

TS 103 246 V0.1.3 (2014-09)82

[11.364]

[11.365] Table 5-80: GNSS-Denied Accuracy, Urban Area

ETSI

TS 103 246 V0.1.3 (2014-09)83

[11.366] Metric [11.367] Max position error (m) after covered area crossing – urban area

[11.369] Class A

[11.370] Class B

[11.371] Class C

[11.372]

[11.373] Horizont

al Position error


]


]


]

[11.388]

[11.389] Cross

track error


]


]


]

[11.404]

[11.405] Along

track error


]


]


]

[11.420] [11.422] Mean value

[11.423] [tbd] [11.424] [tbd] [11.425] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)84

[11.366] Metric [11.367] Max position error (m) after covered area crossing – urban area

[11.421] Vertical

Position error


]


]

ETSI

TS 103 246 V0.1.3 (2014-09)85

[11.436]

[11.437] Table 5-81: GNSS-Denied Accuracy, Asymmetric Area

ETSI

TS 103 246 V0.1.3 (2014-09)86

[11.438] Metric [11.439] Max position error (m) after covered area crossing – asymmetric area

[11.441] Class A

[11.442] Class B

[11.443] Class C

[11.444]

[11.445] Horizont

al Position error


]


]


]

[11.460]

[11.461] Cross

track error


]


]


]

[11.476]

[11.477] Along

track error


]


]


]

[11.492] [11.494] Mean value

[11.495] [tbd] [11.496] [tbd] [11.497] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)87

[11.438] Metric [11.439] Max position error (m) after covered area crossing – asymmetric area

[11.493] Vertical

Position error


]


]

ETSI

TS 103 246 V0.1.3 (2014-09)88

[11.508]

[11.509] Table 5-82: GNSS-Denied Accuracy, Industrial Area

ETSI

TS 103 246 V0.1.3 (2014-09)89

[11.510] Metric [11.511] Max position error (m)after covered area crossing – industrial area

[11.513] Class A

[11.514] Class B

[11.515] Class C

[11.516]

[11.517] Horizont

al Position error


]


]


]

[11.532]

[11.533] Cross

track error


]


]


]

[11.548]

[11.549] Along

track error


]


]


]

[11.564] [11.566] Mean value

[11.567] [tbd] [11.568] [tbd] [11.569] [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)90

[11.510] Metric [11.511] Max position error (m)after covered area crossing – industrial area

[11.565] Vertical

Position error


]


]

[11.580]

[11.581]

[11.582] GNSS SensitivityGNSS Sensitivity is defined in terms of the minimum RF signal power at the receiver input required for a specified reliability for of correct 1) :

tracking and 2) acquisition.

3. The Tracking Sensitivity as the minimum received signal power……………

4. The Acquisition Sensitivity is defined as the minimum received signal power which allows the receiver to have a first fix within 300s with a probability greater than zero.

5.2.5 Operational conditionsThe table below defines the operational conditions for “GNSS sensitivity” and the masking parameters applicable for each of them.

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

Environment type Applicability Masking parameters

Open area Yes Special: see belowUrban No -

Asymmetric area Yes Special: see below

5.2.5.1 Special masking conditions

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

consider use cases are defined in corresponding to the operational environments:

- “open Area”

- and “asymmetric area”

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

ETSI

TS 103 246 V0.1.3 (2014-09)91


5.2.5.2 Initial GNSS time estimate

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

[TBD]

5.2.6 Performance requirementReceiver

Class A Class B Class CMetric Scenario: Open Area Asymmetric Area

Tracking Sensitivity -157 (38 %) -146 (42 %) [tbd]Acquisition Sensitivity -157 (78 %) -142 (45 %) [tbd]

ETSI

TS 103 246 V0.1.3 (2014-09)92

5.2.7 Operational conditions

[11.582.1] Error: 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.

[11.582.2] Table 5-84: Environment applicability for “GNSS sensitivity”


[11.582.4] Applicabil

ity


[11.582.6]


[11.582.8] Yes

[11.582.9] Special


[11.582.11] No

[11.582.12] -

[11.582.13] Suburban

[11.582.14] No

[11.582.15] -

[11.582.16] Urban

[11.582.17] No

[11.582.18] -

[11.582.19] Asymmetri

c area

[11.582.20] Yes

[11.582.21] Special

[11.582.22] Industrial

area

[11.582.23] No

[11.582.24] -

ETSI

TS 103 246 V0.1.3 (2014-09)93

[11.582.25]

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

[11.582.27] Special masking conditions

[11.582.28] 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:

[11.582.29] consider use cases corresponding to the operational environment:

[11.582.30] “open Area”

[11.582.31] and “asymmetric area”

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

[11.582.33]

[11.582.34] GNSS time initial estimate

[11.582.35] Open area conditions correspond to fine estimate, asymmetric conditions correspond to coarse estimate

[11.582.36] [TBD]

[11.582.37]

[11.582.38] Tracking only below??

[11.582.39] Use case: Moving Target

5.2.7.1[11.582.39.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 the table below with different values depending on the type of user.



Outdoor (vehicle)Value

Indoor (pedestrian)

v1 25 km/h 1 km/hv2 100 km/h 4 km/hv3 100 km/h 4 km/hd1 250 m 10 mD2 250 m 10 m

ETSI

TS 103 246 V0.1.3 (2014-09)94



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-86: GNSS sensitivity, Open area (fine time assistance)

Metric minimum RF signal power at the receiver input (dBW)Class A Class B Class C

x1 [tbd] [tbd] [tbd]x2 [tbd] [tbd] [tbd]x3 [tbd] [tbd] [tbd]

Table 5-87: GNSS sensitivity, asymmetric area (coarse time assistance)

Metric minimum RF signal power at the receiver input (dBW)Class A Class B Class C

x1 [tbd] [tbd] [tbd]x2 [tbd] [tbd] [tbd]x3 [tbd] [tbd] [tbd]

5.2.8[11.582.40] Use case: Static Target[TBD]

5.2.8.1[11.582.40.1] Target Position

[TBD]


[TBD]

Position Integrity Protection Level

[TBD]

NOTE: failure modes of GNSS systems are considered in C.2

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

Assigned Test Range

Assigned MI Failure

Probability

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


ETSI

TS 103 246 V0.1.3 (2014-09)95


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

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

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

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

Position Integrity Alarm Limit and TTA

[TBD]

ETSI

TS 103 246 V0.1.3 (2014-09)96

Annex A (normative): Definition of Performance MetricsThis Annex defines how performance shall be determined for each Performance Feature. 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 AccuracyThe horizontal position accuracy is computed using the projection of the position error on the horizontal plane containing the location target true position (i.e. 2-dimensional projection).

The metrics used in order to statistically characterise this accuracy are 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 location target

Let be the position estimates collected over a specified time interval (N samples), projected on the local horizontal plane containing the 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 location target, the following metrics apply:

Along-track error

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 location target true position.

The metrics are used defined in the same way as for Horizontal Position Accuracy above, with “vertical position” substituted for “horizontal position”.

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

ETSI

TS 103 246 V0.1.3 (2014-09)97

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 location target

Let be the position estimates collected over a specified time interval (N samples), projected on the local vertical axis containing the 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 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:

Availability of required accuracy

The 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, expressed in percent.

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

The required quality of service can include an accuracy indicator and a Protection Level etc.

A.3 GNSS Time AccuracyThe 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.

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.3 (2014-09)98


Align with 5.4

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

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

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

mean value of the TTFF computed over a specified number of trials.

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.5 Position AuthenticityThe authenticity performance is characterised by the ability of the system to identify spoofing attempts 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.

ETSI

TS 103 246 V0.1.3 (2014-09)99


Clarify text to define how performance is defined

[A.6] Direction of Arrival (DoA) Accuracy

[A.7] The DoA accuracy is the error between the actual DoA of a signal from a given interference source, and the DoA of this same signal estimated by the location system.

[A.8] The metrics used in order to statistically characterise this quantity are:

[A.9] Mean value of the DoA error computed over a specified time interval.

[A.10] Standard deviation of the DoA error computed over a specified time interval.

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

[A.12]

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

A.6[A.14] Recovery time of normal performance after termination of interference

Considers recovery after front-end saturation.

Includes Pulse, CW and wideband.

A.7[A.15] GNSS sensitivityInclude acquisition and tracking sensitivity, reference 3GPP.

A.8[A.16] Position Integrity Protection LevelThe integrity performance is characterised by:

The position protection level (PPL) expressed in metres

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.3 (2014-09)100


Is this relevant?

[Annex B] (normative): Applicable conditions

This section describes the conditions applicable to the definition of the performance requirements given in clause 5Error: Reference source not found.. These conditions concern:

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

the operational environments applicable to the location system performance.

the moving target scenario description.

[B.1] External Location Systems GeneralParametersA.8.1[B.1.1] GNSS systems parameters

A.8.1.1[B.1.1.1] GNSS Systems constellation geometry and signal parameters

Error: Reference source not found GNSS systems applicable to below provides the reference documents applicable in the frame of the present performance specifications are shown below including. 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-88 – 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

A.8.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].

A.8.2[B.1.2] SBAS systems parameters

A.8.3[B.1.3] Cellular systems parametersfind a parameter equivalent to HDOP range to fix network properties. See 3GPP specs.

ETSI

TS 103 246 V0.1.3 (2014-09)101

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

A.9[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.9.1[B.2.1] Operational environments definitionTable 5-89 – Operational environments definition

Operational environment

typeMasking conditions Multipath

LevelInterference

levelMagnetic

conditions

Telco beacons

distributionPolar plot Zone Atten

Open Area Open skyx1 0 dB

Null Null NominalRural

distributionx2 >100dB

Urban AreaUrban

Canyonx1 0 dB

High Medium DegradedUrban

distributionx2 >100dB

Asymmetric Area

Asymmetric visibility

x1 15 dB

High Medium DegradedUrban

distributionx2 >100dBx3 >100dB

Note: for all of the above environments, the antenna gain is assumed to be 0dBi.

A.9.2 GNSS-related environment characteristicsThe 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 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.

ETSI

TS 103 246 V0.1.3 (2014-09)102

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])

A.9.2.1[B.2.1.1] Sky Attenuation Conditions

Applicable sky conditions are as follows.

Figure 5-1 - 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 attenuation conditions are defined here below

Remove elevation from all. Replace by table simplifying all.

ETSI

TS 103 246 V0.1.3 (2014-09)103

Figure 5-2 - Open Sky plot. Table 5-90 – Open sky definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

Background Area out of Zone A

Figure 5-3 – Light masking plot. Table 5-91 – 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.3 (2014-09)104


Make x values clear

Figure 5-4 – Dense masking plot Table 5-92 – 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-5 – Urban canyon plot. Table 5-93 – 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.3 (2014-09)105

Figure 5-6 – Asymmetric visibility plot Table 5-94 – Asymmetric visibility definition

ZoneElevation range

(deg)Azimuth range

(deg)A 0 – 5 0 – 360

B 5 - 60 30 – 150

C 10 – 60 230 - 310


A.9.2.2[B.2.1.2] Multipath Scenario

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 the table below.

Table 5-95 – 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.

The table 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.3 (2014-09)106


Which?

Table 5-96 – 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/Modernised 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-97 – Ratio between Carrier Frequency and Chip Rate

System Signals N

GalileoE1 1540

E5a 115E5b 118

GPS/Modernised GPS

L1 C/A 1540L1C 1540L2C 1200L5 115

GLONASS G1 3135.03 + k 1.10G2 2438.36 + k 0.86

Note: Parameter “k” above is the GLONASS frequency channel number.

A.9.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 noise power density after 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.3 (2014-09)107

Table 5-98 – Interference levels

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

A.9.3[B.2.2] Additional environment characteristicsFurther 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.

A.9.3.1[B.2.2.1] Telecommunication beacon deployment

According to [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].

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.3 (2014-09)108

B.2.2.1.4 DVB transmitters characteristics and deployment

Relevant standard reference for , 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.

A.9.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).

The table below specifies the jamming signals used as interference sources for the jamming scenarios considered in clauses 5.7 and 5.8. The definition of the jammer is based on the interference models of some PPDs (Personal Privacy Devices) as described in literature.

The jamming signal is a FM modulated signal with a sine waveform with a frequency of the waveform of the FM interfering signal equal to 50 kHz and a deviation depending on the interference bandwidth (10 and 20 MHz).

Table 5-99 – Interference source definition

Class Centre Frequency

Bandwidth Sweep time Peak [dBm]

J#1: Chirp signal with one saw-tooth function

1575.42 MHz 20 MHz 20 µs -9.6

J#2: Chirp signal with one saw-tooth function

1575.42 MHz 10 MHz 20 µs -9.6

Note. The bandwidth is considered as a 3 dB bandwidth around the specified centre frequency, i.e. the first case in Table 5-99 (20 MHz) corresponds to the range of frequencies [1565.42, 1585.42] MHz.

The actual power of the jamming source accounts for the free space propagation losses (as described in Figure 5-7) and the initial jammer power reported in Table 5-99. Besides, the relative Doppler is negligible if compared to the frequency range swept by the jammer.

ETSI

TS 103 246 V0.1.3 (2014-09)109

Figure 5-7 – Free space propagation loss with respect to the jammer distance

A.9.3.3[B.2.2.3] Magnetic conditions

[TBD]

ETSI

-150 -100 -50 0 50 100 150

-80

-75

-70

-65

-60

-55

-50

-45

X: 3.003Y: -45.94

Distance [m]

free

spac

e pr

opag

atio

n Lo

ss [d

B]

Jammer Overtaking

X: 100Y: -76.39

TS 103 246 V0.1.3 (2014-09)110

[B.3] Operational environments definition

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

[B.5] Include assumption of antenna gain (0dBi)

[B.6] Note: Environments applicable to users are defined in section 5.

[B.7] Table 5-100 – Operational environments definition

ETSI

TS 103 246 V0.1.3 (2014-09)111


[B.8] Oper

[B.9] Masking conditions

[B.10] Multip [B.11] I

[B.12] Magn [B.13] T[B.15] P

[B.16] Zo

[B.17] Atte

[B.22] Ope [B.23] O

[B.24] x1

[B.25] 0 dB

[B.26] N[B.27] N [B.28] N[B.29] R[B.32] x2

[B.33] (tota

[B.38] Urba [B.39] U

[B.40] x1

[B.41] 0 dB

[B.42] H[B.43] M[B.44] D[B.45] U[B.48] x2

[B.49] Tota

[B.54] Asy [B.55] A

[B.56] x1

[B.57] 15

[B.58] H[B.59] M[B.60] D[B.61] U

[B.64] x2

[B.65] Tota

[B.72] x3

[B.73] Tota

[B.78] Refer to parameters above

[B.79]

[B.80] Moving Target Scenario The diagram below describes the a reference trajectory used in clause 5.

ETSI

TS 103 246 V0.1.3 (2014-09)112

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 – Location target trajectory

Parameter (m)X 1440Y 940R 20

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

ETSI

X

YA1

A2

A3

A4

A5A6A7

A8

A12

A11

A10

A9

A16A15A14A13

R

Y

A8{0;0;0}

D2D1

TS 103 246 V0.1.3 (2014-09)113

Figure 5-9 – Location target speed profile

Figure 5-10 – Location target speed profile

Specific values of parameters d1, D2, v1, v2 and v3 are defined for each Performance Feature in clause Error: Reference source not found 5.

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

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

B.1.1[C.1.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[C.1.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[C.1.1.2] Scenarios chronology

All the considered scenarios follow the sequence of events depicted in the figure belowError: Reference source not found:

ETSI

TS 103 246 V0.1.3 (2014-09)114

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

Figure 5-12 - 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 Ts and the end of the scenario.

B.1.1.3[C.1.1.3] Scenario parameters

The scenarios are defined by the following list of parameters

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

misleading 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. Misleading information category: determines the type of misleading information based on the impact of the spoofing attack to the data at the output of the GNSS sensor.

tTarget 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 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 consideringation of the overall context (i.e. GNSS constellation geometry, current GNSS time, and GNSS 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 falsecounterfeit GNSS signals are radiated towards the GNSS sensor, and the power received by the GNSS sensor is in line with the TSP specified.

ETSI

TS 103 246 V0.1.3 (2014-09)115


????

Shadowed spoofed GNSS signal introduction

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 lose loses 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 Error: Reference source not found figure below 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-13 - Effects of introduction of Spoofing on PRN signals

Figure 5-14 - Effects of shadowed spoofing 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 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:

[dBW]

where 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 authenticity performance.

ETSI

TS 103 246 V0.1.3 (2014-09)116

C.1.1.3.3 Misleading information category

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

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-15 - Threat scenario error models

Figure 5-16 - Threat scenario error models

These models are applied for each type of misleading information according to Error: Reference source not found the table below, where:

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

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

Table 5-101 - 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 authenticity 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.3 (2014-09)117

Figure 5-17 - Threat scenario trajectory

Figure 5-18 - 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[C.1.2] Threat scenarios for moving targetsThe threat scenarios listed in Error: Reference source not found the table below 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-102 - Threat scenario for moving targets

Scenario identifier

Attack class

Number of spoofed PRNs

TSP range(dBW)

Misleading information category

Error model

Model value range

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

Estimated Time Ramp [2 20] ns/s(2)

M-2 Shadow 4 [-148.5 -144.5]

PSR measurement Ramp [3.5 6.5] m/s

M-3 Shadow 4 [-148.5 -144.5]

Estimated Position Ramp [1 7.5] m/s(2)

M-4 Direct [4 12](3) [-142.5 -137.7]

Estimated Time Unit step function

[5 60] s

M-5 Direct [4 12](3) [-142.5 -137.7]

Estimated Position Unit step function

[0.1 10] km

Scenario identifier

Attack class


TSP range

(dBW)


Error model

Model value range

M-1 Shadow P [tbd] Time estimates

Ramp [tbd] s/s

M-2 Shadow 1 [tbd] PSR measurement

Ramp [tbd] m/s

M-3 Shadow P [tbd] Position estimates

Ramp [tbd] m/s

M-4 Direct P [tbd] Position estimates

Unit step function

[tbd] m

M-5 Direct P [tbd] Position estimates

Ramp [tbd] m/s

ETSI

TS 103 246 V0.1.3 (2014-09)118

M-6 Direct P [tbd] Time estimates

Ramp [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 compliance with Table 5-88.

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 is [TBD].

B.1.3[C.1.3] Threat scenarios for static targetsThe threat scenarios listed in Error: Reference source not found the table below are defined for static targets.

Pre-conditions defined in clause C.1.1.1 apply.

Table 5-103 - Threat scenario for static target

Scenario identifier

Attack class


TSP range(dBW)


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 compliance with Table 5-88.

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

ETSI

TS 103 246 V0.1.3 (2014-09)119

Annex C[Annex D] (informative): Bibliography

The 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 474V0.0.6 May 2014 Inputs from TAS etc.V0.0.7 May 2014 Previous Annex 5 reinstated and renamed, and further correctionsV0.1.1 May 2014 Stable draft for Milestone AV0.1.2 June 2014 Updates following comments from SCN9V0.1.3 Sep 2014 Overall revision after de-scoping, inclusion of parameters etc.

ETSI

TS 103 246 V0.1.3 (2014-09)120

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