7 Broadcast of assistance data
37.3553GPPLTE Positioning Protocol (LPP)Release 17TS
7.1 General
Broadcast of positioning assistance data is supported via Positioning System Information Blocks (posSIBs) as specified in TS 36.331 [12] or TS 38.331 [35]. The posSIBs are carried in RRC System Information (SI) messages (TS 36.331 [12] or TS 38.331 [35]).
For LTE RRC System Information (SI), a single SystemInformationBlockPos IE is defined in TS 36.331 [12] which is carried in IE PosSystemInformation-r15-IEs specified in TS 36.331 [12]. The mapping of positioning SIB type (posSibType) to assistance data carried in SystemInformationBlockPos is specified in clause 7.2.
For NR RRC System Information (SI), a single SIBpos IE is defined in TS 38.331 [35] which is carried in IE PosSystemInformation-r16-IEs specified in TS 38.331 [35]. The mapping of positioning SIB type (posSibType) to assistance data carried in SIBpos is specified in clause 7.2.
7.2 Mapping of posSibType to assistance data element
The supported posSibType‘s are specified in Table 7.2-1. The GNSS Common and Generic Assistance Data IEs are defined in clause 6.5.2.2. The OTDOA Assistance Data IEs and NR DL-TDOA/DL-AoD Assistance Data IEs are defined in clause 7.4.2. The Barometric Assistance Data IEs are defined in clause 6.5.5.8. The TBS (based on MBS signals) Assistance Data IEs are defined in clause 6.5.4.8.
Table 7.2-1: Mapping of posSibType to assistanceDataElement
|
posSibType |
assistanceDataElement |
|
|
GNSS Common Assistance Data (clause 6.5.2.2) |
posSibType1-1 |
GNSS-ReferenceTime |
|
posSibType1-2 |
GNSS-ReferenceLocation |
|
|
posSibType1-3 |
GNSS-IonosphericModel |
|
|
posSibType1-4 |
GNSS-EarthOrientationParameters |
|
|
posSibType1-5 |
GNSS-RTK-ReferenceStationInfo |
|
|
posSibType1-6 |
GNSS-RTK-CommonObservationInfo |
|
|
posSibType1-7 |
GNSS-RTK-AuxiliaryStationData |
|
|
posSibType1-8 |
GNSS-SSR-CorrectionPoints |
|
|
posSibType1-9 |
GNSS-Integrity-ServiceParameters |
|
|
posSibType1-10 |
GNSS-Integrity-ServiceAlert |
|
|
GNSS Generic Assistance Data (clause 6.5.2.2) |
posSibType2-1 |
GNSS-TimeModelList |
|
posSibType2-2 |
GNSS-DifferentialCorrections |
|
|
posSibType2-3 |
GNSS-NavigationModel |
|
|
posSibType2-4 |
GNSS-RealTimeIntegrity |
|
|
posSibType2-5 |
GNSS-DataBitAssistance |
|
|
posSibType2-6 |
GNSS-AcquisitionAssistance |
|
|
posSibType2-7 |
GNSS-Almanac |
|
|
posSibType2-8 |
GNSS-UTC-Model |
|
|
posSibType2-9 |
GNSS-AuxiliaryInformation |
|
|
posSibType2-10 |
BDS-DifferentialCorrections |
|
|
posSibType2-11 |
BDS-GridModelParameter |
|
|
posSibType2-12 |
GNSS-RTK-Observations |
|
|
posSibType2-13 |
GLO-RTK-BiasInformation |
|
|
posSibType2-14 |
GNSS-RTK-MAC-CorrectionDifferences |
|
|
posSibType2-15 |
GNSS-RTK-Residuals |
|
|
posSibType2-16 |
GNSS-RTK-FKP-Gradients |
|
|
posSibType2-17 |
GNSS-SSR-OrbitCorrections |
|
|
posSibType2-18 |
GNSS-SSR-ClockCorrections |
|
|
posSibType2-19 |
GNSS-SSR-CodeBias |
|
|
posSibType2-20 |
GNSS-SSR-URA |
|
|
posSibType2-21 |
GNSS-SSR-PhaseBias |
|
|
posSibType2-22 |
GNSS-SSR-STEC-Correction |
|
|
posSibType2-23 |
GNSS-SSR-GriddedCorrection |
|
|
posSibType2-24 |
NavIC-DifferentialCorrections |
|
|
posSibType2-25 |
NavIC-GridModelParameter |
|
|
OTDOA Assistance Data (clause 7.4.2) |
posSibType3-1 |
OTDOA-UE-Assisted |
|
Barometric Assistance Data (clause 6.5.5.8) |
posSibType4-1 |
Sensor-AssistanceDataList |
|
TBS Assistance Data (clause 6.5.4.8) |
posSibType5-1 |
TBS-AssistanceDataList |
|
NR DL-TDOA/DL-AoD Assistance Data (clauses 6.4.3, 7.4.2) |
posSibType6-1 |
NR-DL-PRS-AssistanceData |
|
posSibType6-2 |
NR-UEB-TRP-LocationData |
|
|
posSibType6-3 |
NR-UEB-TRP-RTD-Info |
|
|
posSibType6-4 |
NR-TRP-BeamAntennaInfo |
|
|
posSibType6-5 |
NR-DL-PRS-TRP-TEG-Info |
|
|
On-demand DL-PRS Configurations (clause 6.4.3) |
posSibType6-6 |
NR-On-Demand-DL-PRS-Configurations |
7.3 Procedures related to broadcast information elements
Upon receiving AssistanceDataSIBelement, the target device shall:
1> if the segmentationInfo is not included:
2> if the cipheringKeyData is included:
3> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted C0 corresponding to the cipherSetID using NAS signalling:
4> if C0 contains less than 128-bits:
5> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits.
4> if the d0 field contains less than 128-bits:
5> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted D0.
4> determine the initial Counter C1 = (C0 + D0) mod 2128 (where all values are treated as non-negative integers);
4> determine any subsequent counter Ci from the previous counter Ci-1 as Ci = (Ci-1 + 1) mod 2128;
4> use the sequence of counters <C1, C2, C3, …> and the cipher key value to decipher the assistanceDataElement;
4> decode the deciphered assistanceDataElement and deliver the related assistance data to upper layers.
3> else:
4> discard the AssistanceDataSIBelement.
2> else:
3> decode the assistanceDataElement and deliver the related assistance data to upper layers.
1> else:
2> if segmentationOption indicates ‘pseudo-seg‘:
3> if the cipheringKeyData is included:
4> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted C0 corresponding to the cipherSetID using NAS signalling:
5> if C0 contains less than 128-bits:
6> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits.
5> if the d0 field contains less than 128-bits:
6> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted D0.
5> determine the initial Counter C1 = (C0 + D0) mod 2128 (where all values are treated as non-negative integers);
5> determine any subsequent counter Ci from the previous counter Ci-1 as Ci = (Ci-1 + 1) mod 2128;
5> use the sequence of counters <C1, C2, C3, …> and the cipher key value to decipher the assistanceDataElement segment;
5> decode the deciphered assistanceDataElement segment and deliver the related assistance data portion together with the assistanceDataSegmentType and assistanceDataSegmentNumber to upper layers.
4> else:
5> discard the AssistanceDataSIBelement segment.
3> else:
4> decode the assistanceDataElement segment and deliver the related assistance data portion together with the assistanceDataSegmentType and assistanceDataSegmentNumber to upper layers.
2> if segmentationOption indicates ‘octet-string-seg‘:
3> if all segments of assistanceDataElement have been received:
4> assemble the assistance data element from the received assistanceDataElement segments;
5> if the cipheringKeyData is included in the first segment:
6> if the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted C0 corresponding to the cipherSetID using NAS signalling:
7> if C0 contains less than 128-bits:
8> pad out the bit string with zeroes in most significant bit positions to achieve 128 bits.
7> if the d0 field contains less than 128-bits:
8> pad out the bit string with zeroes in least significant bit positions to achieve 128 bits, denoted D0.
7> determine the initial Counter C1 = (C0 + D0) mod 2128 (where all values are treated as non-negative integers);
7> determine any subsequent counter Ci from the previous counter Ci-1 as Ci = (Ci-1 + 1) mod 2128;
7> use the sequence of counters <C1, C2, C3, …> and the cipher key value to decipher the assembled assistance data element;
7> decode the assembled and deciphered assistance data element and deliver the related assistance data to upper layers.
6> else:
7> discard the assembled assistance data element.
5> else:
6> decode the assembled assistance data element and deliver the related assistance data to upper layers.
NOTE: As an optional optimisation when segmentationOption indicates ‘octet-string-seg‘, a target device may verify if the cipheringKeyData is included in the first segment as soon as the first segment is received and, if included, may verify that the UE has obtained a valid cipher key value and the first portion of the initial Counter denoted C0 corresponding to the cipherSetID using NAS signalling. When the UE has not obtained a valid cipher key value and initial Counter C0 using NAS signalling, the UE may discard the first segment and ignore all subsequent segments.
The value for D0 shall be different for different AssistanceDataSIBelement‘s to ensure that the counters derived from C1 for any assistanceDataElement are different to the counters for any other assistanceDataElement for a given ciphering key.
D0 shall contain at least 16 least significant bits (LSBs) set to zero to ensure that the values of D0 differ from another by a large value.
7.4 Broadcast information elements
7.4.1 Basic production
This clause defines the LPP broadcast information elements which are encoded as ‘basic production’ for system information broadcast purposes (see TS 36.331 [12], TS 38.331 [35]).
The ‘basic production’ is obtained from their ASN.1 definitions by use of Basic Packed Encoding Rules (BASIC-PER), Unaligned Variant, as specified in ITU-T Rec. X.691 [22]. It always contains a multiple of 8 bits.
– LPP-Broadcast-Definitions
This ASN.1 segment is the start of the LPP Broadcast definitions.
— ASN1START
LPP-Broadcast-Definitions
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
IMPORTS
OTDOA-ReferenceCellInfo,
OTDOA-NeighbourCellInfoList,
NR-TRP-LocationInfo-r16,
NR-DL-PRS-BeamInfo-r16,
NR-RTD-Info-r16
FROM LPP-PDU-Definitions;
— ASN1STOP
7.4.2 Element definitions
– AssistanceDataSIBelement
The IE AssistanceDataSIBelement is used in the IE SystemInformationBlockPos as specified in TS 36.331 [12] and IE SIBpos as specified in TS 38.331 [35].
— ASN1START
AssistanceDataSIBelement-r15 ::= SEQUENCE {
valueTag-r15 INTEGER (0..63) OPTIONAL, — Need OP
expirationTime-r15 UTCTime OPTIONAL, — Need OP
cipheringKeyData-r15 CipheringKeyData-r15 OPTIONAL, — Need OP
segmentationInfo-r15 SegmentationInfo-r15 OPTIONAL, — Need OP
assistanceDataElement-r15 OCTET STRING,
…
}
CipheringKeyData-r15 ::= SEQUENCE {
cipherSetID-r15 INTEGER (0..65535),
d0-r15 BIT STRING (SIZE (1..128)),
…
}
SegmentationInfo-r15 ::= SEQUENCE {
segmentationOption-r15 ENUMERATED {pseudo-seg, octet-string-seg},
assistanceDataSegmentType-r15 ENUMERATED {notLastSegment, lastSegment},
assistanceDataSegmentNumber-r15 INTEGER (0..63),
…
}
— ASN1STOP
|
AssistanceDataSIBelement field descriptions |
|---|
|
valueTag This field is used to indicate to the target device any changes in the broadcast assistance data content. The valueTag is incremented by one, by the location server, every time a modified assistance data content is provided. This field is not included if the broadcast assistance data changes too frequently. If valueTag and expirationTime are absent, the UE assumes that the broadcast assistance data content changes at every broadcast interval. |
|
expirationTime This field indicates how long the broadcast assistance data content is valid. It is specified as UTC time and indicates when the broadcast assistance data content will expire. |
|
cipheringKeyData If present, indicates that the assistanceDataElement octet string is ciphered. |
|
segmentationInfo If present, indicates that the assistanceDataElement is one of many segments. |
|
assistanceDataElement The assistanceDataElement OCTET STRING depends on the posSibType and is specified in Table 7.2-1. NOTE. |
|
cipherSetID This field identifies a cipher set comprising a cipher key value and the first component C0 of the initial counter C1. |
|
d0 This field provides the second component for the initial ciphering counter C1. This field is defined as a bit string with a length of 1 to 128 bits. A target device first pads out the bit string if less than 128 bits with zeroes in least significant bit positions to achieve 128 bits. C1 is then obtained from D0 and C0 (defined by the cipherSetID) as: C1 = (D0 + C0) mod 2128 (with all values treated as non-negative integers). |
|
segmentationOption Indicates the used segmentation option. |
|
assistanceDataSegmentType Indicates whether the included assistanceDataElement segment is the last segment or not. |
|
assistanceDataSegmentNumber Segment number of the assistanceDataElement segment. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on. Segments numbers wraparound should there be more than 64 segments |
NOTE: For example, if the posSibType in IE PosSIB-Type defined in TS 36.331 [12] and TS 38.331 [35] indicates ‘posSibType1-7‘, the assistanceDataElement OCTET STRING includes the LPP IE GNSS‑RTK‑AuxiliaryStationData.
– OTDOA-UE-Assisted
The IE OTDOA-UE-Assisted is used in the assistanceDataElement if the posSibType in IE PosSIB-Type defined in TS 36.331 [12] indicates ‘posSibType3-1‘.
— ASN1START
OTDOA-UE-Assisted-r15 ::= SEQUENCE {
otdoa-ReferenceCellInfo-r15 OTDOA-ReferenceCellInfo,
otdoa-NeighbourCellInfo-r15 OTDOA-NeighbourCellInfoList,
…
}
— ASN1STOP
|
OTDOA-UE-Assisted field descriptions |
|---|
|
otdoa-ReferenceCellInfo LPP IE OTDOA-ReferenceCellInfo as defined in clause 6.5.1.2. |
|
otdoa-NeighbourCellInfo LPP IE OTDOA-NeighbourCellInfoList as defined in clause 6.5.1.2. |
– NR-UEB-TRP-LocationData
The IE NR-UEB-TRP-LocationData is used in the assistanceDataElement if the posSibType in IE PosSIB-Type defined in TS 38.331 [35] indicates ‘posSibType6-2‘.
— ASN1START
NR-UEB-TRP-LocationData-r16 ::= SEQUENCE {
nr-trp-LocationInfo-r16 NR-TRP-LocationInfo-r16,
nr-dl-prs-BeamInfo-r16 NR-DL-PRS-BeamInfo-r16 OPTIONAL, — Need ON
…
}
— ASN1STOP
|
NR-UEB-TRP-LocationData field descriptions |
|---|
|
nr-trp-LocationInfo LPP IE NR-TRP-LocationInfo as defined in clause 6.4.2.1. |
|
nr-dl-prs-BeamInfo LPP IE NR-DL-PRS-Beam-Info as defined in clause 6.4.2.1. |
– NR-UEB-TRP-RTD-Info
The IE NR-UEB-TRP-RTD-Info is used in the assistanceDataElement if the posSibType in IE PosSIB-Type defined in TS 38.331 [35] indicates ‘posSibType6-3‘.
— ASN1START
NR-UEB-TRP-RTD-Info-r16 ::= SEQUENCE {
nr-rtd-Info-r16 NR-RTD-Info-r16,
…
}
— ASN1STOP
|
NR-UEB-TRP-RTD-Info field descriptions |
|---|
|
nr-rtd-Info LPP IE NR-RTD-Info as defined in clause 6.4.2.1. |
– End of LPP-Broadcast-Definitions
— ASN1START
END
— ASN1STOP
7.5 Broadcast ciphering (informative)
The assistanceDataElement OCTET STRING included in IE AssistanceDataSIBelement may be ciphered using the 128-bit Advanced Encryption Standard (AES) algorithm (with counter mode).
AES as specified in [32] and [33] is a block mode cipher algorithm that ciphers blocks of 128 bits at a time. However, Counter mode enables usage for a bit string that is not an exact multiple of 128 bits. Further, Counter mode enables a target (or a server) to perform most of the deciphering (or ciphering) processing independently of receipt of the data to be deciphered (or ciphered) which may enable more efficient processing. Provided counters are chosen in a non‑repeating manner by the server (which is a requirement for Counter mode), every block of data will be ciphered in a unique manner.
The algorithm makes use of a sequence of counters <C1, C2, C3, …> each containing 128 bits, where C1 is specified by the server and each subsequent counter (C2, C3 etc.) is obtained from the previous counter by adding one modulo 2128. Each counter Ci is ciphered using the AES algorithm with a common 128-bit key to produce an output block Oi of 128 bits. To perform ciphering, the assistanceDataElement is divided into blocks B1, B2, … Bn of 128 bits each, except for the last block Bn which may contain fewer than 128 bits. The ciphered assistanceDataElement is obtained as a sequence of n blocks containing 128 bits each (except possibly for the last block) given by (O1 XOR B1), (O2 XOR B2), … (On XOR Bn), where XOR denotes bitwise exclusive OR. In the case of the last block, if Bn contains m bits (m<128), then the m most significant bits of On would be used for the exclusive OR. Deciphering is performed in the same way except that the blocks B1, B2, … Bn are now obtained from the ciphered message and the result of the exclusive OR operations yields the original unciphered message. Figure 7.5-1 provides an illustration of Counter mode for the generic case of an arbitrary block cipher algorithm CIPHk.
Figure 7.5-1: Illustration of Block Ciphering with Counter Mode [33].
The algorithms require specific conventions for bit ordering. The bit ordering applicable to ciphering for a ASN.1 PER encoded assistanceDataElement is the bit ordering produced by the ASN.1 PER encoding where the first bit is the leading bit number zero, the second bit is bit one etc..
The initial counter C1 used to cipher an entire assistanceDataElement is provided to a target by a server in two portions. The first portion, denoted C0, is provided using point to point mode along with the 128-bit ciphering key and an identifier for both of these values as specified in TS 23.271 [3]. The second portion, denoted D0 (d0), is provided in unciphered form in IE CipheringKeyData. A target then obtains C1 as:
C1 = (C0 + D0) mod 2128 (where all values are treated as non-negative integers)
To obtain any subsequent counter Ci from the previous counter Ci1 for any message, the following operation is used:
Ci = (Ci1 + 1) mod 2128
NOTE: As specified in clause 7.3 the value for D0 is different for different AssistanceDataSIBelement‘s to ensure that the counters derived from C1 for any assistanceDataElement can be different to the counters for any other assistanceDataElement. However, a long assistanceDataElement or a segmented assistanceDataElement would require the use of consecutive counter values C1 to Cn, where n is the assistanceDataElement size in bits divided by 128 (and rounded up). There would then be a danger of small changes in the value of D0 for ciphering of different assistanceDataElement‘s (e.g. D0 being chosen as 1 larger than a previous D0 value) reusing previous counter values. To avoid this, the values of D0 contain 16 least significant bits (LSBs) set to zero, as specified in clause 7.3.
Annex A (informative):
Change History
|
Change history of TS 36.355 up to v15.5.0 |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2009-10 |
RAN2 #67bis |
R2-096252 |
RAN2 agreed TS 36.355 v0.1.0 |
0.1.0 |
|||
|
2009-11 |
RAN2 #68 |
R2-097492 |
RAN2 agreed TS 36.355 v2.0.0 |
2.0.0 |
|||
|
2009-12 |
RP-46 |
RP-091208 |
RAN #46 approval of TS 36.355 |
9.0.0 |
|||
|
2010-03 |
RP-47 |
RP-100304 |
0001 |
– |
Clarification on Position location |
9.1.0 |
|
|
RP-47 |
RP-100304 |
0002 |
– |
Clarification on UE Rx-Tx time difference supporting capability |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0003 |
2 |
Completion of LPP common material |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0004 |
5 |
Completion of OTDOA in LPP |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0006 |
– |
Provision of Frame Drift Information in Network Time |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0007 |
– |
Clarification of measurement reference point |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0010 |
– |
GNSS-DifferentialCorrectionsSupport |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0011 |
– |
BSAlign Indication in GNSS Reference Time |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0012 |
1 |
Changes to reflect LPP ASN.1 review |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0013 |
1 |
Introduction of LPP reliability sublayer |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0015 |
– |
LPP error procedures and conditions |
9.1.0 |
||
|
RP-47 |
RP-100304 |
0016 |
– |
Triggered Location Information Transfer due to Cell Change |
9.1.0 |
||
|
2010-06 |
RP-48 |
RP-100558 |
0018 |
2 |
Addition of need codes to optional LPP information elements |
9.2.0 |
|
|
RP-48 |
RP-100558 |
0019 |
1 |
Miscellaneous corrections to LPP stage 3 |
9.2.0 |
||
|
RP-48 |
RP-100558 |
0020 |
1 |
Small corrections to LPP specification |
9.2.0 |
||
|
RP-48 |
RP-100558 |
0021 |
– |
Clarifications of OTDOA parameters |
9.2.0 |
||
|
RP-48 |
RP-100558 |
0022 |
1 |
Signalling support for PRS muting in OTDOA |
9.2.0 |
||
|
– |
– |
– |
– |
Two times capital R replaced by lower case r in "MeasuredResultsElement" (undoing not intended change) |
9.2.1 |
||
|
2010-09 |
RP-49 |
RP-100852 |
0024 |
– |
Addition of an EPDU to an LPP Error and LPP Abort |
9.3.0 |
|
|
RP-49 |
RP-100852 |
0026 |
– |
Division of LPP into Separate ASN.1 Modules with a Global Identifier |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0028 |
– |
Proposed Corrections to LPP Reliable Transport |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0029 |
– |
Proposed Corrections to the PeriodicalReportingCriteria in LPP |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0030 |
1 |
Various corrections and clarifications to LPP |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0031 |
– |
Support of functional components for LPP reliable transport |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0032 |
1 |
Introduction of EPDU ID requested by OMA LOC |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0035 |
1 |
Several corrections in LPP |
9.3.0 |
||
|
RP-49 |
RP-100852 |
0036 |
– |
Clarification to Assistance Data Transfer Procedure |
9.3.0 |
||
|
2010-12 |
RP-50 |
RP-101207 |
0037 |
– |
Correction of reliable transport terminology in description of LPP-Message |
9.4.0 |
|
|
RP-50 |
RP-101207 |
0038 |
– |
One cell with known SFN in OTDOA assistance data |
9.4.0 |
||
|
RP-50 |
RP-101207 |
0039 |
1 |
UE frequency capability for LPP |
9.4.0 |
||
|
RP-50 |
RP-101207 |
0041 |
– |
Correction to LPP reliable transport |
9.4.0 |
||
|
RP-50 |
RP-101207 |
0042 |
– |
Correction to LPP Error procedure |
9.4.0 |
||
|
RP-50 |
RP-101207 |
0043 |
– |
Addition of missing reference to LPPe |
9.4.0 |
||
|
RP-50 |
RP-101207 |
0044 |
2 |
Correction to the ODTOA assistance data |
9.4.0 |
||
|
RP-50 |
RP-101226 |
0040 |
– |
Update of ‘serving cell’ terminology in 36.355 |
10.0.0 |
||
|
2011-03 |
RP-51 |
RP-110269 |
0046 |
– |
Editorial corrections to 36.355 |
10.1.0 |
|
|
RP-51 |
RP-110269 |
0048 |
– |
Removal of FFS for retransmission timer in LPP |
10.1.0 |
||
|
RP-51 |
RP-110269 |
0050 |
– |
Correction to code phase encoding in GNSS acquisition assistance |
10.1.0 |
||
|
RP-51 |
RP-110269 |
0052 |
1 |
Clarification on SFN provided with OTDOA measurement |
10.1.0 |
||
|
RP-51 |
RP-110269 |
0053 |
1 |
Introduction of OTDOA inter-freq RSTD measurement indication procedure |
10.1.0 |
||
|
RP-51 |
RP-110269 |
0057 |
– |
Small corrections in 36.355 |
10.1.0 |
||
|
RP-51 |
RP-110269 |
0058 |
3 |
Further corrections to the OTDOA assistance data |
10.1.0 |
||
|
2011-06 |
RP-52 |
RP-110830 |
0060 |
– |
Clarifications to description of OTDOA positioning fields |
10.2.0 |
|
|
2011-09 |
RP-53 |
RP-111279 |
0062 |
1 |
Various corrections to LPP |
10.3.0 |
|
|
RP-53 |
RP-111279 |
0064 |
– |
Mandatory support of PRS for OTDOA measurements |
10.3.0 |
||
|
2011-12 |
RP-54 |
RP-111709 |
0066 |
– |
Clarification of packed encoding rules of LPP |
10.4.0 |
|
|
RP-54 |
RP-111709 |
0068 |
– |
Clarification of first bit in BIT STRING definitions |
10.4.0 |
||
|
2012-06 |
RP-56 |
RP-120808 |
0071 |
– |
Usage of additionalInformation IE |
10.5.0 |
|
|
2012-09 |
RP-57 |
RP-121424 |
0074 |
2 |
Corrections to GNSS Acquisition Assistance Data |
10.6.0 |
|
|
RP-57 |
– |
– |
– |
Upgrade to the Release 11 – no technical change |
11.0.0 |
||
|
2012-12 |
RP-58 |
RP-121931 |
0077 |
– |
Correcting the referencing of QoS parameters |
11.1.0 |
|
|
RP-58 |
RP-121931 |
0080 |
– |
Correction to missing field description in GNSS-AcquisitionAssistance IE |
11.1.0 |
||
|
2013-03 |
RP-59 |
RP-130237 |
0083 |
1 |
Extending E-UTRA Frequency Band and EARFCN value range |
11.2.0 |
|
|
RP-59 |
RP-130230 |
0086 |
– |
Correction to PRS Muting Configuration |
11.2.0 |
||
|
2013-06 |
RP-60 |
RP-130803 |
0088 |
– |
Correction for ASN.1 errors from CR0083r1 |
11.3.0 |
|
|
RP-60 |
RP-130803 |
0091 |
– |
Correction to integer code phase field description in GNSS Acquisition Assistance |
11.3.0 |
||
|
RP-60 |
RP-130803 |
0093 |
– |
Correction to serving cell terminology |
11.3.0 |
||
|
RP-60 |
RP-130803 |
0094 |
– |
Encoding of LPP IEs |
11.3.0 |
||
|
2013-09 |
RP-61 |
RP-131314 |
0098 |
– |
Correction on svReqList |
11.4.0 |
|
|
2013-12 |
RP-62 |
RP-131984 |
0103 |
– |
Correction to missing capability indication for inter-frequency RSTD measurements |
11.5.0 |
|
|
RP-62 |
RP-131984 |
0107 |
1 |
Correction to Galileo assistance data elements |
11.5.0 |
||
|
RP-62 |
RP-132000 |
0104 |
1 |
Stage 3 CR of TS 36.355 for introducing BDS in LTE |
12.0.0 |
||
|
RP-62 |
RP-131984 |
0108 |
– |
Correction to Galileo assistance data elements |
12.0.0 |
||
|
2014-03 |
RP-63 |
RP-140342 |
0112 |
1 |
Clarification to gnss-DayNumber |
12.1.0 |
|
|
2014-06 |
RP-64 |
RP-140871 |
0119 |
– |
Signaling of OTDOA Neighbour Cell Information and Measurements |
12.2.0 |
|
|
2014-12 |
RP-66 |
RP-142114 |
0122 |
– |
Correction to Galileo Assistance Data |
12.3.0 |
|
|
RP-66 |
RP-142114 |
0123 |
– |
Addition of an Early Position Fix to LPP |
12.3.0 |
||
|
RP-66 |
RP-142120 |
0124 |
– |
BDS update to version 2.0 |
12.3.0 |
||
|
2015-03 |
RP-67 |
RP-150369 |
0126 |
2 |
Correction of GLONASS system time |
12.4.0 |
|
|
RP-67 |
RP-150376 |
0125 |
1 |
LPP clean-up |
12.4.0 |
||
|
2015-12 |
RP-70 |
RP-152055 |
0134 |
1 |
Correction to the definition of Need codes |
12.5.0 |
|
|
2015-12 |
RP-70 |
RP-152068 |
0137 |
3 |
RAT-Independent positioning enhancements |
13.0.0 |
|
|
2016-03 |
RP-71 |
RP-160463 |
0138 |
1 |
Correction to GLONASS IOD value range |
13.1.0 |
|
|
RP-71 |
RP-160470 |
0140 |
1 |
r13 Information Element correction |
13.1.0 |
||
|
RP-71 |
RP-160470 |
0141 |
– |
WLAN AP Identifier correction |
13.1.0 |
||
|
RP-71 |
RP-160470 |
0142 |
1 |
LPP clean-up |
13.1.0 |
||
|
2016-09 |
RP-73 |
RP-161750 |
0143 |
4 |
Correction of ECID positioning for TDD |
13.2.0 |
|
|
2016-12 |
RP-74 |
RP-162317 |
0160 |
1 |
Clarification of WLAN RSSI value range |
13.3.0 |
|
|
2016-12 |
RP-74 |
RP-162326 |
0155 |
1 |
CR for 36.355 Further Indoor positioning enhancements |
14.0.0 |
|
|
RP-74 |
RP-162327 |
0157 |
– |
Barometric Pressure Uncertainty IEs |
14.0.0 |
||
|
RP-74 |
RP-162326 |
0161 |
1 |
Introduction of Further Indoor Positioning Enhancements |
14.0.0 |
||
|
2017-03 |
RP-75 |
RP-170636 |
0162 |
3 |
B |
Introduction of positioning for further enhanced MTC |
14.1.0 |
|
RP-75 |
RP-170642 |
0163 |
– |
C |
Addition of periodical and triggered reporting capabilitiy signalling |
14.1.0 |
|
|
RP-75 |
RP-170642 |
0165 |
2 |
F |
Further Indoor positioning enhancements corrections |
14.1.0 |
|
|
RP-75 |
RP-170637 |
0166 |
– |
B |
Introduction of positioning support for NB-IoT |
14.1.0 |
|
|
2017-06 |
RP-76 |
RP-171224 |
0169 |
3 |
F |
Compact Signal Measurement Information for OTDOA |
14.2.0 |
|
RP-76 |
RP-171223 |
0171 |
1 |
F |
Correction to PRS Subframe Offset |
14.2.0 |
|
|
RP-76 |
RP-171223 |
0173 |
1 |
F |
Correction to SFN time stamp in OTDOA Signal Measurement Information |
14.2.0 |
|
|
RP-76 |
RP-171223 |
0174 |
1 |
F |
Correction to OTDOA capabilities |
14.2.0 |
|
|
RP-76 |
RP-171224 |
0175 |
1 |
F |
Correction to NPRS |
14.2.0 |
|
|
RP-76 |
RP-171225 |
0176 |
2 |
F |
LPP clean-up |
14.2.0 |
|
|
RP-76 |
RP-171224 |
0177 |
– |
F |
Corrections to number of NPRS carriers and ECID measurements for NB-IoT |
14.2.0 |
|
|
RP-76 |
RP-171224 |
0178 |
1 |
F |
Removal of FFS for retransmission timer in LPP |
14.2.0 |
|
|
RP-76 |
RP-171224 |
0181 |
1 |
F |
Signalling optimisation for NB-IoT Enhancements |
14.2.0 |
|
|
2017-09 |
RP-77 |
RP-171913 |
0182 |
2 |
F |
Clarification on definition of PRS Occasion Group |
14.3.0 |
|
RP-77 |
RP-171914 |
0183 |
1 |
F |
Additional OTDOA Capabilities |
14.3.0 |
|
|
RP-77 |
RP-171911 |
0184 |
– |
F |
Clarification to GNSS-TimeModelList |
14.3.0 |
|
|
RP-77 |
RP-171913 |
0185 |
1 |
F |
Minor corrections on TS 36.355 for Rel-14 MTC |
14.3.0 |
|
|
2017-12 |
RP-78 |
RP-172616 |
0187 |
2 |
F |
Correction on PRS hopping configuration |
14.4.0 |
|
2018-03 |
RP-79 |
RP-180446 |
0189 |
1 |
F |
Segmentation of LPP Messages |
14.5.0 |
|
2018-04 |
RP-79 |
New version to fix ASN.1 formatting |
14.5.1 |
||||
|
2018-06 |
RP-80 |
RP-181235 |
0202 |
2 |
F |
Clarification for NRSRQ reporting with E-CID |
14.6.0 |
|
2018-06 |
RP-80 |
RP-181219 |
0204 |
2 |
B |
Introduction of IMU support for OTDOA |
15.0.0 |
|
RP-80 |
RP-181219 |
0205 |
1 |
B |
Addition of RTK and PPP support |
15.0.0 |
|
|
RP-80 |
RP-181219 |
0207 |
1 |
B |
Addition of broadcast of positioning assistance data |
15.0.0 |
|
|
RP-80 |
RP-181215 |
0209 |
1 |
B |
Addition of NR Support |
15.0.0 |
|
|
RP-80 |
RP-181252 |
0210 |
1 |
B |
Addition of NB-IoT TDD support |
15.0.0 |
|
|
2018-09 |
RP-81 |
RP-181963 |
0215 |
1 |
A |
Support for NPRS enhancements |
15.1.0 |
|
RP-81 |
RP-181945 |
0218 |
1 |
F |
Corrections to TDD in 36.355 |
15.1.0 |
|
|
RP-81 |
RP-181961 |
0221 |
3 |
A |
Correction to RSRQ range in 36.355 |
15.1.0 |
|
|
RP-81 |
RP-181942 |
0222 |
1 |
F |
OTDOA Assistance Data Request for NR |
15.1.0 |
|
|
RP-81 |
RP-181960 |
0223 |
– |
F |
LPP clean-up |
15.1.0 |
|
|
RP-81 |
RP-181952 |
0224 |
1 |
F |
GAD shapes for high accuracy positioning |
15.1.0 |
|
|
RP-81 |
RP-181952 |
0226 |
1 |
B |
Positioning SIB value tag and expiration time |
15.1.0 |
|
|
2018-12 |
RP-82 |
RP-182672 |
0213 |
3 |
F |
Addition of TDD UL/DL configuration to OTDOA assistance data |
15.2.0 |
|
RP-82 |
RP-182681 |
0228 |
2 |
F |
Introduction of TDD UL/DL configuration for NB-IoT in 36.355 |
15.2.0 |
|
|
RP-82 |
RP-182659 |
0229 |
3 |
F |
SFN offset for OTDOA |
15.2.0 |
|
|
RP-82 |
RP-182674 |
0230 |
1 |
F |
Alignment of IE/field names between LPP and RRC specifications |
15.2.0 |
|
|
RP-82 |
RP-182672 |
0232 |
1 |
F |
Sensor Assistance Data Elements Correction |
15.2.0 |
|
|
2019-03 |
RP-83 |
RP-190550 |
0234 |
3 |
F |
Stage 2 and stage 3 sensor methods description alignment |
15.3.0 |
|
2019-06 |
RP-84 |
RP-191376 |
0239 |
1 |
F |
Minor corrections on NR Support |
15.4.0 |
|
RP-84 |
RP-191384 |
0240 |
4 |
F |
Periodic assistance data transfer with cell ID change procedure |
15.4.0 |
|
|
2019-09 |
RP-85 |
RP-192196 |
0243 |
1 |
F |
Distinguishing Location Source when sensor method is used |
15.5.0 |
NOTE: The table above will not be further updated in the future. It shows all TS 36.355 CRs taken over into
TS 37.355 v1.0.0.
|
Change history of TS 37.355 |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2019-12 |
RP-86 |
RP-192450 |
– |
– |
– |
TS 36.355 v15.5.0 contents was transferred into this new TS 37.355 as by definition 36 series specifications cover E-UTRA/LTE only aspects and multi-RAT aspects need to be covered in 37 series specifications. The only changes compared to TS 36.355 v15.5.0: – new 37 series TS number is added: TS 37.355 – "Evolved Universal Terrestrial Radio Access (E-UTRA)" is removed from the TS title as beginning with Rel-15 TS 36.355 needs to cover also NR – clarification in the Scope clause that this TS covers radio access technologies E-UTRA/LTE and NR – the CR history table of TS 36.355 was kept for easier reference of all changes included in TS 37.355 but a new CR history table was added for TS 37.355. |
1.0.0 |
|
2019-12 |
RP-86 |
The approved version upgraded to v15.0.0 by MCC. |
15.0.0 |
||||
|
2020-03 |
RP-87 |
RP-200367 |
0001 |
2 |
C |
Addition of broadcast of barometric pressure assistance data |
16.0.0 |
|
RP-87 |
RP-200357 |
0002 |
1 |
F |
Sensor Provide Location Information Elements Correction |
16.0.0 |
|
|
RP-87 |
RP-200365 |
0247 |
8 |
B |
CR of TS 37.355 for introducing NavIC in LTE – core part |
16.0.0 |
|
|
RP-87 |
RP-200357 |
0248 |
1 |
B |
Introduction of B1C signal in BDS system in A-GNSS |
16.0.0 |
|
|
RP-87 |
RP-200367 |
0249 |
1 |
C |
Addition of broadcast TBS assistance data |
16.0.0 |
|
|
RP-87 |
RP-200345 |
0250 |
2 |
B |
Introduction of NR positioning |
16.0.0 |
|
|
RP-87 |
RP-200357 |
0252 |
1 |
B |
Introducing support for GNSS Integer Ambiguity Level Indications |
16.0.0 |
|
|
2020-07 |
RP-88 |
RP-201196 |
0257 |
2 |
F |
Introduction of NavIC Keplerian set IE |
16.1.0 |
|
RP-88 |
RP-201190 |
0259 |
1 |
F |
Update B1I signal ICD file to v3.0 in BDS system in A-GNSS |
16.1.0 |
|
|
RP-88 |
RP-201175 |
0260 |
– |
F |
LPP Clean-Up |
16.1.0 |
|
|
RP-88 |
RP-201175 |
0261 |
1 |
B |
Introduction of Release-16 UE positioning capabilities |
16.1.0 |
|
|
2020-09 |
RP-89 |
RP-201989 |
0272 |
– |
F |
LPP miscellaneous corrections |
16.2.0 |
|
2020-12 |
RP-90 |
RP-202775 |
0274 |
– |
F |
Clarification of quality and time stamp for RSTD measurements |
16.3.0 |
|
RP-90 |
RP-202789 |
0280 |
2 |
F |
Correction of hanging ASN.1 code after END |
16.3.0 |
|
|
RP-90 |
RP-202775 |
0282 |
– |
F |
Correction on LPP spec |
16.3.0 |
|
|
2021-03 |
RP-91 |
RP-210695 |
0284 |
1 |
F |
Corrections on the field description of commonIEsProvideAssistanceData in TS37.355 |
16.4.0 |
|
2021-06 |
RP-92 |
RP-211474 |
0288 |
4 |
F |
LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap |
16.5.0 |
|
RP-92 |
RP-211482 |
0292 |
3 |
F |
Correction to the need code for downlink LPP message-R16 |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0294 |
2 |
F |
Miscellaneous corrections on the field description |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0300 |
2 |
F |
Correction to PRS configuration |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0301 |
2 |
F |
Correction to the uplink LPP message |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0302 |
3 |
F |
Correction to DL-PRS capability |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0306 |
2 |
F |
Correction to NR-ARFCN of the TRP |
16.5.0 |
|
|
RP-92 |
RP-211474 |
0311 |
– |
F |
Description on timestamp reference in NR positioning measurement report |
16.5.0 |
|
|
2021-09 |
RP-93 |
RP-212443 |
0305 |
5 |
F |
Correction to PRS-only TP |
16.6.0 |
|
RP-93 |
RP-212443 |
0312 |
1 |
F |
Correction for LPP assistance information |
16.6.0 |
|
|
RP-93 |
RP-212443 |
0313 |
1 |
F |
Corrections on the conditional presence tag clarification for Uplink LPP message |
16.6.0 |
|
|
RP-93 |
RP-212443 |
0318 |
– |
F |
Correction to the need code in NR-SelectedDL-PRS-IndexList |
16.6.0 |
|
|
2021-12 |
RP-94 |
RP-213344 |
0321 |
2 |
F |
Updates based on RAN1 NR positioning features list |
16.7.0 |
|
RP-94 |
RP-213345 |
0323 |
3 |
F |
Correction on BDS B2I clock model [Rel16BDS] |
16.7.0 |
|
|
2022-03 |
RP-95 |
RP-220835 |
0326 |
– |
F |
Addition of missing need code for the BDS TGD2 parameter |
16.8.0 |
|
RP-95 |
RP-220472 |
0329 |
1 |
A |
Correction on the object identifier of LPP ASN.1 for R16 |
16.8.0 |
|
|
RP-95 |
RP-220835 |
0330 |
– |
F |
Correction of reference TRP for DL-AoD and Multi-RTT measurement report |
16.8.0 |
|
|
RP-95 |
RP-220835 |
0331 |
– |
F |
Correction to NR-DL-PRS-ResourcesCapability field description |
16.8.0 |
|
|
RP-95 |
RP-220835 |
0333 |
1 |
F |
Introducing new high accuracy GAD shape with scalable uncertainty |
16.8.0 |
|
|
2022-03 |
RP-95 |
RP-220479 |
0332 |
– |
B |
Introduction of R17 Positioning Enhancements in LPP |
17.0.0 |
|
2022-06 |
RP-96 |
RP-221725 |
0347 |
– |
F |
LPP Updates and ASN.1 Corrections |
17.1.0 |
|
RP-96 |
RP-221736 |
0349 |
2 |
B |
NMEA GGA sentence info in high accuracy GNSS location estimates [HA-GNSS-NMEA] |
17.1.0 |
|
|
2022-09 |
RP-97 |
RP-222524 |
0359 |
2 |
F |
Corrections on LPP capabilities |
17.2.0 |
|
RP-97 |
RP-222524 |
0377 |
1 |
F |
Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 |
17.2.0 |
|
|
RP-97 |
RP-222524 |
0378 |
1 |
F |
Miscellaneous LPP Corrections |
17.2.0 |
|