6.2.3 Assisted GNSS Mobile Terminated Tests
37.571-23GPPPart 2: Protocol conformanceRelease 16TSUser Equipment (UE) conformance specification for UE positioning
6.2.3.1 MT-LR: UE-based or UE-Assisted A-GNSS – Request for additional assistance data/ Success
6.2.3.1.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities.
6.2.3.1.2 Conformance requirements
1) 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.
2) 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].
3) 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.
4) 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.
5) 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.
6) 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.
7) The UE shall:
1> when a measurement report is triggered:
2> if the UE was able to perform measurements on at least one neighbour cell included in the variable UE_POSITIONING_OTDOA_DATA_UE_ASSISTED in case of OTDOA or one satellite included in the variable UE_POSITIONING_GPS_DATA in case of GPS positioning or one cell from the active set in case of CELL ID:
3> if the IE "Vertical Accuracy" is included:
4> interpret the presence of this IE to indicate that the UTRAN desires to compute a 3-dimensional position estimate.
if the IE "Positioning Methods" is set to "GPS" and the IE "GANSS Positioning Methods" is present indicating other GNSS than GPS allowed and if any of these other GNSSs is measured:
4> include the IE "UE positioning GANSS measured results" in the measurement report and set the contents of the IE as follows:
5> if the UE supports the capability to provide the GANSS timing of the cell frames measurement:
6> if the IE "GANSS timing of Cell wanted" is included with one bit set to value one for a supported GANSS and if IE "UE GPS timing of cell frames" is not present:
7> perform the UE GANSS timing of cell frames measurement on the serving cell or on one cell of the active set;
7> include the IE "Primary CPICH Info" for FDD or the IE "cell parameters id" for TDD; and
7> include the IE "Reference SFN" and the IE "UE GANSS timing of cell frames".
6> if the IE "GANSS timing of Cell wanted" is not included, or included with each bit set to value zero and if IE "UE positioning GPS measured results" is not present:
7> include the IE "GANSS TOD msec" and set it to the GANSS TOD when the measurements included in the MEASUREMENT REPORT were valid.
5> if the UE does not support the capability to provide the GANSS timing of the cell and if IE "UE positioning GPS measured results" is not present:
6> include the IE "GANSS TOD msec" and set it to the GANSS TOD when the measurements included in the MEASUREMENT REPORT were valid.
5> if the UE supports the capability to provide the GANSS carrier-phase measurements:
6> if the IE "GANSS Carrier-Phase Measurement Requested" is included with one bit set to value one for a supported GANSS:
7> include the IE "Carrier Quality Indication" and include the IE "ADR".
5> if the UE supports the capability to perform GANSS measurements on multiple GANSS frequencies:
6> if the IE "GANSS Multi-frequency Measurement Requested" is included with one bit set to value one for a supported GANSS, and if any of these GANSS signals are measured:
7> include the IE "GANSS Signal Measurement Information" for each measured GANSS signal.
8) 1> if the UE is unable to report the requested measurement results due to missing GPS assistance data:
2> the UE may at anytime send a measurement report containing the IE "UE positioning error" and set the contents of this IE as specified in subclause 8.6.7.19.5.
2> after sending the measurement report, the UE shall not send another measurement report to request the same GPS assistance data for at least 20s. This requirement does not apply after release of the current RRC connection.
1> if the UE is unable to report the requested measurement results due to missing GANSS assistance data:
2> the UE may at anytime send a measurement report containing the IE "UE positioning error" and set the contents of this IE as specified in subclause 8.6.7.19.5;
2> after sending the measurement report, the UE shall not send another measurement report to request the same GANSS assistance data for at least 20s. This requirement does not apply after release of the current RRC connection.
9) 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.
Reference(s):
– Conformance requirement 1: TS 25.331, subclause 8.4.1.3.
– Conformance requirement 2: TS 25.331, subclauses 8.6.7.19.3.3a, 8.6.7.19.3.4.
– Conformance requirement 3: TS 25.331, subclause 8.6.7.19.7.4
– Conformance requirement 4: TS 25.331, subclause 8.6.7.19.7.4a
– Conformance requirement 5: TS 25.331, subclause 8.6.7.19.7.4b
– Conformance requirement 6: TS 25.331, subclause 8.6.7.19.1b
– Conformance requirement 7: TS 25.331, subclause 8.6.7.19.1a
– Conformance requirement 8: TS 25.331, subclause 8.6.7.19.1a, 8.6.7.19.1b
– Conformance requirement 9: TS 25.331, subclause 8.6.7.19.5
6.2.3.1.3 Test Purpose
To verify the UE’s behaviour in a mobile-terminated location request procedure using UE-based or UE-assisted A-GNSS with assistance data from the network.
To verify that the UE in CELL_DCH state accepts assistance data received in multiple MEASUREMENT CONTROL messages.
To verify that the UE includes the IE "GPS Additional Assistance Data Request" or "GANSS Additional Assistance Data Request" to request assistance data when it does not have enough assistance data.
6.2.3.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.
– The UE shall begin the test with no GPS and GANSS assistance data stored.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Assisted Network Assisted GANSS
– UE Based Network Assisted GPS (Sub-tests 3. 4, 8 and 10).
– UE Assisted Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
– Method of clearing stored GPS/GANSS 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 stored GPS/GANSS assistance data in the UE shall be cleared.
The SS initiates authentication and ciphering and orders a positioning measurement using a MEASUREMENT CONTROL message including no assistance data.
The UE sends a MEASUREMENT REPORT message to report a positioning error, requesting further assistance data. The SS response with one or more MEASUREMENT CONTROL messages that include the requested assistance data and instructs the UE not to repeat the request for assistance data. The final MEASUREMENT CONTROL message orders periodic reporting.
The UE performs positioning measurements and responds with a MEASUREMENT REPORT message including the IE "UE Positioning Position Estimate Info" in case of UE-based, or including the IE "UE positioning GANSS measured results" and/or "UE positioning GPS measured results" in case of UE-assisted.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
<- |
AUTHENTICATION REQUEST |
||
2 |
-> |
AUTHENTICATION RESPONSE |
||
3 |
SS |
The SS starts ciphering and integrity protection. |
||
4 |
Void |
|||
5 |
Void |
|||
6 |
Void |
|||
7 |
<– |
MEASUREMENT CONTROL |
No assistance data, and "Additional Assistance Data Request" IE set to TRUE. |
|
8 |
-> |
MEASUREMENT REPORT |
Positioning error report ‘Assistance Data Missing’ |
|
9 |
<- |
MEASUREMENT CONTROL |
The SS provides the requested data in one or more MEASUREMENT CONTROL messages. The last message contains: Reporting mode: Periodical reporting Amount of reporting: 1 Reporting interval: 64000 |
|
10 |
–> |
MEASUREMENT REPORT |
Measurement report message containing UE position estimate (UE-based), or IE "UE positioning GANSS measured results" and/or "UE positioning GPS measured results’’ (UE-assisted). |
|
11 |
SS |
The SS releases the RRC connection and the test case ends. |
Specific Message Contents
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 or 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 |
UE assisted: Set according to UE capabilities UE based: Not present |
– Measurement validity |
|
– UE state |
All states |
– CHOICE Reporting criteria |
|
– Periodical reporting criteria |
|
– Amount of reporting |
1 |
– Reporting interval |
64000 |
– No reporting |
|
– 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 "Inadequate assistance data for UE-based A-GNSS" in 4.4.2 or "Inadequate assistance data for UE-assisted A-GNSS" in 4.4.4 |
– UE positioning GANSS assistance data |
Set as specified for "Inadequate assistance data for UE-based A-GNSS" in 4.4.2 or "Inadequate assistance data for UE-assisted A-GNSS" in 4.4.4 |
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 |
Not present |
– Error reason |
Assistance Data Missing |
-GPS additional assistance data requested |
Sub-tests 3, 4, 8 and 10 |
-Almanac |
Present, if requested by UE |
-UTC model |
Present, if requested by UE |
-Ionospheric model |
Present, if requested by UE |
-Navigation model |
Present, if requested by UE |
-DGPS corrections |
Present, if requested by UE |
-Reference location |
Present, if requested by UE |
-Reference time |
Present, if requested by UE |
-Acquisition assistance |
Present, if requested by UE |
-Real-time integrity |
Present, if requested by UE |
-Navigation model additional data |
Present, if requested by UE |
-GANSS additional assistance data requested |
Sub-tests 1, 2, 4, 9 |
-GANSS Reference time |
Present, if requested by UE |
-Reference location |
Present, if requested by UE |
-GANSS Ionospheric model |
Present, if requested by UE |
-GANSS Additional Ionospheric Model for |
Present, if requested by UE |
-GANSS Additional Ionospheric Model for |
Present, if requested by UE |
-GANSS Earth orientation parameters |
Present, if requested by UE |
-GANSS Real-time integrity |
Present, if requested by UE |
-GANSS Almanac |
Present, if requested by UE |
-GANSS Time Model |
Present, if requested by UE |
-GANSS Ephemeris Extension Check |
Present, if requested by UE |
– 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 9)
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 or 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 |
UE assisted: Set according to UE capabilities UE based: Not present |
– Measurement validity |
|
– UE state |
All states |
– CHOICE Reporting criteria |
Set as required according to position in sequence of messages |
– Periodical reporting criteria |
Set as required according to position in sequence of messages |
– Amount of reporting |
Set as required according to position in sequence of messages |
– Reporting interval |
Set as required according to position in sequence of messages |
– 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 |
MEASUREMENT REPORT (Step 10)
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 Position estimate |
One of ‘Ellipsoid point with uncertainty Circle’ or ‘Ellipsoid point with uncertainty Ellipse’ or ‘Ellipsoid point with altitude and uncertainty Ellipsoid’ (UE-based) |
– UE positioning GPS measured results |
Present for UE-assisted (Sub-Tests 3, 4, 8 and 10) |
– UE positioning error |
Not present |
– UE positioning GANSS measured results |
Present for UE-assisted. |
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 |
6.2.3.1.5 Test requirements
After step 7 the UE shall send a MEASUREMENT REPORT message containing the IE "UE positioning error", with "Error reason" set to "Assistance Data Missing".
After step 9 the UE shall send a MEASUREMENT REPORT message containing a valid UE position estimate (UE-based) or GANSS and/or GPS measurements (UE-assisted).
6.2.3.2 MT-LR Position Estimate: UE-Based A-GNSS – Failure Not Enough Satellites
6.2.3.2.1 Definition
This test case applies to all UEs supporting UE-Based GANSS or GNSS Location Service capabilities.
6.2.3.2.2 Conformance requirements
1) 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.
2) 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].
3) 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.
4) 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.
5) 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.
6) 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.
7) 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.
Reference(s):
– Conformance requirement 1: TS 25.331, subclause 8.4.1.3.
– Conformance requirement 2: TS 25.331, subclauses 8.6.7.19.3.3a, 8.6.7.19.3.4.
– Conformance requirement 3: TS 25.331, subclause 8.6.7.19.7.4
– Conformance requirement 4: TS 25.331, subclause 8.6..7.19.4a
– Conformance requirement 5: TS 25.331, subclause 8.6.7.19.4b
– Conformance requirement 6: TS 25.331, subclause 8.6.7.19.1b
– Conformance requirement 7: TS 25.331, subclause 8.6.7.19.5
6.2.3.2.3 Test Purpose
To verify the UE behaviour at a mobile terminated location request procedure using network-assisted UE-based GNSS when the MT-LR procedure fails due to failure of positioning method.
To verify that the UE in CELL_DCH state accepts assistance data received in multiple MEASUREMENT CONTROL messages.
To verify that the UE sets the IE Error Reason in ‘UE Positioning Error’ to ‘Not Enough GANSS Satellites’ when it does not receive enough satellite signals to compute a position.
6.2.3.2.4 Method of Test
Initial Conditions
– System Simulator (SS):
– 1 cell, default parameters.
– Satellite signals switched off or not present.
– User Equipment (UE):
– State “CS-CELL DCH Initial (State 6-1) ” as specified in clause 7.4.1 of TS 34.108.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Based Network Assisted GPS (Sub-tests 3, 4, 8 and 10).
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 SS initiates authentication and ciphering and 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 reporting a positioning error for not enough satellite signal.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
<- |
AUTHENTICATION REQUEST |
||
2 |
-> |
AUTHENTICATION RESPONSE |
||
3 |
SS |
SS starts security procedure |
||
4 |
Void |
|||
5 |
Void |
|||
6 |
Void |
|||
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 satellites’ |
|
9 |
SS |
The SS releases the RRC connection and the test case ends. |
Specific Message Contents
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 |
Not present |
– 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 |
6.2.3.2.5 Test requirements
After step 7 the UE shall send a MEASUREMENT REPORT message containing the IE "UE positioning error", with "Error reason" set to "Not Enough Satellites".
6.2.3.3 Location Notification
6.2.3.3.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities and LCS value added location request notification capability.
6.2.3.3.2 Conformance requirements
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.
References
– Conformance requirement 1: TS 24.030, clause 4.1.1
6.2.3.3.3 Test Purpose
To verify that when the UE receives a REGISTER message during an established CS call, containing a LCS Location Notification Invoke component set to NotifyLocationAllowed, the UE notifies the UE user of the location request and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
6.2.3.3.4 Method of Test
Initial Conditions
System Simulator (SS):
– 1 cell, default parameters
– Satellite signals switched off or not present
UE:
– State "CS-CELL DCH Initial (State 6-1)" as specified in clause 7.4.1 of TS 34.108.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Assisted Network Assisted GANSS.
– UE supporting LCS value added location request notification capability.
Test Procedure
The SS initiates authentication and ciphering and sends an SS REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyLocationAllowed. The UE notifies the UE user of the location request. The UE then responds with a RELEASE COMPLETE message containing a LocationNotification return result to terminate the dialogue.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
<- |
AUTHENTICATION REQUEST |
||
2 |
-> |
AUTHENTICATION RESPONSE |
||
3 |
SS |
SS starts security procedure |
||
4 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyLocationAllowed |
|
5 |
UE |
The UE notifies the UE user of the location request |
||
6 |
-> |
RELEASE COMPLETE |
The UE terminates the dialogue |
|
7 |
SS |
SS releases the RRC connection and the test case ends |
Specific Message Contents
REGISTER (Step 4)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType -> notifyLocationAllowed, locationType -> current Location , lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE (Step 6)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
6.2.3.3.5 Test requirements
After step 4 the UE shall notify the UE user of the location request.
After step 5 the UE shall send a RELEASE COMPLETE message.
6.2.3.4 Privacy Verification – Location Allowed if No Response
6.2.3.4.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities and LCS value added location request notification capability.
6.2.3.4.2 Conformance requirements
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.
2) In case of privacy verification the MS shall respond to the request by sending a RELEASE COMPLETE message containing the mobile subscriber’s response in a return result component.
3) If the timer expires in the network before any response from the MS (e.g. due to no response from the user), the network shall interpret this by applying the default treatment defined in GSM 03.71 for GSM and TS 23.171 for UMTS (i.e. disallow location if barred by subscription and allow location if allowed by subscription).
References
– Conformance requirement 1, 2 and 3: TS 24.030, clause 4.1.1
6.2.3.4.3 Test Purpose
To verify that when the UE receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationAllowedIfNoResponse, the UE notifies the UE user of the location request and indicates that the default response is location allowed if no response and providing the opportunity to accept or deny the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied or permissionGranted as appropriate.
6.2.3.4.4 Method of Test
Initial Conditions
System Simulator (SS):
– 1 cell, default parameters
– Satellite signals switched off or not present
UE:
– State "CS-CELL DCH Initial (State 6-1)" as specified in clause 7.4.1 of TS 34.108.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Assisted Network Assisted GANSS.
– UE supporting LCS value added location request notification capability.
– px_UeLcsNotification: value for UE LCS Notification timeout timer.
Test Procedure
The SS initiates authentication and ciphering and sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be allowed if no user response is received.
The user accepts the location request. The UE responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
The SS sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be allowed if no user response is received.
The user denies the location request. The UE responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
The SS sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be allowed if no user response is received.
The user ignores the location request by taking no action, allowing the verification process to time-out.
The SS send a RELEASE COMPLETE.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
<– |
AUTHENTICATION REQUEST |
||
2 |
–> |
AUTHENTICATION RESPONSE |
||
3 |
SS |
SS starts security procedure |
||
4 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse |
|
5 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
6 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be allowed in the absence of a response |
||
7 |
UE |
The user accepts the location request before timer T(LCSN) expires |
||
8 |
-> |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted |
|
9 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse |
|
10 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
11 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be allowed in the absence of a response |
||
12 |
UE |
The user denies the location request before timer T(LCSN) expires |
||
13 |
-> |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied |
|
14 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationAllowedIfNoResponse |
|
15 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
16 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be allowed in the absence of a response |
||
17 |
UE |
The user does not reply |
||
18 |
SS |
SS waits until T(LCSN) expires to ensure that the UE does not send a RELEASE COMPLETE message. |
||
19 |
<- |
RELEASE COMPLETE |
SS terminates the dialogue |
|
20 |
SS |
SS releases the connection and the test case ends |
Specific Message Contents
REGISTER (Steps 4, 9 and 14)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = LCS-LocationNotification LocationNotificationArg notificationType -> notifyAndVerify-LocationAllowedIfNoResponse locationType -> current Location lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme |
RELEASE COMPLETE (Step 8)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = LCS-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Step 13)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = LCS-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Step 19)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
6.2.3.4.5 Test requirements
After steps 4, 9 and 14 the UE shall notify the UE user of the location request and indicate to the user that location will be allowed in the absence of a response.
After step 7 the UE shall send a RELEASE COMPLETE message with verificationResponse set to permissionGranted.
After step 12 the UE shall send a RELEASE COMPLETE message with verificationResponse set to permissionDenied.
During step 18 the UE shall not send any RELEASE COMPLETE message.
6.2.3.5 Privacy Verification – Location Not Allowed if No Response
6.2.3.5.1 Definition
This test case applies to all UEs supporting UE-Based or UE-Assisted GANSS or GNSS Location Service capabilities and LCS value added location request notification capability.
6.2.3.5.2 Conformance requirements
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.
2) In case of privacy verification the MS shall respond to the request by sending a RELEASE COMPLETE message containing the mobile subscriber’s response in a return result component.
3) If the timer expires in the network before any response from the MS (e.g. due to no response from the user), the network shall interpret this by applying the default treatment defined in GSM 03.71 for GSM and TS 23.171 for UMTS (i.e. disallow location if barred by subscription and allow location if allowed by subscription).
References
– Conformance requirement 1, 2 and 3: TS 24.030, clause 4.1.1
6.2.3.5.3 Test Purpose
To verify that when the UE receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationNotAllowedIfNoResponse, the UE notifies the UE user of the location request and indicates that the default response is location not allowed if no response and providing the opportunity to accept or deny the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied or permissionGranted as appropriate.
6.2.3.5.4 Method of Test
Initial Conditions
System Simulator (SS):
– 1 cell, default parameters
– Satellite signals switched off or not present
UE:
– State "CS-CELL DCH Initial (State 6-1)" as specified in clause 7.4.1 of TS 34.108.
Related PICS/PIXIT Statements
– UE Based Network Assisted GANSS.
– UE Assisted Network Assisted GANSS.
– UE supporting LCS value added location request notification capability.
– px_UeLcsNotification: value for UE LCS Notification timeout timer.
Test Procedure
The SS initiates authentication and ciphering and sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be not allowed if no user response is received.
The user accepts the location request. The UE responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
The SS sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be not allowed if no user response is received.
The user denies the location request. The UE responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
The SS sends a REGISTER message containing a Facility IE containing a LCS Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse.
The UE notifies the UE user of the location request with the option to accept or deny the request and an indication that location will be not allowed if no user response is received.
The user ignores the location request by taking no action, allowing the verification process to time-out.
The SS send a RELEASE COMPLETE.
Expected Sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
<– |
AUTHENTICATION REQUEST |
||
2 |
–> |
AUTHENTICATION RESPONSE |
||
3 |
SS |
SS starts security procedure |
||
4 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse |
|
5 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
6 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be not allowed in the absence of a response |
||
7 |
UE |
The user accepts the location request before timer T(LCSN) expires |
||
8 |
-> |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted |
|
9 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse |
|
10 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
11 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be not allowed in the absence of a response |
||
12 |
UE |
The user denies the location request before timer T(LCSN) expires |
||
13 |
-> |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied |
|
14 |
<- |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyAndVerify-LocationNotAllowedIfNoResponse |
|
15 |
SS |
SS starts timer T(LCSN) set to 90% of px_UeLcsNotification |
||
16 |
UE |
The UE notifies the UE user of the location request and indicates to the user that location will be not allowed in the absence of a response |
||
17 |
UE |
The user does not reply |
||
18 |
SS |
SS waits until T(LCSN) expires to verify that the UE does not send a RELEASE COMPLETE message. |
||
19 |
<- |
RELEASE COMPLETE |
SS terminates the dialogue |
|
20 |
SS |
SS releases the connection and the test case ends |
Specific Message Contents
REGISTER (Steps 4, 9 and 14)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = LCS-LocationNotification LocationNotificationArg notificationType -> notifyAndVerify-LocationNotAllowedIfNoResponse locationType -> current Location lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme |
RELEASE COMPLETE (Step 8)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = LCS-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Step 13)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = LCS-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Step 19)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
6.2.3.5.5 Test requirements
After steps 4, 9 and 14 the UE shall notify the UE user of the location request and indicate to the user that location will be not allowed in the absence of a response.
After step 7 the UE shall send a RELEASE COMPLETE message with verificationResponse set to permissionGranted.
After step 12 the UE shall send a RELEASE COMPLETE message with verificationResponse set to permissionDenied.
During step 18 the UE shall not send any RELEASE COMPLETE message.