70.9 Assisted GPS Mobile Terminated Tests
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
70.9.1 MT-LR Location Notification
70.9.1.1 MT-LR Location Notification for Mobiles Supporting MS-Based GPS
70.9.1.1.1 Conformance requirements
1. The network invokes a location notification procedure by sending a REGISTER message containing a LCS-LocationNotification invoke component to the MS with notificationType set to notifyLocationAllowed. The MS shall notify the MS user of the location request.
2. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.1.1.2 Test Purpose
To verify that when the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to NotifyLocationAllowed, the MS displays information about the LCS client correctly and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
70.9.1.1.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valued TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
–
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message containing a Facility IE containing a DTAP LCS Location Notification Invoke message set to notifyLocationAllowed. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed. The MS then responds with a RELEASE COMPLETE message containing a LocationNotification return to terminate the dialogue.
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyLocationAllowed |
12 |
MS |
MS displays information about LCS client |
|
13 |
MS -> SS |
RELEASE COMPLETE |
|
14 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType -> notifyLocationAllowed, locationType -> current Location , lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification verificationResponse -> permissionGranted |
70.9.1.2 MT-LR Location Notification for Mobiles Supporting MS-Assisted GPS
70.9.1.2.1 Conformance requirements
1. The network invokes a location notification procedure by sending a REGISTER message containing a LCS-LocationNotification invoke component to the MS with notificationType set to notifyLocationAllowed. The MS shall notify the MS user of the location request.
2. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.1.2.2 Test Purpose
To verify that when the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to NotifyLocationAllowed, the MS displays information about the LCS client correctly and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
70.9.1.2.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valued TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
–
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message containing a Facility IE containing a DTAP LCS Location Notification Invoke message set to notifyLocationAllowed. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed. The MS then responds with a RELEASE COMPLETE message containing a LocationNotification return to terminate the dialogue.
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. In the position method support (5 bit field), Bit 3 is set to 1 (MS-Assisted GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE Location Notification Invoke message set to notifyLocationAllowed |
12 |
MS |
MS displays information about LCS client |
|
13 |
MS -> SS |
RELEASE COMPLETE |
|
14 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType -> notifyLocationAllowed, locationType -> current Location, lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification verificationResponse -> permissionGranted |
70.9.2 MT-LR Privacy Options/Verification – Location Allowed If No Response
70.9.2.1 MT-LR Privacy Options/Verification– Location Allowed If No Response for mobiles supporting MS-Based GPS
70.9.2.1.1 Conformance requirements
- On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationAllowedIfNoResponse. The MS: a) notifies the user of the request, b) indicates the default is location allowed if no response is received within a predetermined period, and c) providing the opportunity to accept or deny the request if allowed by subscription or if barred by subscription.
Option 1: The user accepts the location request. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2: The user denies the location request.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3: The user takes no action and the verification process times-out. The SS shall terminate the dialogue.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 / 3GPP TS 24.030 Rel-6 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.2.1.2 Test Purpose
To verify that the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationAllowedIfNoResponse, the MS displays information about the LCS client correctly and indicates that the default response is location allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
70.9.2.1.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
– MS LCS Notification timeout timer
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, if allowed by subscription or if barred by subscription respectively. The MS also indicates that location will be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The SS responds with RELEASE COMPLETE.
Maximum duration of the test
5 minutes.
Expected Sequence
The test sequence is repeated for k = 1 … 3.
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse |
12 |
SS |
SS starts timer T(LCSN) set to 90% of MS LCS Notification timeout timer |
|
13A (k=1) |
MS |
The MS displays the location request and information about LCS Client. The user accepts location request before timer T(LCSN) expires. |
|
14A (k=1) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted. |
13B (k=2) |
MS |
The MS displays the location request and information about LCS Client. The user rejects location request before timer T(LCSN) expires. |
|
14B (k=2) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied. |
13C (k=3) |
MS |
The MS displays the location request and information about LCS Client. The user does not reply and waits for T(LCSN) to expire. |
|
14C (k=3) |
SS->MS |
RELEASE COMPLETE |
SS terminates the dialogue after T(LCSN) expiry |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE (Step 4)
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER (Step 11)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType ->notifyAnd Verify- LocationAllowedIfNoResponse, locationType -> current Location , lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE (Option k=1 Step14A)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Option k=2 Step 14B)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Option k=3, Step 14C)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
70.9.2.2 MT-LR Privacy Options/Verification– Location Allowed If No Response for Mobiles Supporting MS-Assisted GPS
70.9.2.2.1 Conformance requirements
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationAllowedIfNoResponse. The MS: a) notifies the user of the request, b) indicates the default is location allowed if no response is received within a predetermined period, and c) providing the opportunity to accept or deny the request if allowed by subscription or if barred by subscription.
2.
Option 1: The user accepts the location request. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2: The user denies the location request.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3: The user takes no action and the verification process times-out.
The SS shall terminate the dialogue.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 / 3GPP TS 24.030 Rel-6 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.2.2.2 Test Purpose
To verify that the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationAllowedIfNoResponse, the MS displays information about the LCS client correctly and indicates that the default response is location allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
70.9.2.2.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
– MS LCS Notification timeout timer
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, if allowed by subscription or if barred by subscription . The MS also indicates that location will be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The SS responds with RELEASE COMPLETE.
Maximum duration of the test
5 minutes.
Expected Sequence
The test sequence is repeated for k = 1 … 3.
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. In the position method support (5 bit field), Bit 3 is set to 1 (MS-Assisted GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse |
12 |
SS |
SS starts timer T(LCSN) set to 90% of MS LCS Notification timeout timer |
|
13A (k=1) |
MS |
The MS displays the location request and information about LCS Client. The user accepts location request before timer T(LCSN) expires. |
|
14A (k=1) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted. |
13B (k=2) |
MS |
The MS displays the location request and information about LCS Client. The user rejects location request before timer T(LCSN) expires. |
|
14B (k=2) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied. |
13C (k=3) |
MS |
The MS displays the location request and information about LCS Client. The user does not reply and waits for T(LCSN) to expire. |
|
14C (k=3) |
SS->MS |
RELEASE COMPLETE |
SS terminates the dialogue after T(LCSN) expiry |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE (Step 4)
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER (Step 11)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType ->notifyAnd Verify- LocationAllowedIfNoResponse, locationType -> current Location, lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE (Option k=1 Step14A)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Option k=2 Step14B)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Option k=3, Step 14C):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
70.9.3 MT-LR Privacy Options/Verification – Location Not Allowed If No Response
70.9.3.1 MT-LR Privacy Options/Verification– Location Not Allowed If No Response for Mobiles Supporting MS-Based GPS
70.9.3.1.1 Conformance requirements
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationNotAllowedIfNoResponse, the MS: a) notifies the user of the request, b) indicates the default is location not allowed if no response is received within a predetermined period, and c) providing the opportunity to accept or deny the request if allowed by subscription or if barred by subscription.
2.
Option 1: The user accepts the location request. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2: The user denies the location request.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3: The user takes no action and the verification process times-out.
The SS shall terminate the dialogue.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 / 3GPP TS 24.030 Rel-6 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.3.1.2 Test Purpose
To verify that if the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationNotAllowedIfNoResponse, then the MS displays information about the LCS client correctly and indicates that the default response is location not allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
70.9.3.1.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
– MS LCS Notification timeout timer
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, if allowed by subscription or if barred by subscription respectively. The MS also indicates that location will be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The SS responds with RELEASE COMPLETE.
Maximum duration of the test
5 minutes.
Expected Sequence
The test sequence is repeated for k = 1 … 3.
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse |
12 |
SS |
SS starts timer T(LCSN) set to 90% of MS LCS Notification timeout timer |
|
13A (k=1) |
MS |
The MS displays the location request and information about LCS Client. The user accepts location request before timer T(LCSN) expires. |
|
14A (k=1) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted. |
13B (k=2) |
MS |
The MS displays the location request and information about LCS Client. The user rejects location request before timer T(LCSN) expires. |
|
14B (k=2) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied. |
13C (k=3) |
MS |
The MS displays the location request and information about LCS Client. The user does not reply and waits for T(LCSN) to expire. |
|
14C (k=3) |
SS->MS |
RELEASE COMPLETE |
SS terminates the dialogue after T(LCSN) expiry |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE (Step 4)
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER (Step 11)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType ->notifyAnd Verify- LocationNotAllowedIfNoResponse, locationType -> current Location, lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE (Option k=1 Step14A)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Option k=2 Step14B)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Option k=3, Step 14C)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
70.9.3.2 MT-LR Privacy Options/Verification– Location Not Allowed If No Response for mobiles supporting MS-Assisted GPS
70.9.3.2.1 Conformance requirements
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationNotAllowedIfNoResponse, the MS: a) notifies the user of the request, b) indicates the default is location not allowed if no response is received within a predetermined period, and c) providing the opportunity to accept or deny the request if allowed by subscription or if barred by subscription respectively.
2.
Option 1: The user accepts the location request. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2: The user denies the location request.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3: The user takes no action and the verification process times-out.
The SS shall terminate the dialogue.
References
3GPP TS 03.71 sub clause 7.6.1.
3GPP TS 04.30 / 3GPP TS 24.030 Rel-6 sub clause 4.1.1.
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, and 3.4.
70.9.3.2.2 Test Purpose
To verify that the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationNotAllowedIfNoResponse, the MS displays information about the LCS client correctly and indicates that the default response is location not allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
70.9.3.2.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
–
PIXIT statements
– MS LCS Notification timeout timer
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, if allowed by subscription or if barred by subscription respectively. The MS also indicates that location will not be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The SS responds with RELEASE COMPLETE.
Maximum duration of the test
5 minutes.
Expected Sequence
The test sequence is repeated for k = 1 … 3.
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. In the position method support (5 bit field), Bit 3 is set to 1 (MS-Assisted GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
REGISTER |
Call Independent SS containing Facility IE LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse |
12 |
SS |
SS starts timer T(LCSN) set to 90% of MS LCS Notification timeout timer |
|
13A (k=1) |
MS |
The MS displays the location request and information about LCS Client. The user accepts location request before timer T(LCSN) expires. |
|
14A (k=1) |
SS -> MS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionGranted. |
13B (k=2) |
MS |
The MS displays the location request and information about LCS Client. The user rejects location request before timer T(LCSN) expires. |
|
14B (k=2) |
MS -> SS |
RELEASE COMPLETE |
Containing a LocationNotification return result with verificationResponse set to permissionDenied. |
13C (k=3) |
MS |
The MS displays the location request and information about LCS Client. The user does not reply and waits for T(LCSN) to expire. |
|
14C (k=3) |
SS->MS |
RELEASE COMPLETE |
SS terminates the dialogue after T(LCSN) expiry |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
PAGING RESPONSE (Step 4)
Information element |
Value/remark |
Protocol Discriminator |
RR management |
Ciphering Key Sequence number |
|
– Key Sequence |
Key sequence number previously allocated to MS, or "111" if no key is available |
Mobile station Classmark 2 |
|
– ES IND |
Shall indicate early autonomous sending of CLASSMARK CHANGE |
Mobile Identity |
|
– odd/even |
Even |
– Type of identity |
TMSI |
– Identity digits |
TMSI previously allocated to MS |
REGISTER (Step 11)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
REGISTER (0011 1011) |
Facility |
Invoke = lcs-LocationNotification LocationNotificationArg notificationType ->notifyAnd Verify- LocationNotAllowedIfNoResponse, locationType -> current Location , lcsClientExternalID -> externalAddress lcsClientName ->dataCodingScheme nameString |
RELEASE COMPLETE (Option k=1 Step 14A)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionGranted |
RELEASE COMPLETE (Option k=2 Step 14B)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (xx10 1010) |
Facility |
Return result = lcs-LocationNotification LocationNotificationRes verificationResponse -> permissionDenied |
RELEASE COMPLETE (Option k=3, Step 14C)
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction identifier |
|
Message type |
RELEASE COMPLETE (0010 1010) |
70.9.4 MT-LR / RRLP Error Handling for MS-Based A-GPS
70.9.4.1 RRLP Protocol Error
70.9.4.1.1 Conformance requirement:
The MS sends an RRLP PROTOCOL ERROR message to the network if there is a problem that prevents the MS to receive a complete and understandable RRLP MEASURE POSITION REQUEST component.
Test References
3GPP TS04.31 sub clause 2.2, 2.5
70.9.4.1.2 Test Purpose
To verify that the MS sends the correct positioning capability via controled early classmark sending. The MS shall send a RRLP PROTOCOL ERROR message to SS with specific error code if RRLP MEASURE POSITION REQUEST is incomplete. On receipt of second RRLP MEASURE POSITION REQUEST from SS to start the measurement, MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
70.9.4.1.3 Method of Test
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages.
The SS then sends an RRLP MEASURE POSITION REQUEST message with missing information element.
The MS shall send RRLP PROTOCOL ERROR as it fails to decode RRLP MEASURE POSITION REQUEST. The SS repeats RRLP MEASURE POSITION REQUEST with correct message contents.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
15 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
16 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP PROTOCOL ERROR |
17 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 |
18 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo (Option 1) or locationError with gpsAssDataMissing and additionalAssistanceData (Option 2) |
18a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 18a, the MS acknowledges the received assistance data. |
18c |
SS-> MS |
RR APPLICATION INFORMATION |
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 |
RRLP Measure Position Response. If the MS requested additional assistance data in step 18, this message contains locationInfo. |
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, 17 and 18c: RRLP Measure Position Request Step 18 and 18d: RRLP Measure Position Response Step 11, 13, 18a: RRLP Assistance Data Step 12, 14, 18b: RRLP Assistance Data Ack Step 16: RRLP Protocol Error |
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 |
|
navigationModel |
SEQUENCE |
PRNs 4,6,9. See TS 51.010-7 sub clause 5.1.5 |
moreAssDataToBeSent |
ENUMERATED |
1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Assistance Data Ack (Steps 12, 14, 18b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 3 (Option 2, Step 18b) |
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 |
|
navigationModel |
SEQUENCE |
PRNs 10,13,22. See TS 51.010-7 sub clause 5.1.5 |
ionosphericModel |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.6 |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 0. Rel 5 and later: 1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
accuracy* |
Integer (0-127) |
127 |
useMultipleSets* |
ENUMERATED |
oneSet |
Note*: Final octet of data shall be disgarded. E.g if encoded data is [0x20, 0x01, 0xFE, 0xD8] this shall be transmitted as [0x20, 0x01, 0xFE]. |
RRLP Protocol Error (Step 16):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
0 or 1 |
component |
CHOICE |
protocolError |
errorCause |
ENUMERATED |
missingIEorComponentElement, messageTooShort or Incorrect Data |
RRLP Measure Position Request 2 (Step 17):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 18 (Option 1) or 18d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 or 3 (Option 2, Step 18d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain LocationInfo otherwise LocationError will be returned) |
locationInfo |
SEQUENCE |
Any value is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
RRLP Measure Position Response (Step 18 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 |
3 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
If the MS requested further assistance data in Step 18 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
RRLP Measure Position Request (Step 18c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
3 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 18 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
70.9.4.2 RRLP Location Error – Requested Method Not Supported
70.9.4.2.1 Conformance requirement:
The MS sends an RRLP MEASURE POSITION RESPONSE message to the network containing a Location Error component with an error indication if the measurement is not possible.
Test References
3GPP TS04.31 sub clause 2.2, A.3.2.6
70.9.4.2.2 Test Purpose
To verify that the MS sends the correct positioning capability via controled early classmark sending. The MS shall send a RRLP MEASURE POSITION RESPONSE message with Location Error component if the MS does not support the requested method. On receipt of second RRLP MEASURE POSITION REQUEST from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
70.9.4.2.3 Method of Test
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability.
The SS sends an RRLP MEASURE POSITION REQUEST message with a method type not supported by the mobile (type not supported to be E-OTD).
The MS sends RRLP MEASURE POSITION RESPONSE to SS containing a Location Error component (Requested Method not Supported) as the requested method is not supported.
The MS receives RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages followed by a new RRLP MEASURE POSITION REQUEST with correct message contents including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 1 |
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
15 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
16 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
17 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 |
18 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 2: locationInfo (Option 1) or locationError with gpsAssDataMissing and additionalAssistanceData (Option 2) |
18a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 18a, the MS acknowledges the received assistance data. |
18c |
SS-> MS |
RR APPLICATION INFORMATION |
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 |
RRLP Measure Position Response. If the MS requested additional assistance data in step 18, this message contains locationInfo. |
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 11, 17 and 18c: RRLP Measure Position Request Step 12, 18 and 18d: RRLP Measure Position Response Step 13, 15, 18a: RRLP Assistance Data Step 14, 16, 18b: RRLP Assistance Data Ack |
RRLP Measure Position Request 1 (Step 11):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
eotd |
measureResponseTime |
Integer 0 to 7 |
7 |
useMultipleSets |
ENUMERATED |
oneSet |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response 1 (Step 12):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRes |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
methodNotSupported |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
RRLP Assistance Data (Step 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
|
navigationModel |
SEQUENCE |
PRNs 4,6,9. See TS 51.010-7 sub clause 5.1.5 |
moreAssDataToBeSent |
ENUMERATED |
1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Assistance Data Ack (Steps 14, 16, 18b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 or 3 (Option 2, Step 18b) |
component |
CHOICE |
assistanceDataAck |
RRLP Assistance Data (Step 15):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
|
navigationModel |
SEQUENCE |
PRNs 10,13,22. See TS 51.010-7 sub clause 5.1.5 |
ionosphericModel |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.6 |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 0. Rel 5 and later: 1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Request 2 (Step 17):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 18 (Option 1) or 18d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 or 3 (Option 2, Step 18d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain LocationInfo otherwise LocationError will be returned) |
locationInfo |
SEQUENCE |
Any value is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
RRLP Measure Position Response (Step 18 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 |
3 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
If the MS requested further assistance data in Step 18 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
RRLP Measure Position Request (Step 18c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
3 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 18 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
70.9.4.3 RRLP Location Error – GPS Assistance Data Missing
70.9.4.3.1 Conformance requirement
The MS sends an RRLP MEASURE POSITION RESPONSE message to the network containing a Location Error component with an error indication if the measurement is not possible.
Test References
3GPP TS04.31 sub clause 2.2, A.3.2.6
70.9.4.3.2 Test Purpose
To verify that the MS sends the correct positioning capability via controled early classmark sending. The MS shall send a RRLP MEASURE POSITION RESPONSE message with Location Error component if some GPS assistance data are missing. On receipt of second RRLP MEASURE POSITION REQUEST (with all necessary GPS assistance data to obtain a location estimate included) from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
70.9.4.3.3 Method of Test
Initial Conditions
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
The A-GPS assistance data stored in the MS is reset.
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS receives an RRLP MEASURE POSITION REQUEST message with Reference Time GPS assistance data.
The MS requests additional assistance data by sending an RRLP MEASURE POSITION RESPONSE message to SS containing a Location Error component with IE LocErrorReason set to gpsLocCalAssDataMissing or gpsAssDataMissing.
The SS provides the requested assistance data that is available in the SS in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data.
The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Reset all stored A-GPS assistance data |
|
2 |
SS->MS |
PAGING REQUEST TYPE I |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates “answer to paging”. |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS->SS |
PAGING RESPONSE |
Message is contained in SABM. “mobile station classmark 2” includes settings for ES_IND. |
6 |
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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
9 |
SS -> MS |
CIPHERING MODE COMMAND |
|
10 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
11 |
SS |
SS starts ciphering. |
|
12 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
13 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 1 |
14 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. The SS provides the requested data from step 13 that is available in the SS in zero, one or more RRLP Assistance Data delivery messages. |
15 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 14, the MS acknowledges the received assistance data. |
16 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2. This message may include further assistance data. |
17 |
MS-> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 2. (LocationInfo) |
18 |
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 12 and 16: RRLP Measure Position Request Step 13 and 17: RRLP Measure Position Response Step 14: RRLP Assistance Data Step 15: RRLP Assistance Data Ack |
RRLP Measure Position Request 1 (Step 12):
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 |
Assistance Data Reference Time |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response 1 (Step 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsLocCalAssDataMissing or gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
RRLP Assistance Data (Step 14):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data requested in step 13, if available from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
RRLP Assistance Data Ack (Step 15):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request 2 (Step 16):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 13 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response 2 (Step 17):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionRsp A valid response will contain LocationInfo 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 |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
70.9.4.4 Multiple RRLP Requests with same Reference Number
70.9.4.4.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 ignores the latter component if the old and new RRLP Measure Position Request components have the same Reference Number.
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 TS04.31 sub clause 2.5.5
3GPP TS04.31 sub clause 3.2
70.9.4.4.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.
70.9.4.4.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
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability.
After sending 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 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 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” 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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
15 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
16 |
MS (Option 1) |
– 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: |
16a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
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 |
RRLP Measure Position Request 2. 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) |
MS is performing the measurement (Option 2) |
|
17 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 with same reference number as in Request 1 (Option 1) Note: The satellite signals should be made available to MS after sending this message |
18 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo |
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 |
|
navigationModel |
SEQUENCE |
PRNs 4,6,9. See TS 51.010-7 sub clause 5.1.5 |
moreAssDataToBeSent |
ENUMERATED |
1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
|
navigationModel |
SEQUENCE |
PRNs 10,13,22. See TS 51.010-7 sub clause 5.1.5 |
ionosphericModel |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.6 |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 0. Rel 5 and later: 1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
RRLP Measure Position Request 2 (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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 16 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Request 2 (Option 1) or Request 3 (Option 2) (Step 17):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 LocationInfo) |
locationInfo |
SEQUENCE |
Any value is acceptable. |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
70.9.4.5 Multiple RRLP Requests with different Reference Number
70.9.4.5.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 TS04.31 sub clause 2.5.5
3GPP TS04.31 sub clause 3.2
70.9.4.5.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.
70.9.4.5.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
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability.
After sending 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 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 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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
15 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
16 |
MS (Option 1) |
– 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: |
16a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
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 |
RRLP Measure Position Request 2. 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) |
MS is performing the measurement (Option 2) |
|
17 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 with different reference number as in Request 1 (Option 1) Note: The satellite signals should be made available to MS after sending this message |
18 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo (Option 1 or 2a) or locationError with gpsAssDataMissing (Option 2b) Check reference number is 2 |
18a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 18a, the MS acknowledges the received assistance data. |
18c |
SS-> MS |
RR APPLICATION INFORMATION |
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 |
RRLP Measure Position Response. If the MS requested additional assistance data in step 18 this message contains locationInfo. |
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 |
|
navigationModel |
SEQUENCE |
PRNs 4,6,9. See TS 51.010-7 sub clause 5.1.5 |
moreAssDataToBeSent |
ENUMERATED |
1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
|
navigationModel |
SEQUENCE |
PRNs 10,13,22. See TS 51.010-7 sub clause 5.1.5 |
ionosphericModel |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.6 |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 0. Rel 5 and later: 1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
RRLP Measure Position Request 2 (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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 16 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Request 2 (Option 1) or Request 3 (Option 2) (Step 17):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 LocationInfo otherwise LocationError will be returned) |
locationInfo |
SEQUENCE |
Any value is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
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 |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 18 (Option 2b). |
extended-reference |
SEQUENCE |
Rel 5 and later |
70.9.4.6 RR Management Commands
70.9.4.6.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 TS04.31 sub clause 3.2
70.9.4.6.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.
70.9.4.6.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
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. The MS performs control early classmark sending to provide LCS positioning method capability.
After sending 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 to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by 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” 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. In the position method support (5 bit field), Bit 2 is set to 1 (MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
|
10 |
SS |
SS starts ciphering. |
|
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
15 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 1 |
16 |
MS (Option 1) |
– 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: |
16a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
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 |
RRLP Measure Position Request 2. 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) |
MS is performing the measurement (Option 2) |
|
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 2 (Option 1) or RRLP Measure Position Request 3 (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: locationInfo (Option 1 or 2a) or locationError with gpsAssDataMissing (Option 2b) |
20a |
SS -> MS |
RR APPLICATION INFORMATION |
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 |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 20a, the MS acknowledges the received assistance data. |
20c |
SS-> MS |
RR APPLICATION INFORMATION |
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 |
RRLP Measure Position Response. If the MS requested additional assistance data in step 20 this message contains locationInfo. |
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 |
|
navigationModel |
SEQUENCE |
PRNs 4,6,9. See TS 51.010-7 sub clause 5.1.5 |
moreAssDataToBeSent |
ENUMERATED |
1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
|
navigationModel |
SEQUENCE |
PRNs 10,13,22. See TS 51.010-7 sub clause 5.1.5 |
ionosphericModel |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.6 |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 0. Rel 5 and later: 1 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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) |
RRLP Measure Position Request 2 (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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 16 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 2 (Option 1) or Request 3 (Option 2) (Step 19):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
refLocation |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.4 |
extended-reference |
SEQUENCE |
Rel 5 and later |
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 LocationInfo otherwise LocationError will be returned) |
locationInfo |
SEQUENCE |
Any value is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
Rel5 and later The value returned by the MS shall equal the value received from the SS in the earlier Measure Position Request |
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 |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
extended-reference |
SEQUENCE |
Rel5 and later 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 clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets. |
moreAssDataToBeSent |
ENUMERATED |
R98, R99, Rel 4: 1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. Rel 5 and later: 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 |
Rel 5 and later |
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 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 20 (Option 2b). |
extended-reference |
SEQUENCE |
Rel 5 and later |