hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
da8af906ca51c9e372179c3e689b2ddd | 103 242-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 101 569-1 [1], ISO/IEC 9646-7 [3] and ISO/IEC 9646-1 [2] apply. In particular, the following terms given in ISO/IEC 9646-1 [2] apply: Implementation Conformance Statement (ICS): statement made by the supplier of an implementation or sy... |
da8af906ca51c9e372179c3e689b2ddd | 103 242-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ALG Application Layer Gateway ATS Abstract Test Suite CLAT Customer-side XLAT DHCP Dynamic Host Configuration Protocol FTP File Transfer Protocol GRT Global Routing Table ICMP Internet Control Message Protocol IP Internet Protocol IPv4 IP vers... |
da8af906ca51c9e372179c3e689b2ddd | 103 242-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming and ordering of the proforma items. An ICS which conforms to the present document shall be a ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 1 Scope | The present document contains the definition of the logical channel for Assisted-GNSS data broadcast, together with the reference architecture underlying the data broadcast mechanism. The protocol thus defined, called Broadcast Positioning Protocol (BPP), is used to broadcast GNSS assistance data to target device(s) th... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 2 References | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 3 Definitions and abbreviations | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 3.1 Definitions | For the purpose of the present document, the following terms and definitions apply. location server: physical or logical entity that manages the navigation assistance data, and that provides these assistance data to the Target Device in order to help determine their position location radio network (N/W): network throug... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: A-GNSS Assisted-GNSS ASN Abstract Syntax Notation BIPM International Bureau of Weights and Measures BPP Broadcast Positioning Protocol CAN Controller Area Network CGC Complementary ground Component CNAV Civil NAVigation CRL Communications Rese... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 4 Reference System Architecture | Figure 4.1 gives the reference system architecture corresponding to the BPP protocol. Figure 4.1: BPP System Reference Architecture The system is composed of the following entities on one hand: • The Radio Network, with broadcast Service Capability such as Broadcast Network, allowing the broadcast of the different flux... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 5 BPP Protocol description | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 5.1 BPP sessions | A BPP session is used between a Location Server and the target device in order to transfer assistance data from the Location Server to the Target Devices. Each BPP session comprises one or more BPP transactions, with each BPP transaction performing a single operation: here it is limited to assistance data transfer. It ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 5.2 BPP Position Methods | Internal BPP positioning methods and associated signalling content are defined in the present document. This version of the present document defines A-GNSS positioning method. |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 5.3 BPP Messages | Each BPP transaction involves the transfer of one or more BPP messages from the location server to the target device. The general format of a BPP message consists of a set of common fields followed by a body. The body (which may be empty) contains information specific to a particular message type. Each message type con... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6 BPP Procedures | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.1 Introduction | This clause provides the different classes of procedures used in BPP. Compared to LPP procedures in ETSI TS 136 355 [1], the main procedure is the Assistance data delivery procedure. |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.2 Procedures related to Assistance Data Transfer | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.2.1 Assistance Data Delivery procedure | The Assistance Data Delivery procedure allows the server to provide unsolicited assistance data to the target and is shown in figure 6.1. ETSI ETSI TS 103 252 V1.1.1 (2015-06) 11 NOTE: The server sends a ProvideAssistanceData message to the target containing assistance data. This message may set the endTransaction IE t... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.2.2 Reception of BPP Provide Assistance Data | Upon receiving a ProvideAssistanceData message, the target device shall: • for each positioning method contained in the message: - deliver the related assistance data to upper layers. |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.3 Error Handling Procedures | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.3.1 General | This clause describes how the receiving entity (here the target device) behaves in cases when it receives erroneous or unexpected data or detects that certain data are missing. |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.3.2 BPP Error Detection | Upon receiving any BPP message, the target device shall attempt to decode the message and verify the presence of any errors prior to using the following procedure: • if decoding errors are encountered: - if the receiver cannot determine that the received message is a BPP Error or Abort message: discard the received m... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.3.3 Reception of an BPP Error Message | Upon receiving an Error message, the target device shall: • abort any on-going procedure associated with the LPP-TransactionID if included in the received message. The target device may: • restart the aborted procedure taking into consideration the returned error information. ETSI ETSI TS 103 252 V1.1.1 (2015-06) 12 |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.4 Abort Procedure | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.4.1 General | The purpose of the abort procedure is to allow the target device to abort any on-going procedure for instance due to some unexpected event (e.g. recognition of error in the data sent by the location server). |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.4.2 Procedures related to Abort | Figure 6.2 shows the Abort procedure. NOTE 1: A procedure P is on-going between Location Server and Target Device. NOTE 2: Location Server determines that the procedure shall be aborted and sends an Abort message to Target Device carrying the transaction ID for procedure P. Target Device aborts procedure P. Figure 6.2:... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 6.4.3 Reception of an BPP Abort Message | Upon receiving an Abort message, the Target Device shall: • abort any on-going procedure associated with the transaction ID indicated in the message. |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7 BPP Information Element description | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.1 Introduction | As the present document is derived from ETSI TS 136 355 [1], most of the messages are derived from the LPP protocol as in [1]. All the procedures involving a dialog have been removed, as not relevant in a Broadcast Radio Network. The contents of each BPP message are specified in clause 7.2 using ASN.1 to specify the me... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.2 BPP PDU Structure | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.2.1 BPP-PDU-Definitions | This ASN.1 segment is the start of the BPP PDU definitions. -- ASN1START BPP-PDU-Definitions { itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) eps-Access (21) modules (3) BPP (7) version1 (1) BPP-PDU-Definitions (1) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN -- ASN1STOP |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.2.2 BPP-Message | The BPP-Message provides the complete set of information for an invocation or response pertaining to a BPP transaction. -- ASN1START BPP-Message ::= SEQUENCE { transactionID BPP-TransactionID OPTIONAL, -- Need ON endTransaction BOOLEAN, sequenceNumber OPTIONAL, -- Need ON BPP-MessageBody OPTIONAL -- Need ON } SequenceN... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.2.3 BPP-MessageBody | The BPP-MessageBody identifies the type of a BPP message and contains all BPP information specifically associated with that type. The BPP-MessageBody is used in the positioning procedures defined in clause 6. Type of BPP message contained in the BPP-MessageBody depends of the positioning procedure, according to the fol... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.2.4 BPP-TransactionID | The BPP-TransactionID identifies a particular BPP transaction and the initiator of the transaction. -- ASN1START BPP-TransactionID ::= SEQUENCE { initiator Initiator, transactionNumber , ... } Initiator ::= ENUMERATED { locationServer, targetDevice, ... } TransactionNumber ::= INTEGER (0..255) -- ASN1STOP ETSI ETSI TS ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.3 Message Body IEs | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.3.1 ProvideAssistanceData | The ProvideAssistanceData message body in a BPP message is used by the location server to provide assistance data to the target device in an unsolicited manner. (No possible dialog between the LS and the TD). -- ASN1START ProvideAssistanceData ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { provideAssistanceData... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.3.2 Abort | The Abort message body in a BPP message carries a request to abort an on-going BPP procedure. -- ASN1START Abort ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { abort-r9 Abort-r9-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } Abort-r9-IEs ::= SEQUENCE { commonIEsAbort OPTI... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.3.3 Error | The Error message body in a BPP message carries information concerning a BPP message that was received with errors. -- ASN1START Error ::= CHOICE { error-r9 Error-r9-IEs, criticalExtensionsFuture SEQUENCE {} } Error-r9-IEs ::= SEQUENCE { commonIEsError OPTIONAL, -- Need ON ..., } ETSI ETSI TS 103 252 V1.1.1 (2015-06) 1... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4 A-GNSS Positioning | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.1 GNSS Assistance Data | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.1.1 A-GNSS-ProvideAssistanceData | The IE A-GNSS-ProvideAssistanceData is used by the location server to provide assistance data to enable Target Device-based and Target Device-assisted A-GNSS. It may also be used to provide GNSS positioning specific error reasons. -- ASN1START A-GNSS-ProvideAssistanceData ::= SEQUENCE { gnss-CommonAssistData OPTIONAL, ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.1.2 GNSS-CommonAssistData | The IE GNSS-CommonAssistData is used by the location server to provide assistance data which can be used for any GNSS (e.g. GPS, Galileo, GLONASS, etc.). -- ASN1START GNSS-CommonAssistData ::= SEQUENCE { gnss-ReferenceTime GNSS-ReferenceTime OPTIONAL, -- Need ON gnss-ReferenceLocation GNSS-ReferenceLocation OPTIONAL, -... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.1.3 GNSS-GenericAssistData | The IE GNSS-GenericAssistData is used by the location server to provide assistance data for a specific GNSS (e.g. GPS, Galileo, GLONASS, etc.). The specific GNSS for which the provided assistance data are applicable is indicated by the IE GNSS-ID and (if applicable) by the IE SBAS-ID. Assistance for up to 16 GNSSs can ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2 GNSS Assistance Data Elements | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.1 GNSS-ReferenceTime | The IE GNSS-ReferenceTime is used by the location server to provide the GNSS specific system time with uncertainty and the relationship between GNSS system time and network air-interface timing of the DTR (or other Radio Access Point) and/or Satellite (in case of direct satellite link to the Target Device) transmission... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.2 GNSS-SystemTime | -- ASN1START GNSS-SystemTime ::= SEQUENCE { gnss-TimeID GNSS-ID, gnss-DayNumber INTEGER (0..32767), gnss-TimeOfDay INTEGER (0..86399), gnss-TimeOfDayFrac-msec INTEGER (0..999) OPTIONAL, -- Need ON notificationOfLeapSecond BIT STRING (SIZE(2)) OPTIONAL, -- Cond gnss-TimeID-glonass gps-TOW-Assist GPS-TOW-Assist OPTIONAL,... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.3 GPS-TOW-Assist | -- ASN1START GPS-TOW-Assist ::= SEQUENCE (SIZE(1..64)) OF GPS-TOW-AssistElement GPS-TOW-AssistElement ::= SEQUENCE { satelliteID INTEGER (1..64), tlmWord INTEGER (0..16383), antiSpoof INTEGER (0..1), alert INTEGER (0..1), tlmRsvdBits INTEGER (0..3), ... } -- ASN1STOP GPS-TOW-Assist field descriptions satelliteID This f... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.4 NetworkTime | The Network Time, and how it is provide, is typically dependent on the used Radio Network: it gives examples of SH/NGH/T2, but can cover DVB-S2 as well, and other Radio Networks. The IE described here will be different from the LPP, concerning the terms described, but it is the same kind of data. -- ASN1START NetworkTi... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.5 GNSS-ReferenceLocation | The IE GNSS-ReferenceLocation is used by the location server to provide the target device with a-priori knowledge of its location in order to improve GNSS receiver performance. The IE GNSS-ReferenceLocation is provided in WGS-84 reference system. -- ASN1START GNSS-ReferenceLocation ::= SEQUENCE { threeDlocation Ellipso... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.6 GNSS-IonosphericModel | The IE GNSS-IonosphericModel is used by the location server to provide parameters to model the propagation delay of the GNSS signals through the ionosphere. Proper use of these fields allows a single-frequency GNSS receiver to remove parts of the ionospheric delay from the pseudorange measurements. Two Ionospheric Mode... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.7 KlobucharModelParameter | -- ASN1START KlobucharModelParameter ::= SEQUENCE { dataID BIT STRING (SIZE (2)), alfa0 INTEGER (-128..127), alfa1 INTEGER (-128..127), alfa2 INTEGER (-128..127), alfa3 INTEGER (-128..127), beta0 INTEGER (-128..127), beta1 INTEGER (-128..127), beta2 INTEGER (-128..127), beta3 INTEGER (-128..127), ... } -- ASN1STOP Klob... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.8 NeQuickModelParameter | -- ASN1START NeQuickModelParameter ::= SEQUENCE { ai0 INTEGER (0..4095), ai1 INTEGER (0..4095), ai2 INTEGER (0..4095), ionoStormFlag1 INTEGER (0..1) OPTIONAL, -- Need OP ionoStormFlag2 INTEGER (0..1) OPTIONAL, -- Need OP ionoStormFlag3 INTEGER (0..1) OPTIONAL, -- Need OP ionoStormFlag4 INTEGER (0..1) OPTIONAL, -- Need ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.9 GNSS-EarthOrientationParameters | The IE GNSS-EarthOrientationParameters is used by the location server to provide parameters to construct the ECEF and ECI coordinate transformation as defined in [2]. The IE GNSS-EarthOrientationParameters indicates the relationship between the Earth's rotational axis and WGS-84 reference system. -- ASN1START GNSS-Eart... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.10 GNSS-TimeModelList | The IE GNSS-TimeModelList is used by the location server to provide the GNSS-GNSS system time offset between the GNSS system time indicated by IE GNSS-ID in IE GNSS-GenericAssistDataElement to the GNSS system time indicated by IE gnss-TO-ID. Several GNSS-TimeModelElement IEs can be included with different gnss-TO-ID fi... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.11 GNSS-DifferentialCorrections | The IE GNSS-DifferentialCorrections is used by the location server to provide differential GNSS corrections to the target device for a specific GNSS. Differential corrections can be provided for up to 3 signals per GNSS. -- ASN1START GNSS-DifferentialCorrections ::= SEQUENCE { dgnss-RefTime INTEGER (0..3599), dgnss-Sgn... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.12 GNSS-NavigationModel | The IE GNSS-NavigationModel is used by the location server to provide precise navigation data to the GNSS capable target device. In response to a request from a target device for GNSS Assistance Data, the location server shall determine whether to send the navigation model for a particular satellite to a target device ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.13 StandardClockModelList | -- ASN1START StandardClockModelList ::= SEQUENCE (SIZE(1..2)) OF StandardClockModelElement StandardClockModelElement ::= SEQUENCE { stanClockToc INTEGER (0..16383), stanClockAF2 INTEGER (-2048..2047), stanClockAF1 INTEGER (-131072..131071), stanClockAF0 INTEGER (-134217728..134217727), stanClockTgd INTEGER (-512..511) ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.14 NAV-ClockModel | -- ASN1START NAV-ClockModel ::= SEQUENCE { navToc INTEGER (0..37799), navaf2 INTEGER (-128..127), navaf1 INTEGER (-32768..32767), navaf0 INTEGER (-2097152..2097151), navTgd INTEGER (-128..127), ... } -- ASN1STOP NAV-ClockModel field descriptions navToc Parameter toc, time of clock (seconds) [2] and [5] Scale factor 24 ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.15 CNAV-ClockModel | -- ASN1START CNAV-ClockModel ::= SEQUENCE { cnavToc INTEGER (0..2015), cnavTop INTEGER (0..2015), cnavURA0 INTEGER (-16..15), cnavURA1 INTEGER (0..7), cnavURA2 INTEGER (0..7), cnavAf2 INTEGER (-512..511), cnavAf1 INTEGER (-524288..524287), cnavAf0 INTEGER (-33554432..33554431), cnavTgd INTEGER (-4096..4095), cnavISCl1c... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.16 GLONASS-ClockModel | -- ASN1START GLONASS-ClockModel ::= SEQUENCE { gloTau INTEGER (-2097152..2097151), gloGamma INTEGER (-1024..1023), gloDeltaTau INTEGER (-16..15) OPTIONAL, -- Need ON ... } -- ASN1STOP GLONASS-ClockModel field descriptions gloTau Parameter τn(tb), satellite clock offset (seconds) [7]. Scale factor 2-30 seconds. gloGamma... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.17 SBAS-ClockModel | -- ASN1START SBAS-ClockModel ::= SEQUENCE { sbasTo INTEGER (0..5399), sbasAgfo INTEGER (-2048..2047), sbasAgf1 INTEGER (-128..127), ... } -- ASN1STOP SBAS-ClockModel field descriptions sbasTo Parameter t0 [8]. Scale factor 16 seconds. sbasAgfo Parameter aGfo [8]. Scale factor 2-31 seconds. sbasAgf1 Parameter aGf1 [8]. ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.18 NavModelKeplerianSet | -- ASN1START NavModelKeplerianSet ::= SEQUENCE { keplerToe INTEGER (0 .. 16383), keplerW INTEGER (-2147483648..2147483647), keplerDeltaN INTEGER (-32768..32767), keplerM0 INTEGER (-2147483648..2147483647), keplerOmegaDot INTEGER (-8388608.. 8388607), keplerE INTEGER (0..4294967295), keplerIDot INTEGER (-8192..8191), ke... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.19 NavModelNAV-KeplerianSet | -- ASN1START NavModelNAV-KeplerianSet ::= SEQUENCE { navURA INTEGER (0..15), navFitFlag INTEGER (0..1), navToe INTEGER (0..37799), navOmega INTEGER (-2147483648..2147483647), navDeltaN INTEGER (-32768..32767), navM0 INTEGER (-2147483648..2147483647), navOmegaADot INTEGER (-8388608..8388607), navE INTEGER (0..4294967295... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.20 NavModelCNAV-KeplerianSet | -- ASN1START NavModelCNAV-KeplerianSet ::= SEQUENCE { cnavTop INTEGER (0..2015), cnavURAindex INTEGER (-16..15), cnavDeltaA INTEGER (-33554432..33554431), cnavAdot INTEGER (-16777216..16777215), cnavDeltaNo INTEGER (-65536..65535), cnavDeltaNoDot INTEGER (-4194304..4194303), cnavMo INTEGER (-4294967296..4294967295), cn... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.21 NavModel-GLONASS-ECEF | -- ASN1START NavModel-GLONASS-ECEF ::= SEQUENCE { gloEn INTEGER (0..31), gloP1 BIT STRING (SIZE(2)), gloP2 BOOLEAN, gloM INTEGER (0..3), gloX INTEGER (-67108864..67108863), gloXdot INTEGER (-8388608..8388607), gloXdotdot INTEGER (-16..15), gloY INTEGER (-67108864..67108863), gloYdot INTEGER (-8388608..8388607), gloYdot... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.22 NavModel-SBAS-ECEF | -- ASN1START NavModel-SBAS-ECEF ::= SEQUENCE { sbasTo INTEGER (0..5399) OPTIONAL, -- Cond ClockModel sbasAccuracy BIT STRING (SIZE(4)), sbasXg INTEGER (-536870912..536870911), sbasYg INTEGER (-536870912..536870911), sbasZg INTEGER (-16777216..16777215), sbasXgDot INTEGER (-65536..65535), sbasYgDot INTEGER (-65536..6553... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.23 GNSS-RealTimeIntegrity | The IE GNSS-RealTimeIntegrity is used by the location server to provide parameters that describe the real-time status of the GNSS constellations. GNSS-RealTimeIntegrity data communicates the health of the GNSS signals to the mobile in real-time. The location server shall always transmit the GNSS-RealTimeIntegrity with ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.24 GNSS-DataBitAssistance | The IE GNSS-DataBitAssistance is used by the location server to provide data bit assistance data for specific satellite signals for data wipe-off. The data bits included in the assistance data depends on the GNSS and its signal. -- ASN1START GNSS-DataBitAssistance ::= SEQUENCE { gnss-TOD INTEGER (0..3599), gnss-TODfrac... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.25 GNSS-AcquisitionAssistance | The IE GNSS-AcquisitionAssistance is used by the location server to provide parameters that enable fast acquisition of the GNSS signals. Essentially, these parameters describe the range and derivatives from respective satellites to the reference location at the reference time GNSS-SystemTime provided in IE GNSS-Referen... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.26 GNSS-Almanac | The IE GNSS-Almanac is used by the location server to provide the coarse, long-term model of the satellite positions and clocks. The meaning of these parameters is defined in relevant ICDs of the particular GNSS and GNSS specific interpretations apply. For example, GPS and QZSS use the same model parameters but some pa... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.27 AlmanacKeplerianSet | -- ASN1START AlmanacKeplerianSet ::= SEQUENCE { svID SV-ID, kepAlmanacE INTEGER (0..2047), kepAlmanacDeltaI INTEGER (-1024..1023), kepAlmanacOmegaDot INTEGER (-1024..1023), kepSVHealth INTEGER (0..15), kepAlmanacAPowerHalf INTEGER (-65536..65535), kepAlmanacOmega0 INTEGER (-32768..32767), kepAlmanacW INTEGER (-32768..3... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.28 AlmanacNAV-KeplerianSet | -- ASN1START AlmanacNAV-KeplerianSet ::= SEQUENCE { svID SV-ID, navAlmE INTEGER (0..65535), navAlmDeltaI INTEGER (-32768..32767), navAlmOMEGADOT INTEGER (-32768..32767), navAlmSVHealth INTEGER (0..255), navAlmSqrtA INTEGER (0..16777215), navAlmOMEGAo INTEGER (-8388608..8388607), navAlmOmega INTEGER (-8388608..8388607),... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.29 AlmanacReducedKeplerianSet | -- ASN1START AlmanacReducedKeplerianSet ::= SEQUENCE { svID SV-ID, redAlmDeltaA INTEGER (-128..127), redAlmOmega0 INTEGER (-64..63), redAlmPhi0 INTEGER (-64..63), redAlmL1Health BOOLEAN, redAlmL2Health BOOLEAN, redAlmL5Health BOOLEAN, ... } -- ASN1STOP AlmanacReducedKeplerianSet field descriptions svID This field ident... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.30 AlmanacMidiAlmanacSet | -- ASN1START AlmanacMidiAlmanacSet ::= SEQUENCE { svID SV-ID, midiAlmE INTEGER (0..2047), midiAlmDeltaI INTEGER (-1024..1023), midiAlmOmegaDot INTEGER (-1024..1023), midiAlmSqrtA INTEGER (0..131071), midiAlmOmega0 INTEGER (-32768..32767), midiAlmOmega INTEGER (-32768..32767), midiAlmMo INTEGER (-32768..32767), midiAlma... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.31 AlmanacGLONASS-AlmanacSet | -- ASN1START AlmanacGLONASS-AlmanacSet ::= SEQUENCE { gloAlm-NA INTEGER (1..1461), gloAlmnA INTEGER (1..24), gloAlmHA INTEGER (0..31), gloAlmLambdaA INTEGER (-1048576..1048575), gloAlmtlambdaA INTEGER (0..2097151), gloAlmDeltaIa INTEGER (-131072..131071), gloAlmDeltaTA INTEGER (-2097152..2097151), gloAlmDeltaTdotA INTE... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.32 AlmanacECEF-SBAS-AlmanacSet | -- ASN1START AlmanacECEF-SBAS-AlmanacSet ::= SEQUENCE { sbasAlmDataID INTEGER (0..3), svID SV-ID, sbasAlmHealth BIT STRING (SIZE(8)), sbasAlmXg INTEGER (-16384..16383), sbasAlmYg INTEGER (-16384..16383), sbasAlmZg INTEGER (-256..255), sbasAlmXgdot INTEGER (-4..3), sbasAlmYgDot INTEGER (-4..3), sbasAlmZgDot INTEGER (-8.... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.33 GNSS-UTC-Model | The IE GNSS-UTC-Model is used by the location server to provide several sets of parameters needed to relate GNSS system time to Universal Time Coordinate (UTC), as defined in [4], [5], [6], [7], [8] and [9]. The UTC time standard, UTC(k), is GNSS specific. E.g. if GNSS-ID indicates GPS, GNSS-UTC-Model contains a set of... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.34 UTC-ModelSet1 | -- ASN1START UTC-ModelSet1 ::= SEQUENCE { gnss-Utc-A1 INTEGER (-8388608..8388607), gnss-Utc-A0 INTEGER (-2147483648..2147483647), gnss-Utc-Tot INTEGER (0..255), gnss-Utc-WNt INTEGER (0..255), gnss-Utc-DeltaTls INTEGER (-128..127), gnss-Utc-WNlsf INTEGER (0..255), gnss-Utc-DN INTEGER (-128..127), gnss-Utc-DeltaTlsf INTE... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.35 UTC-ModelSet2 | -- ASN1START UTC-ModelSet2 ::= SEQUENCE { utcA0 INTEGER (-32768..32767), utcA1 INTEGER (-4096..4095), utcA2 INTEGER (-64..63), utcDeltaTls INTEGER (-128..127), utcTot INTEGER (0..65535), utcWNot INTEGER (0..8191), utcWNlsf INTEGER (0..255), utcDN BIT STRING (SIZE(4)), utcDeltaTlsf INTEGER (-128..127), ... } -- ASN1STOP... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.36 UTC-ModelSet3 | -- ASN1START UTC-ModelSet3 ::= SEQUENCE { nA INTEGER (1..1461), tauC INTEGER (-2147483648..2147483647), b1 INTEGER (-1024..1023) OPTIONAL, -- Cond GLONASS-M b2 INTEGER (-512..511) OPTIONAL, -- Cond GLONASS-M kp BIT STRING (SIZE(2)) OPTIONAL, -- Cond GLONASS-M ... } -- ASN1STOP Conditional presence Explanation GLONASS-M... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.37 UTC-ModelSet4 | -- ASN1START UTC-ModelSet4 ::= SEQUENCE { utcA1wnt INTEGER (-8388608..8388607), utcA0wnt INTEGER (-2147483648..2147483647), utcTot INTEGER (0..255), utcWNt INTEGER (0..255), utcDeltaTls INTEGER (-128..127), utcWNlsf INTEGER (0..255), utcDN INTEGER (-128..127), utcDeltaTlsf INTEGER (-128..127), utcStandardID INTEGER (0.... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.2.38 GNSS-AuxiliaryInformation | The IE GNSS-AuxiliaryInformation is used by the location server to provide additional information dependent on the GNSS-ID. If GNSS-AuxiliaryInformation is provided together with other satellite dependent GNSS assistance data (i.e. any of GNSS-DifferentialCorrections, GNSS-NavigationModel, GNSS-DataBitAssistance, or GN... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3 Common GNSS Information Elements | |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.1 GNSS-ID | The IE GNSS-ID is used to indicate a specific GNSS. -- ASN1START GNSS-ID ::= SEQUENCE { gnss-id ENUMERATED{ gps, sbas, qzss, galileo, glonass, ...}, ... } -- ASN1STOP |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.2 GNSS-ID-Bitmap | The IE GNSS-ID-Bitmap is used to indicate several GNSSs using a bit map. -- ASN1START GNSS-ID-Bitmap ::= SEQUENCE { gnss-ids BIT STRING { gps (0), sbas (1), qzss (2), galileo (3), glonass (4) } (SIZE (1..16)), ... } -- ASN1STOP GNSS-ID-Bitmap field descriptions gnss-ids This field specifies the GNSS(s). This is represe... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.3 GNSS-SignalID | The IE GNSS-SignalID is used to indicate a specific GNSS signal type. The interpretation of GNSS-SignalID depends on the GNSS-ID. -- ASN1START GNSS-SignalID ::= SEQUENCE { gnss-SignalID INTEGER (0 .. 7), ... } -- ASN1STOP GNSS-SignalID field descriptions gnss-SignalID This field specifies a particular GNSS signal. The ... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.5 GNSS-SignalIDs | The IE GNSSSignal-IDs is used to indicate several GNSS signals using a bit map. The interpretation of GNSSSignal-IDs depends on the GNSS-ID. -- ASN1START GNSS-SignalIDs ::= SEQUENCE { gnss-SignalIDs BIT STRING (SIZE(8)), ... } -- ASN1STOP GNSS-SignalIDs field descriptions gnss-SignalIDs This field specifies one or seve... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.6 SBAS-ID | The IE SBAS-ID is used to indicate a specific SBAS. -- ASN1START SBAS-ID ::= SEQUENCE { sbas-id ENUMERATED { waas, egnos, msas, gagan, ...}, ... } -- ASN1STOP |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.7 SBAS-IDs | The IE SBAS-IDs is used to indicate several SBASs using a bit map. -- ASN1START SBAS-IDs ::= SEQUENCE { sbas-IDs BIT STRING { waas (0), egnos (1), msas (2), gagan (3) } (SIZE (1..8)), ... } -- ASN1STOP SBAS-IDs field descriptions sbas-IDs This field specifies one or several SBAS(s) using a bit map. A one-value at the b... |
94690fa0e4324b6d28f566c1003d783c | 103 252 | 7.4.3.8 SV-ID | The IE SV-ID is used to indicate a specific GNSS satellite. The interpretation of SV-ID depends on the GNSS-ID. -- ASN1START SV-ID ::= SEQUENCE { satellite-id INTEGER(0..63), ... } -- ASN1STOP SV-ID field descriptions satellite-id This field specifies a particular satellite within a specific GNSS. The interpretation of... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 1 Scope | The present document: • identifies and defines possible key performance indicators for voice and fax telephony services; • defines benchmarking methods for the spectrum of potential applications. The offer of new NGN services requires new KPIs, QoS measurement and benchmarking methods which are needed to ensure the qua... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 2 References | |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-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... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-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... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 3 Definition of terms, symbols and abbreviations | |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 3.1 Terms | For the purposes of the present document, the terms given in Recommendation ITU-T E.800 [1] and the following apply: benchmark: evaluation of performance value/s of a parameter or set of parameters for the purpose of establishing value/s as the norm against which future performance achievements may be compared or asses... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 3.2 Symbols | Void. ETSI ETSI TS 103 222-1 V1.4.1 (2025-02) 9 |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AB Direction of call establishment User A to User B ACK ACKnowledgement AGCF Access Gateway Control Function AGW Access GateWay AIMD Additive Increase, Multiplicative Decrease ANS ANSwer tone AS Application Server BA Direction of call establis... |
64b6ac29f6e9a63fe61773c7176d7e07 | 103 222-1 | 4 Management Summary |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.