7.3.3 LPP Error Handling
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
7.3.3.1 Void
7.3.3.1A Void
7.3.3.1B LPP Requested Method not Supported – UE-Assisted
7.3.3.1B.1 Test Purpose (TP)
(1)
with { a UE supporting at least one of UE-assisted GNSS, UE-assisted OTDOA, UE-assisted ECID, UE-assisted WLAN, UE-assisted Bluetooth, UE-assisted Sensor or UE-assisted MBS but not all of them }
and with { a NAS signalling connection for EPC-NI-LR session 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}
}
7.3.3.1B.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.355, clauses 5.3.3 and 5.4.3.
[TS 36.355, clause 5.3.3]
Upon receiving a RequestLocationInformation message, the target device shall:
1> if the requested information is compatible with the target device capabilities and configuration:
[…]
1> otherwise:
2> if one or more positioning methods are included that the target device does not support:
3> continue to process the message as if it contained only information for the supported positioning methods;
3> handle the signalling content of the unsupported positioning methods by LPP error detection as in 5.4.3.
[TS 36.355, clause 5.4.3]
Upon receiving any LPP message, the receiving entity shall attempt to decode the message and verify the presence of any errors and:
1> if the message type is an LPP RequestAssistanceData or RequestLocationInformation and some or all of the requested information is not supported:
2> return any information that can be provided in a normal response, which includes indications on other information that is not supported.
7.3.3.1B.3 Test description
7.3.3.1B.3.1 Pre-test conditions
System Simulator:
– If OTDOA is supported by the UE: Cells 1 and 2, as specified in 5.2.2.
– If ECID is supported by the UE: Cells 1 and 2, as specified in 5.2.3. If OTDOA is also supported then Cells 1 and 2 are as specified in 5.2.2.
– If GNSS is supported by the UE: Cell 1 and satellite signals, as specified in 5.2.1. If OTDOA is also supported then Cell 1 is as specified in 5.2.2.
– If WLAN is supported by the UE: Cell 1 and WLAN signals, as specified in 5.2.5.
– If MBS is supported by the UE: Cell 1 and MBS signals, as specified in 5.2.4.
– If Bluetooth is supported by the UE: Cell 1 and Bluetooth signals, as specified in 5.2.6.
– If Sensor is supported by the UE: Cell 1.
UE:
– –
Preamble:
– The UE is in state Generic RB Established (state 3) according to 3GPP TS 36.508 [8].
Related PICS/PIXIT Statements:
– –
7.3.3.1B.3.2 Test procedure sequence
Table 7.3.3.1B.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0 |
The SS sends a LPP message of type Request Capabilities. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
0a |
The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
0b |
IF the UE LPP message at step 0a includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
|
1 |
IF the UE supports any positioning method other than ECID or Bluetooth, THEN the SS sends a LPP message of type Provide Assistance Data containing the data for all supported positioning methods. |
<– |
DLInformationTransfer (LPP PROVIDE ASSISTANCE DATA) |
– |
– |
|
2 |
The SS sends a LPP message of type Request Location Information including all specified positioning methods. |
<– |
DLInformationTransfer (LPP REQUEST LOCATION INFORMATION) |
– |
– |
|
3 |
The UE sends a LPP message of type Provide Location Information including information for the supported method(s). |
–> |
ULInformationTransfer (LPP PROVIDE LOCATION INFORMATION) |
1 |
P |
|
3a |
IF the UE LPP message at step 3 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
7.3.3.1B.3.3 Specific message contents
Table 7.3.3.1B.3.3-1: DLInformationTransfer (steps 0, 0b, 1, 2 and 3a, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 36.331 clause 6.2.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
DLInformationTransfer ::= SEQUENCE { |
||||
|
rrc-TransactionIdentifier |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
dlInformationTransfer-r8 SEQUENCE { |
||||
|
dedicatedInfoType CHOICE { |
||||
|
dedicatedInfoNAS OCTET STRING |
Set according to Table 7.3.3.1B.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.3.1B.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 0, 0b, 1, 2 and 3a, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 24.301 Table 8.2.31.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
0111 |
EPS mobility management messages |
||
|
Security header type |
0000 |
Plain NAS message |
||
|
Downlink generic NAS transport message identity |
01101000 |
Downlink generic NAS transport |
||
|
Generic message container type |
00000001 |
LTE Positioning Protocol (LPP) message container |
||
|
Generic message container |
Step 0: Set according to Table 7.3.3.1B.3.3-2a |
LPP Request Capabilities. |
||
|
Step 1: Set according to Table 7.3.3.1B.3.3-3 |
LPP Provide Assistance Data |
|||
|
Step 2: Set according to Table 7.3.3.1B.3.3-4 |
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 7.3.3.1B.3.3-2a: LPP Request Capabilities (step 0, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 5.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-1 |
||||
Table 7.3.3.1B.3.3-3: LPP Provide Assistance data (step 1, Table 7.3.3.1B.3.2-1)
|
Derivation Path: Table 5.4-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-2 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 5.4 |
|||
|
otdoa-ProvideAssistanceData |
Present if UE supports UE-assisted OTDOA. As defined in clause 5.4 |
|||
|
sensor-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted Sensor. As defined in clause 5.4 |
Rel-14 onwards |
||
|
tbs-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted MBS. As defined in clause 5.4 |
Rel-14 onwards |
||
|
wlan-ProvideAssistanceData-r14 |
Present if UE supports UE-assisted WLAN. As defined in clause 5.4 |
Rel-14 onwards |
||
Table 7.3.3.1B.3.3-4: 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 |
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 |
||
Table 7.3.3.1B.3.3-5: ULInformationTransfer (steps 0a and 3, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 36.331 clause 6.2.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
ULInformationTransfer ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
ulInformationTransfer-r8 SEQUENCE { |
||||
|
dedicatedInfoType CHOICE { |
||||
|
dedicatedInfoNAS OCTET STRING |
Set according to Table 7.3.3.1B.3.3-6 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.3.1B.3.3-6: UPLINK GENERIC NAS TRANSPORT (steps 0a and 3, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 24.301 Table 8.2.32.1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Protocol discriminator |
0111 |
EPS mobility management messages |
||
|
Security header type |
0000 |
Plain NAS message |
||
|
Uplink generic NAS transport message identity |
01101001 |
Uplink generic NAS transport |
||
|
Generic message container type |
00000001 |
LTE Positioning Protocol (LPP) message container |
||
|
Generic message container |
Step 0a: Set according to Table 7.3.3.1B.3.3-6a |
LPP Provide Capabilities |
||
|
Step 3: Set according to Table 7.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 0 or 2 Table 7.3.3.1B.3.2-1) |
||
Table 7.3.3.1B.3.3-6a: LPP Provide Capabilities (step 0a, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 36.355 clause 6.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in the LPP Request Capabilities message in step 0, Table 7.3.3.1B.3.2-1 |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
|||
|
acknowledgement SEQUENCE { |
Present, or not present |
|||
|
ackRequested |
TRUE |
|||
|
ackIndicator |
Not present |
|||
|
} |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideCapabilities SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideCapabilities-r9 SEQUENCE { |
||||
|
commonIEsProvideCapabilities |
Dependent on UE capabilities |
Rel-14 onwards |
||
|
a-gnss-ProvideCapabilities |
Dependent on UE capabilities |
|||
|
otdoa-ProvideCapabilities |
Dependent on UE capabilities |
|||
|
ecid-ProvideCapabilities |
Dependent on UE capabilities |
|||
|
epdu-ProvideCapabilities |
Not present |
|||
|
sensor-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-13 onwards |
||
|
tbs-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-13 onwards |
||
|
wlan-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-13 onwards |
||
|
bt-ProvideCapabilities-r13 |
Dependent on UE capabilities |
Rel-13 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.3.1B.3.3-7: LPP Provide Location Information (step 3, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 36.355 clause 6.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID SEQUENCE { |
||||
|
Initiator |
locationServer |
|||
|
transactionNumber |
(0..255) |
Contains the same value as the corresponding field in LPP Request Location Information message in step 2, Table 7.3.3.1B.3.1-1 |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
|||
|
acknowledgement SEQUENCE { |
Present, or not present |
|||
|
ackRequested |
TRUE |
|||
|
ackIndicator |
Not present |
|||
|
} |
||||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideLocationInformation-r9 SEQUENCE { |
||||
|
commonIEsProvideLocationInformation SEQUENCE { |
May be present |
|||
|
locationEstimate |
Not present |
|||
|
velocityEstimate |
Not present |
|||
|
locationError |
Not present |
|||
|
earlyFixReport-r12 |
Not present |
Rel-12 onwards |
||
|
} |
||||
|
a-gnss-ProvideLocationInformation SEQUENCE { |
Present if UE supports UE-assisted A-GNSS. |
|||
|
gnss-SignalMeasurementInformation |
Present for each supported GNSS. Any value acceptable |
|||
|
gnss-LocationInformation |
Not present |
|||
|
gnss-Error |
May be present if UE only supports one GNSS |
|||
|
} |
||||
|
otdoa-ProvideLocationInformation SEQUENCE { |
Present if UE supports UE-assisted OTDOA. |
|||
|
otdoa-SignalMeasurementInformation |
Present. Any value acceptable |
|||
|
otdoa-Error |
May be present |
|||
|
} |
||||
|
ecid-ProvideLocationInformation SEQUENCE { |
Present if UE supports UE-assisted ECID. |
|||
|
ecid-SignalMeasurementInformation |
Present. Any value acceptable |
|||
|
ecid-Error |
May be present |
|||
|
} |
||||
|
epdu-ProvideLocationInformation |
Not present |
|||
|
sensor-ProvideLocationInformation-r13 SEQUENCE { |
Present if UE supports UE-assisted Sensor. |
Rel-13 onwards |
||
|
sensor-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
|
sensor-Error-r13 |
May be present |
|||
|
} |
||||
|
tbs-ProvideLocationInformation-r13 SEQUENCE { |
Present if UE supports UE-assisted MBS |
Rel-13 onwards |
||
|
tbs-MeasurementInformation-r13 SEQUENCE { |
||||
|
measurementReferenceTime-r13 |
Present. Any value acceptable |
|||
|
mbs-SgnMeasList-r13 |
Present. Any value acceptable |
|||
|
} |
||||
|
tbs-Error-r13 |
May be present |
|||
|
} |
||||
|
wlan-ProvideLocationInformation-r13 SEQUENCE { |
Present if UE supports UE-assisted WLAN. |
Rel-13 onwards |
||
|
wlan-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
|
wlan-Error-r13 |
May be present |
|||
|
} |
||||
|
bt-ProvideLocationInformation-r13 SEQUENCE { |
Present if UE supports UE-assisted Bluetooth. |
Rel-13 onwards |
||
|
bt-MeasurementInformation-r13 |
Present. Any value acceptable |
|||
|
bt-Error-r13 |
May be present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.3.1B.3.3-8: LPP Acknowledgement (steps 0b and 3a, Table 7.3.3.1B.3.2-1)
|
Derivation Path: 36.355 clause 6.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID |
Not present |
|||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
Not present |
|||
|
acknowledgement SEQUENCE { |
||||
|
ackRequested |
FALSE |
|||
|
ackIndicator |
(0..255) |
Contains the same value of the sequenceNumber field in step 0a or 3, Table 7.3.3.1B.3.2‑1. |
||
|
} |
||||
|
lpp-MessageBody |
Not present. |
|||
|
} |
||||