70.2 EOTD Network Induced Location Request
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
The test cases in this sub clause focus on Network Induced Location requests. Although normally associated with Emergency Calls, it is possible for an MS to receive a NI-LR at any time during idle or dedicated mode by a PLMN operator LCS client.
70.2.1 LCS Network Induced Emergency Call on an SDCCH / idle, no IMSI for Mobiles supporting MS-Assisted EOTD
70.2.1.1 Conformance requirement
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel shall be a CM SERVICE REQUEST message specifying the correct IMEI and a non-available CKSN, with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received form the network, the MS shall send an EMERGENCY SETUP message.
5. On receiving the RRLP MEASURE POSITION REQUEST message the MS will perform position measurements and respond with an RRLP MEASURE POSITION RESPONSE message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
6. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.2.1, 4.5.1.5, 4.5.1.1, 5.2.1.1, and 5.2.1.6
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
70.2.1.2 Test Purpose
To verify when an emergency call is initiated by an MS which does not have a SIM fitted, the network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message and the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
70.2.1.3 Method of Test
Initial Conditions
System Simulator:
Serving cell: Default parameters.
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Specific PICS statements
–
PIXIT statements
–
Test Procedure
An Emergency Call is initiated with the MS, with no SIM inserted in the MS.
Directly after sending EMERGENCY SETUP the MS receives a RR APPLICATION INFORMATION message containing an RRLP Measure Position Request.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing a RRLP Measure Position Response.
The emergency call is then established as normal with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum duration of the test
3 minutes.
Expected Test Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate "emergency called number" is entered. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment. |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". The mobile identity IE specifies the IMEI of the MS. The cipher key sequence number IE indicates "no key is available". |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 . |
6 |
SS -> MS |
CM SERVICE ACCEPT |
|
7 |
MS -> SS |
EMERGENCY SETUP |
|
8 |
SS-> MS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Request) |
9 |
MS -> SS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error) |
10 |
SS -> MS |
CALL PROCEEDING |
|
11 |
SS -> MS |
ALERTING |
|
12 |
SS -> MS |
ASSIGNMENT COMMAND |
|
13 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
14 |
SS -> MS |
CONNECT |
|
15 |
MS -> SS |
CONNECT ACKNOWLEDGE |
The MS indicates that the TCH is through connected in both directions. |
16 |
SS -> MS |
DISCONNECT |
|
17 |
MS -> SS |
RELEASE |
|
18 |
SS -> MS |
RELEASE COMPLETE |
|
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 (SS->MS) RRLP (Measure Position Request) , (MS->SS) RRLP (Measure Position Response), (MS->SS) RRLP (Protocol Error), (SS->MS) RRLP (Assistance Data) , (MS->SS) RRLP (Assistance Data Ack.), |
RRLP Measure Position Request
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
(20,A0,1e) Followed by EOTD Measure Assist Data |
referenceNumber |
Integer,0 to 7 |
1 |
component |
msrPositionReq |
1 |
methodType |
msAssisted |
0 |
positionMethod |
Enumerated |
eotd |
MeasureResponseTime |
Integer,0 to 7 |
7 |
useMultipleSets |
Enumerated |
oneSet |
EOTDMeasure AssistData |
SEQUENCE |
Values of the data within the element is described in tables 70.2.1 – 1 and 70.2.1 – 2 |
Table 70.2.1-1: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name |
Value |
Comments |
BCCH Carrier |
Range 0-1023 |
ARFCN of Serving BCCH |
BSIC |
Range 0 to 65 |
BSIC of Serving BCCH |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Table 70.2.1-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name |
Value |
Comments |
Number of Neighbors |
2 |
|
E-OTD Neighbor Present |
2 |
|
BSIC |
Range 0 to 63 |
BSIC of neighbor BCCH |
Multiframe Offset |
Range 0-51 |
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3. |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Rough RTD |
Range 0-1250 |
Set to rough RTD value for the specific test configuration |
RRLP Measure Position Response
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
|
referenceNumber |
Integer,0 to 7 |
1 |
component |
msrPositionReq |
1 |
EITHER |
||
Eotd MeasureInfo |
SEQUENCE |
Any value for these parameters is acceptable. |
OR |
||
LocationInfoError |
SEQUENCE |
Any error value is acceptable |
70.2.2 Void
70.2.3 Network Induced Location Request Emergency Call on an SDCCH for MS-Assisted EOTD Mobiles
For Mobiles supporting speech, emergency call establishment will be initiated by the MS whether location updating has been successful or not and whether a SIM is inserted into the MS or not.
A Network Induced Location Request could occur at any point during emergency call setup (Ref 3GPP TS 03.71 sub clause 7.6.4.1). This could occur during an emergency setup before connection to a traffic channel.
70.2.3.1 Conformance requirements:
The following requirements apply for this test:
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel, the MS shall send a CM SERVICE REQUEST message specifying the correct CKSN and TMSI with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
5. On receiving the RRLP Measure Position Request message the MS will perform position measurements and respond with an RRLP Measure Position Response message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
6. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10, 9.1.11, 10.5.1.7.
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.1.3, 5.2.1, 4.5.1.1, 4.5.1.5, 5.2.1.1, 5.2.1.6, 9.2.9.
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
70.2.3.3 Test Purpose
To verify when an emergency call is initiated by the MS, the network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message and the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
Specific PICS statements
–
PIXIT statements
–
70.2.3.4 Method of Test
Initial Conditions:
System Simulator:
Serving cell: Default parameters
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
An Emergency Call is initiated with the MS. SIM card is included in the MS.
Directly after sending EMERGENCY SETUP the MS receives a RR APPLICATION INFORMATION message containing an RRLP Measure Position Request.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing a RRLP Measure Position Response.
The emergency call is then established as normal with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate "emergency call number" is entered. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment. |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 . |
6 |
SS -> MS |
CM SERVICE ACCEPT |
|
7 |
MS -> SS |
EMERGENCY SETUP |
|
8 |
SS-> MS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Request) |
9 |
MS -> SS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error) |
10 |
SS -> MS |
CALL PROCEEDING |
|
11 |
SS -> MS |
ALERTING |
|
12 |
SS -> MS |
ASSIGNMENT COMMAND |
|
13 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
14 |
SS -> MS |
CONNECT |
|
15 |
MS -> SS |
CONNECT ACKNOWLEDGE |
The MS indicates that the TCH is through connected in both directions. |
16 |
SS -> MS |
DISCONNECT |
|
17 |
MS -> SS |
RELEASE |
|
18 |
SS -> MS |
RELEASE COMPLETE |
|
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 (SS->MS) RRLP (Measure Position Request) , (MS->SS) RRLP (Measure Position Response), (MS->SS) RRLP (Protocol Error), (SS->MS) RRLP (Assistance Data) , (MS->SS) RRLP (Assistance Data Ack.), |
RRLP Measure Position Request
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
(20,A0,1e) Followed by EOTD Measure Assist Data |
referenceNumber |
Integer,0 to 7 |
1 |
component |
msrPositionReq |
1 |
methodType |
msAssisted |
0 |
positionMethod |
Enumerated |
eotd |
MeasureResponseTime |
Integer,0 to 7 |
7 |
useMultipleSets |
Enumerated |
oneSet |
EotdMeasureAssistData |
SEQUENCE |
Values of the data within the element as described in Tables 70.2.3 – 1 and 70.2.3 – 2 |
Table 70.2.3-2: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name |
Value |
Comments |
BCCH Carrier |
Range 0-1023 |
ARFCN of Serving BCCH |
BSIC |
Range 0 to 65 |
BSIC of Serving BCCH |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Table 70.2.3-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name |
Value |
Comments |
Number of Neighbors |
2 |
|
E-OTD Neighbor Present |
2 |
|
BSIC |
Range 0 to 63 |
BSIC of neighbor BCCH |
Multiframe Offset |
Range 0-51 |
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3. |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Rough RTD |
Range 0-1250 |
Set to rough RTD value for the specific test configuration |
RRLP Measure Position Response
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
|
referenceNumber |
Integer,0 to 7 |
1 |
component |
msrPositionReq |
1 |
EITHER |
||
Eotd MeasureInfo |
SEQUENCE |
Any value for these parameters is acceptable. |
OR |
||
LocationInfoError |
SEQUENCE |
Any error value is acceptable |
70.2.4 Emergency Call NI-LR while Voice is Through Connected for Mobiles supporting MS-Assisted EOTD
A Network Induced Location Request could occur at any point during emergency call setup (Ref 3GPP TS 03.71 sub clause 7.6.4.1). In this case the voice call is established before the MS receives the location request.
70.2.4.1 Conformance requirements:
The following requirements apply for this test:
1. With the MS in the "idle, updated" state, the user shall initiate an emergency call after the number 112 (GSM 900 and 1800 MSs), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 in Mexico) has been entered by the user. The MS shall end a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel, the MS shall send a CM SERVICE REQUEST message specifying the correct CKSN and TMSI with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
5. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call, the MS shall indicate that the TCH is through connected in both directions.
6. On receiving the RRLP Measure Position Request message the MS will perform position measurements and respond with an RRLP Measure Position Response message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10, 9.1.11, 10.5.1.7
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.1.3, 5.2.1, 4.5.1.5, 4.5.1.1, 5.2.1.1, 5.2.1.6, 9.2.9
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
70.2.4.2 Test Purpose
To verify when a network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message, after a traffic channel has been established during an emergency call, the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
Specific PICS statements
–
PIXIT statements
–
70.2.4.3 Method of Test
Initial Conditions
System Simulator:
Serving cell: Default parameters.
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
An Emergency Call is initiated by the MS. SIM card is present in the MS.
The emergency call is established with a late assignment.
After receiving the CONNECT ACKNOWLEDGE message from the MS, the SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request on the FACCH.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The call is then cleared by the SS.
Maximum duration of the test:
1 minute.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
The appropriate Emergency Called number is entered. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause is emergency call establishment. |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 . |
6 |
SS -> MS |
CM SERVICE ACCEPT |
|
7 |
MS -> SS |
EMERGENCY SETUP |
|
8 |
SS -> MS |
CALL PROCEEDING |
|
9 |
SS -> MS |
ALERTING |
|
10 |
SS -> MS |
ASSIGNMENT COMMAND |
|
11 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
12 |
SS -> MS |
CONNECT |
|
13 |
MS -> SS |
CONNECT ACKNOWLEDGE |
The MS indicates that the TCH is through connected in both directions. |
14 |
SS-> MS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Request) |
15 |
MS -> SS |
RR APPLICATION INFORMATION |
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error) |
16 |
SS -> MS |
DISCONNECT |
|
17 |
MS -> SS |
RELEASE |
|
18 |
SS -> MS |
RELEASE COMPLETE |
|
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 (SS->MS) RRLP (Measure Position Request) , (MS->SS) RRLP (Measure Position Response), (MS->SS) RRLP (Protocol Error), (SS->MS) RRLP (Assistance Data) , (MS->SS) RRLP (Assistance Data Ack.), |
RRLP Measure Position Request
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
(20,A0,1e) Followed by EOTD Measure Assist Data |
ReferenceNumber |
Integer,0 to 7 |
1 |
Component |
msrPositionReq |
1 |
MethodType |
msAssisted |
0 |
PositionMethod |
Enumerated |
eotd |
MeasureResponseTime |
Integer,0 to 7 |
7 |
UseMultipleSets |
Enumerated |
oneSet |
EOTD Measurement Assistance |
SEQUENCE |
Values of the data within the element as described in Tables 70.2.4 – 1 and 70.2.4 – 2 |
Table 70.2.4-3: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name |
Value |
Comments |
BCCH Carrier |
Range 0-1023 |
ARFCN of Serving BCCH |
BSIC |
Range 0 to 65 |
BSIC of Serving BCCH |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Table 70.2.4-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name |
Value |
Comments |
Number of Neighbors |
2 |
|
E-OTD Neighbor Present |
2 |
|
BSIC |
Range 0 to 63 |
BSIC of neighbor BCCH |
Multiframe Offset |
Range 0-51 |
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3. |
Time Slot Scheme |
Either 0 or 1, as applicable |
0=All time slots 156.25 bits long |
Rough RTD |
Range 0-1250 |
Set to rough RTD value for the specific test configuration |
RRLP Measure Position Response
Information element |
Type |
Value/remark |
ASN.1 encoded |
– |
|
referenceNumber |
Integer,0 to 7 |
1 |
component |
msrPositionReq |
1 |
EITHER |
||
Eotd MeasureInfo |
SEQUENCE |
Any value for these parameters is acceptable. |
OR |
||
LocationInfoError |
SEQUENCE |
Any error value is acceptable |