docbox.etsi.org€¦ · Web viewA location system central facility consists of a number of...

TS 103 247 V<0.0.3> (<2014-02>)

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

based location systems;Reference architecture

<<

TECHNICAL SPECIFICATION

ReferenceDTS/SES-00331

KeywordsGNSS, location, MSS, navigation, architecture,

receiver, 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.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)2

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

http://www.etsi.org/

ContentsContents...............................................................................................................................................................3

Intellectual Property Rights.................................................................................................................................6

Foreword.............................................................................................................................................................7

1 Scope.........................................................................................................................................................8

2 References.................................................................................................................................................92.1 Normative references...........................................................................................................................................92.2 Informative references.........................................................................................................................................9

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

4 Services provided by location systems – Stage 1 description................................................................144.1 Functional requirements....................................................................................................................................144.1.1 Location system definition...........................................................................................................................144.1.2 High level requirements...............................................................................................................................154.1.3 location-related information.........................................................................................................................164.1.3.1 Geographic location...............................................................................................................................164.1.3.2 Velocity and acceleration.......................................................................................................................174.1.4 Quality of service.........................................................................................................................................174.1.4.1 Horizontal Accuracy..............................................................................................................................174.1.4.2 Vertical Accuracy...................................................................................................................................174.1.4.3 Position Confidence level.......................................................................................................................174.1.4.4 Position authenticity...............................................................................................................................174.1.4.5 Availability.............................................................................................................................................174.1.4.6 Response or Report Latency..................................................................................................................174.1.5 Mobile target identification..........................................................................................................................174.1.6 Priority.........................................................................................................................................................174.1.7 Timestamp....................................................................................................................................................184.1.8 Security........................................................................................................................................................184.1.9 Privacy.........................................................................................................................................................184.1.10 Service authorization....................................................................................................................................184.1.11 Coverage......................................................................................................................................................184.1.11.1 Expected coverage..................................................................................................................................184.1.11.2 Guaranteed coverage..............................................................................................................................194.1.12 Types of location reporting..........................................................................................................................194.2 Logical description............................................................................................................................................194.2.1 Logical reference architecture......................................................................................................................194.2.2 Functional entities........................................................................................................................................204.2.2.1 Application Module................................................................................................................................204.2.2.2 Central Facility.......................................................................................................................................214.2.2.3 Positioning Function..............................................................................................................................214.2.2.4 Privacy Control......................................................................................................................................214.2.2.5 Security...................................................................................................................................................214.2.2.6 Positioning module.................................................................................................................................214.2.2.7 Mobile Target.........................................................................................................................................214.2.2.8 Mobile Target User................................................................................................................................214.2.2.9 Application Module User.......................................................................................................................214.2.3 Interfaces external to Location System........................................................................................................224.2.3.1 Application Module/ Location System interface....................................................................................224.2.3.1.1 Location Request..............................................................................................................................224.2.3.1.2 Location Response or Report...........................................................................................................224.2.3.2 Mobile Target/ Location System interface.............................................................................................224.2.3.3 GNSS / Location System interface.........................................................................................................22

ETSI

TS 103 247 V<0.0.3> (<2014-02>)3

5 Stage 2 functional description of location systems.................................................................................225.1 Main concepts....................................................................................................................................................235.1.1 Assumptions and generalities.......................................................................................................................235.2 Location system architecture definition.............................................................................................................245.2.1 Location system reference generic architecture...........................................................................................245.2.2 Functional description of reference architecture components.....................................................................245.2.2.1 Positioning module.................................................................................................................................245.2.2.2 Central Facility.......................................................................................................................................255.2.2.3 Application Module Interface................................................................................................................255.2.2.4 Assistance Server...................................................................................................................................255.2.2.5 Data enhancers.......................................................................................................................................265.2.2.9 GNSS Sensor..........................................................................................................................................265.2.2.9 Additional Sensors.................................................................................................................................265.2.2.9 Functional allocation..............................................................................................................................265.3 Communication system description...................................................................................................................27

6 Physical description of location systems................................................................................................276.1 Common positioning techniques.......................................................................................................................276.1.1 GNSS methods.............................................................................................................................................276.1.2 Assisted-GNSS methods..............................................................................................................................286.1.3 High accuracy GNSS methods.....................................................................................................................296.1.4 Proximity sensing.........................................................................................................................................296.1.5 Multilateration..............................................................................................................................................296.1.6 Triangulation................................................................................................................................................316.1.7 Multi-sensor positioning through (A-)GNSS hybridization........................................................................316.2 Location system detailed architecture...............................................................................................................326.2.1 Components description...............................................................................................................................326.2.1.1 Positioning module.................................................................................................................................326.2.1.2 Central Facility.......................................................................................................................................336.2.1.3 Application Module Interface................................................................................................................336.2.1.4 Assistance Server...................................................................................................................................346.2.1.5 Location Hybridization Algorithm.........................................................................................................346.2.1.6 Integrity Building Algorithm.................................................................................................................346.2.1.7 EMI Localisation Algorithm..................................................................................................................356.2.1.8 EMI Mitigation algorithm......................................................................................................................356.2.1.8 Map database..........................................................................................................................................356.2.1.9 GNSS Sensor..........................................................................................................................................356.2.1.9 Various Sensors......................................................................................................................................356.2.1 Interfaces identification................................................................................................................................36

Proforma copyright release text block..............................................................................................................37Annexes 38

Annex <A> (normative): Title of normative annex (style H8)....................................................................38

Annex A (informative): Examples of Location System Implementations..................................................39

A.1 Implementation profile #1......................................................................................................................39






A.7 Implementation profile #7......................................................................................................................44A.1.1 First subdivided clause of the annex (style H2).................................................................................................45

Annex <X+3> (informative): Change History..............................................................................................45

Annex <X+4> (informative): Bibliography..................................................................................................46

ETSI

TS 103 247 V<0.0.3> (<2014-02>)4

History...............................................................................................................................................................46A few examples:..................................................................................................................................................................47

ETSI

TS 103 247 V<0.0.3> (<2014-02>)5

Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (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 IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)6

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

ETSI

TS 103 247 V<0.0.3> (<2014-02>)7

1 ScopeThe present document addresses location systems combining telecommunication networks with Global Navigation Satellite System (GNSS) and other navigation technologies in order to deliver location based services.

The requirements contained in the present document is intended to highlight the growing use of complex location systems in order to deal with the expansion of location based applications in a mass market. The objective is thus to provide a Technical Speficiation defining the high level architecture of these systems.

This specification addresses the Stage One description of the services provided by Location Systems, including an inventory of functional requirements and a logical description of these systems. It also defines the Stage Two functional specification for Location systems, including definition of their reference architecture and associated interfaces.

It is highlighted that the scope of this technical specification specifically excludes standardisation of safety of life applications related to civil aviation, which are already addressed through, in particular, Radio Technical Commission for Aeronautics (RTCA) standards. It however covers standardization of liability critical terrestrial and maritime applications.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)8

2 ReferencesReferences are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.

Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.

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

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

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

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

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

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

[refx10] Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.

[refx11] IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, June 17, 2008.

[refx12] Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.

[refX1] ETSI TS 103 248: "Satellite Earth Stations and Systems (SES); GNSS based location systems; Requirements for the location data exchange protocols”

[refX2] RTCM SC104 reference to be determined

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 102 473: "<Title>".

ETSI

TS 103 247 V<0.0.3> (<2014-02>)9

http://docbox.etsi.org/Reference

3 Definitions, symbols and abbreviations3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

Accuracy : The term accuracy relates to the location-related information reported by the location system, i.e. the mobile target position, velocity, acceleration and GNSS system time estimate. The accuracy is thus characterized by the difference between the quantity estimated by the location system, and its actual value. It is expressed in m (position), m.s-1 (speed), m.s-2 (acceleration) or seconds (time), and usually characterized through statistical values (mean, standard deviation, root mean square, percentile, etc.). When not further specified in the present technical context, the term accuracy usually refers to the position accuracy. By extenstion, accuracy is one of the key performance features which can be required from a location system.

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

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

Authentication : Authentication is the provision of assurance that the location-related information associated to a mobile target is correct. By extenstion, authentication is one of the key performance features which can be required to a location system

Availability : Availability measures percentage of time when a location system is able to provide the required location-related information. Note that the required location-related information might vary from one location based application to the other : it can not only contain a required type of information (position, speed, …), but also a required quality of service (accuracy, protection level, authentication, etc. ).

Coverage : The coverage of the location system is the surface area or space volume in which the signals are adequate to determine the mobile targets location-related information to a specified level of accuracy. Coverage is influenced by receiver sensitivity and environmental conditions affecting the signal availability.

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

Horizontal plane : plane locally defined for the mobile target, orthogonal to the zenith/nadir axis.

Integrity : Integrity is an optional function of a location system that aims at measuring the trust that can be placed in the accuracy of the location-related information provided by the location system. In the present technical context, it is expressed through a pair protection level / integrity risk. By extenstion, integrity is one of the key performance features which can be required from a location system

Integrity risk : The integrity risk is the probability that the actual error of the location-related information is larger than the protection level. The integrity risk is, with the protection level, one of the 2 sub-features of integrity feature.

Jamming : Deliberate transmission of radio signals in order to disrupt communications by decreasing the signal to noise ratio. In the present technical context, targeted communication signals are GNSS or telecommunication signals.

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

Location : a place where something is or could be located. In the present technical context, the place where the mobile target is.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)10

NOTE: the term position can have several meaning. In the present technical context, the only relevant meaning is considered to be equivalent to location (and therefore excludes interpretation such as “body posture”, “state of mind or principle”, “job or activity”). The term location will arbitrarily be preferred, except when referring to the action of “determining a location”, for which the term positioning will be used.

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

Location based service : service built on the processing of the Location-related information associated to one or several mobile targets

Location-related information: set of data associated to a given mobile target, containing one or several of the following information, all time-tagged : mobile target position, mobile target motion indicators (linear or angular speed and acceleration), and Quality of service indicators (estimates of the position accuracy, reliability or authenticity indicators).

NOTE: It is the main output of a Location system.

Location system: system in charge of providing to a location based application the Location-related information of one or several mobile targets.

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

Mobile target: physical entity whose position the location system builds the location-related information on, and with which the positioning module is attached

Positioning module: logical entity, inside a Location system, in charge of providing the relevant measurements to the location system central facility (enabling it to determine the mobile target location-related information) or directly providing the mobile target location-related information to the “Application module”. It is composed of a GNSS receiver and possibly additional sensors.

NOTE: It executes the measurements needed to determine its position, and implements part of the location determination functions. It embeds the group of sensors needed to execute these tasks. This group can include navigation sensors (GNSS, Inertial, Odometers, etc.), wireless network modems (terrestrial or satellite). It might be collocated with the mobile target or not.

Privacy : privacy is a function of a location system that aims at ensuring that the mobile target user private information (identity, bank accounts etc.) and its location-related information cannot be accessed by a non authorized third party.

Protection level : The protection level PL is an estimated error value which comply with the following condition : P(> PL) < Irisk , where Irisk is the Integrity risk and the actual error. The protection level is provided by the location system, and is, with the integrity risk, one of the 2 sub-features of integrity feature. The protection level can be measured by a statistical metric similar the the one used for the size of the error (Accuracy).

Quality of service : the quality of service associated to a location based service is a set of indicators which can accompany the mobile target(s) position/motion information and is intended to reflect the quality of the information provided by the location system. QoS indicators can be accuracy estimate, protection level statistics / integrity risk, authentication flag, etc.

Security : security is a function of a location system that aims at ensuring that the location-related information is safeguarded against unapproved disclosure or usage inside or outsite the location system, and that it is also provided in a secure and reliable manner that ensures it is neither lost nor corrupted.

Time to First Fix : The Time To First Fix (TTFF) is a measure of performance of a GNSS receiver that accounts for the time elapsed from the GNSS receiver switch-on until the output of a navigation solution within a certain performance.

Vertical axis : axis locally defined for the mobile target, collinear to the zenith/nadir axis.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)11

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

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

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

3GPP 3rd Generation Partnership ProjectADAS Advanced Driver Assistance SystemsAL Alarm LimitBTS Base station Transceiver SystemDOA Direction Of ArrivalECEF Earth Centred Earth FixedEDGE Enhanced Data for GSM EvolutionEGNOS European Geostationary Navigation Overlay SystemEMI Electro-Magnetic InterferenceFDAF Frequency Domain Adaptive FilteringGCF 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 communicationsHPE 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 Oscillator

ETSI

TS 103 247 V<0.0.3> (<2014-02>)12

NMR Network Measurement ResultsODTS Orbit Determination and Time SynchronisationOMA Open Mobile AllianceOTDOA Observed Time Difference Of ArrivalPAYD Pay As You DrivePE Positioning ErrorPL Protection LevelPRS Public Regulated ServicesPVT Position, Velocity and TimeQoS 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 CenterSUPL Secure User Plane for LocationSV Satellite VehicleTBC To Be ConfirmedTBD To Be DefinedTC-SES Technical Committee Satellite Earth Stations and SystemsTTA Time To AlarmTTFF Time To First FixUDRE User Differential Range ErrorUERE User Equivalent Range ErrorUHF Ultra-High FrequencyUMTS Universal Mobile Telecommunications SystemVPL Vertical Protection LevelWAAS Wide Area Augmentation SystemWI-FI Wireless Fidelity

ETSI

TS 103 247 V<0.0.3> (<2014-02>)13

4 Services provided by location systems – Stage 1 description

4.1 Functional requirementsThe expansion of terrestrial applications including location-based services and transportation means such as road or

train has fostered the design of complex location systems. These systems are designed to deliver a location-related information of one or several mobile targets to an application, in order to enable the development of new and innovative location based services.

These systems shall identify and report in a standard format a set of location-related information concerning one or several mobile targets, and make it available to the 3rd party entity in charge of processing this information and delivering the service to an end user.

The location-related information produced by the location system is meant to be used for various types of applications, all in charge of delivering a specific service to an end-user : location-based charging, geo-localization of a fleet of vehicules, vehicule movement and trajectory monitoring, etc.

The following subsections provide general descriptions of attributes that can be used to describe or characterize the location system expected behavior.

The relative importance of these attributes varies from service to service. However, accuracy, integrity and availability, coverage and privacy may be considered the primary distinguishing attributes that define a value-added service. Briefly:

- accuracy is the difference between actual location and estimated location,

- integrity is the measure of the trust that can be placed in the correctness of the location-related information provided by the system

- availability is the percentage of time that the location system is able to provide the required information with the adequate quality of service

- coverage is an expression of the geographic area in which the mobile target can be localized with the adequate quality of service

- privacy describes the user’s perception of confidentiality of the mobile target location-related information, and

- transaction rate indicates how frequently network messaging is required to support the service.

4.1.1 Location system definitionLocation systems determine the location of at least one mobile target within a given area of coverage (from local to global), and provide to an authorized requesting external entity this information. Execution of the measurements allowing to determine the mobile target position shall be assigned to one or more positioning module. Positioning module measurement source shall include GNSS positioning method.

The diagram depicted in figure 4-3 illustrates the high level context applicable to the location system.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)14

Figure 4-3. Generic context for location systems

4.1.2 High level requirementsThe following high level requirements are applicable:

1 In addition to GNSS method, multiple positioning methods may be supported by the location system, including (but not limited to) :

- Assisted-GNSS

- Inertial Navigation Systems

- In case location system uses external telecommunication networks to connect with the positioning module , techniques such as U-TDOA, E-OTD and cell-ID

2 In case multiple positioning methods are supported, the system may implement measurement fusion algorithm

3 The location system shall be able to provide to a requesting external entity the following information for each of the terminal addressed by the request :

- an identifier of the terminal

- the position of the terminal

- a time tag of the position

4 The location system may be required to handle the delivery of additional location-related information to a requesting external entity for each of the terminal addressed by the request :

- Velocity and/or acceleration

- Indicators of quality of service, such as estimated accuracy of the position/velocity/acceleration estimate, confidence level positionof the /velocity/acceleration estimate, authenticity of the position/velocity/acceleration estimate

5 The location system may be required to comply with additional constrains regarding information delivery, such as :

- Availability of the location-related information

ETSI

TS 103 247 V<0.0.3> (<2014-02>)15

- Latency of the system when answering to the requesting external entity

- Geographical area covered by the system (i.e. over which the system is able to determine the terminal position)

6 When processing the location request from an external entity, the location system shall enforce the following policy :

- Location-related information should be safeguarded against unapproved disclosure or usage (system security)

- Requests for location-related information should be processed by the location system only if the requesting external entity is authorized

- The location system shall be able to handle a privacy profile of each of the mobile targets managed by the location system

- In case of multiple colliding requests, the system shall be able to process them with different level of priority

The previosu high-level requirements can be organized as illustrated in the diagram contained in figure 4-1. Note that mandatory requirements are circled with plain line, optional with dotted line.

Figure 4-1. High level requirements organisation

4.1.3 location-related informationLocation-related information is the kind of information the location system shall provide to an external requesting entity, related to the position and movement of the mobile targets, and consists of one or several of the following information.

4.1.3.1 Geographic location

[To Be filled]

ETSI

TS 103 247 V<0.0.3> (<2014-02>)16

4.1.3.2 Velocity and acceleration

[To Be filled]

4.1.4 Quality of serviceWhen providing the required location-related information, location systems may also, upon request, deliver this information with a pre-determined quality of service. Possible attributes characterizing this quality of service are described here below.

4.1.4.1 Horizontal Accuracy

4.1.4.2 Vertical Accuracy

4.1.4.3 Position Confidence level

2D or 3D

4.1.4.4 Position authenticity

4.1.4.5 Availability

4.1.4.6 Response or Report Latency

4.1.5 Mobile target identification

4.1.6 PriorityLocation requests for different services may be processed with different levels of priority.

The location system may allow different location requests to be assigned different levels of priority. A location request with a higher priority may be accorded faster access to resources than one with a lower priority and may receive a faster, more reliable and/or more accurate location estimate.

When the requesting entity implements Emergency Services (where required by local regulatory requirements) the location request shall be processed with the highest priority level.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)17

4.1.7 TimestampThe location system shall timestamp all location estimates provided to requesting entity, indicating the time at which the location-related information was determined.

4.1.8 SecurityPosition information should be safeguarded against unapproved disclosure or usage. Position information should also be provided in a secure and reliable manner that ensures the information is neither lost nor corrupted. Audit records should be maintained of positioning requests and responses to facilitate resolution of security violations.

The requesting entity shall be authorized by the location system. Security mechanisms of the location system shall be used for authorizing the requesting entity and its request for location-related information.

For Emergency Services (where required by local regulatory requirements) the Emergency Services Network shall be considered as an authorized requesting entity. following requirements shall be met:

Position information shall be provided to the Emergency Services Network as an authorized LCS client. Target UE authorization checks normally performed for value added services are not applicable (privacy is over-ridden). The position information shall be provided to the Emergency Services Network in a secure and reliable manner, such that the location information is neither lost, corrupted, nor made available to any unauthorized third party.

4.1.9 PrivacyThe location system shall be able to handle a privacy profile of each of the mobile targets handled by the location system.

The privacy profile is managed by the location system. In case the application to which the location system contributes envisions the possibility for the mobile target user(s) to determine their privacy profile, the privacy profile may be overridden by the mobile target user.

Unless required by local regulatory requirements, or overridden by the mobile target user, the mobile target may be positioned only if allowed in the privacy profile.

4.1.10 Service authorizationRequests for location-related information should be processed by the location system only if the requesting entity is authorized. The identity and authorization privileges of the requesting entity should be verified prior to processing positioning requests.

4.1.11 CoverageThe coverage of the location system is the geographical area over which the mobile targets shall be localized by the location system.

[induced constrains on communication system selected]

It is noted that from that definition, 2 interpretations are given.

4.1.11.1 Expected coverage

Expected coverage is the geographical area where the mobile targets localization is enabled by the location system through availability of the positionning method.

Thus,

ETSI

TS 103 247 V<0.0.3> (<2014-02>)18

- for a distributed location system composed of terminals using GNSS positioning method, reporting their position through a radio telecommunication network, location system coverage is equivalent to the telecommunication network coverage.

- For a distributed location system composed of terminals using RFID positioning method, reporting their position through a radio telecommunication network, location system coverage is equivalent to the smallest of the following two coverage : telecommunication network coverage or RFID beacons deployment area

Considering network topography and dynamically varying environmental factors, homogeneous service quality might no me guaranteed across the entire location system coverage. Even within those areas where service is offered, the provided quality of service may vary due to dynamic environmental (i.e. radio) conditions. Indeed, the location method may have an accuracy that depends on the UE location, for example due to varying radio conditions, cell configuration and cell density in different areas, and geometric dilution of precision.

4.1.11.2 Guaranteed coverage

Coverage can also be understood as the geographical area where the mobile targets localization is enabled by the location system with a required quality of service.

For liability-critical applications, this would allow to define the area where a minimum quality of service is guaranteed.

4.1.12 Types of location reportingThe provision of the location-related information from the location system to the requesting entity shall be possible through at least one of the schemes presented in table 4-1.

Table 4-1: Location Service Requests

Trigger Report type

On-demandlocation response

Event drivenlocation report

SingleInformation reporting is triggered by a

single request from the requesting entity, and report is provided once

Information reporting is triggered by a specific event, defined in the request received from the requesting entity,

and report is provided once

Periodic

Information reporting is triggered by a single request from the requesting

entity, and report is provided periodically, with a period and over a

duration fixed in the request

Information reporting is triggered by a specific event, defined in the request received from the requesting entity,

and report is provided periodically, with a period and over a duration fixed in

the request

Event-based or time-based decision process is the responsibility of the requesting entity.

4.2 Logical description

4.2.1 Logical reference architectureFigure 4-2 shows the logical reference achitecture for Location systems whereby a requesting entity, identified in this document as the “Application Module”, is enabled to request location-related information for one or more mobile targets covered by the location system.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)19

The location system employs a positioning function to determine the location-related information and furnish the information to the requesting entity. This positioning function shall be at least implemented in the positioning module, and possibly shared on the central facility. In such case, the location system core interface conveys the required data. The core interface might rely on the application layer provided by an external communication system, as depicted in figure 4-3.

The positioning module shall provide GNSS measurements enabling the determination of the location-related information associated to the mobile target, and optionally addition means supporting the positioning function.

The nature of the target interface determines the implementation of the positioning function.

A mobile target privacy profile might optionally be handled internally to the location system, imposing restrictions on the location-related information retrievable for the associated mobile target.

The location system shall be able to provide the mobile target location-related information based on the processing of requests from an application module, through responses provided to it, and implement service authorization check for the requesting application module. The application interface conveys the data supporting this mecanisms.

Figure 4-2: Logical Reference Architecture

4.2.2 Functional entities

4.2.2.1 Application Module

The application module is a functional entity that makes a request to the location system for the location-related information of one or several mobile targets within a specified set of parameters such as Quality of Service (QoS). The application module may reside inside or outside a terminal. The specification of the application module internal logic and its relationship to any external end-user is outside the scope of the present document.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)20

4.2.2.2 Central Facility

A location system central facility consists of a number of location service components and bearers needed to fulfill the application module request. The location system central facility may respond to a location request from a properly authorized application module with location-related information for the mobile targets specified by the application module if considerations of user privacy are satisfied. The location system central facility may enable an application module to determine the services provided to it by the location system central facility through a process of provisioning.

4.2.2.3 Positioning Function

Positioning is the basic function that performs the actual positioning of a specific mobile target(s). The input to this function is a positioning request from an application module with a set of parameters such as QoS requirements. The end results of this function are the location-related information for the positioned mobile target(s).

4.2.2.4 Privacy Control

[TBD]

4.2.2.5 Security

[TBD]

4.2.2.6 Positioning module

Positioning module is the entity in charge of executing the measurements needed to achieve the positioning function. The ability to control privacy might be required to be given to the mobile target user for each location request and/or through the terminal privacy profile to satisfy local regulatory requirements.

The positioning module shall executes the measurements through one of the following methods :

It is physically collocated with the mobile target subject to location request, so that positoning module and mobile target location-related information are identical.

It is not physically collocated with the mobile target subject to location request, and is equipped with remote sensors generating measurements enabling determination of the mobile target location-related information.

4.2.2.7 Mobile Target

The mobile target is the entity (vehicle, person, goods, etc.) whose position is used by the application module to build the value-added service. The positioning module is physically linked to the mobile target, and the nature is linked is assumed to allow to consider that its position is representative of the mobile target position.

4.2.2.8 Mobile Target User

Mobile Target User can be considered in the logical architecture if it appears that, in the frame of the considered application, it is a major stakeholder in the positioning activity. Thus, the determination of the mobile target privacy profile can be offered to its user if local regulatory aspects require so.

4.2.2.9 Application Module User

[…]

ETSI

TS 103 247 V<0.0.3> (<2014-02>)21

4.2.3 Interfaces external to Location System

4.2.3.1 Application Module/ Location System interface

4.2.3.1.1 Location Request

An application module requires to a location system the location-related information for one or more mobile target using location requests.

The location system shall support the processing of location requests having the folloing caracteristics :

The request can ask for an immediate or deferred feed-back, and this feed-back can be composed of a singles or several periodic response or reports.

The request identifies the requestor, the mobile target identity, the type of location-related information expected, optionally the minimum QoS expected

The request optionally describes conditions that shall trigger the provision of the location-related information by the location system

4.2.3.1.2 Location Response or Report

The Location Response or Report provides the result of a Location Request from the location system to the application module.

Location Response and Location Report contain the same information, but it is clarified that :

- Location Response shall be understood as response to an immediate location request (1 Request 1 Response)

- Location Report shall be understood as the message containing the location-related information, triggered by occurrence of an event pre-defined by a previous deferred location request (1 Request Several Reports).

4.2.3.2 Mobile Target/ Location System interface

This interface shall enable the positioning function by being compatible with the type of method applied by the location system to support it :

Positioning module is physically collocated with the mobile target subject to location request, so that positoning module and mobile target location-related information are identical.

Positioning module is not physically collocated with the mobile target subject to location request, but the mobile target / location system interface enables the mobile target location-related information determination.

4.2.3.3 GNSS / Location System interface

[point on GNSSs ICDs]

5 Stage 2 functional description of location systems

5.1 Main conceptsLocation systems are in charge of providing location-related information of one or several mobile targets to an external entity. This provision shall be set-up by the external entity.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)22

This external entity, identified as the application module in this document, relies on the location system in order to obtain the required location-related information, so that it can build value-added services based on this information. Examples of such services are […] The application module, its architecture, functions and performance are out of the present technical specification.

The possible location-related information are the mobile target position, the mobile target motion indicators (linear or angular speed and acceleration), and Quality of service indicators (estimates of the position accuracy, reliability or authenticity indicators).

In order to deliver the required location-related information, a location system relies on a set of positioning techniques which are briefly described in clause 5.1.2. Various such techniques might be selected function of the type of application served, leading to various system architecture. Hence no single location system architecture exists.

However, the present document describes the reference generic modular architecture applicable to location systems. Logical building blocks of any location system architecture shall be taken from this generic architecture, and comply with the interface specification.

This generic architecture envisions :

- a positioning module. The positioning module use GNSS technique as pramiry source for the determination of the location-related information. If additional sensors are to be considered in the location system, they shall be imbedded on the terminal.

- a central facility [optional].

- data processing functions [optional]. Determination of location-related information by the location system might consider using processing function on the top of the sensor(s) used in the terminal (such as measurement fusion, integrity check). Such function can be partly allocated to the positioning module (on-board function) and partly to the central facility (centralized function).

The communication channel between these components can be part of the system, or simply used as data pipe, with associated requirements on data rate, latency, coverage)

5.1.1 Assumptions and generalitiesAs a basis for the further development work on location systems, the following assumptions apply:

- Main source of positioning in the considered location systems is GNSS techniques

- A location system is in charge of providing location-related information only. Further elaboration of actual location services (navigation application, billing information, warning/alarms, …) are outside the perimeter of the system.

- Location-related information may be used internally to the location system in order to improve the system performance

- Several external entities (application modules) can address simultaneously requests to the location system

- The generic architecture described in this document is suited for the positioning techniques described in clause 5.1.2. Further update

- […]

5.2 Location system architecture definition

ETSI

TS 103 247 V<0.0.3> (<2014-02>)23

5.2.1 Location system reference generic architectureFigure 5.1 describes the reference generic modular architecture applicable to location systems. This reference architecture proposes a list of location system main components.

Mandatory components, i.e. which shall be used for any implementation profile, are shadowed.

Optional components, i.e. which might be used for an implementation profile if considered useful, are not shadowed.

Figure 5-1: Location systems reference generic architecture

5.2.2 Functional description of reference architecture components


Positioning module (PM) is a mandatory component of the location system architecture.

It is the entity in charge of executing the measurements needed to determine the position of the mobile target. Several strategies can be adopted in order to generate such measurements :

- positioning module might be physically attached to the mobile target. The mobile target location is thus assimilated to the positioning module.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)24

- positioning module might be a remote measurement unit. The mobile target is then a remote entity. Measurement generated by the positioning module(s) are used to determine the position of the mobile target.

The primary source of positioning module measurements shall be GNSS sensor, associated to an adequate antenna.

The positioning module might embed additional sources of measurement.

In addition, the positioning module might embed positioning functions whose purpose is to build enhanced location-related information, based on the processing of data provided by the measurement sources.


The Central facility (CF) is an optional component of location system architecture.

The location system central shall provide one or several of the following centralized function :

- positioning functions; the purpose of these functions is to build enhanced location-related information, based on the processing of data provided by the measurement sources. The enhancements concern the accuracy of the mobile target position or motion indicators, and the determination or refinements of quality of service (QoS) indicators associated to the mobile target position or motion indicators.In case such functions are implemented in the central facility, they might be allocated partly to the positioning module. The entire positioning function would then be shared on both entities.

- terminal assistance function; the purpose of this function is to elaborate any kind of assistance data which the positioning module might require in order to execute measurements or determine its position.

- profiles management functions; the purpose of this function is to manage all information related to positioning module(s) and required to properly achieve the location system mission. This information is typically a database containing terminal(s) ID(s), terminal(s) user(s) pricavy profile, etc …

- central interface function; the purpose of this function is to manage interface with the external requesting entity, i.e. processing the various received requests, and sending the associated responses or reports.

5.2.2.3 Application Module Interface

The application module interface (AMI) is a mandatory component of location system architecture.

The application interface module is in charge of handling the interface between the external requesting entity, i.e. the application module, and the rest of the system.

The application interface module shall achieve the following functions :

- location request handling functions; this function includes setting up the adequate ressources internal to the location system in order to deliver the required location-related information within the conditions specified by the request. It also manages the priority among the various requests received from one or several application modules,

- [optional] profile management functions; the purpose of this function is to manage all information related to positioning module(s) and required to properly achieve the location system mission. This information is typically a database containing terminal(s) ID(s), terminal(s) user(s) pricavy profile, etc …

- [optional] service authorization function

5.2.2.4 Assistance Server

The assistance server (AS) is an optional component of location system architecture.

The assistance server is in charge of generating and providing assistance data to the positioning module in order to achieve the positioning functions. As such, it shall implement at least one of the following function :

- A-GNSS functions (assistance data as defined in clause X.X)

ETSI

TS 103 247 V<0.0.3> (<2014-02>)25

- multilateration/Triangulation assistance data; applicable in case the Location system has a high level of integration with a cellular NW. In that case, it can provide information enabling techniques such as CID, E-CID, E-OTD, OTDOA, U-TDOA

- Procise positioning data; determination of DGNSS/RTK/WARTK data.

5.2.2.5 Data enhancers

The Data Enhancers (DE) are algorithms used on the top of the usual sensors, use in order to improve the performance of the location-related information, in terms of accuracy, reliability.

The algorithms shall be allocated to the location system components according to one of the following rules :

- allocated to positioning module (on-board function)

- allocated to central facility (centralized function)

- allocated on both components (both on-board and centralized function). Such implementation could be justified by the necessity to imbed specific part of the algorithm at application module level (e.g. for ultra-tight hybridization), and to allocate the remaining processing at central facility level for the sake of terminal consumption.

5.2.2.9 GNSS Sensor

The GNSS sensor (GNSS) is a mandatory component of location system architecture, and shall be on-board the positioning module.

It is in charge of executing the GNSS measurements (including code and carrier phase, Doppler, C/N measurements) and providing the PVT solution.

From a logical description point of view, it is considered that a proper antenna comes with this antenna.

5.2.2.9 Additional Sensors

Additional sensor (AdS) are optional components of location system architecture, and shall be on-board the positioning module.

These additional sensor are one or several of the following components :

- Telecommunication module (TM)

- Inertial Sensor (INS)

- Odometer/tachometer (ODO)

- Magnetometer (MAG)

- Beam-forming antenna (BFN)

5.2.2.9 Functional allocation

The following table summarized the functional allocation between components described above.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)26

FunctionsComponent Generate

measurementEnhance Solution

Positioning Module

assistance

Target Profile

management

Application Interface

Management

System Security

ManagementPM X X X(*) X(*) X(*)

GNSS XAdS XDE XCF X X(*) X(*) X(*)AS XAMI X X X

(*) : depending on where the application module interface is located

Table 5.x:Function allocation of location system components

5.3 Communication system description[introduce the possibility that the communication system used to establish link between positioning module and central facility can be an existing one, to which subscription is taken. In that case, the constrains apply on it (latency, bandwidth, coverage … This section shall introduce this topic. It might be further developed in the TS103 248 on data exchange protocol, once the interface (and data load) are further defined]

6 Physical description of location systems

6.1 Common positioning techniquesThe location system shall support the following common positioning method :

- GNSS method, further described in sub-clause 5.1.2.1

In addition, the location system may support one or several of the following common positioning methods :

- assisted GNSS method, further described in sub-clause 5.1.2.2;

- high accuracy GNSS methods, further described in sub-clause 5.1.2.3;

- Proximity sensing.use of the cell coverage in the frame of cellular telecommunication network,

- Multilateration.Application in the frame of cellular telecommunication network

- Triangulation

- multi-sensor positioning through (A-)GNSS hybridizationexample of sensors : INS, …

6.1.1 GNSS methodsGlobal Navigation Satellite System (GNSS) is the standard generic term for satellite navigation systems that provide autonomous geo-spatial positioning with global or regional coverage. The following GNSSs are supported in this version of the specification:

- GPS and its modernization [refx6,refx7,refx8];

- Galileo [refx9];

ETSI

TS 103 247 V<0.0.3> (<2014-02>)27

- GLONASS [refx10];

- Satellite Based Augmentation Systems (SBAS), including WAAS, EGNOS, MSAS, and GAGAN [refx12];

- Quasi-Zenith Satellite System (QZSS) [refx11].

Each global GNSS can be used individually or in combination with others. When used in combination, the effective number of navigation satellite signals would be increased:

- extra satellites can improve availability (of satellites at a particular location) and results in an improved ability to work in areas where satellite signals can be obscured, such as in urban canyons;

- extra satellites and signals can improve reliability, i.e., with extra measurements the data redundancy is increased, which helps identify any measurement outlier problems;

- extra satellites and signals can improve accuracy due to improved measurement geometry and improved ranging signals from modernized satellites.

[Word on GNSS intergrity monitoring]

[Word on frequency used ]

6.1.2 Assisted-GNSS methodsWhen a GNSS sensor is used as a part of a wider location system, other elements of this system can assist the GNSS sensor to improve the performance in several respects. These performance improvements will:

- reduce the GNSS start-up and acquisition times; the search window can be limited and the measurements speed up significantly;

- increase the GNSS sensitivity; when GNSS sensor operates in defavorable SNR condition, provision of assistance messages internally to the location system can compensate the improper GNSS satellite signals demodulation;

- allow the GNSS sensor to consume less power from the positioning module than with stand-alone GNSS; this is due to rapid start-up times as the GNSS receiver can be in idle mode when it is not needed.

The assisted GNSS methods rely on communication between GNSS receiver embedded in the positioning module,and a so-called assistance server, part of the location system. This server mainly relies on a continuously operating GNSS reference receiver network, which has clear sky visibility of the same GNSS constellation as the assisted receiver. Two assisted modes are supported:

- Terminal-Assisted: The positioning module performs GNSS measurements (pseudo-ranges, pseudo Doppler, etc.) and sends these measurements to a central facility (part of the location system), where the position calculation takes place, possibly using additional measurements from other (non GNSS) sources, as described in sub-clauses 5.1.x;

- Terminal-Based: The positioning module performs GNSS measurements and calculates its own location, possibly using additional measurements from other (non GNSS) sources.

The assistance data content may vary depending on whether the positioning module operates in Terminal-Assisted or Terminal-Based mode.

The assistance data signalled to the terminal can be broadly classified into:

- data assisting the measurements: e.g. reference time, visible satellite list, satellite signal Doppler, code phase, Doppler and code phase search windows;

- data providing means for position calculation: e.g. reference time, reference position, satellite ephemeris, clock corrections.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)28

A UE with GNSS measurement capability may also operate in an autonomous (standalone) mode, as described in sub-clause 5.1.2.1, without assistance from the network.

Table 5-1 indicates where the various (A-)GNSS techniques processing take place function of the supported mode.

Table 5-1: Location Service Requests

Processing step A-GNSSTerminal-Assisted

A-GNSSTerminal-Based

GNSSStandalone

Baseband processing

Terminal Terminal Terminal

Pseudorange calculation

Terminal Terminal Terminal

Position calculation

Central Facility Terminal Terminal

Decoding of Satellite data

Central Facility Central Facility Terminal

Selection of Satellites

Central Facility Central Facility Terminal

6.1.3 High accuracy GNSS methodsIn addition to the above GNSS and A-GNSS techniques, some high accuracy positioning techniques using GNSS signals are considered :

- D-GNSS techniques based on code measurement correction

- RTK and Wide Area RTK techniques based on carrier measurement correction

- Precise Point Positioning (PPP),

[to be developed]

6.1.4 Proximity sensingThe determination of the position of a mobile target can be executed by identifying that it is in the vicinity of a reference point whose position is well known.

The case of cellular networks offers a privileged opportunity to execute such method. Indeed, a cellular network is a wireless network distributed over land areas called cells, each served by at least one fixed-location transceiver, known as a base station. These base stations are reference points. Identifying the transceiver to which a terminal is connected allows to locate it inside the associated cell.

Furthermore, this technique is applicable in the case of WiFi networks or Bluetooth device.

Regardless of which technique is used the term “base station” is used to identify the source of the signal on the which the proximity sensing is applied, and whose position provides the location estimate. Identically, the “cell” is the area covered a given base station.

This technique requires that the position of the base station is somehow known from by the positioning module.

It represents the easiest way to determine the position of a compatible positioning module, but suffers from poor accuracy. Indeed, accuracy of the obtained location depends on the size of the cells, hence of the density of base station.

Typical example of such technique is called Cell-ID (CID) for UMTS and LTE cellular networks.

6.1.5 MultilaterationEnhancements of the previous method are possible if range or range difference measurements between the mobile target and the several reference points are achievable.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)29

Several such techniques exists :

- Circular multilateration; range measurements are executed with at least 3 separate base stations; Each range measurement locates the terminal on a sphere centered on the base station (including uncertainty due to measurement); the intersection of the circles provides a positon estimate. Ranging measurements can be obtained using various techniques with various accuracy : measurement of the received signal strength or of the propagation time

Diagram to be re-executed

Figure 5-1: Circular multilateration method

- Hyperbolic multilateration; this method rather relies on measurement of the range difference between the terminal and surrounding base stations; each range difference measurement, executed for a pair of base station, locates the terminal on a hyperbola with its focal points on the 2 base stations; the intersection of the hyperbolas provides a position estimate.

Diagram to be re-executed

Figure 5-2: Hyperbolic multilateration method

Note that since multilateration requires measurement executed on several base stations, the position of the neighbour transceivers needs to be known.

Typical example of circular multilateration is the enhanced cell-ID method (E-CID) used for LTE networks.

Note that GNSS technique is a circular lateration technique, using a dedicated system whose primary purpose is positioning. Downlink multilateration techniques mentioned above are techniques built upon existing cellular networks whose primary objective is telecommunication. These techniques therefore mainly rely on the use of existing mechanisms, signals and measurements to determine the terminal position.

Typical examples of hyperbolic multilateration are Enhanced Observed Time Different (E-OTD) used for GSM network, Observed Time Difference of Arrival (OTDOA) for UMTS and LTE networks. For both Both techniques, measurements are obtained at cellular network terminal level.

An additional hyperbolic multilateration method relies on uplink measurements. This is the case of Uplink Time Difference of Arrival (U-TDOA) method used for GSM networks. Such methods are network-based, so that no measurement is available at terminal level. Position only would be available at terminal level.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)30

6.1.6 Triangulation à completer

Multilateration brings more accuracy by using ranging measurements between the mobile target and reference points. Triangulation brings more accuracy by using angle of visibility of a mobile target from various observation points.

a refaire

Figure 5-2: Triangulation method

6.1.7 Multi-sensor positioning through (A-)GNSS hybridizationThe hybridization of GNSS sensors with other navigation systems is the computation of a sought final data (position, speed, heading) from intermediate data provided by these systems. The idea behind this association is to develop a hybrid system more robust in operational conditions (interference and multipath, loss of GNSS signal), and more accurate.

The type of intermediate data to be processed depends on the hybridization methods used, and the type of navigation systems considered.

Several levels of hybridization exist :

- in the first level, each navigation source, including GNSS sensor, provides the information of position and velocity of the mobile target. This is called “loose” coupling.

- an enhanced leve of hybridization can be reach if ranging measurements are provided by the various navigation sources, thus providing estimates of distances between the mobile target and a number of reference points. This is called “tight” coupling.

- finally, if it is possible to have access to the heart of the GNSS sensor processing and more particularly to the tracking loops, integration "ultra-tight" can be implemented. In that case, information collected from the other navigation sources are used to optimize the tracking loop behaviour.

The navigation source listed below provide data injectable in an hybridization algorithm :

- Inertial Navigation Sensor (INS) : data from accelerometers and gyrometers can be used to improve the positioning performance

- odometer and tachometer : these devices, typical used in the automotive domain, provide valuable information on the mobile target movement; in addition, when installed on the 2 front (or rear) wheels of a car they provide information on car gyration.

- cellular network modem : such sensors can provide various location-related information, from estimate location (accuracy depending on the method), down to base station ranging measurements.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)31

6.2 Location system detailed architectureThe following detailed architecture is derived based on the inventory of existing location methods provided in clause 6.1 above.

Figure 5-1: Location system detailed architecture

6.2.1 Components description

Further description of the architecture components is provided below.


Positioning module (PM) is a mandatory component of the location system architecture.

It is the entity in charge of executing the measurements needed to determine the position of the mobile target. Several strategies can be adopted in order to generate such measurements :

ETSI

TS 103 247 V<0.0.3> (<2014-02>)32

- positioning module might be physically attached to the mobile target. The mobile target location is thus assimilated to the positioning module.

- positioning module might be a remote measurement unit. The mobile target is then a remote entity. Measurement generated by the positioning module(s) are used to determine the position of the mobile target.

The primary source of positioning module measurements shall be GNSS sensor, associated to an adequate antenna.

The positioning module might embed additional sources of measurement, among the following : inertial navigation sensor, odometer/tachometer, telecommunication module, beam forming antenna, and map.

In addition to the above sources of measurements, the positioning module might embed positioning functions whose purpose is to build enhanced location-related information, based on the processing of data provided by the measurement sources. The enhancements concern the accuracy of the mobile target position or motion indicators, and the determination or refinements of quality of service (QoS) indicators associated to the mobile target position or motion indicators.

NOTE : the classification of a map as a source of measurement is motivated by the fact that it is considered as a snapshot of topographic measures captured in a database. The recorded measures are used inside dedicated processing (map-matching technique) in order to refine the enhance the location-related information


The Central facility (CF) is an optional component of location system architecture.

The location system central shall provide one or several of the following centralized function :

- positioning functions; the purpose of these functions is to build enhanced location-related information, based on the processing of data provided by the measurement sources. The enhancements concern the accuracy of the mobile target position or motion indicators, and the determination or refinements of quality of service (QoS) indicators associated to the mobile target position or motion indicators.In case such functions are implemented in the central facility, they might be allocated partly to the positioning module. The entire positioning function would then be shared on both entities.

- terminal assistance function; the purpose of this function is to elaborate any kind of assistance data which the positioning module might require in order to execute measurements or determine its position.

- profiles management functions; the purpose of this function is to manage all information related to positioning module(s) and required to properly achieve the location system mission. This information is typically a database containing terminal(s) ID(s), terminal(s) user(s) pricavy profile, etc …

- central interface function; the purpose of this function is to manage interface with the external requesting entity, i.e. processing the various received requests, and sending the associated responses or reports.

6.2.1.3 Application Module Interface

The application module interface (AMI) is a mandatory component of location system architecture.

The application interface module is in charge of handling the interface between the external requesting entity, i.e. the application module, and the rest of the system.

The application interface module shall achieve the following functions :

- location request handling functions; this function includes setting up the adequate ressources internal to the location system in order to deliver the required location-related information within the conditions specified by the request. It also manages the priority among the various requests received from one or several application modules,

- [optional] profile management functions; the purpose of this function is to manage all information related to positioning module(s) and required to properly achieve the location system mission. This information is typically a database containing terminal(s) ID(s), terminal(s) user(s) pricavy profile, etc …

ETSI

TS 103 247 V<0.0.3> (<2014-02>)33

- [optional] service authorization function

6.2.1.4 Assistance Server

The assistance server (AS) is an optional component of location system architecture.

The assistance server is in charge of generating and providing assistance data to the positioning module in order to achieve the positioning functions. As such, it shall implement at least one of the following function :

- A-GNSS functions (assistance data as defined in clause X.X)

- multilateration/Triangulation assistance data; applicable in case the Location system has a high level of integration with a cellular NW. In that case, it can provide information enabling techniques such as CID, E-CID, E-OTD, OTDOA, U-TDOA

- Procise positioning data; determination of DGNSS/RTK/WARTK data.

6.2.1.5 Location Hybridization Algorithm

The Location hybridization algorithm (LHA) is an optional component of location system architecture.

The location hybridization algorithm is one of the algorithms in charge of executing the processing required to determine the location-related information of a mobile target. It is specifically in charge of the processing needed in case the mobile targets are not interference sources, and neither position integrity nor authenticity is required as part of the quality of service indicators.

NOTE : location-related information be computed using measurements fusion, i.e. measurement coming from GNSS sensor on one hand, and additional sensor (including map) on the other hand.

This algorithm shall be allocated to the system components according to one of the following rules :



- allocated on both components (both on-board and centralized function). Such implementation could be justified by the necessity to imbed specific hybridization processing at terminal level (in particular for ultra-tight hybridization), and to allocate the remaining processing at central facility level for the sake of terminal consumption.

6.2.1.6 Integrity Building Algorithm

The Integrity Building algorithm (IBA) is an optional component of location system architecture.

The location hybridization algorithm is one of the algorithms in charge of executing the processing required to determine the location-related information of a mobile target. It is specifically in charge of the processing needed in case :

- reliable quality of service indicators are needed

- proof of authenticity of the position-related information are needed.

This algorithm shall be allocated according to one of the following rules :



- allocated on both components (both on-board and centralized function). Such implementation could be justified by the necessity to imbed specific integrity determinal processing at terminal level, and to allocate the remaining processing at central facility level for the sake of terminal consumption.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)34

6.2.1.7 EMI Localisation Algorithm

The EMI localisation algorithm (ELA) is an optional component of location system architecture.

The EMI localisation algorithm is one of the algorithms in charge of executing the processing required to determine the location-related information of a mobile target. This algorithm is in charge of specific computations needed in case the mobile targets addressed by the location system are interference sources.

This algorithm shall be allocated according to one of the following rules :



- allocated on both components (both on-board and centralized function). Such implementation could be justified by the necessity to imbed specific EMI localisation processing at terminal level, and to allocate the remaining processing at central facility level for the sake of terminal consumption.

6.2.1.8 EMI Mitigation algorithm

The EMI mitigation algorithm (EMA) is an optional component of location system architecture.

This algorithm is in charge of mitigating the degradation of the location system performance due to the positioning module operating under interference conditions.

6.2.1.8 Map database

The Map database (MD) is an optional component of location system architecture.

This database shall be available on the positioning module, at the central facility, or on both.

6.2.1.9 GNSS Sensor

The GNSS sensor (GNSS) is a mandatory component of location system architecture, and shall be on-board the positioning module.

It is in charge of executing the GNSS measurements (including code and carrier phase, Doppler, C/N measurements) and providing the PVT solution.

From a logical description point of view, it is considered that a proper antenna comes with this antenna.

6.2.1.9 Various Sensors

Additional sensor are optional components of location system architecture, and shall be on-board the positioning module.

These additional sensor are one or several of the following components :

- Telecommunication module (TM)

- Inertial Sensor (INS)

- Odometer/tachometer (ODO)

- Magnetometer (MAG)

- Beam-forming antenna (BFN)

ETSI

TS 103 247 V<0.0.3> (<2014-02>)35

6.2.1 Interfaces identificationThe following interfaces are defined inside the location system architecture :

- Interface AmLha : This interface is between AMI and LHA, and conveys on the one hand the commands that the AMI sends to the LHA enhancer in order to set-up the location-related information generation, and on the other hands the response received by the AMI in return.

- Interface AmIb : between AMI and IBA […]

- Interface AmEl : between AMI and ELA […]

- Interface AmAs : between AMI and AS […]

- Interface LhaMd : between LHA and MD […]

- Interface IbaMd : between IBA and MD […]

- Interface AsGn : between AS and GNSS […]

- Interface AsTm : between AS and TM […]

- Interface GnEm : between GNSS and EMA […]

- Interface GnEl : between GNSS and ELA […]

- Interface GnLha : between GNSS and LHA […]

- Interface GnIba : between GNSS and IBA […]

- Interface is identical to GnLha […]

- Interface GnBfn : between GNSS and BFN […]

- Interface BfEm : between BFN and EMA […]

- Interface BfIb : between BFN and IBA […]

- Interface BfIb : between BFN and IBA […]

- Interface TmEl : between TM and ELA […]

- Interface TmLha : between TM and LHA […]

- Interface TmIb : between TM and IBA […]

- Interface InLha : between INS and LHA […]

- Interface InIb : between INS and IBA […]

- Interface OdLha : between ODO and LHA […]

- Interface OdIb : between ODO and IBA […]

- Interface MagLha : between MAG and LHA […]

- Interface MagIb : between MAG and IBA […]

- Interface GnAm : between GNSS and AMI […]

ETSI

TS 103 247 V<0.0.3> (<2014-02>)36

The following text is to be used when appropriate:

Proforma copyright release text blockThis text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.

Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the <proformatype> proforma in this {clause|annex} so that it can be used for its intended purposes and may further publish the completed <proformatype>.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)37

AnnexesEach annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).

Use the Heading 8 style for the title and the Normal style for the text.

Specify if the annex is normative or informative.

Annex <A> (normative):Title of normative annex (style H8)<Text>

ETSI

TS 103 247 V<0.0.3> (<2014-02>)38

Annex A (informative):Examples of Location System ImplementationsIn order to provide the required information, the following typical location systems architecture are quoted.

- LTE terminal, connected via IP to a SUPL Location server disseminating GNSS assistance data, and providing data to a local or distant application

- RTK-compatible terminal, mounted on a farming vehicule, receiving RTK corrections from a reference station, and providing location-related information to an automatic guidance device,

- Standalone GPS+GALILEO receiver, embedded in a personal navigation device, and providing position-related information to the device navigation software application,

- Automotive built-it navigation terminal, elaborating location-related information from multi-sensor information (GNSS, odometer), and providing it to the car navigation software application.

- Network of GNSS bandwidths monitoring stations, all connected to a central processing facility, with the objective to provide location-related information of possible interference sources to an external client

- Multisensor terminal mounted on road vehicules usager providing hybridized location-related information to dedicated billing facility in the frame of electronic fee collection application

- […]

A.1 Implementation profile #1

Typical architecture for standalone, multiconstellation GNSS receiver. The location system is then limited to a positioning module, embedded on a navigation terminal.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)39

Figure A-1: Implementation profile exemple #1

A.2 Implementation profile #2

Typical architecture for Electronic Fee Collection terminal. The location system is then limited to a positioning module, embedded on an on-board charging unit.


A.3 Implementation profile #3Typical architecture mapped to the usual GSM, UMTS, LTE or OMA framework. The location system embeds the various components involved in the LCS provision from infrastructure point of view (SMLC, GMLC), and the application module(s) on-board the handset(s) (MS, UE).

ETSI

TS 103 247 V<0.0.3> (<2014-02>)40


A.4 Implementation profile #4Typical architecture for can on-board navigation device. The location system is then limited to a positioning module, embedded on an on-board navigation system.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)41


A.5 Implementation profile #5Typical architecture for DGNSS-based or RTK-based location systems used as a support for precision farming guidance systems. The location system is then composed of a reference station (central facility), and one or several postioning modules embedded in the farming vehicules.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)42


A.6 Implementation profile #6Typical architecture for location system operating in constrained electro-magnetic environment, and seeking for reliability of computed position.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)43


A.7 Implementation profile #7Typical architecture for a personal navigation device. The location system is then limited to a positioning module, embedded on a navigation terminal.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)44


A.1.1 First subdivided clause of the annex (style H2)<Text>

<PAGE BREAK>

Annex <X+3> (informative):Change HistoryThis informative annex is optional. If present, it describes the list of changes implemented in a new version of the deliverable.

Its format is tabular, it may contain the Change Request numbers and titles or textual explanations of the changes that lead to each new version number of the deliverable.

ETSI

TS 103 247 V<0.0.3> (<2014-02>)45

date Version Information about changes

October 2011 v1.1.1First publication of the TS after approval by TC SPAN at SPAN#19(30 September - 2 October 2011; Prague)Rapporteur is John Smith

February 2012 v1.2.1

Implemented Change Requests:SPAN(12)20_019 Error message information clarificationsSPAN(12)20_033 Revised error message informationSPAN(12)20_046 update of figure 3 clause 9.2These CRs were approved by TC SPAN#20 (3 - 5 February 2012; Sophia)

Version 1.2.1 prepared by John Smith

July 2013 v1.3.1

Implemented Changes:

Correction needed because the previously approved version did not contain the last version of the ASN.1 and XML attachments.

Version 1.3.1 prepared by Mark Canterbury (NTAC)

<PAGE BREAK>

Annex <X+4> (informative):BibliographyThe annex entitled "Bibliography" is optional.

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

It shall not include references mentioned in the document.

Use the Heading 8 style for the title and B1+ or Normal for the text.

<Publication>: "<Title>".

OR

<Publication>: "<Title>".

<PAGE BREAK>

HistoryThis clause shall be the last one in the document and list the main phases (all additional information will be removed at the publication stage).

Document history

<Version> <Date> <Milestone>

ETSI

TS 103 247 V<0.0.3> (<2014-02>)46

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

A few examples:

Document history

V1.1.1 April 2001 Publication

V1.3.1 June 2011 Pre-Processing done before TB approvale-mail: mailto:[email protected]

V2.0.0 March 2013 Clean-up done by editHelp!e-mail: mailto:[email protected]

Latest changes made on 2013-05-15

ETSI

TS 103 247 V<0.0.3> (<2014-02>)47

mailto:[email protected]

mailto:[email protected]

docbox.etsi.org€¦ · Web viewA location system central facility consists of a number of...

Documents

Transcript of docbox.etsi.org€¦ · Web viewA location system central facility consists of a number of...