hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
76fe69487daaaeaddd47594232385711 | 103 246-4 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project API Application Programming Interface ASN Abstract Syntax Notation BFN Beam Forming Network CL Confidence Level CNR Carrier-to-Noise Ratio D-GNSS Differential GNSS DoA Direction of Arrival DTD Document T... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4 Data Exchange Requirements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.1 Context | The GBLS data that shall or may be exchanged is defined in ETSI TS 103 246-2 [2] in general terms for two main mandatory cases and one optional case: 1) externally to applications using the GBLS (mandatory); 2) externally to external D-GNSS service provider (optional, required when external D-GNSS services are used as ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2 Protocol Choice and Compatibility | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.1 LSEP (MLP) | LSEP is based on the procedures, messages and elements of OMA MLP [4]. Annex A provides a rationale for this choice. MLP is intended for a Mobile Location Service (MLS) Client (e.g. a GBLS external application) to obtain the related data of a location target (e.g. mobile terminal, GBLS Positioning Module, etc.) from a ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.2 LSIP (LPPe) | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.2.1 General | LSIP is defined as an extension to LPP and relies also on the procedures, messages and elements of LPPe [5]. Annex A provides a rationale for this choice. As LPPe is also defined as an extension to, and relies on the main elements of LPP [6] then LSIP is in effect based on both of these protocols. LPPe is intended to p... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.2.2 LSIP Data Exchange Requirements | A summary of additional data for LSIP (i.e. not included in LPPe) requiring to be transferred over the GBLS interfaces defined in ETSI TS 103 246-2 [2] is shown in table 4.1 (defined for each type of LSIP procedure: Location information exchange and Assistance data exchange). Table 4.1: Extension data for LSIP procedur... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.2.3 Additional LSIP IEs for GBLS using differential GNSS positioning methods | The present document should consider a maximal compatibility with RTCM standards 10402.3 [7] and 10403.2 [8] and should thus consider RTCM messages as new extension to the LPPe. The RTCM message exchanges will essentially depend on the D-GNSS methods and also with the architecture but generalities can be put here: • RT... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.3 EPDD (RTCM 104) | In the particular case where GBLS shall take benefits from differential GNSS services as provided by an external differential service provider, to meet its requirements, the GBLS protocol EPDD should preferably conform to the existing external GNSS service provider data protocols. Since the existing GNSS service provid... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 4.2.4 LSEP/MLP and LSIP/LPPe Terminology | Table 4.4 defines the correspondence between GBLS and 3GPP/OMA MLP/LPPe terminology. Table 4.4: MLP/LPPe and LSEP/LSIP terminology relationships MLP/LPPe LSEP/LSIP Term Definition Term Definition MS Mobile Station Location Target Positioning Module See definition in ETSI TS 103 246-2 [2] MSID MS identifier MSID Identif... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 5 LSEP Requirements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 5.1 LSEP Services and Procedures | LSEP data transactions (i.e. between the GBLS and an external application) shall use the service schemes as defined for MLP [4] including the messages as follows: 1) Standard Location Immediate Service consisting: - Standard Location Immediate Request. - Standard Location Immediate Answer. - Standard Location Immediate... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 5.2 Extension of MLP for LSEP | The MLP specification has been designed with extensibility in mind. Design principles employed to achieve this include: • Separate DTDs for definitions that are common to all messages, e.g. client address and shapes, so they can be re-used. • A parameter (Element) extension mechanism allowing the addition of new parame... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 5.3 LSEP Data Exchange Message Definition | The LSEP Element (parameter) extensions to MLP messages are shown in table 5.1. Table 5.1: LSEP Element extensions for MLP messages MLP Message LSEP parameter extensions Standard Location Immediate Request LSEP_msids LSEP_eqop LSEP_req_info Standard Location Immediate Answer LSEP_pd Standard Location Immediate Report L... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6 LSIP Requirements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.1 LSIP Services and Procedures | LSIP data transactions (i.e. between internal modules of the GBLS) shall use the service schemes as defined for LPPe, see OMA-TS-LPPe [5] as follows: 1) LPP Provide/Request Capabilities (plus LPPe reversed mode). 2) LPP Provide/Request Assistance Data. 3) LPP Provide/Request Location Information (plus LPPe reversed mod... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.2 Extension of LPPe/LPP for LSIP | LSIP (and LPPe) make use of the option included in LPP messages to define extensions to these messages by means of the EPDU container. Within this EPDU, the Identifier may be defined as follows: • EPDU-ID: 2 • EPDU Defining entity ETSI Technical Committee SES • Method name GBLS LSIP • Reference LSIP NOTE 1: This EPDU w... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3 LSIP Data Exchange Message Definition | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.1 General | LSIP re-uses the message and data definitions from LPP/LPPe. In addition the contents of each LSIP IE extension to LPP messages are specified in clauses 6.3.2 and 6.3.3, using ASN.1 to specify the syntax and using tables, when needed, to provide information on the fields and parameters in the message. The information e... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.2 IE Extensions of LPP/LPPe for LSIP | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.2.1 Message Extensions | The IE LSIP-MessageExtension carries version information and the message data carried in the extension. A single LSIP-MessageExtension carries one extension message and all the LSIP information associated with that type. One LSIP-MessageExtension data type is carried within one EPDU-Body OCTET STRING parameter in an LP... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.2.2 LPPe data type imports | LSIP uses as far as possible the data definitions from [5] in order to avoid duplication. This ASN.1 snippet defines these imports. -- ASN1START LSIP DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS GNSS-ID, GNSS-SignalID, GNSS-SignalIDs, GNSS-SystemTime, SV-ID, ECID-SignalMeasurementInformation, CellGlobalIdGERAN, CellGlo... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.3 LSIP Extension Messages | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.3.1 Request Assistance Data | The LSIP-RequestAssistanceData message is used by the "target" entity to request assistance data from the "server" entity. -- ASN1START LSIP-RequestAssistanceData::= SEQUENCE { odometer-ProvideAssistanceData LSIP-Odometer-RequestAssistanceData OPTIONAL, ... } -- ASN1STOP LSIP-RequestAssistanceData information elements ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.3.2 Provide Assistance Data | The LSIP-ProvideAssistanceData message is used by the "server" entity to provide assistance data to the "target" entity either in response to a request from the "target" entity or in an unsolicited manner. -- ASN1START LSIP-ProvideAssistanceData::= SEQUENCE { odometer-ProvideAssistanceData LSIP-Odometer-ProvideAssistan... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.3.3 Request Location Information | The LSIP-RequestLocationInformation message is used by the "server" entity to request location-related data to "target" entity. -- ASN1START LSIP-RequestLocationInformation::= SEQUENCE { commonIEsRequestLocationInformation LSIP-CommonIEsRequestLocationInformation OPTIONAL, gnss-RequestLocationInformation LSIP-GNSS-Requ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 6.3.3.4 Provide Location Information | The LSIP-ProvideLocationInformation message is used by a "target" entity to provide location-related data to a "server" entity. -- ASN1START LSIP-ProvideLocationInformation::= SEQUENCE { commonIEsProvideLocationInformation LSIP-CommonIEsProvideLocationInformation OPTIONAL gnss-ProvideLocationInformation LSIP-GNSS-Provi... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7 LSEP Element Definitions | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.1 Overview | MLP extension elements (parameters) for LSEP messages (see clause 5) are defined in clauses 7.2 and 7.3, using XML DTD representation. Other elements defined for LSEP messages and not listed below are the same as in MLP [4], but any associated syntax shall be ignored. Elements are defined from a semantic point of view ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.2 LSEP Child Elements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.2.1 Identity elements | <!ENTITY % extension.param "LSEP_msids"> <!ELEMENT LSEP_msids (emi_srcs)> <!ELEMENT emi_srcs (#PCDATA)> |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.2.2 Location elements | <!ENTITY % extension.param "LSEP_req_info"> <!ELEMENT LSEP_req_info (auth_req?, accel_req?, emidata_req)> <!ELEMENT auth_req EMPTY> auth_req ( YES | NO ) "NO"> <!ELEMENT accel_req EMPTY> <!ATTLIST accel_req info_type ( LINEAR | ANGULAR ) "LINEAR"> <!ELEMENT emidata_req ( YES | NO ) "NO"> The following rules apply to th... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.2.3 Quality of Position elements | <!ENTITY % extension.param "LSEP_eqop"> <!ELEMENT LSEP_eqop (h_conf_lev?, v_conf_lev?, (vel_acc | vel_conf_lev)?, accel_conf_lev?, head_conf_lev? <!ENTITY % extension.param "LSEP_qop"> <!ELEMENT LSEP_qop (h_conf_lev?, v_conf_lev?, (vel_acc | vel_conf_lev)?, accel_conf_lev?, head_conf_lev? <!ELEMENT h_conf_lev (#PCDATA)... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3 LSEP Sub-Child Elements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.1 accel | Definition The acceleration of the location target, in m/s². When used for relative location, this parameter expresses the acceleration relative to the Reference Point. DTD type: Element Format: Signed decimal value, resolution 0,1 Defined values: range: [-50; 50] Default value: N/A Example in XML: <accel>2.5</accel> N... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.2 accel_conf_lev | Definition This element is the level of reliability required by the application regarding the acceleration accuracy estimate provided by the location system. It is expressed as log10(Level of reliability). DTD type: Element Format: Negative decimal value, resolution 0,01 Defined values: range: [-10; 0] Default value: -... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.3 accel_unc | Definition Estimate of the acceleration uncertainty, in m/s². DTD type: Element Format: Positive decimal value, resolution 0,1 Defined values: range: [0; 10] Default value: Example in XML: <accel_unc>1</accel_unc> Note: |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.4 accel_req | Definition This element indicates that the acceleration information of the location target identified by MSID is required. DTD type: Element Format: Void Defined values: - Default value: - Example in XML: <accel_req /> Note: - ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 27 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.5 auth_flag | Definition Defines the authentication status of PVT location-related data. DTD Type: Element Format: Char string Defined values: NO Spoofing attempt is detected YES Location-related data is authentic UNKNOWN Authentication procedure could not conclude Default value: - Example in XML: <auth_flag>YES</auth_flag> Note: - |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.6 auth_req | Definition Indicates if the location system is required to provide the related (parent) location-related data with associated authentication information. Type: Attribute Format: Boolean Defined values: YES Authenticity of the location-related data shall be determined and provided. NO Authenticity of the location-relate... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.7 conf_class | Definition Determines whether the parent confidence level provided shall be interpreted as an integrity risk or a level of reliability. DTD Type: attribute Format: Char string Defined values: INFO Parent confidence level shall be interpreted as the level of reliability of the required error estimate. ALERT Parent confi... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.8 emidata_req | Definition Indicates that the Direction of Arrival of an EMI source is required. DTD Type: Element Format: Void Defined values: - Default value: - Example in XML: < emidata_req /> Note: - ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 28 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.9 h_acc | Definition Accuracy of horizontal position in metres. DTD Type: Element Format: Positive decimal value, resolution 0,001 Defined values: range: [0; 10 000] Default value: - Example in XML: <h_acc>0.1</h_acc> Note: |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.10 h_acc_not_met | Definition Indication that the requested horizontal position QoS was not met, if needed. DTD Type: Element Format: Void Defined values: - Default value: - Example in XML: - Note: Only applicable if the request was for best effort class, i.e. a horizontal position estimate is returned (rather than an error) although the... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.11 h_conf_lev | Definition Depending on the value of attribute "conf_class", it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the horizontal position error estimate. It is expressed as log10(Level of reliability)... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.12 h_int_alert | Definition Indication that the location system detects location-related data mis-integrity. DTD Type: Element Format: Void Defined values: - Default value: - Example in XML: - Note: Only applicable in case "conf_class" under "h_conf_lev" is set to "ALERT". ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 29 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.13 head_conf_lev | Definition Represents the preferred level of reliability of the heading error estimate. It is expressed as log10(Level of reliability). DTD Type: Element Format: Negative decimal value, resolution 0,01 Defined values: range: [-10; 0] Default value: Example in XML: <head_conf_lev>-2</head_conf_lev> Note: - |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.14 head_req | Definition Indicates that the heading information of the location target identified by MSID is required. DTD type: Element Format: Void Defined values: - Default value: - Example in XML: <head_req /> Note: - |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.15 head_unc | Definition Estimate of the heading uncertainty, in degrees. DTD type: Element Format: Positive decimal value, resolution 0,1 Defined values: range: [0; 10] Default value: - Example in XML: <head_unc>1</head_unc> Note: 7.3.16 LSEP-msids Description Represents an identifier of a GBLS location target. Type: Element Format... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.17 v_acc | Definition Accuracy of requested vertical position in metres. DTD Type: Element Format: Positive decimal value, resolution 0,001 Defined values: range: [0; 10 000] Default value: - Example in XML: <v_acc>0.1</v_acc> Note: ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 30 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.18 v_acc_not_met | Definition Indication that the requested vertical position QoS was not met, if needed. DTD Type: Element Format: Void Defined values: - Default value: - Example in XML: - Note: Only applicable if the request was for best effort class, i.e. a vertical position estimate is returned (rather than an error) although the req... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.19 v_conf_lev | Definition Depending on the value of attribute "conf_class", it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the vertical position error estimate. It is expressed as log10(Level of reliability) o... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.20 v_unc | Definition Estimate of the altitude uncertainty, in metres. DTD type: Element Format: Positive decimal value, resolution 0,01 Defined values: range: [0; 100] Default value: - Example in XML: <v_unc>0.5</v_unc> Note: Usage of this element, in particular regarding the integrity concept, is defined in clause 7.2.2 (locati... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.21 v_req | Definition Indicates that the altitude information (or vertical position) of the location target identified by MSID is required. DTD type: Element Format: Void Defined values: - Default value: - Example in XML: <v_req /> Note: - ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 31 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.22 vel_acc | Definition Accuracy of requested velocity in m/s. DTD type: Element Format: Positive decimal value, resolution 0,01 Defined values: range: [0; 5] Default value: - Example in XML: <vel_acc>1</vel_acc> Note: - |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.23 vel_acc_not_met | Definition Indication that the requested velocity QoS was not met, if needed. DTD Type: Element Format: Void Defined values: - Default value: - Example in XML: - Note: Only applicable if the request was for best effort class, i.e. a velocity estimate is provided (rather than an error) although the requested QoS require... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.24 vel_conf_lev | Definition Depending on the value of attribute "conf_class", it represents either the required integrity risk which shall be used by the location system in its integrity determination process, or the preferred level of reliability of the vertical position error estimate. It is expressed as log10(Level of reliability) o... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.25 vel_unc | Definition Estimate of the velocity uncertainty, in m/s. DTD type: Element Format: Positive decimal value, resolution 0,01 Defined values: range: [0; 5] Default value: - Example in XML: <head_unc>1</head_unc> Note: |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 7.3.26 vel_req | Definition This element indicates that the velocity information of the location target identified by MSID is required. DTD type: Element Format: Void Defined values: - Default value: - Example in XML: <vel_req /> Note: - ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 32 |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8 LSIP Information Elements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.1 LSIP Common Positioning IEs | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.1.1 General | Clauses 8.1.2 and 8.1.3 define IEs that carry common low-level IEs for the corresponding message extensions. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.1.2 LSIP-CommonIEsRequestLocationInformation | -- ASN1START LSIP-CommonIEsRequestLocationInformation ::= SEQUENCE { triggeredReporting LSIP-TriggeredReportingCriteria OPTIONAL, -- Cond ECID qosReq LSIP-QoSReq OPTIONAL, -- Need ON locationTargetIdReq LSIP-LocationTargetIdReq OPTIONAL, ... } LSIP-TriggeredReportingCriteria ::= SEQUENCE { ChangeArea BOOLEAN, distanceE... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.1.3 LSIP-CommonIEsProvideLocationInformation | -- ASN1START LSIP-CommonIEsProvideLocationInformation ::= SEQUENCE { QoS LSIP-QoS OPTIONAL, alerts LSIP-IntegrityAlerts OPTIONAL, locatioTargetId LSIP-LocationTargetId OPTIONAL, locationSource LSIP-LocationSource OPTIONAL, --Cond LocationSource ... } LSIP-QoS::= SEQUENCE { confidenceLevels LSIP-ConfidenceLevels OPTIONA... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.2 LSIP Common Low-Level IEs | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.2.1 General | Clauses 8.2.2 to 8.2.4 define common IEs that are applicable to more than one LSIP positioning method. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.2.2 LSIP-ConfidenceLevels | -- ASN1START LSIP-ConfidenceLevels::= SEQUENCE { velocityCL INTEGER(0..100) OPTIONAL, headingCL INTEGER(0..100) OPTIONAL, accelCL INTEGER(0..100) OPTIONAL, } -- ASN1STOP LSIP-ConfidenceLevels field descriptions • velocityCL • accelCL • headingCL In each case the confidence level is defined in %. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.2.3 LSIP-ErrorMeasurements | -- ASN1START LSIP-ErrorMeasurements ::= SEQUENCE { accelerationUnc INTEGER(0..100) OPTIONAL, headingUnc INTEGER(0..100) OPTIONAL, ... } -- ASN1STOP LSIP-ErrorMeasurements field descriptions accelerationUnc • acceleration uncertainty in 0,1 ms-2 headingUnc • heading uncertainty in 0,1 degrees |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.2.4 LSIP-QosIndicators | -- ASN1START LSIP-QosIndicators::= SEQUENCE { horizontalUncNotMet BOOLEAN, verticalUncNotMet BOOLEAN, velocityUncNotMet BOOLEAN, accelerationUncNotMet BOOLEAN, headingUncNotMet BOOLEAN, ... } -- ASN1STOP ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 37 LSIP-QosIndicators field descriptions horizontalUncNotMet TRUE indicates ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3 Specific Positioning Method IEs | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.1 General | Clauses 8.3.2 to 8.3.4 define low-level IEs for specific LSIP messages. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.2 GNSS Positioning | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.2.1 LSIP-GNSS-RequestLocationInformation | -- ASN1START LSIP-GNSS-PositioningInstructions ::= SEQUENCE { gnssRfSamplesReq LSIP-GNSS-RFSamplesReq OPTIONAL, -- Need ON gnssRfSamplesParameters LSIP-GNSS-RFSamplesControlParameters OPTIONAL, --Cond RFsamplesReq gnssMeasurementsReq LSIP-GNSS-MeasurementsReq OPTIONAL, -- Need ON gnssNavMessageReq LSIP-GNSS-NavMessageR... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.2.2 LSIP-GNSS-ProvideLocationInformation | -- ASN1START LSIP-GNSS-ProvideLocationInformation ::= SEQUENCE { rfSamplingMeasurements LSIP-GNSS-RfSamples OPTIONAL, gnssObservablesMeasurements LSIP-GNSS-Measurements OPTIONAL, gnssNavigationMessageData LSIP-GNSS-NavMessage OPTIONAL, gnssAuthentication LSIP-GNSS-Authentication OPTIONAL, … } LSIP-GNSS-RfSamples ::= SE... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.3 Odometer positioning | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.3.1 LSIP-Odometer-RequestAssistanceData | -- ASN1START LSIP-Odometer-RequestAssistanceData::= SEQUENCE { wheelSizereq BOOLEAN, ... ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 39 } -- ASN1STOP LSIP-Odometer-RequestAssistanceData field descriptions wheelSizereq • request for diameter of wheel. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.3.2 LSIP-Odometer-ProvideAssistanceData | -- ASN1START LSIP-Odometer-ProvideAssistanceData::= SEQUENCE { wheelSize INTEGER (0..1000), ... } -- ASN1STOP LSIP-Odometer-ProvideAssistanceData field descriptions wheelsize • diameter of wheel in millimetres. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.3.3 LSIP-Odometer-RequestLocationInformation | -- ASN1START LSIP-Odometer-RequestLocationInformation::= SEQUENCE { odometerInformationType SEQUENCE{ travelledDistanceReq BOOLEAN, odomVelocityReq BOOLEAN, ... } ... } -- ASN1STOP LSIP-Odometer-RequestLocationInformation field descriptions odometerInformationType This field identifies the sensor. travelledDistanceReq ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.3.4 LSIP-Odometer-ProvideLocationInformation | -- ASN1START LSIP-Odometer-ProvideLocationInformation::= SEQUENCE { travelledDistance INTEGER (0..16383) OPTIONAL, Cond odomDistReq odomVelocity INTEGER (0..1023) OPTIONAL, Cond odomVelReq reverseFlag BOOLEAN ... } -- ASN1STOP Conditional presence Explanation odomDistReq The field is mandatory present if travelledDista... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.4 Beam Forming Network Positioning | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.4.1 LSIP-BFN-RequestLocationInformation | -- ASN1START LSIP-BFN-RequestLocationInformation::= SEQUENCE { MaxNbrofJammersreq INTEGER (1.. 8) OPTIONAL, JammerPowerReq BOOLEAN, doAReq BOOLEAN, ... } -- ASN1STOP LSIP-BFN-RequestLocationInformation field descriptions MaxNbrofJammersreq • request detected number of jammers by the BFN limited to a maximum. JammerPowe... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.4.2 LSIP-BFN-ProvideLocationInformation | -- ASN1START LSIP-BFN-ProvideLocationInformation::= SEQUENCE { detectedNbrofJammers INTEGER (1.. maxNbrofJammers) OPTIONAL, jammerID SEQUENCE (SIZE (1..maxNbrJammers) OF LSIP-JammerSignal OPTIONAL, ... } maxNbrJammers INTEGER ::= 8 -- ASN1STOP LSIP-BFN-ProvideLocationInformation field descriptions detectedNbrofJammers ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.4.3 LSIP-JammerSignal | -- ASN1START LSIP-Jammer Signal::= SEQUENCE { JammerPower LSIP-JammingPower OPTIONAL, JammerDoA LSIP-DirectionOfArrival OPTIONAL, ... LSIP-JammingPower::= SEQUENCE { powerEstimate INTEGER (-10..30]) OPTIONAL, powerEstError INTEGER (0..50]) OPTIONAL, ... ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 41 LSIP-DirectionOfArrival... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 8.3.5 Mapping Positioning | For further study. |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9 D-GNSS information elements | |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9.1 General | All of the following information is extracted from RTCM 10402.3 [7] or RTCM 10403.2 [8]. Presented here is only the list of messages required to process a particular D-GNSS method. More details about the detailed messages contents, data types and data fields will be found in the respective RTCM 10402.3 [7] and RTCM 104... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9.2 Case of conventional D-GNSS | Conventional D-GNSS compatible with RTCM 104 version 3 -recommended (see RTCM 10403.2 [8] paragraph 3.2 for message type summary, paragraph 3.3 for data type and paragraph 3.4 for data fields definitions). Table 9.1: RTCM messages to be used for conventional D-GNSS differential GNSS positioning method Group name Servic... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9.3 Case of RTK | Local RTK (see RTCM 10403.2 [8] paragraph 3.2 for message type summary, paragraph 3.3 for data type and paragraph 3.4 for data fields definitions). Table 9.3: RTCM messages to be used for local RTK differential GNSS positioning method Group name Service Minimum service operation Full service operation Observations GPS ... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9.4 NRTK | NRTK/MAC (see RTCM 10403.2 [8] paragraph 3.2 for message type summary, paragraph 3.3 for data type and paragraph 3.4 for data fields definitions). ETSI ETSI TS 103 246-4 V1.3.1 (2020-10) 43 Table 9.4: RTCM messages to be used for network RTK/MAC differential GNSS positioning method Group name Service Minimum service op... |
76fe69487daaaeaddd47594232385711 | 103 246-4 | 9.5 PPP | PPP (see RTCM 10403.2 [8] paragraph 3.2 for message type summary, paragraph 3.3 for data type and paragraph 3.4 for data fields definitions). Table 9.7: RTCM messages to be used for PPP differential GNSS positioning method Group name Service Minimum service operation Full service operation Orbit and clock corrections G... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 1 Scope | The present document defines the functional requirements applicable to location systems, based on a summary of types of applications relying on location-related data provided by location systems. The present document can be considered as the Stage 1 characterization of location systems according to the ITU/3GPP approac... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 2 References | |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 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... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 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... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 3 Definition of terms, symbols and abbreviations | |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 3.1 Terms | For the purposes of the present document the following terms apply: Accumulated Delta (or Doppler) Range (ADR): pseudorange-rate measurement using the carrier which measures the instantaneous phase of the signal (modulo 1 cycle) plus some arbitrary number of integer cycles NOTE: Once the receiver is tracking the satell... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 3.2 Symbols | Void. |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ADAS Advanced Driver Assistance Systems ADR Accumulated Delta (or Doppler) Range ADS-B Automatic Dependent Surveillance – Broadcast A-SMGCS Advanced Surface Movement Guidance and Control System ATC Air T... |
a2ed1c18e57b2a5468fbd4579c87a077 | 103 246-1 | 4 Context description |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.