7.3.2 LPP Transport
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
7.3.2.1 LPP Duplicated Message
7.3.2.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection for EPC-NI-LR session 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 }
}
7.3.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 4.3.
[TS 36.355, clause 4.3.1]
A UE implementing LPP for the control plane solution shall support LPP reliable transport (including all three of duplicate detection, acknowledgement, and retransmission).
The following requirements in subclauses 4.3.2, 4.3.3, and 4.3.4 [LPP] for LPP reliable transport apply only when the capability is supported.
[TS 36.355, clause 4.3.2]
A sender shall include a sequence number in all LPP messages sent for a particular location session. The sequence number shall be distinct for different LPP messages sent in the same direction in the same location session.
…
A receiver shall record the most recent received sequence number for each location session. If a message is received carrying the same sequence number as that last received for the associated location session, it shall be discarded.
7.3.2.1.3 Test description
7.3.2.1.3.1 Pre-test conditions
System Simulator:
– 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.2.1.3.2 Test procedure sequence
Table 7.3.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a LPP message of type Request Capabilities including a sequence number. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
2 |
Immediately after step 1, the SS sends the same LPP message as in step 1. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
3 |
The UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
3a |
IF the UE LPP message at step 3 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
|
4 |
The SS waits for 10 seconds to ensure the UE does not send another LPP message of type Provide Capabilities with the same transaction ID as received in step 1 or 2. |
1 |
P |
||
7.3.2.1.3.3 Specific message contents
Table 7.3.2.1.3.3-1: DLInformationTransfer (steps 1, 2, and 3a, Table 7.3.2.1.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.2.1.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.1.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 1, 2 and 3a, Table 7.3.2.1.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 |
Steps 1 and 2: Set according to Table 7.3.2.1.3.3-3 |
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 7.3.2.1.3.3-3: LPP Request Capabilities (steps 1 and 2, Table 7.3.2.1.3.2-1)
|
Derivation Path: Table 5.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-1 with the following exceptions: |
||||
|
sequenceNumber |
0 |
|||
Table 7.3.2.1.3.3-4: ULInformationTransfer (step 3, Table 7.3.2.1.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.2.1.3.3-5 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.1.3.3-5: UPLINK GENERIC NAS TRANSPORT (step 3, Table 7.3.2.1.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 |
Set according to Table 7.3.2.1.3.3-6 |
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 7.3.2.1.3.3-6: LPP Provide Capabilities (step 3, Table 7.3.2.1.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 1, Table 7.3.2.1.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.2.1.3.3-7: LPP Acknowledgement (step 3a, Table 7.3.2.1.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 3, Table 7.3.2.1.3.2‑1. |
||
|
} |
||||
|
lpp-MessageBody |
Not present. |
|||
|
} |
||||
7.3.2.2 LPP Acknowledgment
7.3.2.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection for EPC-NI-LR session existing }
ensure that {
when { UE receives a LPP message carrying an acknowledgement request indicator }
then { UE returns an acknowledgement response }
}
7.3.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 4.3.
[TS 36.355, clause 4.3.1]
A UE implementing LPP for the control plane solution shall support LPP reliable transport (including all three of duplicate detection, acknowledgement, and retransmission).
The following requirements in subclauses 4.3.2, 4.3.3, and 4.3.4 [LPP] for LPP reliable transport apply only when the capability is supported.
[TS 36.355, clause 4.3.3.1]
Upon reception of an LPP message which includes the IE ackRequested set to TRUE, a receiver returns an LPP message with an acknowledgement response, i.e., that includes the ackIndicator IE set to the same sequence number of the message being acknowledged.
An acknowledgment response may contain no LPP message body (in which case only the sequence number being acknowledged is significant); alternatively, the acknowledgment may be sent in an LPP message along with an LPP message body.
7.3.2.2.3 Test description
7.3.2.2.3.1 Pre-test conditions
System Simulator:
– 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.2.2.3.2 Test procedure sequence
Table 7.3.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a LPP message of type Request Capabilities including a request for acknowledgement. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
2 Option 1 |
Option 1: The UE sends an acknowledgement along with an LPP message of type Provide Capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES, incl. acknowledgement response) |
1 |
P |
|
2 Option 2 |
Option 2: The UE sends a LPP Acknowledgement response, followed by a LPP message of type Provide Capabilities. |
–> –> |
ULInformationTransfer (LPP ACKNOWLEDGEMENT) ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
1 |
P |
|
3 |
IF the UE LPP message at step 2 includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
7.3.2.2.3.3 Specific message contents
Table 7.3.2.2.3.3-1: DLInformationTransfer (steps 1, and 3, Table 7.3.2.2.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.2.2.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.2.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 1, and 3, Table 7.3.2.2.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 1: Set according to Table 7.3.2.2.3.3-3 |
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 7.3.2.2.3.3-3: LPP Request Capabilities (step 1, Table 7.3.2.2.3.2-1)
|
Derivation Path: Table 5.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-1 with the following exceptions: |
||||
|
sequenceNumber |
0 |
|||
|
acknowledgement SEQUENCE { |
||||
|
ackRequested |
TRUE |
|||
|
ackIndicator |
Not present |
|||
|
} |
||||
Table 7.3.2.2.3.3-4: ULInformationTransfer (step 2, Table 7.3.2.2.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.2.2.3.3-5 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.2.3.3-5: UPLINK GENERIC NAS TRANSPORT (step 2, Table 7.3.2.2.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 2: Set according to Table 7.3.2.2.3.3-6 |
LPP Provide Capabilities |
||
|
Step 2 (Option 2), Set according to Table 7.3.2.2.3.3-7 |
LPP Acknowledgement |
|||
|
Additional information |
Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message |
||
Table 7.3.2.2.3.3-6: LPP Provide Capabilities (step 2, Table 7.3.2.2.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 1, Table 7.3.2.2.3.2-1. |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
|||
|
acknowledgement SEQUENCE { |
Present, or not present. Present for Option 1. |
|||
|
ackRequested |
TRUE or FALSE |
|||
|
ackIndicator |
0 (Option 1) Not present (Option 2) |
|||
|
} |
||||
|
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.2.2.3.3-7: LPP Acknowledgement (step 2 – Option 2, Table 7.3.2.2.3.2-1)
|
Derivation Path: 36.355 clause 6.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID |
Not present |
|||
|
endTransaction |
FALSE |
|||
|
sequenceNumber |
Not present |
|||
|
acknowledgement SEQUENCE { |
||||
|
ackRequested |
FALSE |
|||
|
ackIndicator |
0 |
|||
|
} |
||||
|
lpp-MessageBody |
Not present. |
|||
|
} |
||||
Table 7.3.2.2.3.3-8: LPP Acknowledgement (step 3, Table 7.3.2.2.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 2, Table 7.3.2.2.3.2‑1. |
||
|
} |
||||
|
lpp-MessageBody |
Not present. |
|||
|
} |
||||
7.3.2.3 LPP Retransmission
7.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}
}
7.3.2.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.355, clause 4.3.
[TS 36.355, clause 4.3.1]
A UE implementing LPP for the control plane solution shall support LPP reliable transport (including all three of duplicate detection, acknowledgement, and retransmission).
The following requirements in subclauses 4.3.2, 4.3.3, and 4.3.4 [LPP] for LPP reliable transport apply only when the capability is supported.
[TS 36.355, clause 4.3.4.1]
When an LPP message which requires acknowledgement is sent and not acknowledged, it is resent by the sender following a timeout period up to three times. If still unacknowledged after that, the sender aborts all LPP activity for the associated session.
7.3.2.3.3 Test description
7.3.2.3.3.1 Pre-test conditions
System Simulator:
– 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:
– UE supporting sending of acknowledgement request in LPP Provide Capabilities message.
7.3.2.3.3.2 Test procedure sequence
Table 7.3.2.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a LPP message of type Request Capabilities. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
2 |
The UE sends a LPP message of type Provide Capabilities including a request for acknowledgement along with a sequence number. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
3 |
SS does not send an acknowledgement |
– |
– |
||
|
4 |
After an implementation specific timeout period, the UE retransmits the LPP message from step 2 and includes the same sequence number as in step 2. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
1 |
P |
|
5 |
SS does not send an acknowledgement |
– |
– |
||
|
6 |
The UE either proceeds directly to step 10 or after an implementation specific timeout period, the UE retransmits the LPP message from step 2 and includes the same sequence number as in step 2. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
7 |
SS does not send an acknowledgement |
– |
– |
||
|
8 |
The UE either proceeds directly to step 10 or after an implementation specific timeout period, the UE retransmits the LPP message from step 2 and includes the same sequence number as in step 2. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
9 |
SS does not send an acknowledgement |
||||
|
10 |
UE aborts all procedures and activity associated with LPP support for the location session. SS waits for 10 seconds to ensure the UE does not send another LPP message. |
1 |
P |
||
7.3.2.3.3.3 Specific message contents
Table 7.3.2.3.3.3-1: DLInformationTransfer (step 1, Table 7.3.2.3.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.2.3.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.3.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (step 1, Table 7.3.2.3.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 |
Set according to Table 7.3.2.3.3.3-3 |
LPP Request Capabilities |
||
|
Additional information |
Present |
Routing Identifier/ Correlation ID |
||
Table 7.3.2.3.3.3-3: LPP Request Capabilities (step 1, Table 7.3.2.3.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.2.3.3.3-4: ULInformationTransfer (steps 2, 4, 6, and 8, Table 7.3.2.3.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.2.3.3.3-5 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.3.2.3.3.3-5: UPLINK GENERIC NAS TRANSPORT (steps 2, 4, 6, and 8, Table 7.3.2.3.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 |
Set according to Table 7.3.2.3.3.3-6 |
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 |
||
Table 7.3.2.3.3.3-6: LPP Provide Capabilities (steps 2, 4, 6, and 8, Table 7.3.2.3.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 1 Table 7.3.2.3.3.2-1. |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
|||
|
acknowledgement SEQUENCE { |
||||
|
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 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||