70.14.5 MO-LR / Dedicated Mode for Mobiles Supporting MS-Based GNSS / Assistance Data Request

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

70.14.5.1 Conformance Requirement:

The following requirements apply for this test:

1. The MS sends CM SERVICE REQUEST to network for call independent supplementary service.

2. The MS invokes self-location request by sending a REGISTER message containing a LCS MO LR invoke
component with MO LR-TYPE set to ASSISTANCE DATA, LOCATION_METHOD TYPE set
ASSISTEDGPS, and GPS_ASSISTANCE_DATA TYPE set to the type of ASSISTANCE_DATA requested.

3. The MS sends RRLP ASSISTANCE DATA ACK. for each RRLP ASSISTANCE DATA component.

4. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message.

Test References:

3GPP TS 03.71 sub clause 7.6.6

3Gpp TS 24.30 sub clause 5

3GPP TS 24.80 sub clause 4

70.14.5.2 Test Purpose

To verify that the MS invokes a self-location request by sending the network a REGISTER message containing the FACILITY IE LCS-MOLR REQ on an already established speech call related main DCCH (FACCH). On receipt of a RRLP ASSISTANCE DATA from SS with the requested assistance data, MS shall send back RRLP ASSISTANCE ACK for each component to SS. When the MS receives a FACILITY message containing a FACILITY IE LCS-MOLR return result for the acknowledgment of completing assistance data delivery, it clears the transaction by sending a RELEASE COMPLETE message.

Specific PICS statements

PIXIT statements

70.14.5.3 Method of Test

Initial Conditions:

System Simulator:

Serving Cell: default parameters.

Satellite signals: default conditions.

Mobile Station:

The MS has valid TMSI and CSKN.

The MS is brought into the state U10 by using table 26.8.1.2/3

Specific PICS statements

PIXIT statements

Test Procedure:

This test case includes sub-test cases dependent on the GNSS supported by the MS. Each sub-test case is identified by a Sub-Test Case Number as defined below:

Sub-Test Case Number

Supported GNSS

1

MS supporting A-GLONASS only

2

MS supporting A-Galileo only

3

MS supporting A-GPS and Modernized GPS only

4

MS supporting A-GPS and A-GLONASS only

5

Reserved

6

Reserved

7

Reserved

8

Reserved

9

MS supporting A-BDS only

10

MS supporting A-GPS and A-BDS only

A MOLR procedure as call independent supplementary services is initiated from the MS on the existing FACCH channel.

After received CM SERVICE ACCEPT message, MS sends a REGISTER message with Facility IE containing a component set to a DTAP LCS-MOLR Invoke for Assistance Data.

The SS sends a number of RRLP ASSISTANCE DATA components and MS sends acknowledgement of RRLP ASSISTANCE DATA ACK for each component.

SS sends DTAP LCS-MOLR Return Result for acknowledgement of completion of assistance data delivery procedure.

The MS terminates the dialogue by sending RELEASE COMPLETE message.

Maximum duration of the test:

5 minutes.

Expected Sequence:

Step

Direction

Message

Comments

1

MS

Initiate LCS MOLR Procedure (assistance data request) on existing FACCH channel

2

MS -> SS

CM SERVICE REQUEST

"Mobile identity" IE contains the TMSI.

Establishment cause indicates "Supplementary service activation"

"mobile station classmark 2" including settings for ES IND and CM3 supported.

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

Call Independent SS containing Facility IE

With the component of Invoke message set to LCS-MOLR with MOLR-Type set to assistanceData.

5

SS -> MS

RR APPLICATION INFORMATION

RRLP Positioning Capability Request

6

MS -> SS

RR APPLICATION INFORMATION

RRLP Positioning Capability Response

7n

SS->MS

RR APPLICATION INFORMATION

RRLP ASSISTANCE DATA

The number of instances of this message depends on the amount of assistance data requested in step 4

8n

MS -> SS

RR APPLICATION INFORMATION

RRLP ASSISTANCE DATA ACK

Each instance of RRLP ASSISTANCE DATA message in step 7n is acknowledged

9

SS -> MS

FACILITY

LCS MO-LR RETURN RESULT

10

MS->SS

RELEASE COMPLETE

Terminates the session

11

SS -> MS

CHANNEL RELEASE

The main signalling link is released.

Specific Message Contents:

REGISTER (Step 4):

Information element

Value/remark

Protocol Discriminator

Call Independent SS message (1011)

Transaction Identifier

Message Type

REGISTER (xx11 1011)

Facility

Invoke = LCS-MOLR

LCS-MOLRArg

MOLR-Type-> assistanceData

Location Method-> assistedGANSS / assistedGPSandGANSS (Sub-Tests 3, 4 and 10)

GPSAssistanceData-> any value is acceptable

ganssAssistanceData-> any value is acceptable

RR_APPLICATION_INFORMATION

Information element

Value/remark

Protocol Discriminator

RR Management Protocol (0110)

Skip Indicator

Message Type

Application Information Message type

APDU ID

APDU ID -> RRLP => 0000

APDU Flags

Bit1=0 -> Last or only segment

Bit2=0 -> First or only segment

Bit3=0 -> Command or Final Response

Bit4=spare

APDU Data

2-N Byte  ASN.1 Coded

Step 5: RRLP Positioning Capability Request

Step 6: RRLP Positioning Capability Response

Step 7n: RRLP Assistance Data

Step 8n: RRLP Assistance Data Ack.

RRLP Positioning Capability Request (Step 5):

Information element

Type

Value/remark

ASN.1 encoded

extended-reference

SEQUENCE

RRLP Positioning Capability Response (Step 6):

Information element

Type

Value/remark

ASN.1 encoded

extended-reference

SEQUENCE

The value returned by the MS shall equal the value received from the SS in the Positioning Capability Request (Step 5).

posCapabilities

SEQUENCE

nonGANSSpositionMethods

BIT STRING

May only be included for Sub-Tests 3, 4 and 10.

gANSSPositionMethods

SEQUENCE

Included for each MS supported GANSS

ganssID

INTEGER

Sub-Test 1: value 3

Sub-Test 2: absent

Sub-Test 3: value 1

Sub-Test 4: value 3

Sub-Test 9: value 4

Sub-Test 10: value 4

gANSSPositioningMethodTypes

BIT STRING

Bit 1 (msBased) set to value 1

gANSSSignals

BIT STRING

Dependent on MS capabilities

RRLP Assistance Data (Step 7n):

Information element

Type

Value/remark

ASN.1 encoded

referenceNumber

Integer,0 to 7

1

Component

CHOICE

assistanceData

gps-AssistData

SEQUENCE

This field may only be present for Sub-Tests 3 and 4.

The GPS assistance data requested by the MS in Step 4 that is available in the SS, shall be sent in one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 5.1.3 to 5.1.8. Each message shall contain a maximum of 242 octets.

moreAssDataToBeSent

ENUMERATED

1 or 0.

If SS sends more than one RRLP assistance data delivery message the moreAssDataToBeSent field shall be set accordingly.

extended-reference

SEQUENCE

ganss-AssistData

SEQUENCE

The GANSS assistance data requested by the MS in Step 4 that is available in the SS, SS shall send one or more RRLP Assistance Data messages containing the requested assistance data from TS 51.010-7 sub clauses 6.1.3 and 6.1.4. Each message shall contain a maximum of 242 octets.

RRLP Assistance Data Ack (Step 8n):

Information element

Type

Value/remark

ASN.1 encoded

referenceNumber

Integer,0 to 7

1

Component

CHOICE

assistanceDataAck

FACILITY (Step 9):

Information element

Value/remark

Protocol Discriminator

Call Independent SS message (1011)

Transaction Identifier

Message Type

FACILITY (0011 1010 )

Facility

Return Result = LCS-MOLR

LCS-MOLRRes ->empty (note)

Note: For acknowledgement of assistance data delivery procedure, SS shall send LCS-MOLR Facility return result to MS, there is no parameter for this.

RELEASE COMPLETE (Step 10):

Information element

Value/remark

Protocol Discriminator

Call Independent SS (1011)

Transaction Identifier

Message Type

RELEASE COMPLETE (xx10 1010)