6.2.2 Assisted GNSS Mobile Originated Tests
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
6.2.2.1 MO-LR Position Estimate: UE-Based A-GNSS
6.2.2.1.1 Definition
This test case applies to all UEs supporting UE-Based GANSS or GNSS Location Service capabilities and providing a method to trigger an MO-LR request for a position estimate.
6.2.2.1.2 Conformance requirements
1) The MS 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.
2) The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
3) After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Reference(s):
– Conformance requirements 1, 2 and 3: TS 24.030, subclause 5.1.1
6.2.2.1.3 Test Purpose
To verify the UE behaviour at a mobile originated location request procedure using network-assisted UE-based GNSS.
6.2.2.1.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signals: As specified in 4.2
– User Equipment (UE):
– The UE is in state “MM idle” with valid TMSI and CKSN.
– The UE is in state “PMM idle” with valid P-TMSI.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Based Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of triggering an MO-LR request for a position estimate.
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined below:
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS(1) and A-GLONASS only |
|
8 |
UE supporting A-GPS(1) and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS(1) and A-BDS only |
|
NOTE 1: “A-GPS” includes Modernized GPS if supported by the UE. |
|
The UE invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering.
The UE invokes an MO-LR request of type "locationEstimate".
The SS orders an A-GNSS positioning measurement using one or more (dependent on the Sub-Test) MEASUREMENT CONTROL messages.
The SS responds with a FACILITY message containing an MO-LR result.
When UE receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
-> |
The UE establishes an RRC connection for location service. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originated High Priority Signalling". |
||
|
2 |
-> |
CM SERVICE REQUEST |
The CM service type IE indicates "call independent supplementary service" |
|
|
3 |
<- |
AUTHENTICATION REQUEST |
||
|
4 |
-> |
AUTHENTICATION RESPONSE |
||
|
5 |
SS |
The SS starts ciphering and integrity protection. |
||
|
6 |
-> |
REGISTER |
Call Independent SS containing Facility IE with an LCS MO-LR request of type "locationEstimate". |
|
|
7 |
<– |
MEASUREMENT CONTROL |
All Sub-Tests |
|
|
7a |
<– |
MEASUREMENT CONTROL |
Sub-Tests 2, 3, 4, 8, 10 only |
|
|
7b |
<– |
MEASUREMENT CONTROL |
Sub-Tests 4, 8, 10 only |
|
|
8 |
-> |
MEASUREMENT REPORT |
||
|
9 |
<- |
FACILITY |
LCS MO-LR result message containing a location estimate |
|
|
10 |
-> |
RELEASE COMPLETE |
The UE terminates the dialogue |
|
|
11 |
SS |
The SS releases the RRC connection and the test case ends. |
||
Specific Message Contents
REGISTER (Step 6)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Register message type |
xx11 1011 (REGISTER) |
|
Facility |
Invoke=LCS-MOLR molr-Type ->locationEstimate |
|
SS version |
Version 1 or above |
MEASUREMENT CONTROL (Step 7):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Setup |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 1: bit 5 = 1 |
|
Sub-Test 2: bit 1 = 1 |
|
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
For Sub-Tests 1, 9 only |
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– No reporting |
For Sub-Tests 2, 3, 4, 8, 10 only |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the first MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the first MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT CONTROL (Step 7a):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Modify |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 2: bit 1 = 1 |
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
For Sub-Tests 2, 3 only |
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– No reporting |
For Sub-Tests 4, 8, 10 only |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the second MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the second MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT CONTROL (Step 7b):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Modify |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
|
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the third MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the third MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT REPORT (Step 8)
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measured Results |
|
|
– CHOICE Measurement |
UE positioning measured results |
|
– UE positioning measured results |
|
|
– UE positioning OTDOA measured results |
Not present |
|
– UE positioning position estimate info |
|
|
– CHOICE Reference time |
GPS or GANSS reference time only |
|
– GPS TOW msec |
Not checked |
|
– GANSS TOD msec |
Not checked |
|
– CHOICE Position estimate |
One of ‘Ellipsoid point with uncertainty Circle’ or ‘Ellipsoid point with uncertainty Ellipse’ or ‘Ellipsoid point with altitude and uncertainty Ellipsoid’ |
|
– Position Data |
Not checked |
|
– CHOICE Velocity estimate |
Not present |
|
– UE positioning GPS measured results |
Not present |
|
– UE positioning error |
Not present |
|
– UE positioning GANSS measured results |
Not present |
|
Measured Results on secondary UL frequency |
Not present |
|
Measured Results on RACH |
Not present |
|
Additional Measured Results |
Not present |
|
Additional Measured results on secondary UL frequency |
Not present |
|
Event Results |
Not present |
|
Event results on secondary UL frequency |
Not present |
|
Inter-RAT cell info indication |
Not present |
|
E-UTRA Measured Results |
Not present |
|
E-UTRA Event Results |
Not present |
|
CSG Proximity Indication |
Not present |
FACILITY (Step 9)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Facility message type |
xx11 1010 (FACILITY) |
|
Facility |
Return Result=LCS‑MOLRRes 🡪 locationEstimate |
RELEASE COMPLETE (Step 10)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Release Complete message type |
xx10 1010 (RELEASE COMPLETE) |
6.2.2.1.5 Test requirements
After step 5 the UE shall transmit a REGISTER message with an LCS MO-LR request with the IE "MOLR-Type" set to "locationEstimate".
After step 7, the UE shall respond with a MEASUREMENT REPORT message.
After step 9, the UE shall send a RELEASE COMPLETE message.
6.2.2.2 MO-LR Position Estimate: UE-Assisted A-GNSS
6.2.2.2.1 Definition
This test case applies to all UEs supporting UE-Assisted GANSS or GNSS Location Service capabilities and providing a method to trigger an MO-LR request for a position estimate.
6.2.2.2.2 Conformance requirements
1) The MS 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.
2) The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
3) After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Reference(s):
– Conformance requirements 1, 2 and 3: TS 24.030, subclause 5.1.1
6.2.2.2.3 Test Purpose
To verify the UE behaviour at a mobile originated location request procedure using network-assisted UE-assisted GNSS.
6.2.2.2.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signals: As specified in 4.2
– User Equipment (UE):
– The UE is in state "MM idle" with valid TMSI and CKSN.
– The UE is in state "PMM idle" with valid P-TMSI.
Related PICS/PIXIT Statements
– UE Assisted Network Assisted GANSS.
– UE Assisted Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of triggering an MO-LR request for a position estimate.
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined below:
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS(1) and A-GLONASS only |
|
8 |
UE supporting A-GPS(1) and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS(1) and A-BDS only |
|
NOTE 1: "A-GPS" includes Modernized GPS if supported by the UE. |
|
The UE invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering.
The UE invokes an MO-LR request of type "locationEstimate".
The SS orders an A-GNSS positioning measurement using a MEASUREMENT CONTROL message, including assistance data as specified in subclause 4.4.3. The UE may request additional assistance data by sending a MEASUREMENT REPORT message containing a positioning error indication with the IE "Error reason" set to "Assistance Data Missing". If the UE requests additional assistance data, the SS provides the requested assistance data in one or more MEASUREMENT CONTROL messages.
The SS responds with a FACILITY message containing an MO-LR result.
When UE receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
-> |
The UE establishes an RRC connection for location service. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originated High Priority Signalling". |
||
|
2 |
-> |
CM SERVICE REQUEST |
The CM service type IE indicates "call independent supplementary service" |
|
|
3 |
<- |
AUTHENTICATION REQUEST |
||
|
4 |
-> |
AUTHENTICATION RESPONSE |
||
|
5 |
SS |
The SS starts ciphering and integrity protection. |
||
|
6 |
-> |
REGISTER |
Call Independent SS containing Facility IE with an LCS MO-LR request of type "locationEstimate". |
|
|
7 |
<- |
MEASUREMENT CONTROL |
||
|
8 |
-> |
MEASUREMENT REPORT |
UE reports positioning measurement results (Option 1) or requests additional assistance data (Option 2). |
|
|
8a |
<- |
MEASUREMENT CONTROL |
If UE requested additional assistance data in step 8, SS provides the requested data in one or more MEASUREMENT CONTROL messages as specified in subclause 4.4.5. |
|
|
8b |
-> |
MEASUREMENT REPORT |
If UE requested additional assistance data in step 8, this message contains the IE "UE positioning GANSS measured results" and "UE positioning GPS measured results" (Sub-tests 3, 4, 8 and 10). |
|
|
9 |
<- |
FACILITY |
LCS MO-LR result message containing a location estimate |
|
|
10 |
-> |
RELEASE COMPLETE |
The UE terminates the dialogue |
|
|
11 |
SS |
The SS releases the RRC connection and the test case ends |
||
Specific Message Contents
REGISTER (Step 6):
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Register message type |
xx11 1011 (REGISTER) |
|
Facility |
Invoke=LCS-MOLR molr-Type ->locationEstimate |
|
SS version |
Version 1 or above |
MEASUREMENT CONTROL (Step 7):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Setup |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE assisted |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
TRUE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 1: bit 5 = 1 |
|
Sub-Test 2: bit 1 = 1 |
|
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Set according to UE capabilities |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
|
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for "Adequate assistance data for UE-assisted A-GNSS" in 4.4.3 |
|
– UE positioning GANSS assistance data |
Set as specified for "Adequate assistance data for UE-assisted A-GNSS" in 4.4.3 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT REPORT (Step 8 (Option 1) or 8b (Option 2)):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measured Results |
|
|
– CHOICE Measurement |
UE positioning measured results |
|
– UE positioning measured results |
|
|
– UE positioning OTDOA measured results |
Not present |
|
– UE positioning position estimate info |
Not present |
|
– UE positioning GPS measured results |
Present for Sub-Tests 3, 4, 8 and 10 |
|
– UE positioning error |
Not present |
|
– UE positioning GANSS measured results |
Present |
|
Measured Results on secondary UL frequency |
Not present |
|
Measured Results on RACH |
Not present |
|
Additional Measured Results |
Not present |
|
Additional Measured results on secondary UL frequency |
Not present |
|
Event Results |
Not present |
|
Event results on secondary UL frequency |
Not present |
|
Inter-RAT cell info indication |
Not present |
|
E-UTRA Measured Results |
Not present |
|
E-UTRA Event Results |
Not present |
|
CSG Proximity Indication |
Not present |
MEASUREMENT REPORT (Step 8 (Option 2)):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measured Results |
|
|
– CHOICE Measurement |
UE positioning measured results |
|
– UE positioning measured results |
|
|
– UE positioning OTDOA measured results |
Not present |
|
– UE positioning position estimate info |
Not present |
|
– UE positioning GPS measured results |
Not present |
|
– UE positioning error |
|
|
– Error reason |
Assistance Data Missing |
|
– GPS Additional Assistance Data Request |
Not checked |
|
– GANSS Additional Assistance Data Request |
Not checked |
|
– UE positioning GANSS measured results |
Not present |
|
Measured Results on secondary UL frequency |
Not present |
|
Measured Results on RACH |
Not present |
|
Additional Measured Results |
Not present |
|
Additional Measured results on secondary UL frequency |
Not present |
|
Event Results |
Not present |
|
Event results on secondary UL frequency |
Not present |
|
Inter-RAT cell info indication |
Not present |
|
E-UTRA Measured Results |
Not present |
|
E-UTRA Event Results |
Not present |
|
CSG Proximity Indication |
Not present |
MEASUREMENT CONTROL (Step 8a (Option 2)):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Modify |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE assisted |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 1: bit 5 = 1 |
|
Sub-Test 2: bit 1 = 1 |
|
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Set according to UE capabilities |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
|
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified in 4.4.5 |
|
– UE positioning GANSS assistance data |
Set as specified in 4.4.5 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
FACILITY (Step 9):
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Facility message type |
xx11 1010 (FACILITY) |
|
Facility |
Return Result=LCS‑MOLRRes 🡪 locationEstimate Any values may be used. The SS shall not be required to calculate the value from the returned measurements. |
RELEASE COMPLETE (Step 10):
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Release Complete message type |
xx10 1010 (RELEASE COMPLETE) |
6.2.2.2.5 Test requirements
After step 5 the UE shall transmit a REGISTER message with an LCS MO-LR request with the IE "MOLR-Type" set to "locationEstimate".
After step 7, the UE shall send a MEASUREMENT REPORT message containing the IE "UE positioning GPS measured results" and/or "UE positioning GANSS measured results".
After step 9, the UE shall send a RELEASE COMPLETE message.
6.2.2.3 MO-LR Position Estimate: UE-Based A-GNSS – Failure Not Enough Satellites
6.2.2.3.1 Definition
This test case applies to all UEs supporting UE-Based GANSS or GNSS Location Service capabilities and providing a method to trigger an MO-LR request for a position estimate.
6.2.2.3.2 Conformance requirements
1) The MS 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.
2) if the IE "Measurement command" has the value "modify":
2> for all IEs present in the MEASUREMENT CONTROL message:
3> if a measurement was stored in the variable MEASUREMENT_IDENTITY associated to the identity by the IE "measurement identity":
4> if measurement type is set to "UE positioning measurement" and the IE "UE positioning GPS assistance data" is present, for any of the optional IEs "UE positioning GPS reference time", "UE positioning GPS reference UE position", "UE positioning GPS DGPS corrections", "UE positioning GPS ionospheric model", "UE positioning GPS UTC model", "UE positioning GPS acquisition assistance", "UE positioning GPS real-time integrity" that are present in the MEASUREMENT CONTROL message:
4> if measurement type is set to "UE positioning measurement" and the IE "UE positioning GANSS assistance data" is present, for any of the optional IEs "UE positioning GANSS reference time", "UE positioning GANSS reference UE position", "UE positioning DGANSS corrections", "UE positioning GANSS ionospheric model", "UE positioning GANSS additional ionospheric model", "UE positioning GANSS UTC model", "UE positioning GANSS additional UTC models", "UE positioning GANSS reference measurement information", "UE positioning GANSS data bit assistance", "UE positioning GANSS Time model", "UE positioning GANSS real-time integrity", "UE positioning GANSS Earth orientation parameters", "UE positioning GANSS auxiliary information" that are present in the MEASUREMENT CONTROL message:
5> replace all instances of the IEs listed above (and all their children) stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the IE "measurement identity" with the IEs received in the MEASUREMENT CONTROL message;
5> leave all other stored information elements unchanged in the variable MEASUREMENT_IDENTITY.
3) If the IE "UE positioning GPS Navigation Model" is included, for each satellite, the UE shall:
1> use IE "Satellite Status" to determine if an update of IE "UE positioning GPS Ephemeris and Clock Correction parameters" has been provided for the satellite indicated by the IE "SatID";
1> if an update has been provided for this satellite:
2> act as specified in subclause 8.6.7.19.3.4.
If the IE "UE positioning GPS Ephemeris and Clock Correction parameters" is included, for each satellite, the UE shall:
1> update the variable UE_POSITIONING_GPS_DATA as follows:
2> store this IE at the position indicated by the IE "Sat ID" in the IE "UE positioning GPS Navigation Model" in the variable UE_POSITIONING_GPS_DATA, possibly overwriting any existing information in this position.
1> act on these GPS ephemeris and clock correction parameters in a manner similar to that specified in [12].
4) If the IE "UE positioning GANSS Navigation Model" is included, the UE shall:
1> for each GANSS:
2> for each satellite, the UE shall:
3> for IE "UE positioning GANSS clock model":
4> act as specified in subclause 8.6.7.19.7.4a.
3> for IE "UE positioning GANSS orbit model":
4> act as specified in subclause 8.6.7.19.7.4b.
5) If the IE "UE positioning GANSS clock model" is included, the UE shall:
1> for each GANSS:
2> update the variable UE_POSITIONING_GANSS_DATA as follows:
3> store this IE at the position indicated by the IE "Sat ID" in the IE "UE positioning GANSS Navigation Model" in the variable UE_POSITIONING_GANSS_DATA, possibly overwriting any existing information in this position.
2> act on these GANSS clock models in a manner similar to that specified in a relevant ICD.
6) If the IE "UE positioning GANSS orbit model" is included, for each satellite of each supported GNSS, the UE shall:
1> update the variable UE_POSITIONING_GANSS_DATA as follows:
2> store this IE at the position indicated by the IE "Sat ID" in the IE "UE positioning GANSS Navigation Model" in the variable UE_POSITIONING_GANSS_DATA, possibly overwriting any existing information in this position..
1> act on these GANSS orbit models in a manner similar to that specified in a relevant ICD.
7) The UE shall when a measurement report is triggered:
2> if the UE has been able to calculate a position after performing measurements on the cells included in the variable UE_POSITIONING_OTDOA_DATA_UE_BASED in case of OTDOA or the UE has been able to calculate a position in case of GPS or GANSS positioning or the UE has been able to calculate a position using a standalone positioning method:
3> include IE "UE positioning Position Estimate Info" in the MEASUREMENT REPORT and set the contents of the IE as follows:
4> if the UE supports the capability to perform the UE GPS timing of cell frames measurement:
5> if the IE "GPS timing of Cell wanted" is set to TRUE:
6> perform the UE GPS timing of cell frames measurement on the serving cell or on one cell of the active set.
6> include the IE "Primary CPICH Info" for FDD or the IE "cell parameters id" for TDD;
6> include the SFN when the position was determined;
6> include the IE "UE GPS timing of cell frames";
6> include the IE "UE Positioning GPS Reference Time Uncertainty".
5> if the IE "GPS timing of Cell wanted" is set to FALSE:
6> include the IE "GPS TOW msec" and set it to the GPS TOW when the position estimate was valid.
4> if the position was calculated with GPS; and
4> the UE does not support the capability to provide the GPS timing of the cell:
5> include the IE "GPS TOW msec" and set it to the GPS TOW when the position estimate was valid.
4> if the UE supports the capability to provide the GANSS timing of the cell frames measurement:
5> if the IE "GANSS timing of Cell wanted" is included with one bit set to value one for a supported GANSS:
6> perform the UE GANSS timing of cell frames measurement on the serving cell or on one cell of the active set;
6> include the IE "GANSS Time ID" to identify the GNSS system time;
6> include the IE "Primary CPICH Info" for FDD or the IE "cell parameters id" for TDD; and
6> include the IE "Reference SFN" and the IE "UE GANSS timing of cell frames".
5> if the IE "GANSS timing of Cell wanted" is not included, or included with each bit set to value zero:
6> include the IE "GANSS TOD msec" and set it to the GANSS TOD when the position estimate was valid.
4> if the UE does not support the capability to provide the GANSS timing of the cell:
5> include the IE "GANSS TOD msec" and set it to the GANSS TOD when the position estimate was valid;
5> include the IE "GANSS Time ID" to identify the GNSS system time.
4> if IE "Vertical Accuracy" has been included in IE "UE positioning reporting quantity":
5> if the IE "Vertical Accuracy" has been assigned to value "0":
6> if the IE "Horizontal Accuracy" has been assigned a value "0":
7> may include IE "Ellipsoid point with altitude".
6> if the IE "Horizontal Accuracy" has been assigned a value unequal to "0"; and
6> if the UE has been able to calculate a 3-dimensional position
7> include IE "Ellipsoid point with altitude" or IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate.
6> if the UE has not been able to calculate a 3-dimensional position:
7> may act as if IE "Vertical Accuracy" was not included in IE "UE positioning reporting quantity".
5> if the IE "Vertical Accuracy" has been assigned to a value unequal to "0":
6> if the UE has been able to calculate a 3-dimensional position:
7> include IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate.
6> if the UE has not been able to calculate a 3-dimensional position:
7> act as if IE "Vertical Accuracy" has not been included in IE "UE positioning reporting quantity".
4> if IE "Vertical Accuracy" has not been included in IE "UE positioning reporting quantity":
5> if IE "Horizontal Accuracy" in IE "UE positioning reporting quantity" has been assigned to value "0":
6> may include IE "Ellipsoid point".
5> if IE "Horizontal Accuracy" in IE "UE positioning reporting quantity" has been assigned to a value unequal to 0:
6> include either IE "Ellipsoid point with uncertainty circle" or IE "Ellipsoid point with uncertainty ellipse" or IE "Ellipsoid point with altitude and uncertainty ellipsoid" as the position estimate.
4> if any of the IEs "Ellipsoid point with uncertainty ellipse" or "Ellipsoid point with altitude and uncertainty ellipsoid" is reported:
5> should calculate a value of the IE "Confidence", different from "0", as the probability that the UE is located within the uncertainty region of the one of the IEs "Ellipsoid point with uncertainty ellipse" or "Ellipsoid point with altitude and uncertainty ellipsoid" that is reported.
NOTE: The value "0" of the IE "Confidence" is interpreted as "no information" by the UTRAN [57].
4> if IE "Velocity Requested" has been included in IE "UE positioning reporting quantity":
5> include IE "Velocity estimate" if supported and available.
2> if the UE was not able to calculate a position:
3> include IE "UE positioning error" in the MEASUREMENT REPORT and set the contents of this IE as specified in subclause 8.6.7.19.5.
8) The UE shall set the contents of the IE "UE positioning Error" as follows:
…
1> if the IE "Positioning Methods" in IE "UE positioning reporting quantity" has been assigned to value "GPS" and the IE "GANSS Positioning Methods" is present:
2> if there were not enough GANSS satellites to be received:
3> set IE "Error reason" to "Not Enough GANSS Satellites".
2> if some GANSS assistance data was missing:
3> set IE "Error reason" to "Assistance Data Missing"; and
3> if the IE "Additional Assistance Data Request" included in the IE "UE positioning reporting quantity" stored in the variable MEASUREMENT_IDENTITY is set to TRUE:
4> include the IE "GANSS Additional Assistance Data Request".
3> if the IE "Additional Assistance Data Request" included in the IE "UE positioning reporting quantity" stored in the variable MEASUREMENT_IDENTITY is set to FALSE:
4> not include the IE "GANSS Additional Assistance Data Request", and use the assistance data available for doing a positioning estimate.
9) If the network is unable to successfully fulfil the request received from the MS (e.g. to provide a location estimate or location assistance information), it shall clear the transaction by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080.
10) PositionMethodFailure: This error is returned by the network when the network is unable to obtain any of the location information requested or none of the information obtained satisfies the requested LCS QoS or if requested LCS assistance data could not be transferred or requested deciphering keys for broadcast assistance data could not be returned.
Reference(s):
– Conformance requirements 1 and 9: TS 24.030, subclause 5.1.1
– Conformance requirement 2: TS 25.331, subclause 8.4.1.3.
– Conformance requirement 3: TS 25.331, subclauses 8.6.7.19.3.3a, 8.6.7.19.3.4.
– Conformance requirement 4: TS 25.331, subclause 8.6.7.19.7.4
– Conformance requirement 5: TS 25.331, subclause 8.6..7.19.4a
– Conformance requirement 6: TS 25.331, subclause 8.6.7.19.4b
– Conformance requirement 7: TS 25.331, subclause 8.6.7.19.1b
– Conformance requirement 8: TS 25.331, subclause 8.6.7.19.1b
– Conformance requirement 9: TS 25.331, subclause 8.6.7.19.5
– Conformance requirement 10: TS 24.080, subclause 4.3.2.29
6.2.2.3.3 Test Purpose
To verify the UE behaviour at a mobile originated location request procedure using network-assisted UE-based GNSS when the MO-LR procedure fails due to failure of positioning method.
6.2.2.3.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signals switched off or not present.
– User Equipment (UE):
– The UE is in state “MM idle” with valid TMSI and CKSN.
– The UE is in state “PMM idle” with valid P-TMSI
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Based Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of triggering an MO-LR request for a position estimate.
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined below:
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS(1) and A-GLONASS only |
|
8 |
UE supporting A-GPS(1) and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS(1) and A-BDS only |
|
NOTE 1: “A-GPS” includes Modernized GPS if supported by the UE. |
|
The UE invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering.
The UE invokes an MO-LR request of type "locationEstimate".
The SS orders an A-GNSS positioning measurement using one or more (dependent on the Sub-Test) MEASUREMENT CONTROL messages.
The UE sends a MEASUREMENT REPORT message with a positioning error indication.
The SS sends a RELEASE COMPLETE message containing a return error component.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
-> |
The UE establishes an RRC connection for location service. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originated High Priority Signalling". |
||
|
2 |
-> |
CM SERVICE REQUEST |
The CM service type IE indicates "call independent supplementary service" |
|
|
3 |
<- |
AUTHENTICATION REQUEST |
||
|
4 |
-> |
AUTHENTICATION RESPONSE |
||
|
5 |
SS |
The SS starts ciphering and integrity protection. |
||
|
6 |
-> |
REGISTER |
Call Independent SS containing Facility IE with an LCS MO-LR request of type "locationEstimate". |
|
|
7 |
<– |
MEASUREMENT CONTROL |
All Sub-Tests |
|
|
7a |
<– |
MEASUREMENT CONTROL |
Sub-Tests 2, 3, 4, 8, 10 only |
|
|
7b |
<– |
MEASUREMENT CONTROL |
Sub-Tests 4, 8, 10 only |
|
|
8 |
-> |
MEASUREMENT REPORT |
Positioning error report "not enough GANSS satellites" or "not enough GPS satellites" (sub-tests 3, 4, 8 and 10 only) |
|
|
9 |
SS |
SS is unable to fulfil the MO-LR request |
||
|
10 |
<- |
RELEASE COMPLETE |
SS terminates the dialogue containing a return error component |
|
|
11 |
SS |
The SS releases the RRC connection and the test case ends. |
||
Specific Message Contents
REGISTER (Step 6)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Register message type |
xx11 1011 (REGISTER) |
|
Facility |
Invoke=LCS-MOLR molr-Type ->locationEstimate |
|
SS version |
Version 1 or above |
MEASUREMENT CONTROL (Step 7):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Setup |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 1: bit 5 = 1 |
|
Sub-Test 2: bit 1 = 1 |
|
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
For Sub-Tests 1, 9 only |
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– No reporting |
For Sub-Tests 2, 3, 4, 8, 10 only |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the first MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the first MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT CONTROL (Step 7a):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Modify |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 2: bit 1 = 1 |
|
Sub-Test 3: bit 0 and 3 = 1 |
|
|
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 9: bit 6 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
For Sub-Tests 2, 3 only |
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– No reporting |
For Sub-Tests 4, 8, 10 only |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the second MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the second MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT CONTROL (Step 7b):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measurement Command |
Modify |
|
Measurement Reporting Mode |
|
|
– Measurement report transfer mode |
Acknowledged mode RLC |
|
– Periodical reporting / Event trigger reporting mode |
Periodical reporting |
|
Additional Measurements List |
Not present |
|
CHOICE Measurement type |
UE positioning measurement |
|
– UE positioning measurement |
|
|
– UE positioning reporting quantity |
|
|
– Method type |
UE based |
|
– Positioning methods |
GPS |
|
– Response time |
128 |
|
– Horizontal accuracy |
127 |
|
– Vertical accuracy |
127 |
|
– GPS timing of cell wanted |
FALSE |
|
– Multiple sets |
FALSE |
|
– Additional assistance data request |
FALSE |
|
– Environmental characterization |
Not present |
|
– Velocity Requested |
Not present |
|
– GANSS Positioning Method |
Sub-Test 4: bit 0 and 3 and 5 = 1 Sub-Test 8: bit 0 and 1 and 3 = 1 Sub-Test 10: bit 0 and 3 and 6 = 1 |
|
– GANSS timing of cell wanted |
Not present |
|
– GANSS Carrier-Phase Measurement Requested |
Not present |
|
– GANSS Multi-frequency Measurement Requested |
Not present |
|
– Measurement validity |
|
|
– UE state |
All states |
|
– CHOICE Reporting criteria |
|
|
– Periodical reporting criteria |
|
|
– Amount of reporting |
1 |
|
– Reporting interval |
64000 |
|
– UE pos OTDOA assistance data for UE-assisted |
Not present |
|
– UE pos OTDOA assistance data for UE-based |
Not present |
|
– UE positioning GPS assistance data |
Set as specified for the third MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
– UE positioning GANSS assistance data |
Set as specified for the third MEASUREMENT CONTROL message for "Adequate assistance data for UE-based A-GNSS" in 4.4.1 |
|
Physical Channel Information Elements |
|
|
DPCH compressed mode status info |
Not present |
MEASUREMENT REPORT (Step 8)
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
Measurement Identity |
10 |
|
Measured Results |
|
|
– CHOICE Measurement |
UE positioning measured results |
|
– UE positioning measured results |
|
|
– UE positioning OTDOA measured results |
Not present |
|
– UE positioning position estimate info |
Not present |
|
– UE positioning GPS measured results |
Not present |
|
– UE positioning error |
|
|
– Error reason |
notEnoughGANSS-Satellites or notEnoughGPS-Satellites (sub-tests 3, 4, 8 and 10 only) |
|
– UE positioning GANSS measured results |
Not present |
|
Measured Results on secondary UL frequency |
Not present |
|
Measured Results on RACH |
Not present |
|
Additional Measured Results |
Not present |
|
Additional Measured results on secondary UL frequency |
Not present |
|
Event Results |
Not present |
|
Event results on secondary UL frequency |
Not present |
|
Inter-RAT cell info indication |
Not present |
|
E-UTRA Measured Results |
Not present |
|
E-UTRA Event Results |
Not present |
|
CSG Proximity Indication |
Not present |
RELEASE COMPLETE (Step 10)
|
Information element |
Value/remark |
|
Protocol Discriminator |
Call Independent SS message (1011) |
|
Transaction identifier |
|
|
Message type Facility |
RELEASE COMPLETE (0010 1010) Return error = LCS-MOLR Error -> positionMethodFailure |
6.2.2.3.5 Test requirements
After step 5 the UE shall transmit a REGISTER message with an LCS MO-LR request with the IE "MOLR-Type" set to "locationEstimate".
After step 7b, the UE shall respond with a MEASUREMENT REPORT message.
6.2.2.4 MO-LR Assistance Data: UE-Based or UE-Assisted A-GNSS – Success
6.2.2.4.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities and providing a method to trigger an MO-LR request for a assistance data.
6.2.2.4.2 Conformance requirements
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.
2) The network shall send a FACILITY message to the UE containing a LCS-MOLR return result component.
3) After the last location request operation the UE shall terminate the dialogue by sending a RELEASE COMPLETE message.
Reference(s):
– Conformance requirements 1, 2 and 3: TS 24.030, subclause 5.1.1
6.2.2.4.3 Test Purpose
To verify the UE behaviour at a mobile originated location request procedure using network-assisted UE-based or UE-assisted GNSS.
6.2.2.4.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signal s: As specified in 4.2
– User Equipment (UE):
– The UE is in state “MM idle” with valid TMSI and CKSN.
– The UE is in state “PMM idle” with valid P-TMSI.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Based Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– UE Assisted Network Assisted GANSS.
– UE Assisted Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of triggering an MO-LR request for assistance data.
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined below:
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS(1) and A-GLONASS only |
|
8 |
UE supporting A-GPS(1) and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS(1) and A-BDS only |
|
NOTE 1: “A-GPS” includes Modernized GPS if supported by the UE. |
|
The UE invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering.
The UE invokes an MO-LR request of type "AssistanceData".
The SS transmits an ASSISTANCE DATA delivery message with assistance data. When the assistance data delivery was successful, the SS sends a FACILITY message to the UE.
The SS responds with a FACILITY message containing an MO-LR result.
When the UE receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
-> |
The UE establishes an RRC connection for location service. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originated High Priority Signalling". |
||
|
2 |
-> |
CM SERVICE REQUEST |
The CM service type IE indicates "call independent supplementary service" |
|
|
3 |
<- |
AUTHENTICATION REQUEST |
||
|
4 |
-> |
AUTHENTICATION RESPONSE |
||
|
5 |
SS |
The SS starts ciphering and integrity protection. |
||
|
6 |
-> |
REGISTER |
Call Independent SS containing Facility IE with an LCS MO-LR request of type "AssistanceData". |
|
|
7 |
<- |
ASSISTANCE DATA DELIVERY |
The SS provides the requested data in one or more ASSISTANCE DATA DELIVERY messages as specified in subclause 4.4.5. |
|
|
8 |
<- |
FACILITY |
||
|
9 |
-> |
RELEASE COMPLETE |
The UE terminates the dialogue |
|
|
10 |
SS |
The SS releases the RRC connection and the test case ends. |
||
|
Information element |
Value/remark |
|
Protocol Discriminator |
Call Independent SS message (1011) |
|
Transaction identifier |
|
|
Message type |
REGISTER (xx11 1011) |
|
Facility |
For sub-tests 1, 2, 9: Invoke = LCS-MOLR LCS-MOLRArg molr-Type ->assistanceData locationMethod -> assistedGANSS ganssAssistanceData -> OCTET STRING For sub-tests 3, 4, 8 and 10: Invoke = LCS-MOLR LCS-MOLRArg molr-Type ->assistanceData locationMethod ->assistedGPSandGANSS gpsAssistanceData -> OCTET STRING ganssAssistanceData -> OCTET STRING |
|
SS Version |
Value 1 or above |
ASSISTANCE DATA DELIVERY (Step 7):
|
Information element |
Value/remark |
|
Measurement Information Elements |
|
|
UE positioning OTDOA assistance data for UE-based |
Not present |
|
UE positioning GPS assistance data |
Not present for sub-tests 1, 2 and 9. |
|
UE positioning GANSS assistance data |
Set as specified in 4.4.5 |
FACILITY (Step 8)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Facility message type |
xx11 1010 (FACILITY) |
|
Facility |
Return Result=LCS‑MOLRRes 🡪 EMPTY |
RELEASE COMPLETE (Step 9)
|
Information element |
Value/remark |
|
Supplementary service protocol discriminator |
1011 (supplementary services (call independent)) |
|
Transaction identifier |
|
|
Release Complete message type |
xx10 1010 (RELEASE COMPLETE) |
6.2.2.4.5 Test requirements
After step 5 the UE shall transmit a REGISTER message with an LCS MO-LR request with the IE "MOLR-Type" set to "assistanceData".
After step 8, the UE shall send a RELEASE COMPLETE message.
6.2.2.5 MO-LR Assistance Data: UE-Based or UE-Assisted A-GNSS – Failure
6.2.2.5.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities and providing a method to trigger an MO-LR request for assistance data.
6.2.2.5.2 Conformance requirements
1) The UE invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component.
2) If the network is unable to successfully fulfil the request received from the UE (e.g. to provide a location estimate or location assistance information), it shall clear the transaction by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080.
3) PositionMethodFailure: This error is returned by the network when the network is unable to obtain any of the location information requested or none of the information obtained satisfies the requested LCS QoS or if requested LCS assistance data could not be transferred or requested deciphering keys for broadcast assistance data could not be returned.
Reference(s):
– Conformance requirements 1 and 2: TS 24.030, subclause 5.1.1
– Conformance requirement 3: TS 24.080, subclause 4.3.2.29
6.2.2.5.3 Test Purpose
To verify the UE behaviour at a mobile originated location request for assistance data where the network is unable to provide the requested assistance data.
6.2.2.5.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signals: As specified in 4.2
– User Equipment (UE):
The UE shall begin the test with neither GPS nor GANSS assistance data stored.
– The UE is in state “MM idle” with valid TMSI and CKSN.
– The UE is in state “PMM idle” with valid P-TMSI
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Based Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– UE Assisted Network Assisted GANSS.
– UE Assisted Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of triggering an MO-LR request for assistance data.
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the UE. Each sub-test case is identified by a Sub-Test Case Number as defined below:
|
Sub-Test Case Number |
Supported GNSS |
|
1 |
UE supporting A-GLONASS only |
|
2 |
UE supporting A-Galileo only |
|
3 |
UE supporting A-GPS and Modernized GPS only |
|
4 |
UE supporting A-GPS(1) and A-GLONASS only |
|
8 |
UE supporting A-GPS(1) and A-Galileo only |
|
9 |
UE supporting A-BDS only |
|
10 |
UE supporting A-GPS(1) and A-BDS only |
|
NOTE 1: "A-GPS" includes Modernized GPS if supported by the UE. |
|
The UE invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering.
The UE invokes an MO-LR request of type "assistanceData".
The SS is unable to provide the requested assistance data.
The SS sends a RELEASE COMPLETE message containing a return error component.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
-> |
The UE establishes an RRC connection for location service. The SS verifies that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Originated High Priority Signalling". |
||
|
2 |
-> |
CM SERVICE REQUEST |
The CM service type IE indicates "call independent supplementary service" |
|
|
3 |
<- |
AUTHENTICATION REQUEST |
||
|
4 |
-> |
AUTHENTICATION RESPONSE |
||
|
5 |
SS |
The SS starts ciphering and integrity protection. |
||
|
6 |
-> |
REGISTER |
Call Independent SS containing Facility IE with an LCS MO-LR request of type "AssistanceData". |
|
|
7 |
SS |
SS is unable to provide the requested assistance data |
||
|
8 |
<- |
RELEASE COMPLETE |
SS terminates the dialogue containing a return error component |
|
|
9 |
SS |
The SS waits for 10 seconds to verify that the UE does not send a RELEASE COMPLETE message. |
||
|
10 |
SS |
The SS releases the RRC connection and the test case ends |
||
Specific Message Contents
REGISTER (Step 6)
|
Information element |
Value/remark |
|
Protocol Discriminator |
Call Independent SS message (1011) |
|
Transaction identifier |
|
|
Message type |
REGISTER (xx11 1011) |
|
Facility SS version indicator |
Sub-tests 1, 2 and 9: Invoke = LCS-MOLR LCS-MOLRArg molr-Type ->assistanceData locationMethod -> assistedGANSS ganssAssistanceData -> OCTET STRING Octets 1 to 40 are coded in the Sub-tests 3, 4, 8 and 10: Invoke = LCS-MOLR LCS-MOLRArg molr-Type ->assistanceData LocationMethod ->assistedGPSandGANSS gpsAssistanceData -> OCTET STRING ganssAssistanceData -> OCTET STRING Value 1 or above |
RELEASE COMPLETE (Step 8)
|
Information element |
Value/remark |
|
Protocol Discriminator |
Call Independent SS message (1011) |
|
Transaction identifier |
|
|
Message type Facility |
RELEASE COMPLETE (0010 1010) Return error = LCS-MOLR Error -> positionMethodFailure |
6.2.2.5.5 Test requirements
After step 5 the UE shall transmit a REGISTER message with an LCS MO-LR request with the IE "MOLR-Type" set to "assistanceData".
During step 9 the UE shall not send any RELEASE COMPLETE message.