hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.6.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 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.15.6.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
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 CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages.
The SS then sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including further assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay to of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER 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 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. 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).
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" 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
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
13
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
14
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
15
SS -> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request 1
16
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 17.
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 16a.
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 (Option 2)
Option 2 only :
MS is performing the measurement
17
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with same reference number and same extended reference IE as in step 15 (Option 1)
or
RRLP MEASURE POSITION REQUEST with same reference number and same extended reference IE as in step 16c (Option2)
Note: The satellite signals should be made available to MS after sending this message
18
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(ganssMeasureInfo and gps-measureInfo for Sub-Tests 3, 4 and 10)
19
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 15, 16c, 17: RRLP Measure Position Request
Step 16, 18: RRLP Measure Position Response
Step 11, 13, 16a: RRLP Assistance Data
Step 12, 14, 16b: RRLP Assistance Data Ack
RRLP Assistance Data (Step 11):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Assistance Data Ack (Steps 12, 14, 16b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Assistance Data (Step 13):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ionosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ganssIonosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Request (Step 15):
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
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
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssReferenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Response (Step 16 (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: 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
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further 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
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 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 Measure Position Request (Step 16c):
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
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
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 16 (Option 2).
RRLP Measure Position Request (Step 17 (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
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 18):
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.7 MT-LR / Multiple RRLP Requests with Different Reference Number | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.7.1 Conformance requirement: | When after reception of a Measure Position Request component, but before responding with a Measure Position Response or Protocol Error Component, the MS receives a new RRLP message with the Measure Position Request component, the MS aborts activity for the former component, and starts to act according to the latter component, if the old and new RRLP Measure Position Request components have different Reference Numbers.
The SMLC may use the same Reference Number or different Reference Numbers for different RRLP components within the same pseudo-segmentation sequence.
Test References
3GPP TS 04.31 sub clause 2.5.5
3GPP TS 04.31 sub clause 3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.7.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. 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.15.7.3 Method of Test | Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
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 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 CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages.
The SS then sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including further 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 from 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 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 a different REFERENCE NUMBER from 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).
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 and Positioning Method Support.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
13
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
14
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
15
SS -> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request 1
16
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 17.
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 16a.
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 (Option 2)
Option 2 only :
MS is performing the measurement
17
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with different reference number and same extended reference IE as in step 15 (Option 1)
or
RRLP MEASURE POSITION REQUEST with different reference number and same extended reference IE as in step 16c (Option2)
Note: The satellite signals should be made available to MS after sending this message
18
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 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 reference number is 2
18a
SS -> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 18 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
18b
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 18a, the MS acknowledges the received assistance data.
18c
SS-> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 18 that is available in the SS, this message may include further assistance data.
18d
MS -> SS
RR APPLICATION INFORMATION
Option 2b only :
RRLP Measure Position Response.
If the MS requested additional assistance data in step 18, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
19
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 15, 16c, 17, 18c: RRLP Measure Position Request
Step 16, 18, 18d: RRLP Measure Position Response
Step 11, 13, 16a, 18a: RRLP Assistance Data
Step 12, 14, 16b, 18b: RRLP Assistance Data Ack
RRLP Assistance Data (Step 11):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Assistance Data Ack (Steps 12, 14, 16b and 18b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Assistance Data (Step 13):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ionosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ganssIonosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Request (Step 15):
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
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
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssReferenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Response (Step 16 (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: 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
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further 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
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 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 Measure Position Request (Step 16c):
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
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
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 16 (Option 2).
RRLP Measure Position Request (Step 17 (Option 1 or Option 2)):
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
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 18 (Option 1 or 2a) or Step 18d (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 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
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 18 (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: 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 18a):
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 18 (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 18 (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.
RRLP Measure Position Request (Step 18c):
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
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 18 (Option 2b).
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 18 (Option 2b). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.8 MT-LR / Multiple RRLP Requests with Different Extended Reference Number | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.8.1 Conformance requirement: | When after reception of a Measure Position Request component, but before responding with a Measure Position Response or Protocol Error Component, the MS receives a new RRLP message with the Measure Position Request component, the MS aborts activity for the former component, and starts to act according to the latter component, if the old and new RRLP Measure Position Request components have different Extended Reference Numbers.
The SMLC may use the same Extended Reference Number or different Extended Reference Numbers for different RRLP components within the same pseudo-segmentation sequence.
Test References
3GPP TS04.31 sub clause 2.5.5
3GPP TS04.31 sub clause 3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.8.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 EXTENDED REFERENCE NUMBER. 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.15.8.3 Method of Test | Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
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 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 CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages.
The SS then sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including further 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 EXTENDED REFERENCE IE and the same REFERENCE NUMBER 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 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 a different EXTENDED REFERENCE IE and the same REFERENCE NUMBER 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).
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 and Positioning Method Support.
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESP
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
13
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
14
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
15
SS -> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
16
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 17.
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 16a.
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 assistanceDataAck.
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 (Option 2)
Option 2 only :
MS is performing the measurement
17
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST with same reference number and different extended reference IE as in step 15 (Option 1)
or
RRLP MEASURE POSITION REQUEST with same reference number and different extended reference IE as in step 16c (Option2)
Note: The satellite signals should be made available to MS after sending this message
18
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 17
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 17
18a
SS -> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 18 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
18b
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 18a, the MS acknowledges the received assistance data.
18c
SS-> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 18 that is available in the SS, this message may include further assistance data.
18d
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Response.
If the MS requested additional assistance data in step 18, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
19
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 15, 16c, 17, 18c: RRLP Measure Position Request
Step 16, 18, 18d: RRLP Measure Position Response
Step 11, 13, 16a, 18a: RRLP Assistance Data
Step 12, 14, 16b, 18b: RRLP Assistance Data Ack
RRLP Assistance Data (Step 11):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Assistance Data Ack (Steps 12, 14, 16b and 18b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Assistance Data (Step 13):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ionosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ganssIonosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Request 1 (Step 15):
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
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.
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssReferenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Response (Step 16 (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 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 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 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 Measure Position Request (Step 16c):
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
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
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 16.
RRLP Measure Position Request (Step 17 (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
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 18 (Option 1 or 2a) or Step 18d (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 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
ganssMeasureInfo
SEQUENCE
Any value is acceptable
RRLP Measure Position Response (Step 18 (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 18a):
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 18 (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 18 (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.
RRLP Measure Position Request (Step 18c):
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
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 18 (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 sub clause 6.1.4 as requested by the MS in step 18 (Option 2b).
70.15.9 MT-LR / RR Management Commands |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.9.1 Conformance requirement | A target MS shall terminate any positioning procedure or the transfer of RRLP positioning assistance data without sending any response to the SMLC if any RR message is received from the BSC that starts some other RR management procedure, including a new positioning procedure. The new RR procedure shall then be executed by the MS.
Upon receiving the HO or other RR management command, the MS will stop the location procedure and start on handover or other RR management procedure, since this has higher priority than location. The MS will then send the HO complete or other RR management response message to BSC.
The SMLC may use the same Reference Number or different Reference Numbers for different RRLP components within the same pseudo-segmentation sequence.
Test References
3GPP TS 03.71 sub clause 7.11.5,
3GPP TS 03.71 sub clause 10.6
3GPP TS 04.31 sub clause 3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.9.2 Test Purpose | Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall terminate the current location measurement if an RR MANAGEMENT command is received during the measurement procedure. The MS shall send an RR MANAGEMENT RESPONSE message to SS when the RR MANAGEMENT procedure is complete. The MS shall perform the measurement according to the newly received RRLP MEASURE POSITION REQUEST and send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.15.9.3 Method of Test | Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
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 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 CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages.
The SS then sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including further assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds the SS sends an RR MANAGEMENT command. The MS shall terminate the current location measurement and perform the RR MANAGEMENT command. The MS sends an RR MANAGEMENT RESPONSE message to SS when the RR MANAGEMENT procedure is complete. The SS sends a new RRLP MEASURE POSITION REQUEST including assistance data and the MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data finishing the measurement according to the newly received RRLP MEASUREMENT POSITION REQUEST (possibly by requesting additional assistance data first).
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 ganssAssDataMissing or 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 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 a RR MANAGEMENT command. The MS shall terminate the current location measurement and perform the RR MANAGEMENT command. The MS sends a RR MANAGEMENT RESPONSE message to SS when the RR MANAGEMENT procedure is complete. The SS sends a new RRLP MEASURE POSITION REQUEST including assistance data and the MS either sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data finishing the measurement according to the newly received RRLP MEASUREMENT POSITION REQUEST or requests more assistance data and then sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data.
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).
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" 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
8
SS -> MS
CIPHERING MODE COMMAND
9
MS -> SS
CIPHERING MODE COMPLETE
10
SS
SS starts ciphering.
11
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
12
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
13
SS -> MS
RR APPLICATION INFORMATION
RRLP Assistance Data
14
MS -> SS
RR APPLICATION INFORMATION
RRLP Assistance Data Ack
15
SS -> MS
RR APPLICATION INFORMATION
RRLP Measure Position Request
16
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 17.
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 16a.
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 (Option 2)
Option 2 only:
MS is performing the measurement
17
SS -> MS
RR MANAGEMENT COMMAND
18
MS -> SS
RR MANAGEMENT COMPLETE
MS terminates the measurement procedure and act on the RR management command
19
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST (Option 1)
or
RRLP MEASURE POSITION REQUEST (Option 2)
Note: The satellite signals should be made available to MS after sending this message
20
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
ganssMeasureInfo and gps-measureInfo for Sub-Tests 3, 4 and 10 (Option 1 or 2a).
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)
20a
SS -> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data.
If the MS requested additional assistance data in step 20 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages.
20b
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Assistance Data Ack.
If the SS sent additional assistance data in step 20a, the MS acknowledges the received assistance data.
20c
SS-> MS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Request.
If the MS requested additional assistance data in step 20 that is available in the SS, this message may include further assistance data.
20d
MS -> SS
RR APPLICATION INFORMATION
Option 2b only:
RRLP Measure Position Response.
If the MS requested additional assistance data in step 20, this message contains ganssMeasureInfo and gps-MeasureInfo (Sub-Tests 3, 4 and 10).
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 15, 16c, 19, 20c: RRLP Measure Position Request
Step 16, 20, 20d: RRLP Measure Position Response
Step 11, 13, 16a, 20a: RRLP Assistance Data
Step 12, 14, 16b, 20b: RRLP Assistance Data Ack
RRLP Assistance Data (Step 11):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Assistance Data Ack (Steps 12, 14, 16b, 20b):
Information element
Type
Value/remark
ASN.1 encoded
referenceNumber
Integer,0 to 7
1
component
CHOICE
assistanceDataAck
RRLP Assistance Data (Step 13):
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
navigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ionosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
moreAssDataToBeSent
ENUMERATED
1
extended-reference
SEQUENCE
ganss-AssistData
SEQUENCE
Dependent on MS capabilities and defined in sub clause 70.1.3
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssNavigationModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
ganssIonosphericModel
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Request (Step 15):
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
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
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.
ganssID
Integer
See TS 51.010-7 sub clause 6.1.4
ganssReferenceTime
SEQUENCE
See TS 51.010-7 sub clause 6.1.4
RRLP Measure Position Response (Step 16 (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: 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
1
component
CHOICE
assistanceData
gps-AssistData
SEQUENCE
If the MS requested further 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 section 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 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 section 6.1.4. Each message shall contain a maximum of 242 octets.
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
msBased
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 section 6.1.4 as requested by the MS in step 16 (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 clause 6.1.4 as requested by the MS in step 16 (Option 2).
RR Management Command (Classmark Enquiry) (Step 17):
Information element
Value/remark
Encoded
(06 13)
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Classmark Enquiry Message Type
0001 0011
RRLP Measure Position Request (Step 19 (Option 1 or Option 2)):
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
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 20 (Option 1 or 2a) or Step 20d (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 20 (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: 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 20a):
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 20 (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 20 (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 Measure Position Request (Step 20c):
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
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 20 (Option 2b).
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 clause 6.1.4 as requested by the MS in step 20 (Option 2b). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16 A-GNSS Minimum Performance tests | This sub clause specifies the measurement procedures for the conformance test of the minimum performance requirements for GSM user equipment (MS) that supports Assisted Global Navigation Satellite Systems (A-GNSS). It excludes performance requirements for MSs where the only A-GNSS supported is A-GPS L1C/A which are specified in sub clause 70.11 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.1 Abbreviations | A-GNSS Assisted - Global Navigation Satellite Systems
A-GPS Assisted - Global Positioning System
BDS BeiDou Navigation Satellite System
C/A Coarse/Acquisition
ECI Earth-Centered-Inertial
ECEF Earth Centred, Earth Fixed
EGNOS European Geostationary Navigation Overlay Service
FEC Forward Error Correction
GAGAN GPS Aided Geo Augmented Navigation
GANSS Galileo and Additional Navigation Satellite Systems
GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)
GNSS Global Navigation Satellite System
GPS Global Positioning System
GSS GNSS System Simulator
HDOP Horizontal Dilution Of Precision
ICD Interface Control Document
LOS Line Of Sight
MSAS Multi-functional Satellite Augmentation System
QZSS Quasi-Zenith Satellite System
SBAS Space Based Augmentation System
SV Space Vehicle
SV ID Space Vehicle Identification
WAAS Wide Area Augmentation System
WLS Weighted Least Square
WGS-84 World Geodetic System 1984 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2 GNSS test conditions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.1 GNSS signals | The GNSS signal is defined at the A-GNSS antenna connector of the MS. For MS with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.2 GNSS frequency | The GNSS signals shall be transmitted with a frequency accuracy of 0.025 PPM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.3 GNSS static propagation conditions | The propagation for the static performance measurement is an Additive White Gaussian Noise (AWGN) environment. No fading and multi-paths exist for this propagation model. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.4 GNSS multi-path conditions | Doppler frequency difference between direct and reflected signal paths is applied to the carrier and code frequencies. The Carrier and Code Doppler frequencies of LOS and multi-path for GNSS signals are defined in table 70.16.2.1.
Table 70.16.2.1: Multi-path Conditions for GNSS Signals
Initial relative Delay
[GNSS chip]
Carrier Doppler frequency of tap [Hz]
Code Doppler frequency of tap [Hz]
Relative mean Power [dB]
0
Fd
Fd / N
0
X
Fd - 0.1
(Fd-0.1) /N
Y
NOTE: Discrete Doppler frequency is used for each tap.
Where the X and Y depends on the GNSS signal type and is shown in Table 70.16.2.2, and N is the ratio between the transmitted carrier frequency of the signals and the transmitted chip rate as shown in Table 70.16.2.3 (where k in Table 70.16.2.3 is the GLONASS frequency channel number).
Table 70.16.2.2
System
Signals
X [m]
Y [dB]
Galileo
E1
125
-4.5
E5a
15
-6
E5b
15
-6
GPS/Modernized GPS
L1 C/A
150
-6
L1C
125
-4.5
L2C
150
-6
L5
15
-6
GLONASS
G1
275
-12.5
G2
275
-12.5
BDS
B1I
75
-4.5
Table 70.16.2.3
System
Signals
N
Galileo
E1
1540
E5a
115
E5b
118
GPS/Modernized GPS
L1 C/A
1540
L1C
1540
L2C
1200
L5
115
GLONASS
G1
3135.03 + k 1.10
G2
2438.36 + k 0.86
BDS
B1I
763
The initial carrier phase difference between taps shall be randomly selected between 0 and 2radians. The initial value shall have uniform random distribution. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.5 Mobile stations supporting multiple GNSS signals | For mobile stations supporting multiple GNSS signals, different minimum performance requirements may be associated with different signals. The satellite simulator shall generate all signals supported by the MS. Signals not supported by the MS do not need to be simulated. The relative power levels of each signal type for each GNSS are defined in Table 70.16.2.4. The individual test scenarios define the reference signal power level for each satellite. The power level of each simulated satellite signal type shall be set to the reference signal power level defined in each test scenario plus the relative power level defined in Table 70.16.2.4.
Table 70.16.2.4: Relative signal power levels for each signal type for each GNSS
Galileo
GPS/Modernized GPS
GLONASS
QZSS
SBAS
BDS
Signal power levels relative to reference power levels
E1
0 dB
L1 C/A
0 dB
G1
0 dB
L1 C/A
0 dB
L1
0 dB
B1I
D1
0 dB
E6
+2 dB
L1C
+1.5 dB
G2
-6 dB
L1C
+1.5 dB
D2
+5 dB
E5
+2 dB
L2C
-1.5 dB
L2C
-1.5 dB
L5
+3.6 dB
L5
+3.6 dB
NOTE 1: For test cases which involve “Modernized GPS”, the satellite simulator shall also generate the GPS L1 C/A signal if the MS supports “GPS” in addition to “Modernized GPS”.
NOTE 2: The signal power levels in the Test Parameter Tables represent the total signal power of the satellite per channel not e.g. pilot and data channels separately.
NOTE 3: For test cases which involve "BDS", D1 represents MEO/IGSO satellites B1I signal type and D2 represents GEO satellites B1I signal type. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.2.6 GNSS multi System Time Offsets | If more than one GNSS is used in a test, the accuracy of the GNSS-GNSS Time Offsets used at the system simulator shall be better than 3 ns. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.3 GSM and other test conditions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.3.1 GSM frequency band and frequency range | The tests in this sub clause are performed on one of the mid range ARFCNs of the GSM operating frequency band of the MS. The ARFCNs to be used for mid range are defined in Table 3.3.
If the MS supports multiple frequency bands then the Sensitivity tests in clause 70.16.5 shall be repeated in each supported frequency band. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.3.2 Sensors | The minimum performances shall be met without the use of any data coming from sensors that can aid the positioning. A dedicated test message 'RESET MS POSITIONING STORED INFORMATION' has been defined in TS 44.014 for the purpose of disabling any such sensors. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.4 A-GNSS test conditions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.4.1 General | This sub clause defines the minimum performance requirements for both MS based and MS assisted A‑GNSS terminals. If a terminal supports both modes then it shall be tested in both modes. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.4.2 Measurement parameters | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.4.2.1 MS based A-GNSS measurement parameters | In case of MS-based A-GNSS, the measurement parameters are contained in the RRLP GANSS 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.16.4.2.2 MS assisted A-GNSS measurement parameters | In case of MS-assisted A-GNSS, the measurement parameters are contained in the RRLP GANSS MEASUREMENT INFORMATION IE, and in the RRLP GPS MEASUREMENT INFORMATION IE if GPS L1C/A is supported. The measurement parameters are the MS GANSS Code Phase measurements and the MS GPS Code Phase measurements (if supported). The MS GANSS Code Phase measurements and MS GPS Code Phase measurements are converted into a horizontal position estimate using the procedure detailed in clause 70.16.4.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.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.16.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 and GANSS Measurement Information, and ending when the MS starts sending the MEASURE POSITION RESPONSE containing the Location Information or the GPS and GANSS 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 GNSS 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.16.4.3 Converting MS-assisted measurement reports into position estimates | To convert the MS measurement reports in case of MS-assisted mode of A-GNSS 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 clauses. The details can be found in [ICD-GPS 200], [IS-GPS-705], [IS-GPS-800], [SBAS], [IS-QZSS], [GLONASS ‑ICD], [Galileo-ICD], [P. Axelrad, R.G. Brown], [S.K. Gupta] and [BDS-ICD]. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.4.3.1 MS measurement reports | In case of MS-assisted A-GANSS, the measurement parameters are contained in the RRLP GANSS MEASUREMENT INFORMATION ELEMENT (sub clause A.3.2.10 in 3GPP TS 44.031). In case the MS provides also measurements on the GPS L1 C/A signal, 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) "GANSS TOD" and/or "GPS TOW" if GPS L1 C/A signal measurements are also provided.
NOTE: It is not expected that an MS will ever report both a GANSS TOD and a GPS TOW. However if two time stamps are provided and they derive from different user times, be aware that no compensation is made for this difference and this could affect the location accuracy.
2) Measurement Parameters for each GANSS and GANSS Signal: 1 to <maxSat>:
a) "SV ID"; mapping according to Table A.10.14 in 3GPP TS 44.031;
b) "Code Phase";
c) "Integer Code Phase";
d) "Code Phase RMS Error";
3) Additional Measurement Parameters in case of GPS L1 C/A signal measurements are also provided: 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 or A.4.2.6.1 in 3GPP TS 44.031):
Used for initial approximate receiver coordinates.
2) "GANSS Navigation Model" (sub clause A.4.2.6.2 in 3GPP TS 44.031):
Contains the ephemeris and clock correction parameters as specified in the relevant ICD of each supported GANSS; used for calculating the satellite positions and clock corrections.
3) "GANSS Ionospheric Model" (sub clause A.4.2.6.1 in 3GPP TS 44.031):
Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [Galileo-ICD] for computation of the ionospheric delay.
4) "GANSS Additional Ionospheric Model" (sub clause A.4.2.6.1 in 3GPP TS 44.031):
Contains the ionospheric parameters which allow the single frequency user to utilize the ionospheric model as specified in [QZSS-ICD] and [BDS-ICD] for computation of the ionospheric delay.
5) "GANSS Time Model" (sub clause A.4.2.6.2 in 3GPP TS 44.031):
Contains the GNSS-GNSS Time Offset for each supported GANSS. Note, that "GANSS Time Model" IE contains only the sub-ms part of the offset. Any potential integer seconds offset may be obtained from "UTC Model" (sub clause A.4.2.4 in 3GPP TS 44.031), "GANSS UTC Model" (sub clause A.4.2.6.2 in 3GPP TS 44.031), or "GANSS Additional UTC Model" (sub clause A.4.2.6.2 in 3GPP TS 44.031).
6) "Navigation Model" (sub clause A.4.2.4 in 3GPP TS 44.031):
Contains the GPS ephemeris and clock correction parameters as specified in [IS-GPS-200]; used for calculating the GPS satellite positions and clock corrections in case of GPS L1 C/A signal measurements are the only GPS measurements provided in addition to GANSS measurements.
7) "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 [IS-GPS 200] for computation of the ionospheric delay. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.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 relative to the selected GNSS specific system time. 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 the "GANSS Code Phase Ambiguity", or modulo 1 ms (the length of the C/A code period) in case of GPS L1 C/A signal measurements. 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 at the time of measurement is calculated, and the integer number of milliseconds to be added to the MS code phase measurements is obtained.
Step 2: Correction of pseudo-ranges for the GNSS-GNSS time offsets
In case the MS reports measurements for more than a single GNSS, the pseudo-ranges are corrected for the time offsets between the GNSSs relative to the selected reference time using the GNSS-GNSS time offsets available at the system simulator:
,
where is the measured pseudo-range of satellite i of GNSSm. The system time of GNSSk is the reference time frame, andis the available GNSS-GNSS time offset, and c is the speed of light.
Step 3: Formation of weighting matrix
The MS reported "Code Phase RMS Error" and/or "Pseudorange RMS Error" values are used to calculate the weighting matrix for the WLS algorithm described in [P. Axelrad, R.G. Brown]. According to 3GPP TS 44.031, the encoding for these fields is a 6 bit value that consists of a 3 bit mantissa, Xi and a 3 bit exponent, Yi for each SVi of GNSSj:
The weighting Matrix W is defined as a diagonal matrix containing the estimated variances calculated from the "Code Phase RMS Error" and/or "Pseudorange RMS Error" values:
Step 4: WLS position solution
The WLS position solution is described in e.g., [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 the relevant ICD of the particular GNSS. The satellite locations are transformed into WGS-84 reference frame, if needed.
2) Computation of clock correction parameters using the parameters and algorithms as defined in the relevant ICD of the particular GNSS.
3) Computation of atmospheric delay corrections using the parameters and algorithms defined in the relevant ICD of the particular GNSS for the ionospheric delay, and using the Gupta model defined in [S.K. Gupta] p. 121 equation (2) for the tropospheric delay. For GNSSs which do not natively provide ionospheric correction models (e.g., GLONASS), the ionospheric delay is determined using the available ionospheric model adapted to the particular GNSS frequency.
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 the relevant ICD of the particular GNSS 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 rsGNSSm,i is the satellite position vector for SVi of GNSSm (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 relative to the selected GNSS system time. 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.16.5 Sensitivity | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.1 Sensitivity Coarse Time Assistance | 70.16.5.1.1a Sub-tests
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 in Table 70.16.5.1.1.
Table 70.16.5.1.1: Sub-Test Case Number Definition
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.1.1 Definition | Sensitivity with coarse time assistance is the minimum level of GNSS satellite signals required for the MS to make an A-GNSS 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.16.5.1.2 Conformance requirement | The first fix position estimates shall meet the accuracy and response time requirements in table 70.16.5.1.4 for the parameters specified in table 70.16.5.1.2.
Table 70.16.5.1.2: Test parameters for Sensitivity Coarse Time Assistance
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.5.1.3
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
2
Galileo
Reference high signal power level
dBm
-142
Reference low signal power level
dBm
-147
GPS(1)
Reference high signal power level
dBm
-142
Reference low signal power level
dBm
-147
GLONASS
Reference high signal power level
dBm
-142
Reference low signal power level
dBm
-147
BDS
Reference high signal power level
dBm
-136
Reference low signal power level
dBm
-145
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.5.1.3: Power level and satellite allocation
Satellite allocation for each constellation
GNSS-1(1)
GNSS-2
GNSS-3
Single constellation
High signal level
1
-
-
Low signal level
5
-
-
Dual constellation
High signal level
1
-
-
Low signal level
2
3
-
Triple constellation
High signal level
1
-
-
Low signal level
1
2
2
Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.
Table 70.16.5.1.4: Conformance requirement for Sensitivity Coarse Time Assistance
System
Success rate
2-D position error
Max response time
All
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, clause O.2.1.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.1.3 Test purpose | To verify the MS's first position estimate meets the Conformance requirement under GNSS satellite signal conditions that represent weak signal conditions and with only Coarse Time Assistance provided by the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.1.4 Method of test | Initial conditions
Test environment: normal; see clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GNSS test parameters as specified in table 70.16.5.1.5 for GNSS scenario #1. For GNSS-1, select the first satellite SV ID defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7 for the one satellite with the higher level.
3. Switch on the MS.
4. Establish a signalling connection according to the generic procedure in clause 10.1a on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 51.010-7 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 clause 6.2.1.2.5 of TS 51.010-7
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 clauses 6.2.2 and 6.2.6 of TS 51.010-7 for MS based testing; or clauses 6.2.4 and 6.2.6 of TS 51.010-7 for MS assisted testing with the value of GNSS TOW offset by a random value as specified in clause 6.2.6.2 of TS 51.010-7; 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.16.5.1.7 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.16.5.1.7 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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.5.1.7 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GNSS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in clause 70.16.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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.5.1.7 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. For GNSS-1, select the first satellite SV ID defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 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 GNSS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of clause 70.16.5.1.5 are met. Each time scenario #1 or #2 is used, the start time of the GNSS 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, for GNSS-1 select the next satellite SV ID from the one used previously, defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7, for the one satellite with the higher level.
7. Release the signalling connection.
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.16.5.1.5 Test Requirements | For the parameters specified in table 70.16.5.1.5 the MS shall meet the requirements and the success rate specified in table 70.16.5.1.7 with a confidence level of 95% according to annex A7.2.
Table 70.16.5.1.5: Test parameters for Sensitivity Coarse Time Assistance
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.5.1.6
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
1.8
Galileo
Reference high signal power level
dBm
-141
Reference low signal power level
dBm
-146
GPS(1)
Reference high signal power level
dBm
-141
Reference low signal power level
dBm
-146
GLONASS
Reference high signal power level
dBm
-141
Reference low signal power level
dBm
-146
BDS
Reference high signal power level
dBm
-135
Reference low signal power level
dBm
-144
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.5.1.6: Power level and satellite allocation
Satellite allocation for each constellation
GNSS-1(1)
GNSS-2
GNSS-3
Single constellation
High signal level
1
-
-
Low signal level
5
-
-
Dual constellation
High signal level
1
-
-
Low signal level
2
3
-
Triple constellation
High signal level
1
-
-
Low signal level
1
2
2
Note 1: For GPS capable receivers, GNSS-1, i.e. the system having the satellite with high signal level, shall be GPS.
Table 70.16.5.1.7: Test requirements for Sensitivity Coarse Time Assistance
System
Success rate
2-D position error
Max response time
All
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 clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in clause A5.5.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.2 Sensitivity Fine Time Assistance | 70.16.5.2.1a Sub-tests
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 in Table 70.16.5.2.1.
Table 70.16.5.2.1: Sub-Test Case Number Definition
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.2.1 Definition | Sensitivity with fine time assistance is the minimum level of GNSS satellite signals required for the MS to make an A-GNSS 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.16.5.2.2 Conformance requirement | The first fix position estimates shall meet the accuracy and response time requirements in table 70.16.5.2.4 for the parameters specified in table 70.16.5.2.2.
Table 70.16.5.2.2: Test parameters for Sensitivity Fine Time Assistance
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.5.2.3
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
2
GNSS fine time assistance error range
s
10
Galileo
Reference signal power level
dBm
-147
GPS(1)
Reference signal power level
dBm
-147
GLONASS
Reference signal power level
dBm
-147
BDS
Reference signal power level
dBm
-147
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.5.2.3: Satellite allocation
Satellite allocation for each constellation
GNSS-1
GNSS-2
GNSS-3
Single constellation
6
-
-
Dual constellation
3
3
-
Triple constellation
2
2
2
Table 70.16.5.2.4: Conformance requirement for Sensitivity Fine Time Assistance
System
Success rate
2-D position error
Max response time
All
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, clause O.2.1.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.2.3 Test purpose | To verify the MS's first position estimate meets the Conformance requirement under GNSS satellite signal conditions that represent weak signal conditions and with Fine Time Assistance provided by the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.5.2.4 Method of test | Initial conditions
Test environment: normal; see clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GNSS test parameters as specified in table 70.16.5.2.5 for GNSS scenario #1.
3. Switch on the MS.
4. Establish a signalling connection according to the generic procedure in clause 10.1a on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 51.010-7 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 clause 6.2.1.2.5 of TS 51.010-7
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 clauses 6.2.2 and 6.2.6 of TS 51.010-7 for MS based testing; or clauses 6.2.4 and 6.2.6 of TS 51.010-7 for MS assisted testing with the values of GNSS TOW and BN offset by random values as specified in clause 6.2.6.2 of TS 51.010-7; 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.16.5.2.7 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.16.5.2.7 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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.5.2.7 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GNSS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in clause 70.16.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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.5.2.7 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GNSS 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 GNSS TOW and BN offsets in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of clause 70.16.5.2.5 are met. Each time scenario #1 or #2 is used, the start time of the GNSS 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. Release the signalling connection.
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.16.5.2.5 Test Requirements | For the parameters specified in table 70.16.5.2.5 the MS shall meet the requirements and the success rate specified in table 70.16.5.2.7 with a confidence level of 95% according to annex A7.2.
Table 70.16.5.2.5: Test parameters for Sensitivity Fine Time Assistance
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.5.2.6
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
1.8
GNSS fine time assistance error range
s
9
Galileo
Reference signal power level
dBm
-146
GPS(1)
Reference signal power level
dBm
-146
GLONASS
Reference signal power level
dBm
-146
BDS
Reference signal power level
dBm
-146
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.5.2.6: Satellite allocation
Satellite allocation for each constellation
GNSS-1
GNSS-2
GNSS-3
Single constellation
6
-
-
Dual constellation
3
3
-
Triple constellation
2
2
2
Table 70.16.5.2.7: Test requirements for Sensitivity Fine Time Assistance
System
Success rate
2-D position error
Max response time
All
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 clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in clause A5.5.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6 Nominal Accuracy | 70.16.6.1a Sub-tests
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 in Table 70.16.6.1.
Table 70.16.6.1: Sub-Test Case Number Definition
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6.1 Definition | Nominal accuracy is the accuracy of the MS's A-GNSS position estimate under ideal GNSS signal conditions. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6.2 Conformance requirement | The first fix position estimates shall meet the accuracy and response time requirements in table 70.16.6.4 for the parameters specified in table 70.16.6.2.
Table 70.16.6.2: Test parameters for Nominal Accuracy
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.6.3
Total number of generated satellites
-
6 or 7(2)
HDOP Range
-
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
2
GPS(1)
Reference signal power level for all satellites
dBm
-128.5
Galileo
Reference signal power level for all satellites
dBm
-127
GLONASS
Reference signal power level for all satellites
dBm
-131
QZSS
Reference signal power level for all satellites
dBm
-128.5
SBAS
Reference signal power level for all satellites
dBm
-131
BDS
Reference signal power level for all satellites
dBm
-133
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
NOTE 2: 7 satellites apply only for SBAS case.
If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
Table 70.16.6.3: Satellite allocation
Satellite allocation for each constellation
GNSS 1(1)
GNSS 2(1)
GNSS 3(1)
SBAS
Single constellation
6
--
--
1
Dual constellation
3
3
--
1
Triple constellation
2
2
2
1
NOTE1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.
Table 70.16.6.4: Conformance requirement for Nominal Accuracy
System
Success rate
2-D position error
Max response time
All
95 %
15 m
20 s
The reference for this requirement is 3GPP TS 45.005, clause O.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6.3 Test purpose | To verify the MS's first position estimate meets the Conformance requirement under GNSS satellite signal conditions that represent ideal conditions. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6.4 Method of test | Initial conditions
Test environment: normal; see clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GNSS test parameters as specified in table 70.16.6.5 for GNSS scenario #3.
3. Switch on the MS.
4. Establish a signalling connection according to the generic procedure in clause 10.1a on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GNSS scenario #3 as specified in clause 6.2.1.2 of TS 51.010-7 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 clause 6.2.1.2.5 of TS 51.010-7
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 clauses 6.2.2 and 6.2.6 of TS 51.010-7 for MS based testing; or clauses 6.2.4 and 6.2.6 of TS 51.010-7 for MS assisted testing with the value of GNSS TOW offset by a random value as specified in clause 6.2.6.2 of TS 51.010-7; 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.16.6.7 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.16.6.7 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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.6.7 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GNSS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in clause 70.16.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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.6.7 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GNSS scenario #4 instead of #3 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 GNSS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of clause 70.16.6.5 are met. Each time scenario #3 or #4 is used, the start time of the GNSS 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. Release the signalling connection.
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
7.7m
20s |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.6.5 Test Requirements | For the parameters specified in table 70.16.6.5 the MS shall meet the requirements and the success rate specified in table 70.16.6.7 with a confidence level of 95% according to annex A7.2.
Table 70.16.6.5: Test parameters for Nominal Accuracy
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.6.3
Total number of generated satellites
-
6 or 7(2)
HDOP Range
-
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
1.8
GPS(1)
Reference signal power level for all satellites
dBm
-128.5
Galileo
Reference signal power level for all satellites
dBm
-127
GLONASS
Reference signal power level for all satellites
dBm
-131
QZSS
Reference signal power level for all satellites
dBm
-128.5
SBAS
Reference signal power level for all satellites
dBm
-131
BDS
Reference signal power level for all satellites
dBm
-133
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
NOTE 2: 7 satellites apply only for SBAS case.
If QZSS is supported, one of the GPS satellites will be replaced by a QZSS satellite with respective signal support.
If SBAS is supported, the SBAS satellite with the highest elevation will be added to the scenario.
Table 70.16.6.6: Satellite allocation
Satellite allocation for each constellation
GNSS 1(1)
GNSS 2(1)
GNSS 3(1)
SBAS
Single constellation
6
--
--
1
Dual constellation
3
3
--
1
Triple constellation
2
2
2
1
NOTE1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS
Table 70.16.6.7: Test requirements for Nominal Accuracy
System
Success rate
2-D position error
Max response time
All
95 %
16.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 clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in clause A5.5.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.7 Dynamic Range | 70.16.7.1a Sub-tests
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 in Table 70.16.7.1.
Table 70.16.7.1: Sub-Test Case Number Definition
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.7.1 Definition | Dynamic Range is the maximum difference in level of the GNSS signals from a number of satellites that allows the MS to make an A-GNSS position estimate with a specific accuracy and a specific response time. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.7.2 Conformance requirement | The first fix position estimates shall meet the accuracy and response time requirements in table 70.16.7.4 for the parameters specified in table 70.16.7.2.
Table 70.16.7.2: Test parameters for Dynamic Range
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.7.3
Total number of generated satellites
-
6
HDOP Range
-
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
2
Galileo
Reference high signal power level
dBm
-127,5
Reference low signal power level
dBm
-147
GPS(1)
Reference high signal power level
dBm
-129
Reference low signal power level
dBm
-147
GLONASS
Reference high signal power level
dBm
-131.5
Reference low signal power level
dBm
-147
BDS
Reference high signal power level
dBm
-133.5
Reference low signal power level
dBm
-145
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.7.3: Power level and satellite allocation
Satellite allocation for each constellation
GNSS 1(1)
GNSS 2(1)
GNSS 3(1)
Single constellation
High signal level
2
--
--
Low signal level
4
--
--
Dual constellation
High signal level
1
1
--
Low signal level
2
2
--
Triple constellation
High signal level
1
1
1
Low signal level
1
1
1
NOTE1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.
Table 70.16.7.4: Conformance requirement for Dynamic Range
System
Success rate
2-D position error
Max response time
All
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, clause O.2.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.7.3 Test purpose | To verify the MS's first position estimate meets the Conformance requirement under GNSS 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.16.7.4 Method of test | Initial conditions
Test environment: normal; see clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GNSS test parameters as specified in table 70.16.7.5 for GNSS scenario #1. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7 for the satellites with the higher levels.
3. Switch on the MS.
4. Establish a signalling connection according to the generic procedure in clause 10.1a on a channel in the Mid ARFCN range.
Specific PICS statements
-
PIXIT statements
-
Procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 51.010-7 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 clause 6.2.1.2.5 of TS 51.010-7
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 clauses 6.2.2 and 6.2.6 of TS 51.010-7 for MS based testing; or clauses 6.2.4 and 6.2.6 of TS 51.010-7 for MS assisted testing with the value of GNSS TOW offset by a random value as specified in clause 6.2.6.2 of TS 51.010-7; 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.16.7.7 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.16.7.7 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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.7.7 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GNSS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in clause 70.16.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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.7.7 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7 for the satellites with the higher levels. Use new random values for the MS location and altitude in step 1 and for the GNSS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of clause 70.16.7.5 are met. Each time scenario #1 or #2 is used, the start time of the GNSS 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, randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7, for the satellites with the higher levels.
7. Release the signalling connection.
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.16.7.5 Test Requirements | For the parameters specified in table 70.16.7.5 the MS shall meet the requirements and the success rate specified in table 70.16.7.7 with a confidence level of 95% according to annex A7.2.
Table 70.16.7.5: Test parameters for Dynamic Range
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.7.6
Total number of generated satellites
-
6
HDOP Range
-
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
1.8
Galileo
Reference high signal power level
dBm
-126,7
Reference low signal power level
dBm
-146
GPS(1)
Reference high signal power level
dBm
-128.2
Reference low signal power level
dBm
-146
GLONASS
Reference high signal power level
dBm
-130.7
Reference low signal power level
dBm
-146
BDS
Reference high signal power level
dBm
-132.7
Reference low signal power level
dBm
-144
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.7.6: Power level and satellite allocation
Satellite allocation for each constellation
GNSS 1(1)
GNSS 2(1)
GNSS 3(1)
Single constellation
High signal level
2
--
--
Low signal level
4
--
--
Dual constellation
High signal level
1
1
--
Low signal level
2
2
--
Triple constellation
High signal level
1
1
1
Low signal level
1
1
1
NOTE1: GNSS refers to global systems i.e., GPS, Galileo, GLONASS and BDS.
Table 70.16.7.7: Test requirements for Dynamic Range
System
Success rate
2-D position error
Max response time
All
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 clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in clause A5.5.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.8 Multi-Path scenario | 70.16.8.1a Sub-tests
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 in Table 70.16.8.1.
Table 70.16.8.1: Sub-Test Case Number Definition
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.8.1 Definition | Multi-path performance measures the accuracy and response time of the MS's A-GNSS position estimate in a specific GNSS signal multi-path environment. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.8.2 Conformance requirement | The first fix position estimates shall meet the accuracy and response time requirements in table 70.16.8.4 for the parameters specified in table 70.16.8.2.
Table 70.16.8.2: Test parameters for Multi-Path scenario
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.8.3
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
2
Galileo
Reference signal power level
dBm
-127
GPS(1)
Reference signal power level
dBm
-128.5
GLONASS
Reference signal power level
dBm
-131
BDS
Reference signal power level
dBm
-133
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.8.3: Channel model allocation
Channel model allocation for each constellation
GNSS-1
GNSS-2
GNSS-3
Single constellation
One-tap channel (see note)
2
--
--
Two-tap channel (see note)
4
--
--
Dual constellation
One-tap channel (see note)
1
1
--
Two-tap channel (see note)
2
2
--
Triple constellation
One-tap channel (see note)
1
1
1
Two-tap channel (see note)
1
1
1
NOTE: One-tap channel: no multi-path. Two-tap channel: multi-path defined in clause 70.16.2.4
Table 70.16.8.4: Conformance requirement for Multi-Path scenario
System
Success rate
2-D position error
Max response time
All
95 %
100 m
20 s
The reference for this requirement is 3GPP TS 45.005, clause O.2.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.8.3 Test purpose | To verify the MS's first position estimate meets the Conformance requirement under GNSS satellite signal conditions that represent simple multi-path conditions. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 70.16.8.4 Method of test | Initial conditions
Test environment: normal; see clause A1.2.2.
1. Connect SS and GSS to the MS antenna connector or antenna connectors.
2. Set the GNSS test parameters as specified in table 70.16.8.5 for GNSS scenario #1. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7 for the satellites with one-tap channels.
3. Switch on the MS.
4. Establish a signalling connection according to the generic procedure in clause 10.1a on a channel in the Mid ARFCN range.
Specific PICS statements:
-
PIXIT statements:
-
Procedure
1. Start GNSS scenario #1 as specified in clause 6.2.1.2 of TS 51.010-7 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 clause 6.2.1.2.5 of TS 51.010-7. 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 clauses 6.2.2 and 6.2.6 of TS 51.010-7 for MS based testing; or clauses 6.2.4 and 6.2.6 of TS 51.010-7 for MS assisted testing with the value of GNSS TOW offset by a random value as specified in clause 6.2.6.2 of TS 51.010-7; 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.16.8.8 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.16.8.8 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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.8.8 and record one Good Result or Bad Result as appropriate; or
For MS assisted testing convert the GNSS Measurement Information reported in the Measure Position Response message to a 2D position using the method described in clause 70.16.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 clause 70.16.4.2.3. Compare the 2D position error against the value in table 70.16.8.8 and record one Good Result or Bad Result as appropriate.
5. Repeat steps 1 to 4 using GNSS scenario #2 instead of #1 so that the reference location changes sufficiently such that the MS shall have to use the new assistance data. Randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7 for the satellites with the one-tap channels. 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 GNSS TOW offset in step 2.
6. Repeat steps 1 to 5 until the statistical requirements of clause 70.16.8.5 are met. Each time scenario #1 or #2 is used, the start time of the GNSS 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, randomly select from the satellite SV IDs defined in the relevant table of Satellites to be simulated in clause 6.2.1.2 in TS 51.010-7, for the satellites with the one-tap channels.
7. Release the signalling connection
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.16.8.5 Test Requirements | For the parameters specified in table 70.16.8.5 the MS shall meet the requirements and the success rate specified in table 70.16.8.8 with a confidence level of 95% according to annex A7.2.
Table 70.16.8.5: Test parameters for Multi-Path scenario
System
Parameters
Unit
Value
Number of generated satellites per system
-
See Table 70.16.8.6
Total number of generated satellites
-
6
HDOP range
1.4 to 2.1
Propagation conditions
-
AWGN
GNSS coarse time assistance error range
seconds
1.8
Galileo
Reference signal power level
dBm
-127
GPS(1)
Reference signal power level
dBm
-128.5
GLONASS
Reference signal power level
dBm
-131
BDS
Reference signal power level
dBm
-133
NOTE 1: ”GPS” here means GPS L1 C/A, Modernized GPS, or both, dependent on MS capabilities.
Table 70.16.8.6: Channel model allocation
Channel model allocation for each constellation
GNSS-1
GNSS-2
GNSS-3
Single constellation
One-tap channel(see note)
2
--
--
Two-tap channel(see note)
4
--
--
Dual constellation
One-tap channel(see note)
1
1
--
Two-tap channel(see note)
2
2
--
Triple constellation
One-tap channel(see note)
1
1
1
Two-tap channel(see note)
1
1
1
NOTE: One-tap channel: no multi-path. Two-tap channel: multi-path defined in clause 70.16.2.4 with Relative mean Power (Y) defined in Table 70.16.8.7.
Table 70.16.8.7: Relative mean Power (Y)for use in Table 70.16.2.1
System
Signals
Y [dB]
Galileo
E1
-4.7
E5a
-6.2
E5b
-6.2
GPS/Modernized GPS
L1 C/A
-6.2
L1C
-4.7
L2C
-6.2
L5
-6.2
GLONASS
G1
-12.7
G2
-12.7
BDS
B1I
-4.7
Table 70.16.8.8: Test requirements for Multi-Path scenario
System
Success rate
2-D position error
Max response time
All
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 clause A5.5.2 and the explanation of how the Conformance requirement has been relaxed by the Test Parameter Relaxation is given in clause A5.5.4.
80 Generic Access default conditions, message contents and macros |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1 Default test conditions | The following default test conditions shall apply if not stated otherwise within an individual test description. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.1 Unlicensed Radio Access | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.1.1 IEEE 802.11 | First access point.
Setting
Channel
7
SSID
GAN_1
SSID-Broadcast
On
Ciphering
Off
Mode
Infrastructure
Second access point.
Setting
Channel
3
SSID
GAN_2
SSID-Broadcast
On
Ciphering
Off
Mode
Infrastructure |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.1.2 Bluetooth | Setting
Profile
PAN |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2 Protocol Settings | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.1 Dynamic Host Configuration Protocol - DHCP | Setting
Server IP-Address
192.168.11.1
Port
67
Client (Transport) IP Range Pool
192.168.11.10 - 15
Address Mask
255.255.255.0
Default Gateway
192.168.11.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.2 Domain Name System – DNS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.2.1 Public DNS Server | Setting
Server IP-Address
192.168.11.16
Port
53
The following entries should be used:
FQDN
IP
Provisioning SEGW
psgw.gan.mnc001.mcc001.3gppnetwork.org
192.168.11.32
Default SEGW
dsgw.default.gan
192.168.11.33
Serving SEGW
ssgw.serving.gan
192.168.11.34 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.2.2 DNS associated with GANC | Setting
Server IP-Address
172.16.0.144
Port
53
The following entries should be used:
FQDN
IP
Provisioning GANC
gan.mnc001.mcc001.3gppnetwork.org
172.16.0.192
Default GANC
gan.default.gan
172.16.0.193
Serving GANC
gan.serving.gan
172.16.0.194 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.3 Secure Gateway (SEGW) | FQDN
IP
Provisioning SEGW
psgw.gan.mnc001.mcc001.3gppnetwork.org
192.168.11.32
Default SEGW
dsgw.default.gan
192.168.11.33
Serving SEGW
ssgw.serving.gan
192.168.11.34 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.4 Generic Access Network Controller (GANC) | FQDN
IP
Provisioning GANC
gan.mnc001.mcc001.3gppnetwork.org
172.16.0.192
Default GANC
gan.default.gan
172.16.0.193
Serving GANC
gan.serving.gan
172.16.0.194
The TCP port used for Discovery and Registration is port number 14001 (see 44.318: 12.2.1) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.1.2.5 Secure Internet Protocol - IPsec | All cryptographic suites must be supported on SS side.
The certificates specified in annex A9 shall be used for authentication of the SS by the MS.
Setting
Client (Local) IP Range Pool
172.16.0.202 -217 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.2 Default message contents | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3 Macros | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.1 Overview | The present document presents macros for Generic Access test cases. It is intended to be a working document forming part of the Generic Access Test Specifications. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.1.1 Definition | A macro is a name or sentence, possibly followed by an argument list, that is equated to a text to which it is to be expanded, possibly with the substitution of actual arguments.
Macros may be used to simplify the writing and reading of the test cases or to avoid the repetition of common sentences, message contents or message sequences. The macros defined in this subclause can be used throughout the test cases.
The definition of the macros is done in alphabetical order. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.1.2 Syntax | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.1.2.1 Message contents | Any macro referencing message contents shall use the following table:
Macro reference (arguments)
(P)SI
Information Element
Value/Remarks
The table must contain:
Macro reference: word or sentence that gives the name to the macro. It may include a list of arguments with actual values for some IE's.
(P)SI: the System Information and Packet System Information messages whose content is referenced. Several (P)SIs can be referenced in this column. The defined IE value(s) refers to the (P)SI(s) in the same row.
Information Element: IE which value is specified.
Value/Remarks: value and any other comment specific to the IE's. In particular, the mapping between an argument value and its coding shall be specified in this column (see note).
NOTE: If possible, only the meaning of the value will be shown and not the value itself; this avoids updating when the core specifications are modified. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.1.2.2 Message sequence | Any macro referencing message contents shall use the following table:
Step
Direction
Message
Comments
{ Macro reference }
Macro (arguments)
The table must contain:
Macro reference: word or sentence that assigns the name to the macro. It may include a list of arguments with actual values for some parameters used within the macro.
Step: Number of the message. Letters may be used for general values: the same rules as in 3GPP TS 11.10 apply.
Direction: it must be either:
- "MS SS": for an uplink message or a macro containing only uplink message(s);
- "SS MS": for a downlink message or a macro containing only downlink message(s);
- "SS MS": for a macro containing both uplink and downlink message(s);
- "MS": for an action performed on the mobile side; or
- "SS": for an action performed on the system simulator side.
Message: Message name or macro reference.
Comments: any other comment specific to the message. In particular, value of certain bits/fields of the corresponding message.
The symbol '' can be used to indicate that the previous and following message or sequence of messages (both previous and following must appear) is repeated an unknown number of times, probably referenced with a letter on the 'step' column. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.2 Default message contents | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.3 Macro message sequences | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.3.1 Location Update Procedure | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.3.1.1 GAN A/Gb Mode Location Update Procedure | Step
Direction
Message
Comments
{ GAN A/Gb Mode Location Update Procedure }
1
MS SS
GA-CSR REQUEST
2
SS MS
GA-CSR REQUEST ACCEPT
3
MS SS
GA-CSR UPLINK DIRECT TRANSFER
Containing L3 (MM) Location Update Request
4
SS MS
GA-CSR DOWNLINK DIRECT TRANSFER
Containing L3 (MM) Authentication Request
5
MS SS
GA-CSR UPLINK DIRECT TRANSFER
Containing L3 (MM) Authentication Response
6
SS MS
GA-CSR DOWNLINK DIRECT TRANSFER
Containing L3 (MM) Location Update Accept
A6
(Optional)
MS SS
GA-CSR UPLINK DIRECT TRANSFER
Containing L3 (MM) TMSI Reallocation Complete
This step is executed only when assigned mobile identity is of type TMSI
7
SS MS
GA-CSR RELEASE
NOTE:
Only in case the MS performed GPRS suspension procedure prior to the CS session, then the GPRS RESUMPTION IE shall be present with ACK field set to 1.
8
MS SS
GA-CSR RELEASE COMPLETE |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.3.3.1.2 GAN Iu Mode Location Update Procedure | Step
Direction
Message
Comments
{ GAN Iu Mode Location Update Procedure }
1
MS SS
GA-RRC REQUEST
2
SS MS
GA-RRC REQUEST ACCEPT
3
MS SS
GA-RRC UPLINK DIRECT TRANSFER
Containing L3 (MM) Location Update Request
4
SS MS
GA-RRC DOWNLINK DIRECT TRANSFER
Containing L3 (MM) Authentication Request
5
MS SS
GA-RRC UPLINK DIRECT TRANSFER
Containing L3 (MM) Authentication Response
6
SS MS
GA-RRC DOWNLINK DIRECT TRANSFER
Containing L3 (MM) Location Update Accept
A6
(Optional)
MS SS
GA-RRC UPLINK DIRECT TRANSFER
Containing L3 (MM) TMSI Reallocation Complete
This step is executed only when assigned mobile identity is of type TMSI
7
SS MS
GA-RRC RELEASE
8
MS SS
GA-RRC RELEASE COMPLETE |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 80.4 Test PDP contexts | PDP context 1: same as PDP context 1 in section 40.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81 GAN Discovery and Registration Procedures | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1 Discovery Procedure | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1 Discovery Procedure, Accepted | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.1 Discovery Procedure, MS holds the IP address of the provisioning SEGW and FQDN of provisioning GANC, provisioning GANC and default GANC belong to the same SEGW | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.1.1 Conformance requirement | The MS shall:
- If the MS holds an IP address of the Provisioning SEGW, the MS establishes the secure connection towards the Provisioning SEGW according to sub-clause 4.2
- Following successful establishment of secure connection to the Provisioning SEGW:
- If the MS holds a FQDN of the Provisioning GANC, the MS shall perform a DNS query "inside the secure connection" to retrieve the IP-address of the Provisioning GANC. The MS shall establish a TCP connection to the Provisioning GANC using this IP address and a TCP port defined for Discovery (see sub-clause 12.2.1). The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching).
When the MS receives GA-RC DISCOVERY ACCEPT message, it shall:
- stop the timer TU3901.
- set the timer value for TU3903 to the default value,
- store the information about Default GANC in persistent storage:
- The Default GANC information consists of the Default GANC, SEGW associated with the Default GANC and optionally a TCP port to be used with that Default GANC. If a specific TCP Port is not received in the message, the defined port for Registration is used (see sub-clause 12.2.1)
- release the TCP connection towards the Provisioning GANC
- the secure connection to the Provisioning SEGW can be reused as follows;
- If the MS is provisioned with an IP address of the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW IP address IE, the MS shall reuse the existing secure connection.
- If the MS is provisioned with a FQDN of the Provisioning GANC-SEGW or derived a FQDN for the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW FQDN IE, the MS shall reuse the existing secure connection.
- otherwise the MS shall release the existing secure connection towards the SEGW of the Provisioning GANC as defined in sub-clause 4.5
- initiate the registration procedure towards the Default GANC as defined in sub-clause 6.2.
Reference(s)
3GPP TS 44.318 sub-clause 5.3 and 5.5.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.1.2 Test purpose | To verify that the MS is able to initiate the Discovery Procedure with an IP address to the SEGW associated with the provisioning GANC and the FQDN to the GANC.
To verify that the MS keeps the secure connection when registering to the default GANC if the provisioning GANC and default GANC have the same SEGW. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.1.3 Method of test | Initial conditions
System Simulator:
- 1 GAN cell, default parameter
- Provisioning GANC and default GANC belonging to the same SEGW
- Public DNS without knowledge of SEGW FQDN associated with Provisioning GANC
Mobile Station:
- MS in state GA-RC DEREGISTERED
- The MS has the IP address for the SEGW associated with the provisioning GANC, but not the FQDN
- The MS has the FQDN for the provisioning GANC, but not the IP address
- The MS does not have any knowledge about the default GANC
- The MS does not have any knowledge about the serving GANC
Foreseen final state of the MS
The MS will stay in state GA-RC DEREGISTERED.
Test procedure
Make the MS join the AP so that the Discovery procedure is kicked off.
The SS is supposed to answer the Discovery Request message with a valid FQDN or IP address of Default GANC and IP address of the SEGW associated with Default GANC matching the IP address of SEGW associated with Provisioning GANC before timer TU3901 expires.
The MS shall attempt to register towards the Default GANC reusing the same security connection used during Discovery procedure.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is joining the AP
2
MS
Set up Ipsec tunnel to SEGW
3
DNS Standard Query for GANC to the DNS server associated with the GANC
4
Standard Query Response with IP address to GANC
5
MS
Establish TCP connection to provisioning GANC
6
GA-RC DISCOVERY REQUEST
To provisioning GANC
7
GA-RC DISCOVERY ACCEPT
Default GANC and SEGW provided.
Note:
Default GANC belongs to the same SEGW as the Provisioning GANC
The message is sent before expiry of TU3901.
8
MS
Establish TCP connection to default GANC using either IP address or FQDN
9
GA-RC REGISTER REQUEST
To default GANC |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.2 Discovery procedure, the MS holds the FQDN of the provisioning SEGW and IP address of the provisioning GANC, provisioning GANC and default GANC belong to different SEGWs | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 81.1.1.2.1 Conformance requirement | - If the MS holds a FQDN of the Provisioning SEGW, the MS performs a public DNS query to retrieve the IP-address of the Provisioning SEGW and establish the secure connection towards the Provisioning SEGW according to sub-clause 4.2. The MS shall not store the IP address retrieved from DNS for subsequent procedures (apart from DNS resolver caching).
- Following successful establishment of secure connection to the Provisioning SEGW
- If the MS holds an IP address of the Provisioning GANC, the MS shall establish a TCP connection to the Provisioning GANC using the well-known TCP port for Discovery as defined in sub-clause 12.2.1
When the MS receives GA-RC DISCOVERY ACCEPT message, it shall:
- stop the timer TU3901.
- set the timer value for TU3903 to the default value,
- store the information about Default GANC in persistent storage:
- The Default GANC information consists of the Default GANC, SEGW associated with the Default GANC and optionally a TCP port to be used with that Default GANC. If a specific TCP Port is not received in the message, the defined port for Registration is used (see sub-clause 12.2.1)
- release the TCP connection towards the Provisioning GANC
- the secure connection to the Provisioning SEGW can be reused as follows;
- If the MS is provisioned with an IP address of the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW IP address IE, the MS shall reuse the existing secure connection.
- If the MS is provisioned with a FQDN of the Provisioning GANC-SEGW or derived a FQDN for the Provisioning GANC-SEGW and it matches the received Default GANC-SEGW FQDN IE, the MS shall reuse the existing secure connection.
- otherwise the MS shall release the existing secure connection towards the SEGW of the Provisioning GANC as defined in sub-clause 4.5
- initiate the registration procedure towards the Default GANC as defined in sub-clause 6.2.
Reference(s)
3GPP TS 44.318 sub-clause 5.3 and 5.5.1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.