9.4 RRC Protocol Procedures
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
9.4.1 PosSIB broadcasting followed by location information transfer
9.4.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE has no assistance data stored and receives the positioning assistance data via posSIBs and then UE receives a location request from LMF}
then { the UE sends a PROVIDE LOCATION INFORMATION message containing a location estimate }
}
9.4.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 37.355 clauses 7.1, 7.2, and TS 38.331 clause 5.2.2.3.5. Unless otherwise stated these are Rel-16 requirements.
[TS 37.355, clause 7.1]
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.
[TS 37.355, clause 7.2]
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 |
|
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 |
[TS 38.331, clause 5.2.2.3.5]
The UE shall:
1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with sub-clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with sub-clause 5.2.2.1:
2> for the SI message(s) that, according to the si-SchedulingInfo or posSI-SchedulingInfo in the stored SIB1, contain at least one required SIB or requested posSIB:
3> if onDemandSIB-Request is configured and timer T350 is not running:
4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;
4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;
1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with sub-clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with sub-clause 5.2.2.1:
2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting:
3> acquire the SI message(s) as defined in sub-clause 5.2.2.3.2;
2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting:
3> if onDemandSIB-Request is configured and timer T350 is not running:
4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;
4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;
4> acquire the requested SI message(s) corresponding to the requested SIB(s) as defined in sub-clause 5.2.2.3.2.
2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting:
3> acquire the SI message(s) as defined in sub-clause 5.2.2.3.2;
2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to notBroadcasting:
3> if onDemandSIB-Request is configured and timer T350 is not running:
4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;
4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;
4> acquire the requested SI message(s) corresponding to the requested posSIB(s) as defined in sub-clause 5.2.2.3.2.
NOTE: UE may include on demand request for SIB and/or posSIB(s) in the same DedicatedSIBRequest message.
9.4.1.3 Test description
9.4.1.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.4.1.3.2-2): NR Cell 1 and system information combination NR-1 as defined in TS 38.508-1 [30] clause 4.4.3.1.2.
– Satellite signals (sub-test case 25): as specified in 8.2.1.
– MBS signals (Sub-test 23): as specified in 8.2.4.
– Sub-test 20: NR Cell 1 and NR Cell 2 as specified in 8.2.10 and system information combination NR-2 as defined in TS 38.508-1 [30] clause 4.4.3.1.2.
– Sub-test 21: NR Cell 1, NR Cell 2 and NR Cell 3 as specified in 8.2.11 and system information combination NR-4 as defined in TS 38.508-1 [30] clause 4.4.3.1.2.
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.4.1.3.2-2): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– Then the SS sends the RESET UE POSITIONING STORED INFORMATION message to the UE to clear the stored assistance data in the UE.
– The UE is switched-off.
Related PICS/PIXIT Statements:
–
9.4.1.3.2 Test procedure sequence
This test case includes sub-test cases dependent on the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 9.4.1.3.2-1 below:
Table 9.4.1.3.2-1: Sub-test case numbers
Sub-Test Case Number |
Supported Positioning Methods |
20 |
UE supporting DL-AoD (Rel-16 onwards) |
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
23 |
UE supporting MBS(2) (Rel-16 onwards) |
24 |
UE supporting Sensor (Rel-16 onwards) |
25 |
UE supporting GNSS(1) (Rel-15 onwards) |
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
Table 9.4.1.3.2-2: Test Configuration
Test Configuration |
Network Deployment Type |
Test Implementation |
B |
NG-RAN NR |
Table 9.4.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The UE is switched on. |
– |
– |
||
2 |
System information that includes the needed posSystemInformation is broadcasted. Note: The sysinfo combination is NR-16 for Sub-test 20, NR-17 for Sub-test 21, NR-15 for Sub-test 23, Sub-test 24 and Sub-test 25. |
<– |
RRC: SYSTEM INFORMATION (BCCH) |
– |
– |
3-10 |
Steps 1 to 8 of the NR RRC_CONNECTED procedure in TS 38.508-1 [3] Table 4.5.4.2-3 are executed. |
– |
– |
||
– |
EXCEPTION: Steps 11a1 to 11a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
||||
11a1 |
IF sub-test 20 or 21 THEN The SS sends an RRCReconfiguration message as in Table 8.3.1-1 to configure the measurement gap. |
<– |
RRC RRCReconfiguration |
– |
– |
11a2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
12 |
The SS sends a LPP message of type Request Capabilities. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
13 |
The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
14 |
IF the UE LPP message at step 13 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
15 |
The SS sends a LPP message of type Request Location Information including a request for location estimate and location measurements. |
<– |
DLInformationTransfer (LPP REQUEST LOCATION INFORMATION) |
– |
– |
16 |
The UE sends a LPP message of type Provide Location Information including location estimate. |
–> |
ULInformationTransfer (LPP PROVIDE LOCATION INFORMATION) |
1 |
P |
17 |
IF the UE LPP message at step 16 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
9.4.1.3.3 Specific message contents
Table 9.4.1.3.3-1: RESET UE POSITIONING STORED INFORMATION (Preamble)
Derivation Path: 38.509 clause 6.6 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
UE Positioning Technology |
Sub-test 20: 0 0 0 0 1 0 0 0 Sub-test 21: 0 0 0 0 0 1 1 1 Sub-test 23: 0 0 0 0 0 0 1 0 Sub-test 24: 0 0 0 0 0 1 0 1 Sub-test 25: 0 0 0 0 0 0 0 0 |
Sub-test 20: DL-AoD Sub-test 21: DL-TDOA Sub-test 23: MBS Sub-test 24: Sensor Sub-test 25: GNSS |
Table 9.4.1.3.3-2: SIB1 (step 2, Table 9.4.1.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-28 with condition posSIB. |
Table 9.4.1.3.3-3: PosSI-SchedulingInfo (SIB1, Table 9.4.1.3.3-2)
Derivation Path: TS 38.508-1, Table 4.6.2a-2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PosSI-SchedulingInfo-r16 ::= SEQUENCE { |
||||
posSchedulingInfoList-r16 SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16 { |
2 entries |
The size of PosSchedulingInfo-r16 is 1 for Sub-tests 20, 21, 23 and 24. If Sub-test 25 and UE supports X GNSS systems, the size of PosSchedulingInfo-r16 is (X+1) and the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
||
PosSchedulingInfo-r16[1] SEQUENCE { |
entry 1 |
|||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
3 entries for Sub-test 25, 1 entry for Sub-tests 20, 21, 23 and 24 |
PosSibType-n = posSibType1-1, posSibType1-2, posSibType1-3 |
Sub-test 25 |
|
PosSibType-n = posSibType4-1 |
Sub-test 24 |
|||
PosSibType-n = posSibType5-1 |
Sub-test 23 |
|||
PosSibType-n = posSibType6-1 |
Sub-test 20 or Sub-test 21 |
|||
PosSIB-Type-r16[n] SEQUENCE { |
entry n |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Not present |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-n |
The posSibType-r16 is depending on the sub–test cases and entry number n |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
PosSchedulingInfo-r16[2] SEQUENCE { |
entry 2 If the UE supports X GNSS systems, the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
Sub-test 25 |
||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
6 entries for Sub-test 25 |
posSibType2-1, posSibType2-3, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9 |
||
PosSIB-Type-r16[m] SEQUENCE { |
entry m |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Set depending on the GNSS supported by the UE |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-m, |
The posSibType-r16 is depending on the entry number m |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.1.3.3-4: SystemInformation – Sub-tests 20, 21, 23 and 24 (step 2, Table 9.4.1.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB. |
Table 9.4.1.3.3-4A: SystemInformation – Sub-test 25, message 1 (step 2, Table 9.4.1.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB and posSib1-x. |
Table 9.4.1.3.3-4B: SystemInformation – Sub-test 25, message 2 and subsequent (step 2, Table 9.4.1.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB and posSib2-x. |
Table 9.4.1.3.3-5: PosSystemInformation-r16-IEs (step 2, Table 9.4.1.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.2a-1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PosSystemInformation-r16-IEs ::= SEQUENCE { |
||||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
3 entries |
Sub-test 25 posSib1-x |
||
posSib1-1-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 1 |
||
posSib1-2-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 2 |
||
posSib1-3-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 3 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
6 entries |
Sub-test 25, posSib2-x |
||
posSib2-1-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 1 |
||
posSib2-3-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 2 |
||
posSib2-6-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 3 |
||
posSib2-7-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 4 |
||
posSib2-8-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 5 |
||
posSib2-9-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 6 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 24 |
||
posSib4-1-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 1 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 23 |
||
posSib5-1-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 1 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 20, Sub-test 21 |
||
posSib6-1-r16 |
SIBpos as defined in Table 9.4.1.3.3-6 |
entry 1 |
||
} |
||||
lateNonCriticalExtension |
Not present |
|||
nonCriticalExtension |
Not present |
|||
} |
Table 9.4.1.3.3-6: SIBpos (PosSystemInformation-r16-IEs, Table 9.4.1.3.3-5)
Derivation Path: TS 38.501-1, Table 4.6.2a-3 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SIBpos-r16 ::= SEQUENCE { |
||||
assistanceDataSIB-Element-r16 |
OCTET STRING containing AssistanceDataSIBelement |
|||
} |
Table 9.4.1.3.3-7: AssistanceDataSIBelement
Derivation Path: TS 37.355, clause 7.4.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
AssistanceDataSIBelement-r15 ::= SEQUENCE { |
||||
valueTag-r15 |
Not present |
|||
expirationTime-r15 |
Not present |
|||
cipheringKeyData-r15 |
Not present |
|||
segmentationInfo-r15 |
Not present |
Not present when the posSIB is not segmented |
||
segmentationInfo-r15 SEQUENCE { |
Present when the posSIB is segmented |
|||
segmentationOption-r15 |
octet-string-seg |
|||
assistanceDataSegmentType-r15 |
notLastSegment |
Used when posSIB is segmented and the segment is not the last segment |
||
lastSegment |
Used when posSIB is not segmented, or posSIB is segmented and the segment is the last segment |
|||
assistanceDataSegmentNumber-r15 |
index of the segmented posSIB |
|||
} |
||||
assistanceDataElement-r15 |
OCTET STRING containing LPP IEs (GNSS-ReferenceTime, GNSS-ReferenceLocation, GNSS-IonosphericModel,GNSS-TimeModelList, GNSS-NavigationModel, GNSS-AcquisitionAssistance, GNSS-Almanac, GNSS-UTC-Model, GNSS-AuxiliaryInformation ) as defined in TS 37.571-5 [12] and mapped according to the content of posSibType-r16 in Table 9.4.1.3.3-3. |
Sub-test 25 |
||
OCTET STRING containing sensor-AssistanceDataList as defined in Table 8.4-1 |
Sub-test 24 |
|||
OCTET STRING containing tbs-AssistanceDataList as defined in Table 8.4-1 |
Sub-test 23 |
|||
OCTET STRING containing NR-DL-PRS-AssistanceData as defined in Table 8.4.1.6-1. |
Sub-test 20, Sub-test 21 |
|||
} |
Table 9.4.1.3.3-8: DLInformationTransfer (step 12, step 14, step 15 and step 17, Table 9.4.1.3.2-3)
Derivation Path: 38.331 clause 6.2.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DLInformationTransfer ::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
||||
criticalExtensions CHOICE { |
||||
dlInformationTransfer SEQUENCE { |
||||
dedicatedNAS-Message OCTET STRING |
Set according to Table 9.4.1.3.3-9 |
DL NAS TRANSPORT |
||
nonCriticalExtension SEQUENCE {} |
Not present |
|||
} |
||||
} |
||||
} |
Table 9.4.1.3.3-9: DL NAS TRANSPORT (DLInformationTransfer, Table 9.4.1.3.2-8)
Derivation Path: 24.501 Table 8.2.11.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Extended Protocol discriminator |
01111110 |
5GS mobility management messages |
||
Security header type |
0000 |
Plain 5GS NAS message |
||
Spare half octet |
0000 |
Downlink generic NAS transport |
||
DL NAS TRANSPORT message identity |
01101000 |
DL NAS transport |
||
Payload container type |
0011 |
LTE Positioning Protocol (LPP) message container |
||
Spare half octet |
0000 |
|||
Payload container |
Step 12: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
Step 15: Set according to Table 9.3.4.1.3.3-10 |
LPP Request Location Information |
|||
Steps 14 and 17: Set according to Table 9.4.1.3.3-11 |
LPP Acknowledgement |
|||
Additional information |
Present |
Routing Identifier/Correlation ID |
Table 9.4.1.3.3-10: LPP Request Location Information (DL NAS TRANSPORT, Table 9.4.1.3.2-9)
Derivation Path: Table 8.4-3 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-3 with the following exceptions: |
||||
locationInformationType |
locationMeasurementsPreferred |
Table 9.4.1.3.3-11: LPP Acknowledgement (DL NAS TRANSPORT, Table 9.4.1.3.2-9)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID |
Not present |
|||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement SEQUENCE { |
||||
ackRequested |
FALSE |
|||
ackIndicator |
(0..255) |
Contains the same value of the sequenceNumber field in step 13 or 16, Table 9.4.1.3.2-3 |
||
} |
||||
lpp-MessageBody |
Not present. |
|||
} |
Table 9.4.1.3.3-12: ULInformationTransfer (steps 13 and 16, Table 9.4.1.3.2-3)
Derivation Path: 38.331 clause 6.2.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
ULInformationTransfer ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
ulInformationTransfer SEQUENCE { |
||||
dedicatedNAS-Message OCTET STRING |
Set according to Table 9.4.1.3.3-13 |
UL NAS TRANSPORT |
||
nonCriticalExtension SEQUENCE {} |
Not present |
|||
} |
||||
} |
||||
} |
Table 9.4.1.3.3-13: UL NAS TRANSPORT (ULInformationTransfer, Table 9.4.1.3.3-12)
Derivation Path: 24.501 Table 8.2.10.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Extended Protocol discriminator |
01111110 |
5GS mobility management messages |
||
Security header type |
0000 |
Plain 5GS NAS message |
||
Spare half octet |
0000 |
|||
UL NAS TRANSPORT message identity |
01100111 |
UL NAS TRANSPORT |
||
Payload container type |
0011 |
LTE Positioning Protocol (LPP) message container |
||
Spare half octet |
0000 |
|||
Payload container |
Step 13: Set according to Table 9.4.1.3.3-14 |
LPP Provide Capabilities |
||
Step 16: Set according to Table 9.4.1.3.3-15 |
LPP Provide Location Information |
|||
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 12 Table 9.4.1.3.2-3) |
Table 9.4.1.3.3-14: LPP Provide Capabilities (UL NAS TRANSPORT, Table 9.4.1.3.3-13)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
locationServer |
|||
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in the LPP Request Capabilities message in step 12, Table 9.4.1.3.2-3 |
||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement SEQUENCE { |
Present, or not present |
|||
ackRequested |
TRUE |
|||
ackIndicator |
Not present |
|||
} |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideCapabilities SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideCapabilities-r9 SEQUENCE { |
||||
commonIEsProvideCapabilities |
Dependent on UE capabilities |
Rel-14 onwards |
||
a-gnss-ProvideCapabilities |
Dependent on UE capabilities |
|||
sensor-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-16 onwards |
||
tbs-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-16 onwards |
||
nr-DL-AoD-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
nr-DL-TDOA-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.1.3.3-15: LPP Provide Location Information (UL NAS TRANSPORT, Table 9.4.1.3.3-13)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
locationServer |
|||
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in LPP Request Location Information message in step 15, Table 9.4.1.3.2-3 |
||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement SEQUENCE { |
present, or not present |
|||
ackRequested |
TRUE |
|||
ackIndicator |
Not present |
|||
} |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
May be present. Any value acceptable |
|||
a-gnss-ProvideLocationInformation SEQUENCE { |
Present for sub-test 25 |
|||
gnss-SignalMeasurementInformation SEQUENCE { |
Present. |
|||
measurementReferenceTime |
Any value acceptable |
|||
gnss-MeasurementList |
Any value acceptable |
|||
} |
||||
gnss-LocationInformation SEQUENCE { |
May be present |
|||
measurementReferenceTime |
Any value acceptable |
|||
agnss-List |
Any value acceptable |
|||
} |
||||
gnss-Error |
Not present |
|||
} |
||||
sensor-ProvideLocationInformation-r13 SEQUENCE { |
Present for sub-test 24 |
Rel-16 onwards |
||
sensor-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
sensor-Error-r13 |
Not present |
|||
sensor-MotionInformation-r15 |
May be present |
|||
} |
||||
tbs-ProvideLocationInformation-r13 SEQUENCE { |
Present for sub-test 23 |
Rel-16 onwards |
||
tbs-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
tbs-Error-r13 |
Not present |
|||
} |
||||
nr-DL-AoD-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 20 |
Rel-16 onwards |
||
nr-DL-AoD-SignalMeasurementInformation-r16 SEQUENCE { |
Present. |
|||
nr-DL-AoD-MeasList-r16 |
Any value acceptable |
|||
} |
||||
nr-dl-AoD-LocationInformation-r16 |
May be present |
|||
nr-DL-AoD-Error-r16 |
Not present |
|||
} |
||||
nr-DL-TDOA-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 21 |
Rel-16 onwards |
||
nr-DL-TDOA-SignalMeasurementInformation-r16 SEQUENCE { |
Present. |
|||
dl-PRS-ReferenceInfo-r16 |
Any value acceptable |
|||
nr-DL-TDOA-MeasList-r16 |
Any value acceptable |
|||
} |
||||
nr-dl-tdoa-LocationInformation-r16 |
May be present |
|||
nr-DL-TDOA-Error-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
9.4.2 PosSIB broadcasting followed by location information transfer / Positioning SI messages offset
9.4.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE has no assistance data stored and receives the positioning assistance data via posSIBs and offsetToSI-Used-r16 is present and then UE receives a location request from LMF}
then { the UE acquires the SI message at the correct position and then sends a PROVIDE LOCATION INFORMATION message containing a location estimate }
}
9.4.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 clauses 5.2.2.3.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.2.2.3.2]
For SI message acquisition PDCCH monitoring occasion(s) are determined according to searchSpaceOtherSystemInformation. If searchSpaceOtherSystemInformation is set to zero, PDCCH monitoring occasions for SI message reception in SI-window are same as PDCCH monitoring occasions for SIB1 where the mapping between PDCCH monitoring occasions and SSBs is specified in TS 38.213[13]. If searchSpaceOtherSystemInformation is not set to zero, PDCCH monitoring occasions for SI message are determined based on search space indicated by searchSpaceOtherSystemInformation. PDCCH monitoring occasions for SI message which are not overlapping with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from one in the SI window. The [x×N+K]th PDCCH monitoring occasion (s) for SI message in SI-window corresponds to the Kth transmitted SSB, where x = 0, 1, …X-1, K = 1, 2, …N, N is the number of actual transmitted SSBs determined according to ssb-PositionsInBurst in SIB1 and X is equal to CEIL(number of PDCCH monitoring occasions in SI-window/N). The actual transmitted SSBs are sequentially numbered from one in ascending order of their SSB indexes. The UE assumes that, in the SI window, PDCCH for an SI message is transmitted in at least one PDCCH monitoring occasion corresponding to each transmitted SSB and thus the selection of SSB for the reception SI messages is up to UE implementation.
When acquiring an SI message, the UE shall:
1> determine the start of the SI-window for the concerned SI message as follows:
2> if the concerned SI message is configured in the schedulingInfoList:
3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of SI messages configured by schedulingInfoList in si-SchedulingInfo in SIB1;
3> determine the integer value x = (n – 1) × w, where w is the si-WindowLength;
3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the si-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];
2> else if the concerned SI message is configured in the posSchedulingInfoList and offsetToSI-Used is not configured:
3> create a concatenated list of SI messages by appending the posSchedulingInfoList in posSI-SchedulingInfo in SIB1 to schedulingInfoList in si-SchedulingInfo in SIB1;
3> for the concerned SI message, determine the number n which corresponds to the order of entry in the concatenated list;
3> determine the integer value x = (n – 1) × w, where w is the si-WindowLength;
3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N), where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];
2> else if the concerned SI message is configured by the posSchedulingInfoList and offsetToSI-Used is configured:
3> determine the number m which corresponds to the number of SI messages with an associated si-Periodicity of 8 radio frames (80 ms), configured by schedulingInfoList in SIB1;
3> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of SI messages configured by posSchedulingInfoList in SIB1;
3> determine the integer value x = m × w + (n – 1) × w, where w is the si-WindowLength;
3> the SI-window starts at the slot #a, where a = x mod N, in the radio frame for which SFN mod T = FLOOR(x/N) +8, where T is the posSI-Periodicity of the concerned SI message and N is the number of slots in a radio frame as specified in TS 38.213 [13];.
9.4.2.3 Test description
9.4.2.3.1 Pre-test conditions
Same as in clause 9.4.1.3.1.
9.4.2.3.2 Test procedure sequence
Same as in clause 9.4.1.3.2.
9.4.2.3.3 Specific message contents
Same as 9.4.1.3.3 except that Table 9.4.2.3.3-1 replaces Table 9.4.1.3.3-3.
Table 9.4.2.3.3-1: PosSI-SchedulingInfo (SIB1, Table 9.4.1.3.3-2)
Derivation Path: TS 38.508-1, Table 4.6.2a-2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PosSI-SchedulingInfo-r16 ::= SEQUENCE { |
||||
posSchedulingInfoList-r16 SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16 { |
2 entries |
The size of PosSchedulingInfo-r16 is 1 for Sub-tests 20, 21, 23 and 24. If Sub-test 25 and UE supports X GNSS systems, the size of PosSchedulingInfo-r16 is (X+1) and the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
||
PosSchedulingInfo-r16[1] SEQUENCE { |
entry 1 |
|||
offsetToSI-Used-r16 |
true |
|||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
3 entries for Sub-test 25, 1 entry for Sub-tests 20, 21, 23 and 24 |
PosSibType-n = posSibType1-1, posSibType1-2, posSibType1-3 |
Sub-test 25 |
|
PosSibType-n = posSibType4-1 |
Sub-test 24 |
|||
PosSibType-n = posSibType5-1 |
Sub-test 23 |
|||
PosSibType-n = posSibType6-1 |
Sub-test 20 or Sub-test 21 |
|||
PosSIB-Type-r16[n] SEQUENCE { |
entry n |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Not present |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-n |
The posSibType-r16 is depending on the sub–test cases and entry number n |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
PosSchedulingInfo-r16[2] SEQUENCE { |
entry 2 If the UE supports X GNSS systems, the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
Sub-test 25 |
||
offsetToSI-Used-r16 |
true |
|||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
6 entries for Sub-test 25 |
posSibType2-1, posSibType2-3, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9 |
||
PosSIB-Type-r16[m] SEQUENCE { |
entry m |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Set depending on the GNSS supported by the UE |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-m, |
The posSibType-r16 is depending on the entry number m |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
9.4.3 On-demand PosSIB followed by location information transfer / RRC_connected state
9.4.3.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE has no assistance data stored and receives a REQUEST LOCATION INFORMATION message }
then { the UE sends the DedicatedSIBRequest message indicating the requested posSIB }
}
(2)
with { a NAS signalling connection existing }
ensure that {
when { UE receives the positioning assistance data via posSIBs after sending the onDemandSIB-Request message }
then { the UE sends a PROVIDE LOCATION INFORMATION message containing a location estimate }
}
9.4.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 clauses 5.2.2.1, 5.2.2.3.5, 5.2.2.3.6 and TS 37.355 clause7.2. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.2.2.1]
The UE applies the SI acquisition procedure to acquire the AS, NAS- and positioning assistance data information. The procedure applies to UEs in RRC_IDLE, in RRC_INACTIVE and in RRC_CONNECTED.
[TS 38.331, clause 5.2.2.3.5]
The UE shall:
1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with sub-clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with sub-clause 5.2.2.1:
2> for the SI message(s) that, according to the si-SchedulingInfo or posSI-SchedulingInfo in the stored SIB1, contain at least one required SIB or requested posSIB:
3> if onDemandSIB-Request is configured and timer T350 is not running:
4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;
4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;
1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with sub-clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with sub-clause 5.2.2.1:
…
2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting:
3> acquire the SI message(s) as defined in sub-clause 5.2.2.3.2;
2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to notBroadcasting:
3> if onDemandSIB-Request is configured and timer T350 is not running:
4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6;
4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer;
4> acquire the requested SI message(s) corresponding to the requested posSIB(s) as defined in sub-clause 5.2.2.3.2.
[TS 38.331, clause 5.2.2.3.6]
The UE shall set the contents of DedicatedSIBRequest message as follows:
1> if the procedure is triggered to request the required SIB(s):
2> include requestedSIB-List in the onDemandSIB-RequestList to indicate the requested SIB(s);
1> if the procedure is triggered to request the required posSIB(s):
2> include requestedPosSIB-List in the onDemandSIB-RequestList to indicate the requested posSIB(s).
The UE shall submit the DedicatedSIBRequest message to lower layers for transmission.
[TS 37.355, clause 7.2]
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 |
|
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 |
9.4.3.3 Test description
9.4.3.3.1 Pre-test conditions
System Simulator:
– Sub-test 23, sub-test 24 and sub-test 25: NR Cell 1 and system information combination NR-1 as defined in TS 38.508-1 [30] clause 4.4.3.1.2.
– Satellite signals (sub-test case 25): as specified in 8.2.1.
– MBS signals (Sub-test 23): as specified in 8.2.4.
– Sub-test 20: NR Cell 1 and NR Cell 2 as specified in 8.2.10 and system information combination NR-2 as defined in TS 38.508-1 [30] clause 4.4.3.1.2.
– Sub-test 21: NR Cell 1, NR Cell 2 and NR Cell 3 as specified in 8.2.11 and system information combination NR-4 as defined in TS 38.508-1 [30] clause 4.4.3.1.2..
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– Then the SS sends the RESET UE POSITIONING STORED INFORMATION message to the UE to clear the stored assistance data in the UE.
Related PICS/PIXIT Statements:
–
9.4.3.3.2 Test procedure sequence
This test case includes sub-test cases dependent on the positioning method(s) supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined in Table 9.4.3.3.2-1 below:
Table 9.4.3.3.2-1: Sub-test case numbers
Sub-Test Case Number |
Supported Positioning Methods |
20 |
UE supporting DL-AoD (Rel-16 onwards) |
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
23 |
UE supporting MBS(2) (Rel-16 onwards) |
24 |
UE supporting Sensor (Rel-16 onwards) |
25 |
UE supporting GNSS(1) (Rel-15 onwards) |
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
Table 9.4.3.3.2-2: Test Configuration
Test Configuration |
Network Deployment Type |
Test Implementation |
B |
NG-RAN NR |
Table 9.4.3.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
– |
EXCEPTION: Steps 1a1 to 1a2 describe behaviour that depends on the UE capability; the "lower case letter" identifies a step sequence that takes place if a capability is supported. |
||||
1a1 |
IF sub-test 20 or 21 THEN The SS sends an RRCReconfiguration message as in Table 8.3.1-1 to configure the measurement gap. |
<– |
RRC RRCReconfiguration |
– |
– |
1a2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
2 |
The SS sends a LPP message of type Request Capabilities. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
3 |
The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
4 |
IF the UE LPP message at step 3 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
5 |
The SS sends a LPP message of type Request Location Information including a request for location estimate and location measurements. |
<– |
DLInformationTransfer (LPP REQUEST LOCATION INFORMATION) |
– |
– |
6 |
Check: Does the UE send the DedicatedSIBRequest message indicating the requested posSIBs within 5 S? |
–> |
RRC: DedicatedSIBRequest |
1 |
P |
– |
EXCEPTION: In parallel to events described in step 6 steps 7a and 7b may take place. |
||||
7a |
The UE sends the LPP message of type REQUEST ASSISTANCE DATA message |
–> |
ULInformationTransfer (LPP REQUEST ASSISTANCE DATA) |
||
7b |
The SS does not respond to the LPP REQUEST ASSISTANCE DATA message. |
||||
8 |
The requested posSIBs that includes the needed posSystemInformation are broadcasted. |
<– |
RRC: SYSTEM INFORMATION (BCCH) |
||
9 |
Check: Does the UE send an LPP message of type Provide Location Information including location estimate? |
–> |
ULInformationTransfer (LPP PROVIDE LOCATION INFORMATION) |
2 |
P |
10 |
IF the UE LPP message at step 9 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
9.4.3.3.3 Specific message contents
Table 9.4.3.3.3-1: RESET UE POSITIONING STORED INFORMATION (Preamble)
Derivation Path: 38.509 clause 6.6 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
UE Positioning Technology |
Sub-test 20: 0 0 0 0 1 0 0 0 Sub-test 21: 0 0 0 0 0 1 1 1 Sub-test 23: 0 0 0 0 0 0 1 0 Sub-test 24: 0 0 0 0 0 1 0 1 Sub-test 25: 0 0 0 0 0 0 0 0 |
Sub-test 20: DL-AoD Sub-test 21: DL-TDOA Sub-test 23: MBS Sub-test 24: Sensor Sub-test 25: GNSS |
Table 9.4.3.3.3-2: SIB1 (Preamble)
Derivation Path: TS 38.508-1, Table 4.6.1-28 with condition posSIB. |
Table 9.4.3.3.3-3: PosSI-SchedulingInfo (SIB1, Table 9.4.3.3.3-2)
Derivation Path: TS 38.508-1, Table 4.6.2a-2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PosSI-SchedulingInfo-r16 ::= SEQUENCE { |
||||
posSchedulingInfoList-r16 SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16 { |
2 entries |
The size of PosSchedulingInfo-r16 is 1 for Sub-tests 20, 21, 23 and 24. If Sub-test 25 and UE supports X GNSS systems, the size of PosSchedulingInfo-r16 is (X+1) and the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
||
PosSchedulingInfo-r16[1] SEQUENCE { |
entry 1 |
|||
offsetToSI-Used-r16 |
Not present |
|||
posSI-Periodicity-r16 |
rf32 |
|||
posSI-BroadcastStatus-r16 |
notBroadcasting |
|||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
3 entries for Sub-test 25, 1 entry for Sub-tests 20, 21, 23 and 24 |
PosSibType-n = posSibType1-1, posSibType1-2, posSibType1-3 |
Sub-test 25 |
|
PosSibType-n = posSibType4-1 |
Sub-test 24 |
|||
PosSibType-n = posSibType5-1 |
Sub-test 23 |
|||
PosSibType-n = posSibType6-1 |
Sub-test 20 or Sub-test 21 |
|||
PosSIB-Type-r16[n] SEQUENCE { |
entry n |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Not present |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-n |
The posSibType-r16 is depending on the sub–test cases and entry number n |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
PosSchedulingInfo-r16[2] SEQUENCE { |
entry 2 If the UE supports X GNSS systems, the PosSchedulingInfo-r16 needs to be broadcasted X times, once for each different GNSS. |
Sub-test 25 |
||
offsetToSI-Used-r16 |
Not present |
|||
posSI-Periodicity-r16 |
rf32 |
|||
posSI-BroadcastStatus-r16 |
notBroadcasting |
|||
posSIB-MappingInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 { |
6 entries for Sub-test 25 |
posSibType2-1, posSibType2-3, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9 |
||
PosSIB-Type-r16[m] SEQUENCE { |
entry m |
|||
encrypted-r16 |
Not present |
|||
gnss-id-r16 |
Set depending on the GNSS supported by the UE |
|||
sbas-id-r16 |
Not present |
|||
posSibType-r16 |
PosSibType-m, |
The posSibType-r16 is depending on the entry number m |
||
areaScope-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-4: RRCReconfiguration (Preamble, step 7 as defined in TS 38.508-1 [30] Table 4.5.4.2-3)
Derivation Path: TS 38.331 [6], clause 6.2.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
RRC-TransactionIdentifier |
|||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
onDemandSIB-Request-r16 CHOICE SEQUENCE { |
||||
setup SEQUENCE { |
||||
onDemandSIB-RequestProhibitTimer-r16 |
s5 |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-5: DLInformationTransfer (step 2, step 4, step 5 and step 10, Table 9.4.3.3.2-3)
Derivation Path: 38.331 clause 6.2.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DLInformationTransfer ::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
||||
criticalExtensions CHOICE { |
||||
dlInformationTransfer SEQUENCE { |
||||
dedicatedNAS-Message OCTET STRING |
Set according to Table 9.4.3.3.3-6 |
DL NAS TRANSPORT |
||
nonCriticalExtension SEQUENCE {} |
Not present |
|||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-6: DL NAS TRANSPORT (DLInformationTransfer, Table 9.4.3.3.3-4)
Derivation Path: 24.501 Table 8.2.11.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Extended Protocol discriminator |
01111110 |
5GS mobility management messages |
||
Security header type |
0000 |
Plain 5GS NAS message |
||
Spare half octet |
0000 |
Downlink generic NAS transport |
||
DL NAS TRANSPORT message identity |
01101000 |
DL NAS transport |
||
Payload container type |
0011 |
LTE Positioning Protocol (LPP) message container |
||
Spare half octet |
0000 |
|||
Payload container |
Step 2: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
Step 5: Set according to Table 9.4.3.3.3-7 |
LPP Request Location Information |
|||
Steps 4 and 10: Set according to Table 9.4.3.3.3-8 |
LPP Acknowledgement |
|||
Additional information |
Present |
Routing Identifier/Correlation ID |
Table 9.4.3.3.3-7: LPP Request Location Information (DL NAS TRANSPORT, Table 9.4.3.3.3-5)
Derivation Path: Table 8.4-3 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-3 with the following exceptions: |
||||
locationInformationType |
locationMeasurementsPreferred |
Table 9.4.3.3.3-8: LPP Acknowledgement (DL NAS TRANSPORT, Table 9.4.3.3.3-5)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID |
Not present |
|||
endTransaction |
TRUE |
|||
sequenceNumber |
Not present |
|||
acknowledgement SEQUENCE { |
||||
ackRequested |
FALSE |
|||
ackIndicator |
(0..255) |
Contains the same value of the sequenceNumber field in step 3 or 9, Table 9.4.3.3.2- |
||
} |
||||
lpp-MessageBody |
Not present. |
|||
} |
Table 9.4.3.3.3-9: DedicatedSIBRequest (step 6, Table 9.4.3.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-2A |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
DedicatedSIBRequest-r16 ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
dedicatedSIBRequest-r16 SEQUENCE { |
||||
onDemandSIB-RequestList-r16 SEQUENCE { |
||||
requestedSIB-List-r16 |
Not checked |
|||
requestedPosSIB-List-r16 SEQUENCE (SIZE (1..maxOnDemandPosSIB-r16)) OF PosSIB-ReqInfo-r16 { |
1 entry for Sub-tests 20, 21, 23 and 24; 9 entries for Sub-test 25 |
The size of PosSIB-ReqInfo-r16 is 1 for Sub-tests 20, 21, 23 and 24. If Sub-test 25 and UE supporting X GNSS systems, the size of PosSIB-ReqInfo-r16 is (6X+3). |
||
PosSIB-ReqInfo-r16[n] SEQUENCE { |
entry n |
|||
gnss-id-r16 |
Not present |
Sub-test 25 posSibType2-x |
||
Set depending on the GNSS supported by the UE |
Sub-test 25 posSibType2-x |
|||
sbas-id-r16 |
Not checked |
|||
posSibType-r16 |
PosSibType-n |
PosSibType-n = posSibType1-1, posSibType1-2, posSibType1-3, posSibType2-1, posSibType2-3, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9 |
Sub-test 25 |
|
PosSibType-n = posSibType4-1 |
Sub-test 24 |
|||
PosSibType-n = posSibType5-1 |
Sub-test 23 |
|||
PosSibType-n = posSibType6-1 |
Sub-test 20 or Sub-test 21 |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-10: ULInformationTransfer (steps 3, 7a and 9, Table 9.4.3.3.2-3)
Derivation Path: 38.331 clause 6.2.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
ULInformationTransfer ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
ulInformationTransfer SEQUENCE { |
||||
dedicatedNAS-Message OCTET STRING |
Set according to Table 9.4.3.3.3-11 |
UL NAS TRANSPORT |
||
nonCriticalExtension SEQUENCE {} |
Not present |
|||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-11: UL NAS TRANSPORT (ULInformationTransfer, Table 9.4.3.3.3-10)
Derivation Path: 24.501 Table 8.2.10.1.1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
Extended Protocol discriminator |
01111110 |
5GS mobility management messages |
||
Security header type |
0000 |
Plain 5GS NAS message |
||
Spare half octet |
0000 |
|||
UL NAS TRANSPORT message identity |
01100111 |
UL NAS TRANSPORT |
||
Payload container type |
0011 |
LTE Positioning Protocol (LPP) message container |
||
Spare half octet |
0000 |
|||
Payload container |
Step 3: Set according to Table 9.4.3.3.3-12 |
LPP Provide Capabilities |
||
Step 7a: Set according to Table 9.4.3.3.3-13 |
LPP Request Assistance Data |
|||
Step 9: Set according to Table 9.4.3.3.3-14 |
LPP Provide Location Information |
|||
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 2 Table Table 9.4.3.3.2-3) |
Table 9.4.3.3.3-12: LPP Provide Capabilities (UL NAS TRANSPORT, Table 9.4.3.3.3-11)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
locationServer |
|||
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in the LPP Request Capabilities message in step 12, Table 9.4.1.3.2-3 |
||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement SEQUENCE { |
Present, or not present |
|||
ackRequested |
TRUE |
|||
ackIndicator |
Not present |
|||
} |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideCapabilities SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideCapabilities-r9 SEQUENCE { |
||||
commonIEsProvideCapabilities |
Dependent on UE capabilities |
Rel-14 onwards |
||
a-gnss-ProvideCapabilities |
Dependent on UE capabilities |
|||
sensor-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-16 onwards |
||
tbs-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-16 onwards |
||
nr-DL-AoD-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
nr-DL-TDOA-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-13: LPP Request Assistance Data (UL NAS TRANSPORT, Table 9.4.3.3.3-11)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
targetDevice |
|||
transactionNumber |
(0..255) |
|||
} |
||||
endTransaction |
FALSE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement SEQUENCE { |
Present or not present |
|||
ackRequested |
TRUE |
|||
ackIndicator |
Not present |
|||
} |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
requestAssistanceData SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
requestAssistanceData-r9 SEQUENCE { |
||||
commonIEsRequestAssistanceData |
Present or not present |
|||
a-gnss-RequestAssistanceData |
Present for sub-test 25 |
Rel-15 onwards |
||
otdoa-RequestAssistanceData |
Not present |
|||
epdu-RequestAssistanceData |
Not present |
|||
sensor-RequestAssistanceData-r14 |
Present for sub-test 24 |
Rel-16 onwards |
||
tbs-RequestAssistanceData-r14 |
Present for sub-test 23 |
Rel-16 onwards |
||
wlan-RequestAssistanceData-r14 |
Not present |
|||
nr-Multi-RTT-RequestAssistanceData-r16 |
Not present |
|||
nr-DL-AoD-RequestAssistanceData-r16 |
Present for sub-test 20 |
Rel-16 onwards |
||
nr-DL-TDOA-RequestAssistanceData-r16 |
Present for sub-test 21 |
Rel-16 onwards |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-14: LPP Provide Location Information (UL NAS TRANSPORT, Table 9.4.3.3.3-11)
Derivation Path: 37.355 clause 6.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
LPP-Message ::= SEQUENCE { |
||||
transactionID SEQUENCE { |
||||
initiator |
locationServer |
|||
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in LPP Request Location Information message in step 15, Table 9.4.1.3.2-3 |
||
} |
||||
endTransaction |
TRUE |
|||
sequenceNumber |
(0..255) |
|||
acknowledgement SEQUENCE { |
present, or not present |
|||
ackRequested |
TRUE |
|||
ackIndicator |
Not present |
|||
} |
||||
lpp-MessageBody CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
c1 CHOICE { |
||||
provideLocationInformation-r9 SEQUENCE { |
||||
commonIEsProvideLocationInformation |
May be present. Any value acceptable |
|||
a-gnss-ProvideLocationInformation SEQUENCE { |
Present for sub-test 25 |
|||
gnss-SignalMeasurementInformation |
Present. Any value acceptable |
|||
gnss-LocationInformation |
May be present |
|||
gnss-Error |
Not present |
|||
} |
||||
sensor-ProvideLocationInformation-r13 SEQUENCE { |
Present for sub-test 24 |
Rel-16 onwards |
||
sensor-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
sensor-Error-r13 |
Not present |
|||
sensor-MotionInformation-r15 |
May be present |
|||
} |
||||
tbs-ProvideLocationInformation-r13 SEQUENCE { |
Present for sub-test 23 |
Rel-16 onwards |
||
tbs-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
tbs-Error-r13 |
Not present |
|||
} |
||||
nr-DL-AoD-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 20 |
Rel-16 onwards |
||
nr-DL-AoD-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
nr-DL-AoD-Error-r16 |
Not present |
|||
} |
||||
nr-DL-TDOA-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 21 |
Rel-16 onwards |
||
nr-DL-TDOA-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
nr-DL-TDOA-Error-r16 |
Not present |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 9.4.3.3.3-15: SystemInformation – Sub-tests 20, 21, 23 and 24 (step 8, Table 9.4.3.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB. |
Table 9.4.3.3.3-16: SystemInformation – Sub-test 25, message 1 (step 8, Table 9.4.3.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB and posSib1-x. |
Table 9.4.3.3.3-17: SystemInformation – Sub-test 25, message 2 (step 8, Table 9.4.3.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.1-29 with condition posSIB and posSib2-x. |
Table 9.4.3.3.3-18: PosSystemInformation-r16-IEs (step 8, Table 9.4.3.3.2-3)
Derivation Path: TS 38.508-1, Table 4.6.2a-1 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PosSystemInformation-r16-IEs ::= SEQUENCE { |
||||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
3 entries |
Sub-test 25 posSib1-x |
||
posSib1-1-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 1 |
||
posSib1-2-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 2 |
||
posSib1-3-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 3 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
6 entries |
Sub-test 25, posSib2-x |
||
posSib2-1-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 1 |
||
posSib2-3-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 2 |
||
posSib2-6-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 3 |
||
posSib2-7-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 4 |
||
posSib2-8-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 5 |
||
posSib2-9-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 6 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 24 |
||
posSib4-1-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 1 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 23 |
||
posSib5-1-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 1 |
||
posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { |
1 entry |
Sub-test 20, Sub-test 21 |
||
posSib6-1-r16 |
SIBpos as defined in Table 9.4.3.3.3-19 |
entry 1 |
||
} |
||||
lateNonCriticalExtension |
Not present |
|||
nonCriticalExtension |
Not present |
|||
} |
Table 9.4.3.3.3-19: SIBpos (PosSystemInformation-r16-IEs, Table 9.4.3.3.3-18)
Derivation Path: TS 38.508-1, Table 4.6.2a-3 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SIBpos-r16 ::= SEQUENCE { |
||||
assistanceDataSIB-Element-r16 |
OCTET STRING containing AssistanceDataSIBelement |
|||
} |
Table 9.4.3.3.3-20: AssistanceDataSIBelement
Derivation Path: TS 37.355, clause 7.4.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
AssistanceDataSIBelement-r15 ::= SEQUENCE { |
||||
valueTag-r15 |
Not present |
|||
expirationTime-r15 |
Not present |
|||
cipheringKeyData-r15 |
Not present |
|||
segmentationInfo-r15 |
Not present |
Not present when the posSIB is not segmented |
||
segmentationInfo-r15 SEQUENCE { |
Present when the posSIB is segmented |
|||
segmentationOption-r15 |
octet-string-seg |
|||
assistanceDataSegmentType-r15 |
notLastSegment |
Used when posSIB is segmented and the segment is not the last segment |
||
lastSegment |
Used when posSIB is not segmented, or posSIB is segmented and the segment is the last segment |
|||
assistanceDataSegmentNumber-r15 |
index of the segmented posSIB |
|||
} |
||||
assistanceDataElement-r15 |
OCTET STRING containing LPP IEs (GNSS-ReferenceTime, GNSS-ReferenceLocation, GNSS-IonosphericModel,GNSS-TimeModelList, GNSS-NavigationModel, GNSS-AcquisitionAssistance, GNSS-Almanac, GNSS-UTC-Model, GNSS-AuxiliaryInformation ) as defined in TS 37.571-5 [12] and mapped according to the content of posSibType-r16 in Table 9.4.1.3.3-3. |
Sub-test 25 |
||
OCTET STRING containing sensor-AssistanceDataList as defined in Table 8.4-1 |
Sub-test 24 |
|||
OCTET STRING containing tbs-AssistanceDataList as defined in Table 8.4-1 |
Sub-test 23 |
|||
OCTET STRING containing NR-DL-PRS-AssistanceData as defined in Table 8.4.1.6-1. |
Sub-test 20, Sub-test 21 |
|||
} |
Annex A (informative):
Change history
Change history |
|||||||
---|---|---|---|---|---|---|---|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
36.571-2 |
|||||||
2010-08 |
R5#48 |
R5-104119 |
Initial skeleton proposal |
0.0.0 |
|||
R5#48 |
R5-104741 |
Merge of documents R5-104119, R5-104120, R5-104121, R5-104122, together with small editorial modifications |
0.0.0 |
0.0.1 |
|||
2011-02 |
R5#50 |
R5-110250 |
Various corrections based on LPP v9.3.0 (R5-106431) |
0.0.1 |
|||
New test cases: LPP Reliable Transport (R5-106433) |
|||||||
New test cases: CS fallback (R5-106698) |
0.1.0 |
||||||
2011-05 |
R5#51 |
R5-112388 |
Various corrections (R5-110251) |
0.1.0 |
|||
OTDOA default conditions (R5-110252) |
0.2.0 |
||||||
2011-08 |
R5#52 |
R5-113770 |
Small corrections to 36.571-2 baseline text |
0.2.0 |
|||
R5-113771 |
Addition of LPP abort test case |
||||||
R5-113147 |
Addition of Position Capability Transfer test case |
||||||
R5-113140 |
Addition of Notification test cases |
||||||
R5-113769 |
Addition of UE Network Capability test case |
||||||
R5-113847 |
Addition of LPP Error handling test cases |
1.0.0 |
|||||
37.571-2 |
|||||||
2011-11 |
R5#53 |
R5-115249 |
Creation of 37.571-2 based on 36.571-2 v1.0.0 and 34.123-1 v9.6.0 |
1.0.0 |
|||
R5-115250 |
Default conditions for ECID signalling test cases in 37.571-2 baseline text |
||||||
R5-115251 |
Various corrections to the 37.571-2 baseline text |
||||||
R5-115252 |
Default system information for UTRAN A-GNSS tests in 37.571-2 baseline text |
2.0.0 |
|||||
2011-12 |
RAN#54 |
– |
– |
– |
Moved to Rel-9 with editorial changes only. |
2.0.0 |
9.0.0 |
2012-03 |
RAN#55 |
R5-120358 |
0001 |
– |
Addition of missing test case 7.3.4.1 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120359 |
0002 |
– |
Addition of missing test case 7.3.4.2 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120360 |
0003 |
– |
Addition of missing test case 7.3.4.3 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120361 |
0004 |
– |
Addition of missing test case 7.3.4.4 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120362 |
0005 |
– |
Editorial corrections to 37.571-2 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120363 |
0006 |
– |
Completion of Test Case 7.3.1.1 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120364 |
0007 |
– |
Removal of FFS for Sub-test -7 |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120395 |
0008 |
– |
Addition of RESET command to EPC MO-LR tests |
9.0.0 |
9.1.0 |
2012-03 |
RAN#55 |
R5-120725 |
0009 |
– |
Correction of MO-LR CS fallback test cases 7.4.1 |
9.0.0 |
9.1.0 |
2012-06 |
RAN#56 |
R5-121134 |
0010 |
– |
Clarification to cell synchronization for OTDOA |
9.1.0 |
9.2.0 |
2012-06 |
RAN#56 |
R5-121148 |
0011 |
– |
Completion of Test Case 7.3.1.1 |
9.1.0 |
9.2.0 |
2012-06 |
RAN#56 |
– |
– |
– |
Upgrade to v10.0.0 with no change. |
9.2.0 |
10.0.0 |
2012-09 |
RAN#57 |
R5-123067 |
0012 |
– |
Removal of FFS for Sub-test-7 |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123068 |
0013 |
– |
Correction of references to clauses in 37.571-5 |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123070 |
0014 |
– |
Editorial Corrections |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123071 |
0015 |
– |
Correction of MO-LR CS fallback test cases 7.4.1 |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123072 |
0016 |
– |
Correction to UE Network Capability Test Procedure |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123073 |
0017 |
– |
Correction to Register and Facility message type content |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123074 |
0018 |
– |
Addition of RESET command to EPC MO-LR tests |
10.0.0 |
10.1.0 |
2012-09 |
RAN#57 |
R5-123698 |
0019 |
– |
Small corrections to default E-UTRAN message contents |
10.0.0 |
10.1.0 |
2013-03 |
RAN#59 |
R5-130112 |
0021 |
– |
Correction to LPP Request Location Information Message Content for TC 7.3.4.4 |
10.1.0 |
10.2.0 |
2013-03 |
RAN#59 |
R5-130593 |
0022 |
– |
Correction of applicability for TC 7.3.2.3 |
10.1.0 |
10.2.0 |
2013-06 |
RAN#60 |
R5-131099 |
0023 |
– |
Clarification of IE values |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131100 |
0024 |
– |
Correction of behaviour in 7.3.2.3 |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131101 |
0025 |
– |
Simplification of test set-up for OTDOA and ECID tests |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131306 |
0026 |
– |
Correction to LTE UE Positioning test cases |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131326 |
0027 |
– |
Correction to available GNSS assistance data elements |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131877 |
0028 |
– |
Clarification of Sub-Test Case Numbers Tables |
10.2.0 |
10.3.0 |
2013-06 |
RAN#60 |
R5-131878 |
0029 |
– |
New test case for inter-frequency RSTD measurement indication procedure |
10.2.0 |
10.3.0 |
2013-09 |
RAN#61 |
R5-133175 |
0030 |
– |
Clarifications to 7.3.3.1 |
10.3.0 |
10.4.0 |
2013-12 |
RAN#62 |
R5-134907 |
0031 |
– |
Addition of missing IEs from otdoa-ProvideCapabilities in 7.3.1.1 |
10.4.0 |
10.5.0 |
2013-12 |
RAN#62 |
R5-134908 |
0032 |
– |
Change Applicability of test 7.3.5.1 |
10.4.0 |
10.5.0 |
2013-12 |
RAN#62 |
R5-134909 |
0033 |
– |
Addition of Capability exchange in various clause 7 tests |
10.4.0 |
10.5.0 |
2013-12 |
RAN#62 |
R5-134910 |
0034 |
– |
Clarification of Provide Capabilities content for test 7.2.2.2 |
10.4.0 |
10.5.0 |
2014-03 |
RAN#63 |
R5-140133 |
0035 |
– |
Add Assistance Data delivery to test 7.3.5.1 |
10.5.0 |
10.6.0 |
2014-03 |
RAN#63 |
R5-140606 |
0036 |
– |
Correction to LTE UE Positioning test case 7.2.1.2 |
10.5.0 |
10.6.0 |
2014-03 |
RAN#63 |
R5-140608 |
0037 |
– |
Correction to LTE UE Positioning test case 7.2.1.3 |
10.5.0 |
10.6.0 |
2014-03 |
RAN#63 |
R5-140793 |
0038 |
– |
Correction to message content for inter-frequency RSTD measurement indication test case |
10.5.0 |
10.6.0 |
2014-06 |
RAN#64 |
R5-142251 |
0039 |
– |
Clarification of use of satellite simulator |
10.6.0 |
10.7.0 |
2014-06 |
RAN#64 |
R5-142886 |
0040 |
– |
Correction to EUTRA UE Positioning test cases 7.3.4.x |
10.6.0 |
10.7.0 |
2014-09 |
RAN#65 |
R5-144194 |
0041 |
– |
Clarification for configuration of cell 1 in OTDOA tests |
10.7.0 |
10.8.0 |
2014-09 |
RAN#65 |
R5-144195 |
0042 |
– |
RESET Positioning Information in LPP Abort Procedures |
10.7.0 |
10.8.0 |
2014-09 |
RAN#65 |
R5-144237 |
0043 |
– |
Adding extra neighbour cells to 7.3.5.1 |
10.7.0 |
10.8.0 |
2014-09 |
RAN#65 |
R5-144626 |
0044 |
– |
Correct OTDOA and ECID Elements in 7.3.4.2 and 7.3.4.4 |
10.7.0 |
10.8.0 |
2014-09 |
RAN#65 |
R5-144702 |
0045 |
– |
Correction to test case 7.5.1, Table 7.5.1.3.2-1: Main behaviour |
10.7.0 |
10.8.0 |
2014-09 |
RAN#65 |
R5-144703 |
0046 |
– |
Updates OTDOA Neighbour Cell Info List |
10.7.0 |
10.8.0 |
2014-12 |
RAN#66 |
R5-145137 |
0047 |
– |
Clarification to OTDOA Assistance Data |
10.8.0 |
10.9.0 |
2014-12 |
RAN#66 |
R5-145347 |
0048 |
– |
Addition of Galileo in test 7.3.3 |
10.8.0 |
10.9.0 |
2014-12 |
RAN#66 |
R5-145736 |
0049 |
– |
Correction to OTDOA related default message contents in LPP common procedure for Position Capability Transfer |
10.8.0 |
10.9.0 |
2014-12 |
RAN#66 |
– |
– |
– |
Raised to v 11.0.0 with no change |
10.9.0 |
11.0.0 |
2014-12 |
RAN#66 |
R5-145737 |
0050 |
– |
Addition of Beidou |
11.0.0 |
12.0.0 |
2015-03 |
RAN#67 |
R5-150741 |
0051 |
– |
Abbreviation Corrections for BDS in 37.571-2 |
12.0.0 |
12.1.0 |
2015-06 |
RAN#68 |
R5-151109 |
0054 |
– |
IMS settings for LTE Positioning test cases |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-151981 |
0053 |
1 |
Correction of prs-ConfigurationIndex for TDD |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-151982 |
0055 |
1 |
LPP updates and corrections |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-151983 |
0056 |
1 |
Update of default GNSS Assistance Data Elements |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-151984 |
0057 |
1 |
Correction to EUTRA UE Positioning test case 7.3.3.1 |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-152147 |
0058 |
1 |
Correction to EUTRA UE Positioning test cases covering the UE-assisted case |
12.1.0 |
12.2.0 |
2015-06 |
RAN#68 |
R5-152149 |
0052 |
2 |
Addition of "early fix" to A-GNSS tests |
12.1.0 |
12.2.0 |
2015-09 |
RAN#69 |
R5-153110 |
0059 |
– |
Correction to GANSS Multi-frequency Measurement Requested IE |
12.2.0 |
12.3.0 |
2015-09 |
RAN#69 |
R5-153111 |
0060 |
– |
Corrections to MEASUREMENT CONTROL messages |
12.2.0 |
12.3.0 |
2015-09 |
RAN#69 |
R5-153153 |
0061 |
– |
Missing " earlyFixReport-r12 " in Table 7.2.2.2.3.3-13 |
12.2.0 |
12.3.0 |
2015-09 |
RAN#69 |
– |
– |
– |
update of the "non-specific references" in section 2 according to the approved R5-153582 and an action point on ETSI MCC |
12.2.0 |
12.3.0 |
2015-12 |
RAN#70 |
R5-155101 |
0064 |
– |
Correction to use of Modernized GPS with BDS |
12.3.0 |
12.4.0 |
2016-03 |
RAN#71 |
R5-160354 |
0067 |
– |
Addition of extra call flow to test case 7.3.4.4 |
12.4.0 |
12.5.0 |
2016-09 |
RAN#73 |
R5-165993 |
0069 |
1 |
Add missing references to GPS and Galileo and A-GPS and A-Galileo |
12.5.0 |
12.6.0 |
2016-09 |
RAN#73 |
R5-165996 |
0070 |
1 |
Addition of Indoor Positioning Protocol Conformance Testing (MBS) |
12.6.0 |
13.0.0 |
2016-12 |
RAN#74 |
R5-168065 |
0071 |
– |
Change of applicability of ECID tests for TDD |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-168461 |
0073 |
– |
Missing Satellite signal sub-test case reference |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-168463 |
0075 |
– |
Incorrect Procedure Step referenced for Main behaviour Table |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-169094 |
0074 |
1 |
Correction in Table 7.3.4.4.3.3-11 for sub test 6 |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-169100 |
0072 |
1 |
Addition of TC 7.3.3.1A |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-169101 |
0076 |
1 |
Add WLAN signalling sub-test and references for Indoor Positioning |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-169102 |
0077 |
1 |
Add BT signalling sub-test and references for Indoor Positioning |
13.0.0 |
13.1.0 |
2016-12 |
RAN#74 |
R5-169103 |
0078 |
1 |
Add Sensor signalling sub-test and references for Indoor Positioning |
13.0.0 |
13.1.0 |
2017-03 |
RAN#75 |
R5-170736 |
0079 |
– |
Remove Bluetooth Abbreviations and Add Missing References for WLAN |
13.1.0 |
13.2.0 |
2017-03 |
RAN#75 |
– |
– |
– |
Administrative release upgrade to match the release of 3GPP TS 37.571-1 which was upgraded at RAN#74 to Rel-14 due to Rel-14 relevant CR(s) |
13.2.0 |
14.0.0 |
2017-06 |
RAN#76 |
R5-172963 |
0082 |
1 |
Merge GNSS sub-tests into one sub-test |
14.0.0 |
14.1.0 |
2017-06 |
RAN#76 |
R5-172964 |
0084 |
1 |
Correction to tbs-ProvideCapabilities in several tables |
14.0.0 |
14.1.0 |
2017-06 |
RAN#76 |
R5-172967 |
0083 |
1 |
Introduction of MBS Assistance Data Signalling Sub-test 16 |
14.0.0 |
14.1.0 |
2017-09 |
RAN#77 |
R5-173685 |
0086 |
– |
Editorial changes for Release 14 alignment with core specification |
14.1.0 |
14.2.0 |
2017-09 |
RAN#77 |
R5-173922 |
0089 |
– |
Clarifications to test 7.2.2.1 for UEs that support more than one positioning technology |
14.1.0 |
14.2.0 |
2017-09 |
RAN#77 |
R5-174060 |
0091 |
– |
Editorial change to remove referenced text for ‘signals switched off or not present’ in Section 7 |
14.1.0 |
14.2.0 |
2017-09 |
RAN#77 |
R5-174582 |
0087 |
1 |
Correction to Inter-frequency RSTD measurement indication test cases 7.5.1 to support Band > 64 |
14.1.0 |
14.2.0 |
2017-09 |
RAN#77 |
R5-174583 |
0090 |
1 |
Editorial change to correct typos and missing Information Elements in tables |
14.1.0 |
14.2.0 |
2017-09 |
RAN#77 |
R5-174585 |
0088 |
1 |
Editorial change to correct IEs |
14.1.0 |
14.2.0 |
2017-12 |
RAN#78 |
R5-176088 |
0092 |
– |
Correction to LPP ProvideAssistanceData for UE Based MBS |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
R5-176569 |
0093 |
– |
Addition of Rel-14 WLAN Positioning Protocol Tests and Sub-Tests |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
R5-176570 |
0094 |
– |
Addition of Rel-14 Sensor Positioning Protocol Tests and Sub-Tests |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
R5-176574 |
0095 |
– |
Correction for UE Assisted TBS Request Location Information Table |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
R5-176576 |
0096 |
– |
Deletion of Duplicated IEs in Table 5.4.1.3-2 |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
R5-177039 |
0097 |
1 |
Editorial change to correct typos, grammar, descriptive text in table content, missing references and formatting issues |
14.2.0 |
14.3.0 |
2017-12 |
RAN#78 |
– |
– |
– |
Administrative release upgrade to match the release of 3GPP TS 37.571-1 which was upgraded at RAN#78 to Rel-15 due to Rel-15 relevant CR(s) |
14.3.0 |
15.0.0 |
2018-03 |
RAN#79 |
R5-181111 |
0102 |
– |
Update Main Behaviour positioning method |
15.0.0 |
15.1.0 |
2018-03 |
RAN#79 |
R5-181112 |
0103 |
– |
Missing Release 14 Information Element for otdoa |
15.0.0 |
15.1.0 |
2018-03 |
RAN#79 |
R5-181113 |
0104 |
– |
Update Simulated Environment conditions for MBS, WLAN, and Bluetooth |
15.0.0 |
15.1.0 |
2018-06 |
RAN#80 |
R5-182957 |
0106 |
– |
Correction to UE Positioning TCs 7.2.2.1 + 7.2.2.2 |
15.1.0 |
15.2.0 |
2018-06 |
RAN#80 |
R5-183169 |
0105 |
1 |
Addition of Rel-14 LPP message segmentation IEs into Capabilities messages |
15.1.0 |
15.2.0 |
2018-09 |
RAN#81 |
R5-184037 |
0108 |
– |
Addition of PICS for support of LPP message segmentation in test 7.3.1.1 |
15.2.0 |
15.3.0 |
2018-12 |
RAN#82 |
R5-186618 |
0109 |
– |
Addition of NR background information |
15.3.0 |
15.4.0 |
2018-12 |
RAN#82 |
R5-186695 |
0110 |
– |
Addition of Rel-12 missing IEs to LPP message contents |
15.3.0 |
15.4.0 |
2018-12 |
RAN#82 |
R5-186696 |
0111 |
– |
Addition of Rel-15 missing IEs to LPP message contents |
15.3.0 |
15.4.0 |
2018-12 |
RAN#82 |
R5-187726 |
0112 |
1 |
Positioning NSA Protocol tests – LPP Procedures |
15.3.0 |
15.4.0 |
2019-03 |
RAN#83 |
R5-192382 |
0113 |
1 |
Addition NR SA positioning tests and removal of NSA |
15.4.0 |
15.5.0 |
2019-03 |
RAN#83 |
– |
– |
– |
Administrative release upgrade to match the release of TS 37.571-1 which was upgraded at RAN#83 to Rel-16 due to a Rel-16 relevant CR |
15.5.0 |
16.0.0 |
2019-06 |
RAN#84 |
R5-195201 |
0119 |
– |
Addition of information for test environments for NR |
16.0.0 |
16.1.0 |
2019-06 |
RAN#84 |
R5-195203 |
0118 |
1 |
Clean Up of NR Positioning Test Cases |
16.0.0 |
16.1.0 |
2019-09 |
RAN#85 |
R5-197164 |
0124 |
1 |
Correction to Testcases 7.2.2.2, 7.3.4.2 and 7.3.4.4 |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197166 |
0120 |
1 |
Addition of sub-test information for NR tests |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197167 |
0121 |
1 |
Alignment of NR terminology |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197168 |
0122 |
1 |
Complete positioning protocol tests for NR |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197169 |
0123 |
1 |
Add default conditions for FR2 positioning tests |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197170 |
0125 |
1 |
Clean Up of NR Positioning Test Cases |
16.1.0 |
16.2.0 |
2019-09 |
RAN#85 |
R5-197175 |
0126 |
– |
Missing Values from Request Assistance Data Table |
16.1.0 |
16.2.0 |
2019-12 |
RAN#86 |
R5-198966 |
0127 |
1 |
Additional test coverage for multi-frequency GNSS test cases |
16.2.0 |
16.3.0 |
2019-12 |
RAN#86 |
R5-198967 |
0128 |
1 |
Update to protocol positioning tests |
16.2.0 |
16.3.0 |
2020-03 |
RAN#87 |
R5-201010 |
0131 |
1 |
ECID test cases deleted for NR Test Configuration B up to and including LPP Rel-15 |
16.3.0 |
16.4.0 |
2020-03 |
RAN#87 |
R5-201012 |
0129 |
1 |
Editorial changes to TS 37.571-X titles to remove references to individual RATs |
16.3.0 |
16.4.0 |
2020-06 |
RAN#88 |
R5-203511 |
0133 |
– |
Correction of WLAN Assistance Data Element referenced clause |
16.4.0 |
16.5.0 |
2020-06 |
RAN#88 |
R5-204489 |
0132 |
1 |
Adding measurement gaps for OTDOA configuration |
16.4.0 |
16.5.0 |
2020-06 |
RAN#88 |
R5-204532 |
0134 |
1 |
Addition of OTDOA information for pre-test conditions for test 9.3.3.1B |
16.4.0 |
16.5.0 |
2020-12 |
RAN#90 |
R5-205211 |
0136 |
– |
Addition of miscellaneous Release 16 fields to tables in test case 7.3.1.1 |
16.5.0 |
16.6.0 |
2020-12 |
RAN#90 |
R5-205667 |
0139 |
– |
Clarification of configuration of measurement gaps for OTDOA in NR tests |
16.5.0 |
16.6.0 |
2020-12 |
RAN#90 |
R5-206424 |
0137 |
1 |
Addition of BDS B1C Signal test contents in TS 37.571-2 |
16.5.0 |
16.6.0 |
2020-12 |
RAN#90 |
R5-206442 |
0135 |
1 |
Deletion of tests 7.3.3.1, 7.3.3.1A, 9.3.3.1 and 9.3.3.1A |
16.5.0 |
16.6.0 |
2020-12 |
RAN#90 |
R5-206443 |
0138 |
1 |
Corrections to LPP Provide Assistance Data for NR test cases in clause 9 |
16.5.0 |
16.6.0 |
2021-03 |
RAN#91 |
R5-210258 |
0140 |
– |
Definition of values for epdu fields |
16.6.0 |
16.7.0 |
2021-03 |
RAN#91 |
R5-210260 |
0141 |
– |
Corrections and clarifications to default MBS, WLAN and Sensor assistance data in clause 5.4.1 |
16.6.0 |
16.7.0 |
2021-03 |
RAN#91 |
R5-211298 |
0142 |
– |
Corrections for support of multiple GPS signals |
16.6.0 |
16.7.0 |
2021-06 |
RAN#92 |
R5-213638 |
0144 |
1 |
Addition of NR Rel 16 positioning methods information into protocol conformance test cases for NR |
16.7.0 |
16.8.0 |
2021-06 |
RAN#92 |
R5-213639 |
0145 |
1 |
Addition of NR Rel 16 positioning methods into default conditions for NR |
16.7.0 |
16.8.0 |
2021-09 |
RAN#93 |
R5-215154 |
0149 |
– |
Clarifications for OTDOA (LTE) test cases for NR |
16.8.0 |
16.9.0 |
2021-09 |
RAN#93 |
R5-215616 |
0151 |
– |
Clarification text on LCS Sub-Test Cases |
16.8.0 |
16.9.0 |
2021-09 |
RAN#93 |
R5-216322 |
0147 |
1 |
Correction to NR positioning method information in Position Capability Transfer test case |
16.8.0 |
16.9.0 |
2021-09 |
RAN#93 |
R5-216323 |
0148 |
1 |
Addition of assistance data information elements for Multi-RTT, DL-AoD and DL-TDOA positioning methods |
16.8.0 |
16.9.0 |
2021-12 |
RAN#94 |
R5-217127 |
0155 |
– |
Correction to pre-test conditions for NR DL-TDOA UE-Based test cases |
16.9.0 |
16.10.0 |
2021-12 |
RAN#94 |
R5-217936 |
0152 |
1 |
Addition of RESET UE POSITIONING STORED INFORMATION message contents |
16.9.0 |
16.10.0 |
2021-12 |
RAN#94 |
R5-217937 |
0153 |
1 |
Correction of the test steps for Multi-RTT sub-tests |
16.9.0 |
16.10.0 |
2021-12 |
RAN#94 |
R5-217938 |
0154 |
1 |
Correction of the conditions for Multi-RTT and Dl-AoD assistance data elements |
16.9.0 |
16.10.0 |
2022-03 |
RAN#95 |
R5-221592 |
0156 |
1 |
Addition of TC 9.4.1 PosSIB broadcasting followed by location information transfer |
16.10.0 |
16.11.0 |
2022-03 |
RAN#95 |
R5-221593 |
0157 |
1 |
Correction of the assistance data elements for NR positioning support |
16.10.0 |
16.11.0 |
2022-06 |
RAN#96 |
R5-223388 |
0158 |
1 |
Correction of TC 9.4.1 PosSIB broadcasting followed by location information transfer |
16.11.0 |
16.12.0 |
2022-06 |
RAN#96 |
R5-223389 |
0159 |
1 |
Addition of TC 9.4.2 PosSIB broadcasting followed by location information transfer / Positioning SI messages offset |
16.11.0 |
16.12.0 |
2022-06 |
RAN#96 |
R5-223390 |
0160 |
1 |
Addition of TC 7.5.2 PosSIB broadcasting followed by location information transfer |
16.11.0 |
16.12.0 |
2022-09 |
RAN#97 |
R5-224406 |
0162 |
– |
Removal of test case 7.5.2 |
16.12.0 |
16.13.0 |
2022-09 |
RAN#97 |
R5-224407 |
0163 |
– |
Correction of posSIB broadcasting test case |
16.12.0 |
16.13.0 |
2022-09 |
RAN#97 |
R5-225313 |
0161 |
1 |
Correction to LPP Provide Capabilities template for subclause 9 test cases |
16.12.0 |
16.13.0 |
2022-09 |
RAN#97 |
R5-225314 |
0164 |
1 |
Addition of on-demand PosSIB followed by location information transfer in RRC_connected state |
16.12.0 |
16.13.0 |