hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.1 General
|
This sub clause defines the minimum performance requirements for both MS based and MS assisted A‑GPS terminals. If a terminal supports both modes then it shall be tested in both modes.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.2 Measurement parameters
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.2.1 MS based A-GPS measurement parameters
|
In case of MS-based A-GPS, the measurement parameters are contained in the RRLP LOCATION INFORMATION IE. The measurement parameter is the horizontal position estimate reported by the MS and expressed in latitude/longitude.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.2.2 MS assisted A-GPS measurement parameters
|
In case of MS-assisted A-GPS, the measurement parameters are contained in the RRLP GPS MEASUREMENT INFORMATION IE. The measurement parameters are the MS GPS Code Phase measurements. The MS GPS Code Phase measurements are converted into a horizontal position estimate using the procedure detailed in sub clause 70.11.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.2.3 2D position error
|
The 2D position error is defined by the horizontal difference in meters between the ellipsoid point reported or calculated from the MS Measurement Report and the actual simulated position of the MS in the test case considered.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.2.4 Response time
|
Max Response Time is defined as the time starting from the moment that the MS has received the final RRLP MEASURE POSITION REQUEST sent before the MS sends the MEASURE POSITION RESPONSE containing the Location Information or the GPS Measurement Information, and ending when the MS starts sending the MEASURE POSITION RESPONSE containing the Location Information or the GPS Measurement Information on the Air interface. The response times specified for all test cases are Time-to-First-Fix (TTFF), i.e. the MS shall not re‑use any information on GPS time, location or other aiding data that was previously acquired or calculated and stored internally in the MS. A dedicated test message 'RESET MS POSITIONING STORED INFORMATION' has been defined in TS 44.014 for the purpose of deleting this information.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.3 Converting MS-assisted measurement reports into position estimates
|
To convert the MS measurement reports in case of MS-assisted mode of A-GPS into position errors, a transformation between the "measurement domain" (code-phases, etc.) into the "state" domain (position estimate) is necessary. Such a transformation procedure is outlined in the following sub clauses. The details can be found in [ICD-GPS 200], [P. Axelrad, R.G. Brown] and [S.K. Gupta]
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.3.1 MS measurement reports
|
In case of MS-assisted A-GPS, the measurement parameters are contained in the RRLP GPS MEASUREMENT INFORMATION ELEMENT (sub clause A.3.2.5 in 3GPP TS 44.031). The measurement parameters required for calculating the MS position are:
1) Reference Time: The MS has two choices for the Reference Time:
a) "Reference Frame";
b) "GPS TOW ".
2) Measurement Parameters: 1 to <maxSat>:
a) "Satellite ID (SV PRN)";
b) "Whole GPS chips";
c) "Fractional GPS Chips";
d) "Pseudorange RMS Error".
Additional information required at the system simulator:
1) "Reference Location" (sub clause A.4.2.4 in 3GPP TS 44.031):
Used for initial approximate receiver coordinates.
2) "Navigation Model" (sub clause A.4.2.4 in 3GPP TS 44.031):
Contains the GPS ephemeris and clock correction parameters as specified in [ICD-GPS 200]; used for calculating the satellite positions and clock corrections.
3) "Ionospheric Model" (sub clause A.4.2.4 in 3GPP TS 44.031):
Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [ICD-GPS 200] for computation of the ionospheric delay.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.4.3.2 WLS position solution
|
The WLS position solution problem is concerned with the task of solving for four unknowns; xu, yu, zu the receiver coordinates in a suitable frame of reference (usually ECEF) and bu the receiver clock bias. It typically requires the following steps:
Step 1: Formation of pseudo-ranges
The observation of code phase reported by the MS for each satellite SVi is related to the pseudo-range/c modulo 1 ms (the length of the C/A code period). For the formation of pseudo-ranges, the integer number of milliseconds to be added to each code-phase measurement has to be determined first. Since 1 ms corresponds to a travelled distance of 300 km, the number of integer ms can be found with the help of reference location and satellite ephemeris. The distance between the reference location and each satellite SVi is calculated and the integer number of milliseconds to be added to the MS code phase measurements is obtained.
Step 2: Formation of weighting matrix
The MS reported "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm [P. Axelrad, R.G. Brown]. According to 3GPP TS 44.031, the encoding for this field is a 6 bit value that consists of a 3 bit mantissa, Xi and a 3 bit exponent, Yi for each SVi:
The weighting Matrix W is defined as a diagonal matrix containing the estimated variances calculated from the "Pseudorange RMS Error" values:
Step 3: WLS position solution
The WLS position solution is described in reference [P. Axelrad, R.G. Brown] and usually requires the following steps:
1) Computation of satellite locations at time of transmission using the ephemeris parameters and user algorithms defined in [ICD-GPS 200], sub clause 20.3.3.4.3.
2) Computation of clock correction parameters using the parameters and algorithms as defined in [ICD-GPS 200], sub clause 20.3.3.3.3.1.
3) Computation of atmospheric delay corrections using the parameters and algorithms defined in [ICD-GPS 200], sub clause 20.3.3.5.2.5 for the ionospheric delay, and using the Gupta model in reference [S.K. Gupta], p. 121 equation (2) for the tropospheric delay.
4) The WLS position solution starts with an initial estimate of the user state (position and clock offset). The Reference Location is used as initial position estimate. The following steps are required:
a) Calculate geometric range (corrected for Earth rotation) between initial location estimate and each satellite included in the MS measurement report.
b) Predict pseudo-ranges for each measurement including clock and atmospheric biases as calculated in 1) to 3) above and defined in [ICD-GPS 200] and [P. Axelrad, R.G. Brown].
c) Calculate difference between predicted and measured pseudo-ranges
d) Calculate the "Geometry Matrix" G as defined in [P. Axelrad, R.G. Brown]:
with where rsi is the Satellite position vector for SVi (calculated in 1) above), and is the estimate of the user location.
e) Calculate the WLS solution according to [P. Axelrad, R.G. Brown]:
f) Adding the to the initial state estimate gives an improved estimate of the state vector:
.
5) This new state vector can be used as new initial estimate and the procedure is repeated until the change in is sufficiently small.
Step 4: Transformation from Cartesian coordinate system to Geodetic coordinate system
The state vector calculated in Step 3 contains the MS position in ECEF Cartesian coordinates together with the MS receiver clock bias. Only the user position is of further interest. It is usually desirable to convert from ECEF coordinates xu, yu, zu to geodetic latitude , longitude and altitude h on the WGS84 reference ellipsoid.
Step 5: Calculation of "2-D Position Errors"
The latitude / longitude obtained after Step 4 is used to calculate the 2-D position error.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5 Sensitivity
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1 Sensitivity Coarse Time Assistance
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1.1 Definition
|
Sensitivity with coarse time assistance is the minimum level of GPS satellite signals required for the MS to make an A-GPS position estimate to a specific accuracy and within a specific response time when the network only provides coarse time assistance.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1.2 Conformance requirement
|
The first fix position estimates shall meet the accuracy and response time requirements in table 70.11.5.1.2 for the parameters specified in table 70.11.5.1.1.
Table 70.11.5.1.1: Test parameters for Sensitivity Coarse Time Assistance
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse Time assistance error range
seconds
2
GPS Signal for one satellite
dBm
-142
GPS Signal for remaining satellites
dBm
-147
Table 70.11.5.1.2: Conformance requirement for Sensitivity Coarse Time Assistance
Success rate
2-D position error
Max response time
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, sub clause M.2.1.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1.3 Test purpose
|
To verify the MS's first position estimate meets the Conformance requirement under GPS satellite signal conditions that represent weak signal conditions and with only Coarse Time Assistance provided by the SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1.4 Method of test
|
Initial conditions
Test environment: normal; see sub clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GPS test parameters as specified in table 70.11.5.1.3 for GPS scenario #1. Select the first satellite PRN defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the one satellite with the higher level.
3. Switch on the MS.
4. Set up a voice call according to the generic call set up procedure in sub clause 10.1, or for a device not supporting a voice call set up a signalling connection according to the generic call set up procedure in sub clause 10.1a, on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GPS scenario #1 as specified in TS 51.010-7 sub clause 5.2.1.2 with the MS location randomly selected to be within 3 km of the Reference Location and the altitude of the MS randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in TS 51.010-7 sub clause 5.2.1.2.4.
2. Send a RESET MS POSITIONING STORED INFORMATION message followed by RRLP Assistance Data and RRLP Measure Position Request messages containing appropriate assistance data; as specified in TS 51.010-7 sub clauses 5.2.2 and 5.2.6 for MS based testing; or sub clauses 5.2.4 and 5.2.6 for MS assisted testing with the value of GPS TOW offset by a random value as specified in TS 51.010-7 sub clause 5.2.6.2; as required to obtain a fix.
3. If the MS returns a valid result in the Measure Position Response message within the Max response time specified in table 70.11.5.1.4 then record the result and process it as specified in step 4. If the MS does not return a valid result within the Max response time specified in table 70.11.5.1.4 or reports a MS positioning error in the Measure Position Response message then record one Bad Result.
4. For MS based testing compare the reported Location Information in the Measure Position Response message against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.5.1.4 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GPS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in sub clause 70.11.4.3 and then compare the result against the simulated position of the MS, used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.5.1.4 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Select the first satellite PRN defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the one satellite with the higher level. Use new random values for the MS location and altitude in step 1 and for the GPS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of sub clause 70.11.5.1.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used select the next satellite PRN from the one used previously, defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7, for the one satellite with the higher level.
7. Terminate the call.
Minimum / Maximum duration of the test
Minimum duration approximately 1 hour, maximum duration approximately 20 hours
Specific Message Contents
MEASURE POSITION REQUEST (3GPP TS 44.031 sub clause A.2) to the MS
Information Element
Value/remark
Positioning Instructions
Accuracy
Required Response Time
51.2m
20s
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.1.5 Test Requirements
|
For the parameters specified in table 70.11.5.1.3 the MS shall meet the requirements and the success rate specified in table 70.11.5.1.4 with a confidence level of 95% according to annex A7.2.
Table 70.11.5.1.3: Test parameters for Sensitivity Coarse Time Assistance
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse Time assistance error range
seconds
1.8
GPS Signal for one satellite
dBm
-141
GPS Signal for remaining satellites
dBm
-146
Table 70.11.5.1.4: Test requirements for Sensitivity Coarse Time Assistance
Success rate
2-D position error
Max response time
95 %
101.3 m
20.3 s
NOTE: If the above Test Requirement differs from the Conformance requirement then the Test Parameter Relaxation applied for this test is non-zero. The Test Parameter Relaxation for this test is defined in sub clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in sub clause A5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2 Sensitivity Fine Time Assistance
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2.1 Definition
|
Sensitivity with fine time assistance is the minimum level of GPS satellite signals required for the MS to make an A-GPS position estimate to a specific accuracy and within a specific response time when the network provides fine time assistance in addition to coarse time assistance.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2.2 Conformance requirement
|
The first fix position estimates shall meet the accuracy and response time requirements in table 70.11.5.2.2 for the parameters specified in table 70.11.5.2.1.
Table 70.11.5.2.1: Test parameters for Sensitivity Fine Time Assistance
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse time assistance error range
seconds
2
GPS Fine Time assistance error range
s
10
GPS Signal for all satellites
dBm
-147
Table 70.11.5.2.2: Conformance requirement for Sensitivity Fine Time Assistance
Success rate
2-D position error
Max response time
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, sub clause M.2.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2.3 Test purpose
|
To verify the MS's first position estimate meets the Conformance requirement under GPS satellite signal conditions that represent weak signal conditions and with Fine Time Assistance provided by the SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2.4 Method of test
|
Initial conditions
Test environment: normal; see sub clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GPS test parameters as specified in table 70.11.5.2.3 for GPS scenario #1.
3. Switch on the MS.
4. Set up a voice call according to the generic call set up procedure in sub clause 10.1, or for a device not supporting a voice call set up a signalling connection according to the generic call set up procedure in sub clause 10.1a, on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GPS scenario #1 as specified in TS 51.010-7 sub clause 5.2.1.2 with the MS location randomly selected to be within 3 km of the Reference Location and the altitude of the MS randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in TS 51.010-7 sub clause 5.2.1.2.4.
2. Send a RESET MS POSITIONING STORED INFORMATION message followed by RRLP Assistance Data and RRLP Measure Position Request messages containing appropriate assistance data; as specified in TS 51.010-7 sub clauses 5.2.3 and 5.2.6 for MS based testing; or sub clauses 5.2.5 and 5.2.6 for MS assisted testing with the values of GPS TOW and BN offset by random values as specified in TS 51.010-7 sub clause 5.2.6.2; as required to obtain a fix.
3. If the MS returns a valid result in the Measure Position Response message within the Max response time specified in table 70.11.5.2.4 then record the result and process it as specified in step 4. If the MS does not return a valid result within the Max response time specified in table 70.11.5.2.4 or reports a MS positioning error in the Measure Position Response message then record one Bad Result.
4. For MS based testing compare the reported Location Information in the Measure Position Response message against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.5.2.4 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GPS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in sub clause 70.11.4.3 and then compare the result against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.5.2.4 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Use new random values for the MS location and altitude in step 1 and for the GPS TOW and BN offsets in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of sub clause 70.11.5.2.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again.
7. Terminate the call.
Minimum / Maximum duration of the test
Minimum duration approximately 1 hour, maximum duration approximately 20 hours
Specific Message Contents
MEASURE POSITION REQUEST (3GPP TS 44.031 sub clause A.2) to the MS
Information Element
Value/remark
Positioning Instructions
Accuracy
Required Response Time
51.2m
20s
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.5.2.5 Test Requirements
|
For the parameters specified in table 70.11.5.2.3 the MS shall meet the requirements and the success rate specified in table 70.11.5.2.4 with a confidence level of 95% according to annex A7.2.
Table 70.11.5.2.3: Test parameters for Sensitivity Fine Time Assistance
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse time assistance error range
seconds
1.8
GPS Fine Time assistance error range
s
9
GPS Signal for all satellites
dBm
-146
Table 70.11.5.2.4: Test requirements for Sensitivity Fine Time Assistance
Success rate
2-D position error
Max response time
95 %
101.3 m
20.3 s
NOTE: If the above Test Requirement differs from the Conformance requirement then the Test Parameter Relaxation applied for this test is non-zero. The Test Parameter Relaxation for this test is defined in sub clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in sub clause A5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6 Nominal Accuracy
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6.1 Definition
|
Nominal accuracy is the accuracy of the MS's A-GPS position estimate under ideal GPS signal conditions.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6.2 Conformance requirement
|
The first fix position estimates shall meet the accuracy and response time requirements in table 70.11.6.2 for the parameters specified in table 70.11.6.1.
Table 70.11.6.1: Test parameters for Nominal Accuracy
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse Time assistance error range
seconds
2
GPS Signal for all satellites
dBm
-130
Table 70.11.6.2: Conformance requirement for Nominal Accuracy
Success rate
2-D position error
Max response time
95 %
30 m
20 s
The reference for this requirement is 3GPP TS 45.005, sub clause M.2.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6.3 Test purpose
|
To verify the MS's first position estimate meets the Conformance requirement under GPS satellite signal conditions that represent ideal conditions.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6.4 Method of test
|
Initial conditions
Test environment: normal; see sub clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GPS test parameters as specified in table 70.11.6.3 for GPS scenario #1.
3. Switch on the MS.
4. Set up a voice call according to the generic call set up procedure in sub clause 10.1, or for a device not supporting a voice call set up a signalling connection according to the generic call set up procedure in sub clause 10.1a, on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GPS scenario #1 as specified in TS 51.010-7 sub clause 5.2.1.2 with the MS location randomly selected to be within 3 km of the Reference Location and the altitude of the MS randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in TS 51.010-7 sub clause 5.2.1.2.4.
2. Send a RESET MS POSITIONING STORED INFORMATION message followed by RRLP Assistance Data and RRLP Measure Position Request messages containing appropriate assistance data; as specified in TS 51.010-7 sub clauses 5.2.2 and 5.2.6 for MS based testing; or sub clauses 5.2.4 and 5.2.6 for MS assisted testing with the value of GPS TOW offset by a random value as specified in TS 51.010-7 sub clause 5.2.6.2; as required to obtain a fix.
3. If the MS returns a valid result in the Measure Position Response message within the Max response time specified in table 70.11.6.4 then record the result and process it as specified in step 4. If the MS does not return a valid result within the Max response time specified in table 70.11.6.4 or reports a MS positioning error in the Measure Position Response message then record one Bad Result.
4. For MS based testing compare the reported Location Information in the Measure Position Response message against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.6.4 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GPS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in sub clause 70.11.4.3 and then compare the result against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.6.4 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Use new random values for the MS location and altitude in step 1 and for the GPS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of sub clause 70.11.6.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again.
7. Terminate the call.
Minimum / Maximum duration of the test
Minimum duration approximately 1 hour, maximum duration approximately 20 hours
Specific Message Contents
MEASURE POSITION REQUEST (3GPP TS 44.031 sub clause A.2) to the MS
Information Element
Value/remark
Positioning Instructions
Accuracy
Required Response Time
16m
20s
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.6.5 Test Requirements
|
For the parameters specified in table 70.11.6.3 the MS shall meet the requirements and the success rate specified in table 70.11.6.4 with a confidence level of 95% according to annex A7.2.
Table 70.11.6.3: Test parameters for Nominal Accuracy
Parameters
Unit
Value
Number of generated satellites
-
8
HDOP Range
-
1.1 to 1.6
Propagation conditions
-
AWGN
GPS Coarse Time assistance error range
seconds
1.8
GPS Signal for all satellites
dBm
-130
Table 70.11.6.4: Test requirements for Nominal Accuracy
Success rate
2-D position error
Max response time
95 %
31.3 m
20.3 s
NOTE: If the above Test Requirement differs from the Conformance requirement then the Test Parameter Relaxation applied for this test is non-zero. The Test Parameter Relaxation for this test is defined in sub clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in sub clause A5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7 Dynamic Range
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7.1 Definition
|
Dynamic Range is the maximum difference in level of the GPS signals from a number of satellites that allows the MS to make an A-GPS position estimate with a specific accuracy and a specific response time.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7.2 Conformance requirement
|
The first fix position estimates shall meet the accuracy and response time requirements in table 70.11.7.2 for the parameters specified in table 70.11.7.1.
Table 70.11.7.1: Test parameters for Dynamic Range
Parameters
Unit
Value
Number of generated satellites
-
6
HDOP Range
-
1.4 to 2.1
GPS Coarse Time assistance error range
seconds
2
Propagation conditions
-
AWGN
GPS Signal for 1st satellite
dBm
-129
GPS Signal for 2nd satellite
dBm
-135
GPS Signal for 3rd satellite
dBm
-141
GPS Signal for 4th satellite
dBm
-147
GPS Signal for 5th satellite
dBm
-147
GPS Signal for 6th satellite
dBm
-147
Table 70.11.7.2: Conformance requirement for Dynamic Range
Success rate
2-D position error
Max response time
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, sub clause M.2.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7.3 Test purpose
|
To verify the MS's first position estimate meets the Conformance requirement under GPS satellite signal conditions that have a wide dynamic range. Strong satellites are likely to degrade the acquisition of weaker satellites due to their cross‑correlation products.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7.4 Method of test
|
Initial conditions
Test environment: normal; see sub clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GPS test parameters as specified in table 70.11.7.3 for GPS scenario #1. Select the first three satellite PRNs defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the three satellites with the higher levels.
3. Switch on the MS.
4. Set up a voice call according to the generic call set up procedure in sub clause 10.1, or for a device not supporting a voice call set up a signalling connection according to the generic call set up procedure in sub clause 10.1a, on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GPS scenario #1 as specified in TS 51.010-7 sub clause 5.2.1.2 with the MS location randomly selected to be within 3 km of the Reference Location and the altitude of the MS randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in TS 51.010-7 sub clause 5.2.1.2.4.
2. Send a RESET MS POSITIONING STORED INFORMATION message followed by RRLP Assistance Data and RRLP Measure Position Request messages containing appropriate assistance data; as specified in TS 51.010-7 sub clauses 5.2.2 and 5.2.6 for MS based testing; or sub clauses 5.2.4 and 5.2.6 for MS assisted testing with the value of GPS TOW offset by a random value as specified in TS 51.010-7 sub clause 5.2.6.2; as required to obtain a fix.
3. If the MS returns a valid result in the Measure Position Response message within the Max response time specified in table 70.11.7.4 then record the result and process it as specified in step 4. If the MS does not return a valid result within the Max response time specified in table 70.11.7.4 or reports a MS positioning error in the Measure Position Response message then record one Bad Result.
4. For MS based testing compare the reported Location Information in the Measure Position Response message against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.7.4 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GPS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in sub clause 70.11.4.3 and then compare the result against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.7.4 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Select the first three satellite PRNs defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the three satellites with the higher levels. Use new random values for the MS location and altitude in step 1 and for the GPS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of sub clause 70.11.7.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used, increment the set of three satellite PRNs by one from the ones used previously, defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7, for the three satellites with the higher levels (i.e. if the set of satellites is a, b, c, d, e, f and the first set used was a, b, c, the second set shall be b, c, d and so on).
7. Terminate the call.
Minimum / Maximum duration of the test
Minimum duration approximately 1 hour, maximum duration approximately 20 hours
Specific Message Contents
MEASURE POSITION REQUEST (3GPP TS 44.031 sub clause A.2) to the MS
Information Element
Value/remark
Positioning Instructions
Accuracy
Required Response Time
51.2m
20s
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.7.5 Test Requirements
|
For the parameters specified in table 70.11.7.3 the MS shall meet the requirements and the success rate specified in table 70.11.7.4 with a confidence level of 95% according to annex A7.2.
Table 70.11.7.3: Test parameters for Dynamic Range
Parameters
Unit
Value
Number of generated satellites
-
6
HDOP Range
-
1.4 to 2.1
GPS Coarse Time assistance error range
seconds
1.8
Propagation conditions
-
AWGN
GPS Signal for 1st satellite
dBm
-128.2
GPS Signal for 2nd satellite
dBm
-134
GPS Signal for 3rd satellite
dBm
-140
GPS Signal for 4th satellite
dBm
-146
GPS Signal for 5th satellite
dBm
-146
GPS Signal for 6th satellite
dBm
-146
Table 70.11.7.4: Test requirements for Dynamic Range
Success rate
2-D position error
Max response time
95 %
101.3 m
20.3 s
NOTE: If the above Test Requirement differs from the Conformance requirement then the Test Parameter Relaxation applied for this test is non-zero. The Test Parameter Relaxation for this test is defined in sub clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in sub clause A5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8 Multi-Path scenario
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8.1 Definition
|
Multi-path performance measures the accuracy and response time of the MS's A-GPS position estimate in a specific GPS signal multi-path environment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8.2 Conformance requirement
|
The first fix position estimates shall meet the accuracy and response time requirements in table 70.11.8.2 for the parameters specified in table 70.11.8.1.
Table 70.11.8.1: Test parameters for Multi-Path scenario
Parameters
Unit
Value
Number of generated satellites (see note)
-
5
GPS Coarse Time assistance error range
seconds
2
HDOP Range
-
1.8 to 2.5
GPS signal for Satellite 1, 2 (see note)
dBm
-130
GPS signal for Satellite 3, 4, 5 (see note)
dBm
LOS signal of -130 dBm, multi-path signal of -136 dBm
NOTE: Satellites 1, 2 no multi-path. Satellites 3, 4, 5 multi-path defined in sub clause 70.11.2.4.
Table 70.11.8.2: Conformance requirement for Multi-Path scenario
Success rate
2-D position error
Max response time
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, sub clause M.2.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8.3 Test purpose
|
To verify the MS's first position estimate meets the Conformance requirement under GPS satellite signal conditions that represent simple multi-path conditions.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8.4 Method of test
|
Initial conditions
Test environment: normal; see sub clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GPS test parameters as specified in table 70.11.8.3 for GPS scenario #1. Select the first two satellite PRNs defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the two satellites with the higher levels.
3. Switch on the MS.
4. Set up a voice call according to the generic call set up procedure in sub clause 10.1, or for a device not supporting a voice call set up a signalling connection according to the generic call set up procedure in sub clause 10.1a, on a channel in the Mid ARFCN range.
Specific PICS statements:
-
PIXIT statements:
-
Procedure
1. Start GPS scenario #1 as specified in TS 51.010-7 sub clause 5.2.1.2 with the MS location randomly selected to be within 3 km of the Reference Location and the altitude of the MS randomly selected between 0 m to 500 m above WGS‑84 reference ellipsoid using the method described in TS 51.010-7 sub clause 5.2.1.2.4. The initial carrier phase difference between taps of the multi-path model shall be randomly selected between 0 and 2radians by selecting the next random number from a standard uniform random number generator, in the range 0 to 2, representing radians with a resolution of 0.1, representing 0.1 radians.
2. Send a RESET MS POSITIONING STORED INFORMATION message followed by RRLP Assistance Data and RRLP Measure Position Request messages containing appropriate assistance data; as specified in TS 51.010-7 sub clauses 5.2.2 and 5.2.6 for MS based testing; or sub clauses 5.2.4 and 5.2.6 for MS assisted testing with the value of GPS TOW offset by a random value as specified in TS 51.010-7 sub clause 5.2.6.2; as required to obtain a fix.
3. If the MS returns a valid result in the Measure Position Response message within the Max response time specified in table 70.11.8.4 then record the result and process it as specified in step 4. If the MS does not return a valid result within the Max response time specified in table 70.11.8.4 or reports a MS positioning error in the Measure Position Response message then record one Bad Result.
4. For MS based testing compare the reported Location Information in the Measure Position Response message against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.8.4 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GPS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in sub clause 70.11.4.3 and then compare the result against the simulated position of the MS used in step 1, and calculate the 2D position error as specified in sub clause 70.11.4.2.3. Compare the 2D position error against the value in table 70.11.8.4 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GPS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Select the first two satellite PRNs defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7 for the two satellites with the higher levels. Use new random values for the MS location and altitude, and the initial carrier phase difference between taps of the multi-path model in step 1 and for the GPS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of sub clause 70.11.8.5 are met. Each time scenario #1 or #2 is used, the start time of the GPS scenario shall be advanced by 2 minutes from the time used previously for that scenario. Once a scenario reaches the end of its viable running time, restart it from its nominal start time again. Each time scenario #1 or #2 is used, increment the set of two satellite PRNs by one from the ones used previously, defined in the table in sub clause 5.2.1.2.5 in TS 51.010-7, for the two satellites with the higher level (i.e. if the set of satellites is a, b, c, d, e and the first set used was a, b the second set shall be b, c and so on).
7. Terminate the call
Minimum / Maximum duration of the test
Minimum duration approximately 1 hour, maximum duration approximately 20 hours
Specific Message Contents
MEASURE POSITION REQUEST (3GPP TS 44.031 sub clause A.2) to the MS
Information Element
Value/remark
Positioning Instructions
Accuracy
Required Response Time
51.2m
20s
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.11.8.5 Test Requirements
|
For the parameters specified in table 70.11.8.3 the MS shall meet the requirements and the success rate specified in table 70.11.8.4 with a confidence level of 95% according to annex A7.2.
Table 70.11.8.3: Test parameters for Multi-Path scenario
Parameters
Unit
Value
Number of generated satellites (see note)
-
5
GPS Coarse Time assistance error range
seconds
1.8
HDOP Range
-
1.8 to 2.5
GPS signal for Satellite 1, 2 (see note)
dBm
-130
GPS signal for Satellite 3, 4, 5 (see note)
dBm
LOS signal of -130 dBm, multi-path signal of -136.2 dBm
NOTE: Satellites 1, 2 no multi-path. Satellites 3, 4, 5 multi-path defined in sub clause 70.11.2.4.
Table 70.11.8.4: Test requirements for Multi-Path scenario
Success rate
2-D position error
Max response time
95 %
101.3 m
20.3 s
NOTE: If the above Test Requirement differs from the Conformance requirement then the Test Parameter Relaxation applied for this test is non-zero. The Test Parameter Relaxation for this test is defined in sub clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in sub clause A5.5.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.12 Assisted GNSS General Procedures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.12.1 Positioning Capability Transfer procedure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.12.1.1 Conformance requirement:
|
When the MS receives a complete POSITIONING CAPABILITY REQUEST message, it shall send the POSITIONING CAPABILITY RESPONSE message. The message shall include the positioning capabilities of the MS and the types of supported assistance data. The message may include the types of assistance needed by the MS to obtain a location estimate or positioning measurements.
Test References
3GPP TS 43.059 sub clause 9.4.3a
3GPP TS 44.031sub clauses 2.3a, 4.6, 4.7, A.7 and A.8
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.12.1.2 Test Purpose
|
To verify that the MS sends the correct positioning capabilities and the types of supported assistance data in the POSITIONING CAPABILITY RESPONSE message. Note: no positioning procedure is performed.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.12.1.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability.
After sending the CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION message containing an RRLP POSITIONING CAPABILITY REQUEST message.
The MS sends a POSITIONING CAPABILITY RESPONSE message. The message includes the positioning capabilities of the MS and the types of supported assistance data.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS->MS
PAGING REQUEST TYPE I
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates “answer to paging”.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS->SS
PAGING RESPONSE
Message is contained in SABM.
“mobile station classmark 2” includes settings for ES_IND.
5
MS->SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The setting for positioning specifies Positioning Method capability, Positioning Method Support and Additional Positioning Capabilities.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESPONSE
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
13
SS -> MS
CHANNEL RELEASE
The main signalling link is released
Specific Message Contents
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 11, RRLP Positioning Capability Request
Step 12: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 11).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May be included if the MS supports A-GPS L1 C/A in addition to A‑GANSS
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Dependent on MS capabilities. Absence of this field indicates Galileo
gANSSPositioningMethodTypes
BIT STRING
Bit 0 is set to 1 (MS-Assisted) and/or Bit 1 is set to 1 (MS-Based) depending on the positioning method(s) supported by the MS for the GANSS
gANSSSignals
BIT STRING
Dependent on MS capabilities
sbasID
BIT STRING
Included if ganssID indicates support for SBAS.
Dependent on MS capabilities
multipleMeasurementSets
Dependent on MS capabilities
assistanceSupported
SEQUENCE
gpsAssistance
BIT STRING
Dependent on MS capabilities Included if the MS supports A-GPS L1 C/A in addition to A‑GANSS
gANSSAssistanceSet
SEQUENCE
commonGANSSAssistance
BIT STRING
Dependent on MS capabilities
specificGANSSAssistance
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Dependent on MS capabilities. Absence of this field indicates Galileo
gANSSAssistance
BIT STRING
Dependent on MS capabilities
gANSSAdditionalAssistanceChoices
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Dependent on MS capabilities. Absence of this field indicates Galileo
ganssClockModelChoice
BIT STRING
Dependent on MS capabilities
gannsOrbitModelChoice
BIT STRING
Dependent on MS capabilities
ganssAlmanacModelChoice
BIT STRING
Dependent on MS capabilities
ganssAdditionalUTCModelChoice
BIT STRING
Dependent on MS capabilities
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13 Assisted GNSS Network Induced Location Request (NI-LR)
|
70.13.1 NI-LR / Emergency Call on TCH Radio Channel for Mobiles Supporting MS-Based GNSS
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.1.1 Conformance requirements
|
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM900 and 1800 MS), or 911 (for PCS 1900 MS in the USA), or 08 (for PCS 1900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. When a user requests an emergency call establishment the mobile station will send a CM SERVICE REQUEST message to the network with a CM service type information element indicating emergency call establishment and the correct CKSN and TMSI. A mobile station which implements the “LCS” option shall also implement the “Controlled Early Classmark Sending” option. A mobile station which implements the “Controlled Early Classmark Sending” option shall indicate it in the classmark (ES IND bit).
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The “Mobile Station Classmark 3” information element shall correctly specify the positioning methods supported by the MS and shall indicate support for additional positioning capabilities which can be retrieved using RRLP.
7. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
8. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
9. On receiving the POSITIONING CAPABILITY REQUEST message the MS responds with a POSITIONING CAPABILITY RESPONSE message indicating the positioning methods supported by the MS.
10. On receiving an ASSISTANCE DATA message the MS responds with an ASSISTANCE DATA ACKNOWLEDGEMENT message. The message contains the reference number of the ASSISTANCE DATA message received.
11. On receiving the MEASURE POSITION REQUEST message the MS tries to perform the requested location measurements, and calculates its own position. It sends the results in the RRLP MEASURE POSITION RESPONSE message.
References
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9, 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.1.2 Test Purpose
|
To verify when a network instigates the LCS positioning procedure using GNSS by sending RRLP (Measure Position Request) message, after a traffic channel has been established during an emergency call, the mobile responds with RRLP (Measure Position Response) containing MS location estimate.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.1.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valued TMSI and CKSN.
SIM:
Normal SIM
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub test cases dependent on the GNSS supported by the MS. Each sub test case is identified by a Sub Test Case Number as defined below:
Sub Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
An Emergency Call is initiated with the MS. SIM card is included in the MS.
The emergency call is established with a late assignment.
After receiving the CONNECT ACKNOWLEDGE message from the MS, the SS sends RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS sends one or more RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages dependent on the GNSS positioning methods supported by the MS. The reception of each RRLP Assistance Data message is acknowledged by the MS by sending a RR APPLICATION INFORMATION message containing an RRLP Assistance Data Acknowledgement component.
The SS then sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request on FACCH including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The call is cleared by the SS.
Maximum duration of the test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The appropriate “emergency call number" is entered.
2
MS -> SS
CHANNEL REQUEST
Establishment cause is emergency call establishment.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. The CM service type IE indicates "emergency call establishment".
“mobile station classmark 2” includes settings for ES_IND.
5
MS->SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The Additional Positioning Capabilities (1 bit field) is set to 1 (the mobile station supports additional positioning capabilities which can be retrieved using RRLP).
6
SS -> MS
CM SERVICE ACCEPT
7
MS -> SS
EMERGENCY SETUP
8
SS -> MS
CALL PROCEEDING
9
SS -> MS
ALERTING
10
SS -> MS
ASSIGNMENT COMMAND
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> MS
CONNECT
13
MS -> SS
CONNECT ACKNOWLEDGE
The MS indicates that the TCH is through connected in both directions.
14
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
15
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
16
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
The SS provides assistance data in one or more RRLP assistance data delivery messages as defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
17
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
Each RRLP Assistance Data message is acknowledged by the MS.
18
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
May contain further assistance data as defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
19
MS -> SS
RR APPLICATION INFORMATION
Option 1:
RRLP Measure Position Response:
ganssLocationInfo
Option 2:
locationError with gpsAssDataMissing (Sub Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub Tests 3, 4 and 10) and/or ganssAssistanceData
19a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 19 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
19b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 19a, the MS acknowledges the received assistance data.
19c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 19 that is available in the SS, this message may include further assistance data.
19d
MS-> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Response.
If the MS requested additional assistance data in step 19, this message contains ganssLocationInfo.
20
SS -> MS
DISCONNECT
21
MS -> SS
RELEASE
22
SS -> MS
RELEASE COMPLETE
23
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Steps 18 and 19c: RRLP Measure Position Request
Steps 19 and 19d: RRLP Measure Position Response
Steps 16 and 19a: RRLP Assistance Data
Steps 17 and 19b: RRLP Assistance Data Ack.
Step 14: RRLP Positioning Capability Request
Step 15: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 15):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 14).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub Test 1: value 3
Sub Test 2: absent
Sub Test 3: value 1
Sub Test 4: value 3
Sub Test 9: value 4
Sub Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 1 (msBased) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Assistance Data (Step 16):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message at step 16 the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
RRLP Assistance Data Ack (Step 17, 19b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 19b)
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 18):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub Test 1: bit 5 set to value 1
Sub Test 2: bit 1 set to value 1
Sub Test 3: bits 0 and 3 set to
value 1
Sub Test 4: bits 0 and 5 set to
value 1
Sub Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
RRLP Measure Position Response (Step 19 (Option 1) or 19d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 19d)
component
CHOICE
msrPositionRsp
(A valid response will contain ganssLocationInfo otherwise locationError will be returned)
locationError
SEQUENCE
Any error value is acceptable.
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssLocationInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 19 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing GPS assistance data elements.
This field may only be present for Sub Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 19a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 19 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 19 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Measure Position Request (Step 19c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 19 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub Test 1: bit 5 set to value 1
Sub Test 2: bit 1 set to value 1
Sub Test 3: bits 0 and 3 set to
value 1
Sub Test 4: bits 0 and 5 set to
value 1
Sub Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 19 (Option 2).
70.13.2 NI-LR / Emergency Call on TCH Radio Channel for Mobiles Supporting MS-Assisted GNSS
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.2.1 Conformance requirements
|
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM900 and 1800 MS), or 911 (for PCS 1900 MS in the USA), or 08 (for PCS 1900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
7. When a user requests an emergency call establishment the mobile station will send a CM SERVICE REQUEST message to the network with a CM service type information element indicating emergency call establishment and the correct CKSN and TMSI. A mobile station which implements the “LCS” option shall also implement the “Controlled Early Classmark Sending” option. A mobile station which implements the “Controlled Early Classmark Sending” option shall indicate it in the classmark (ES IND bit).
8. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The “Mobile Station Classmark 3” information element shall correctly specify the positioning methods supported by the MS and shall indicate support for additional positioning capabilities which can be retrieved using RRLP.
9. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
10. After receipt of a CONNECT ACKNOWLEDGE message during establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
11. On receiving the POSITIONING CAPABILITY REQUEST message the MS responds with a POSITIONING CAPABILITY RESPONSE message indicating the positioning methods supported by the MS.
12. On receiving the RRLP MEASURE POSITION REQUEST the MS tries to perform the requested location measurements. It sends the results in the RRLP MEASURE POSITION RESPONSE message.
References
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.2.2 Test Purpose
|
To verify when a network instigates the LCS positioning procedure using GNSS by sending RRLP (Measure Position Request) message, after a traffic channel has been established during an emergency call, the mobile responds with RRLP (Measure Position Response) containing A-GNSS measurement values.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.13.2.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valued TMSI and CKSN.
SIM:
Normal SIM
Specific PICSstatements
-
PIXIT statements
-
Test Procedure
This test case includes sub test cases dependent on the GNSS supported by the MS. Each sub test case is identified by a Sub Test Case Number as defined below:
Sub Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
An Emergency Call is initiated with the MS. SIM card is included in the MS.
The emergency call is established with a late assignment.
After receiving the CONNECT ACKNOWLEDGE message from the MS, the SS sends RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request on FACCH including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The call is cleared by the SS.
Maximum duration of the test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The appropriate “emergency call number" is entered.
2
MS -> SS
CHANNEL REQUEST
Establishment cause is emergency call establishment.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. The CM service type IE indicates "emergency call establishment".
“mobile station classmark 2” includes settings for ES_IND.
5
MS->SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The Additional Positioning Capabilities (1 bit field) is set to 1 (the mobile station supports additional positioning capabilities which can be retrieved using RRLP).
6
SS -> MS
CM SERVICE ACCEPT
7
MS -> SS
EMERGENCY SETUP
8
SS -> MS
CALL PROCEEDING
9
SS -> MS
ALERTING
10
SS -> MS
ASSIGNMENT COMMAND
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> MS
CONNECT
13
MS -> SS
CONNECT ACKNOWLEDGE
The MS indicates that the TCH is through connected in both directions.
14
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
15
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
16
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
Contains assistance data as defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
17
MS -> SS
RR APPLICATION INFORMATION
Option 1:
RRLP Measure Position Response:
ganssMeasureInfo and gps-MeasureInfo (Sub Tests 3, 4 and 10)
Option 2:
locationError with gpsAssDataMissing (Sub Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub Tests 3, 4 and 10) and/or ganssAssistanceData
17a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 17 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
17b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 17a, the MS acknowledges the received assistance data.
17c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 17 that is available in the SS, this message may include further assistance data.
17d
MS -> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Response.
If the MS requested additional assistance data in step 17, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub Tests 3, 4 and 10).
18
SS -> MS
DISCONNECT
19
MS -> SS
RELEASE
20
SS -> MS
RELEASE COMPLETE
21
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 16 and 17c: RRLP Measure Position Request
Step 17 and 17d: RRLP Measure Position Response
Step 17a: RRLP Assistance Data
Step 17b: RRLP Assistance Data Ack.
Step 14: RRLP Positioning Capability Request
Step 15: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 15):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 14).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub Test 1: value 3
Sub Test 2: absent
Sub Test 3: value 1
Sub Test 4: value 3
Sub Test 9: value 4
Sub Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Measure Position Request (Step 16):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub Test 1: bit 5 set to value 1
Sub Test 2: bit 1 set to value 1
Sub Test 3: bits 0 and 3 set to
value 1
Sub Test 4: bits 0 and 5 set to
value 1
Sub Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
RRLP Measure Position Response (Step 17 (Option 1) or Step 17d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 17d)
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 17 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing GPS assistance data elements.
This field may only be present for Sub Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 17a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 17b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 17c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 17 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub Test 1: bit 5 set to value 1
Sub Test 2: bit 1 set to value 1
Sub Test 3: bits 0 and 3 set to
value 1
Sub Test 4: bits 0 and 5 set to
value 1
Sub Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 17 (Option 2).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14 Assisted GNSS Mobile Originated Location Request (MO-LR)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.1 MO-LR / Idle mode for Mobiles Supporting MS-Assisted GNSS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.1.1 Conformance requirements
|
1) The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2) The MS invokes self-location request by sending REGISTER message containing Facility IE LCS MO-LR with MOLR-TYPE set to locationEstimate.
3) The MS needs to interact with the network for each separate location request.
4) On receiving an RRLP MEASURE POSITION REQUEST message the MS tries to perform the requested location measurements. It sends the results in an RRLP MEASURE POSITION RESPONSE message.
5) The network returns an LCS result to the MS carrying location estimate requested by the MS in FACILITY message.
6) The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
3GPP TS 44.031
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.1.2 Test Purpose
|
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the Facility IE LCS MO-LR. When the MS receives a FACILITY message containing a Facility IE MO-LR LCS result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.1.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CSKN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The MS invokes call independent supplementary service through a CM SERVICE REQUEST.
The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request.
The SS sends an RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When MS receives FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate LCS MOLR Procedure (location estimation)
2
MS -> SS
CHANNEL REQUEST
establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
The CM service type IE indicates "Supplementary service activation".
"mobile station classmark 2" includes settings for ES_IND.
5
MS->SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The Additional Positioning Capabilities (1 bit field) is set to 1 (the mobile station supports additional positioning capabilities which can be retrieved using RRLP).
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESPONSE
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE with
LCS-MOLR request with MOLR-Type set to locationEstimate
12
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
13
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
14
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request.
Contains assistance data as defined in sub clause 70.1.3.
15
MS -> SS
RR APPLICATION INFORMATION
Option 1:
RRLP Measure Position Response:
ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10)
Option 2:
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData
15a
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data.
If the MS requested additional assistance data in step 15 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
15b
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 15a, the MS acknowledges the received assistance data.
15c
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request.
If the MS requested additional assistance data in step 15 that is available in the SS, this message may include further assistance data.
15d
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response.
If the MS requested additional assistance data in step 15, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
16
SS -> MS
FACILITY
LCS MO-LR result message containing location estimate
17
MS -> SS
RELEASE COMPLETE
MS terminates the dialogue
18
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 11):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 12: RRLP Positioning Capability Request
Step 13: RRLP Positioning Capability Response
Step 14 and 15c: RRLP Measure Position Request
Step 15 and 15d: RRLP Measure Position Response
Step 15a: RRLP Assistance Data
Step 15b: RRLP Assistance Data Ack.
RRLP Positioning Capability Request (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 12).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Measure Position Request (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 15 (Option 1) or Step 15d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 15d)
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 15 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements
This field may only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 15a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub-Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 15 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 15 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 15b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 15c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 15 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 15 (Option 2).
FACILITY (Step 16):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010)
Facility
Return Result = LCS-MOLR
LCS-MOLRRes -> locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo and/or ganssMeasureInfo values
RELEASE COMPLETE (Step 17):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.2 MO-LR / Idle mode for Mobiles Supporting MS-Based GNSS / Assistance Data Request
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.2.1 Conformance requirements
|
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes self-location request by sending REGISTER message containing Facility IE LCS MO-LR with MOLR-TYPE set to assistance data.
3. The MS sends RRLP ASSISTANCE DATA ACK for each RRLP ASSISTANCE DATA component
4. The network shall returns an LCS result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
5. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
3GPP TS 44.031
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.2.2 Test Purpose
|
To verify that a MS invokes a self-location request by sending the network a REGISTER message containing an LCS-MOLR REQ of type “Assistance data”. On receipt of each RRLP ASSISTANCE DATA from SS with the requested assistance data, MS shall send RRLP ASSISTANCE ACK for each component to SS. When the MS receives a FACILITY message containing a LCS-MOLR return result for the acknowledgement of completing assistance data delivery, it clears the transaction by sending a RELEASE COMPLETE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.2.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CSKN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The MS invokes call independent supplementary service through a CM SERVICE REQUEST.
The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request, with MOLR- TYPE set to assistance data.
The SS sends a number of RRLP Assistance Data components and MS sends RRLP Assistance Data Ack for each component.
SS sends LCS-MOLR Return Result for acknowledgement of completion of assistance data delivery.
The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test
10 minutes.
Expected Sequence
Normal Case:
Step
Direction
Message
Comments
1
MS
Initiate LCS MOLR Procedure (assistance data request)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Establishment cause indicates "Supplementary service activation".
"mobile station classmark 2" includes settings for ES_IND.
5
MS -> SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The Additional Positioning Capabilities (1 bit field) is set to 1 (the mobile station supports additional positioning capabilities which can be retrieved using RRLP).
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
8
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
9
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
10
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR with MOLR-Type set to assistanceData.
11n
SS -> MS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA
The number of instances of this message depends on the amount of assistance data requested in step 10
12n
MS -> SS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA ACK
Each instance of RRLP ASSISTANCE DATA message in step 11n is acknowledged
13
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT
14
MS -> SS
RELEASE COMPLETE
Terminates the session
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
MOLR-Type-> assistanceData
Location Method-> assistedGANSS / assistedGPSandGANSS (Sub-Tests 3, 4 and 10)
gpsAssistanceData-> any value is acceptable
ganssAssistanceData-> any value is acceptable
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 11n: RRLP Assistance Data
Step 12n: RRLP Assistance Data Ack.
RRLP Assistance Data (Step 11n):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message at step 11n the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Assistance Data Ack (Step 12n):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
assistanceDataAck
FACILITY (Step 13):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes -> empty (Note)
Note: For acknowledgement of assistance data delivery procedure, SS shall send LCS-MOLR Facility return result to MS, there is no parameter for this.
RELEASE COMPLETE (Step 14):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx11 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.3 MO-LR / Idle mode for Mobiles Supporting MS-Based GNSS / Location Estimate Request
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.3.1 Conformance requirements
|
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes self-location request by sending REGISTER message containing Facility IE LCS MO-LR with MOLR-TYPE set to locationEstimate.
3. On receiving the POSITIONING CAPABILITY REQUEST message the MS responds with a POSITIONING CAPABILITY RESPONSE message indicating the positioning methods supported by the MS.
4. On receiving an RRLP MEASURE POSITION REQUEST message, the MS tries to perform the requested location measurements, and possibly calculates it own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC.
5. The network shall returns an LCS result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
6. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
3GPP TS 44.031
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.3.2 Test Purpose
|
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing an MO-LR Request of type “locationEstimate”. When the MS receives a FACILITY message containing a MO-LR return result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.3.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CSKN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The MS invokes call independent supplementary service through a CM SERVICE REQUEST.
The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request, with MOLR-TYPE set to locationEstimate.
The SS sends an RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
10 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimation)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
The CM Service Type IE indicates "Supplementary service activation".
"mobile station classmark 2" includes settings for ES_IND.
5
MS -> SS
CLASSMARK CHANGE
“mobile station classmark 2” includes settings for ES_IND.
“mobile station classmark 3” includes settings for Positioning. The Additional Positioning Capabilities (1 bit field) is set to 1 (the mobile station supports additional positioning capabilities which can be retrieved using RRLP).
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESPONSE
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
with LCS-MOLR request and MO-LR Type set to “locationEstimate”.
12
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
13
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
14
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
The SS provides assistance data in one or more RRLP assistance data delivery messages as defined in sub clause 70.1.3. Each message shall contain a maximum of 242 octets.
15
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
Each RRLP Assistance Data message is acknowledged by the MS.
16
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
May contain further assistance data as defined in sub clause 70.1.3.
17
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response:
ganssLocationInfo (Option 1)
or
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData
17a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 17 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
17b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 17a, the MS acknowledges the received assistance data.
17c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 17 that is available in the SS, this message may include further assistance data.
17d
MS-> SS
RR APPLICATION INFORMATION
Option 2 only:
RRLP Measure Position Response.
If the MS requested additional assistance data in step 17, this message contains ganssLocationInfo.
18
Void
19
Void
20
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT message containing location estimate
21
MS -> SS
RELEASE COMPLETE
MS terminates the dialogue
22
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 11):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
MOLR-Type->locationEstimate
SS version indicator
Value 1 or above
RRLP Positioning Capability Request (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 12).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 1 (msBased) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 12: RRLP Positioning Capability Request
Step 13: RRLP Positioning Capability Response
Steps 16 and 17c: RRLP Measure Position Request
Steps 17 and 17d: RRLP Measure Position Response
Steps 14, 17a: RRLP Assistance Data
Steps 15, 17b: RRLP Assistance Data Ack.
RRLP Assistance Data (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message at step 14 the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Assistance Data Ack (Steps 15, 17b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 17b)
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 16):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 17 (Option 1) or 17d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 17d)
component
CHOICE
msrPositionRsp
(A valid response will contain ganssLocationInfo otherwise locationError will be returned)
locationError
SEQUENCE
Any error value is acceptable.
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssLocationInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 17 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing GPS assistance data elements.
This field may only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 17a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub-Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Measure Position Request (Step 17c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 17 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 17 (Option 2).
FACILITY (Step 20):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes -> locationEstimate
RELEASE COMPLETE (Step 22):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.4 MO-LR / Dedicated Mode for Mobiles Supporting MS-Assisted GNSS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.4.1 Conformance Requirement:
|
The MS sends a DTAP LCS MO-LR invoke to the VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component with MO_LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 03.71, sub clause 7.6.6.
3GPP TS 04.30, sub clause 5.1.1.
3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.4.2 Test Purpose
|
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the Facility IE LCS MO-LR on an already established speech call related main DCCH (FACCH). When the MS receives a FACILITY message containing a Facility IE MO-LR LCS result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.4.3 Method of Test
|
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS has valid TMSI and CSKN.
The MS is brought into the state U10 by using table 26.8.1.2/3.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The MS invokes call independent supplementary service on an existing FACCH channel. After receiving a CM SERVICE ACCEPT message, the MS invokes a self-location request by sending a REGISTER message containing the Facility IE LCS MO-LR.
The SS sends an RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives a FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate LCS MOLR Procedure (location estimation) on existing FACCH channel
2
MS -> SS
CM SERVICE REQUEST
The CM Service Type IE indicates "Supplementary service activation".
"mobile station classmark 2" includes settings for ES_IND.
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
Call Independent SS containing Facility IE with
LCS-MOLR request with MOLR-Type set to locationEstimate
5
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
6
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
7
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request Contains assistance data as defined in sub clause 70.1.3.
8
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response:
Option 1:
ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10)
Option 2:
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData
8a
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data.
If the MS requested additional assistance data in step 8 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
8b
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 8a, the MS acknowledges the received assistance data.
8c
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request.
If the MS requested additional assistance data in step 8 that is available in the SS, this message may include further assistance data.
8d
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response.
If the MS requested additional assistance data in step 8, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
9
SS -> MS
FACILITY
LCS MO-LR result message containing location estimate
10
MS -> SS
RELEASE COMPLETE
MS terminates the dialogue
11
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 4):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR APPLICATION INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 5: RRLP Positioning Capability Request
Step 6: RRLP Positioning Capability Response
Step 7 and 8c: RRLP Measure Position Request
Step 8 and 8d: RRLP Measure Position Response
Step 8a: RRLP Assistance Data
Step 8b: RRLP Assistance Data Ack.
RRLP Positioning Capability Request (Step 5):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 6):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 5).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Measure Position Request (Step 7):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
Component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
Gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 5.1.3 and 5.1.8.
referenceTime
SEQUENCE
See TS 51.010-7 sub clause 5.1.3
acquisAssist
SEQUENCE
See TS 51.010-7 sub clause 5.1.8
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4.
RRLP Measure Position Response (Step 8 (Option 1) or Step 8d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 8d)
Component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable except gpsAssDataMissing.
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 8 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements
This field may only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 8a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
Component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub-Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 8 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly.
Except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 8 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 8b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
Component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 8c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
Gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 8 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 8 (Option 2).
FACILITY (Step 9):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010)
Facility
Return Result = LCS-MOLR
LCS-MOLRRes -> locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values and/or ganssMeasureInfo values
RELEASE COMPLETE (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.5 MO-LR / Dedicated Mode for Mobiles Supporting MS-Based GNSS / Assistance Data Request
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.5.1 Conformance Requirement:
|
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes self-location request by sending a REGISTER message containing a LCS MO LR invoke
component with MO LR-TYPE set to ASSISTANCE DATA, LOCATION_METHOD TYPE set
ASSISTEDGPS, and GPS_ASSISTANCE_DATA TYPE set to the type of ASSISTANCE_DATA requested.
3. The MS sends RRLP ASSISTANCE DATA ACK. for each RRLP ASSISTANCE DATA component.
4. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 sub clause 7.6.6
3Gpp TS 24.30 sub clause 5
3GPP TS 24.80 sub clause 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.5.2 Test Purpose
|
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the FACILITY IE LCS-MOLR REQ on an already established speech call related main DCCH (FACCH). On receipt of a RRLP ASSISTANCE DATA from SS with the requested assistance data, MS shall send back RRLP ASSISTANCE ACK for each component to SS. When the MS receives a FACILITY message containing a FACILITY IE LCS-MOLR return result for the acknowledgment of completing assistance data delivery, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.5.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS has valid TMSI and CSKN.
The MS is brought into the state U10 by using table 26.8.1.2/3
Specific PICS statements
-
PIXIT statements
-
Test Procedure:
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
A MOLR procedure as call independent supplementary services is initiated from the MS on the existing FACCH channel.
After received CM SERVICE ACCEPT message, MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke for Assistance Data.
The SS sends a number of RRLP ASSISTANCE DATA components and MS sends acknowledgement of RRLP ASSISTANCE DATA ACK for each component.
SS sends DTAP LCS-MOLR Return Result for acknowledgement of completion of assistance data delivery procedure.
The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence:
Step
Direction
Message
Comments
1
MS
Initiate LCS MOLR Procedure (assistance data request) on existing FACCH channel
2
MS -> SS
CM SERVICE REQUEST
"Mobile identity" IE contains the TMSI.
Establishment cause indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR with MOLR-Type set to assistanceData.
5
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
6
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
7n
SS->MS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA
The number of instances of this message depends on the amount of assistance data requested in step 4
8n
MS -> SS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA ACK
Each instance of RRLP ASSISTANCE DATA message in step 7n is acknowledged
9
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT
10
MS->SS
RELEASE COMPLETE
Terminates the session
11
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
REGISTER (Step 4):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
MOLR-Type-> assistanceData
Location Method-> assistedGANSS / assistedGPSandGANSS (Sub-Tests 3, 4 and 10)
GPSAssistanceData-> any value is acceptable
ganssAssistanceData-> any value is acceptable
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 5: RRLP Positioning Capability Request
Step 6: RRLP Positioning Capability Response
Step 7n: RRLP Assistance Data
Step 8n: RRLP Assistance Data Ack.
RRLP Positioning Capability Request (Step 5):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 6):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 5).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 1 (msBased) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Assistance Data (Step 7n):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub-Tests 3 and 4.
The GPS assistance data requested by the MS in Step 4 that is available in the SS, shall be sent in one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1 or 0.
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly.
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
The GANSS assistance data requested by the MS in Step 4 that is available in the SS, SS shall send one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 8n):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
assistanceDataAck
FACILITY (Step 9):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->empty (note)
Note: For acknowledgement of assistance data delivery procedure, SS shall send LCS-MOLR Facility return result to MS, there is no parameter for this.
RELEASE COMPLETE (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.6 MO-LR / Dedicated Mode for Mobiles Supporting MS-Based GNSS / Location Estimate request
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.6.1 Conformance requirements:
|
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component.
3. On receiving the POSITIONING CAPABILITY REQUEST message the MS responds with a POSITIONING CAPABILITY RESPONSE message indicating the positioning methods supported by the MS.
4. On receiving an RRLP MEASURE POSITION REQUEST message, the MS tries to perform the requested location measurements, and possibly calculates it own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC.
5. 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.
6. After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 44.031
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.6.2 Test Purpose
|
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing an MO-LR Request of type “locationEstimate” on an already established speech call related SACCH. When the MS receives a FACILITY message containing a MO-LR return result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.6.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS has valid TMSI and CKSN.
The MS is brought into state U10 by using table 26.8.1.2/3.
Test Procedure:
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The MS invokes call independent supplementary service on an existing SACCH channel. After receiving a CM SERVICE ACCEPT message, the MS invokes a self location request by sending a REGISTER message containing an MO-LR request of type “locationEstimate”.
The SS sends an RR APPLICATION INFORMATION messages containing a RRLP Positioning Capability Request message.
The MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS orders positioning measurement by sending RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages followed by an RRLP Measure Position Request including further assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MO-LR procedure (location estimation) on existing SACCH channel
2
MS -> SS
CM SERVICE REQUEST
The CM Service Type IE indicates "Supplementary service activation".
"mobile station classmark 2" includes settings for ES_IND.
3
SS -> MS
CM SERVICE ACCEPT
4
MS -> SS
REGISTER
Call Independent SS containing Facility IE with LCS-MOLR request and MO-LR Type set to “locationEstimate”.
5
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
6
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
7
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
8
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
9
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
10
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
11
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response:
ganssLocationInfo (Option 1)
or
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData (Option 2)
12a
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data.
If the MS requested additional assistance data in step 12 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
12b
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 12a, the MS acknowledges the received assistance data.
12c
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request.
If the MS requested additional assistance data in step 12 that is available in the SS, this message may include further assistance data.
12d
MS-> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response.
If the MS requested additional assistance data in step 12, this message contains ganssLocationInfo.
13
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT message containing location estimate
14
MS -> SS
RELEASE COMPLETE
MS terminates the dialogue
15
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 4):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
MOLR-Type->locationEstimate
SS version indicator
Value 1 or above
RRLP Positioning Capability Request (Step 5):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 6):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request.
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 1 (msBased) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Steps 11 and 12c: RRLP Measure Position Request
Steps 12 and 12d: RRLP Measure Position Response
Steps 7, 9, 12a: RRLP Assistance Data
Steps 8, 10, 12b: RRLP Assistance Data Ack.
RRLP Assistance Data (Step 7):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Assistance Data Ack (Steps 8, 10, 12b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 12b)
Component
CHOICE
assistanceDataAck
RRLP Assistance Data (Step 9):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly.
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
Gps
measureResponseTime
Integer 0 to 7
5
Accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 12 (Option 1) or 12d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1 or 2 (Option 2, Step 12d)
Component
CHOICE
msrPositionRsp
(A valid response will contain ganssLocationInfo otherwise LocationError will be returned)
locationError
SEQUENCE
Any error value is acceptable except gpsAssDataMissing or ganssAssDataMissing.
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssLocationInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 12 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
Component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing or ganssAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing GPS assistance data elements.
This field may only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 12a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 to 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly.
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Measure Position Request (Step 12c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
Component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
ENUMERATED
Gps
measureResponseTime
Integer 0 to 7
5
Accuracy
Integer (0-127)
127
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 as requested by the MS in step 12 (Option 2).
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 12 (Option 2).
FACILITY (Step 13):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes -> locationEstimate
RELEASE COMPLETE (Step 14):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
70.14.7
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8 MO-LR / Location Error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.1 MO-LR / Location Error / Requested Method not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.1.1 Conformance requirement:
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS sends a RRLP MEASURE POSITION RESPONSE to network containing a Location Error component with an error indication if the measurement is not possible.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.1.2 Test Purpose:
|
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall send back RRLP MEASURE POSITION RESPONSE message with Location Error component if the MS does not support the requested method. On receipt of second RRLP MEASURE POSITION REQUEST from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.1.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure:
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
The SS then instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST with a method type not supported by the mobile. (Type not supported to be GPS for sub-tests 1, 2 and 9,, Galileo for sub-tests 3, 4 and 10). The MS sends RRLP MEASURE POSITION RESPONSE to SS containing a Location Error component (Request Method not Supported) as the requested method is not supported.
The SS then sends a RR APPLICATION INFORMATION message containing a RRLP Positioning Capability Request message, and the MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS repeats RRLP MEASURE POSITION REQUEST with correct message contents including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the TMSI.
The CM Service Type IE indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 2" including settings for ES IND and CM3 supported.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
8
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
9
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
10
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR request with MOLR-Type set to locationEstimate
11
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
(Request method not supported)
12
MS->SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(location_error)
13
SS -> MS
RR APPLICATION INFORMATION
RRLP POSITIONING CAPABILITY REQUEST
14
MS->SS
RR APPLICATION INFORMATION
RRLP POSITIONING CAPABILITY RESPONSE
15
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
16
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response:
ganssMeasureInfo and gps-MeasureInfo, (Sub-Tests 3, 4 and 10) (Option 1)
or
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData (Option 2)
16a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data.
If the MS requested additional assistance data in step 16 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
16b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 16a, the MS acknowledges the received assistance data.
16c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Measure Position Request.
If the MS requested additional assistance data in step 16 that is available in the SS, this message may include further assistance data.
16d
MS -> SS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Measure Position Response.
If the MS requested additional assistance data in step 16, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
17
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
18
MS -> SS
RELEASE COMPLETE
Terminates the session
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR_APPLICATION_INFORMATION:
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 11, Step 15 and 16c: RRLP Measure Position Request
Step 12, Step 16 and 16d: RRLP Measure Position Response
Step 16a: RRLP Assistance Data
Step 16b: RRLP Assistance Data Ack.
Step 13: RRLP Positioning Capability Request
Step 14: RRLP Positioning Capability Response
RRLP Measure Position Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
Sub-tests 1, 2 and 9: gps
Sub-tests 3, 4 and 10: galileo
measureResponseTime
Integer 0 to 7
7
useMultipleSets
ENUMERATED
oneSet
extended-reference
SEQUENCE
RRLP Measure Position Response (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRes
locationError
SEQUENCE
locErrorReason
ENUMERATED
methodNotSupported
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Positioning Capability Request (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityReq
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityRsp
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 13).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
methodType
CHOICE
msAssisted
RRLP Measure Position Request (Step 15):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 16 (Option 1) or Step 16d (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2 or 3 (Option 2, Step 16d)
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 16 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 16a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
This field may only be present for Sub-Tests 3, 4 and 10.
If the MS requested further GPS assistance data in Step 16 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly:
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further GANSS assistance data in Step 16 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 16b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 16c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
3
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clause 6.1.4 as requested by the MS in step 16 (Option 2).
extended-reference
SEQUENCE
Rel 5 and later
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 16 (Option 2).
FACILITY (Step 17):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values.
RELEASE COMPLETE (Step 18):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.2 MO-LR / Location Error / GNSS Assistance Data Missing
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.2.1 Conformance requirement:
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS sends a RRLP MEASURE POSITION RESPONSE to network containing a Location Error component with an error indication if the measurement is not possible.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.2.2 Test Purpose:
|
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall send back RRLP MEASURE POSITION RESPONSE message with Location Error component if GNSS assistance data is missing. On receipt of second RRLP MEASURE POSITION REQUEST (with GNSS assistance data included) from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.8.2.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure:
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
The A-GNSS assistance data stored in the MS is reset.
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
On receiving the RR APPLICATION INFORMATION message containing a RRLP Positioning Capability Request message, the MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS then instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST without GNSS assistance data (GPS or GANSS according to the receiver capabilities).
The MS requests additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing or ganssAssDataMissing for sub-test cases 3, 4 and 10 and set to ganssAssDataMissing for sub-test cases 1, 2 and 9. The SS provides the requested assistance data that is available in the SS in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data.
The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Reset all stored A-GNSS assistance data
2
MS
Initiate MOLR Procedure (location estimate)
3
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH".
4
SS -> MS
IMMEDIATE ASSIGNMENT
5
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the TMSI.
The CM Service Type IE indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
6
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 2" including settings for ES IND and CM3 supported.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7.
7
SS -> MS
AUTHENTICATION REQUEST
8
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
9
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
10
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR request with MOLR-Type set to locationEstimate
12
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
13
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
14
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
(without GNSS assistance data)
15
MS -> SS
RR APPLICATION INFORMATION
RRLP Measure Position Response:
locationError with ganssAssDataMissingor gpsAssDataMissing (Sub-Tests 3, 4 and 10)
16
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data.
The SS provides the requested data from step 15 that is available in the SS in zero, one or more RRLP Assistance Data delivery messages.
17
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 16, the MS acknowledges the received assistance data.
18
SS-> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request.
This message may include further assistance data.
19
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10))
20
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
21
MS -> SS
RELEASE COMPLETE
Terminates the session
22
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 11):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR_APPLICATION_INFORMATION:
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Step 14 and 18: RRLP Measure Position Request
Step 15 and 19: RRLP Measure Position Response
Step 16: RRLP Assistance Data
Step 17: RRLP Assistance Data Ack.
Step 12: RRLP Positioning Capability Request
Step 13: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 12).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
RRLP Measure Position Request (Step 14):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPostionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
RRLP Measure Position Response (Step 15):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing.
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 16):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data requested in step 15, if available from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data requested in step 15, if available from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 17):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 18):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 15
extended-reference
SEQUENCE
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 15.
RRLP Measure Position Response (Step 19):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionRsp
A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable.
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
FACILITY (Step 20):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values.
RELEASE COMPLETE (Step 21):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.9 MO-LR / Multiple RRLP Requests with Same Reference Number and Extended Reference Number
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.9.1 Conformance requirement:
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS ignores the later component if the old and new RRLP MEASURE POSITION REQUEST components have the same Reference Number.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.9.2 Test Purpose:
|
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall ignore the second RRLP MEASURE POSITION REQUEST if the second RRLP MEASURE POSITION REQUEST has the same REFERENCE NUMBER and the same Extended Reference IE as in the previous one. The MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the current measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.9.3 Method of Test
|
Initial Conditions
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
On receiving the RR APPLICATION INFORMATION message containing a RRLP Positioning Capability Request message, the MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS then instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER and the same EXTENDED REFERENCE IE as the first one (this delay shall be cancelled in the event of option 2). The MS shall ignore the second RRLP MEASURE POSITION REQUEST. The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
Option 2: The MS may request additional assistance data by immediately sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to ganssAssDataMissing, and gpsAssDataMissing for sub-test cases 3, 4 and 10. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by a second RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS sends the second RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements and the SS sends the third RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER and the same EXTENDED REFERENCE IE as the second one. The MS shall ignore the third RRLP MEASURE POSITION REQUEST. The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
The satellite signals should be made available after sending the second Measure Position request (in case of option 1) and third Measure Position request (in case of option 2)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the TMSI.
The CM Service Type IE indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 2" including settings for ES IND and CM3 supported.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
8
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
9
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
10
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
13
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
14
MS (Option 1)
or
MS ->SS (Option 2)
-
or
RR APPLICATION INFORMATION
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1). The SS continues to step 15.
If the MS sends RRLP Measure Position Response:
locationError (Option 2) with ganssAssDataMissing or gpsAssDataMissing (Sub-Tests 3, 4 and 10) within 8 seconds, then the SS continues to step 14a.
14a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data.
If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
14b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only :
RRLP assistanceDataAck.
If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data.
14c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Measure Position Request.
If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data.
14d
MS (Option 2)
Option 2 only :
MS is performing the measurement
15
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with same reference number and same extended reference IE as in step 13 (Option 1)
or
RRLP MEASURE POSITION REQUEST with same reference number and same extended reference IE as in step 14c (Option2)
Note: The satellite signals should be made available to MS after sending this message
16
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(ganssMeasureInfo and gps-measureInfo for Sub-Tests 3, 4 and 10)
17
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
18
MS -> SS
RELEASE COMPLETE
Terminates the session
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Steps 13, 14c and 15: RRLP Measure Position Request
Steps 14, 16: RRLP Measure Position Response
Step 14a: RRLP Assistance Data
Step 14b: RRLP Assistance Data Ack.
Step 11: RRLP Positioning Capability Request
Step 12: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityReq
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityRsp
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 11).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
methodType
CHOICE
msAssisted
RRLP Measure Position Request (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
referenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
acquisAssist
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 14 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 14a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data requested in step 14, if available data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 14b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 14c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 14 (Option 2).
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 14.
RRLP Measure Position Request (Step 15 (Option 1 or Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msBased
positionMethod
Enumerated
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
Enumerated
oneSet
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
RRLP Measure Position Response (Step 16):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
FACILITY (Step 17):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values.
RELEASE COMPLETE (Step 18):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.10 MO-LR / Multiple RRLP Requests with Different Reference Number
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.10.1 Conformance requirement:
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS aborts activity for the former RRLP MEASURE POSITION REQUEST component and starts to act according to the later RRLP MEASURE POSITION REQUEST component if the old and new RRLP MEASURE POSITION REQUEST components have different Reference Number.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.10.2 Test Purpose:
|
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall terminate the current location measurement if the second RRLP MEASURE POSITION REQUEST is received with a different REFERENCE NUMBER and the same EXTENDED REFERENCE IE as the first one. The MS shall perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST. The MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.10.3 Method of Test
|
Initial Conditions
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
On receiving the RR APPLICATION INFORMATION message containing a RRLP Positioning Capability Request message, the MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS then instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with a different REFERENCE NUMBER and the same EXTENDED REFERENCE IE as the first one (this delay shall be cancelled in the event of option 2). The MS shall terminate the current location measurement and perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST. The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
Option 2: The MS may request additional assistance data by immediately sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to ganssAssDataMissing, and gpsAssDataMissing for sub-test cases 3, 4 and 10. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by a second RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS sends the second RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements and the SS sends the third RRLP MEASURE POSITION REQUEST with a different REFERENCE NUMBER and the same EXTENDED REFERENCE IE as the second one. The MS shall terminate the current location measurement and perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST, including the possibility of repeating the request for more assistance data (Option 2b). The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
The satellite signals should be made available after sending the second Measure Position request (in case of option 1) and third Measure Position request (in case of option 2)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the TMSI.
The CM Service Type IE indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 2" including settings for ES IND and CM3 supported.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
8
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
9
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
10
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
13
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 1
14
MS (Option 1)
or
MS ->SS (Option 2)
-
or
RR APPLICATION INFORMATION
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1). The SS continues to step 15.
If the MS sends RRLP Measure Position Response:
locationError (Option 2) with ganssAssDataMissing or gpsAssDataMissing for Sub-Tests 3, 4 and 10 within 8 seconds, then the SS continues to step 14a.
14a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data.
If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
14b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data.
14c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Measure Position Request.
If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data.
14d
MS (Option 2)
Option 2 only :
MS is performing the measurement
15
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with different reference number and same extended reference IE as in step 13 (Option 1)
or
RRLP MEASURE POSITION REQUEST 3 with different reference number and same extended reference IE as in step 14c (Option2)
Note: The satellite signals should be made available to MS after sending this message
16
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
ganssMeasureInfo and gps-measureInfo for Sub-Tests 3, 4 and 10 (Option 1 or 2a).
Check reference number is 2
or
locationError with gpsAssDataMissing (Sub-Tests 3, 4 and 10) or ganssAssDataMissing and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData (Option 2b)
Check reference number is 2
16a
SS -> MS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Assistance Data.
If the MS requested additional assistance data in step 16 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
16b
MS -> SS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 16a, the MS acknowledges the received assistance data.
16c
SS-> MS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Measure Position Request.
If the MS requested additional assistance data in step 16 that is available in the SS, this message may include further assistance data.
16d
MS -> SS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Measure Position Response.
If the MS requested additional assistance data in step 16, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
17
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
18
MS -> SS
RELEASE COMPLETE
Terminates the session
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Steps 13, 14c, 15 and 16c: RRLP Measure Position Request
Steps 14, 16 and 16d: RRLP Measure Position Response
Step 14a and 16a: RRLP Assistance Data
Step 14b and 16b: RRLP Assistance Data Ack.
Step 11: RRLP Positioning Capability Request
Step 12: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityReq
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityRsp
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 11).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
methodType
CHOICE
msAssisted
RRLP Measure Position Request 1 (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
referenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
acquisAssist
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 14 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 14a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data requested in step 14, if available data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 14b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 14c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 14 (Option 2).
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 14.
RRLP Measure Position Request (Step 15 (Option 1 or Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
Enumerated
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
Enumerated
oneSet
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
RRLP Measure Position Response (Step 16 (Option 1 or 2a) or Step 16d (Option 2b)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 16 (Option 2b)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 16a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 16 (Option 2b) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further assistance data in Step 16 (Option 2b) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 16b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
2
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 16c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
2
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 16 (Option 2).
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4 as requested by the MS in step 16.
FACILITY (Step 17):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values.
RELEASE COMPLETE (Step 18):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.11 MO-LR / Multiple RRLP Requests with Different Extended Reference Number
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.11.1 Conformance requirements
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS aborts activity for the former RRLP MEASURE POSITION REQUEST component and starts to act according to the later RRLP MEASURE POSITION REQUEST component if the old and new RRLP MEASURE POSITION REQUEST components have different Extended Reference Number.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.11.2 Test Purpose:
|
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall terminate the current location measurement if the second RRLP MEASURE POSITION REQUEST is received with the same REFERENCE NUMBER as the first one and a different EXTENDED REFERENCE IE. The MS shall perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST. The MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.11.3 Method of Test
|
Initial Conditions
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:
Sub-Test Case Number
Supported GNSS
1
MS supporting A-GLONASS only
2
MS supporting A-Galileo only
3
MS supporting A-GPS and Modernized GPS only
4
MS supporting A-GPS and A-GLONASS only
5
Reserved
6
Reserved
7
Reserved
8
Reserved
9
MS supporting A-BDS only
10
MS supporting A-GPS and A-BDS only
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
On receiving the RR APPLICATION INFORMATION message containing a RRLP Positioning Capability Request message, the MS responds with an RR APPLICATION INFORMATION message containing an RRLP Positioning Capability Response message indicating the GNSS(s) supported by the MS.
The SS then instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER as the first one and a different EXTENDED REFERENCE IE (this delay shall be cancelled in the event of option 2). The MS shall terminate the current location measurement and perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST. The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
Option 2: The MS may request additional assistance data by immediately sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to ganssAssDataMissing or gpsAssDataMissing (sub-tests 3, 4 and 10). If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by a second RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS sends the second RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements and the SS sends the third RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER as the second one and a different EXTENDED REFERENCE IE. The MS shall terminate the current location measurement and perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST, including the possibility of repeating the request for more assistance data (Option 2b). The MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data after finishing the measurement.
The satellite signals should be made available after sending the second Measure Position request (in case of option 1) and third Measure Position request (in case of option 2)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "Other procedures which can be completed with an SDCCH".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the TMSI.
The CM Service Type IE indicates "Supplementary service activation"
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 2" including settings for ES IND and CM3 supported.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
SRES specifies correct value.
8
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
9
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
10
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Positioning Capability Request
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Positioning Capability Response
13
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
14
MS (Option 1)
or
MS ->SS (Option 2)
-
or
RR APPLICATION INFORMATION
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1). The SS continues to step 15.
If the MS sends RRLP Measure Position Response:
locationError (Option 2) with ganssAssDataMissing or gpsAssDataMissing for Sub-Tests 3, 4 and 10 within 8 seconds, then the SS continues to step 14a.
14a
SS -> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data.
If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
14b
MS -> SS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data.
14c
SS-> MS
RR APPLICATION INFORMATION
Option 2 only :
RRLP Measure Position Request.
If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data.
14d
MS (Option 2)
Option 2 only :
MS is performing the measurement
15
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with same reference number as in Step 13 and different extended reference IE (Option 1)
or
RRLP MEASURE POSITION REQUEST 3 with same reference number as in Step 14c and different extended reference IE (Option2)
Note: The satellite signals should be made available to MS after sending this message
16
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
ganssMeasureInfo and gps-measureInfo for Sub-Tests 3, 4 and 10 (Option 1 or 2a).
Check extended reference IE is the equal to the one contained in the request of step 15
or
locationError with ganssAssDataMissing or gpsAssDataMissing (Sub-Tests 3, 4 and 10) and additionalAssistanceData including gpsAssistanceData (Sub-Tests 3, 4 and 10) and/or ganssAssistanceData (Option 2b)
Check extended reference IE is the equal to the one contained in the request of step 15
16a
SS -> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 16 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
16b
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 16a, the MS acknowledges the received assistance data.
16c
SS-> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 16 that is available in the SS, this message may include further assistance data.
16d
MS -> SS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Measure Position Response.
If the MS requested additional assistance data in step 16, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
17
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
18
MS -> SS
RELEASE COMPLETE
Terminates the session
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
REGISTER (Step 10):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
REGISTER (xx11 1011)
Facility
Invoke = LCS-MOLR
LCS-MOLRArg
Molr-Type -> locationEstimate
SS version indicator
Value 1 or above
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
Steps 13, 14c, 15 and 16c: RRLP Measure Position Request
Steps 14, 16 and 16d: RRLP Measure Position Response
Step 14a and 16a: RRLP Assistance Data
Step 14b and 16b: RRLP Assistance Data Ack.
Step 11: RRLP Positioning Capability Request
Step 12: RRLP Positioning Capability Response
RRLP Positioning Capability Request (Step 11):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityReq
extended-reference
SEQUENCE
RRLP Positioning Capability Response (Step 12):
Information element
Type
Value/remark
ASN.1 encoded
ReferenceNumber
Integer 0 to 7
1
component
CHOICE
posCapabilityRsp
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 11).
posCapabilities
SEQUENCE
nonGANSSpositionMethods
BIT STRING
May only be included for Sub-Tests 3, 4 and 10.
gANSSPositionMethods
SEQUENCE
Included for each MS supported GANSS
ganssID
INTEGER
Sub-Test 1: value 3
Sub-Test 2: absent
Sub-Test 3: value 1
Sub-Test 4: value 3
Sub-Test 9: value 4
Sub-Test 10: value 4
gANSSPositioningMethodTypes
BIT STRING
Bit 0 (msAssisted) set to value 1
gANSSSignals
BIT STRING
Dependent on MS capabilities
methodType
CHOICE
msAssisted
RRLP Measure Position Request (Step 13):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
referenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
acquisAssist
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3.
RRLP Measure Position Response (Step 14 (Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request
RRLP Assistance Data (Step 14a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further assistance data in Step 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 14b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 14c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clause 6.1.4 as requested by the MS in step 14 (Option 2).
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262143
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clause 6.1.4 as requested by the MS in step 14.
RRLP Measure Position Request (Step 15 (Option 1 or Option 2)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
Enumerated
gps
measureResponseTime
Integer 0 to 7
5
accuracy
Integer (0-127)
127
useMultipleSets
Enumerated
oneSet
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262142
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
RRLP Measure Position Response (Step 16 (Option 1 or 2a) or Step 16d (Option 2b)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
gps-MeasureInfo
SEQUENCE
Any value of the parameters is acceptable.
locationError
SEQUENCE
Any error value is acceptable
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262142
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 16 (Option 2b)):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
msrPositionRsp
(A valid response will contain ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10); otherwise locationError will be returned)
locationError
SEQUENCE
locErrorReason
ENUMERATED
Sub-Tests 1, 2 and 9: ganssAssDataMissing
Sub-Tests 3, 4 and 10: ganssAssDataMissing or gpsAssDataMissing
additionalAssistanceData
SEQUENCE
gpsAssistanceData
OCTET STRING
Indicates missing assistance data elements. This field shall only be present for Sub-Tests 3, 4 and 10.
ganssAssistanceData
OCTET STRING
Indicates missing GANSS assistance data elements
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262142
RRLP Assistance Data (Step 16a):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further assistance data in Step 16 (Option 2b) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
moreAssDataToBeSent
ENUMERATED
1, except in the case of the final Assistance Data message when the following Measure Position Request contains no additional Assistance Data (in which case: 0)
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
If the MS requested further assistance data in Step 16 (Option 2b) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the assistance data from TS 51.010-7 sub clause 6.1.4. Each message shall contain a maximum of 242 octets.
RRLP Assistance Data Ack (Step 16b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Measure Position Request (Step 16c):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer, 0 to 7
1
component
CHOICE
msrPositionReq
methodType
CHOICE
msAssisted
positionMethod
ENUMERATED
gps
measureResponseTime
Integer 0 to 7
5
useMultipleSets
ENUMERATED
oneSet
gps-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 sub clause 6.1.4 as requested by the MS in step 16 (Option 2b).
extended-reference
SEQUENCE
smlc-code
Integer, 0 to 63
63
transaction-ID
Integer, 0 to 262143
262142
ganssPositionMethod
BIT STRING
Sub-Test 1: bit 5 set to value 1
Sub-Test 2: bit 1 set to value 1
Sub-Test 3: bits 0 and 3 set to
value 1
Sub-Test 4: bits 0 and 5 set to
value 1
Sub-Test 9: bit 6 set to value 1
Sub Test 10: bits 0 and 6 set to value 1
ganss-AssistData
SEQUENCE
May contain further assistance data from TS 51.010-7 section 6.1.4 as requested by the MS in step 16.
FACILITY (Step 17):
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction Identifier
Message Type
FACILITY (0011 1010 )
Facility
Return Result = LCS-MOLR
LCS-MOLRRes ->locationEstimate (Note)
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values.
RELEASE COMPLETE (Step 18):
Information element
Value/remark
Protocol Discriminator
Call Independent SS (1011)
Transaction Identifier
Message Type
RELEASE COMPLETE (xx10 1010)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.12 MO-LR / RR Management Commands
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.14.12.1 Conformance requirement
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS aborts the measurement procedure and starts on the RR MANAGEMENT procedure if a RR MANAGEMENT command is received during the measurement procedure. The MS sends RR MANAGEMENT RESPONSE message upon completion.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 44.018 sub clauses 3.3.1.1 and 9.1.11.
3GPP TS 24.008 sub clauses 4.5.1.5, 5.2.1, 9.2.9 and 10.5.1.6, 10.5.1.7.
3GPP TS 44.031.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.