9.3 LPP Procedures
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
9.3.1 LPP Common Procedures
9.3.1.1 Position Capability Transfer
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.1.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a LPP message of type REQUEST CAPABILITIES }
then { UE sends a LPP message of type PROVIDE CAPABILITIES with the correct supported capabilities }
}
9.3.1.1.2 Conformance requirements
As defined in clause 7.3.1.1.2.
9.3.1.1.3 Test description
9.3.1.1.3.1 Pre-test conditions
System Simulator:
– For Test Configuration B (Table 9.3.1.1.3.2-1): NR Cell 1.
– For Test Configuration D (Table 9.3.1.1.3.2-1): LTE Cell 1.
UE:
–
Preamble:
– For Test Configuration B (Table 9.3.1.1.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.1.1.3.2-1): FFS
Related PICS/PIXIT Statements:
–
9.3.1.1.3.2 Test procedure sequence
Table 9.3.1.1.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.1.1 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour is as defined in Table 7.3.1.1.3.2-1.
9.3.1.1.3.3 Specific message contents
As defined in clause 7.3.1.1.3.3, with the following exceptions:
Table 9.3.1.1.3.3-1 replaces Table 7.3.1.1.3.3-1, Table 9.3.1.1.3.3-2 replaces Table 7.3.1.1.3.3-2, Table 9.3.1.1.3.3-3 replaces Table 7.3.1.1.3.3-4 and Table 9.3.1.1.3.3-4 replaces Table 7.3.1.1.3.3-5.
Table 9.3.1.1.3.3-1: DLInformationTransfer (steps 1 and 2a, Table 7.3.1.1.3.2-1)
|
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.3.1.1.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.1.1.3.3-2: DL NAS TRANSPORT (steps 1 and 2a, Table 7.3.1.1.3.2‑1)
|
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 1: Set according to Table 8.4-2 |
LPP Request Capabilities |
||
|
Step 2a: Set according to Table 7.3.1.1.3.3-14 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.1.1.3.3-2A: Void
Table 9.3.1.1.3.3-3: ULInformationTransfer (step 2, Table 7.3.1.1.3.2-1)
|
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.3.1.1.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.1.1.3.3-4: UL NAS TRANSPORT (step 2, Table 7.3.1.1.3.2-1)
|
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 |
Set according to Table 9.3.1.1.3.3-5 |
LPP Provide Capabilities |
||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1 Table 7.3.1.1.3.2‑1) |
||
Table 9.3.1.1.3.3-5: LPP PROVIDE CAPABILITIES (step 2, Table 7.3.1.1.3.2-1)
|
Derivation Path: Table 7.3.1.1.3.3-6 |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.1.1.3.3-6 with the following exception: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-ECID-ProvideCapabilities-r16 |
Present or not present dependent on pc_NR_ECID. Set according to Table 9.3.1.1.3.3-6. |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 SEQUENCE { |
Present or not present dependent on pc_Multi_RTT. |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-PRS-Capability-r16 |
Set according to Table 9.3.1.1.3.3-7 |
|||||||
|
nr-Multi-RTT-MeasurementCapability-r16 |
Set according to Table 9.3.1.1.3.3-8 |
|||||||
|
nr-DL-PRS-QCL-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-9 |
|||||||
|
nr-DL-PRS-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-10 |
|||||||
|
nr-UL-SRS-Capability-r16 |
Set according to Table 9.3.1.1.3.3-11 |
|||||||
|
additionalPathsReport-r16 |
Dependent on UE capabilities |
|||||||
|
periodicalReporting-r16 |
Dependent on UE capabilities |
|||||||
|
} |
||||||||
|
nr-DL-AoD-ProvideCapabilities-r16 SEQUENCE { |
Present or not present dependent on (pc_UEA_DL_AoD OR pc_UEB_DL_AoD). |
Rel-16 onwards |
||||||
|
nr-DL-AoD-Mode-r16 |
Dependent on UE capabilities |
|||||||
|
nr-DL-AoD-PRS-Capability-r16 |
Set according to Table 9.3.1.1.3.3-7. |
|||||||
|
nr-DL-AoD-MeasurementCapability-r16 |
Set according to Table 9.3.1.1.3.3-12. |
|||||||
|
nr-DL-PRS-QCL-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-9. |
|||||||
|
nr-DL-PRS-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-10. |
|||||||
|
periodicalReporting-r16 |
Dependent on UE capabilities |
|||||||
|
} |
||||||||
|
nr-DL-TDOA-ProvideCapabilities-r16 SEQUENCE { |
Present or not present dependent on (pc_UEA_DL_TDOA OR pc_UEB_DL_TDOA) |
Rel-16 onwards |
||||||
|
nr-DL-TDOA-Mode-r16 |
Dependent on UE capabilities |
|||||||
|
nr-DL-TDOA-PRS-Capability-r16 |
Set according to Table 9.3.1.1.3.3-7. |
|||||||
|
nr-DL-TDOA-MeasurementCapability-r16 |
Set according to Table 9.3.1.1.3.3-13. |
|||||||
|
nr-DL-PRS-QCL-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-9. |
|||||||
|
nr-DL-PRS-ProcessingCapability-r16 |
Set according to Table 9.3.1.1.3.3-10. |
|||||||
|
additionalPathsReport-r16 |
Dependent on UE capabilities |
|||||||
|
periodicalReporting-r16 |
Dependent on UE capabilities |
|||||||
|
} |
||||||||
|
nr-UL-ProvideCapabilities-r16 SEQUENCE { |
Present or not present and value dependent on UE capabilities. |
Rel-16 onwards |
||||||
|
nr-UL-SRS-Capability-r16 |
Set according to Table 9.3.1.1.3.3-11 |
|||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.1.1.3.3-6: NR-ECID-ProvideCapabilities (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.5.9.4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-ECID-ProvideCapabilities-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
nr-ECID-MeasSupported-r16 |
Dependent on UE capabilities |
|||
|
periodicalReporting-r16 |
Dependent on UE capabilities |
|||
|
triggeredReporting-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
Table 9.3.1.1.3.3-7: NR-DL-PRS-ResourcesCapability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.4.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-DL-PRS-ResourcesCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
maxNrOfDL-PRS-ResourceSetPerTrpPerFrequencyLayer-r16 |
Dependent on UE capabilities |
|||
|
maxNrOfTRP-AcrossFreqs-r16 |
Dependent on UE capabilities |
|||
|
maxNrOfPosLayer-r16 |
Dependent on UE capabilities |
|||
|
dl-PRS-ResourcesCapabilityBandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
maxNrOfDL-PRS-ResourcesPerResourceSet-r16 |
Dependent on UE capabilities |
|||
|
maxNrOfDL-PRS-ResourcesPerPositioningFrequencylayer-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
dl-PRS-ResourcesBandCombinationList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
bandList-r16 |
Not checked |
|||
|
maxNrOfDL-PRS-ResourcesAcrossAllFL-TRP-ResourceSet-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
} |
||||
Table 9.3.1.1.3.3-8: NR-Multi-RTT-MeasurementCapability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.5.12.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-Multi-RTT-MeasurementCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
maxNrOfRx-TX-MeasFR1-r16 |
Dependent on UE capabilities |
|||
|
maxNrOfRx-TX-MeasFR2-r16 |
Dependent on UE capabilities |
|||
|
supportOfRSRP-MeasFR1-r16 |
Dependent on UE capabilities |
|||
|
supportOfRSRP-MeasFR2-r16 |
Dependent on UE capabilities |
|||
|
srs-AssocPRS-MultiLayersFR1-r16 |
Dependent on UE capabilities |
|||
|
srs-AssocPRS-MultiLayersFR2-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
Table 9.3.1.1.3.3-9: NR-DL-PRS-QCL-ProcessingCapability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.4.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-DL-PRS-QCL-ProcessingCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
dl-PRS-QCL-ProcessingCapabilityBandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
ssb-FromNeighCellAsQCL-r16 |
Dependent on UE capabilities |
|||
|
prs-FromServNeighCellAsQCL-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
} |
||||
Table 9.3.1.1.3.3-10: NR-DL-PRS-ProcessingCapability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.4.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-DL-PRS-ProcessingCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
prs-ProcessingCapabilityBandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
supportedBandwidthPRS-r16 |
Dependent on UE capabilities |
|||
|
dl-PRS-BufferType-r16 |
Dependent on UE capabilities |
|||
|
durationOfPRS-Processing-r16 SEQUENCE { |
||||
|
durationOfPRS-ProcessingSymbols-r16 |
Dependent on UE capabilities |
|||
|
durationOfPRS-ProcessingSymbolsInEveryTms-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
maxNumOfDL-PRS-ResProcessedPerSlot-r16 SEQUENCE { |
||||
|
scs15-r16 |
Dependent on UE capabilities |
|||
|
scs30-r16 |
Dependent on UE capabilities |
|||
|
scs60-r16 |
Dependent on UE capabilities |
|||
|
scs120-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
} |
||||
|
maxSupportedFreqLayers-r16 |
Dependent on UE capabilities |
|||
|
simulLTE-NR-PRS-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
Table 9.3.1.1.3.3-11: NR-UL-SRS-Capability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.4.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-UL-SRS-Capability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
srs-CapabilityBandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
olpc-SRS-Pos-r16 SEQUENCE { |
||||
|
olpc-SRS-PosBasedOnPRS-Serving-r16 |
Dependent on UE capabilities |
|||
|
olpc-SRS-PosBasedOnSSB-Neigh-r16 |
Dependent on UE capabilities |
|||
|
olpc-SRS-PosBasedOnPRS-Neigh-r16 |
Dependent on UE capabilities |
|||
|
maxNumberPathLossEstimatePerServing-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
spatialRelationsSRS-Pos-r16 SEQUENCE { |
||||
|
spatialRelation-SRS-PosBasedOnSSB-Serving-r16 |
Dependent on UE capabilities |
|||
|
spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 |
Dependent on UE capabilities |
|||
|
spatialRelation-SRS-PosBasedOnPRS-Serving-r16 |
Dependent on UE capabilities |
|||
|
spatialRelation-SRS-PosBasedOnSRS-r16 |
Dependent on UE capabilities |
|||
|
spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 |
Dependent on UE capabilities |
|||
|
spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
} |
||||
|
srs-PosResourceConfigCA-BandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
maxNumberSRS-PosResourceSetsPerBWP-r16 |
Dependent on UE capabilities |
|||
|
maxNumberSRS-PosResourcesPerBWP-r16 |
Dependent on UE capabilities |
|||
|
maxNumberPeriodicSRS-PosResourcesPerBWP-r16 |
Dependent on UE capabilities |
|||
|
maxNumberAP-SRS-PosResourcesPerBWP-r16 |
Dependent on UE capabilities |
|||
|
maxNumberSP-SRS-PosResourcesPerBWP-r16 |
Dependent on UE capabilities |
|||
|
} |
Dependent on UE capabilities |
|||
|
maxNumberSRS-PosPathLossEstimateAllServingCells-r16 |
Dependent on UE capabilities |
|||
|
maxNumberSRS-PosSpatialRelationsAllServingCells-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
Table 9.3.1.1.3.3-12: NR-DL-AoD-MeasurementCapability-r16 (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.5.11.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-DL-AoD-MeasurementCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
maxDL-PRS-RSRP-MeasurementFR1-r16 |
Dependent on UE capabilities |
|||
|
maxDL-PRS-RSRP-MeasurementFR2-r16 |
Dependent on UE capabilities |
|||
|
dl-AoD-MeasCapabilityBandList-r16 SEQUENCE (SIZE (1..n)) OF SEQUENCE { |
Size n of SEQUENCE is dependent on UE capabilities |
|||
|
freqBandIndicatorNR-r16 |
Dependent on UE capabilities |
|||
|
simul-NR-DL-AoD-DL-TDOA-r16 |
Dependent on UE capabilities |
|||
|
simul-NR-DL-AoD-Multi-RTT-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
|
} |
||||
Table 9.3.1.1.3.3-13: NR-DL-TDOA-MeasurementCapability (Table 9.3.1.1.3.3-5)
|
Derivation Path: 37.355 clause 6.5.10.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
NR-DL-TDOA-MeasurementCapability-r16 ::= SEQUENCE { |
Rel-16 onwards |
|||
|
dl-RSTD-MeasurementPerPairOfTRP-FR1-r16 |
Dependent on UE capabilities |
|||
|
dl-RSTD-MeasurementPerPairOfTRP-FR2-r16 |
Dependent on UE capabilities |
|||
|
supportOfDL-PRS-RSRP-MeasFR1-r16 |
Dependent on UE capabilities |
|||
|
supportOfDL-PRS-RSRP-MeasFR2-r16 |
Dependent on UE capabilities |
|||
|
} |
||||
9.3.1.2 LPP Abort
Editor’s note: Test configuration D is incomplete:
– The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
– The message contents need to be revised for Test Configuration D.
9.3.1.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a LPP Abort message carrying the transaction ID of an on-going procedure }
then { UE aborts the on-going procedure }
}
9.3.1.2.2 Conformance requirements
As defined in clause 7.3.5.1.2.
9.3.1.2.3 Test description
9.3.1.2.3.1 Pre-test conditions
System Simulator:
– For Test Configuration B (Table 9.3.1.2.3.2-1):
– Sub-tests 11, 12, 13, 15, 16, 17, 19: NR Cell 1.
– Sub-test 5: NR Cell 1 and independent LTE Cell 1, as specified in 8.2.2.
– Sub-test 20: NR Cell 1 and NR Cell 2 (only applicable to UE-Based DL-TDOA).
– Sub-test 21: NR Cell 1, NR Cell 2 and NR Cell 3 (only applicable to UE-Based DL-AoD).
– For Test Configuration D (Table 9.3.1.2.3.2-1):
– Sub-tests 11, 12, 13, 15, 16, 17: LTE Cell 1.
– Sub-test 5: LTE Cell 1, as specified in 8.2.2.
UE:
– The UE shall begin the tests with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.3.1.2.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– Sub-test 5: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.1.2.3.1-1 for the configuration of measurement gaps for OTDOA (LTE).
– Sub-test 19: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.1.2.3.1-1 for the configuration of measurement gaps for Multi-RTT and then the SS shall execute the steps in Table 9.3.1.2.3.1-2 for the configuration of UL-SRS for Multi-RTT.
– Sub-test 20: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.1.2.3.1-1 for the configuration of measurement gaps for DL-AoD.
– Sub-test 21: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.1.2.3.1-1 for the configuration of measurement gaps for DL-TDOA.
Table 9.3.1.2.3.1-1: Configuration of measurement gaps
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.1-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
Table 9.3.1.2.3.1-2: Configuration of UL-SRS for Multi-RTT
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.2-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
– For Test Configuration D (Table 9.3.1.2.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.1.2.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.3.1.2.3.2-0 below:
Table 9.3.1.2.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
5 |
UE supporting OTDOA (LTE) (Rel-15 onwards) |
|
11 |
UE supporting WLAN (Rel-13 only) |
|
12 |
UE supporting MBS (Rel-13 only) |
|
13 |
UE supporting Bluetooth |
|
15 |
UE supporting GNSS(1) |
|
16 |
UE supporting MBS (Rel-14 onwards) |
|
17 |
UE supporting WLAN (Rel-14 onwards) |
|
19 |
UE supporting Multi-RTT (Rel-16 onwards) |
|
20 |
UE supporting DL-AoD (Rel-16 onwards) |
|
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Note that this test case does not include a sub-test for the case where ECID (LTE), NR E-CID or Sensor is supported by the UE as the behaviour required cannot be guaranteed in these cases.
Table 9.3.1.2.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.5.1 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour is as defined in Table 7.3.5.1.3.2-1.
9.3.1.2.3.3 Specific message contents
As defined in clause 7.3.5.1.3.3, with the following exceptions:
Table 9.3.1.2.3.3-0 replaces Table 7.3.5.1.3.3-0, Table 9.3.1.2.3.3-1 replaces Table 7.3.5.1.3.3-1, Table 9.3.1.2.3.3-2 replaces Table 7.3.5.1.3.3-2, Table 9.3.1.2.3.3-2a replaces Table 7.3.5.1.3.3-2c, Table 9.3.1.2.3.3-2b replaces Table 7.3.5.1.3.3-2d, Table 9.3.1.2.3.3-3 replaces Table 7.3.5.1.3.3-5, Table 9.3.1.2.3.3-4 replaces Table 7.3.5.1.3.3-6, Table 9.3.1.2.3.3-5 replaces Table 7.3.5.1.3.3-3 and Table 9.3.1.2.3.3-6 replaces Table 7.3.5.1.3.3-7.
Table 9.3.1.2.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 00, Table 7.3.5.1.3.2-1)
|
Derivation Path: 38.509 clause 6.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.5.1.3.3-0 with the following exceptions: |
||||
|
UE Positioning Technology |
Sub-test 19: 0 0 0 0 0 1 1 0 Sub-test 20: 0 0 0 0 1 0 0 0 Sub-test 21: 0 0 0 0 0 1 1 1 |
Sub-test 19: Multi-RTT Sub-test 20: DL-AoD Sub-test 21: DL-TDOA |
||
Table 9.3.1.2.3.3-1: DLInformationTransfer (steps 0, 0b, 0c, 1 and 2, Table 7.3.5.1.3.2-1)
|
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.3.1.2.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.1.2.3.3-2: DL NAS TRANSPORT (steps 0, 0b, 0c, 1 and 2, Table 7.3.5.1.3.2‑1)
|
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 0: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
|
Step 0b: Set according to Table 7.3.5.1.3.3-2b |
LPP Acknowledgement |
|||
|
Step 0c: Set according to Table 9.3.1.2.3.3-2a |
LPP Provide Assistance Data |
|||
|
Step 1: Set according to Table 9.3.1.2.3.3-5 |
LPP Request Location Information |
|||
|
Step 2: Set according to Table 7.3.5.1.3.3-4 |
LPP Abort |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.1.2.3.3-2a: LPP Provide Assistance Data (step 0c, Table 7.3.5.1.3.2-1)
|
Derivation Path: Table 8.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-1 with the following exceptions: |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
|
OTDOA-NeighbourCellInfoList ::= SEQUENCE (SIZE(1)) OF SEQUENCE { |
Sub-test 5 |
|||
|
SEQUENCE (SIZE(18)) OF SEQUENCE { |
Sequence contains 18 instances of the following data. |
|||
|
physCellId |
Refer to Sequence data values in Table 9.3.1.2.3.3-2b |
|||
|
cellGlobalId |
For values of cellidentity refer to Sequence data values in Table 9.3.1.2.3.3-2b |
|||
|
earfcn |
Not present |
Same as for the reference cell |
||
|
cpLength |
Not present |
Same as for the reference cell |
||
|
prsInfo |
Not present |
Same as for the reference cell |
||
|
antennaPortConfig |
Not present |
Same as for the reference cell |
||
|
slotNumberOffset |
Not present |
Same as for the reference cell |
||
|
prs-SubframeOffset |
Not present |
Same as for the reference cell |
||
|
expectedRSTD |
Refer to Sequence data values in Table 9.3.1.2.3.3-2b |
|||
|
expectedRSTD-Uncertainty |
Refer to Sequence data values in Table 9.3.1.2.3.3-2b |
|||
|
earfcn-v9a0 |
Not present |
Same as for the reference cell |
||
|
tpId-r14 |
Not present |
Transmission Points not used |
Rel-14 onwards |
|
|
prs-only-tp-r14 |
Not present |
Not required |
Rel-14 onwards |
|
|
cpLengthCRS-r14 |
Not present |
Not required |
Rel-14 onwards |
|
|
sameMBSFNconfigNeighbour-r14 |
TRUE |
Same as for the reference cell |
Rel-14 onwards |
|
|
dlBandwidth-r14 |
Not present |
Same as for the reference cell and PRS frequency hopping not used |
Rel-14 onwards |
|
|
addPRSconfigNeighbour-r14 |
Not present |
No additional PRS configuration(s) |
Rel-14 onwards |
|
|
tdd-config-v1520 |
Not present |
Rel-15 onwards |
||
|
} |
||||
|
} |
||||
Table 9.3.1.2.3.3-2b: Sequence data values for 18 instances of sequence for Table 9.3.1.2.3.3-2a
|
Cell |
Value physCellId |
Value cellidentity (E-UTRAN Cell Identity) |
Value expectedRSTD |
Value expectedRSTD-Uncertainty |
Comment |
|
|
Value eNB ID |
Value Cell Identity |
|||||
|
Cell 2 |
2 |
‘0000 0000 0000 0000 0001’B |
‘0000 0010’B |
8192 |
10 |
As defined for Cell 2 in 36.508 [8] |
|
Cell 4 |
4 |
‘0000 0000 0000 0000 0011’B |
‘0000 0100’B |
8192 |
10 |
As defined for Cell 4 in 36.508 [8] |
|
Dummy cell |
1 |
‘0000 0000 0000 0000 0001’B |
‘0000 0001’B |
8253 |
51 |
|
|
Dummy cell |
3 |
‘0000 0000 0000 0000 0010’B |
‘0000 0011’B |
8211 |
51 |
|
|
Dummy cell |
6 |
‘0000 0000 0000 0000 0100’B |
‘0000 0110’B |
8221 |
51 |
|
|
Dummy cell |
7 |
‘0000 0000 0000 0000 0110’B |
‘0000 0111’B |
8192 |
51 |
|
|
Dummy cell |
8 |
‘0000 0000 0000 0000 0010’B |
‘0000 1000’B |
8233 |
51 |
|
|
Dummy cell |
9 |
‘0000 0000 0000 0000 0100’B |
‘0000 1001’B |
8161 |
51 |
|
|
Dummy cell |
10 |
‘0000 0000 0000 0000 0101’B |
‘0000 1010’B |
8226 |
51 |
|
|
Dummy cell |
11 |
‘0000 0000 0000 0000 0110’B |
‘0000 1011’B |
8232 |
51 |
|
|
Dummy cell |
16 |
‘0000 0000 0000 0000 0010’B |
‘0001 0000’B |
8223 |
51 |
|
|
Dummy cell |
111 |
‘0000 0000 0000 0000 1100’B |
‘0110 1111’B |
8236 |
51 |
|
|
Dummy cell |
118 |
‘0000 0000 0000 0000 1111’B |
‘0111 0110’B |
8223 |
51 |
|
|
Dummy cell |
119 |
‘0000 0000 0000 0000 1110’B |
‘0111 0111’B |
8221 |
51 |
|
|
Dummy cell |
120 |
‘0000 0000 0000 0000 1111’B |
‘0111 1000’B |
8223 |
51 |
|
|
Dummy cell |
122 |
‘0000 0000 0000 0000 1010’B |
‘0111 1010’B |
8243 |
51 |
|
|
Dummy cell |
125 |
‘0000 0000 0000 0000 1011’B |
‘0111 1101’B |
8253 |
51 |
|
|
Dummy cell |
126 |
‘0000 0000 0000 0000 1100’B |
‘0111 1110’B |
8257 |
51 |
|
Table 9.3.1.2.3.3-3: ULInformationTransfer (step 0a, Table 7.3.5.1.3.2-1)
|
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.3.1.2.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.1.2.3.3-4: UL NAS TRANSPORT (step 0a, Table 7.3.5.1.3.2-1)
|
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 |
Set according to Table 9.3.1.1.3.3-5 |
LPP Provide Capabilities |
||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1 Table 7.3.1.1.3.2‑1) |
||
Table 9.3.1.2.3.3-5: LPP Request Location Information (step 1, Table 7.3.5.1.3.2-1)
|
Derivation Path: Table 8.4-3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-3 with the following exceptions: |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
locationServer |
|||
|
transactionNumber |
0 |
|||
|
} |
||||
|
locationInformationType |
locationEstimateRequired |
In case of "UE-based" Location method supported by the UE |
||
|
locationMeasurementsRequired |
In case of "UE-assisted" Location method supported by the UE |
|||
|
time |
10 |
|||
Table 9.3.1.2.3.3-6: LPP Provide Capabilities (step 0a, Table 7.3.5.1.3.2-1)
|
Derivation Path: Table 7.3.5.1.3.3-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table ith the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideCapabilities SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideCapabilities-r9 SEQUENCE { |
||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||
|
nr-ECID-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
9.3.2 LPP Transport
9.3.2.1 LPP Duplicated Message
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.2.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a LPP message carrying the same sequence number as that last received for the
associated location session }
then { UE discards the LPP message }
}
9.3.2.1.2 Conformance requirements
As defined in clause 7.3.2.1.2.
9.3.2.1.3 Test description
9.3.2.1.3.1 Pre-test conditions
System Simulator:
– For Test Configuration B (Table 9.3.2.1.3.2-1): NR Cell 1.
– For Test Configuration D (Table 9.3.2.1.3.2-1): LTE Cell 1.
UE:
–
Preamble:
– For Test Configuration B (Table 9.3.2.1.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.2.1.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.2.1.3.2 Test procedure sequence
Table 9.3.2.1.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.2.1 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour is as defined in Table 7.3.2.1.3.2-1.
9.3.2.1.3.3 Specific message contents
As defined in clause 7.3.2.1.3.3, with the following exceptions:
Table 9.3.2.1.3.3-1 replaces Table 7.3.2.1.3.3-1, Table 9.3.2.1.3.3-2 replaces Table 7.3.2.1.3.3-2, Table 9.3.2.1.3.3-3 replaces Table 7.3.2.1.3.3-4, Table 9.3.2.1.3.3-4 replaces Table 7.3.2.1.3.3-5, Table 9.3.2.1.3.3-2a replaces Table 7.3.2.1.3.3-3 and Table 9.3.2.1.3.3-5 replaces Table 7.3.2.1.3.3-6.
Table 9.3.2.1.3.3-1: DLInformationTransfer (steps 1, 2, and 3a, Table 7.3.2.1.3.2-1)
|
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.3.2.1.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.1.3.3-2: DL NAS TRANSPORT (steps 1, 2 and 3a, Table 7.3.2.1.3.2‑1)
|
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 1 and 2: Set according to Table 9.3.2.1.3.3-2a |
LPP Request Capabilities |
||
|
Step 3a: Set according to Table 7.3.2.1.3.3-7 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.2.1.3.3-2a: LPP Request Capabilities (steps 1 and 2, Table 7.3.2.1.3.2-1)
|
Derivation Path: Table 8.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-1 with the following exceptions: |
||||
|
sequenceNumber |
0 |
|||
Table 9.3.2.1.3.3-3: ULInformationTransfer (step 3, Table 7.3.2.1.3.2-1)
|
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.3.2.1.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.1.3.3-4: UL NAS TRANSPORT (step 3, Table 7.3.2.1.3.2-1)
|
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 |
Set according to Table 9.3.2.1.3.3-5 |
LPP Provide Capabilities |
||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1 Table 7.3.2.1.3.2‑1) |
||
Table 9.3.2.1.3.3-5: LPP Provide Capabilities (step 3, Table 7.3.2.1.3.2-1)
|
Derivation Path: Table 7.3.2.2.3.3-6 |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.2.2.3.3-6 with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-ECID-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
9.3.2.2 LPP Acknowledgment
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.2.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a LPP message carrying an acknowledgement request indicator }
then { UE returns an acknowledgement response }
}
9.3.2.2.2 Conformance requirements
As defined in clause 7.3.2.2.2.
9.3.2.2.3 Test description
9.3.2.2.3.1 Pre-test conditions
System Simulator:
– For Test Configuration B (Table 9.3.2.2.3.2-1): NR Cell 1.
– For Test Configuration D (Table 9.3.2.2.3.2-1): LTE Cell 1.
UE:
–
Preamble:
– For Test Configuration B (Table 9.3.2.2.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.2.2.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.2.2.3.2 Test procedure sequence
Table 9.3.2.2.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.2.2 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in Table 7.3.2.2.3.2-1.
9.3.2.2.3.3 Specific message contents
As defined in clause 7.3.2.2.3.3, with the following exceptions:
Table 9.3.2.2.3.3-1 replaces Table 7.3.2.2.3.3-1, Table 9.3.2.2.3.3-2 replaces Table 7.3.2.2.3.3-2, Table 9.3.2.2.3.3-3 replaces Table 7.3.2.2.3.3-4, Table 9.3.2.2.3.3-4 replaces Table 7.3.2.2.3.3-5, Table 9.3.2.2.3.3-2a replaces Table 7.3.2.2.3.3-3 and Table 9.3.2.2.3.3-5 replaces Table 7.3.2.2.3.3-6.
Table 9.3.2.2.3.3-1: DLInformationTransfer (steps 1, and 3, Table 7.3.2.2.3.2-1)
|
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.3.2.2.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.2.3.3-2: DL NAS TRANSPORT (steps 1, and 3, Table 7.3.2.2.3.2‑1)
|
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 1: Set according to Table 9.3.2.2.3.3-2a |
LPP Request Capabilities |
||
|
Step 3: Set according to Table 7.3.2.2.3.3-8 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.2.2.3.3-2a: LPP Request Capabilities (step 1, Table 7.3.2.2.3.2-1)
|
Derivation Path: Table 8.4-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-2 with the following exceptions: |
||||
|
sequenceNumber |
0 |
|||
|
acknowledgement SEQUENCE { |
||||
|
ackRequested |
TRUE |
|||
|
ackIndicator |
Not present |
|||
|
} |
||||
Table 9.3.2.2.3.3-3: ULInformationTransfer (step 2, Table 7.3.2.2.3.2-1)
|
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.3.2.2.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.2.3.3-4: UL NAS TRANSPORT (step 2, Table 7.3.2.2.3.2-1)
|
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 |
Set according to Table 9.3.2.2.3.3-5 |
LPP Provide Capabilities |
||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1 Table 7.3.2.2.3.2‑1) |
||
Table 9.3.2.2.3.3-5: LPP Provide Capabilities (step 2, Table 7.3.2.2.3.2-1)
|
Derivation Path: Table 7.3.2.2.3.3-6 |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.2.2.3.3-6 with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-ECID-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
9.3.2.3 LPP Retransmission
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.2.3.1 Test Purpose (TP)
(1)
with { a NAS signalling connection for EPC-NI-LR session existing}
ensure that {
when { UE does not receive an LPP acknowledgement for an LPP message which requires
acknowledgement }
then { UE retransmits the LPP message up to three times. If still unacknowledged after that, the
UE aborts all LPP activity for the associated session}
}
9.3.2.3.2 Conformance requirements
As defined in clause 7.3.2.3.2.
9.3.2.3.3 Test description
9.3.2.3.3.1 Pre-test conditions
System Simulator:
– For Test Configuration B (Table 9.3.2.3.3.2-1): NR Cell 1.
– For Test Configuration D (Table 9.3.2.3.3.2-1): LTE Cell 1.
UE:
–
Preamble:
– For Test Configuration B (Table 9.3.2.3.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.2.3.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.2.3.3.2 Test procedure sequence
Table 9.3.2.3.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.2.3 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in Table 7.3.2.3.3.2-1.
9.3.2.3.3.3 Specific message contents
As defined in clause 7.3.2.3.3.3, with the following exceptions:
Table 9.3.2.3.3.3-1 replaces Table 7.3.2.3.3.3-1, Table 9.3.2.3.3.3-2 replaces Table 7.3.2.3.3.3-2, Table 9.3.2.3.3.3-3 replaces Table 7.3.2.3.3.3-4, Table 9.3.2.3.3.3-4 replaces Table 7.3.2.3.3.3-5 and Table 9.3.2.3.3.3-5 replaces Table 7.3.2.3.3.3-6.
Table 9.3.2.3.3.3-1: DLInformationTransfer (step 1, Table 7.3.2.3.3.2-1)
|
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.3.2.3.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.3.3.3-2: DL NAS TRANSPORT (steps 1 and 2a, Table 7.3.2.3.3.2‑1)
|
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 |
Set according to Table 8.4-2 |
LPP Request Capabilities |
||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.2.3.3.3-3: ULInformationTransfer (steps 2, 4, 6, and 8, Table 7.3.2.3.3.2-1)
|
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.3.2.3.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.2.3.3.3-4: UL NAS TRANSPORT (steps 2, 4, 6, and 8, Table 7.3.2.3.3.2-1)
|
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 |
Set according to Table Table 9.3.2.3.3.3-5 |
LPP Provide Capabilities |
||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 1 Table 7.3.2.3.3.2‑1) |
||
Table 9.3.2.3.3.3-5: LPP Provide Capabilities (steps 2, 4, 6, and 8, Table 7.3.2.3.3.2-1)
|
Derivation Path: Table 7.3.2.3.3.3-6 |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.2.3.3.3-6 with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-ECID-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
9.3.3 LPP Error Handling
9.3.3.1 Void
9.3.3.1A Void
9.3.3.1B LPP Requested Method not Supported – UE-Assisted
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.3.1B.1 Test Purpose (TP)
(1)
with { a UE supporting at least one of UE-assisted GNSS, UE-assisted OTDOA (LTE) (LPP Rel-15 onwards), UE-assisted ECID (LTE) (Test Configuration D only), UE-assisted WLAN, UE-assisted Bluetooth, UE-assisted Sensor, UE-assisted MBS, UE-assisted DL-TDOA, UE-assisted DL-AoD, UE-assisted Multi-RTT or UE-assisted NR E-CID but not all of them }
and with { a NAS signalling connection existing }
ensure that {
when { UE receives a LPP message requesting at least one location method not supported }
then { the UE provides location information for the supported methods}
}
9.3.3.1B.2 Conformance requirements
As defined in clause 7.3.3.1B.2.
9.3.3.1B.3 Test description
9.3.3.1B.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.3.3.1B.3.2-1):
– If GNSS is supported by the UE: NR Cell 1 and satellite signals, as specified in 8.2.1.
– If OTDOA (LTE) is supported by the UE: NR Cell 1 independent and LTE Cell 1 and LTE Cell 2 as specified in 8.2.2.
– If WLAN is supported by the UE: NR Cell 1 and WLAN signals, as specified in 8.2.5.
– If Bluetooth is supported by the UE: NR Cell 1 and Bluetooth signals, as specified in 8.2.6.
– If Sensor is supported by the UE: NR Cell 1.
– If MBS is supported by the UE: NR Cell 1 and MBS signals, as specified in 8.2.4.
– If DL-TDOA is supported by the UE: NR Cell 1 and NR Cell 2, as specified in 8.2.11.
– If DL-AoD is supported by the UE: NR Cell 1, as specified in 8.2.10.
– If Multi-RTT is supported by the UE: NR Cell 1, as specified in 8.2.9.
– If NR E-CID is supported by the UE: NR Cell 1, as specified in 8.2.12.
For Test Configuration D (Table 9.3.3.1B.3.2-1):
– If GNSS is supported by the UE: LTE Cell 1 and satellite signals, as specified in 8.2.1.
– If OTDOA (LTE) is supported by the UE: LTE Cell 1 and LTE Cell 2, as specified in 8.2.2
– If ECID (LTE) is supported by the UE: LTE Cell 1 and LTE Cell 2, as specified in 8.2.3.
– If WLAN is supported by the UE: LTE Cell 1 and WLAN signals, as specified in 8.2.5.
– If Bluetooth is supported by the UE: LTE Cell 1 and Bluetooth signals, as specified in 8.2.6.
– If Sensor is supported by the UE: LTE Cell 1.
– If MBS is supported by the UE: LTE Cell 1 and MBS signals, as specified in 8.2.4.
UE:
–
Preamble:
– For Test Configuration B (Table 9.3.3.1B.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– If OTDOA (LTE) is supported by the UE then after the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.3.1B.3.1-1 for the configuration of measurement gaps for OTDOA (LTE).
– If DL-TDOA is supported by the UE then after the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.3.1B.3.1-1 for the configuration of measurement gaps for DL-TDOA.
– If DL-AoD is supported by the UE then after the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.3.1B.3.1-1 for the configuration of measurement gaps for DL-AoD.
– If Multi-RTT is supported by the UE then after the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.3.1B.3.1-1 for the configuration of measurement gaps for Multi-RTT and then the SS shall execute the steps in Table 9.3.3.1B.3.1-2 for the configuration of UL-SRS for Multi-RTT.
Table 9.3.3.1B.3.1-1: Configuration of measurement gaps
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.1-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
Table 9.3.3.1B.3.1-2: Configuration of UL-SRS for Multi-RTT
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.2-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
– For Test Configuration D (Table 9.3.3.1B.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.3.1B.3.2 Test procedure sequence
Table 9.3.3.1B.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.3.1B |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in clause 7.3.3.1B.3.2.
9.3.3.1B.3.3 Specific message contents
As defined in clause 7.3.3.1B.3.3, with the following exceptions:
Table 9.3.3.1B.3.3-1 replaces Table 7.3.3.1B.3.3-1, Table 9.3.3.1B.3.3-2 replaces Table 7.3.3.1B.3.3-2, Table 9.3.3.1B.3.3-2a replaces Table 7.3.3.1B.3.3-3, Table 9.3.3.1B.3.3-3 replaces Table 7.3.3.1B.3.3-5, Table 9.3.3.1B.3.3-4 replaces Table 7.3.3.1B.3.3-6, Table 9.3.3.1B.3.3.5 replaces Table 7.3.3.1B.3.3-4, Table 9.3.3.1B.3.3.6 replaces Table 7.3.3.1B.3.3-6a and Table 9.3.3.1B.3.3-7 replaces Table 7.3.3.1B.3.3-7.
Table 9.3.3.1B.3.3-1: DLInformationTransfer (steps 0, 0b, 1, 2 and 3a, Table 7.3.3.1B.3.2-1)
|
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.3.3.1B.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.3.1B.3.3-2: DL NAS TRANSPORT (steps 0, 0b, 1, 2 and 3a, Table 7.3.3.1B.3.2-1)
|
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 0: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
|
Step 1: Set according to Table 9.3.3.1B.3.3-2a |
LPP Provide Assistance Data |
|||
|
Step 2: Set according to Table 9.3.3.1B.3.3-5 |
LPP Request Location Information |
|||
|
Steps 0b and 3a: Set according to Table 7.3.3.1B.3.3-8 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.3.1B.3.3-2a: LPP Provide Assistance data (step 1, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 8.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-1 with the following exceptions: |
||||
|
transactionID SEQUENCE { |
||||
|
Initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
|
a-gnss-ProvideAssistanceData |
Present for all supported GNSSs if UE supports UE-assisted A-GNSS. As defined in clause 8.4 |
|||
|
otdoa-ProvideAssistanceData |
Present if UE supports UE-assisted OTDOA (LTE). As defined in clause 8.4 |
|||
|
sensor-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted Sensor. As defined in clause 8.4 |
Rel-14 onwards |
||
|
tbs-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted MBS. As defined in clause 8.4 |
Rel-14 onwards |
||
|
wlan-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted WLAN. As defined in clause 8.4 |
Rel-14 onwards |
||
|
nr-Multi-RTT-ProvideAssistanceData |
Present if UE supports UE-assisted Multi-RTT. As defined in clause 8.4 |
Rel-16 onwards |
||
|
nr-DL-AoD-ProvideAssistanceData-r16 |
Present if UE supports UE-assisted DL-AoD. As defined in clause 8.4 |
Rel-16 onwards |
||
|
nr-DL-TDOA-ProvideAssistanceData-r16 |
Present if UE supports UE-assisted DL-TDOA. As defined in clause 8.4 |
Rel-16 onwards |
||
Table 9.3.3.1B.3.3-3: ULInformationTransfer (steps 0a and 3, Table 7.3.3.1B.3.2-1)
|
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.3.3.1B.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.3.1B.3.3-4: UL NAS TRANSPORT (steps 0a and 3, Table 7.3.3.1B.3.2-1)
|
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 0a: Set according to Table 9.3.3.1B.3.3-6 |
LPP Provide Capabilities |
||
|
Step 3: Set according to Table 9.3.3.1B.3.3-7 |
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 1 Table 7.3.3.1B.3.2‑1) |
||
Table 9.3.3.1B.3.3-5: LPP Request Location Information (step 2, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 5.4-3 |
|||||||
|
Information Element |
Value/remark |
Comment |
Condition |
||||
|
As defined in Table 5.4-3 with the following exceptions: |
|||||||
|
locationInformationType |
locationMeasurementsRequired |
||||||
|
a-gnss-RequestLocationInformation |
Present. As defined in Table 5.4-4 |
||||||
|
gnss-Methods |
GNSS-ID-Bitmap: bits 0, 3, 4, 5 = 1 |
||||||
|
otdoa-RequestLocationInformation |
Present. As defined in Table 5.4-5 |
||||||
|
ecid-RequestLocationInformation |
Present. As defined in Table 5.4-6 |
||||||
|
requestedMeasurements |
Test Configuration D: bits 0, 1, 2 = 1 |
||||||
|
tbs-RequestLocationInformation-r13 |
Present. As defined in Table 5.4-7 |
Rel-13 onwards |
|||||
|
sensor-RequestLocationInformation-r13 |
Present. As defined in Table 5.4-10 |
Rel-13 onwards |
|||||
|
wlan-RequestLocationInformation-r13 |
Present. As defined in Table 5.4-8 |
Rel-13 onwards |
|||||
|
bt-RequestLocationInformation-r13 |
Present. As defined in Table 5.4-9 |
Rel-13 onwards |
|||||
|
nr-ECID-RequestLocationInformation-r16 |
Present. As defined in Table 8.4-4 |
Rel-16 onwards |
|||||
|
nr-Multi-RTT-RequestLocationInformation-r16 |
Present. As defined in Table 8.4-5 |
Rel-16 onwards |
|||||
|
nr-DL-AoD-RequestLocationInformation-r16 |
Present. As defined in Table 8.4-6 |
Rel-16 onwards |
|||||
|
nr-DL-TDOA-RequestLocationInformation-r16 |
Present. As defined in Table 8.4-7 |
Rel-16 onwards |
|||||
Table 9.3.3.1B.3.3-6: LPP Provide Capabilities (step 0a, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 7.3.3.1B.3.3-6a |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.3.1B.3.3-6a with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-ECID-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.3.1B.3.3-7: LPP Provide Location Information (step 3, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 7.3.3.1B.3.3-7 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.3.1B.3.3-7 with the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation-r9 SEQUENCE { |
||||
|
nr-Multi-RTT-ProvideLocationInformation-r16 SEQUENCE { |
Present if UE supports UE-assisted Multi-RTT. |
Rel-16 onwards |
||
|
nr-Multi-RTT-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
|
nr-Multi-RTT-Error-r16 |
May be present |
|||
|
} |
||||
|
nr-DL-AoD-ProvideLocationInformation-r16 SEQUENCE { |
Present if UE supports UE-assisted DL-AoD. |
Rel-16 onwards |
||
|
nr-DL-AoD-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
|
nr-dl-AoD-LocationInformation-r16 |
Not present |
|||
|
nr-DL-AoD-Error-r16 |
May be present |
|||
|
} |
||||
|
nr-DL-TDOA-ProvideLocationInformation-r16 SEQUENCE { |
Present if UE supports UE-assisted DL-TDOA. |
Rel-16 onwards |
||
|
nr-DL-TDOA-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
|
nr-dl-tdoa-LocationInformation-r16 |
Not present |
|||
|
nr-DL-TDOA-Error-r16 |
May be present |
|||
|
} |
||||
|
nr-ECID-ProvideLocationInformation-r16 SEQUENCE { |
Present if UE supports UE-assisted NR E-CID. |
Rel-16 onwards |
||
|
nr-ECID-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
|||
|
nr-ECID-Error-r16 |
May be present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
9.3.4 LPP Positioning Procedures
9.3.4.1 E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE-Based
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.4.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives assistance data and a location request for UE-based }
then { UE sends a PROVIDE LOCATION INFORMATION message containing a location estimate }
}
9.3.4.1.2 Conformance requirements
As defined in clause 7.3.4.1.2.
9.3.4.1.3 Test description
9.3.4.1.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.3.4.1.3.2-1):NR Cell 1.
– Satellite signals (sub-test case 15): as specified in 8.2.1.
– MBS signals (Sub-test 16): as specified in 8.2.4.
– WLAN signals (Sub-test 17): as specified in 8.2.5.
– Sub-test 20: NR Cell 1 and NR Cell 2, as specified in 8.2.10.
– Sub-test 21: NR Cell 1, NR Cell 2 and NR Cell 3, as specified in 8.2.11.
For Test Configuration D (Table 9.3.4.1.3.2-1): LTE Cell 1.
– Satellite signals (sub-test case 15): as specified in 8.2.1.
– MBS signals (Sub-test 16): as specified in 8.2.4.
– WLAN signals (Sub-test 17): as specified in 8.2.5.
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.3.4.1.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.4.1.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.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.3.4.1.3.2-0 below:
Table 9.3.4.1.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
15 |
UE supporting GNSS(1) |
|
16 |
UE supporting MBS (Rel-14 onwards) |
|
17 |
UE supporting WLAN (Rel-14 onwards) |
|
18 |
UE supporting Sensor (Rel-14 onwards) |
|
20 |
UE supporting DL-AoD (Rel-16 onwards) |
|
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 9.3.4.1.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.4.1 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in Table 7.3.4.1.3.2-1.
9.3.4.1.3.3 Specific message contents
As defined in clause 7.3.4.1.3.3, with the following exceptions:
Table 9.3.4.1.3.3-0 replaces Table 7.3.4.1.3.3-1, Table 9.3.4.1.3.3-1 replaces Table 7.3.4.1.3.3-2, Table 9.3.4.1.3.3-2 replaces Table 7.3.4.1.3.3-3, Table 9.3.4.1.3.3-2a replaces Table 7.3.4.1.3.3-4, Table 9.3.4.1.3.3-3 replaces Table 7.3.4.1.3.3-6, Table 9.3.4.1.3.3-4 replaces Table 7.3.4.1.3.3-7, Table 9.3.4.1.3.3-2b replaces Table 7.3.4.1.3.3-5, Table 9.3.4.1.3.3-5 replaces Table 7.3.4.1.3.3-7a and Table 9.3.4.1.3.3-6 replaces Table 7.3.4.1.3.3-8.
Table 9.3.4.1.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.1.3.2-1)
|
Derivation Path: 38.509 clause 6.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.1.3.3-1 with the following exceptions: |
||||
|
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 20: DL-AoD Sub-test 21: DL-TDOA |
||
Table 9.3.4.1.3.3-1: DLInformationTransfer (steps 1a, 1c, 2, 3 and 4a, Table 7.3.4.1.3.2-1)
|
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.3.4.1.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.1.3.3-2: DL NAS TRANSPORT (steps 1a, 1c, 2, 3 and 4a, Table 7.3.4.1.3.2-1)
|
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 1a: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
|
Step 2: Set according to Table 9.3.4.1.3.3-2a |
LPP Provide Assistance Data |
|||
|
Step 3: Set according to Table 9.3.4.1.3.3-2b |
LPP Request Location Information |
|||
|
Steps 1c and 4a: Set according to Table 7.3.4.1.3.3-9 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.4.1.3.3-2a: LPP Provide Assistance data (step 2, Table 7.3.4.1.3.2-1)
|
Derivation Path: Table 8.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-1 with the following exceptions: |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
Table 9.3.4.1.3.3-2b: LPP Request Location Information (step 3, Table 7.3.4.1.3.2-1)
|
Derivation Path: Table 8.4-3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-3 with the following exceptions: |
||||
|
locationInformationType |
locationEstimateRequired |
|||
Table 9.3.4.1.3.3-3: ULInformationTransfer (steps 1b and 4, Table 7.3.4.1.3.2-1)
|
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.3.4.1.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.1.3.3-4: UL NAS TRANSPORT (steps 1b and 4, Table 7.3.4.1.3.2-1)
|
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 1b: Set according to Table 9.3.4.1.3.3-5 |
LPP Provide Capabilities |
||
|
Step 4: Set according to Table 9.3.4.1.3.3-6 |
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 1 Table 7.3.4.1.3.2‑1) |
||
Table 9.3.4.1.3.3-5: LPP Provide Capabilities. (step 1b, Table 7.3.4.1.3.2-1)
|
Derivation Path: Table 7.3.4.1.3.3-7a |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.4.1.3.3-7a with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.4.1.3.3-6: LPP Provide Location Information (step 4, Table 7.3.4.1.3.2-1)
|
Derivation Path: Table 7.3.4.1.3.3-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.1.3.3-8 with the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation-r9 SEQUENCE { |
||||
|
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-LocationInformation-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-LocationInformation-r16 |
Present. Any value acceptable |
|||
|
nr-DL-TDOA-Error-r16 |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
9.3.4.2 E-SMLC Initiated Assistance Data Delivery followed by Location Information Transfer: UE‑Assisted
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.4.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives assistance data and a location request for UE-assisted }
then { UE sends a PROVIDE LOCATION INFORMATION message containing location measurements }
}
9.3.4.2.2 Conformance requirements
As defined in clause 7.3.4.2.2.
9.3.4.2.3 Test description
9.3.4.2.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.3.4.2.3.2-1):
– Sub-tests 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 22: NR Cell 1.
– Sub-tests 5 and 7: NR Cell 1 and independent LTE Cell 1 and LTE Cell 2 as specified in 8.2.2.
– Sub-test 6: not applicable.
– Satellite signals (Sub-test 15): as specified in 8.2.1.
– WLAN signals (Sub-tests 11, 17): as specified in 8.2.5.
– MBS signals (Sub-tests 12, 16): as specified in 8.2.4
– Bluetooth signals (Sub-test 13): as specified in 8.2.6.
– Sub-test 21: NR Cell 1 and NR Cell 2, as specified in 8.2.11.
For Test Configuration D (Table 9.3.4.2.3.2-1):
– Sub-tests 11, 12, 13, 14, 15, 16, 17, 18: LTE Cell 1.
– Sub-tests 5 and 7: LTE Cell 1 and LTE Cell 2, as specified in 8.2.2.
– Sub-test 6: LTE Cell 1 and LTE Cell 2, as specified in 8.2.3.
– Satellite signals (Sub-test 15): as specified in 8.2.1.
– WLAN signals (Sub-tests 11, 17): as specified in 8.2.5.
– MBS signals (Sub-tests 12, 16): as specified in 8.2.4
– Bluetooth signals (Sub-test 13): as specified in 8.2.6.
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.3.4.2.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– Sub-test 5 and 7: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.2.3.1-1 for the configuration of measurement gaps for OTDOA (LTE).
– Sub-test 19: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.2.3.1-1 for the configuration of measurement gaps for Multi-RTT and then the SS shall execute the steps in Table 9.3.4.2.3.1-2 for the configuration of UL-SRS for Multi-RTT.
– Sub-test 20: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.2.3.1-1 for the configuration of measurement gaps for DL-AoD.
– Sub-test 21 After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.2.3.1-1 for the configuration of measurement gaps for DL-TDOA.
Table 9.3.4.2.3.1-1: Configuration of measurement gaps
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.1-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
Table 9.3.4.2.3.1-2: Configuration of UL-SRS for Multi-RTT
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.2-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
– For Test Configuration D (Table 9.3.4.2.3.2-1): FFS.
Related PICS/PIXIT Statements:
–
9.3.4.2.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.3.4.2.3.2-0 below:
Table 9.3.4.2.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
5 |
UE supporting OTDOA (LTE) (Rel-15 onwards) |
|
6 |
UE supporting ECID (LTE) (Test Configuration D only) |
|
7 |
UE supporting GNSS(1) and OTDOA (LTE) (Rel-15 onwards) |
|
11 |
UE supporting WLAN (Rel-13 only) |
|
12 |
UE supporting MBS (Rel-13 only) |
|
13 |
UE supporting Bluetooth |
|
14 |
UE supporting Sensor (Rel-13 only) |
|
15 |
UE supporting GNSS(1) |
|
16 |
UE supporting MBS (Rel-14 onwards) |
|
17 |
UE supporting WLAN (Rel-14 onwards) |
|
18 |
UE supporting Sensor (Rel-14 onwards) |
|
19 |
UE supporting Multi-RTT (Rel-16 onwards) |
|
20 |
UE supporting DL-AoD (Rel-16 onwards) |
|
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
|
22 |
UE supporting NR E-CID (Rel-16 onwards) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 9.3.4.2.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.4.2 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in clause 7.3.4.2.3.2.
For sub-test 19 or sub-test 20 or sub-test 21, the SS sends the RESET UE POSITIONING STORED INFORMATION message to the UE at step 1. Then the stored assistance data in the UE are cleared.
For sub-test 22 NR E-CID, the SS does not send LPP message of type Provide Assistance Data at step 2.
9.3.4.2.3.3 Specific message contents
As defined in clause 7.3.4.2.3.3, with the following exceptions:
Table 9.3.4.2.3.3-0 replaces Table 7.3.4.2.3.3-1, Table 9.3.4.2.3.3-1 replaces Table 7.3.4.2.3.3-3, Table 9.3.4.2.3.3-2 replaces Table 7.3.4.2.3.3-4, Table 9.3.4.2.3.3-2a replaces Table 7.3.4.2.3.3-5, Table 9.3.4.2.3.3-3 replaces Table 7.3.4.2.3.3-7, Table 9.3.4.2.3.3-4 replaces Table 7.3.4.2.3.3-8, Table 9.3.4.2.3.3-5 replaces Table 7.3.4.2.3.3-6, Table 9.3.4.2.3.3-6 replaces Table 7.3.4.2.3.3-8a and Table 9.3.4.2.3.3-7 replaces Table 7.3.4.2.3.3-9.
Table 9.3.4.2.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.2.3.2-1)
|
Derivation Path: 38.509 clause 6.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.2.3.3-1 with the following exceptions: |
||||
|
UE Positioning Technology |
Sub-test 19: 0 0 0 0 0 1 1 0 Sub-test 20: 0 0 0 0 1 0 0 0 Sub-test 21: 0 0 0 0 0 1 1 1 |
Sub-test 19: Multi-RTT Sub-test 20: DL-AoD Sub-test 21: DL-TDOA |
||
Table 9.3.4.2.3.3-1: DLInformationTransfer (steps 1b, 1d, 2, 3, 4a2, 4b2 and 4b4, Table 7.3.4.2.3.2-1)
|
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.3.4.2.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.2.3.3-2: DL NAS TRANSPORT (steps 1b, 1d, 2, 3, 4a2, 4b2 and 4b4, Table 7.3.4.2.3.2-1)
|
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 1b: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
|
Step 2: Set according to Table 9.3.4.2.3.3-2a |
LPP Provide Assistance Data |
|||
|
Step 3: Set according to Table9.3.4.2.3.3-5 |
LPP Request Location Information |
|||
|
Steps 1d, 4a2, 4b2 and 4b4: Set according to Table 7.3.4.2.3.3-10 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.4.2.3.3-2a: LPP Provide Assistance data (step 2, Table 7.3.4.2.3.2-1)
|
Derivation Path: Table 8.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 8.4-1 with the following exceptions: |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
Table 9.3.4.2.3.3-3: ULInformationTransfer (steps 1c, 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)
|
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.3.4.2.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.2.3.3-4: UL NAS TRANSPORT (steps 1c, 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)
|
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 1c: Set according to Table 9.3.4.2.3.3-6 |
LPP Provide Capabilities |
||
|
Steps 4 a1, 4b1 and 4b3: Set according to Table 9.3.4.2.3.3-7 |
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 1 Table 7.3.4.2.3.2‑1) |
||
Table 9.3.4.2.3.3-5: LPP Request Location Information (step 3, Table 7.3.4.2.3.2-1)
|
Derivation Path: Table 8.4-3 |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
As defined in Table 8.4-3 with the following exceptions: |
|||||
|
LPP-Message ::= SEQUENCE { |
|||||
|
lpp-MessageBody CHOICE { |
|||||
|
c1 CHOICE { |
|||||
|
requestLocationInformation SEQUENCE { |
|||||
|
criticalExtensions CHOICE { |
|||||
|
c1 CHOICE { |
|||||
|
requestLocationInformation-r9 SEQUENCE { |
|||||
|
commonIEsRequestLocationInformation SEQUENCE { |
|||||
|
locationInformationType |
locationMeasurementsRequired |
||||
|
} |
|||||
|
ecid-RequestLocationInformation SEQUENCE { |
|||||
|
requestedMeasurements |
Test Configuration D: bits 0, 1, 2 = 1 |
||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
|
} |
|||||
Table 9.3.4.2.3.3-6: LPP Provide Capabilities. (step 1c, Table 7.3.4.2.3.2-1)
|
Derivation Path: Table 7.3.4.2.3.3-8a |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.4.2.3.3-8a with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.4.2.3.3-7: LPP Provide Location Information (steps 4 a1, 4b1 and 4b3, Table 7.3.4.2.3.2-1)
|
Derivation Path: Table 7.3.4.2.3.3-9 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 7.3.4.2.3.3-9 with the following exceptions: |
|||
|
LPP-Message ::= SEQUENCE { |
|||
|
lpp-MessageBody CHOICE { |
|||
|
c1 CHOICE { |
|||
|
provideLocationInformation SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
provideLocationInformation-r9 SEQUENCE { |
|||
|
nr-ECID-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 22 |
Rel-16 onwards |
|
|
nr-ECID-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
||
|
nr-ECID-Error-r16 |
May be present |
||
|
} |
|||
|
nr-Multi-RTT-ProvideLocationInformation-r16 SEQUENCE { |
Present for sub-test 19 |
Rel-16 onwards |
|
|
nr-Multi-RTT-SignalMeasurementInformation-r16 |
Present. Any value acceptable |
||
|
nr-Multi-RTT-Error-r16 |
May be 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 |
May be present |
||
|
nr-dl-AoD-LocationInformation-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-LocationInformation-r16 |
Not present |
||
|
nr-DL-TDOA-Error-r16 |
May be present |
||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
9.3.4.3 E-SMLC Initiated Position Measurement without assistance data: UE‑Based
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.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 location request for UE-based and the UE
requires assistance data in order to fulfil the location request }
then { UE sends a REQUEST ASSISTANCE DATA message followed by a PROVIDE LOCATION INFORMATION
message containing a location estimate }
}
9.3.4.3.2 Conformance requirements
As defined in clause 7.3.4.3.2.
9.3.4.3.3 Test description
9.3.4.3.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.3.4.3.3.2-1): NR Cell 1.
– Satellite signals (sub-test 15): as specified in 8.2.1.
– MBS signals (sub-test 16): as specified in 8.2.4.
– WLAN signals (sub-test 17): as specified in 8.2.5.
– Sub-test 20: NR Cell 1 and NR Cell 2, as specified in 8.2.10.
– Sub-test 21: NR Cell 1, NR Cell 2 and NR Cell 3, as specified in 8.2.11.
For Test Configuration D (Table 9.3.4.3.3.2-1): LTE Cell 1.
– Satellite signals (sub-test 15): as specified in 8.2.1.
– MBS signals (sub-test 16): as specified in 8.2.4.
– WLAN signals (sub-test 17): as specified in 8.2.5.
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.3.4.3.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– For Test Configuration D (Table 9.3.4.3.3.2-1): FFS.
Related PICS/PIXIT Statements:
Method of triggering an LPP Request Assistance Data message.
9.3.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.3.4.3.3.2-0 below:
Table 9.3.4.3.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
15 |
UE supporting GNSS(1) |
|
16 |
UE supporting MBS (Rel-14 onwards) |
|
17 |
UE supporting WLAN (Rel-14 onwards) |
|
18 |
UE supporting Sensor (Rel-14 onwards) |
|
20 |
UE supporting DL-AoD (Rel-16 onwards) |
|
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 9.3.4.3.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.4.3 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in Table 7.3.4.3.3.2-1.
9.3.4.3.3.3 Specific message contents
As defined in clause 7.3.4.3.3.3, with the following exceptions:
Table 9.3.4.3.3.3-0 replaces Table 7.3.4.3.3.3-1, Table 9.3.4.3.3.3-1 replaces Table 7.3.4.3.3.3-2, Table 9.3.4.3.3.3-2 replaces Table 7.3.4.3.3.3-3, Table 9.3.4.3.3.3-2a replaces Table 7.3.4.3.3.3-9, Table 9.3.4.3.3.3-3 replaces Table 7.3.4.3.3.3-6, Table 9.3.4.3.3.3-4 replaces Table 7.3.4.3.3.3-7, Table 9.3.4.3.3.3-5 replaces Table 7.3.4.3.3.3-7a, Table 9.3.4.3.3.3-6 replaces Table 7.3.4.3.3.3-8 and Table 9.3.4.3.3.3-7 replaces Table 7.3.4.3.3.3-10.
Table 9.3.4.3.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.3.3.2-1)
|
Derivation Path: 38.509 clause 6.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.3.3.3-1 with the following exceptions: |
||||
|
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 20: DL-AoD Sub-test 21: DL-TDOA |
||
Table 9.3.4.3.3.3-1: DLInformationTransfer (steps 1a, 1c, 2, 4 and 5a, Table 7.3.4.3.3.2-1)
|
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.3.4.3.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.3.3.3-2: DL NAS TRANSPORT (steps 1a, 1c, 2, 4 and 5a, Table 7.3.4.3.3.2-1)
|
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 1a: Set according to Table 8.4-2 |
LPP Request Capabilities. |
||
|
Step 2: Set according to Table 9.3.4.3.3.3-2b |
LPP Request Location Information |
|||
|
Step 4: Set according to Table 9.3.4.3.3.3-2a |
LPP Provide Assistance Data |
|||
|
Steps 1c and 5a: Set according to Table 7.3.4.3.3.3-11 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.4.3.3.3-2a: LPP Provide Assistance Data (step 4, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 8.4-1 |
|||||||
|
Information Element |
Value/remark |
Comment |
Condition |
||||
|
LPP-Message ::= SEQUENCE { |
|||||||
|
transactionID SEQUENCE { |
|||||||
|
initiator |
targetDevice |
||||||
|
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in the LPP Request Assistance Data message in step 3 Table 7.3.4.3.3.2-1 |
|||||
|
} |
|||||||
|
endTransaction |
TRUE |
||||||
|
sequenceNumber |
Not present |
||||||
|
acknowledgement SEQUENCE { |
Present if acknowledgement field is included by the UE at step 3, Table 7.3.4.3.3.2-1. |
||||||
|
ackRequested |
FALSE |
||||||
|
ackIndicator |
(0..255) |
Contains the same value as the sequenceNumber in step 3, Table 7.3.4.3.3.2-1 |
|||||
|
} |
|||||||
|
lpp-MessageBody CHOICE { |
|||||||
|
c1 CHOICE { |
|||||||
|
provideAssistanceData SEQUENCE { |
|||||||
|
criticalExtensions CHOICE { |
|||||||
|
c1 CHOICE { |
|||||||
|
provideAssistanceData-r9 SEQUENCE { |
|||||||
|
a-gnss-ProvideAssistanceData |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2‑1 which are available according to TS 37.571-5 [12]. |
||||||
|
sensor-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 8.4.1.5. |
Rel-14 onwards |
|||||
|
tbs-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 8.4.1.3. |
Rel-14 onwards |
|||||
|
wlan-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 8.4.1.4. |
Rel-14 onwards |
|||||
|
nr-DL-AoD-ProvideAssistanceData-r16 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 8.4.1.7. |
Rel-16 onwards |
|||||
|
nr-DL-TDOA-ProvideAssistanceData-r16 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.3.3.2-1 which are available according to subclause 8.4.1.8. |
Rel-16 onwards |
|||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
Table 9.3.4.3.3.3-2b: LPP Request Location Information (step 2, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 5.4-3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-3 with the following exceptions: |
||||
|
locationInformationType |
locationEstimateRequired |
|||
|
a-gnss-RequestLocationInformation |
Set according to Table 7.3.4.3.3.3-5 |
Sub-test 15 |
||
|
sensor-RequestLocationInformation-r14 |
Set according to Table 7.3.4.3.3.3-5B |
Rel-14 onwards |
Sub-test 18 |
|
|
tbs-RequestLocationInformation-r13 |
Set according to Table 7.3.4.3.3.3-5A |
Rel-13 onwards |
Sub-test 16 |
|
|
wlan-RequestLocationInformation-r14 |
Set according to Table 7.3.4.3.3.3-5C |
Rel-14 onwards |
Sub-test 17 |
|
|
nr-DL-AoD-RequestLocationInformation-r16 |
As defined in Table 9.3.4.3.3.3-2c |
Rel-16 onwards |
Sub-test 20 |
|
|
nr-DL-TDOA-RequestLocationInformation-r16 |
As defined in Table 9.3.4.3.3.3-2d |
Rel-16 onwards |
Sub-test 21 |
|
Table 9.3.4.3.3.3-2c: NR DL-AoD Request Location Information (step 2, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 8.4-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-6 with the following exceptions: |
|||
|
nr-AssistanceAvailability-r16 |
TRUE |
||
Table 9.3.4.3.3.3-2d: NR DL-TDOA Request Location Information (step 2, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 8.4-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-7 with the following exceptions: |
|||
|
nr-AssistanceAvailability-r16 |
TRUE |
||
Table 9.3.4.3.3.3-3: ULInformationTransfer (steps 1b, 3 and 5, Table 7.3.4.3.3.2-1)
|
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.3.4.3.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.3.3.3-4: UL NAS TRANSPORT (steps 1b, 3 and 5, Table 7.3.4.3.3.2-1)
|
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 1b: Set according to Table 9.3.4.3.3.3-5 |
LPP Provide Capabilities |
||
|
Step 3: Set according to Table 9.3.4.3.3.3-6 |
LPP Request Assistance Data |
|||
|
Step 5: Set according to Table 9.3.4.3.3.3-7 |
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 1 Table 7.3.4.3.3.2‑1) |
||
Table 9.3.4.3.3.3-5: LPP Provide Capabilities. (step 1b, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 7.3.4.3.3.3-7a |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.4.3.3.3-7a with the following exceptions: |
||||||||
|
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 1a, Table 7.3.4.3.3.2-1 |
||||||
|
} |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-DL-AoD-RequestCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
nr-DL-TDOA-RequestCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.4.3.3.3-6: LPP Request Assistance Data (step 3, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 7.3.4.3.3.3-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.3.3.3-8 with the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData-r9 SEQUENCE { |
||||
|
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.3.4.3.3.3-7: LPP Provide Location Information (step 5, Table 7.3.4.3.3.2-1)
|
Derivation Path: Table 7.3.4.3.3.3-10 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.3.3.3-10 with the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation-r9 SEQUENCE { |
||||
|
nr-DL-AoD-ProvideLocationInformation-r16 |
Present for sub-test 20 |
Rel-16 onwards |
||
|
nr-DL-TDOA-ProvideLocationInformation-r16 |
Present for sub-test 21 |
Rel-16 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
9.3.4.4 E-SMLC Initiated Position Measurement without assistance data: UE‑Assisted
Editor’s note: Test configuration D is incomplete:
- The corresponding attach procedure for NG-RAN E-UTRA has not yet been defined.
- The message contents need to be revised for Test Configuration D.
9.3.4.4.1 Test Purpose (TP)
with { a NAS signalling connection existing }
ensure that {
when { UE has no assistance data stored and receives a location request for UE-assisted and the
UE requires assistance data in order to fulfil the location request }
then { UE sends a REQUEST ASSISTANCE DATA message followed by a PROVIDE LOCATION INFORMATION
message containing location measurements }
}
9.3.4.4.2 Conformance requirements
As defined in clause 7.3.4.4.2.
9.3.4.4.3 Test description
9.3.4.4.3.1 Pre-test conditions
System Simulator:
For Test Configuration B (Table 9.3.4.4.3.2-1):
– Sub-tests 15, 16, 17, 18, 19, 20: NR Cell 1.
– Sub-tests 5 and 7: NR Cell 1 and independent LTE Cell 1 and LTE Cell 2 as specified in 8.2.2.
– Satellite signals (sub-test 15): as specified in 8.2.1.
– MBS signals (sub-test 16): as specified in 8.2.4.
– WLAN signals (sub-test 17): as specified in 8.2.5.
– Sub-test 21: NR Cell 1 and NR Cell 2, as specified in 8.2.11.
For Test Configuration D (Table 9.3.4.4.3.2-1):
– Sub-tests 15, 16, 17, 18: LTE Cell 1.
– Sub-tests 5 and 7: LTE Cell 1 and LTE Cell 2, as specified in 8.2.2.
– Satellite signals (sub-test 15): as specified in 8.2.1.
– MBS signals (sub-test 16): as specified in 8.2.4.
– WLAN signals (sub-test 17): as specified in 8.2.5.
UE:
The UE shall begin the test with no assistance data stored.
Preamble:
– For Test Configuration B (Table 9.3.4.4.3.2-1): The UE is in state 3N-A as defined in TS 38.508-1 [30], subclause 4.4A on NR Cell 1.
– Sub-test 5 and 7: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.4.3.1-1 for the configuration of measurement gaps for OTDOA (LTE).
– Sub-test 19: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.4.3.1-1 for the configuration of measurement gaps for Muti-RTT and then the SS shall execute the steps in Table 9.3.4.4.3.1-2 for the configuration of UL-SRS for Muti-RTT.
– Sub-test 20: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.4.3.1-1 for the configuration of measurement gaps for DL-AoD.
– Sub-test 21: After the UE is in state 3N-A, the SS shall execute the steps in Table 9.3.4.4.3.1-1 for the configuration of measurement gaps for DL-TDOA.
Table 9.3.4.4.3.1-1: Configuration of measurement gaps
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.1-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
Table 9.3.4.4.3.1-2: Configuration of UL-SRS for Multi-RTT
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends an RRCReconfiguration message as in Table 8.3.2-1. |
<– |
RRCReconfiguration |
– |
– |
|
2 |
The UE sends an RRCReconfigurationComplete message. |
–> |
RRCReconfigurationComplete |
– |
– |
– For Test Configuration D (Table 9.3.4.4.3.2-1): FFS.
Related PICS/PIXIT Statements:
Method of triggering an LPP Request Assistance Data message.
9.3.4.4.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.3.4.4.3.2-0 below:
Table 9.3.4.4.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
5 |
UE supporting OTDOA (LTE) (Rel-15 onwards) |
|
7 |
UE supporting GNSS(1) and OTDOA (LTE) (Rel-15 onwards) |
|
15 |
UE supporting GNSS(1) |
|
16 |
UE supporting MBS (Rel-14 onwards) |
|
17 |
UE supporting WLAN (Rel-14 onwards) |
|
18 |
UE supporting Sensor (Rel-14 onwards) |
|
19 |
UE supporting Multi-RTT (Rel-16 onwards) |
|
20 |
UE supporting DL-AoD (Rel-16 onwards) |
|
21 |
UE supporting DL-TDOA (Rel-16 onwards) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 9.3.4.4.3.2-1: Test Configuration
|
Test Configuration |
Network Deployment Type |
Test Implementation |
|
A |
EN-DC |
Functionality is tested by test case 7.3.4.4 |
|
B |
NG-RAN NR |
|
|
C |
NE-DC |
Functionality is tested by test configuration B |
|
D |
NG-RAN E-UTRA |
|
|
E |
NGEN-DC |
Functionality is tested by test configuration D |
Main behaviour as defined in Table 7.3.4.4.3.2-1.
For sub-test 19 or sub-test 20 or sub-test 21, the SS sends the RESET UE POSITIONING STORED INFORMATION message to the UE at step 1. Then the stored assistance data in the UE are cleared.
9.3.4.4.3.3 Specific message contents
As defined in clause 7.3.4.4.3.3, with the following exceptions:
Table 9.3.4.4.3.3-0 replaces Table 7.3.4.4.3.3-1, Table 9.3.4.4.3.3-1 replaces Table 7.3.4.4.3.3-3, Table 9.3.4.4.3.3-2 replaces Table 7.3.4.4.3.3-4,Table 9.3.4.4.3.3-2a replaces Table 7.3.4.4.3.3-10, Table 9.3.4.4.3.3-3 replaces Table 7.3.4.4.3.3-7, Table 9.3.4.4.3.3-4 replaces Table 7.3.4.4.3.3-8, Table 9.3.4.4.3.3-2b replaces Table 7.3.4.4.3.3-5, Table 9.3.4.4.3.3-5 replaces Table 7.3.4.4.3.3-8a, Table 9.3.4.4.3.3-6 replaces Table 7.3.4.4.3.3-9 and Table 9.3.4.4.3.3-7 replaces Table 7.3.4.4.3.3-11.
Table 9.3.4.4.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 1, Table 7.3.4.4.3.2-1)
|
Derivation Path: 38.509 clause 6.6 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.4.3.3-1 with the following exceptions: |
||||
|
UE Positioning Technology |
Sub-test 19: 0 0 0 0 0 1 1 0 Sub-test 20: 0 0 0 0 1 0 0 0 Sub-test 21: 0 0 0 0 0 1 1 1 |
Sub-test 19: Multi-RTT Sub-test 20: DL-AoD Sub-test 21: DL-TDOA |
||
Table 9.3.4.4.3.3-1: DLInformationTransfer (steps 1b, 1d, 2, 4, 4b, 5a2, 5b2 and 5b4, Table 7.3.4.4.3.2-1)
|
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.3.4.4.3.3-2 |
DL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.4.3.3-2: DL NAS TRANSPORT (steps 1b, 1d, 2, 4, 4b, 5a2, 5b2 and 5b4, Table 7.3.4.4.3.2-1)
|
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 1b: Set according to Table 8.4-2 |
LPP Request Capabilities |
||
|
Step 2: Set according to Table 9.3.4.4.3.3-2b |
LPP Request Location Information |
|||
|
Steps 4 and 4b: Set according to Table 9.3.4.4.3.3-2a |
LPP Provide Assistance Data |
|||
|
Steps 1d, 5a2, 5b2 and 5b4: Set according to Table 7.3.4.4.3.3-12 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
Routing Identifier/Correlation ID |
||
Table 9.3.4.4.3.3-2a: LPP Provide Assistance Data (steps 4 and 4b, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 8.4-1 |
|||||||
|
Information Element |
Value/remark |
Comment |
Condition |
||||
|
LPP-Message ::= SEQUENCE { |
|||||||
|
transactionID SEQUENCE { |
|||||||
|
initiator |
targetDevice |
||||||
|
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in the LPP Request Assistance Data message in step 3 or 4a Table 7.3.4.4.3.2-1. |
|||||
|
} |
|||||||
|
endTransaction |
TRUE |
||||||
|
sequenceNumber |
Not present |
||||||
|
acknowledgement SEQUENCE { |
Present if acknowledgement field is included by the UE at step 3 or 4a, Table 7.3.4.4.3.2-1. |
||||||
|
ackRequested |
FALSE |
||||||
|
ackIndicator |
(0..255) |
Contains the same value as the sequenceNumber in step 3 or 4a, Table 7.3.4.4.3.2-1. |
|||||
|
} |
|||||||
|
lpp-MessageBody CHOICE { |
|||||||
|
c1 CHOICE { |
|||||||
|
provideAssistanceData SEQUENCE { |
|||||||
|
criticalExtensions CHOICE { |
|||||||
|
c1 CHOICE { |
|||||||
|
provideAssistanceData-r9 SEQUENCE { |
|||||||
|
a-gnss-ProvideAssistanceData |
The SS provides the assistance data requested by the UE at step 3 or 4a, Table 7.3.4.4.3.2‑1 which are available according to TS 37.571-5 [12]. |
For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then the SS sends two seperate LPP Provide Assistance Data messages in steps 4 and 4b each containing the relevant assistance data. |
Sub-tests 7, 15 |
||||
|
otdoa-ProvideAssistanceData |
The SS provides the assistance data requested by the UE at step 3 or 4a, Table 7.3.4.4.3.2-1 according to subclause 8.4.1.2. |
For sub-test 7, in case the UE sends two separate LPP Request Assistance Data messages in steps 3 and 4a then the SS sends two seperate LPP Provide Assistance Data messages in steps 4 and 4b each containing the relevant assistance data. |
Sub-tests 5,7 |
||||
|
sensor-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.5. |
Release 14 onwards |
Sub-test 18 |
||||
|
tbs-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.3. |
Release 14 onwards |
Sub-test 16 |
||||
|
wlan-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.4. |
Release 14 onwards |
Sub-test 17 |
||||
|
nr-Multi-RTT-ProvideAssistanceData-r16 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.6. |
Release 16 onwards |
Sub-test 19 |
||||
|
nr-DL-AoD-ProvideAssistanceData-r16 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.7. |
Release 16 onwards |
Sub-test 20 |
||||
|
nr-DL-TDOA-ProvideAssistanceData-r16 |
The SS provides the assistance data requested by the UE at step 3, Table 7.3.4.4.3.2-1 which are available according to subclause 8.4.1.8. |
Release 16 onwards |
Sub-test 21 |
||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
|
} |
|||||||
Table 9.3.4.4.3.3-2b: LPP Request Location Information (step 2, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 7.3.4.4.3.3-5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.4.3.3-5 with the following exceptions: |
||||
|
nr-Multi-RTT-RequestLocationInformation-r16 |
As defined in Table 9.3.4.4.3.3-2c |
Rel-16 onwards |
Sub-test 19 |
|
|
nr-DL-AoD-RequestLocationInformation-r16 |
As defined in Table 9.3.4.4.3.3-2d |
Rel-16 onwards |
Sub-test 20 |
|
|
nr-DL-TDOA-RequestLocationInformation-r16 |
As defined in Table 9.3.4.4.3.3-2e |
Rel-16 onwards |
Sub-test 21 |
|
Table 9.3.4.4.3.3-2c: NR Multi-RTT Request Location Information (step 2, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 8.4-5 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-5 with the following exceptions: |
|||
|
nr-AssistanceAvailability-r16 |
TRUE |
||
Table 9.3.4.4.3.3-2d: NR DL-AoD Request Location Information (step 2, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 8.4-6 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-6 with the following exceptions: |
|||
|
nr-AssistanceAvailability-r16 |
TRUE |
||
Table 9.3.4.4.3.3-2e: NR DL-TDOA Request Location Information (step 2, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 8.4-7 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 8.4-7 with the following exceptions: |
|||
|
nr-AssistanceAvailability-r16 |
TRUE |
||
Table 9.3.4.4.3.3-3: ULInformationTransfer (steps 1c, 3, 4a, 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)
|
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.3.4.4.3.3-4 |
UL NAS TRANSPORT |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
Table 9.3.4.4.3.3-4: UL NAS TRANSPORT (steps 1c, 3, 4a, 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)
|
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 1c: Set according to Table 9.3.4.4.3.3-5 |
LPP Provide Capabilities |
||
|
Steps 3 and 4a: Set according to Table 9.3.4.4.3.3-6 |
LPP Request Assistance Data |
|||
|
Steps 5a1, 5b1 and 5b3: Set according to Table 9.3.4.4.3.3-7 |
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 1 Table 7.3.4.4.3.2‑1) |
||
Table 9.3.4.4.3.3-5: LPP Provide Capabilities. (step 1c, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 7.3.4.4.3.3-8a |
||||||||
|
Information Element |
Value/remark |
Comment |
Condition |
|||||
|
As defined in Table 7.3.4.4.3.3-8a with the following exceptions: |
||||||||
|
LPP-Message ::= SEQUENCE { |
||||||||
|
lpp-MessageBody CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities SEQUENCE { |
||||||||
|
criticalExtensions CHOICE { |
||||||||
|
c1 CHOICE { |
||||||||
|
provideCapabilities-r9 SEQUENCE { |
||||||||
|
otdoa-ProvideCapabilities |
Present or not present dependent on pc_OTDOA_onNR |
|||||||
|
ecid-ProvideCapabilities |
Present or not present dependent on pc_ECID_onNR |
|||||||
|
nr-Multi-RTT-ProvideCapabilities-r16 |
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 |
||||||
|
nr-UL-ProvideCapabilities-r16 |
Dependent on UE capabilities |
Rel-16 onwards |
||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
|
} |
||||||||
Table 9.3.4.4.3.3-6: LPP Request Assistance Data (steps 3 and 4a, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 7.3.4.4.3.3-9 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 7.3.4.4.3.3-9 with the following exceptions: |
||||
|
LPP-Message ::= SEQUENCE { |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData-r9 SEQUENCE { |
||||
|
nr-Multi-RTT-RequestAssistanceData-r16 |
Present for sub-test 19 |
Rel-16 onwards |
||
|
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.3.4.4.3.3-7: LPP Provide Location Information (steps 5a1, 5b1 and 5b3, Table 7.3.4.4.3.2-1)
|
Derivation Path: Table 7.3.4.4.3.3-11 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
As defined in Table 7.3.4.4.3.3-11 with the following exceptions: |
|||
|
LPP-Message ::= SEQUENCE { |
|||
|
lpp-MessageBody CHOICE { |
|||
|
c1 CHOICE { |
|||
|
provideLocationInformation SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
c1 CHOICE { |
|||
|
provideLocationInformation-r9 SEQUENCE { |
|||
|
nr-Multi-RTT-ProvideLocationInformation-r16 |
Present for sub-test 19 |
Rel-16 onwards |
|
|
nr-DL-AoD-ProvideLocationInformation-r16 |
Present for sub-test 20 |
Rel-16 onwards |
|
|
nr-DL-TDOA-ProvideLocationInformation-r16 |
Present for sub-test 21 |
Rel-16 onwards |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||