7.2 LCS Procedures
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
7.2.1 Location Notification and Privacy Verification
7.2.1.1 Location Notification
7.2.1.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a REGISTER message containing the LCS-LocationNotification Invoke component set to NotifyLocationAllowed }
then { UE notifies the user of the location procedure and terminates the dialogue by sending a
RELEASE COMPLETE message }
}
7.2.1.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171, clause 5.2.1.1.1.
[TS 24.171, clause 5.2.1.1.1]
The network invokes a location notification procedure by sending a REGISTER message containing a LCS-LocationNotification invoke component to the UE. This may be sent either to request verification for MT-LR or to notify about already authorized MT-LR.
…
In the case of location notification no response is required from the UE, the UE shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result.
…
7.2.1.1.3 Test description
7.2.1.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 36.508 [8].
Related PICS/PIXIT Statements:
– UE supporting LCS value added location request notification capability.
7.2.1.1.3.2 Test procedure sequence
Table 7.2.1.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
2 |
The UE notifies the user of the location procedure |
1 |
P |
||
|
3 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
1 |
P |
7.2.1.1.3.3 Specific message contents
Table 7.2.1.1.3.3-1: DLInformationTransfer (step 1, Table 7.2.1.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.2.1.1.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.1.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (step 1, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Set according to Table 7.2.1.1.3.3-3 |
REGISTER |
||
|
Additional information |
Not present. |
|||
Table 7.2.1.1.3.3-3: REGISTER (step 1, Table 7.2.1.1.3.2-1)
|
Derivation Path: 24.080 Table 2.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Register message type |
0011 1011 |
REGISTER |
||
|
Facility |
Invoke = lcs-LocationNotification |
Set according to Table 7.2.1.1.3.3‑4 |
||
Table 7.2.1.1.3.3-4: LCS-LocationNotification (step 1, Table 7.2.1.1.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationArg ::= SEQUENCE { |
||||
|
notificationType |
notifyLocationAllowed |
|||
|
locationType |
currentLocation |
|||
|
lcsClientExternalID SEQUENCE { |
||||
|
externalAddress |
ISDN-AddressString |
|||
|
} |
||||
|
lcsClientName SEQUENCE { |
||||
|
dataCodingScheme |
USSD‑DataCodingScheme |
|||
|
nameString |
NameString |
|||
|
} |
||||
|
} |
||||
Table 7.2.1.1.3.3-5: ULInformationTransfer (step 3, Table 7.2.1.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.2.1.1.3.3-6 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.1.3.3-6: UPLINK GENERIC NAS TRANSPORT (step 3, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Set according to Table 7.2.1.1.3.3-7 |
RELEASE COMPLETE |
||
|
Additional information |
Not present |
|||
Table 7.2.1.1.3.3-7: RELEASE COMPLETE (step 3, Table 7.2.1.1.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Facility |
Return result = LocationNotificationRes |
Set according to Table 7.2.1.1.3.3‑8 |
||
Table 7.2.1.1.3.3-8: LocationNotificationRes (step 3, Table 7.2.1.1.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationRes ::= SEQUENCE { |
||||
|
verificationResponse |
permissionGranted |
|||
|
} |
||||
7.2.1.2 Privacy Verification – Location Allowed if no Response
7.2.1.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a REGISTER message containing the LCS-LocationNotification Invoke component
set to NotifyAndVerify-LocationAllowedIfNoResponse }
then { UE notifies the user of the location procedure and indicates that the default response
is location allowed, allows the user to accept or deny the request and terminates the
dialogue by sending a RELEASE COMPLETE message with verificationResponse set as
appropriate }
}
(2)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a REGISTER message containing the LCS-LocationNotification Invoke component
set to NotifyAndVerify-LocationAllowedIfNoResponse }
then { UE notifies the user of the location procedure and indicates that the default response
is location allowed, allows the user to accept or deny the request and waits for the
user to respond }
}
7.2.1.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171, clause 5.2.1.1.1.
[TS 24.171, clause 5.2.1.1.1]
The network invokes a location notification procedure by sending a REGISTER message containing a LCS-LocationNotification invoke component to the UE. This may be sent either to request verification for MT-LR or to notify about already authorized MT-LR.
In case of privacy verification the UE shall respond to the request by sending a RELEASE COMPLETE message containing the mobile subscriber’s response in a return result component.
If the timer T(LCSN) expires in the network before any response from the UE (e.g. due to no response from the user), the network shall interpret this by applying the default treatment defined in 3GPP TS 23.271 (i.e. disallow location if barred by subscription and allow location if allowed by subscription).
…
7.2.1.2.3 Test description
7.2.1.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 36.508 [8].
Related PICS/PIXIT Statements:
– UE supporting LCS value added location request notification capability.
– px_UeLcsNotification: value for UE LCS Notification timeout timer.
7.2.1.2.3.2 Test procedure sequence
Table 7.2.1.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
2 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
3 |
The UE notifies the user of the location procedure and indicates that location will be allowed in the absence of a response |
1 |
P |
||
|
4 |
The user accepts the location request before timer T(LCSN) expires |
– |
– |
||
|
5 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
1 |
P |
|
6 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
7 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
8 |
The UE notifies the user of the location procedure and indicates that location will be allowed in the absence of a response |
1 |
P |
||
|
9 |
The user denies the location request before timer T(LCSN) expires |
– |
– |
||
|
10 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
1 |
P |
|
11 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
12 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
13 |
The UE notifies the user of the location procedure and indicates that location will be allowed in the absence of a response |
2 |
P |
||
|
14 |
The user does not reply |
– |
– |
||
|
15 |
SS waits until T(LCSN) expires to ensure that the UE does not send a RELEASE COMPLETE message. |
2 |
P |
||
|
16 |
The SS terminates the dialogue by sending a RELEASE COMPLETE message. |
<– |
DLInformationTransfer (RELEASE COMPLETE) |
– |
– |
7.2.1.2.3.3 Specific message contents
Table 7.2.1.2.3.3-1: DLInformationTransfer (steps 1, 6, 11 and 16, Table 7.2.1.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.2.1.2.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.2.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 1, 6, 11 and 16, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Step 1, 6, 11: Set according to Table 7.2.1.2.3.3-3 |
REGISTER |
||
|
Step 16: Set according to Table 7.2.1.2.3.3-11 |
RELEASE COMPLETE |
|||
|
Additional information |
Not present. |
|||
Table 7.2.1.2.3.3-3: REGISTER (steps 1, 6, and 11, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 Table 2.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Register message type |
0011 1011 |
REGISTER |
||
|
Facility |
Invoke = lcs-LocationNotification |
Set according to Table 7.2.1.2.3.3‑4 |
||
Table 7.2.1.2.3.3-4: LCS-LocationNotification (step 1, 6 and 11, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationArg ::= SEQUENCE { |
||||
|
notificationType |
notifyAndVerify-LocationAllowedIfNoResponse |
|||
|
locationType |
currentLocation |
|||
|
lcsClientExternalID SEQUENCE { |
||||
|
externalAddress |
ISDN-AddressString |
|||
|
} |
||||
|
lcsClientName SEQUENCE { |
||||
|
dataCodingScheme |
USSD‑DataCodingScheme |
|||
|
nameString |
NameString |
|||
|
} |
||||
|
} |
||||
Table 7.2.1.2.3.3-5: ULInformationTransfer (steps 5 and 10, Table 7.2.1.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.2.1.2.3.3-6 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.2.3.3-6: UPLINK GENERIC NAS TRANSPORT (steps 5 and 10, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Step 5: Set according to Table 7.2.1.2.3.3-7 |
RELEASE COMPLETE |
||
|
Step 10: Set according to Table 7.2.1.2.3.3-9 |
RELEASE COMPLETE |
|||
|
Additional information |
Not present |
|||
Table 7.2.1.2.3.3-7: RELEASE COMPLETE (step 5, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Facility |
Return result = LocationNotificationRes |
Set according to Table 7.2.1.2.3.3‑8 |
||
Table 7.2.1.2.3.3-8: LocationNotificationRes (step 5, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationRes ::= SEQUENCE { |
||||
|
verificationResponse |
permissionGranted |
|||
|
} |
||||
Table 7.2.1.2.3.3-9: RELEASE COMPLETE (step 10, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Facility |
Return result = LocationNotificationRes |
Set according to Table 7.2.1.2.3.3‑10 |
||
Table 7.2.1.2.3.3-10: LocationNotificationRes (step 10, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationRes ::= SEQUENCE { |
||||
|
verificationResponse |
permissionDenied |
|||
|
} |
||||
Table 7.2.1.2.3.3-11: RELEASE COMPLETE (step 16, Table 7.2.1.2.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Cause |
31 = Normal Unspecified |
Set according to TS 24.008 |
||
7.2.1.3 Privacy Verification – Location not Allowed if No Response
7.2.1.3.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a REGISTER message containing the LCS-LocationNotification Invoke component
set to NotifyAndVerify-LocationNotAllowedIfNoResponse }
then { UE notifies the user of the location procedure and indicates that the default response
is location not allowed, allows the user to accept or deny the request and terminates
the dialogue by sending a RELEASE COMPLETE message with verificationResponse set as
appropriate }
}
(2)
with { a NAS signalling connection existing }
ensure that {
when { UE receives a REGISTER message containing the LCS-LocationNotification Invoke component
set to NotifyAndVerify-LocationNotAllowedIfNoResponse }
then { UE notifies the user of the location procedure and indicates that the default response
is location not allowed, allows the user to accept or deny the request and waits for the user to respond }
}
7.2.1.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171, clause 5.2.1.1.1.
[TS 24.171, clause 5.2.1.1.1]
The network invokes a location notification procedure by sending a REGISTER message containing a LCS-LocationNotification invoke component to the UE. This may be sent either to request verification for MT-LR or to notify about already authorized MT-LR.
In case of privacy verification the UE shall respond to the request by sending a RELEASE COMPLETE message containing the mobile subscriber’s response in a return result component.
If the timer T(LCSN) expires in the network before any response from the UE (e.g. due to no response from the user), the network shall interpret this by applying the default treatment defined in 3GPP TS 23.271 (i.e. disallow location if barred by subscription and allow location if allowed by subscription).
…
7.2.1.3.3 Test description
7.2.1.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 36.508 [8].
Related PICS/PIXIT Statements:
– UE supporting LCS value added location request notification capability.
– px_UeLcsNotification: value for UE LCS Notification timeout timer.
7.2.1.3.3.2 Test procedure sequence
Table 7.2.1.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
2 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
3 |
The UE notifies the user of the location procedure and indicates that location will be not allowed in the absence of a response |
1 |
P |
||
|
4 |
The user accepts the location request before timer T(LCSN) expires |
– |
– |
||
|
5 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
1 |
P |
|
6 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
7 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
8 |
The UE notifies the user of the location procedure and indicates that location will be not allowed in the absence of a response |
1 |
P |
||
|
9 |
The user denies the location request before timer T(LCSN) expires |
– |
– |
||
|
10 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
1 |
P |
|
11 |
The SS sends a REGISTER message containing a LCS-LocationNotification Invoke component. |
<– |
DLInformationTransfer (REGISTER) |
– |
– |
|
12 |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
– |
– |
||
|
13 |
The UE notifies the user of the location procedure and indicates that location will be not allowed in the absence of a response |
2 |
P |
||
|
14 |
The user does not reply |
– |
– |
||
|
15 |
SS waits until T(LCSN) expires to ensure that the UE does not send a RELEASE COMPLETE message. |
2 |
P |
||
|
16 |
The SS terminates the dialogue by sending a RELEASE COMPLETE message. |
<– |
DLInformationTransfer (RELEASE COMPLETE) |
– |
– |
7.2.1.3.3.3 Specific message contents
Table 7.2.1.3.3.3-1: DLInformationTransfer (steps 1, 6, 11 and 16, Table 7.2.1.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.2.1.3.3.3-2 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.3.3.3-2: DOWNLINK GENERIC NAS TRANSPORT (steps 1, 6, 11 and 16, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Step 1, 6, 11: Set according to Table 7.2.1.3.3.3-3 |
REGISTER |
||
|
Step 16: Set according to Table 7.2.1.3.3.3-11 |
RELEASE COMPLETE |
|||
|
Additional information |
Not present. |
|||
Table 7.2.1.3.3.3-3: REGISTER (steps 1, 6, and 11, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 Table 2.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Register message type |
0011 1011 |
REGISTER |
||
|
Facility |
Invoke = lcs-LocationNotification |
Set according to Table 7.2.1.3.3.3‑4 |
||
Table 7.2.1.3.3.3-4: LCS-LocationNotification (step 1, 6 and 11, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationArg ::= SEQUENCE { |
||||
|
notificationType |
notifyAndVerify-LocationNotAllowedIfNoResponse |
|||
|
locationType |
currentLocation |
|||
|
lcsClientExternalID SEQUENCE { |
||||
|
externalAddress |
ISDN-AddressString |
|||
|
} |
||||
|
lcsClientName SEQUENCE { |
||||
|
dataCodingScheme |
USSD‑DataCodingScheme |
|||
|
nameString |
NameString |
|||
|
} |
||||
|
} |
||||
Table 7.2.1.3.3.3-5: ULInformationTransfer (steps 5 and 10, Table 7.2.1.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.2.1.3.3.3-6 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.1.3.3.3-6: UPLINK GENERIC NAS TRANSPORT (steps 5 and 10, Table 7.2.1.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Step 5: Set according to Table 7.2.1.3.3.3-7 |
RELEASE COMPLETE |
||
|
Step 10: Set according to Table 7.2.1.3.3.3-9 |
RELEASE COMPLETE |
|||
|
Additional information |
Not present |
|||
Table 7.2.1.3.3.3-7: RELEASE COMPLETE (step 5, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Facility |
Return result = LocationNotificationRes |
Set according to Table 7.2.1.3.3.3‑8 |
||
Table 7.2.1.3.3.3-8: LocationNotificationRes (step 5, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationRes ::= SEQUENCE { |
||||
|
verificationResponse |
permissionGranted |
|||
|
} |
||||
Table 7.2.1.3.3.3-9: RELEASE COMPLETE (step 10, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Facility |
Return result = LocationNotificationRes |
Set according to Table 7.2.1.3.3.3‑10 |
||
Table 7.2.1.3.3.3-10: LocationNotificationRes (step 10, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LocationNotificationRes ::= SEQUENCE { |
||||
|
verificationResponse |
permissionDenied |
|||
|
} |
||||
Table 7.2.1.3.3.3-11: RELEASE COMPLETE (step 16, Table 7.2.1.3.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
|
Cause |
31 = Normal Unspecified |
Set according to TS 24.008 |
||
7.2.2 EPC MO-LR
7.2.2.1 Autonomous Self Location: UE-based
7.2.2.1.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { an EPC-MO-LR location session is initiated at the UE of type "assistanceData" }
then { UE sends a REGISTER message containing a LCS-MOLR invoke component }
}
(2)
with { UE having performed the last location request operation }
ensure that {
when { UE has received a FACILITY message containing the LCS-MOLR return result component }
then { UE terminates the dialogue by sending a RELEASE COMPLETE message }
}
7.2.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171, clause 5.2.2.1.
[TS 24.171, clause 5.2.2.1.1]
The UE invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.
…
The network shall pass the result of the location procedure to the UE by sending a FACILITY message to the UE containing a LCS-MOLR return result component.
…
After the last location request operation the UE shall terminate the dialogue by sending a RELEASE COMPLETE message.
…
7.2.2.1.3 Test description
7.2.2.1.3.1 Pre-test conditions
System Simulator:
– Cell 1.
– Satellite signals (Sub-test 15): As specified in 5.2.1.
– MBS signals (Sub-test 16): as specified in 5.2.4.
– WLAN signals (Sub-test 17): as specified in 5.2.5.
UE:
–
Preamble:
– The UE is in state Generic RB Established (state 3) according to 3GPP 36.508 [8].
Related PICS/PIXIT Statements:
– Method of triggering an EPC-MO-LR request for assistance data.
7.2.2.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 7.2.2.1.3.2-0 below:
Table 7.2.2.1.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
1 |
Void |
|
2 |
Void |
|
3 |
Void |
|
4 |
Void |
|
8 |
Void |
|
9 |
Void |
|
10 |
Void |
|
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) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 7.2.2.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0 |
The SS sends a RESET UE POSITIONING STORED INFORMATION message. |
<– |
RESET UE POSITIONING STORED INFORMATION |
– |
– |
|
0A |
Cause the UE to initiate MO-LR procedure |
– |
– |
– |
– |
|
1 |
The UE sends a NAS PDU containing an MO-LR Request of type "assistanceData" inside an RRC UL Information Transfer message. The embedded LPP message specifies the type of assistance data. |
–> |
ULInformationTransfer (REGISTER) |
1 |
P |
|
2 |
The SS provides the requested assistance data in an LPP message of type "Assistance Data". |
<– |
DLInformationTransfer (LPP PROVIDE ASSISTANCE DATA) |
– |
– |
|
3 |
The SS sends a FACILITY message containing a LCS-MOLR return result component. |
<– |
DLInformationTransfer (FACILITY) |
– |
– |
|
4 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
2 |
P |
7.2.2.1.3.3 Specific message contents
Table 7.2.2.1.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 0, Table 7.2.2.1.3.2-1)
|
Derivation Path: 36.509 clause 6.9 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UE Positioning Technology |
Sub-test 15: 0 0 0 0 0 0 0 0 Sub-test 16: 0 0 0 0 0 0 1 0 Sub-test 17: 0 0 0 0 0 0 1 1 Sub-test 18: 0 0 0 0 0 1 0 1 |
Sub-test 15: AGNSS Sub-test 16: MBS Sub-test 17: WLAN Sub-test 18: Sensor |
|
Table 7.2.2.1.3.3-1: ULInformationTransfer (steps 1 and 4, Table 7.2.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.2.2.1.3.3-2 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.1.3.3-2: UPLINK GENERIC NAS TRANSPORT (steps 1 and 4, Table 7.2.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 |
00000010 |
Location services message container |
||
|
Generic message container |
Step 1: Set according to Table 7.2.2.1.3.3-3 |
REGISTER |
||
|
Step 4: Set according to Table 7.2.2.1.3.3-11 |
RELEASE COMPLETE |
|||
|
Additional information |
Not present |
|||
Table 7.2.2.1.3.3-3: REGISTER (step 1, Table 7.2.2.1.3.2-1)
|
Derivation Path: 24.080 Table 2.4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Register message type |
xx11 1011 |
REGISTER |
||
|
Facility |
Invoke=LCS-MOLR |
Set according to Table 7.2.2.1.3.3‑4 |
||
|
SS version |
Version 1 or above |
|||
Table 7.2.2.1.3.3-4: LCS-MOLRArg (step 1, Table 7.2.2.1.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LCS-MOLRArg ::= SEQUENCE { |
||||
|
molr-Type |
assistanceData |
|||
|
multiplePositioningProtocolPDUs SEQUENCE |
At least one LPP message of type Request Assistance Data (UE may include additional LPP messages) |
Set according to Table 7.2.2.1.3.3‑5 |
||
|
} |
||||
Table 7.2.2.1.3.3-5: LPP Request Assistance Data (step 1, Table 7.2.2.1.3.2-1)
|
Derivation Path: 36.355 clause 6.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID SEQUENCE { |
||||
|
initiator |
targetDevice |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
|
endTransaction |
FALSE |
|||
|
sequenceNumber |
(0..255) |
|||
|
acknowledgement |
Not present |
|||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
requestAssistanceData-r9 SEQUENCE { |
||||
|
commonIEsRequestAssistanceData |
Present or not present |
|||
|
a-gnss-RequestAssistanceData |
Present for sub-test 15. May be present for other sub-tests |
|||
|
otdoa-RequestAssistanceData |
Not present |
|||
|
epdu-RequestAssistanceData |
Not present |
|||
|
sensor-RequestAssistanceData-r14 |
Present for sub-test 18. May be present for other sub-tests |
Rel-14 onwards |
||
|
tbs-RequestAssistanceData-r14 |
Present for sub-test 16. May be present for other sub-tests |
Rel-14 onwards |
||
|
wlan-RequestAssistanceData-r14 |
Present for sub-test 17. May be present for other sub-tests |
Rel-14 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.1.3.3-6: DLInformationTransfer (steps 2 and 3, Table 7.2.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.2.2.1.3.3-7 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.1.3.3-7: DOWNLINK GENERIC NAS TRANSPORT (steps 2 and 3, Table 7.2.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 |
Step 2: 00000001 |
LTE Positioning Protocol (LPP) message container |
||
|
Step 3: 00000010 |
Location services message container |
|||
|
Generic message container |
Step 2: Set according to Table 7.2.2.1.3.3-8 |
LPP Provide Assistance Data |
||
|
Step 3: Set according to Table 7.2.2.1.3.3-9 |
FACILITY |
|||
|
Additional information |
Step 2: Present |
Routing Identifier/ Correlation ID |
||
|
Step 3: Not present. |
||||
Table 7.2.2.1.3.3-8: LPP Provide Assistance Data (step 2, Table 7.2.2.1.3.2-1)
|
Derivation Path: Table 5.4-2 |
||||
|
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 1 Table 7.2.2.1.3.2-1. |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
Not present |
|||
|
acknowledgement |
Not present |
|||
|
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 1, Table 7.2.2.1.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 1, Table 7.2.2.1.3.2-1 which are available according to subclause 5.4.1.5. |
Rel-14 onwards |
||
|
tbs-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 1, Table 7.2.2.1.3.2-1 which are available according to subclause 5.4.1.3. |
Rel-14 onwards |
||
|
wlan-ProvideAssistanceData-r14 |
The SS provides the assistance data requested by the UE at step 1, Table 7.2.2.1.3.2-1 which are available according to subclause 5.4.1.4. |
Rel-14 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.1.3.3-9: FACILITY (step 3, Table 7.2.2.1.3.2-1)
|
Derivation Path: 24.080 Table 2.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Facility message type |
0011 1010 |
FACILITY |
||
|
Facility |
Return Result=LCS‑MOLRRes |
Set according to Table 7.2.2.1.3.3‑10 |
||
Table 7.2.2.1.3.3-10: LCS-MOLRRes (step 3, Table 7.2.2.1.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LCS-MOLRRes::= SEQUENCE { |
empty |
|||
|
} |
||||
Table 7.2.2.1.3.3-11: RELEASE COMPLETE (step 4, Table 7.2.2.1.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||
7.2.2.2 Basic Self Location: UE-assisted
7.2.2.2.1 Test Purpose (TP)
(1)
with { a NAS signalling connection existing }
ensure that {
when { an EPC-MO-LR location session is initiated at the UE of type "locationEstimate" }
then { UE sends a REGISTER message containing a LCS-MOLR invoke component }
}
(2)
with { UE having performed the last location request operation }
ensure that {
when { UE has received a FACILITY message containing the LCS-MOLR return result component }
then { UE terminates the dialogue by sending a RELEASE COMPLETE message }
}
7.2.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 24.171, clause 5.2.2.1.
[TS 24.171, clause 5.2.2.1.1]
The UE invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.
…
The network shall pass the result of the location procedure to the UE by sending a FACILITY message to the UE containing a LCS-MOLR return result component.
…
After the last location request operation the UE shall terminate the dialogue by sending a RELEASE COMPLETE message.
…
7.2.2.2.3 Test description
7.2.2.2.3.1 Pre-test conditions
System Simulator:
– Sub-tests 11, 12, 13, 14, 15, 16, 17, 18: Cell 1.
– Sub-test 5: Cell 1, Cell 2 as specified in 5.2.2.
– Sub-tests 6 FDD, 6 TDD: Cell 1, Cell 2 as specified in 5.2.3.
– Satellite signals (Sub-test 15): As specified in 5.2.1.
– WLAN signals (Sub-test 11, 17): as specified in 5.2.5.
– MBS signals (Sub-tests 12, 16): as specified in 5.2.4.
– Bluetooth signals (Sub-test 13): as specified in 5.2.6.
UE:
–
Preamble:
– The UE is in state Generic RB Established (state 3) according to 3GPP TS 36.508 [8].
Related PICS/PIXIT Statements:
– Method of triggering an EPC-MO-LR request for a location estimate.
7.2.2.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 7.2.2.2.3.2-0 below:
Table 7.2.2.2.3.2-0: Sub-test case numbers
|
Sub-Test Case Number |
Supported Positioning Methods |
|
1 |
Void |
|
2 |
Void |
|
3 |
Void |
|
4 |
Void |
|
5 |
UE supporting OTDOA |
|
6 FDD |
UE supporting ECID (FDD) |
|
6 TDD |
UE supporting ECID (TDD) |
|
8 |
Void |
|
9 |
Void |
|
10 |
Void |
|
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) |
|
NOTE 1: The GNSS combination of GPS, GLONASS, Galileo, BDS supported by the UE |
|
Table 7.2.2.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0 |
IF NOT sub-test 6 FDD or sub-test 6 TDD THEN The SS sends a RESET UE POSITIONING STORED INFORMATION message. |
<– |
RESET UE POSITIONING STORED INFORMATION |
– |
– |
|
0A |
Cause the UE to initiate MO-LR procedure |
– |
– |
– |
– |
|
1 |
The UE sends a NAS PDU containing an MO-LR Request of type "locationEstimate" inside an RRC UL Information Transfer message. The MO-LR message may optionally include up to three LPP positioning messages. |
–> |
ULInformationTransfer (REGISTER) |
1 |
P |
|
2a |
IF the UE does not include a LPP Provide Capabilities message in step 1 THEN the SS sends a LPP message of type Request Capabilities. |
<– |
DLInformationTransfer (LPP REQUEST CAPABILITIES) |
– |
– |
|
2b |
IF the SS performed step 2a THEN the UE sends a LPP message of type Provide Capabilities including the UE positioning capabilities. |
–> |
ULInformationTransfer (LPP PROVIDE CAPABILITIES) |
– |
– |
|
2c |
IF the UE LPP message at step 2b includes an acknowledgment request THEN SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
|
2d |
IF the UE included a LPP message of type Request Assistance Data in step 1 THEN SS sends a LPP message of type Provide Assistance Data including an error indication without assistance data. |
<– |
DLInformationTransfer (LPP PROVIDE ASSISTANCE DATA) |
– |
– |
|
3 |
IF NOT sub-test 6 FDD or sub-test 6 TDD or sub-test-11 or sub-test 12 or sub-test 13 or sub-test 14 THEN The SS sends a LPP message of type Provide Assistance Data including the assistance data as defined in subclause 5.4.1, dependent on UE capabilities. |
<– |
DLInformationTransfer (LPP PROVIDE ASSISTANCE DATA) |
– |
– |
|
4 |
The SS sends a LPP message of type Request Location Information. |
<– |
DLInformationTransfer (LPP REQUEST LOCATION INFORMATION) |
– |
– |
|
5 |
The UE sends a LPP message of type Provide Location Information including measurements as requested at step 4. |
–> |
ULInformationTransfer (LPP PROVIDE LOCATION INFORMATION) |
– |
– |
|
5a |
IF the UE LPP message at step 5 includes an acknowledgement request THEN the SS sends a LPP Acknowledgement response. |
<– |
DLInformationTransfer (LPP ACKNOWLEDGEMENT) |
– |
– |
|
6 |
The SS sends a FACILITY message containing a LCS-MOLR return result component. |
<– |
DLInformationTransfer (FACILITY) |
– |
– |
|
7 |
The UE terminates the dialogue by sending a RELEASE COMPLETE message. |
–> |
ULInformationTransfer (RELEASE COMPLETE) |
2 |
P |
7.2.2.2.3.3 Specific message contents
Table 7.2.2.2.3.3-0: RESET UE POSITIONING STORED INFORMATION (step 0, Table 7.2.2.2.3.2-1)
|
Derivation Path: 36.509 clause 6.9 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
UE Positioning Technology |
Sub-test 15: 0 0 0 0 0 0 0 0 Sub-test 5: 0 0 0 0 0 0 0 1 Sub-test 11, 17: 0 0 0 0 0 0 1 1 Sub-tests 12, 16: 0 0 0 0 0 0 1 0 Sub-test 13: 0 0 0 0 0 1 0 0 Sub-test 14, 18: 0 0 0 0 0 1 0 1 |
Sub-test 15: AGNSS Sub-test 5: OTDOA Sub-test 11, 17: WLAN Sub-tests 12, 16: MBS Sub-test 13: Bluetooth Sub-test 14, 18: Sensor |
|
Table 7.2.2.2.3.3-1: ULInformationTransfer (steps 1, 2b, 5 and 7, Table 7.2.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.2.2.2.3.3-2 |
UPLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.2.3.3-2: UPLINK GENERIC NAS TRANSPORT (steps 1, 2b, 5 and 7, Table 7.2.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 |
Steps 1 and 7: 00000010 |
Location services message container |
||
|
Step 2b, and 5: 00000001 |
LTE Positioning Protocol (LPP) message container |
|||
|
Generic message container |
Step 1: Set according to Table 7.2.2.2.3.3-3 |
REGISTER |
||
|
Step 2b: Set according to Table 7.2.2.2.3.3-8 |
LPP Provide Capabilities |
|||
|
Step 5: Set according to Table 7.2.2.2.3.3-13 |
LPP Provide Location Information |
|||
|
Step 7: Set according to Table 7.2.2.2.3.3-16 |
RELEASE COMPLETE |
|||
|
Additional information |
Steps 1 and 7: Not present |
|||
|
Step 2b: Present |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 2a Table 7.2.2.2.3.2‑1) |
|||
|
Step 5: |
The UE includes the Routing Identifier received in the Additional Information IE of the DOWNLINK GENERIC NAS TRANSPORT message (step 4 Table 7.2.2.2.3.2‑1) |
|||
Table 7.2.2.2.3.3-3: REGISTER (step 1, Table 7.2.2.2.3.2-1)
|
Derivation Path: 24.080 Table 2.4 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Register message type |
xx11 1011 |
REGISTER |
||
|
Facility |
Invoke=LCS-MOLR |
Set according to Table 7.2.2.2.3.3‑4 |
||
|
SS version |
Version 1 or above |
|||
Table 7.2.2.2.3.3-4: LCS-MOLRArg (step 1, Table 7.2.2.2.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LCS-MOLRArg ::= SEQUENCE { |
||||
|
molr-Type |
locationEstimate |
|||
|
multiplePositioningProtocolPDUs SEQUENCE |
May include up to three LPP messages |
|||
|
} |
||||
Table 7.2.2.2.3.3-5: DLInformationTransfer (steps 2a, 2c, 2d, 3, 4, 5a and 6, Table 7.2.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.2.2.2.3.3-6 |
DOWNLINK GENERIC NAS TRANSPORT |
||
|
} |
||||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.2.3.3-6: DOWNLINK GENERIC NAS TRANSPORT
(steps 2a, 2c, 2d, 3, 4, 5a and 6, Table 7.2.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 |
Step 2a, 2c, 2d, 3, 4, 5a: 00000001 |
LTE Positioning Protocol (LPP) message container |
||
|
Step 6: 00000010 |
Location services message container |
|||
|
Generic message container |
Step 2a: Set according to Table 7.2.2.2.3.3-7 |
LPP Request Capabilities |
||
|
Step 2c, 5a: Set according to Table 7.2.2.2.3.3-9 |
LPP Acknowledgement |
|||
|
Step 2d: Set according to Table 7.2.2.2.3.3-10 |
LPP Provide Assistance Data |
|||
|
Step 3: Set according to Table 7.2.2.2.3.3-11 |
LPP Provide Assistance Data |
|||
|
Step 4: Set according to Table 7.2.2.2.3.3-12 |
LPP Request Location Information |
|||
|
Step 6: Set according to Table 7.2.2.2.3.3-14 |
FACILITY |
|||
|
Additional information |
Steps 2a, 2c, 2d, 3, 4, 5a: Present |
Routing Identifier/ Correlation ID |
||
|
Step 6: Not present. |
||||
Table 7.2.2.2.3.3-7: LPP Request Capabilities (step 2a, Table 7.2.2.2.3.2-1)
|
Derivation Path: Table 5.4-1 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
As defined in Table 5.4-1 |
||||
Table 7.2.2.2.3.3-8: LPP Provide Capabilities (step 2b, Table 7.2.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 2a Table 7.2.2.2.3.2-1. |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
Contains a different value compared to any other UL message already sent by the UE. |
||
|
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 SEQUENCE{ |
Dependent on UE capabilities |
|||
|
ueRxTxSupTDD-r13 |
Present (TRUE) for sub-test 6 TDD |
Rel-13 onwards |
||
|
} |
||||
|
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.2.2.2.3.3-9: LPP Acknowledgement (steps 2c and 5a, Table 7.2.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 |
Step 2c: (0..255) |
Contains the same value of the sequenceNumber field as received by the SS in the LPP Provide Capabilities message in step 2b, Table 7.2.2.2.3.2‑1. |
||
|
Step 5a: (0..255) |
Contains the same value of the sequenceNumber field as received by the SS in the LPP Provide Location Information message in step 5, Table 7.2.2.2.3.2‑1. |
|||
|
} |
||||
|
lpp-MessageBody |
Not present. |
|||
|
} |
||||
Table 7.2.2.2.3.3-10: LPP Provide Assistance Data (step 2d, Table 7.2.2.2.3.2-1)
|
Derivation Path: Table 5.4-2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LPP-Message ::= SEQUENCE { |
||||
|
transactionID SEQUENCE { |
Contains the same value as any potential LPP Request Assistance Data message included by the UE at step 1, Table 7.2.2.2.3.2‑1. |
|||
|
Initiator |
targetDevice |
|||
|
transactionNumber |
(0..255) |
|||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
Not present |
|||
|
acknowledgement |
Not present. |
|||
|
lpp-MessageBody CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideAssistanceData SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
provideAssistanceData-r9 SEQUENCE { |
||||
|
commonIEsProvideAssistanceData |
Not present |
|||
|
a-gnss-ProvideAssistanceData SEQUENCE { |
Present, if UE requested GNSS assistance data at step 1, Table 7.2.2.2.3.2‑1. |
|||
|
gnss-CommonAssistData |
Not present |
|||
|
gnss-GenericAssistData |
Not present |
|||
|
gnss-Error CHOICE { |
||||
|
locationServerErrorCauses SEQUENCE { |
||||
|
cause |
undefined |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
otdoa-ProvideAssistanceData SEQUENCE { |
Present, if UE requested OTDOA assistance data at step 1, Table 7.2.2.2.3.2-1. |
|||
|
otdoa-ReferenceCellInfo |
Not present |
|||
|
otdoa-NeighbourCellInfo |
Not present |
|||
|
otdoa-Error CHOICE { |
||||
|
locationServerErrorCauses SEQUENCE { |
||||
|
cause |
undefined |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
epdu-Provide-AssistanceData |
Not present |
|||
|
sensor-ProvideAssistanceData-r14 SEQUENCE { |
Present, if UE requested Sensor assistance data at step 1, Table 7.2.2.2.3.2-1. |
Rel-14 onwards |
||
|
sensor-AssistanceDataList-r14 |
Not present |
|||
|
sensor-Error-r14 CHOICE{ |
||||
|
locationServerErrorCauses-r13 SEQUENCE { |
||||
|
cause-r13 |
undefined |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
tbs-ProvideAssistanceData-r14 SEQUENCE { |
Present, if UE requested MBS assistance data at step 1, Table 7.2.2.2.3.2-1. |
Rel-14 onwards |
||
|
tbs-AssistanceDataList-r14 |
Not present |
|||
|
tbs-Error-r14 CHOICE{ |
||||
|
locationServerErrorCauses-r13 SEQUENCE { |
||||
|
cause-r13 |
undefined |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
wlan-ProvideAssistanceData-r14 SEQUENCE { |
Present, if UE requested WLAN assistance data at step 1, Table 7.2.2.2.3.2-1. |
Rel-14 onwards |
||
|
wlan-AssistanceDataList-r14 |
Not present |
|||
|
wlan-Error-r14 CHOICE{ |
||||
|
locationServerErrorCauses-r13 SEQUENCE { |
||||
|
cause-r13 |
undefined |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.2.3.3-11: LPP Provide Assistance Data (step 3, Table 7.2.2.2.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) |
|||
|
} |
||||
Table 7.2.2.2.3.3-12: LPP Request Location Information (step 4, Table 7.2.2.2.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 |
|||
Table 7.2.2.2.3.3-13: LPP ProvideLocation Information (step 5, Table 7.2.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 Location Information message in step 4 Table 7.2.2.2.3.2‑1. |
||
|
} |
||||
|
endTransaction |
TRUE |
|||
|
sequenceNumber |
(0..255) |
Contains a different value compared to any other UL message already sent by the UE. |
||
|
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 |
Present for sub-test 15. Any value acceptable |
|||
|
otdoa-ProvideLocationInformation |
Present for sub-test 5. Any value acceptable |
|||
|
ecid-ProvideLocationInformation |
Present for sub-tests 6 FDD, 6 TDD. Any value acceptable |
|||
|
epdu-ProvideLocationInformation |
Not present |
|||
|
sensor-ProvideLocationInformation-r13 |
Present for sub-test 14, 18 Any value acceptable |
Rel-13 onwards |
||
|
tbs-ProvideLocationInformation-r13 |
Present for sub-tests 12, 16 Any value acceptable |
Rel-13 onwards |
||
|
wlan-ProvideLocationInformation-r13 |
Present for sub-test 11, 17 Any value acceptable |
Rel-13 onwards |
||
|
bt-ProvideLocationInformation-r13 |
Present for sub-test 13 Any value acceptable |
Rel-13 onwards |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 7.2.2.2.3.3-14: FACILITY (step 6, Table 7.2.2.2.3.2-1)
|
Derivation Path: 24.080 Table 2.3 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Facility message type |
0011 1010 |
FACILITY |
||
|
Facility |
Return Result=LCS‑MOLRRes |
Set according to Table 7.2.2.2.3.3‑15 |
||
Table 7.2.2.2.3.3-15: LCS-MOLRRes (step 6, Table 7.2.2.2.3.2-1)
|
Derivation Path: 24.080 clause 4.4.2 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
LCS-MOLRRes::= SEQUENCE { |
||||
|
locationEstimate |
Any value. The SS shall not be required to calculate the value from the returned measurements. |
|||
|
} |
||||
Table 7.2.2.2.3.3-16: RELEASE COMPLETE (step 7, Table 7.2.2.2.3.2-1)
|
Derivation Path: 24.080 Table 2.5 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
Supplementary service protocol discriminator |
1011 |
supplementary services (call independent) |
||
|
Transaction identifier |
||||
|
Release Complete message type |
xx10 1010 |
RELEASE COMPLETE |
||