70.8 Assisted GPS Mobile Originated Tests
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
70.8.1 Basic Self Location
70.8.1.1 Conformance requirements
1) The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2) The MS invokes self-location request by sending REGISTER message containing Facility IE LCS MO-LR with MOLR-TYPE set to locationEstimate.
3) The MS needs to interact with the network for each separate location request.
4) On receiving an RRLP MEASURE POSITION REQUEST message the MS tries to perform the requested location measurements. It sends the results in an RRLP MEASURE POSITION RESPONSE message.
5) The network returns an LCS result to the MS carrying location estimate requested by the MS in FACILITY message.
6) The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 03.71, sub clause 7.6.6.
3GPP TS 04.30, sub clause 5.1.1.
3GPP TS 04.80 / 3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
70.8.1.2 Test Purpose
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the Facility IE LCS MO-LR. When the MS receives a FACILITY message containing a Facility IE MO-LR LCS result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
70.8.1.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CSKN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
The MS invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When MS receives FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate LCS MOLR Procedure (location estimation) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
establishment cause "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
The CM service type IE indicates "Supplementary service activation". "mobile station classmark 2" includes settings for ES_IND. |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning. The 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 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request with MOLR-Type set to locationEstimate |
12 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
13 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1) or locationError with gpsAssDataMissing (Option 2) |
13a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 13 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
13b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 13a, the MS acknowledges the received assistance data. |
13c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 13 that is available in the SS, this message may include further assistance data. |
13d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 13, this message contains gps-MeasureInfo. |
14 |
SS -> MS |
FACILITY |
LCS MO-LR result message containing location estimate |
15 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
16 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 11):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR APPLICATION INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 12 and 13c: RRLP Measure Position Request Step 13 and 13d: RRLP Measure Position Response Step 13a: RRLP Assistance Data Step 13b: RRLP Assistance Data Ack. |
RRLP Measure Position Request (Step 12):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 13 (Option 1) or Step 13d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 13d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 13 (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 13a):
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 13 (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 Assistance Data Ack (Step 13b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 13c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 13 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 14):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.2 Basic Self Location in Dedicated Mode
70.8.2.1 Conformance requirements
The MS sends a DTAP LCS MO-LR invoke to the VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component with MO_LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
References
3GPP TS 03.71, sub clause 7.6.6.
3GPP TS 04.30, sub clause 5.1.1.
3GPP TS 04.80 / 3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
70.8.2.2 Test Purpose
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the Facility IE LCS MO-LR on an already established speech call related main DCCH (FACCH). When the MS receives a FACILITY message containing a Facility IE MO-LR LCS result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
70.8.2.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS has valid TMSI and CSKN.
The MS is brought into the state U10 by using table 26.8.1.2/3.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
The MS invokes call independent supplementary service on an existing FACCH channel. After receiving a CM SERVICE ACCEPT message, the MS invokes a self-location request by sending a REGISTER message containing the Facility IE LCS MO-LR.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives a FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate LCS MOLR Procedure (location estimation) on existing FACCH channel |
|
2 |
MS -> SS |
CM SERVICE REQUEST |
The CM Service Type IE indicates "Supplementary service activation". "mobile station classmark 2" includes settings for ES_IND. |
3 |
SS -> MS |
CM SERVICE ACCEPT |
|
4 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request with MOLR-Type set to locationEstimate |
5 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
6 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1) or locationError with gpsAssDataMissing (Option 2) |
6a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 6 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
6b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 6a, the MS acknowledges the received assistance data. |
6c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 6 that is available in the SS, this message may include further assistance data. |
6d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 6, this message contains gps-MeasureInfo. |
7 |
SS -> MS |
FACILITY |
LCS MO-LR result message containing location estimate |
8 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
9 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 4):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR APPLICATION INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 5 and 6c: RRLP Measure Position Request Step 6 and 6d: RRLP Measure Position Response Step 6a: RRLP Assistance Data Step 6b: RRLP Assistance Data Ack. |
RRLP Measure Position Request (Step 5):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 6 (Option 1) or Step 6d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 6d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 6 (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 6a):
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 6 (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 Assistance Data Ack (Step 6b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 6c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 6 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 7):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 8):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.3 Transfer to 3rd Party
70.8.3.1 Conformance requirements
The MS sends a DTAP LCS MO-LR invoke to the VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time). If the MS is requesting that its location be sent to another LCS client, the message shall include the identity of the LCS client and may include the address of the GMLC through which the LCS client should be accessed.
The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component with MO_LR TYPE set to LocationEstimate, LCS QoS value, LCS-ClientExternalID and MLC_Number if it is available.
References
3GPP TS 03.71, sub clause 7.6.6.
3GPP TS 04.30, sub clause 5.1.1.
3GPP TS 04.80 / 3GPP TS 24.080, sub clauses 2.4, 2.5, 3.4 and 4.
70.8.3.2 Test Purpose
To verify that the MS invokes a transfer of its own location to a 3rd party LCS Client by sending the network a REGISTER message containing the Facility IE LCS MO-LR with LCSClientExternalID present. The network sends location information of the MS to another LCS Client, and then it clears the transaction by sending a RELEASE COMPLETE message.
70.8.3.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
The MS invokes call independent supplementary service for an LCS MO-LR. After receiving a CM SERVICE ACCEPT message, the MS invokes a transfer to 3rd party location request by sending a REGISTER message containing the Facility IE LCS MO-LR with LCSClientExternalID present.
The SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS sends location information of the MS to another LCS Client, and then it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate LCS MOLR Procedure (location estimation) with transfer to 3rd party |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates, "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" includes settings for ES_IND. |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning. The 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 |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request with MOLR-Type set to locationEstimate with LCSClientExternalID present |
11 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
12 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1) or locationError with gpsAssDataMissing (Option 2) |
12a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 12 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
12b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 12a, the MS acknowledges the received assistance data. |
12c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 12 that is available in the SS, this message may include further assistance data. |
12d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 12, this message contains gps-MeasureInfo. |
13 |
SS |
SS may return the location estimate result to the LCS Client as identified by the LCSClientExternalID provided in the REGISTER message |
|
14 |
SS -> MS |
FACILITY |
LCS MO-LR Return Result message as confirmation that the position estimate was transferred to the requested LCS client. |
15 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
16 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate lcsClientExternalID -> externalAddress |
SS version indicator |
Value 1 or higher |
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 and 12c: RRLP Measure Position Request Step 12 and 12d: RRLP Measure Position Response Step 12a: RRLP Assistance Data Step 12b: RRLP Assistance Data Ack. |
RRLP Measure Position Request (Step 11):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 12 (Option 1) or Step 12d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 12d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 12 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
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 12a):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
If the MS requested further assistance data in Step 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 12b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 12c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 12 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 14):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4 MO-LR Positioning Measurement
70.8.4.1 MO-LR Positioning Measurement / Protocol Error
70.8.4.1.1 Conformance requirement:
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS sends a RRLP PROTOCOL ERROR message to network if there is a problem that prevents the MS to receive a complete and understandable RRLP MEASURE POSITION REQUEST component.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS04.31 sub clause 2.2, 2.5
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 & 4
70.8.4.1.2 Test Purpose
Verifies that a MS sends a correct positioning capability via control 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.8.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:
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST 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 including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimate) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR request with MOLR-Type set to locationEstimate |
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 (with missing final octet) |
12 |
MS->SS |
RR APPLICATION INFORMATION |
RRLP PROTOCOL ERROR |
13 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1) or locationError with gpsAssDataMissing (Option 2) |
14a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
14b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data. |
14c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data. |
14d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 14, this message contains gps-MeasureInfo. |
15 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
16 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 11, 13 and 14c: RRLP Measure Position Request Step 14 and 14d: RRLP Measure Position Response Step 14a: RRLP Assistance Data Step 14b: RRLP Assistance Data Ack Step 12: RRLP Protocol Error |
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 |
ENUMERATED |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
Note: Final octet of ASN.1 stream is not included in the APDU Data information element of the RR Application Information L3 message. |
RRLP Protocol Error (Step 12):
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 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 14 (Option 1) or Step 14d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 or 3 (Option 2, Step 14d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 14 (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 14a):
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 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 14b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
3 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 14c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
3 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 14 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 16):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4.2 MO-LR Positioning Measurement / Location Error
70.8.4.2.1 Location Error: Requested Method not Supported
70.8.4.2.1.1 Conformance requirement:
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS sends a RRLP MEASURE POSITION RESPONSE to network containing a Location Error component with an error indication if the measurement is not possible.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS04.31 sub clause 2.2
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 and 4
70.8.4.2.1.2 Test Purpose:
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall send back RRLP MEASURE POSITION RESPONSE message with Location Error component if the MS does not support the requested method. On receipt of second RRLP MEASURE POSITION REQUEST from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
70.8.4.2.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:
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke. The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST with a method type not supported by the mobile. (Type not supported to be EOTD).
The MS sends RRLP MEASURE POSITION RESPONSE to SS containing a Location Error component (Request Method not Supported) as the requested method is not supported. The SS repeats RRLP MEASURE POSITION REQUEST with correct message contents including assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimate) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR request with MOLR-Type set to locationEstimate |
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 (Request method not supported) |
12 |
MS->SS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION RESPONSE 1 ( location error) |
13 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2 |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 2: gps-MeasureInfo (Option 1) or locationError with gpsAssDataMissing (Option 2) |
14a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
14b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data. |
14c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data. |
14d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 14, this message contains gps-MeasureInfo. |
15 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
16 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION:
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 11, 13 and 14c: RRLP Measure Position Request Step 12, 14 and 14d: RRLP Measure Position Response Step 14a: RRLP Assistance Data Step 14b: 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 Measure Position Request 2 (Step 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response 2 (Step 14 (Option 1) or Step 14d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 or 3 (Option 2, Step 14d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 14 (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 14a):
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 14 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 14b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
3 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 14c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
3 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8 as requested by the MS in step 14 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 16):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4.2.2 Location Error: GPS Assistance Data Missing
70.8.4.2.2.1 Conformance requirement:
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS sends a RRLP MEASURE POSITION RESPONSE to network containing a Location Error component with an error indication if the measurement is not possible.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 subclause7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS04.31 sub clause 2.2
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 & 4
70.8.4.2.2.2 Test Purpose:
Verifies that a MS sends a correct positioning capability via control classmark sending. MS shall send back RRLP MEASURE POSITION RESPONSE message with Location Error component if GPS assistance data is missing. On receipt of second RRLP MEASURE POSITION REQUEST (with GPS assistance data included) from SS to start the measurement, the MS shall send back RRLP MEASURE POSITION RESPONSE to SS after finishing the measurement.
70.8.4.2.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 A-GPS assistance data stored in the MS is reset.
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke.
The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST without GPS assistance data.
The MS requests additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to 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.
The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Reset all stored A-GPS assistance data |
|
2 |
MS |
Initiate MOLR Procedure (location estimate) |
|
3 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH". |
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
5 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
6 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
7 |
SS -> MS |
AUTHENTICATION REQUEST |
|
8 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
9 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
10 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
11 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR request with MOLR-Type set to locationEstimate |
12 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 (without GPS assistance data) |
13 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response 1: locationError with gpsAssDataMissing |
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 (gps-measureInfo) |
18 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
19 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
20 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 11):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION:
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 12 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 |
msrPostionReq |
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 1 (Step 13):
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 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 |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 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 gps-MeasureInfo 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 |
FACILITY (Step 18):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step19):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4.3 MO-LR Positioning Measurement / Multiple RRLP Requests with Same Reference Number
70.8.4.3.1 Conformance requirement:
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS ignores the later component if the old and new RRLP MEASURE POSITION REQUEST components have the same Reference Number.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 subclause7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS04.31 sub clause 2.5.5
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 & 4
70.8.4.3.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.8.4.3.3 Method of Test
Initial Conditions
System Simulator:
Serving Cell: default parameters.
Satellite signals: No GPS signal available.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke. The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER as the first one (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)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimate) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate. |
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 |
12 |
MS (Option 1) or MS ->SS (Option 2) |
– or RR APPLICATION INFORMATION |
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1). The SS continues to step 13. If the MS sends RRLP Measure Position Response: locationError with gpsAssDataMissing (Option 2) within 8 seconds, then the SS continues to step 12a. |
12a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 12 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
12b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 12a, the MS acknowledges the received assistance data. |
12c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2. If the MS requested additional assistance data in step 12 that is available in the SS, this message may include further assistance data. |
12d |
MS (Option 2) |
MS is performing the measurement (Option 2) |
|
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 2 with same reference number as in Request 1 (Option 1) or RRLP MEASURE POSITION REQUEST 3 with same reference number as in Request 2 (Option2) Note: The satellite signals should be made available to MS after sending this message |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION RESPONSE (gps-measureInfo) |
15 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
16 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 11, 12c and 13: RRLP Measure Position Request Steps 12, 14: RRLP Measure Position Response Step 12a: RRLP Assistance Data Step 12b: 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 |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 12 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
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 12a):
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 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 12b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request 2 (Step 12c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 12 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Request 2 (Option 1) or Request 3 (Option 2) (Step 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
Enumerated |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
Enumerated |
oneSet |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 14):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp A valid response will contain gps-MeasureInfo |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters 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 |
FACILITY (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 16):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4.4 MO-LR Positioning Measurement / Multiple RRLP Requests with Different Reference Number
70.8.4.4.1 Conformance requirement
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS aborts activity for the former RRLP MEASURE POSITION REQUEST component and starts to act according to the later RRLP MEASURE POSITION REQUEST component if the old and new RRLP MEASURE POSITION REQUEST components have different Reference Number.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 subclause7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.31 sub clause 2.5.5
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 & 4
70.8.4.4.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.8.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 in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke. The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends the second RRLP MEASURE POSITION REQUEST with a different REFERENCE NUMBER 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)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimate) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate. |
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 |
12 |
MS (Option 1) or MS ->SS (Option 2) |
– or RR APPLICATION INFORMATION |
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1) The SS continues to step 13. If the MS sends RRLP Measure Position Response: locationError with gpsAssDataMissing (Option 2) within 8 seconds, then the SS continues to step 12a. |
12a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 12 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
12b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 12a, the MS acknowledges the received assistance data. |
12c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2. If the MS requested additional assistance data in step 12 that is available in the SS, this message may include further assistance data. |
12d |
MS (Option 2) |
MS is performing the measurement (Option 2) |
|
13 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 2 with different reference number from Request 1 (Option 1) or RRLP MEASURE POSITION REQUEST 3 with different reference number from Request 2 (Option2) Note: The satellite signals should be made available to MS after sending this message |
14 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1 or 2a) Check reference number is 2 or locationError with gpsAssDataMissing (Option 2b) Check reference number is 2 |
14a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 14 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
14b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 14a, the MS acknowledges the received assistance data. |
14c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 14 that is available in the SS, this message may include further assistance data. |
14d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 14, this message contains gps-MeasureInfo. |
15 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
16 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
17 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 11, 12c, 13 and 14c: RRLP Measure Position Request Steps 12, 14 and 14d: RRLP Measure Position Response Steps 12a and 14a: RRLP Assistance Data Steps 12b and 14b: 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 |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 12 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
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 12a):
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 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 12b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request 2 (Step 12c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 12 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Request 2 (Option 1) or Request 3 (Option 2) (Step 13):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 14 (Option 1 or 2a) or Step 14d (Option 2b)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 14 (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 14a):
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 14 (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 Assistance Data Ack (14b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 14c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 14 (Option 2b). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 15):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 16):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.4.5 MO-LR Positioning Measurement / RR Management Commands
70.8.4.5.1 Conformance requirement
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting its own location or that its own location be sent to another LCS client, this message carries LCS QoS information (e.g. accuracy, response time).
The MS invokes a MO-LR by sending a REGISTER message to network containing a LCS-MOLR invoke component with MO-LR TYPE set to LocationEstimate, LCS QoS value and other optional field if it is needed.
The MS aborts the measurement procedure and starts on the RR MANAGEMENT procedure if a RR MANAGEMENT command is received during the measurement procedure. The MS sends RR MANAGEMENT RESPONSE message upon completion.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 sub clauses 7.6.6, 10.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.80 / 3GPP TS 24.080 sub clauses 2.4, 2.5, 3.4 & 4
70.8.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 a RR MANAGEMENT command is received during the measurement procedure. The MS shall send a 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.8.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 in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke. The SS determines the positioning method and instigates the particular message sequence by sending RRLP MEASURE POSITION REQUEST including assistance data to start the measurement.
Option 1: The MS then performs positioning measurements. After a delay of 8 seconds, the SS sends 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.
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)
The SS returns location estimate to MS through DTAP LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message after receiving location estimate.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimate) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM "Mobile identity" IE contains the TMSI. The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR with MOLR-Type set to locationEstimate. |
11 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP MEASURE POSITION REQUEST 1 |
12 |
MS (Option 1) or MS ->SS (Option 2) |
– or RR APPLICATION INFORMATION |
If no message is received from the MS within 8 seconds, then the SS shall assume that the MS is performing the measurement (Option 1). The SS continues to step 13. If the MS sends RRLP Measure Position Response: locationError with gpsAssDataMissing (Option 2) within 8 seconds, then the SS continues to step 12a. |
12a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 12 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
12b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 12a, the MS acknowledges the received assistance data. |
12c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request 2. If the MS requested additional assistance data in step 12 that is available in the SS, this message may include further assistance data. |
12d |
MS (Option 2) |
MS is performing the measurement (Option 2) |
|
13 |
SS -> MS |
RR MANAGEMENT COMMAND |
|
14 |
MS -> SS |
RR MANAGEMENT COMPLETE |
MS terminates the measurement procedure and act on the RR management command |
15 |
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 |
16 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: gps-MeasureInfo (Option 1 or 2a) or locationError with gpsAssDataMissing (Option 2b) |
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. If the MS requested additional assistance data in step 16 that is available in the SS, this message may include further assistance data. |
16d |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 16, this message contains gps-MeasureInfo. |
17 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT (locationEstimate) |
18 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
19 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 11, 12c, 15 and 16c: RRLP Measure Position Request Steps 12, 16 and 16d: RRLP Measure Position Response Steps 12a and 16a: RRLP Assistance Data Steps 12b and 16b: 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 |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 12 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
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 12a):
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 12 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 12b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request 2 (Step 12c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 12 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
RR Management Command (Classmark Enquiry) (Step 13):
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 15):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
referenceTime |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.3 |
acquisAssist |
SEQUENCE |
See TS 51.010-7 sub clause 5.1.8 |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Measure Position Response (Step 16 (Option 1 or 2a) or Step 16d (Option 2b)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionRsp (A valid response will contain gps-MeasureInfo otherwise locationError will be returned) |
gps-MeasureInfo |
SEQUENCE |
Any value of the parameters is acceptable. |
locationError |
SEQUENCE |
Any error value is acceptable except gpsAssDataMissing. |
extended-reference |
SEQUENCE |
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 16 (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 16a):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
If the MS requested further assistance data in Step 16 (Option 2b) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 (16b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceDataAck |
RRLP Measure Position Request (Step 16c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer, 0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msAssisted |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 16 (Option 2b). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 17):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = lcs-MOLR LCS-MOLRRes ->locationEstimate (Note) |
Note: Any value for locationEstimate may be used. The SS shall not be required to calculate the value from the returned gps-MeasureInfo values. |
RELEASE COMPLETE (Step 18):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.5 MO_LR Basic Self Location Request for MS-Based AGPS
The test cases in this sub clause focus on Mobile Originating Location Request using MS-Based AGPS method. A MO-LR procedure could occur for requesting assistance data for mobile’s own location.
70.8.5.1 MO_LR Basic Self Location Request in Idle Mode (Normal Case)
70.8.5.1.1 Conformance requirements:
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes self-location request by sending a REGISTER message containing a LCS-MOLR invoke component with MO_LR TYPE set to ASSISTANCE DATA, LOCATION_METHOD TYPE set ASSISTEDGPS, and GPS_ASSISTANCE_DATA TYPE set to the type of ASSISTANCE_DATA requested.
3. The MS sends RRLP ASSISTANCE DATA ACK. for each RRLP ASSISTANCE DATA component.
4. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 03.71, sub clause 7.6.6,
3GPP TS 04.30 sub clause 5.1.1,
3GPP TS 04.80 / 3GPP TS 24.080 sub clause 2.4, 2.5, 3.4 and 4
70.8.5.1.2 Test Purpose
To verify that a MS invokes a self-location request by sending the network a REGISTER message containing FACILITY IE LCS-MOLR REQ. On receipt of each of RRLP ASSISTANCE DATA from SS with the requested assistance data, MS shall send RRLP ASSISTANCE ACK for each component to SS. When the MS receives a FACILITY message containing a FACILITY IE LCS-MOLR return result for the acknowledgement of completing assistance data delivery, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
70.8.5.1.3 Method of Test
Initial Conditions
System Simulator:
Serving cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test Procedure:
A MOLR procedure as call independent supplementary services is initiated from the MS. The MS performs control early classmark sending to provide LCS positioning method capability. After sending the CIPHERING MODE COMPLETE message the MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke for Assistance Data. The SS sends a number of RRLP Assistance Data components and MS sends RRLP Assistance Data Ack for each component. SS sends DTAP LCS-MOLR Return Result for acknowledgement of completion of assistance data delivery. The MS performs the measurement and calculates the position fix using the assistance data delivered. The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate LCS MOLR Procedure (assistance data request) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Establishment cause indicates "Supplementary service activation". "mobile station classmark 2" includes settings for ES_IND. |
5 |
MS -> SS |
CLASSMARK CHANGE |
"mobile station classmark 2" including settings for ES IND and CM3 supported. "mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. Position method Capability is set to 1 and Bit 2 is set to 1 ( MS-Based GPS) |
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
7 |
MS -> SS |
AUTHENTICATION RESP |
SRES specifies correct value. |
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
10 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR with MOLR-Type set to assistanceData. |
11n |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP ASSISTANCE DATA The number of instances of this message depends on the amount of assistance data requested in step 10 |
12n |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP ASSISTANCE DATA ACK Each instance of RRLP ASSISTANCE DATA message in step 11 is acknowledged |
13 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT |
14 |
MS -> SS |
RELEASE COMPLETE |
Terminates the session |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
CLASSMARK CHANGE
Information element |
Value/remark |
as default except: |
|
Mobile station Classmark 2 |
|
-ES_IND |
"Controlled Early Classmark Sending" option is implemented in the MS. |
CM3 |
The MS Supports options that are indicated in classmark 3 IE |
Mobile station Classmark 3 |
See below |
MS Positioning Method Capability |
This bit indicates that the MS supports Positioning Method for the provision of Location Services. |
Positioning Method(s) support, 5 bit field |
Support of certain positioning method (3GPP TS 24.008, table 10.5.1.7), Bit 2 set to 1. |
REGISTER (Step 10):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg MOLR-Type->assistanceData Location Method->assistedGPS GPSAssistanceData-> any value is acceptable |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 11n: RRLP Assistance Data Steps 12n: RRLP Assistance Data Ack. |
RRLP Assistance Data (Step 11n):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
The assistance data requested by the MS in Step 10 that is available in the SS, shall be sent in 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 |
1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Assistance Data Ack (Step 12n):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceDataAck |
FACILITY (Step 13):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> empty (Note) |
Note: For acknowledgement of assistance data delivery procedure, SS shall send LCS-MOLR Facility return result to MS, there is no parameter for this. |
RELEASE COMPLETE (Step 14):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (0011 1010) |
70.8.5.2 MO_LR Basic Self Location Request in Dedicated Mode (Normal case)
70.8.5.2.1 Conformance Requirement:
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes self-location request by sending a REGISTER message containing a LCS-MOLR invoke
component with MO_LR TYPE set to ASSISTANCE DATA, LOCATION_METHOD TYPE set
ASSISTEDGPS, and GPS_ASSISTANCE_DATA TYPE set to the type of ASSISTANCE_DATA requested.
3. The MS sends RRLP ASSISTANCE DATA ACK. for each RRLP ASSISTANCE DATA component.
4. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References:
3GPP TS 03.71 sub clause 7.6.6
3Gpp TS 24.30 sub clause 5
3GPP TS 24.80 sub clause 4
70.8.5.2.2 Test Purpose
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the FACILITY IE LCS-MOLR REQ on an already established speech call related main DCCH (FACCH). On receipt of a RRLP ASSISTANCE DATA from SS with the requested assistance data, MS shall send back RRLP ASSISTANCE ACK for each component to SS. When the MS receives a FACILITY message containing a FACILITY IE LCS-MOLR return result for the acknowledgment of completing assistance data delivery, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
70.8.5.2.3 Method of Test
Initial Conditions:
System Simulator:
Serving Cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS has valid TMSI and CSKN.
The MS is brought into the state U10 by using table 26.8.1.2/3
Test Procedure:
A MOLR procedure as call independent supplementary services is initiated from the MS on the existing FACCH channel. After received CM SERVICE ACCEPT message, MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke for Assistance Data. The SS sends a number of RRLP ASSISTANCE DATA components and MS sends acknowledgement of RRLP ASSISTANCE DATA ACK for each component. SS sends DTAP LCS-MOLR Return Result for acknowledgement of completion of assistance data delivery procedure. MS performs the measurement and calculates the location estimate using the assistance data delivered. The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence:
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate LCS MOLR Procedure (assistance data request) on existing FACCH channel |
|
2 |
MS -> SS |
CM SERVICE REQUEST |
"Mobile identity" IE contains the TMSI. Establishment cause indicates "Supplementary service activation" "mobile station classmark 2" including settings for ES IND and CM3 supported. |
3 |
SS -> MS |
CM SERVICE ACCEPT |
|
4 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE With the component of Invoke message set to LCS-MOLR with MOLR-Type set to assistanceData. |
5n |
SS->MS |
RR APPLICATION INFORMATION |
RRLP ASSISTANCE DATA The number of instances of this message depends on the amount of assistance data requested in step 4 |
6n |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP ASSISTANCE DATA ACK Each instance of RRLP ASSISTANCE DATA message in step 5 is acknowledged |
7 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT |
8 |
MS->SS |
RELEASE COMPLETE |
Terminates the session |
9 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents:
REGISTER (Step 4):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg MOLR-Type->assistanceData Location Method->assistedGPS GPSAssistanceData-> any value is acceptable |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Step 5n: RRLP Assistance Data Step 6n: RRLP Assistance Data Ack. |
RRLP Assistance Data (Step 5n):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
The assistance data requested by the MS in Step 4 that is available in the SS, shall be sent in 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 |
1 or 0. If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly. |
extended-reference |
SEQUENCE |
Rel 5 and later |
RRLP Assistance Data Ack (Step 6n):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceDataAck |
FACILITY (Step 7):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS message (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes ->empty (note) |
Note: For acknowledgement of assistance data delivery procedure, SS shall send LCS-MOLR Facility return result to MS, there is no parameter for this. |
RELEASE COMPLETE (Step 8):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.5.3 MO_LR Basic Self Location Request in Idle Mode (Alternative Case)
70.8.5.3.1 Conformance requirements:
The following requirements apply for this test:
1. If the MS is in idle mode, the MS requests an SDCCH and sends a DTAP CM service request indicating a request for call independent supplementary services to the BSC.
2. The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.
3. On receiving an RRLP MEASURE POSITION REQUEST message, the MS tries to perform the requested location measurements, and possibly calculates it own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC.
5. The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
6. After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.31 sub clause 2.2
70.8.5.3.2 Test Purpose
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing an MO-LR Request of type “locationEstimate”. When the MS receives a FACILITY message containing a MO-LR return result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
70.8.5.3.3 Method of Test
Initial Conditions
System Simulator:
Serving cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Test Procedure:
The MS invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request of type “locationEstimate”.
The SS orders an A-GPS positioning measurement by sending RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages followed by an RRLP Measure Position Request including further assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Procedure (location estimation) |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
The CM Service Type IE indicates "Supplementary service activation". |
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 filed), 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 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request and MO-LR Type set to “locationEstimate”. |
12 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
13 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
14 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
15 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
16 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
17 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo (Option 1) or locationError with gpsAssDataMissing and additionalAssistanceData (Option 2) |
17a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 17 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
17b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 17a, the MS acknowledges the received assistance data. |
17c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 17 that is available in the SS, this message may include further assistance data. |
17d |
MS-> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 17, this message contains locationInfo. |
18 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT message containing location estimate |
19 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
20 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 11):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg MOLR-Type->locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 16 and 17c: RRLP Measure Position Request Steps 17 and 17d: RRLP Measure Position Response Steps 12, 14, 17a: RRLP Assistance Data Steps 13, 15, 17b: RRLP Assistance Data Ack. |
RRLP Assistance Data (Step 12):
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 13, 15, 17b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 17b) |
component |
CHOICE |
assistanceDataAck |
RRLP Assistance Data (Step 14):
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 (Step 16):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
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 17 (Option 1) or 17d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 17d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain 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 17 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
additionalAssistanceData |
SEQUENCE |
|
gpsAssistanceData |
OCTET STRING |
Indicates missing assistance data elements |
RRLP Assistance Data (Step 17a):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
If the MS requested further assistance data in Step 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 17c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 17 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 18):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate |
RELEASE COMPLETE (Step 20):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.5.4 MO_LR Basic Self Location Request in Dedicated Mode (Alternative Case)
70.8.5.4.1 Conformance requirements:
The following requirements apply for this test:
1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.
2. The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.
3. On receiving an RRLP MEASURE POSITION REQUEST message, the MS tries to perform the requested location measurements, and possibly calculates it own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC.
5. The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
6. After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.31 sub clause 2.2
70.8.5.4.2 Test Purpose
To verify that the MS invokes a self-location request by sending the network a REGISTER message containing an MO-LR Request of type “locationEstimate” on an already established speech call related SACCH. When the MS receives a FACILITY message containing a MO-LR return result carrying the requested location estimate, it clears the transaction by sending a RELEASE COMPLETE message.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
70.8.5.4.3 Method of Test
Initial Conditions
System Simulator:
Serving cell: default parameters.
Satellite signals: default conditions.
Mobile Station:
The MS has valid TMSI and CKSN.
The MS is brought into state U10 by using table 26.8.1.2/3.
Test Procedure:
The MS invokes call independent supplementary service on an existing SACCH channel. After receiving a CM SERVICE ACCEPT message, the MS invokes a self location request by sending a REGISTER message containing an MO-LR request of type “locationEstimate”.
The SS orders an A-GPS positioning measurement by sending RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages followed by an RRLP Measure Position Request including further assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result. When the MS receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test:
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MO-LR procedure (location estimation) on existing SACCH channel |
|
2 |
MS -> SS |
CM SERVICE REQUEST |
The CM Service Type IE indicates "Supplementary service activation". |
3 |
SS -> MS |
CM SERVICE ACCEPT |
|
4 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request and MO-LR Type set to “locationEstimate”. |
5 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
6 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
7 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
8 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
9 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
10 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo (Option 1) or locationError with gpsAssDataMissing and additionalAssistanceData (Option 2) |
10a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 10 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
10b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 10a, the MS acknowledges the received assistance data. |
10c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 10 that is available in the SS, this message may include further assistance data. |
10d |
MS-> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 10, this message contains locationInfo. |
11 |
SS -> MS |
FACILITY |
LCS MO-LR RETURN RESULT message containing location estimate |
12 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
13 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 4):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg MOLR-Type->locationEstimate |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 9 and 10c: RRLP Measure Position Request Steps 10 and 10d: RRLP Measure Position Response Steps 5, 7, 10a: RRLP Assistance Data Steps 6, 8, 10b: RRLP Assistance Data Ack. |
RRLP Assistance Data (Step 5):
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 6, 8, 10b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 10b) |
component |
CHOICE |
assistanceDataAck |
RRLP Assistance Data (Step 7):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
assistanceData |
gps-AssistData |
SEQUENCE |
|
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 (Step 9):
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 10 (Option 1) or 10d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 10d) |
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 10 (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 10a):
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 10 (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 10c):
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 10 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 11):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010 ) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate |
RELEASE COMPLETE (Step 12):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |
70.8.6 MO-LR Transfer to 3rd Party for MS-Based A-GPS
70.8.6.1 Conformance requirements
The following requirements apply for this test:
1. If the MS is in idle mode, the MS requests an SDCCH and sends a DTAP CM service request indicating a request for call independent supplementary services to the BSC.
2. The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.
3. If the MS is requesting that its location be sent to another LCS client, the message shall include the identity of the LCS client and may include the address of the GMLC through which the LCS client should be accessed.
4. On receiving an RRLP MEASURE POSITION REQUEST message, the MS tries to perform the requested location measurements, and possibly calculates it own position. When the MS has location measurements, location estimate, or an error indication (measurements/location estimation not possible), it sends the results in the Measure Position Response component to the SMLC.
5. The VMSC returns a DTAP LCS MO-LR Return Result to the MS carrying any location estimate requested by the MS, ciphering keys or a confirmation that a location estimate was successfully transferred to the GMLC serving an LCS client.
6. The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component.
7. After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.
Test References
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.31 sub clause 2.2
70.8.6.2 Test Purpose
To verify that the MS invokes a transfer of its own location to a 3rd party LCS Client by sending the network a REGISTER message containing the Facility IE LCS MO-LR with LCSClientExternalID present. After receiving a FACILITY message as confirmation that the location estimate has been transferred to the requested LCS client, the MS terminates the dialogue by sending a RELEASE COMPLETE message.
70.8.6.3 Method of Test
Initial Conditions
System Simulator (SS):
Serving Cell: default parameters
Satellite signals: default conditions.
Mobile Station (MS):
The MS is in MM-state “idle, updated” with valid TMSI and CKSN.
Specific PICS statements
– TSPC_MS_RRLP_RELEASE
PIXIT statements
–
Test Procedure
The MS invokes call independent supplementary service through a CM SERVICE REQUEST. The SS initiates authentication and ciphering. Then the MS invokes an MO-LR request of type “locationEstimate” with “LCSClientExternalID” present.
The SS orders an A-GPS positioning measurement by sending RR APPLICATION INFORMATION messages containing RRLP Assistance Data messages followed by an RRLP Measure Position Request including further assistance data.
Option 1: The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
Option 2: The MS may request additional assistance data by sending an RRLP Measure Position Response message containing a location error with IE LocErrorReason set to gpsAssDataMissing. If the MS requests additional assistance data that is available in the SS, then the SS provides the requested assistance data in zero, one or more RRLP Assistance Data delivery messages followed by an RRLP Measure Position Request message which may include further assistance data. If the MS requests additional assistance data and the entire requested assistance data is not available in the SS, then the SS repeats the RRLP Measure Position Request message without assistance data. The MS then performs positioning measurements, and responds with an RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The SS responds with a FACILITY message containing an MO-LR result to confirm that the location estimate has been transferred to the LCS client. When the MS receives the FACILITY message, it clears the transaction by sending a RELEASE COMPLETE message.
Maximum duration of the test
5 minutes.
Expected Sequence
Step |
Direction |
Message |
Comments |
1 |
MS |
Initiate MOLR Transfer to 3rd Party Procedure |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates, "Other procedures which can be completed with an SDCCH" |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
The CM Service Type IE indicates "Supplementary service activation" "mobile station classmark 2" includes settings for ES_IND. |
5 |
MS->SS |
CLASSMARK CHANGE |
"mobile station classmark 2" includes settings for ES_IND. "mobile station classmark 3" includes settings for Positioning. The 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 |
MS -> SS |
REGISTER |
Call Independent SS containing Facility IE with LCS-MOLR request with MOLR-Type set to locationEstimate with LCSClientExternalID present |
12 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
13 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
14 |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data |
15 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck |
16 |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request |
17 |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response: locationInfo (Option 1) or locationError with gpsAssDataMissing and additionalAssistanceData (Option 2) |
17a |
SS -> MS |
RR APPLICATION INFORMATION |
RRLP Assistance Data. If the MS requested additional assistance data in step 17 that is available in the SS, then SS provides the requested data in zero, one or more RRLP Assistance Data delivery messages. |
17b |
MS -> SS |
RR APPLICATION INFORMATION |
RRLP assistanceDataAck. If the SS sent additional assistance data in step 17a, the MS acknowledges the received assistance data. |
17c |
SS-> MS |
RR APPLICATION INFORMATION |
RRLP Measure Position Request. If the MS requested additional assistance data in step 17 that is available in the SS, this message may include further assistance data. |
17d |
MS-> SS |
RR APPLICATION INFORMATION |
RRLP Measure Position Response. If the MS requested additional assistance data in step 17, this message contains locationInfo. |
18 |
SS |
SS may return the location estimate result to the LCS Client as identified by the LCSClientExternalID provided in the REGISTER message |
|
19 |
SS -> MS |
FACILITY |
LCS MO-LR Return Result message as confirmation that the position estimate was transferred to the requested LCS client. |
20 |
MS -> SS |
RELEASE COMPLETE |
MS terminates the dialogue |
21 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific Message Contents
REGISTER (Step 11):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
REGISTER (xx11 1011) |
Facility |
Invoke = LCS-MOLR LCS-MOLRArg Molr-Type -> locationEstimate lcsClientExternalID -> externalAddress |
SS version indicator |
Value 1 or above |
RR_APPLICATION_INFORMATION
Information element |
Value/remark |
Protocol Discriminator |
RR Management Protocol (0110) |
Skip Indicator |
|
Message Type |
Application Information Message type |
APDU ID |
APDU ID -> RRLP => 0000 |
APDU Flags |
Bit1=0 -> Last or only segment Bit2=0 -> First or only segment Bit3=0 -> Command or Final Response Bit4=spare |
APDU Data |
2-N Byte ASN.1 Coded Steps 16 and 17c: RRLP Measure Position Request Steps 17 and 17d: RRLP Measure Position Response Steps 12, 14, 17a: RRLP Assistance Data Steps 13, 15, 17b: RRLP Assistance Data Ack. |
RRLP Assistance Data (Step 12):
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 13, 15, 17b):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 17b) |
component |
CHOICE |
assistanceDataAck |
RRLP Assistance Data (Step 14):
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 (Step 16):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
|
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 17 (Option 1) or 17d (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 or 2 (Option 2, Step 17d) |
component |
CHOICE |
msrPositionRsp (A valid response will contain 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 17 (Option 2)):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
1 |
component |
CHOICE |
msrPositionRsp |
locationError |
SEQUENCE |
|
locErrorReason |
ENUMERATED |
gpsAssDataMissing |
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 17a):
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 17 (Option 2) that is available in the SS, SS shall send zero, one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 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 17c):
Information element |
Type |
Value/remark |
ASN.1 encoded |
||
referenceNumber |
Integer,0 to 7 |
2 |
component |
CHOICE |
msrPositionReq |
methodType |
CHOICE |
msBased |
positionMethod |
ENUMERATED |
gps |
measureResponseTime |
Integer 0 to 7 |
5 |
accuracy |
Integer (0-127) |
127 |
useMultipleSets |
ENUMERATED |
oneSet |
gps-AssistData |
SEQUENCE |
May contain further assistance data from TS 51.010-7 as requested by the MS in step 17 (Option 2). |
extended-reference |
SEQUENCE |
Rel 5 and later |
FACILITY (Step 19):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
FACILITY (0011 1010) |
Facility |
Return Result = LCS-MOLR LCS-MOLRRes -> locationEstimate |
RELEASE COMPLETE (Step 20):
Information element |
Value/remark |
Protocol Discriminator |
Call Independent SS (1011) |
Transaction Identifier |
|
Message Type |
RELEASE COMPLETE (xx10 1010) |