hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.5.3.1.3 Operational environment: Asymmetric area | The performance requirements are specified in tables 25 and 26. The location target follows the trajectory defined in clause A.4. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 100 m. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10)... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.5.3.2 Use case: Static Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.5.3.2.1 Operational environment: Open area | The performance requirements are specified in table 27. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 100 m. Table 27: Performance requirements for TTFF, Static location target, Open area Metric TTFF[s] Class A Class B Cla... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.5.3.2.2 Operational environment: Urban area | The performance requirements are specified in table 28. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 100 m. Table 28: Performance requirements for TTFF, Static location target, Urban area Metric (as per clause 4.2) TTFF[s... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.5.3.2.3 Operational environment: Asymmetric area | The performance requirements are specified in table 29. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 100 m. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10) 29 Table 29: Performance requirements for TTFF, Static location target, A... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6 Position Authenticity | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.1 Definition | Position Authenticity gives a level of assurance that the data for a location target has been derived from real signals relating to the location target. GBLS authenticates the estimated positions by means of specific algorithms that detect, and possibly mitigate, the presence of structured RF interference (i.e. RF spoo... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.2 Metrics | The Position Authenticity performance is defined in terms of: • Probability of False Alarm (PFA): the probability that the GBLS falsely detects spoofed GNSS signals when there is no RF spoofing attack (clear scenario). • Probability of Detection (PD): the probability that the GBLS detects spoofed GNSS signals during an... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3 Performance requirements | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.1 Specific conditions and interference threat scenarios | The interference threat scenarios for position authenticity are defined in clause A.7. These scenarios represent a typical spoofing attack against the GBLS. The scenarios can be easily replicated in a controlled environment and was used to derive the performance requirements given below. The applicable operational envi... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.2 Use case: Moving Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.2.1 Operational environment: Open area | The PFA shall meet the levels specified in table 30. Table 30: Performance requirements for PFA, Moving location target, Open area Maximum False Alarm probability (%) Class A Class B Class C 0,20 1,0 10 |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.2.2 Operational environment: Interference (Spoofing) Scenario | The PD shall meet the following requirements. Table 31: Performance requirements for PD, Moving location target, Spoofing scenario Interference scenario (clause A.7) Maximum Total Spoofing Power [dBW] Maximum Error Minimum D P (%) Class A Class B Class C M-1 -143,5 0,55 × 10-6 s 85 75 68 -142,5 0,66 × 10-6 s 92 85 80 -... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.3 Use case: Static Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.3.1 Operational environment: Open area | The PFA shall meet the levels specified in table 32. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10) 31 Table 32: Performance requirements for PFA Requirement, Static location target, Open area Maximum False Alarm probability (%) Class A Class B Class C 0,05 0,20 1,0 |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.6.3.3.2 Operational environment: Interference (Spoofing) scenarios | The PD shall meet the following requirements. Table 33: Performance requirements for PD, Static location target, Spoofing scenario Interference scenario (clause A.7) Maximum Total Spoofing Power (dBW) Maximum Error Minimum D P (%) Class A Class B Class C S-1 -156,09 0,48 × 10-6 s 90 75 63 -154,46 0,58 × 10-6 s 95 90 85... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7 Robustness to Interference | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.1 Definition | GBLSs might be required to operate in RF environments subject to interference, in particular in the GNSS frequency bands. Robustness to interference characterizes the ability of the receiver to operate under interference conditions and maintain an appropriate level of performance in terms of PVT degradation. Robustness... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.2 Metrics | The performance parameters which characterize the robustness to interference are the following: • position fix accuracy (horizontal) with degradation under interference conditions; • position fix availability as a function either of the jammer distance or the jamming-to-GNSS signal power ratio (J/S). NOTE: Further work... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.3 Performances requirements | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.3.1 Specific conditions and operational environment | The operational environment applicable to Robustness to Interference Performance Feature is the Open Area type, defined in clause A.3. The location target follows the trajectory defined in clause A.4. The jammers to be used are J#1 and J#2, defined in clause A.6. |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.3.2 Use case 1: 20 MHz FM deviation | The performance requirements are specified in tables 34 and 35. Table 34: Performance requirements for Robustness to Interference with J#1 Metric Performance requirement Class A Class B Class C maximum J/S (dB) 59,0 53,0 47,0 minimum Jammer distance (m) 28,0 45,1 64,5 Maximum Horizontal Position Error [m] Mean value 64... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.7.3.3 Use case 2: 10 MHz FM deviation | The performance requirements are specified in tables 36 and 37. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10) 33 Table 36: Performance requirements for Robustness to Interference with J#2 Metric Performance requirement Class A Class B Class C maximum J/S (dB) 40 34 28 minimum Jammer distance (m) 68 87 105 Maximum Horizontal ... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8 GNSS Sensitivity | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8.1 Definition | GNSS Sensitivity is defined in terms of the maximum masking (attenuation) values tolerated by the GBLS while still allowing the provision of the required location-related data. It is respectively specified for Tracking and Acquisition. |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8.2 Metrics | The Tracking Sensitivity is defined as the maximum attenuation (dB) which allows the receiver to provide a position fix. The Acquisition Sensitivity is defined as the maximum attenuation (dB) which allows the receiver to have a first position fix within a given time. 5.8.3 Performance requirements |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8.3.1 Operational scenario and specific masking conditions | The Location target follows the trajectory defined in clause A.4. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10) 34 Two different environment types are used: Open area and Asymmetric area with specific masking conditions. The Sky Attenuation Conditions described in clause A.3.2 are used with attenuation values to compute the ... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8.3.2 Use case 1: Open area and fine time assistance | The performance requirements are specified in tables 39 and 40. For all tables performance requirements are met if the receiver is able to provide a position fix with a horizontal position error and probability as defined above in clause 5.8.2. Table 39: Performance requirements for GNSS Sensitivity, Open area and fine... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.8.3.3 Use case 2: Asymmetric area and coarse time assistance | The performance requirements are specified in table 40. Table 40: Performance requirements for GNSS Sensitivity, Asymmetric area and coarse time assistance Operational condition: Signal Power Attenuation [dB] (x1,x2 and x3 defined in clause A.3.2) Tracking/ Acquisition Sensitivity Metrics Performance requirements Class... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.9 Position Integrity (Protection Level) | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.9.1 Definition | Position Integrity is the ability of the GBLS to measure the trust that can be placed in the accuracy of the location target position. It is relevant to Safety- and Liability-Critical applications (e.g. critical navigation, billing) where undetected large position errors can generate legal or economic consequences. It ... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.9.2 Operational conditions | The Operational environments defined in clause A.3 are applicable. For the Urban Area attenuation conditions, additional environmental features including Integrity Threats as defined in clause A.8 are applicable. The location target follows the trajectory defined in clause A.4. The integrity risk is set to 10-5 per ind... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.9.3 Use case: Moving Location Target | The performance requirements are specified in table 41. Table 41: Performance requirements for Position integrity: Protection levels Environment Horizontal Protection Level (in metres at 95 percentile) Class A Class B Class C Open Area 1 10 18 Urban Area 10 30 110 NOTE: The integrity risk to be taken into account is de... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10 Position day-to-day repeatability in the Horizontal Plane | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.1 Definition | The day-to-day repeatability of the position characterizes the ability of the GBLS to provide an estimation of its position which is stable in time when the GBLS repeats the same trajectory. This performance shows that the position error is mainly due to the effect of the Gaussian thermal noise in the receiver, and not... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.2 Metrics | The metric used to characterize the position day-to-day repeatability is the difference in horizontal Position estimations over M trials separated by one or several days in terms of its: • Mean value • Standard deviation • 95th percentiles distribution These metrics are defined as follows: • Let , ∗ ∈,, ∈, ... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3 Performance requirements | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.1 Use case: Moving Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.1.1 Operational environment: Open area | The performance requirements are specified in table 42. The location target follows the trajectory defined in clause A.4. Table 42: Performance requirements for day to day repeatability (Horizontal Plane), Moving location target, Open area Metric Max position error [m] Class A Class B Class C Mean error 0,015 0,15 0,50... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.1.2 Operational environment: Urban area | The performance requirements are specified in table 43. The location target follows the trajectory defined in clause A.4. Table 43: Performance requirements for day to day repeatability (Horizontal Plane), Moving location target, Urban area Metric Max position error [m] Class A Class B Class C Mean value 0,075 0,60 2,0... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.1.3 Operational environment: Asymmetric area | The performance requirements are specified in table 44. The location target follows the trajectory defined in clause A.4. Table 44: Performance requirements for day to day repeatability (Horizontal Plane), Moving location target, Asymmetric area Metric Max position error [m] Class A Class B Class C Mean value 0,075 0,6... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.2 Use case: Static Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.2.1 Operational environment: Open area | The performance requirements are specified in table 45. Table 45: Performance requirements for day to day repeatability (Horizontal Plane), Static location target, Open area Metric Max position error [m] Class A Class B Class C Mean value 0,015 0,15 0,50 Standard deviation 0,02 0,20 0,60 95th percentile 0,025 0,25 0,70 |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.2.2 Operational environment: Urban area | The performance requirements are specified in table 46. Table 46: Performance requirements for day to day repeatability (Horizontal Plane), Static location target, Urban area Metric Max position error [m] Class A Class B Class C Mean value 0,075 0,60 2,00 Standard deviation 0,10 0,80 2,40 95th percentile 0,125 1,00 2,8... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.10.3.2.3 Operational environment: Asymmetric area | The performance requirements are specified in table 47. Table 47: Performance requirements for day to day repeatability (Horizontal Plane), Static location target, Asymmetric area Metric Max position error [m] Class A Class B Class C Mean value 0,075 0,60 2,00 Standard deviation 0,10 0,80 2,40 95th percentile 0,125 1,0... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11 Position day-to-day repeatability in the Vertical Plane | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.1 Definition | The day-to-day repeatability of the position characterizes the ability of the GBLS to provide an estimation of its position which is stable in time when the GBLS repeats the same trajectory. The position day-to-day repeatability is measured by computing the maximum of the difference (error) between the vertical positio... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.2 Metrics | The metric used to characterize the position day-to-day repeatability is the difference in horizontal Position estimations over M trials separated by one or several days in terms of its: • Mean value • Standard deviation • 95th percentiles distribution These metrics are defined as follows: • Let , ∗∈,,∈,... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3 Performance requirements | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.1 Use case: Moving Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.1.1 Operational environment: Open area | The performance requirements are specified in table 48. The location target follows the trajectory defined in clause A.4. Table 48: Performance requirements for day to day repeatability (Vertical Plane), Moving location target, Open area Metric Max position error [m] Class A Class B Class C Mean error 0,025 0,25 0,75 S... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.1.2 Operational environment: Urban area | The performance requirements are specified in table 49. The location target follows the trajectory defined in clause A.4. Table 49: Performance requirements for day to day repeatability (Vertical Plane), Moving location target, Urban area Metric Max position error [m] Class A Class B Class C Mean value 0,15 1,20 4,00 S... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.1.3 Operational environment: Asymmetric area | The performance requirements are specified in table 50. The location target follows the trajectory defined in clause A.4. Table 50: Performance requirements for day to day repeatability (Vertical Plane), Moving location target, Asymmetric area Metric Max position error [m] Class A Class B Class C Mean value 0,15 1,20 4... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.2 Use case: Static Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.2.1 Operational environment: Open area | The performance requirements are specified in table 51. Table 51: Performance requirements for day to day repeatability (Vertical Plane), Static location target, Open area Metric Max position error [m] Class A Class B Class C Mean value 0,03 0,30 1,00 Standard deviation 0,04 0,40 1,20 95th percentile 0,08 0,50 2,00 ETS... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.2.2 Operational environment: Urban area | The performance requirements are specified in table 52. Table 52: Performance requirements for day to day repeatability (Vertical Plane), Static location target, Urban area Metric Max position error [m] Class A Class B Class C Mean value 0,15 1,00 5,00 Standard deviation 0,20 1,50 5,00 95th percentile 0,30 2,00 10,00 |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.11.3.2.3 Operational environment: Asymmetric area | The performance requirements are specified in table 53. Table 53: Performance requirements for day to day repeatability (Vertical Plane), Static location target, Asymmetric area Metric Max position error [m] Class A Class B Class C Mean value 0,15 1,00 5,00 Standard deviation 0,20 1,50 5,00 95th percentile 0,30 2,00 10... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12 Time-To-Fix Ambiguity (TTFA) | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.1 Definition | TTFA is the time taken by the GBLS to provide location-related data with a completed resolution of the integer ambiguity for the carrier phase measurement, thus achieving the best accuracy for differential positioning. The TTFA starts at the instant when one message of each required differential data has been received ... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.2 Metrics | The TTFA is the elapsed time between the instant when the process of the GBLS applying a differential model is started (i.e. the time when at least one message of each type in the differential protocol is received) and the instant when the expected highest accuracy output is achieved by the positioning output of the GB... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3 Performance requirements | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.1 Use case: Moving Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.1.1 Operational environment: Open area | The performance requirements are specified in table 54. The location target follows the trajectory defined in clause A.4. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of better than 5 cm. Table 54: Performance requirements f... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.1.2 Operational environment: Urban area | The performance requirements are specified in table 55. The location target follows the trajectory defined in clause A.4. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 15 cm. Table 55: Performance requirements for TTFA, Mo... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.1.3 Operational environment: Asymmetric area | The performance requirements are specified in table 56. The location target follows the trajectory defined in clause A.4. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 15 cm. ETSI ETSI TS 103 246-3 V1.3.1 (2020-10) 43 Tabl... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.2 Use case: Static Location Target | |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.2.1 Operational environment: Open area | The performance requirements are specified in table 57. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 5 cm. Table 57: Performance requirements for TTFA, Static location target, Open area Metric TTFF[s] Class A Class B Clas... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.2.2 Operational environment: Urban area | The performance requirements are specified in table 58. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 15 cm. Table 58: Performance requirements for TTFA, Static location target, Urban area Metric (as per clause 4.2) TTFF[s... |
0caae3e3690e823d4cf338177c4d7bd4 | 103 246-3 | 5.12.3.2.3 Operational environment: Asymmetric area | The performance requirements are specified in table 59. In all cases the requirements are dependent on achieving a maximum 95th percentile horizontal and vertical (if applicable) positioning error of 15 cm. Table 59: Performance requirements for TTFA, Static location target, Asymmetric area Metric TTFF[s] Class A Class... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 1 Scope | The present document defines the architecture applicable to location systems. This is a "functional" architecture, meaning that the system is defined in terms of discrete functional elements connected to other internal or external functional elements via associated "logical" interfaces. These functional elements and in... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 2 References | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 3 Definition of terms, symbols and abbreviations | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: accuracy (or error): difference between a measured or estimated value and its real value application module: entity in charge of retrieving from a location system the location-related data associated with one or more location targets and processing it... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 3.2 Symbols | Void. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project A-GNSS Assisted GNSS AOA Angle Of Arrival CF Central Facility CID Cell IDentifier CMM Central Management Module CPCM Centralized Position Calculation Module CPU Central Processing Unit CRC Cyclic Redunda... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 4 Requirements for GNSS-Based Location Systems | The Reference Architecture for GNSS-Based Location Systems (GBLS), as defined in the following clauses, is derived from the GBLS Functional Requirements [10] which are intended to provide one or more users with location-related data (as defined in ETSI TS 103 246-1 [10]) associated with one or more Location Targets. An... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5 GBLS Architecture (Level 1) | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.1 Level 1 architecture functional blocks and logical interfaces | The functional requirements summarized in clause 4 are used in this clause to define mandatory and optional functional elements to be included in the GBLS Architecture. These elements are grouped into higher level functional blocks with common features. In clauses 6 and 7, the GBLS Architecture is defined hierarchicall... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.2 External Functional Blocks | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.2.1 GNSS and Other External Systems | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.2.1.1 GNSS | The elements defined in this clause and in clause 5.2.1.2 are external to the GBLS, and have interfaces with it. GNSS provide autonomous geo-spatial positioning with global or regional coverage. The following GNSS systems are supported in the present document: • GPS and Modernized GPS [1], [2] and [3]; • Galileo [4]; •... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.2.1.2 Other External Systems | Other external systems may include: • Terrestrial telecommunications networks providing position information (e.g. 3G, 4G, Wi-Fi®, etc.). |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.2.2 Application(s) | One or more user applications in external systems or subsystems may interface to the GBLS. An application may obtain location-related data to build value-added services (such as fleet tracking, collision avoidance systems and asset tracking), with which the user(s) may interact. In case the GBLS does not broadcast its ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.3 GBLS Functions | The overall functions provided by the GBLS are: • Sensor Management to collect measurement data from the sensors attached to the target and to provide assistance data. • Position Calculation that derives and issues the positioning and other parameters of a location target(s) from the sensor measurements, and possibly f... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 5.4 GBLS External Interfaces | The primary inputs to the GBLS are signals and data from GNSS and other sensors. The GBLS shall communicate with external applications to accept requests and subsequently provide requested location-related data. For D-GNSS, RTK and PPP solutions, RTCM 104 [9] and [11] should be applied for a direct compatibility. For d... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6 GBLS Architecture (Level 2) | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.1 Level 2 architecture mandatory and optional components | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.1.1 General | Level 2 architecture is derived from Figure 5-1 where mandatory elements that shall be used for any implementation profile are indicated, together with optional components. ETSI ETSI TS 103 246-2 V1.3.1 (2020-10) 18 Figure 6-1: GBLS architecture (level 2) - Overall view In this architecture level, Target Positioning Mo... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.1.2 GBLS architecture with Target Positioning Module only | Target Positioning Module Data Exchange with GNSS & other external positioning systems Data Exchange with external Service Provider On-Board Position Calculation Module Sensor Management (GNSS and other Sensors) Application Interface Module Data Exchange with Location-based Application(s) Core Interface Core Interface ... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.2 Positioning Module (PM) | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.2.1 Sensor Management | The sensor management function provides the interface between each sensor and the On-Board Position Calculation module including: • sensor-to-sensor feedback (e.g. INS-aided GNSS tracking); • the data encoding of sensor measurements to the Position Calculation module and vice-versa; • the data encoding of support infor... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.2.2 On-Board Position Calculation Module (OBPCM) | The Position Calculation module consists of algorithms to process the measurements received from the sensors and produce location-related data. These algorithms can be shared with the Centralized Position Calculation module in different ways: • Allocated only to the On-Board module (e.g. for simple or self-contained sy... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.2.3 Application Interface Module | The Application Interface module shall support the following functions: • request handling function: this function includes forwarding the required location-related data according to the conditions specified by the request. It also manages the priority amongst the various requests received from one or several applicati... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.3 Central Facility (CF) | |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.3.1 Centralized Position Calculation Module (CPCM) | This Position Calculation module consists of algorithms that can be shared as defined in clause 6.2.2. |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.3.2 Central Management Module (CMM) | The Central Management module shall provide one or more of the following services: • Terminal assistance function: the purpose of this function is to manage assistance data that the Position Calculation module may require in order to perform its position calculation functions. ETSI ETSI TS 103 246-2 V1.3.1 (2020-10) 22... |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.3.3 Application Interface Module | The Application Interface module is functionally identical to that defined for the PM (see clause 6.2.3). |
0f9e4c9dc9e6c3b716a463710e33a3cc | 103 246-2 | 6.4 Core Interface | The core interface manages all location data exchanges between: • the sensors and the On-Board Location module; • the Position Calculation module and the Application Interface module; • the On-board Position Calculation module and the Centralized Position Calculation module; • the Centralized Position Calculation modul... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.