hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it received INTER SYSTEM TO UTRAN HANDOVER COMMAND towards a non-existing UTRAN cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 will be referenced for the default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with FR speech call. The SS does not configure a dedicated channel corresponding to the default configuration 3. The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORT and, then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. The MS will not be able to establish the connection to UTRAN dedicated channel. The SS checks that the handover is failed by checking that the MS returns to the old channel and transmits HANDOVER FAILURE to the SS through the old channel.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
MS
The SS brings the MS into GSM U10 state in cell 1 on a hopping traffic channel
2
SS
The SS configures the Physical channel of the UTRAN cell but here is no dedicated channel with the configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell.
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
MS
The MS fails to configure to the indicated RAB in Step 6 and fails to establish a connection to UTRAN cell
8
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell)
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.5 Test requirement
|
At step 8 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7 Inter system handover to UTRAN/From GSM/Failure/Cause: Frequency not implemented
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter‑system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency.
The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use frequency that it is not capable of, and then the MS shall return a HANDOVER FAILURE message with cause "frequency not implemented" (Reference 3GPP TS 04.18 subclause 3.4.4a.3).
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it received HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of frequency not implemented.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1 subclause 26.6.5.1 shall be referenced for the default parameters of Cell 1.
MS:
CC State U10 in cell 1.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure:
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell. The MS selects the GSM cell.
SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures the dedicated channel corresponding to the default configuration (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS), then sends HANDOVER TO UTRAN COMMAND the MS through the GSM serving cell. The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use frequency that it is not capable of, and then the MS shall return a HANDOVER FAILURE message with cause "frequency not implemented" (Reference 3GPP TS 04.18 subclause 3.4.4a.3) and continue the voice call on the old channel.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; the UTRAN cell broadcasts SIB16 containing pre-configuration information. MS camps on GSM cell and received SIB 16 from UTRAN cell.
2
MS
The SS brings the MS into GSM U10 state in cell 1.
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with unsupported frequency.
5
MS
The MS fails to establish a connection to UTRAN cell
6
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR Cause "frequency not implemented".
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1 except that the INTER SYSTEM TO UTRAN HANDOVER COMMAND indicates a frequency not supported by the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.5 Test requirement
|
At step 7 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8 Inter system handover to UTRAN/From GSM/Failure/Cause: UTRAN configuration unknown
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter-system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency. The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use preconfiguration that the mobile station has not read or instruct to use default reconfiguration not implemented by MS, then the MS shall return a HANDOVER FAILURE message with cause "UTRAN configuration unknown" (3GPP TS 04.18 subclause 3.4.4a.3).
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it receives HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of UTRAN configuration unknown.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1section 26.6.5.1 shall be referenced for the default parameters of cell 1.
MS:
CC State U10 in cell.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell, SIB16 is not broadcast in UTRAN cell and MS has no predefined configuration stored.
The MS selects the GSM cell. SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures a dedicated channel (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS). The SS sends a HANDOVER TO UTRAN COMMAND message through the GSM cell that instructs the MS to use a preconfiguration that the mobile station has not read or instructed to use default configuration not implemented by MS. The MS shall return a HANDOVER FAILURE message with cause "UTRAN preconfiguration unknown" and continue the voice call on the old cell.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; SIB16 is not broadcast in the UTRAN cell.
2
MS
The SS brings the MS into GSM U10 state in cell 1and MS has not any pre-configuration stored.
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with unknown preconfiguration.
5
MS
The MS fails to establish a connection to UTRAN cell
6
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR Cause "UTRAN configuration unknown".
Specific message contents
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Information Element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Inter System to UTRAN Handover Command Message Type
‘01100011'B
Handover to UTRAN Command IEI
TBD
Length of Handover to UTRAN Command contents
Octet length of the "Handover to UTRAN Command value part"
Handover to UTRAN Command value part
PER encoded ASN.1 value of type "HandoverToUTRANCommand-v1-IEs", content is presented in the next table.
Content of "HandoverToUTRANCommand-r3-IEs"
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
1
Activation time
now
Ciphering algorithm
Standard UMTS Encryption Algorithm UEA1
CHOICE Specification mode
Preconfiguration
- Predefined configuration identity
1
- RAB Info
- RAB identity
- GSM-MAP RAB identity
‘00000001'B
- CN domain identity
CS domain
- CHOICE Mode specific info
FDD
- uplink DPCH info
- uplink DPCH power control info
- DPCCH power offset
-6dB
- PC Preamble
1 frame
- SRB delay
7 frames
- Scrambling code type
long
- Reduced scrambling code number
0
- Spreading factor
16
- DL common information post
- DL DPCH info common
- DL DPCH power control info
- CHOICE Mode specific info
FDD
- DPC mode
Single TPC
- DL information perRL list
- Primary CPICH info
- Primary scrambling code
100
- DL DPCH info perRL
- pCPICH usage for channelEst
May be used
- DL channelization code
- Secondary scrambling code
1
- SF and code number
SF = 32, code number = 31
- Scrambling code change
No code change
- TPC combination index
0
- Frequency info
- UARFCN uplink(Nu)
See PIXIT
- UARFCN downlink(Nd)
See PIXIT
Maximum allowed uplink TX power
33dBm
HANDOVER FAILURE message content
Information element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Handover Failure Message Type
‘00101000'B
RR Cause
RR Cause (Refer : table 10.5.2.31.1/3GPP TS 04.18: RR Cause information element)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.5 Test requirement
|
At step 7 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9 Inter system handover to UTRAN/From GSM/Failure/Cause: Protocol Error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter‑system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency. The HANDOVER TO UTRAN COMMAND message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set TRUE according to subclause 9 of 3GPP TS 25.331.
3GPP TS 04.18 subclause 8.5
When on receipt of a message,
- an "imperative message part" error; or
- a "missing mandatory IE" error
is diagnosed or when a message containing:
- a syntactically incorrect mandatory IE; or
- an IE unknown in the message, but encoded as "comprehension required" (see clause 3GPP TS 24.007); or
- an out of sequence IE encoded as "comprehension required" (see clause 3GPP TS 24.007)
is received,
- the mobile station shall proceed as follows:
If the message is not one of the messages listed in clauses 8.5.1, 8.5.2, 8.5.3 the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (RR STATUS) with cause # 96 "Invalid mandatory information".
Reference(s)
3GPP TS 25.331 subclause 8.3.6 and 9.
3GPP TS 04.18 subclause 3.4.4a and 8.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.3 Test purpose
|
To test that the MS reactivates the old channel and transmits RR Status message to the network on the old channel in the GSM cell when it receives HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of protocol error.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1 section 26.6.5.1 shall be referenced for the default parameters of cell 1.
MS:
CC State U10 in cell 1.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell. The MS selects the GSM cell. SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures the dedicated channel corresponding to the default configuration 3 (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS), then sends HANDOVER TO UTRAN COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell.
The SS sends a HANDOVER TO UTRAN COMMAND message, that contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set TRUE according to 3GPP TS 25.331 subclause 9. Then the MS shall return an RR STATUS message on DCCH of cell 1 (old channel in GSM cell) with RR cause #96 “Invalid mandatory information”.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; The MS camps on GSM cell
2
MS
The SS brings the MS into GSM U10 state in cell 1
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with missing mandatory IE.
5
RR STATUS
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR cause #96 "Invalid mandatory information".
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1 except that in the INTER SYSTEM TO UTRAN HANDOVER COMMAND a mandatory IE is missing causing a protocol error.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.5 Test requirement
|
At step 5 the RR STATUS shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10 Inter system handover to UTRAN/From GSM/Integrity Protection Activation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.2 Conformance requirement
|
The MS shall include the Security START values in INTER RAT HANDOVER INFO in the RR message UTRAN CLASSMARK CHANGE -definition and in the RRC message HANDOVER TO UTRAN COMPLETE.
If the MS succeeds to establish the connection to UTRAN after reception of an INTERSYSTEM TO UTRAN HANDOVER COMMAND, the NW may start Integrity protection using the previously received CS START value by sending a SECURITY MODE COMMAND message to the MS.
Reference(s)
3GPP TS 25.331 subclause 8.1.12 and 8.3.6.
3GPP TS 04.18 subclause 3.4.4a and 3.4.11.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.3 Test purpose
|
To test that MS supporting both GSM and UTRAN applies the correct CS Security START value after a successful handover from GSM to UTRAN when Integrity protection is activated by the NW.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN.
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters of Cell 2.
Mobile Station:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with FR speech call.
The SS starts the UTRAN cell, configures the UTRAN dedicated channel corresponding to default handover configuration 3 and sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell.
The SS verifies that the MS includes the UTRAN cell in the MEASUREMENT REPORT. The SS then sends a CLASSMARK ENQUIRY requesting an UTRAN CLASSMARK CHANGE from the MS. The MS responds with a UTRAN CLASSMARK CHANGE and the SS verifies that the INTER RAT HANDOVER INFO includes a START value for the CS domain.
The SS sends an INTERSYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS. After the MS receives the command, it shall switch to the dedicated channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell. It is also verified that the START value for the CS domain in the HANDOVER TO UTRAN COMPLETE message is the same as the START value received in the INTER RAT HANDOVER INFO.
The SS attempts to activate Integrity protection by sending an Integrity protected SECURITY MODE COMMAND on the DCCH with an incorrect IE “Integrity check info”. It is verified that the MS does not respond with a SECURITY MODE COMPLETE message.
The SS retransmits the SECURITY MODE COMMAND on the DCCH with a correct IE Integrity Check Info and the MS responds with an Integrity protected SECURITY MODE COMPLETE. Both SS and MS shall use the START value for the CS domain for Integrity protection that the MS has indicated in UTRAN CLASSMARK CHANGE and HANDOVER TO UTRAN COMPLETE.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
MS – SS
The SS brings the MS into GSM U10 state in cell 1 on a hopping traffic channel
2
SS
The SS configures the UTRAN cell with a dedicated channel configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell (default handover configuration 3).
The following messages are sent and received on the GSM cell
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4.
5
CLASSMARK ENQUIRY
6
UTRAN CLASSMARK CHANGE
Verify that the ue-SecurityInformation is present.
7
INTERSYSTEM TO UTRAN HANDOVER COMMAND
8
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTERSYSTEM TO UTRAN HANDOVER COMMAND
9
SS
The SS waits for uplink physical channel in synchronization
The following messages are sent and received on the UTRAN cell.
10
HANDOVER TO UTRAN COMPLETE
Received on DCCH of the UTRAN cell.
Verify that the same CS-domain START-Value is indicated as in step 6.
11
SECURITY MODE COMMAND
Integrity protected with a different CS-domain START value than the indicated in step 6 is applied.
12
SS
Verify that no SECURITY MODE COMPLETE is sent by the MS for 5 sec.
13
SECURITY MODE COMMAND
Integrity protected with the CS-domain START value indicated in step 6 is applied.
14
SECURITY MODE COMPLETE
Verify that Integrity protection is applied using the CS-domain START value indicated in step 6.
Specific message contents
MEASUREMENT INFORMATION in Step 3
Same as in 60.1
CLASSMARK ENQUIRY message in Step 5
Information Element
Value/remark
Protocol Discriminator
RR management
Skip Indicator
‘0000’B
Message Type
Classmark Enquiry
Classmark Enquiry Mask
Classmark Enquiry Mask IEI
‘00010000’B
Length of Classmark Enquiry Mask contents
‘00000001’B
Classmark Enquiry Mask value part
‘10001000’B Note
Note CLASSMARK CHANGE message is not requested;
UTRAN CLASSMARK CHANGE message is requested;
CDMA2000 CLASSMARK CHANGE message is not requested
UTRAN CLASSMARK CHANGE message in step 6
Information Element
Value/remark
Protocol Discriminator
RR management
Skip Indicator
‘0000’B
Message Type
UTRAN ‘Classmark Change
UTRAN Classmark
Length of UTRAN Classmark
Length of INTER RAT HANDOVER INFO
UTRAN Classmark value part
INTER RAT HANDOVER INFO
InterRATHandoverInfo
RR management
PredefinedConfigurationStatusList
(Optional) Not checked
ue-SecurityInformation
Checked that the IE is present
start-CS
20 bits
…
Rest of message not checked
INTER SYSTEM TO UTRAN HANDOVER COMMAND message in Step 7
Same content as in 60.1
HANDOVER TO UTRAN COMPLETE message in step 10
Information Element
Value/remark
UL-DCCH-Message
IntegrityCheckInfo
Not defined
Message
handoverToUTRANComplete
HandoverToUTRANComplete
StartList
[0]
cn-DomainIdentity
cs –domain Checked that IE is present
start-Value
20 bits
[1]
cn-DomainIdentity
ps-domain Not checked
start-Value
20 bits
…
-
SECURITY MODE COMMAND message AM, in step 11
Information Element
Value/remark
Message Type
RRC transaction identifier
Arbitrarily selects an integer between 0 and 3
Integrity check info
- Message authentication code
Set to MAC-I value computed by the SS using a different START value for the CS domain from the indicated in the INTER RAT HANDOVER INFO. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
UE system specific security capability
- Inter-RAT UE security capability
- CHOICE system
GSM
- GSM security capability
The indicated algorithms must be the same as the algorithms supported by the UE as indicated in the IE " Mobile station classmark 2 " in the LOCATION UPDATING REQUEST message.
SECURITY MODE COMMAND message AM, in step 13
Information Element
Value/remark
Message Type
RRC transaction identifier
Arbitrarily selects an integer between 0 and 3
Integrity check info
- Message authentication code
Set to MAC-I value computed by the SS using the indicated START value for the CS domain from the INTER RAT HANDOVER INFO. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
UE system specific security capability
- Inter-RAT UE security capability
- CHOICE system
GSM
- GSM security capability
The indicated algorithms must be the same as the algorithms supported by the UE as indicated in the IE " Mobile station classmark 2 " in the LOCATION UPDATING REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.5 Test requirement
|
After step 14, the ongoing call shall continue on UTRAN cell with Integrity protection using the CS Security START value indicated in the UTRAN CLASSMARK CHANGE.
61-69 Void
70 Location Services
This sub clause contains test cases for Location Services (LCS).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.1 Default conditions during LCS tests
|
During signalling tests in sub clause 70, default conditions from sub clause 26 shall apply, if not otherwise stated within the test descriptions, with the following exception.
SYSTEM INFORMATION TYPE 3:
as default except:
Information Element
value/remark
SI 3 rest octets
- Early Classmark Sending Control
1 (perform early classmark sending)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.1.1 Default conditions during EOTD tests
|
For EOTD testing the serving cell shall provide a BCCH for the duration of the test to enable the MS to make the required measurements.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.1.2 Default conditions during A-GPS signalling tests
|
During A-GPS signalling tests defined in sub clause 70.7 to 70.9 the SS shall generate the six satellite signals and shall provide assistance data as defined in sub TS 51.010-7 subclasses 5.1.3 to 5.1.8. The levels of the simulated satellites shall all be at -125dBm +/- 6dB.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.1.3 Default conditions during A-GNSS signalling tests
|
During A-GNSS signalling tests defined in sub clause 70.12 to 70.15 the SS shall generate all the MS supported GNSS satellite signals defined in TS 51.010-7 sub clause 6.1.2 and shall provide assistance data, dependent on the MS capabilities, defined in TS 51.010-7 sub clauses 6.1.3 and 6.1.4. The levels of the simulated satellites shall all be at -125dBm +/- 6dB.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2 EOTD Network Induced Location Request
|
The test cases in this sub clause focus on Network Induced Location requests. Although normally associated with Emergency Calls, it is possible for an MS to receive a NI-LR at any time during idle or dedicated mode by a PLMN operator LCS client.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.1 LCS Network Induced Emergency Call on an SDCCH / idle, no IMSI for Mobiles supporting MS-Assisted EOTD
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.1.1 Conformance requirement
|
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel the first layer message sent by the MS on the assigned dedicated channel shall be a CM SERVICE REQUEST message specifying the correct IMEI and a non-available CKSN, with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received form the network, the MS shall send an EMERGENCY SETUP message.
5. On receiving the RRLP MEASURE POSITION REQUEST message the MS will perform position measurements and respond with an RRLP MEASURE POSITION RESPONSE message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
6. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.2.1, 4.5.1.5, 4.5.1.1, 5.2.1.1, and 5.2.1.6
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.1.2 Test Purpose
|
To verify when an emergency call is initiated by an MS which does not have a SIM fitted, the network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message and the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.1.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters.
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, no IMSI", no SIM inserted.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
An Emergency Call is initiated with the MS, with no SIM inserted in the MS.
Directly after sending EMERGENCY SETUP the MS receives a RR APPLICATION INFORMATION message containing an RRLP Measure Position Request.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing a RRLP Measure Position Response.
The emergency call is then established as normal with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum duration of the test
3 minutes.
Expected Test Sequence
Step
Direction
Message
Comments
1
MS
The appropriate "emergency called number" is entered.
2
MS -> SS
CHANNEL REQUEST
Establishment cause is emergency call establishment.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. The CM service type IE indicates "emergency call establishment". The mobile identity IE specifies the IMEI of the MS. The cipher key sequence number IE indicates "no key is available".
5
MS->SS
CLASSMARK CHANGE
"mobile station classmark 2" includes settings for ES_IND.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 .
6
SS -> MS
CM SERVICE ACCEPT
7
MS -> SS
EMERGENCY SETUP
8
SS-> MS
RR APPLICATION INFORMATION
(RRLP Measure Position Request)
9
MS -> SS
RR APPLICATION INFORMATION
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error)
10
SS -> MS
CALL PROCEEDING
11
SS -> MS
ALERTING
12
SS -> MS
ASSIGNMENT COMMAND
13
MS -> SS
ASSIGNMENT COMPLETE
14
SS -> MS
CONNECT
15
MS -> SS
CONNECT ACKNOWLEDGE
The MS indicates that the TCH is through connected in both directions.
16
SS -> MS
DISCONNECT
17
MS -> SS
RELEASE
18
SS -> MS
RELEASE COMPLETE
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,A0,1e) Followed by EOTD Measure Assist Data
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
methodType
msAssisted
0
positionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
useMultipleSets
Enumerated
oneSet
EOTDMeasure AssistData
SEQUENCE
Values of the data within the element is described in tables 70.2.1 – 1 and 70.2.1 - 2
Table 70.2.1-1: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name
Value
Comments
BCCH Carrier
Range 0-1023
ARFCN of Serving BCCH
BSIC
Range 0 to 65
BSIC of Serving BCCH
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Table 70.2.1-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name
Value
Comments
Number of Neighbors
2
E-OTD Neighbor Present
2
BSIC
Range 0 to 63
BSIC of neighbor BCCH
Multiframe Offset
Range 0-51
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3.
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Rough RTD
Range 0-1250
Set to rough RTD value for the specific test configuration
RRLP Measure Position Response
Information element
Type
Value/remark
ASN.1 encoded
-
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
EITHER
Eotd MeasureInfo
SEQUENCE
Any value for these parameters is acceptable.
OR
LocationInfoError
SEQUENCE
Any error value is acceptable
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.3 Network Induced Location Request Emergency Call on an SDCCH for MS-Assisted EOTD Mobiles
|
For Mobiles supporting speech, emergency call establishment will be initiated by the MS whether location updating has been successful or not and whether a SIM is inserted into the MS or not.
A Network Induced Location Request could occur at any point during emergency call setup (Ref 3GPP TS 03.71 sub clause 7.6.4.1). This could occur during an emergency setup before connection to a traffic channel.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.3.1 Conformance requirements:
|
The following requirements apply for this test:
1. With the MS in the "idle, updated" state, the user shall initiate an emergency after the number 112 (for GSM 900 and 1800 MS), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 MS in Mexico) has been entered by the user. The MS shall send a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel, the MS shall send a CM SERVICE REQUEST message specifying the correct CKSN and TMSI with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
5. On receiving the RRLP Measure Position Request message the MS will perform position measurements and respond with an RRLP Measure Position Response message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
6. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call the MS shall indicate that the TCH is through connected in both directions.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10, 9.1.11, 10.5.1.7.
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.1.3, 5.2.1, 4.5.1.1, 4.5.1.5, 5.2.1.1, 5.2.1.6, 9.2.9.
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.3.3 Test Purpose
|
To verify when an emergency call is initiated by the MS, the network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message and the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.3.4 Method of Test
|
Initial Conditions:
System Simulator:
Serving cell: Default parameters
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
An Emergency Call is initiated with the MS. SIM card is included in the MS.
Directly after sending EMERGENCY SETUP the MS receives a RR APPLICATION INFORMATION message containing an RRLP Measure Position Request.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing a RRLP Measure Position Response.
The emergency call is then established as normal with late assignment. Having reached the active state, the call is cleared by the SS.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The appropriate "emergency call number" is entered.
2
MS -> SS
CHANNEL REQUEST
Establishment cause is emergency call establishment.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. The CM service type IE indicates "emergency call establishment".
5
MS->SS
CLASSMARK CHANGE
"mobile station classmark 2" includes settings for ES_IND.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 .
6
SS -> MS
CM SERVICE ACCEPT
7
MS -> SS
EMERGENCY SETUP
8
SS-> MS
RR APPLICATION INFORMATION
(RRLP Measure Position Request)
9
MS -> SS
RR APPLICATION INFORMATION
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error)
10
SS -> MS
CALL PROCEEDING
11
SS -> MS
ALERTING
12
SS -> MS
ASSIGNMENT COMMAND
13
MS -> SS
ASSIGNMENT COMPLETE
14
SS -> MS
CONNECT
15
MS -> SS
CONNECT ACKNOWLEDGE
The MS indicates that the TCH is through connected in both directions.
16
SS -> MS
DISCONNECT
17
MS -> SS
RELEASE
18
SS -> MS
RELEASE COMPLETE
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,A0,1e) Followed by EOTD Measure Assist Data
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
methodType
msAssisted
0
positionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
useMultipleSets
Enumerated
oneSet
EotdMeasureAssistData
SEQUENCE
Values of the data within the element as described in Tables 70.2.3 – 1 and 70.2.3 – 2
Table 70.2.3-2: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name
Value
Comments
BCCH Carrier
Range 0-1023
ARFCN of Serving BCCH
BSIC
Range 0 to 65
BSIC of Serving BCCH
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Table 70.2.3-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name
Value
Comments
Number of Neighbors
2
E-OTD Neighbor Present
2
BSIC
Range 0 to 63
BSIC of neighbor BCCH
Multiframe Offset
Range 0-51
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3.
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Rough RTD
Range 0-1250
Set to rough RTD value for the specific test configuration
RRLP Measure Position Response
Information element
Type
Value/remark
ASN.1 encoded
-
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
EITHER
Eotd MeasureInfo
SEQUENCE
Any value for these parameters is acceptable.
OR
LocationInfoError
SEQUENCE
Any error value is acceptable
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.4 Emergency Call NI-LR while Voice is Through Connected for Mobiles supporting MS-Assisted EOTD
|
A Network Induced Location Request could occur at any point during emergency call setup (Ref 3GPP TS 03.71 sub clause 7.6.4.1). In this case the voice call is established before the MS receives the location request.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.4.1 Conformance requirements:
|
The following requirements apply for this test:
1. With the MS in the "idle, updated" state, the user shall initiate an emergency call after the number 112 (GSM 900 and 1800 MSs), or 911 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 in the USA), or 08 (for GSM 710, GSM 750, T_GSM 810, GSM 850, PCS 1 900 in Mexico) has been entered by the user. The MS shall end a CHANNEL REQUEST message with correct establishment cause ("emergency call").
2. After assignment of a dedicated channel, the MS shall send a CM SERVICE REQUEST message specifying the correct CKSN and TMSI with CM Service Type "emergency call establishment". The ES_IND bit in the Mobile Station Classmark 2 information element shall be set to "Controlled Early Classmark Sending is implemented".
3. After sending the CM SERVICE REQUEST message the MS shall send a CLASSMARK CHANGE message. The "Mobile Station Classmark 3" information element shall correctly specify the positioning methods supported by the MS.
4. After the CM SERVICE ACCEPT message is received from the network, the MS shall send an EMERGENCY SETUP message.
5. After receipt of a CONNECT ACKNOWLEDGE message during correct establishment of the emergency call, the MS shall indicate that the TCH is through connected in both directions.
6. On receiving the RRLP Measure Position Request message the MS will perform position measurements and respond with an RRLP Measure Position Response message. The RRLP Measure Position Response message shall contain either an EOTD Measurement Information element or a Location Information Error element.
References
3GPP TS 04.08 / 3GPP TS 44.018 sub clauses 3.3.1.1, 3.4.10, 9.1.11, 10.5.1.7
3GPP TS 04.08 / 3GPP TS 24.008 sub clauses 5.1.3, 5.2.1, 4.5.1.5, 4.5.1.1, 5.2.1.1, 5.2.1.6, 9.2.9
3GPP TS 02.30 clause 4.
3GPP TS 04.31 Annex A sub clause 2.2.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.4.2 Test Purpose
|
To verify when a network instigates the LCS positioning procedure by sending RRLP (Measure Position Request) message, after a traffic channel has been established during an emergency call, the mobile responds with RRLP (Measure Position Response) containing E-OTD measurement values.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.2.4.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters.
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
An Emergency Call is initiated by the MS. SIM card is present in the MS.
The emergency call is established with a late assignment.
After receiving the CONNECT ACKNOWLEDGE message from the MS, the SS sends an RR APPLICATION INFORMATION message containing an RRLP Measure Position Request on the FACCH.
The MS then performs positioning measurements and responds with a RR APPLICATION INFORMATION message containing an RRLP Measure Position Response.
The call is then cleared by the SS.
Maximum duration of the test:
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The appropriate Emergency Called number is entered.
2
MS -> SS
CHANNEL REQUEST
Establishment cause is emergency call establishment.
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. The CM service type IE indicates "emergency call establishment".
5
MS->SS
CLASSMARK CHANGE
"mobile station classmark 2" includes settings for ES_IND.
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7 .
6
SS -> MS
CM SERVICE ACCEPT
7
MS -> SS
EMERGENCY SETUP
8
SS -> MS
CALL PROCEEDING
9
SS -> MS
ALERTING
10
SS -> MS
ASSIGNMENT COMMAND
11
MS -> SS
ASSIGNMENT COMPLETE
12
SS -> MS
CONNECT
13
MS -> SS
CONNECT ACKNOWLEDGE
The MS indicates that the TCH is through connected in both directions.
14
SS-> MS
RR APPLICATION INFORMATION
(RRLP Measure Position Request)
15
MS -> SS
RR APPLICATION INFORMATION
(RRLP Measure Position Response indicating either EOTD Measurement Information or a Location Information Error)
16
SS -> MS
DISCONNECT
17
MS -> SS
RELEASE
18
SS -> MS
RELEASE COMPLETE
19
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,A0,1e) Followed by EOTD Measure Assist Data
ReferenceNumber
Integer,0 to 7
1
Component
msrPositionReq
1
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
UseMultipleSets
Enumerated
oneSet
EOTD Measurement Assistance
SEQUENCE
Values of the data within the element as described in Tables 70.2.4 - 1 and 70.2.4 – 2
Table 70.2.4-3: RRLP Measure Position Request Field Values,
E-OTD Reference BTS for Assistance Data Element
Field Name
Value
Comments
BCCH Carrier
Range 0-1023
ARFCN of Serving BCCH
BSIC
Range 0 to 65
BSIC of Serving BCCH
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Table 70.2.4-2: RRLP Measure Position Request Field Values,
E-OTD Measurement Assistance Data for System Information List Element
Field Name
Value
Comments
Number of Neighbors
2
E-OTD Neighbor Present
2
BSIC
Range 0 to 63
BSIC of neighbor BCCH
Multiframe Offset
Range 0-51
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, Section A.2.2.3.
Time Slot Scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slots 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Rough RTD
Range 0-1250
Set to rough RTD value for the specific test configuration
RRLP Measure Position Response
Information element
Type
Value/remark
ASN.1 encoded
-
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
EITHER
Eotd MeasureInfo
SEQUENCE
Any value for these parameters is acceptable.
OR
LocationInfoError
SEQUENCE
Any error value is acceptable
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3 Mobile Originating Location Request
|
The test cases in this sub clause focus on Mobile Originating Location Request. A MO_LR could occur by a MS to request the network to start location procedure, which is used for either its own location, location assistance data or deciphering keys for broadcast assistance data message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1 MO_LR Basic Self Location Request
|
Basic Self Location Request is only applicable for requesting its own location by using MS Assisted E-OTD positioning..
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.1 MO_LR Basic Self Location Request In Idle Mode (Normal Case)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.1.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.
Test References
3GPP TS 03.71, sub clause 7.6.6.
3GPP TS 04.30 sub clause 5.1.1.
3GPP TS 04.80 sub clauses 2.4, 2.5 and 4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.1.2 Test Purpose
|
Verifies that a MS sends a correct LCS-MOLR Invoke message with the component MO_LR TYPE set to LocationEstimate and LCS_QoS value on the initiation of MOLR. On receipt of a RRLP Measure position request from SS to start the measurement, MS shall send back RRLP Measure Position Response to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.1.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: at least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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 LCS-MOLR Invoke. The SS sends RRLP Request to start the measurement. Once the measurement is done, RRLP response is sent back to SS with the measurement data. The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (Basic Self Location Request)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
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
14
SS -> MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate)
15
MS -> SS
RELEASE COMPLETE
Terminates the session
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocationEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
methodType
msAssisted
0
positionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
useMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.2 MO_LR Basic Self Location Request In Dedicated Mode (Normal case)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.2.1 Conformance Requirement:
|
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.
Test References:
3GPP TS 03.71 sub clause 7.6.6
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.80 sub clauses 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.2.2 Test Purpose
|
Verifies that a MS sends a correct LCS-MOLR Invoke message on already established speech call related SACCH with the component MO_LR TYPE sets to LocationEstimate and LCS_QoS value on the initiation of MO_LR. On receipt of a RRLP Measure position request from SS to start the measurement, MS shall send back RRLP Measure Position Response to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.1.2.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: Default parameters.
Neighbor Cells: 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow
the MS to perform the required timing measurements.
Mobile Station:
The MS has valid TMSI and CKSN.
The MS is brought into the state U10 by using table 26.8.1.2/3.
Specific PICS statements
-
PIXIT statements
-
Test Procedure:
A MOLR procedure as call independent supplementary services is initiated from the MS on the existing SACCH channel. After received CM SERVICE ACCEPT message, MS sends a REGISTER message with Facility IE containing a component set to a LCS-MOLR Invoke. The SS sends RRLP Request to start the measurement. Once the measurement is done, RRLP Response is sent back to SS with the measurement data. The SS returns location estimate to MS through LCS-MOLR Return Result. The MS terminates the dialogue by sending RELEASE COMPLETE message.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure ((Basic Self Location Request)
2
MS -> SS
CM SERVICE REQUEST
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
3
(optional step)
MS -> SS
CLASSMARK CHANGE
This message is optional does not have to be sent by the MS.
4
SS -> MS
CM SERVICE ACCEPT
5
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
MOLR-Type set to LocationEstimate
6
SS->MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
7
MS->SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
8
SS->MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate
9
MS->SS
RELEASE COMPLETE
Terminates the session
10
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocationEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request),
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data),
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
methodType
msAssisted
0
positionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
useMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.2 MO_LR Transfer to 3rd Party
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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). 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.
Test References
3GPP TS 03.71, sub clause 7.6.6,
3GPP TS 04.030 sub clause 5.1.1,
3GPP TS 04.80 sub clauses 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.2.2 Test Purpose
|
Verifies that a MS sends a correct LCS-MOLR Invoke message with the component MO_LR TYPE set to LocationEstimate, LCS_QoS value, LCS-ClientExternalID and MLC_Number (if available) on the initiation of MOLR. On receipt of a RRLP Measure position request from SS to start the measurement, MS shall send back RRLP Measure Position Response to SS after finishing the measurement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.2.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: at least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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 LCS-MOLR Invoke. The SS sends RRLP Request to start the measurement. Once the measurement is done, RRLP response is sent back to SS with the measurement data. The SS may then transfer the location information to the internal or external LCS client.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (Transfer to 3rd Party)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
MOLR-Type set to LocationEstimate
LCSClientExternalID present
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
13
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
14
SS
SS may return the location estimate result to the LCS client as MAP subscriber location report
15
SS -> MS
RELEASE COMPLETE
Confirmation of successful transfer to 3rd Party
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocationEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
referenceNumber
Integer,0 to 7
1
component
msrPositionReq
1
methodType
msAssisted
0
positionMethod
Enumerated
eotd
MeasureResponseTime
Integer,0 to 7
7
useMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.3 MO_LR Autonomous Location
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.3.1 Conformance Requirement
|
The MS sends a DTAP LCS MOLR invoke to VMSC. If the MS is requesting location assistance data, the message specifies the type of assistance data and the positioning method for which the assistance data applies.
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 AssistanceData, Location-Method set to MS-AssistedEOTD, LCS QoS value and other optional field if it is needed.
The MS acknowledges the reception of each assistance data component to network with a RRLP ASSISTANCE DATA Ack before the next Assistance Data component is received.
References
3GPP TS 03.71 sub clause 7.6.6, 10.4, 10.5
3GPP TS 04.30 sub clause 5.1.1
3GPP TS 04.31 sub clause 2.3
3GPP TS 04.80 sub clauses 2.4, 2.5 and 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.3.2 Test Purpose
|
Verifies that a MS sends a correct LCS-MOLR Invoke message with the component MOLR Type set to Assistance Data, Location-Method sets to MS-Assisted EOTD, and LCS-QoS on the initiation of MO_LR. The MS shall acknowledge the reception of each assistance data component.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.3.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Specific PICS statements
-
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 LCS-MOLR Invoke. The SS determines the exact location assistance data to transfer according to the type of data specified by the MS, the MS location capabilities and the current cell ID and sends RRLP Assistance Data to MS. The MS acknowledges each assistance data components by sending RRLP Assistance Data Ack.
Maximum duration of the test:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure( assistance data )
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
MOLR-Type set to AssistanceData
LocationMethod set to MSAssistedEOTD
12
SS -> MS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA
13
MS -> SS
RR APPLICATION INFORMATION
RRLP ASSISTANCE DATA ACK.
14
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(SS->MS) RRLP (Assistance Data),
(MS->SS) RRLP (Assistance Data Ack.),
(MS->SS) RRLP (Protocol Error),
RRLP Assistance Data
Information element
Type
Value/remark
ASN.1 encoded
-
ReferenceNumber
Integer 0 to 7
1
Component
assistanceData
referenceAssistanceData
ReferenceAssistData
See below
MsrAssistData
MsrAssistData
See below
systemInfoAssistData
SystemInfoAssistData
See below
moreAssDataToBeSent
Enumerated
0
RRLP Assistance Data Field Values: Reference Assistance Data
Field Name
Value
Comments
BCCH Carrier
Range 0 - 1023
ARFCN of Serving BCCH
BSIC
Range 0 - 63
BSIC of Serving BCCH
Time Slot Scheme
Either o or 1, as applicable
0=All time slot 156.25 bits long
1=Time slot 0 and 4 are 157 bits long, all other time slots are 156 bits long
BTS Position
None
Not applicable
RRLP Assistance Data Field Values: Measure Assistance Data
Field Name
Value
Comments
Number of Neighbors
1
BCCH Carrier
Range 0 - 1023
ARFCN of neighbour BCCH
BSIC
Range 0 - 63
BSIC of neighbour BCCH
Multiframe Offset
Range 0 - 51
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, section A.2.2.3
Time Slot scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slot 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Rough RTD
Range 0 - 1250
Set to rough RTD value for the specific test configuration
Expected OTD
None
Not Applicable
Uncertainty of Expected OTD
None
Not Applicable
Fine RTD
None
Not Applicable
Relative North
None
Not Applicable
Relative East
None
Not Applicable
RRLP Assistance Data Field Values: System Info Assistance Data
Field Name
Value
Comments
Number of Neighbours
1
E-OTD Neighbour Present
1
BSIC
Range 0 - 63
BSIC of neighbour BCCH
Multiframe Offset
Range 0 - 51
The value of this field is specific to the test configuration, and shall be calculated according to 3GPP TS 04.31, Annex A, section A.2.2.3
Time Slot scheme
Either 0 or 1, as applicable
0=All time slots 156.25 bits long
1=Time slot 0 and 4 are 157 bits long, all other time slots are 156 bits long.
Rough RTD
Range 0 - 1250
Set to rough RTD value for the specific test configuration
Expected OTD
None
Not Applicable
Uncertainty of Expected OTD
None
Not Applicable
Fine RTD
None
Not Applicable
Relative North
None
Not Applicable
Relative East
None
Not Applicable
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4 MO_LR Positioning Measurement
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.1 MO_LR Positioning Measurement / Protocol Error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
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 sub clause 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.1.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: At least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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. Once the measurement is done, RRLP MEASURE POSITION RESPONSE is sent back to SS with the measurement data. 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
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates " call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
(with missing information element)
13
MS->SS
RR APPLICATION INFORMATION
RRLP PROTOCOL ERROR
14
SS->MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
13
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(otd_measureInfo)
14
SS -> MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate)
15
MS -> SS
RELEASE COMPLETE
Terminates the session
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocationEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request (Step 12)
Information element
Type
Value/remark
ASN.1 encoded
-
( 00100000, 00000000, 000111)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
EOTD
MeasureResponseTime
Integer 0 to 7
7
RRLP Measure Position Request (Step 14)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.2 MO_LR Positioning Measurement /Location Error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.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.
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 sub clause 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.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 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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.2.3 Method of Test
|
Initial Conditions:
System Simulator:
Serving Cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: At least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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. The MS sends RRLP MEASURE POSITION RESPONSE to network 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. Once the measurement is done, RRLP MEASURE POSITION RESPONSE is sent back to SS with the measurement data. 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:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates " call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
(Request method not supported)
13
MS->SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
( location error)
14
SS->MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST
13
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE
(otd_measureInfo)
14
SS -> MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate)
15
MS -> SS
RELEASE COMPLETE
Terminates the session
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocatibonEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request (Step 12)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,3e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
GPS
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
RRLP Measure Position Request (Step 14)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.3 MO_LR Positioning Measurement / Multiple RRLP REQUEST with same Reference Number
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
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 sub clause 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.3.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: at least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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 to start the measurement. Before the current positioning measurement finishes, the SS sends the second RRLP MEASURE POSITION REQUEST with the same REFERENCE NUMBER as the first one. 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. 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:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates " call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 1
13
MS
MS is performing the measurement
14
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 2
(with same reference number as in Request 1)
15
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE 1
(otd-measureInfo - msAssisted)
16
SS -> MS
FACILITY
LCS MO-LR RETURN RESULT (locationEstimate)
17
MS -> SS
RELEASE COMPLETE
Terminates the session
18
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocatibonEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request (Step 12)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
RRLP Measure Position Request (Step 14)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,3e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msBased
1
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.4 MO_LR Positioning Measurement / Multiple RRLP REQUEST with different Reference Number
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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 sub clause 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.4.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: at least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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 to start the measurement. Before the current positioning measurement finishes, the MS receives the second RRLP MEASURE POSITION REQUEST with a different REFERENCE NUMBER as in the first one. 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. 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:
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates " call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 1
13
MS
MS is performing the measurement
14
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 2
(with different reference number as in Request 1)
13
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE 2
(otd-measureInfo)
Check reference number is 2
14
SS -> MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate)
15
MS -> SS
RELEASE COMPLETE
Terminates the session
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocatibonEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request 1 (Step 12)
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
RRLP Measure Position Request 2 (Step 14)
Information element
Type
Value/remark
ASN.1 encoded
-
(40,00,1e)
ReferenceNumber
Integer 0 to 7
2
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.5 MO_LR Positioning Measurement / RR Management Commands
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
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 sub clauses 2.4, 2.5 & 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.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.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.3.4.5.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Neighbor Cells: at least 2 neighbor cells are used with a minimum configuration of a BCCH. This is to allow the MS to perform the required timing measurements.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements
-
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 to start the measurement. Before the current positioning measurement finishes, the MS receives 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 MS sends RRLP MEASURE POSITION RESPONSE to SS with the measurement data finishing the measurement according to the newly received RRLP MEASUREMENT POSITION REQUEST. 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
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
Initiate MOLR Procedure (location estimate)
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates " call independent supplementary Services”".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS -> MS
CM SERVICE ACCEPT
11
MS -> SS
REGISTER
Call Independent SS containing Facility IE
With the component of Invoke message set to LCS-MOLR
12
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 1
13
MS
MS is performing the measurement
14
SS -> MS
RR MANAGEMENT COMMAND
15
MS -> SS
RR MANAGEMENT COMPLETE
MS terminates the measurement procedure and act on the RR management command
16
SS -> MS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION REQUEST 2
17
MS -> SS
RR APPLICATION INFORMATION
RRLP MEASURE POSITION RESPONSE 2
(otd-measureInfo)
18
SS -> MS
FACILITY
LCS MO-LR RETURE RESULT (locationEstimate)
19
MS -> SS
RELEASE COMPLETE
Terminates the session
20
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
FACILITY
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
FACILITY (0x11 1010 )
Facility
Return Result = lcs-MOLR LocatibonEstimate
LCS-MOLRRes ->locationEstimate
RR_APPLICATION_INFORMATION
Information element
Value/remark
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Message Type
Application Information Message type
APDU ID
APDU ID -> RRLP => 0000
APDU Flags
Bit1=0 -> Last or only segment
Bit2=0 -> First or only segment
Bit3=0 -> Command or Final Response
Bit4=spare
APDU Data
2-N Byte ASN.1 Coded
(SS->MS) RRLP (Measure Position Request) ,
(MS->SS) RRLP (Measure Position Response),
(MS->SS) RRLP (Protocol Error),
(SS->MS) RRLP (Assistance Data) ,
(MS->SS) RRLP (Assistance Data Ack.),
RRLP Measure Position Request
Information element
Type
Value/remark
ASN.1 encoded
-
(20,00,1e)
ReferenceNumber
Integer 0 to 7
1
Component
msrPositionReq
MethodType
msAssisted
0
PositionMethod
Enumerated
eotd
MeasureResponseTime
Integer 0 to 7
7
UseMultipleSets
Enumerated
oneSet
RR Management Command (Classmark Enquiry)
Information element
Value/remark
Encoded
(06 13)
Protocol Discriminator
RR Management Protocol (0110)
Skip Indicator
Classmark Enquiry Message Type
0001 0011
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4 Mobile Terminated Location Request for Mobiles supporting MS-Assisted EOTD
|
The test cases in this sub clause focus on Mobile Terminated Location Request. A MT-LR occurs when an external LCS client requests the position of an MS by sending the SS REGISTER message. This may be sent to request verification for a particular MT-LR or simply to notify the user about an MT-LR that has already been authorized.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.1 MT-LR Location Notification for MS-Assisted EOTD
|
Location notification takes place to inform the MS user that a particular LCS client is requesting their position without seeking the user's permission.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.1.1 Conformance requirements:
|
The following requirements apply for this test:
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyLocationAllowed. The MS shall notify the MS user of the location request using the method defined in the manufacturers' specification.
2. The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Test References
3GPP TS 03.71, sub clause 7.6.1,
3GPP TS 04.30, sub clause 4.1.1,
3GPP TS 04.80, sub clauses 2.4 and 2.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.1.2 Test Purpose
|
Verifies that when the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyLocationAllowed, the MS displays information about the LCS client correctly (as defined by the individual manufacturer) and sends a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.1.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message containing a Facility IE containing a DTAP LCS Location Notification Invoke message set to notifyLocationAllowed. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed as defined by the Manufacturer. The MS then responds with a RELEASE COMPLETE message containing a LocationNotification return to terminate the dialogue.
Maximum duration of the test:
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
Sent on the correct paging subchannel
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "answer to paging".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS
SS starts ciphering.
11
SS -> MS
REGISTER
Call Independent SS containing Facility IE
Location Notification Invoke message set to notifyLocationAllowed
12
MS -> SS
RELEASE COMPLETE
Contains a LocationNotification return result to terminate the dialogue
13
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
PAGING RESPONSE
Information element
Value/remark
Protocol Discriminator
RR management
Ciphering Key Sequence number
- Key Sequence
Key sequence number previously allocated to MS, or "111" if no key is available
Mobile station Classmark 2
- ES IND
“Controlled Early Classmark Sending” option is implemented in the MS.
CM3
The MS Supports options that are indicated in classmark 3 IE in the Classmark Change message
Mobile Identity
- odd/even
Even
- Type of identity
TMSI
- Identity digits
TMSI previously allocated to MS
REGISTER
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
REGISTER (0x11 1011)
Facility
Invoke = lcs-LocationNotification
LocationNotificationArg
notificationType -> notifyLocationAllowed,
locationType -> current Location ,
lcsClientExternalID -> externalAddress
lcsClientName ->dataCodingScheme
nameString
RELEASE COMPLETE
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
XX
Message type
RELEASE COMPLETE (0x10 1010)
Facility
Return result = lcs-LocationNotification
verificationResponse -> permissionGranted
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2 MT-LR Privacy Options for Mobiles supporting MS-Assisted EOTD
|
Privacy options are used in conjunction with the MS subscription profile on the VLR. They give the MS user the option to grant or withhold permission for individual location requests as they occur.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.1 MT-LR Privacy Options/ Verification – Location Allowed If No Response for mobiles supporting MS-Assisted EOTD
|
The case occurs when the target MS subscription profile on the VLR is set to location allowed if no response is sent. This is the default option if the VMSC does not receive verification from the target MS within a predetermined time.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.1.1 Conformance requirements
|
The following requirements apply for this test:
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationAllowedIfNoResponse. The MS a) notifies the user of the request and b) indicates the default is location allowed if no response is received within a predetermined period, while c) providing the opportunity to accept or deny the request by the method defined in the manufacturer's specification.
2.
Option 1:
The user accepts the location request using the method specified by the manufacturer.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user denies the location request using the method defined by the manufacturer.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user takes no action and the verification process times-out.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Test References
For conformance requirement 1:
3GPP TS 03.71, sub clause 7.6.1.
3GPP TS 24.030 sub clause 4.1.1.
3GPP TS 24.080 sub clause 2.4, 2.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.1.2 Test Purpose
|
Verifies that when the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationAllowedIfNoResponse, the MS displays information about the LCS client correctly and indicates that the default response is location allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.1.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure:
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, as defined by the Manufacturer. The MS also indicates that location will be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request by the method defined by the manufacturer. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request by the method defined by the manufacturer. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Maximum duration of the test:
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
Sent on the correct paging subchannel
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "answer to paging".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND, CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support for LCS VA Capability.
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
SS
SS starts ciphering.
11
SS -> MS
REGISTER
Call Independent SS containing Facility IE
LCS Location Notification Invoke set to notifyAndVerify-LocationAllowedIfNoResponse
12A
k=1
MS
MS displays location request and info about LCS client. The MS accepts location request.
13A
k=1
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionGranted.
12B
k=2
MS
MS displays location request and info about LCS client. The MS rejects location request.
13B
k=2
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionDenied
12C
k=3
MS
MS displays location request and info about LCS client. The MS does not reply
13C
k=3
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionGranted
14
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
PAGING RESPONSE
Information element
Value/remark
Protocol Discriminator
RR management
Ciphering Key Sequence number
- Key Sequence
Key sequence number previously allocated to MS, or "111" if no key is available
Mobile station Classmark 2
- ES IND
“Controlled Early Classmark Sending” option is implemented in the MS.
CM3
The MS Supports options that are indicated in classmark 3 IE in the Classmark Change message.
Mobile Identity
- odd/even
Even
- Type of identity
TMSI
- Identity digits
TMSI previously allocated to MS
REGISTER
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
Xx
Message type
REGISTER (0x11 1011)
Facility
invoke = lcs-LocationNotification
locationNotificationArg
notificationType ->notifyAndVerify-LocationAllowedIfNoResponse,
locationType -> current Location,
lcsClientExternalID -> externalAddress
lcsClientName ->dataCodingScheme
nameString
RELEASE COMPLETE (options 1 and 3)
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
Xx
Message type
RELEASE COMPLETE (0x10 1010)
Facility
return result = lcs-LocationNotification
locationNotificationRes
verificationResponse -> permissionGranted
RELEASE COMPLETE (option 2)
Information element
Value/remark
Protocol Discriminator
Call Independent SS message (1011)
Transaction identifier
Xx
Message type
RELEASE COMPLETE (0x10 1010)
Facility
return result = lcs-LocationNotification
locationNotificationRes
verificationResponse -> permissionDenied
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.2 MT-LR Privacy Options/ Verification – Location Not Allowed If No Response for Mobiles supporting MS-Assisted EOTD
|
This case occurs when the target MS subscription profile on the VLR is set to location not allowed if no response is sent. This is the default option if the VMSC does not receive verification from the target MS within a predetermined time.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.2.1 Conformance requirements:
|
The following requirements apply for this test:
1. On receipt of a REGISTER message containing the LCS Notification Invoke component with notificationType set to notifyAndVerify-LocationAllowedIfNoResponse. The MS a) notifies the user of the request and b) indicates that the default is location not allowed if no response is received within a predetermined period, while c) providing the opportunity to accept or deny the request by the method defined in the manufacturer's specification.
2.
Option 1:
The user accepts the location request using the method specified by the manufacturer.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user denies the location request using the method defined by the manufacturer.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user takes no action and the verification process times-out.
The MS shall terminate the dialogue by sending a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Test References
For conformance requirement 1:
3GPP TS 03.71, sub clause 7.6.1.
3GPP TS 24.030 sub clause 4.1.1.
3GPP TS 24.080 sub clause 2.4, 2.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.2.2 Test Purpose
|
Verifies that when the MS receives a REGISTER message, containing a LCS Location Notification Invoke component set to notifyAndVerify-LocationNotAllowedIfNoResponse, the MS displays information about the LCS client correctly and indicates that the default response is location not allowed if no response is sent. Gives the user the option to accept or reject the request and sends a RELEASE COMPLETE message containing a LocationNotification return result with the verificationResponse set to permissionDenied or permissionGranted as appropriate.
Specific PICS statements
-
PIXIT statements
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.4.2.2.3 Method of Test
|
Initial Conditions
System Simulator:
Serving cell: Default parameters, in SYSTEM INFORMATION TYPE 3 (SI3 Rest Octet) the early classmark sending control is implemented in the SS.
Mobile Station:
The MS is in MM-state "idle, updated" with valued TMSI and CKSN.
Test Procedure
The MS is paged with a PAGING REQUEST TYPE 1 message. After sending the CIPHERING MODE COMPLETE message the MS receives an SS REGISTER message with a Facility IE containing a LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse. The LCS Client Name contained in the USSD text string of the lcs-LocationNotification shall be displayed with the option to accept or deny the request, as defined by the Manufacturer. The MS also indicates that location will not be allowed if a response is not received within a predetermined time.
Option 1:
The user then accepts the location request by the method defined by the manufacturer. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionGranted.
Option 2:
The user then denies the location request by the method defined by the manufacturer. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Option 3:
The user ignores the location request by taking no action, allowing the verification process timer to time-out. The MS responds with a RELEASE COMPLETE message containing a LocationNotification return result with verificationResponse set to permissionDenied.
Maximum duration of the test:
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
Sent on the correct paging subchannel
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "answer to paging".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM
"Mobile identity" IE contains the IMSI.
"mobile station classmark 2" including settings for ES IND and CM3 supported.
5
MS -> SS
CLASSMARK CHANGE
"mobile station classmark 3" includes settings for Positioning according to 3GPP TS 24.008, table 10.5.1.7. This includes support of LCS VA Capability.
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
SS
SS starts ciphering.
11
SS -> MS
REGISTER
Call Independent SS containing Facility IE
LCS Location Notification Invoke set to notifyAndVerify-LocationNotAllowedIfNoResponse
12
MS -> SS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionGranted or permissionDenied as appropriate.
12A
k=1
MS
MS displays location request and info about LCS client. The MS accepts location request.
13A
k=1
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionGranted.
12B
k=2
MS
MS displays location request and info about LCS client. The MS rejects location request.
13B
k=2
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionDenied
12C
k=3
MS
MS displays location request and info about LCS client. The MS does not reply
13C
k=3
SS -> MS
RELEASE COMPLETE
Containing a LocationNotification return result with verificationResponse set to permissionGranted
14
SS->MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents
PAGING RESPONSE
Information element
Value/remark
Protocol Discriminator
RR management
Ciphering Key Sequence number
- Key Sequence
Key sequence number previously allocated to MS, or "111" if no key is available
Mobile station Classmark 2
- ES IND
“Controlled Early Classmark Sending” option is implemented in the MS.
CM3
The MS Supports options that are indicated in classmark 3 IE in the Classmark Change message.
Mobile Identity
- odd/even
Even
- Type of identity
TMSI
- Identity digits
TMSI previously allocated to MS
REGISTER
Information element
Value/remark
Protocol Discriminator
Call independent SS message (1011)
Transaction identifier
Xx
Message type
REGISTER (0x11 1011)
Facility
invoke = lcs-LocationNotification
locationNotificationArg
notificationType ->notifyAndVerify-LocationNotAllowedIfNoResponse,
nocationType -> current Location,
lcsClientExternalID -> externalAddress
lcsClientName ->dataCodingScheme
nameString
RELEASE COMPLETE (option 1)
Information element
Value/remark
Protocol Discriminator
Call independent SS message (1011)
Transaction identifier
Xx
Message type
RELEASE COMPLETE (0x10 1010)
Facility
return result = lcs-LocationNotification
locationNotificationRes
verificationResponse -> permissionGranted
RELEASE COMPLETE (options 2 and 3)
Information element
Value/remark
Protocol Discriminator
Call independent SS message (1011)
Transaction identifier
Xx
Message type
RELEASE COMPLETE (0x10 1010)
Facility
return result = lcs-LocationNotification
locationNotificationRes
verificationResponse -> permissionDenied
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.5 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
70.6 E-OTD Timing Measurement Accuracy
|
Scope of Tests
This test procedure plan is intended verify the operation of Enhanced Observed Timing Difference (E-OTD) measurement functionality from an E-OTD capable GSM Mobile Station (MS).
The scope of this test plan is limited to verification of the MS physical layer against 3GPP TS 05.05, Release 1999, version 8.7.1, annex I. Specifically, this includes validation of MS observed timing measurement accuracy only.
The recommended measurement test environment is shown in the present document annex 6.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.