hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.2 Receipt of an I frame in the timer recovery state
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.2.1 Test purpose
|
To test that the MS is able to respond to I frames whilst in the timer recovery state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.2.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS sends an Identity Request message asking for IMEI to the MS.
The MS shall respond with a RR frame though this may be incorporated with the Identity Response I frame.
The SS does not respond to the I frame.
The MS shall wait for expiry of timer T200 and then repeat the I frame but with the P bit set to 1.
The SS then sends a valid Identity Request I frame asking for IMEI which does not acknowledge receipt of the I frame from the MS.
On the FACCH the MS may send an RR frame acknowledging the I frame.
The MS shall repeat the I frame, this frame will acknowledge receipt of the second I frame from the SS.
The SS then acknowledges receipt of the MS I frame by sending a RR frame.
The MS shall send the next I frame. The SS acknowledges this I frame.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
2 RR (SAPI, R, M, L, N(R), F) >
May be incorporated
3 I (SAPI, C, P, M, L, N(S), N(R)) >
Time-out of T200
4 I (SAPI, C, P, M, L, N(S), N(R)) >
< I (SAPI, C, P, M, L, N(S), N(R)) 5
5 bis RR(SAPI, R, M, L, N(R), F) >
6 I (SAPI, C, P, M, L, N(S), N(R)) >
< RR (SAPI, R, M, L, N(R), F) 7
Time-out of T200
8 I (SAPI, C, P, M, L, N(S), N(R)) >
< RR (SAPI, R, M, L, N(R), F) 9
The frames from the SS will be:
1, 5: One I frame (occurs twice) containing:
SAPI = 0, C = 1, P = 0, M = 0, 0 L N201, N(S) = 0, 1, N(R) = 0.
information field = Identity Request.
7, 9: One RR frame (occurs twice) containing:
SAPI = 0, R = 0, F = 1, 0, M = 0, L = 0, N(R) = 1, 2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.2.3 Test requirements
|
The frames from the MS shall be:
2: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
3, 8: One I frame (occurs twice) containing:
SAPI = 0, C = 0, P = 0, M = 0, 0 L N201, N(R) = 1, 2, N(S) = 0, 1
information field = Identity Response
4, 6: One I frame (occurs twice) containing:
SAPI = 0, C = 0, P = 1, M = 0, 0 L N201, N(R) = 1, 2, N(S) = 0.
information field = Identity Response.
5 bis: (possible only on the FACCH) One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.3 Segmentation and concatenation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.3.1 Test purpose
|
To test the proper use of segmentation and concatenation, suspend and resume.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.3.2 Method of test
|
Specific PICS statements:
- MS supporting USSD (TSPC_Serv_SS_unstruct)
- MS supporting CC protocol for at least one Bearer Capability (TSPC_AddInfo_CCprotocol_oneBC)
If the MS supports the UnStructuredSSData operation, then the MS is made to activate an unknown supplementary service as defined in 3GPP TS 02.30 with the following sequence *NN*si#: NN is chosen to be undefined in 3GPP TS 02.30 annex 2 and is an IA5. Total length of *NN*si# shall be 20 characters.
If the MS does not support the UnStructuredSSData operation, then the MS is made to initiate a call.
The SS responds with the Immediate Assign procedure firstly allocating a SDCCH and on the second repeat of the test a TCH.
The MS is brought into the multiple frame established state by continuing as described in test 25.2.1.1.1. The layer three message element in the SABM will be CM Serv Request.
The SS sends the UA and waits for 10 s. The SS then sends an I frame with CM Serv Accept.
The MS sends either:
- a REGISTER message which is segmented between two I frames; or
- a SETUP message.
The SS shall acknowledge only the I frame with more bit set to 1 (if any) but it shall not acknowledge the I frame with more bit set to 0.
The SS then performs a handover (in the case of SDCCH this shall be finely synchronized) while still on the assigned channel and without acknowledging the last I frame of the MS layer 3 message, making sure to fill the handover command to more than 21 octets (for example by using the cell channel description element).
On the SDCCH the MS will go into timer recovery and resend the last I frame of the layer 3 message with the P bit set to 1 when it acknowledges the two I frames of the handover command. On the FACCH the MS may simply acknowledge both I frames.
The MS does not attempt to resend the last I frame of the REGISTER or SETUP message on the old channel but instead goes to the new channel where it performs a random access using the Handover Access message and then multiple frame establishment without contention resolution as described in test 25.2.1.2.1.
The MS shall then send an I frame with the Handover complete message. Assuming this is a finely synchronized handover.
The SS acknowledges this I frame.
The MS shall then resend the previous REGISTER or SETUP message, that is all frames which are acknowledged in the usual way.
The test has to be repeated on the FACCH.
Expected Sequence
MS SS
1 SABM (SAPI, C, P, M, L) >
< UA (SAPI, R, F, M, L) 2
< I (SAPI, C, P, M, L, N(S), N(R)) 3
4 RR (SAPI, R, F, M, L, N(R)) >
May be incorporated
5 I (SAPI, C, P, M, L, N(S), N(R)) >
May be absent
< RR (SAPI, R, M, L, N(R), F) 6
7 I (SAPI, C, P, M, L, N(S), N(R)) >
< I (SAPI, C, P, M, L, N(S), N(R)) 8
9 I (SAPI, C, P, M, L, N(S), N(R)) >
(see Note 1)
< I (SAPI, C, P, M, L, N(S), N(R)) 10
11 I (SAPI, C, P, M, L, N(S), N(R)) >
(see Note 2)
*********************** Channel Change **********************
***************** including Handover Access *****************
12 SABM (SAPI, C, P, M, L) >
< UA (SAPI, R, F, M, L) 13
14 I (SAPI, C, P, M, L, N(S), N(R)) >
< RR (SAPI, R, F, M, L, N(R)) 15
16 I (SAPI, C, P, M, L, N(S), N(R)) >
May be absent
< RR (SAPI, R, M, L, N(R), F) 17
18 I (SAPI, C, P, M, L, N(S), N(R)) >
< RR (SAPI, R, M, L, N(R), F) 19
Fill
20 UI (C, P, M, L) >
Frame
NOTE 1: The MS may send RR frames on the FACCH in addition to the I frames in 9 and 11.
NOTE 2: The I frame in 11 is optional.
The frames from the SS will be:
2: One UA frame containing:
SAPI = 0, R = 0, F = 1, M = 0, L = L of SABM.
information field = information field of SABM.
3: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, 0 < L <N201, N(S) = 0, N(R) = 0.
information field = CM Service Accept.
6: One RR frame containing: (This frame is sent only if frame 5 was received)
SAPI = 0, R = 0, F = 0, M = 0, L = 0, N(R) = 1.
8, 10: Two I frames containing:
SAPI = 0, C = 1, P = 0, M = 1, 0, L = N201, <= N201, N(S) = 1, 2, N(R) = 1 or 0.
information field = Handover.
13: One UA frame containing:
SAPI = 0, R = 0, F = 1, M = 0, L = 0.
15, 17, 19: Two or three RR frames containing:
SAPI = 0, R = 0, F = 0, M = 0, L = 0, N(R) = 1, 2 or 1, 2, 3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.2.3.3 Test requirements
|
The frames from the MS shall be:
1: One SABM frame containing:
SAPI = 0, C = 0, P = 1, M = 0, 0 L N201.
information field = CM Service Request.
4: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
5, 7: Two I frames containing: (The first I frame may be missing)
SAPI = 0, C = 0, P = 0, M = 1, 0, L = N201, N201, N(S) = 0, 1 or 0, N(R) = 1.
information field = Register or Setup.
9, 11: Two I frames containing:
SAPI = 0, C = 0, P = 1, M = 0, 0 < L N201, N(S) = 1 or 0, N(R) = 2, 3.
information field = Register or Setup.
NOTE: The I frame in 11 is optional.
12: One SABM frame containing:
SAPI = 0, C = 0, P = 1, M = 0, L = 0.
14: One I frame containing:
SAPI = 0, C = 0, P = 0, M = 0, 0 < L < N201, N(S) = 0, N(R) = 0.
information field = Handover Complete.
16, 18: Two I frames containing: (The first I frame may be missing)
SAPI = 0, C = 0, P = 0, M = 1, 0, L = N201, 0 < L N201, N(S) = 1, 2 or 1, N(R) = 0.
information field = Register or Setup.
20: UI frame containing:
C = 0, P = 0, M = 0, L = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.3 Normal layer 2 disconnection
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.3.1 Test purpose
|
To test the normal data link disconnection sequences.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.3.2 Method of test
|
The data link is setup between the MS and the SS as in test 25.2.1.1.1.
The SS sends a Layer 2 Disconnect message to the MS.
The MS shall respond with a UA frame and return to the idle state; no more Layer 2 (I, S or U) frames, except possibly one or more "Fill" frames, shall be sent. The SS may receive "Fill" frames after the sending of the DISC frame. If this occurs this may only happen for up to T200 after the sending of the DISC frame. The checking for Layer 2 frames, and the recording of any "Fill" frames, is done for a time defined as 4 T200.
The SS confirms that the MS has returned to the idle state by performing test 25.2.1.1.1.
Expected Sequence
MS SS
< DISC (SAPI, C, P, M, L) 1
2 UA (SAPI, R, M, L, F) >
The frames from the SS will be:
1: One DISC frame containing:
SAPI = 0, C = 1, P = 1, M = 0, L = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.3.3 Test requirements
|
The frames from the MS shall be:
2: One UA frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0.
No other Layer 2 (I, S or U) frames shall occur. If "Fill" frames are sent this may only be done for up to T200 after the sending of the DISC frame.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4 Test of link failure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.1 I frame loss (MS to SS)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.1.1 Test purpose
|
To test that the MS repeats an I frame N200 times with T200 between two I frames and that the MS releases the layer 2 link after N200 repetitions of the I frame in the case when no answer to the I frame is received.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.1.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS sends an Identity Request message asking for IMEI to the MS.
The MS shall respond with a RR frame though this may be incorporated with the Identity Response I frame.
The SS does not respond to the I frame.
The MS shall wait for expiry of timer T200 and then repeat the I frame but with the P bit set to 1.
This is repeated until the MS has sent the I frame N200+1 times. The MS shall not send any layer 2 frame. This is checked for a time of 4 T200. The MS shall return to the idle state. This is checked by performing test 25.2.1.1.1.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
2 RR (SAPI, R, M, L, N(R), F) >
May be incorporated
3 I (SAPI, C, P, M, L, N(S), N(R)) >
Time-out of T200
4 I (SAPI, C, P, M, L, N(S), N(R)) >
Time-out of T200
4 I (SAPI, C, P, M, L, N(S), N(R)) >
Time-out of T200
. .
. .
. .
4 I (SAPI, C, P, M, L, N(S), N(R)) >
Time-out of T200
4 I (SAPI, C, P, M, L, N(S), N(R)) >
The frames from the SS will be:
1: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, 0 L N201, N(S) = 0, N(R) = 0.
information field = Identity Request.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.1.3 Test requirements
|
The frames from the MS shall be:
2: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
3: One I frame containing:
SAPI = 0, C = 0, P = 0, M = 0, 0 L N201, N(R) = 1, N(S) = 0.
information field = Identity Response.
4: One I frame (occurs N200 times) containing:
SAPI = 0, C = 0, P = 1, M = 0, 0 L N201, N(R) = 1, N(S) = 0.
information field = Identity Response.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.2 RR response frame loss (SS to MS)
|
Covered in test 25.2.2.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.3 RR response frame loss (MS to SS)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.3.1 Test purpose
|
To test the Layer 2 recovery mechanism in the event of RR frame loss.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.3.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS sends a I frame containing a Layer 3 message using PD = 1111 (e.g. 0FH) to the MS. The L3 message is TEST INTERFACE with tested device equal to 0.
The MS shall respond with a RR frame.
The SS ignores the RR frame from the MS but after T200 from the I frame sent by the SS the SS repeats the I frame but with the P bit set to 1. This simulates loss of the RR from the MS.
The MS shall respond with either an RR or REJ frame.
NOTE: This requirement is less restrictive than 3GPP TS 04.06.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
2 RR (SAPI, R, M, L, N(R), F) >
Time-out of T200
< I (SAPI, C, P, M, L, N(S), N(R)) 3
4 RR (SAPI, R, M, L, N(R), F) >
OR
4 REJ (SAPI, R, M, L, N(R), F) >
The frames from the SS will be:
1: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, L = 3, N(S) = 0, N(R) = 0.
3: One I frame containing:
SAPI = 0, C = 1, P = 1, M = 0, L = 3, N(S) = 0, N(R) = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.4.3.3 Test requirements
|
The frames from the MS shall be:
2: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
4: One RR frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 1.
OR
4: One REJ frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5 Test of frame transmission with incorrect C/R values
|
Purpose of tests
To test that the MS will react correctly upon the reception of a frame with incorrect C/R value.
Initial Conditions
Perform the establishment of the dedicated physical resource according to 25.1.5 and initialize the link as in subclause 25.2.1.1.1. Then proceed as stated below.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.1 I frame with C bit set to zero
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.1.1 Test purpose
|
To test that the MS will take no action when it receives an I frame with the C bit set to zero (R).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.1.2 Method of test
|
The data link is set up between the MS and the SS as in test 25.2.1.1.1.
The SS shall send an I frame with the C bit set to zero to the MS.
The SS shall then wait for at least 4 times T200 to make sure that the MS does not respond to that I frame but that the MS keeps sending fill frames.
The SS shall after 4 times T200 send a RR command, P bit set to 1.
The MS shall respond with a RR response, F bit set to 1.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, M, L, N(R), P) 3
4 RR (SAPI, R, M, L, N(R), F) >
The frames from the SS will be:
1: One I frame containing:
SAPI = 0, C = 0, P = 1, M = 0, 0 L N201, N(R) = 0, N(S) = 0.
Information field = Identity Request.
3: One RR frame containing:
SAPI = 0, C = 1, P = 1, M = 0, L = 0, N(R) = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.1.3 Test requirements
|
The frames from the MS shall be:
2: UI frames containing:
C = 0, P = 0, M = 0, L = 0.
4: One RR frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.2 SABM frame with C bit set to zero
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.2.1 Test purpose
|
To test that the MS will take no action when it receives an SABM frame with the C bit set to zero (R).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.2.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS sends an I frame containing a Layer 3 message using PD=1111 (e.g. 0FH) in order to raise V(R) in the MS to 1. The L3 message is TEST INTERFACE with tested device equal to 0.
The MS shall acknowledge this by the appropriate RR frame.
The SS sends SABM with the C bit set to zero.
The SS shall after 4 times T200 send a RR command, P bit set to 1.
The MS shall respond with a RR response, F bit set to 1.
The MS is returned to the idle state as described in subclause 25.2.1.1.6.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
2 RR (SAPI, R, M, L, N(R), F) >
< SABM (SAPI, C, P, M, L) 3
Fill
4 UI (C, P, M, L) >
Frame
< RR (SAPI, C, M, L, N(R), P) 5
6 RR (SAPI, R, M, L, N(R), F) >
The frames from the SS will be:
1: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, L = 3, N(S) = 0, N(R) = 0.
3: One SABM frame containing:
SAPI = 0, C = 0, P = 1, M = 0, L = 0.
5: One RR frame containing:
SAPI = 0, C = 1, P = 1, M = 0, L = 0, N(R) = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.5.2.3 Test requirements
|
The frames from the MS shall be:
2: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
4: One UI frame containing:
C = 0, P = 0, M = 0, L = 0.
6: One RR frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6 Test of errors in the control field
|
Purpose of tests
To test that the MS will react in the proper way to errors in the Control Field.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.1 N(S) sequence error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.1.1 Test purpose
|
To test that the MS will ignore the contents of the I field of an out-of-sequence I frame from the SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.1.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS shall send a correct I frame containing Identity Request.
The MS shall acknowledge this in a RR frame or piggy back the acknowledgement onto the I frame carrying Identity Response.
The SS shall then send an I frame containing Identity Request with incorrect N(S) but correctly acknowledging the MS's I frame; P bit set to zero.
The MS shall send a REJ frame.
The SS shall, after T200, send another I frame with incorrect N(S), P bit set to 1 this time.
The MS shall respond with a REJ, F bit set to 1.
The MS shall resume the transmission of fill frames.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(S), N(R)) 1
2 RR (SAPI, R, M, L, N(R), F) >
May be incorporated
3 I (SAPI, C, P, M, L, N(S), N(R)) >
< I (SAPI, C, P, M, L, N(S), N(R)) 4
5 REJ (SAPI, R, P, M, L, N(R)) >
Time out of T200.
< I (SAPI, C, P, M, L, N(S), N(R)) 6
7 REJ (SAPI, R, F, M, L, N(R)) >
Fill
8 UI (C, P, M, L) >
Frame
The frames from the SS will be:
1: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, 0 L N201, N(S) = 0, N(R) = 0.
information field = Identity Request.
4: One I frame containing:
SAPI = 0, C = 1, P = 0, M = 0, 0 L N201, N(S) = 0, N(R) = 1
information field = Identity Request
6: One I frame containing:
SAPI = 0, C = 1, P = 1, M = 0, 0 L N201, N(S) = 0, N(R) = 1
information field = Identity Request
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.1.3 Test requirements
|
The frames from the MS shall be:
2: One RR frame containing:
SAPI = 0, R = 1, F = 0, M = 0, L = 0, N(R) = 1.
3: One I frame containing:
SAPI = 0, C = 0, P = 0, M = 0, 0 L N201, N(R) = 1, N(S) = 0.
information field = Identity Response.
5: One REJ frame containing:
SAPI = 0, R = 1, P = 0, M = 0, L = 0, N(R) = 1.
7: One REJ frame containing:
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 1.
8: One UI frame containing:
C = 0, P = 0, M = 0, L = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.2 N(R) sequence error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.2.1 Test purpose
|
To test that the MS will detect a N(R) sequence error and react in the proper way to it.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.2.2 Method of test
|
The MS is brought into the multiple frame established state as described in test 25.2.1.1.1.
The SS shall send an I frame containing an information field of length N201 and an incorrect receive sequence number.
The MS may:
a) send a DISC frame within N200T200; or
b) perform a "local end release".
In case a) the SS shall respond with a UA frame. In case b) it detects a lower layer failure.
NOTE: The delay N200T200 is specified for test purpose only. It is assumed that the L3 reaction time within the MS to command a release is less than this delay, which is less than the delay before the SS would detect a L2 failure.
Expected Sequence
MS SS
< I (SAPI, C, P, M, L, N(R), N(S)) 1
optional
2 DISC (C, P, M, L) >
< UA (R, F, M, L) 3
The frames from the SS are:
1: One I frame:
SAPI 0, C = 1, P = 0, M = 1, L = N201, N(R) = 1, N(S) = 0.
In case a):
3: One UA frame:
SAPI = 0, R = 0, F = 1, M = 0, L = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.2.3 Test requirements
|
The frame from the MS in case a) shall be:
2: One DISC frame:
SAPI = 0, C = 0, P = 1, M = 0, L = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.3 Improper F bit
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.6.3.1 Test purpose
|
To test that the MS, being in the timer recovery state, will return to the multiple frame established state only after having received an RR response with the F bit set to 1. This test is covered in test 25.2.2.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.7 Test on receipt of invalid frames
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.7.1 Test purpose
|
To test that the MS will ignore all invalid frames.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.7.2 Method of test
|
The data link is set up between the MS and the SS as in test 25.2.1.1.1.
The SS shall then transmit an:
- RR frame with the Length indicator greater than zero and a faulty N(R);
- REJ frame with the EA bit set to zero and a faulty N(R);
- SABM frame with the EL bit set to zero;
- DM frame with the Length indicator greater than zero;
- DISC frame with the M bit set to 1;
- UA frame with the EA bit set to zero;
- I frame with the Length indicator greater than N201;
- I frame with the M bit set to 1 and the Length indicator less than N201;
- command frames with correct Address and Length indicator field and a non-implemented control field.
After T200 the SS shall in every case transmit an RR command, P bit set to 1.
The MS shall respond with an RR response, F bit set to 1.
Expected Sequence
MS SS
< RR (SAPI, R, F, M, L, N(R)) 1
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< REJ (SAPI, R, F, M, L, N(R) 3
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< SABM (SAPI, C, P, M, L) 4
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< DM (SAPI, R, F, M, L) 5
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< DISC (SAPI, C, P, M, L) 6
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< UA (SAPI, R, F, M, L) >7
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< I (SAPI, C, P, M, L, N(R), N(S)) 8
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< I (SAPI, C, P, M, L, N(R), N(S)) 9
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 12
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 13
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 14
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 15
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 16
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 17
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
< 18
Fill
2 UI (C, P, M, L) >
Frame
< RR (SAPI, C, P, M, L, N(R)) 10
11 RR (SAPI, R, F, M, L, N(R)) >
The frames from the SS are:
1: One RR frame:
SAPI = 0, R = 0, F = 0, M = 0, L > 0, N(R) = 1.
3: One REJ frame:
SAPI = 0, R = 0, F = 0, M = 0, L = 0, N(R) = 1, EA = 0.
4: One SABM frame:
SAPI = 0, C = 1, P = 1, M = 0, L = 0, EL = 0.
5: One DM frame:
SAPI = 0, R = 0, F = 1, M = 0, L > 0.
6: One DISC frame:
SAPI = 0, C = 1, P = 1, M = 1, L = 0.
7: One UA frame:
SAPI = 0, R = 0, F = 0, M = 0, L = 0, EA = 0.
8: One I frame:
SAPI = 0, C = 1, P = 0, M = 0, L > N201, N(R) = 0, N(S) = 6.
9: One I frame:
SAPI = 0, C = 1, P = 0, M = 1, L < N201, N(R) = 0, N(S) = 7.
10: One RR frame:
SAPI = 0, C = 1, P = 1, M = 0, L = 0, N(R) = 0.
12: One command frame with
Control Field = xxx1 1101.
13: One command frame with
Control field = xxx1 1011.
14: One command frame with
Control field = xxx1 0111.
15: One command frame with
Control field = 01x1 1111.
16: One command frame with
Control field = 1xx1 1111.
17: One command frame with
Control field = 0011 0011.
18: One command frame with
Control field = 1xx1 0011.
NOTE: An "x" stands for an arbitrary bit value.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
25.2.7.3 Test requirements
|
The frames from the MS shall be:
2: One UI frame (occurs fifteen times):
C = 0, P = 0, M = 0, L = 0.
11: One RR frame (occurs fifteen times):
SAPI = 0, R = 1, F = 1, M = 0, L = 0, N(R) = 0.
26 Testing of layer 3 functions
Ref.: 3GPP TS 04.08 / 3GPP TS 24.008 / 3GPP TS 44.018
NOTE: The tests on functioning of the elementary procedures in the MS are grouped as the description of those procedures in 3GPP TS 04.08 / 3GPP TS 24.008 / 3GPP TS 44.018. However, the test procedures are carried out in an order which is more logic for the purpose of testing.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1 Default conditions and structured sequence of tests
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1.1 Default test conditions during layer 3 tests
|
During tests in clause 26 the following default test conditions shall apply if not otherwise stated within the test description. In the table below, decimal values are normally used. Sometimes a hexadecimal value, indicated with a "H", or a binary value, indicated with a "B" is given.
GSM 900
DCS 1 800
General signalling conditions for all carriers
Ciphering
yes
yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Non-hopping
Propagation profile
Static
Static
Downlink Input Level
63 dBVemf( )
63 dBVemf( )
Uplink output power
Minimum according
Minimum according
to MS power class
to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
20
590
Alternative channels
40 or 60
690 or 830
Serving cell, Traffic channel, SDCCH
Channel ARFCN
30
650
Alternative channels
50 or 70
750 or 850
Power Control Indicator
0
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
10, 80, 90, 100, 110, 120
520, 600, 700, 780, 810, 870
Alternative channels
15, 85, 95, 105, 115, 122
530, 610, 710, 790, 820, 880
Input level
53 dBVemf( )
53 dBVemf( )
Network dependent parameters
Cell identity
0001H
0001H
Mobile country code, MCC
001 (decimal)
001 (decimal)
Mobile network code, MNC
01 (decimal)
01 (decimal)
Location area code, LAC
0001H
0001H
Frequency List
Bit Map 0
Range 512
BCCH allocation sequence
0
0
number(BA_IND)
Cell Channel Descriptor
Bit Map 0
Range 512
PLMN colour code, NCC
1
1
BS colour code, BCC
5
5
SMS Cell Broadcast
not active
not active
DTX
MS must not use
MS must not use
IMSI Attach-detach
MS shall not apply
MS shall not apply
CCCH_CONF
1 basic physical channel for
1 basic physical channel for
CCCH combined with SDCCH
CCCH combined with SDCCH
BS_AG_BLKS_RES
0 blocks reserved
0 blocks reserved
BS_PA_MFRMS
5 paging subgroups
5 paging subgroups
GSM 900
DCS 1 800
CELL_BAR_ACCESS
(not barred)
(not barred)
Call-reestablishment (RE)
(allowed)
(allowed)
Emergency Call allowed
allowed
same
Access Control Class
allowed
same
(AC) (0..9, 11..15)
Network dependent timers
Radio_Link_Time-out
8
8
T3212 Periodic
Infinite
Infinite
updating in decihours
Access control parameters
Max retrans
1
1
Tx-integer, nr. of slots
5
5
CELL_RESELECT_HYSTERESIS
12 dB
12 dB
MS_TXPWR_MAX_CCH
minimum level
minimum level
RXLEV_ACCESS_MIN
minimum
minimum
NECI
New establishment causes
same
are not supported
ACS (ADDITIONAL RESELECTION
No additional cell parameters
same
PARAM IND)
are present in SI messages
7 and 8
C2 parameters
C2 parameters not present
same
POWER OFFSET
N/A
POWER OFFSET Parameter not
present.
GSM 450
GSM 480
General signalling conditions for all carriers
Ciphering
yes
yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Non-hopping
Propagation profile
Static
Static
Downlink Input Level
63 dBVemf( )
63 dBVemf( )
Uplink output power
Minimum according
Minimum according
to MS power class
to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
263
310
Alternative channels
274 or 276
321 or 323
Serving cell, Traffic channel, SDCCH
Channel ARFCN
267
314
Alternative channels
275 or 279
322 or 326
Power Control Indicator
0
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
260, 281, 284, 287, 290, 293
307, 328, 331, 334, 337, 340
Alternative channels
261, 280, 283, 286, 289, 292
308, 327, 330, 333, 336, 339
Input level
53 dBVemf( )
53 dBVemf( )
Network dependent parameters
Cell identity
0001H
0001H
Mobile country code, MCC
001 (decimal)
001 (decimal)
Mobile network code, MNC
01 (decimal)
01 (decimal)
Location area code, LAC
0001H
0001H
Frequency List
Range 128
Range 128
BCCH allocation sequence
0
0
number(BA_IND)
Cell Channel Descriptor
Range 128
Range 128
PLMN colour code, NCC
1
1
BS colour code, BCC
5
5
SMS Cell Broadcast
not active
not active
DTX
MS must not use
MS must not use
IMSI Attach-detach
MS shall not apply
MS shall not apply
CCCH_CONF
1 basic physical channel for
1 basic physical channel for
CCCH combined with SDCCH
CCCH combined with SDCCH
BS_AG_BLKS_RES
0 blocks reserved
0 blocks reserved
BS_PA_MFRMS
5 paging subgroups
5 paging subgroups
GSM 450
GSM 480
CELL_BAR_ACCESS
(not barred)
(not barred)
Call-reestablishment (RE)
(allowed)
(allowed)
Emergency Call allowed
allowed
same
Access Control Class
allowed
same
(AC) (0..9, 11..15)
Network dependent timers
Radio_Link_Time-out
8
8
T3212 Periodic
Infinite
Infinite
updating in decihours
Access control parameters
Max retrans
1
1
Tx-integer, nr. of slots
5
5
CELL_RESELECT_HYSTERESIS
12 dB
12 dB
MS_TXPWR_MAX_CCH
minimum level
minimum level
RXLEV_ACCESS_MIN
minimum
minimum
NECI
New establishment causes
same
are not supported
ACS (ADDITIONAL RESELECTION
No additional cell parameters
same
PARAM IND)
are present in SI messages
7 and 8
C2 parameters
C2 parameters not present
same
POWER OFFSET
N/A
N/A
GSM 710 or GSM 750 or T-GSM 810
GSM 850
General signalling conditions for all carriers
Ciphering
yes
yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Non-hopping
Propagation profile
Static
Static
Downlink Input Level
63 dBVemf( )
63 dBVemf( )
Uplink output power
Minimum according
Minimum according
to MS power class
to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
460
150
Alternative channels
480 or 500
170 or 190
Serving cell, Traffic channel, SDCCH
Channel ARFCN
470
160
Alternative channels
490 or 510
180 or 200
Power Control Indicator
0
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
440, 445, 450, 455, 475, 495
140, 210, 220, 230, 240, 250
Alternative channels
443, 448, 453, 465, 485, 505
145, 215, 225, 235, 245, 251
Input level
53 dBVemf( )
53 dBVemf( )
Network dependent parameters
Cell identity
0001H
0001H
Mobile country code, MCC
001 (decimal)
001 (decimal)
Mobile network code, MNC
011(decimal)
011(decimal)
Location area code, LAC
0001H
0001H
Frequency List
Range 128
Range 128
BCCH allocation sequence
0
0
number(BA_IND)
Cell Channel Descriptor
Range 128
Range 128
PLMN colour code, NCC
1
1
BS colour code, BCC
5
5
SMS Cell Broadcast
not active
not active
DTX
MS must not use
MS must not use
IMSI Attach-detach
MS shall not apply
MS shall not apply
CCCH_CONF
1 basic physical channel for
1 basic physical channel for
CCCH combined with SDCCH
CCCH combined with SDCCH
BS_AG_BLKS_RES
0 blocks reserved
0 blocks reserved
BS_PA_MFRMS
5 paging subgroups
5 paging subgroups
GSM 710 or GSM 750 or T-GSM 810
GSM 850
CELL_BAR_ACCESS
(not barred)
(not barred)
Call-reestablishment (RE)
(allowed)
(allowed)
Emergency Call allowed
allowed
allowed
Access Control Class
allowed
allowed
(AC) (0..9, 11..15)
Network dependent timers
Radio_Link_Time-out
8
8
T3212 Periodic
Infinite
Infinite
updating in decihours
Access control parameters
Max retrans
1
1
Tx-integer, nr. of slots
5
5
CELL_RESELECT_HYSTERESIS
12 dB
12 dB
MS_TXPWR_MAX_CCH
minimum level
minimum level
RXLEV_ACCESS_MIN
minimum
minimum
NECI
New establishment causes
New establishment causes
are not supported
are not supported
ACS (ADDITIONAL RESELECTION
No additional cell parameters
No additional cell parameters
PARAM IND)
are present in SI messages
are present in SI messages
7 and 8
7 and 8
C2 parameters
C2 parameters not present
C2 parameters not present
POWER OFFSET
N/A
N/A
PCS 1 900
General signalling conditions for all carriers
Ciphering
yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Propagation profile
Static
Downlink Input Level
63 dBVemf( )
Uplink output power
Minimum according
to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
590
Alternative channels
690 or 730
Serving cell, Traffic channel, SDCCH
Channel ARFCN
650
Alternative channels
750 or 780
Power Control Indicator
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
520, 600, 700, 720, 760, 780
Alternative channels
530, 610, 710, 740, 770, 790
Input level
53 dBVemf( )
Network dependent parameters
Cell identity
0001H
Mobile country code, MCC
001 (decimal)
Mobile network code, MNC
011 (decimal)
Location area code, LAC
0001H
Frequency List
Range 512
BCCH allocation sequence
0
number(BA_IND)
Cell Channel Descriptor
Range 512
PLMN colour code, NCC
1
BS colour code, BCC
5
SMS Cell Broadcast
not active
DTX
MS must not use
IMSI Attach-detach
MS shall not apply
CCCH_CONF
1 basic physical channel for
CCCH combined with SDCCH
BS_AG_BLKS_RES
0 blocks reserved
BS_PA_MFRMS
5 paging subgroups
PCS 1 900
CELL_BAR_ACCESS
(not barred)
Call-reestablishment (RE)
(allowed)
Emergency Call allowed
same
Access Control Class
same
(AC) (0..9, 11..15)
Network dependent timers
Radio_Link_Time-out
8
T3212 Periodic
Infinite
updating in decihours
Access control parameters
Max retrans
1
Tx-integer, nr. of slots
5
CELL_RESELECT_HYSTERESIS
12 dB
MS_TXPWR_MAX_CCH
minimum level
RXLEV_ACCESS_MIN
minimum
NECI
same
ACS (ADDITIONAL RESELECTION
same
PARAM IND)
C2 parameters
same
POWER OFFSET
N/A
These informations are provided by system information 1, 2, 3 and 4 messages.
The system information elements which are broadcast on the SACCH during the dedicated mode should be consistent with those sent on the BCCH when the MS was in idle mode prior to the channel request.
In addition, all fill paging messages sent on the paging sub-channels will have by default, their page mode set to NORMAL PAGING.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1.2 Structured sequence of the tests
|
The tests shall be performed in the order as indicated in the following table.
The validity of the tests depends upon the results of the tests performed before.
Channel request (basic test)
RR
26.2.1
Immediate assignment
RR
26.6.1
IMSI attach/detach (basic)
RR
26.2.2
Paging
RR
26.6.2
Test of the mobile station functions in idle mode
RR
26.3
Frequency redefinition
RR
26.6.6
Measurement report (incl. system info not idle)
RR
26.6.3
Authentication
MM
26.7.2
Cipher mode setting
RR
26.6.8
Identification
MM
26.7.3
Sequenced MM/CM message transfer
..
26.2.3
Channel release
RR
26.6.12
Location updating
MM
26.7.4
TMSI reallocation
MM
26.7.1
Classmark change
RR
26.6.11
Call control (verification on CC state diagram)
CC
26.8.1.1 and
26.8.1.2
Call rearrangement
CC
26.8.1.4.4
DTMF information transfer
CC
26.8.1.4.1
Handover
RR
26.6.5
Additional assignment
RR
26.6.9
Partial release
RR
26.6.10
Re-establishment
CC
26.8.2
Dedicated channel assignment (during calls)
RR
26.6.4
Transmission mode change
RR
26.6.7
Mobility management connection establishment
MM
26.7.5
Test of Layer 3 error handling
26.5
User to user signalling
CC
26.8.3
Testing of structured procedures
26.9
E-GSM or R-GSM or ER-GSM signalling
26.10
Multiband signalling
26.11
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1.3 General rules for message parameters
|
The following rules concerning message parameters apply to clause 26:
1) Those values of parameters which are a consequence of the context of a test and which are not specific to that test need not be defined.
2) If the value of a parameter of an uplink message (MS to Network) is specified in a test, the implicit meaning is that it has to be checked; if the value is not specified, it is not to be checked unless stated otherwise.
3) An optional field or optional Information Element of a downlink message (Network to MS), the presence of which is not a consequence of a test description, shall be absent in that test.
4) If an optional field or Information Element is not indicated for the uplink (MS to Network) - unless specified otherwise -, it may be included or not.
5) The Protocol Discriminator, Transaction Identifier and Message Type of all uplink messages have to be checked.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1.4 General rules for layer 3 testing
|
Unless otherwise specified, before the SS pages the MS, the MS must be given the necessary time to be able to receive paging (see clause 20). In addition and unless otherwise specified,the SS must wait at least 1s after the last time slot of the message block containing a CHANNEL RELEASE, before sending a PAGING to the mobile (see 3GPP TS 04.13).
In the signalling tests, where the following statement is used:
- 'the RF level of cell x is set sufficiently low to ensure that cell x is not suitable as defined in 3GPP TS 05.08 subclause 6.6.2';
this means that for the cell to be "not suitable" by virtue of its RF level, the RF level is to be lowered until C1 is below 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.1.5 Format of layer 3 test descriptions
|
In subclauses 26.2, 26.5, 26.6, 26.7, 26.9, 26.10 and 26.11 a rigorous description technique is used which is defined here.
For every test, a subclause titled "method of test" and a subclause titled "expected sequence" define the exact test steps and the verifications to be performed in the test. These subclauses are normative and give requirements for the MS behaviour. The information of both subclauses applies.
For the message contents further normative requirements for the MS behaviour are defined in the following parts which apply in the following order (starting with the highest) on basis of the general rules of 26.1.3:
- specifications in the "method of test" and "expected sequence" subclauses;
- specifications in the subclause titled "specific message contents";
- specifications in the subclause "default message contents" at the end of the relevant subclauses 26.5, 26.6, 26.7, 26.9, 26.10 or 26.11;
- specifications of default conditions in subclause 26.1.
The relevant section may contain the definition of abbreviations of L3 message names that are used in that section.
In many cases, a test description contains an introductory subclause explaining the background of the relevant procedures and explaining why the tests of that description are essential.
For every test, test purposes are given. In general conformance testing methodology, the correspondence between test purposes and test cases can be n to m: To one test purpose more than one test case may correspond (e.g. different test cases checking data variations); also a test case may serve more than one test purpose. In some contexts a structure of conformance test descriptions is advisable which specifies in one part (non-duplicated) test purposes with references to corresponding test suites serving the test purposes, in another part test suites realizing the test purposes; this structuring is especially useful for gaining completeness and avoiding duplications. In the present document, however, it is preferred to group descriptions by test cases. The reasons are:
- The structure is more sought to assist the test execution and evaluation than test development. It must be easy to determine why a wrong behaviour leads to a verdict.
- The structure is to be close to GSM 11.10 phase 1.
For every test purpose of a test, a conformance requirement is given.
For each conformance requirement in a test description, references to core specifications are given.
For every test, the related PICS/PIXIT statements that are necessary for performing the test are given.
For every test, initial conditions for both the System Simulator and the Mobile Station are given. Unless otherwise specified, these initial conditions apply together with the default conditions of 26.1, the initial conditions of the test prevailing over the default conditions of 26.1.
For every test, the foreseen final state of the MS after the test and the maximum duration of the test are specified. These parts are non-normative and do not contain a description of verifications to be performed. The contained information might be used for sequencing different tests and for the decision when a test is to be interrupted.
The expected sequence specifies the actions in numbered steps in a tabular form. In the column "direction", "SS -> MS" denotes a message sent from the SS to the MS, "MS -> SS" denotes a message sent from the MS to the SS, "SS" denotes an action at the SS, "MS" denotes an action at the MS (e.g. interaction with the user or higher layers). The column "message" defines the L3 messages to be sent or expected by the SS. In the "comments" column, further normative information is to be found, e.g. message parameters. In some cases, different alternative behaviours are possible in a test. Then test steps in alternative sequences are numbered as:
"A n", "A n + 1",...,"A n + k";
"B n", "B n + 1",...,"B n + l";
"C n", "C n + 1",...,"C n + m";
etc. (n, m, l, k integers > 0).
and step numbering of a re-unified sequence resumes with the lowest of n + k + 1, n + l + 1, n + m + 1.
In some cases the test steps of a test are to be repeated. Then an execution counter is introduced for the test.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2 Initial tests
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1 Channel request
|
The random access procedure is used by the MS to ask for resources to the network. If it is not performed correctly, the MS could prevent other MSs from obtaining resources, or the network could be overloaded if the MS does not respect the duration between 2 CHANNEL REQUEST messages.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.1 Channel request / initial time
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.1.1 Conformance requirement
|
1) The MS shall start the initial access procedure at the latest 0,7 s after reception of the paging message.
2) The MS shall spread the initial CHANNEL REQUEST with equal probability on the correct number of time slots.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclauses 3.3.1.1.2 and 3.3.2.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.1.2 Test purpose
|
1) To verify that the MS answers to a PAGING message by sending a CHANNEL REQUEST message within 0,7 s after reception of the PAGING message.
2 To verify that the MS does not always use the same delay between reception of paging message and sending of the CHANNEL REQUEST message. If an MS uses a fixed delay, there is a high probability that different MSs of the same product series use the same delay. There would then be a high risk of collision.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, Tx-Integer = 5. The CCCH is either combined or not with SDCCH. This is arbitrarily chosen.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
Specific test parameters:
K = 200.
The MS is paged. The SS measures and stores the number of CCCH RACH slots between the sending of the PAGING REQUEST message and the reception of the CHANNEL REQUEST from the MS, excluding the slots containing the messages themselves. The SS sends an IMMEDIATE ASSIGNMENT REJECT. The sequence is performed K times.
Maximum Duration of Test
30 min.
Between two consecutive executions (for k and k+1), the SS must wait for an amount of time which is enough to guarantee that the MS is in service (listening to its paging subchannel).
Expected Sequence
The sequence is executed for execution counter k = 1, ... , K.
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
"Mobile Identity" IE contains the TMSI allocated to the MS.
2
SS
The SS measures the number f of CCCH RACH slots between the sending of PAGING REQUEST message and the reception of a CHANNEL REQUEST message from the MS.
3
SS
The SS stores f. f(k) shall be lower than 700/4,615+8 if the CCCH is not combined or lower than 81+8 if the CCCH is combined with SDCCH.
4
MS -> SS
CHANNEL REQUEST
"Establishment Cause" = Answer to paging.
5
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
the first "request reference" corresponds to the CHANNEL REQUEST sent by the MS.
NOTE: The test limit has been computed to give a confidence of [99,74 %] that a unit which follows the requirements will pass. The number of samples (200) has been chosen to get a good compromise between the test time and the risk of passing a bad unit.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.1.4 Test requirements
|
S(n) = CARD {k | f(k) = n}
The following requirements shall be met:
S(n) 41 for all n.
NOTE: CARD {k | f(k) = n} is mathematical notation for the number of times that f(k) equals n.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.2 Channel request / repetition time
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.2.1 Conformance requirement
|
1) The MS shall spread retransmissions of a CHANNEL REQUEST message, with equal probability on Tx-Integer timeslots and with the correct delay after the reception of the PAGING REQUEST.
2) The MS shall not retransmit another CHANNEL REQUEST message when Max-retrans is reached.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.3.1.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.2.2 Test purpose
|
1) To verify that the MS spreads retransmission of a CHANNEL REQUEST message with equal probability on Tx-Integer time slots and correctly applies the fixed delay when the following conditions apply:
- the CCCH is combined or not combined with SDCCHs;
- the maximum number of retransmissions is equal to one of the following values: 1, 2, 4, 7;
- Tx-Integer is put to any of the allowed values among those which are greater or equal to 6.
2) To verify that the MS retransmits exactly Max_Retrans times a CHANNEL REQUEST message if the network never responds to the CHANNEL REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell.
Tx-Integer is arbitrarily chosen in the set {6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50}.
Max_Retrans is arbitrarily chosen in the set {1, 2, 4, 7}.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
Specific test parameters
K equals the upper rounded value of 230/Max_Retrans.
m equals the upper rounded value of 0,5 Tx-Integer.
Counter M = 0.
Parameter S: according to table 3.1/3GPP TS 04.08 / 3GPP TS 44.018 (this parameter depend on the value chosen for Tx-Integer).
N0 = max (8, Tx-Integer).
The MS is paged. The MS sends a CHANNEL REQUEST message. The MS retransmits CHANNEL REQUEST messages Max_Retrans times. The SS measures the number of CCCH RACH slots f(i,k) between the moment where a CHANNEL REQUEST message has been received, and the reception of the following CHANNEL REQUEST message, excluding the slots containing the messages themselves. The SS updates the counter M. The SS does not answer to the CHANNEL REQUEST messages Max_Retrans times. After the last CHANNEL REQUEST message in every sequence where k is lower than K, the SS sends an IMMEDIATE ASSIGNMENT REJECT . In the last sequence (k = K), the SS does not respond to the MS. The MS shall not send any other CHANNEL REQUEST message.
Maximum Duration of Test
The execution of one sequence (for one value k): 10 s.
Between two consecutive executions (for k and k+1), the SS must wait for 35 s,which is enough to guarantee that the MS is in service (listening to its paging subchannel).
Expected Sequence
The sequence is executed for execution counter k = 1, ... , K for each of the 2 test cases.
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
"Mobile Identity" = TMSI of the MS.
2
MS -> SS
CHANNEL REQUEST
"Establishment Cause" = Answer to paging.
Steps 3, 4, 5 are executed for execution counter i = 1,...,Max_Retrans.
3
MS -> SS
CHANNEL REQUEST
"Establishment Cause" = Answer to paging.
4
SS
The SS measures the number f(i,k) of CCCH RACH slots between: - the moment where the last CHANNEL REQUEST message has been received, and - the reception of the new CHANNEL REQUEST message from the MS, excluding the slots containing the messages themselves. f(i,k) shall be in the set {S,S+1,...,S+T‑1}
5
SS
If f(i,k)-S >= m, M = M+1
Depending on the value of k, step A6 or B6 is performed:
A6
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
k < K The third "Request Reference" IE corresponds to the last CHANNEL REQUEST message received. The third "Wait Indication" IE specifies 0 sond. Other fields do not address the MS under test.
B6
SS
k = K The SS checks that the MS sends no more CHANNEL REQUEST messages. This is verified during 3 s.
7
SS
M / (K * Max_Retrans) shall be inside the following interval: [0,8 - m/Tx-Integer ; 1,2 - m/Tx-Integer]
NOTE: The confidence interval in step 7, and the number of samples are chosen in such a way that the possibility of not accepting a correct MS is less than [0,26 %].
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.3 Channel request / random reference
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.3.1 Conformance requirement
|
A CHANNEL REQUEST message sent by the MS shall include a random reference randomly drawn from a uniform probability distribution for every new transmission.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.3.1.1.23.3.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.3.2 Test purpose
|
To verify that an MS produces different random references for a CHANNEL REQUEST. If a MS always produces the same random reference, it makes possible that different MSs of the same product series produce the same random reference.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, CCCH not combined with SDCCH.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is in the MM-state "idle, updated" and in the RR idle-mode.
Test Procedure
Specific test parameters:
K = 7.
D = 4.
The SS sends a PAGING REQUEST message. The SS stores the "Random Reference" r(k) contained as a parameter in the CHANNEL REQUEST message sent by the MS. This sequence is performed K times, and it is verified that the MS produces different values r(k).
Maximum Duration of Test
6 min
Between two consecutive executions (for k and k+1), the SS must wait for an amount of time which is enough to guarantee that the MS is in service (listening to its paging subchannel).
Expected Sequence
The sequence is executed for execution counter k = 1, ..., K.
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
2
MS -> SS
CHANNEL REQUEST
"Establishment Cause" = Answer to paging.
3
SS
The SS stores the "Random Reference" contained in the CHANNEL REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.1.3.4 Test requirements
|
At least D values of r(1), ..., r(k) shall be different.
NOTE: D has been computed such that the probability of refusing a correct MS is less than [0,027 %].
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.2 IMSI detach and IMSI attach
|
The IMSI detach/attach procedures are used to indicate to the network that the MS is deactivated/activated. Theses procedures are allowed or not by the network (ATT flag set to "MSs in the cell shall apply IMSI attach and detach procedure" or "MSs in the cell are not allowed to apply IMSI attach and detach procedure").
If the IMSI attach procedure does not work correctly then the network would in certain situations not try to establish Mobile Terminating call even if the MS is "idle updated".
If an MS performs an unwanted IMSI detach procedure or does not perform IMSI detach when required, network resources are wasted.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.2.1 Conformance requirement
|
1) When the Attach-detach flag in the Control Channel Description of the System Information Type 3 indicates "MSs in the cell are not allowed to apply IMSI attach and detach procedure", the MS shall not perform the IMSI detach procedure upon deactivation.
2) When the Attach-detach flag in the Control Channel Description of the System Information Type 3 indicates "MSs in the cell are not allowed to apply IMSI attach and detach procedure", the MS shall not perform the IMSI attach procedure upon activation.
3) The MS shall not perform the IMSI detach procedure if the Subscriber Identity Module is removed when the Attach-detach flag in the Control Channel Description of the System Information Type 3 indicates "MSs in the cell are not allowed to apply IMSI attach and detach procedure".
4) The MS shall not perform the IMSI attach procedure if the Subscriber Identity Module is inserted, when the Attach-detach flag in the Control Channel Description of the System Information Type 3 indicates "MSs in the cell are not allowed to apply IMSI attach and detach procedure".
5) The MS shall correctly perform the IMSI detach procedure, upon switch off, when it is required by the network to do so.
6) The MS shall correctly perform the IMSI attach procedure upon switch on when the IMSI attach procedure is required by the network. The MS shall correctly acknowledge the implicit TMSI reallocation procedure, which is part of this IMSI attach procedure, this means that the MS shall send a TMSI REALLOCATION COMPLETE message.
7) The MS shall correctly perform the IMSI detach procedure upon SIM removal when it is required by the network to do so.
8) The MS shall correctly perform the IMSI attach procedure, following SIM insertion and switch on when the IMSI attach procedure is required by the network. The MS shall correctly acknowledge the implicit TMSI reallocation procedure which is part of this IMSI attach procedure. This means that the MS shall send a TMSI REALLOCATION COMPLETE message.
Reference(s):
3GPP TS 02.07, normative annex B, subclause B1.17.
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 4.4.3 and 4.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.2.2 Test purpose
|
1) To verify that the MS correctly performs IMSI detach/attach procedures when it is required by the network and upon deactivation/activation or SIM removal/insertion and does not perform these procedures when not required.
2) To verify that the mobile station acknowledges a re-allocated TMSI during IMSI attach.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default parameters.
For procedures 1 and 2 ATT flag is set to "MSs in the cell are not allowed to apply IMSI attach and detach procedure".
For procedures 3 and 4 ATT flag is set to "MSs in the cell should apply IMSI attach and detach procedure".
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
- a: SIM removal possible without removing power source (TSPC_AddInfo_SIMRmv)
- b: On/off switch (TSPC_Feat_OnOff)
- c: IMSI detach after SIM removal (TSPC_AddInfo_DetachOnSIMRmv)
- d: IMSI detach after removing power source (TSPC_AddInfo_DetachOnPwrDn)
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI which may be different from the initial one. It is "idle updated".
Test Procedure
The SS indicates that IMSI detach/attach is not allowed. If possible the MS is switched off, then switched on, otherwise it has its power source removed and then restored (see b in PICS). The SS checks that the MS does not perform IMSI detach/attach procedures. If possible (if a = Yes, see PICS), the SIM is removed, then the SIM is inserted. The SS checks that the MS does not perform IMSI detach/attach procedures.
The SS indicates that IMSI detach/attach is allowed. After a delay of 35s the MS should have detected that the SS indicates now, that IMSI detach/attach is allowed. If possible (if b = Yes, see PICS) the MS is switched off, otherwise it has its power source removed (if d = Yes, see PICS). The MS initiates an IMSI detach procedure. Then depending on what has been performed before, the MS is switched on or has its power source restored. It initiates an IMSI attach procedure. The location updating procedure contains an implicit TMSI reallocation. The SIM is removed or power source is removed. If (a = yes and c = yes) or (a = no and d = yes) the MS initiates an IMSI detach procedure. Then the SIM is inserted or power source is restored, it initiates an IMSI attach procedure, the location updating procedure contains an implicit TMSI reallocation.
Maximum Duration of Test
4 min
Expected Sequence
Procedure 1
Step
Direction
Message
Comments
1
MS
If possible the MS is switched off (see b in PICS), otherwise the MS has its power source removed.
2
MS
The MS shall not initiate the IMSI detach procedure. This is checked by the SS during 5 s.
3
MS
Depending on what has been performed in step 1, the MS is brought back to operation.
4
MS
The MS shall not initiate an IMSI attach procedure. This is checked by the SS during 30 s.
Procedure 2
1
MS
If possible (a = Yes, see PICS), the SIM is removed from the MS.
2
MS
The MS shall not initiate the IMSI detach procedure. This is checked by the SS during 5 s.
3
MS
The SIM is inserted in the MS.
4
MS
The MS shall not initiate an IMSI attach procedure. This is checked by the SS during 30 s.
Procedure 3
1
MS
The MS is switched off, or has its power source removed, depending on value b in the PICS file. If b = Yes or d = Yes the MS initiates an IMSI detach procedure (steps A2, A3, A4, A5), otherwise the SS goes straight to step 6.
A2
MS -> SS
CHANNEL REQUEST
A3
SS -> MS
IMMEDIATE ASSIGNMENT
A4
MS -> SS
IMSI DETACH INDICATION
A5
SS -> MS
CHANNEL RELEASE
After the sending of this message, the SS waits the disconnection of the main signalling link.
6
MS
Depending on what has been performed in step 1, the MS is brought back to operation.
7
MS -> SS
CHANNEL REQUEST
The MS initiates an IMSI attach procedure.
8
SS -> MS
IMMEDIATE ASSIGNMENT
9
MS -> SS
LOCATION UPDATING REQUEST
"Location Updating Type" = IMSI attach.
10
SS -> MS
LOCATION UPDATING ACCEPT
The SS allocates a new TMSI
11
MS -> SS
TMSI REALLOCATION COMPLETE
12
SS -> MS
CHANNEL RELEASE
After the sending of this message, the SS waits the disconnection of the main signalling link.
Specific message contents:
SYSTEM INFORMATION TYPE 3 message:
Information Element
value/remark
Control Channel Description
- Attach/Detach allowed
MS shall apply IMSI attach and detach procedures.
Procedure 4
1
MS
The SIM is removed from the MS, or has its power source removed. If (a = Yes and c= Yes) or (a = no and d = yes) in PICS, the MS initiates an IMSI detach procedure (steps A2, A3, A4, A5), otherwise the SS goes straight to step 6.
A2
MS -> SS
CHANNEL REQUEST
A3
SS -> MS
IMMEDIATE ASSIGNMENT
A4
MS -> SS
IMSI DETACH INDICATION
A5
SS -> MS
CHANNEL RELEASE
After the sending of this message, the SS waits the disconnection of the main signalling link.
6
MS
Depending on what has been performed in step 1, the MS is brought back to operation.
7
MS -> SS
CHANNEL REQUEST
The MS initiates a IMSI attach procedure.
8
SS -> MS
IMMEDIATE ASSIGNMENT
9
MS -> SS
LOCATION UPDATING REQUEST
"Location Updating Type" = IMSI attach.
10
SS -> MS
LOCATION UPDATING ACCEPT
The SS allocates a new TMSI
11
MS -> SS
TMSI REALLOCATION COMPLETE
12
SS -> MS
CHANNEL RELEASE
After the sending of this message, the SS waits the disconnection of the main signalling link.
Specific message contents:
SYSTEM INFORMATION TYPE 3 message:
Information Element
value/remark
Control Channel Description
- Attach/Detach allowed
MS shall apply IMSI attach and detach procedures.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.3 Sequenced MM / CM message transfer
|
The RR sublayer of the MS shall have an associated send state variable V(SD) for sending MM and CM messages. This send state variable has been introduced to avoid the duplication of MM and CM messages. It is useful for the network after a handover or a change of channel to identify duplicated messages.
If the MS started V(SD) with 1 instead of 0 the network would incorrectly diagnose loss of message.
If the MS later on does not handle correctly incrementation of V(SD) the network would not be able to continue the dialogue.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.3.1 Conformance requirement
|
The MS shall implement correctly the "send state variable V(SD)" ("Send duplicated"), included in transmitted MM and CM messages.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.1.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.3.2 Test purpose
|
To verify that V(SD) is correctly set to 0 at the beginning of the establishment of the first RR connection and to verify that the MS handles correctly this variable in the special case of IDENTITY REQUEST messages, which are MM messages.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
The MS is paged. After reception of the PAGING RESPONSE message from the MS, the SS sends an IDENTITY REQUEST message. The MS sends an IDENTITY RESPONSE message where N(SD) = 0. The SS repeats its IDENTITY REQUEST message 10 times. The MS transmits IDENTITY RESPONSE message with the value 1 and 0 in the N(SD) field alternately.
Maximum Duration of Test
1 min
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
IDENTITY REQUEST
6
MS -> SS
IDENTITY RESPONSE
N(SD) = 0
7
SS -> MS
IDENTITY REQUEST
Steps 7, 8, 9 and 10 are repeated 5 times.
8
MS -> SS
IDENTITY RESPONSE
N(SD) = 1.
9
SS -> MS
IDENTITY REQUEST
10
MS -> SS
IDENTITY RESPONSE
N(SD) = 0.
11
SS -> MS
CHANNEL RELEASE
After the sending of this message, the SS waits the disconnection of the main signalling link.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.4 Establishment cause
|
The establishment cause set by the MS in the CHANNEL REQUEST message shall be consistent with the requested service or function, with the capabilities of the MS and with the indications given by the network.
If the MS uses a wrong establishment cause, the network might assign an inappropriate or incompatible resource.
In the case of Emergency call a wrong priority might be used.
If a reserved value is used, the network may discard the channel request.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.4.1 Conformance requirements
|
In the CHANNEL REQUEST message, the MS shall include an establishment cause which correspond to the establishment cause given by the MM sublayer and the broadcasted NECI value, or which correspond to one of the establishment causes "answer to paging" given by the RR entity in response to a PAGING REQUEST message including the Channel Needed information.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.3.1.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.4.2 Test purpose
|
To verify that the establishment cause sent by the MS in the Max-Retrans+1 CHANNEL REQUEST messages is consistent with the requested service, with the capabilities of the MS and with the indications of the network in the following cases:
1) If the MS supports a service on a traffic channel:
1.1 when the NECI bit is set to 0 and call re-establishment is attempted and the call was established on TCH/H if the MS supports a service on half rate channel or on TCH/F otherwise.
2) If the MS supports a service on half rate channel:
2.1 when the NECI bit is set to 1 and call re-establishment is attempted and the call was established on TCH/H.
3) If the MS supports speech:
3.1 when the NECI bit is set to 0 and a speech call is attempted.
3.2 when the NECI bit is set to 1 and a speech call is attempted.
4) If the MS supports a data service:
4.1 when the NECI bit is set to 0 and a data call is attempted.
4.2 when the NECI bit is set to 1 and a data call is attempted for a service supported on half rate channel (if the MS does not support any data call on half rate channel any data service is used).
5)
5.1 when the NECI bit is set to 0 and the MS is paged with the paging indication set to "any channel".
5.2 when the NECI bit is set to 0 and the MS is paged with the paging indication set to "SDCCH".
5.3 when the NECI bit is set to 0 and the MS is paged with the paging indication set to "TCH/F".
5.4 when the NECI bit is set to 0 and the MS is paged with the paging indication set to "TCH/H or TCH/F".
6)
6.1 when the NECI bit is set to 0 and IMSI attach is attempted.
6.2 when the NECI bit is set to 0 and normal location updating is attempted.
6.3 when the NECI bit is set to 0 and periodic location updating is attempted.
6.4 when the NECI bit is set to 0 and IMSI detach is attempted.
6.5 when the NECI bit is set to 1 and IMSI attach is attempted.
6.6 when the NECI bit is set to 1 and normal location updating is attempted.
6.7 when the NECI bit is set to 1 and periodic location updating is attempted.
6.8 when the NECI bit is set to 1 and IMSI detach is attempted.
7) If the MS supports a non call related supplementary service operation:
7.1 when the NECI bit is set to 0 and a supplementary service operation is attempted at the MS.
7.2 when the NECI bit is set to 1 and a supplementary service operation is attempted at the MS.
8) If the MS supports SMS/PP MO:
8.1 when the NECI bit is set to 0 and a mobile originated short message service transaction is attempted.
8.2 when the NECI bit is set to 1 and a mobile originated short message service transaction is attempted.
NOTE: To verify that when the MS supports speech and an emergency call is attempted and the NECI bit is set to 0, then the MS sends a CHANNEL REQUEST message with an establishment cause consistent with the requested service, with the capabilities of the MS and with the indications of the network is done in test 26.9.6.1.1 test purpose 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.2.4.3 Method of test
|
Initial Conditions
System Simulator:
for all procedures: 1 cell, Max-Retrans = 7 slots. The NECI bit is set to 0.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
- a: MS supports speech on TCH/F (TSPC_AddInfo_Full_rate_version_1)
- b: MS supports speech on TCH/H (TSPC_AddInfo_Half_rate_version_1)
- c: MS supports data on TCH/F (TSPC_AddInfo_FullRateData)
- d: MS supports data on TCH/H (TSPC_AddInfo_HalfRateData)
- e: MS only supports SDCCH (TSPC_AddInfo_SDCCHOnly)
- f: MS supports a supplementary service operation (TSPC_AddInfo_SS)
- g: MS supports SMS/PP MO (TSPC_Serv_TS22)
- h: On/Off switch (TSPC_Feat_OnOff)
- i: MS supports AMR (TSPC_AddInfo_Full_rate_version_3)
- j: MS supports Speech for Half Rate Version 3 (TSPC_AddInfo_Half_rate_version_3)
NOTE: In the above PICS, data and speech refer to the Radio Resource Channel Mode.
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedures
NOTE: If the procedures are chained, the SS shall ensure that at the beginning of each procedure, the initial conditions are reached and that the MS had enough time to decode the broadcasted parameters.
Procedure 1
If the MS supports a service on a traffic channel:
A call is established on TCH/H if the MS supports a service on half rate channel or on TCH/F otherwise. The SS stops transmission on the SACCH. The MS attempts call reestablishment. The SS does not answer to Max‑Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "110".
Procedure 2
If the MS supports a service on half rate channel:
The NECI bit is set to 1. A call is established on TCH/H for a supported service. The SS stops transmission on the SACCH. The MS attempts call reestablishment. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "011010".
Procedure 3
If the MS supports speech:
A speech call is attempted. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "111". The NECI bit is set to 1. A speech call is attempted. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "111" if the MS does not support speech on half rate channel (version 1, GSM, nor version 3, AMR) or "0100" if the MS supports speech on half rate channel (version 1, GSM, or/and version 3, AMR).
Procedure 4
If the MS supports a data service:
A data call is attempted. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "111". The NECI bit is set to 1. A data call is attempted for a service supported on half rate channel (if the MS does not support any data call on half rate channel any data service is used). The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "111"if the MS does not support a data service on half rate channel or "0101" if the MS supports a data service on half rate channel.
Procedure 5
The MS is paged with the paging indication set to "any channel". The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "100". The SS waits for a time sufficient for the MS to be "idle updated". The MS is paged with the paging indication set to "SDCCH". The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "0001". The SS waits for a time sufficient for the MS to be "idle updated". The MS is paged with he paging indication set to "TCH/F". The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "100" if the MS capability is full rate only, "0010" if the MS capability is dual rate and "0001" if the MS capability is SDCCH only. The SS waits for a time sufficient for the MS to be "idle updated". The MS is paged with the paging indication set to "TCH/H or TCH/F". The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "100" if the MS capability is full rate only, "0011" if the MS capability is dual rate and "0001" if the MS capability is SDCCH only.
Procedure 6
This procedure is performed twice. Once for NECI = 0 and once for NECI = 1.
The MS is switched off or powered off. Then system information messages are altered so that IMSI attach/detach is allowed in the cell. The MS is switched on or powered on. The MS performs IMSI attach. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the values "0000" when NECI = 1, or "000" when NECI = 0. The IMSI attach procedure is followed. The location area code of the cell is changed, T3212 is set to 1 deci-hour. The MS performs a location updating. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the values "0000" when NECI = 1, or "000" when NECI = 0. The location updating procedure is followed. The SS waits for at least 7 minutes. The MS performs a periodic updating. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the values "0000". The location updating procedure is followed. The MS is switched off or powered off. If the MS has an On/off switch (see PICS), it attempts IMSI detach. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "0001" when NECI = 1, or "111" when NECI = 0.
Procedure 7
This procedure is performed twice. Once for NECI = 0 and once for NECI = 1.
If the MS supports a non call related supplementary service operation:
A supplementary service operation is attempted at the MS. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "0001".
Procedure 8
If the MS supports SMS/PP MO:
A mobile originated short message service transaction is attempted. The SS does not answer to Max-Retrans CHANNEL REQUEST messages and answers to the next CHANNEL REQUEST with an IMMEDIATE ASSIGNMENT REJECT message. The SS checks that all CHANNEL REQUEST messages contain an establishment cause with the value "0001" when NECI = 1, or "111" when NECI = 0.
Maximum Duration of Test
For procedures 1, 2, 3, 4 and 5: 5 minutes, including 1 minute for any necessary operator actions.
For procedure 6: 20 minutes, including 2 minutes for any necessary operator actions.
For procedures 7, 8: 10 minutes, including 2 minutes for any necessary operator actions.
Expected Sequence
Procedure 1
This procedure is performed if the MS supports a service on a traffic channel.
Step
Direction
Message
Comments
1
a call is established on TCH/H if the MS supports a service on half rate channel or on TCH/F otherwise. The generic call setup procedure is used.
2
SS
the SS stops transmission on the SACCH.
3
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "110"
4
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 2
This procedure is performed if the MS supports a service on half rate channel.
Step
Direction
Message
Comments
1
SS
The NECI bit is set to 1, a call is established on
2
TCH/H for a supported service. The generic call setup procedure is used.
3
SS
the SS stops transmission on the SACCH.
4
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "011010"
5
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 3
This procedure is performed if the MS supports speech.
Step
Direction
Message
Comments
1
MS
a speech call is attempted
2
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "111"
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
4
SS
The NECI bit is set to 1
5
SS
The SS waits for 30 s
6
MS
a speech call is attempted
7
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "0100" if the MS supports speech (GSM and/or AMR) on half rate or set to "111" otherwise
8
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 4
This procedure is performed if the MS supports a data service.
Step
Direction
Message
Comments
1
MS
a data call is attempted
2
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "111"
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
4
SS
The NECI bit is set to 1
5
SS
The SS waits for 30 s
6
MS
a data call is attempted for a service supported by the MS on half rate (for any data service if the MS does not support any data service on half rate)
7
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "0101" if the MS supports a data service on half rate or set to "111" otherwise
8
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 5
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
paging indication = any channel
2
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "100"
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
4
SS
The SS waits for 5 s
5
SS -> MS
PAGING REQUEST TYPE 1
paging indication = SDCCH
6
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "0001"
7
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
8
SS
The SS waits for 5 s
9
SS -> MS
PAGING REQUEST TYPE 1
paging indication = TCH/F
10
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "100" if the MS capability is full rate only or "0010" if the MS capability is dual rate or "0001" if the MS capability is SDCCH only
11
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
12
SS
The SS waits for 5 s
13
SS -> MS
PAGING REQUEST TYPE 1
paging indication = TCH/H or TCH/F
14
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to "100" if the MS capability is full rate only or "0011" if the MS capability is dual rate or "0001" if the MS capability is SDCCH only
15
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 6
The sequence is executed for execution counter k = 1, 2.
Step
Direction
Message
Comments
0
SS
When k = 1, NECI set to 0 When k = 2, NECI set to 1
1
MS
The MS is switched off or has its power source removed
2
SS
IMSI attach/detach is set to "MSs in the cell shall apply IMSI attach and detach procedure"
3
MS
The MS is switched on or powered on
4
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "000" when k = 1 "0000" when k = 2
5
SS -> MS
IMMEDIATE ASSIGNMENT
6
MS -> SS
LOCATION UPDATING REQUEST
"location updating type" = IMSI attach
7
SS -> MS
LOCATION UPDATING ACCEPT
with no mobile identity
8
SS -> MS
CHANNEL RELEASE
9
SS
the LAC of the cell is changed and T3212 is set to 6 minutes
10
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "000" when k = 1 "0000" when k = 2. The MS must send its first Channel Request within 33s after the LAC has been changed.
11
SS -> MS
IMMEDIATE ASSIGNMENT
12
MS -> SS
LOCATION UPDATING REQUEST
"location updating type" = Normal location updating
13
SS -> MS
LOCATION UPDATING ACCEPT
with no mobile identity
14
SS -> MS
CHANNEL RELEASE
15
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "000" when k = 1 "0000" when k = 2. The MS must send its first Channel Request within 7 minutes after the preceeding Channel Release
16
SS -> MS
IMMEDIATE ASSIGNMENT
17
MS -> SS
LOCATION UPDATING REQUEST
"location updating type" = Periodic updating
18
SS -> MS
LOCATION UPDATING ACCEPT
with no mobile identity
19
SS -> MS
CHANNEL RELEASE
20
MS
If possible (see PICS), the MS is switched off, otherwise it has its power source removed
21
MS
If the MS was switched off it attempts IMSI detach
22
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "111" when k = 1 "0001" when k = 2
23
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 7
The sequence is executed for execution counter k = 1, 2.
This procedure is performed if the MS supports a non call related supplementary service operation.
Step
Direction
Message
Comments
0
SS
When k = 1, NECI set to 0 When k = 2, NECI set to 1
1
MS
a non call related supplementary service operation is attempted
2
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "111" when k = 1 "0001" when k = 2
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Procedure 8
This procedure is performed if the MS supports SMS/PP MO.
The sequence is executed for execution counter k = 1, 2.
Step
Direction
Message
Comments
0
SS
When k = 1, NECI set to 0 When k = 2, NECI set to 1
1
MS
a mobile originated short message service transaction is attempted
2
MS -> SS
8 CHANNEL REQUEST
all messages have establishment cause set to: "111" when k = 1 "0001" when k = 2
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3 Test of MS functions in idle mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.1 Initial conditions
|
The SIM shall contain a PLMN-Selector that contains only the HPLMN of the MS, and an empty forbidden PLMN list.
Related PICS/PIXIT statements
During the tests in subclauses 26.3.2 and 26.3.3, the following parameters apply according to the above PICS/PIXIT statement:
RACH control parameters
In cells:
GSM 400: 1 to 7;
GSM 710: 1 to 7;
GSM 750: 1 to 7;
T-GSM 810: 1 to 7;GSM 850: 1 to 7;
GSM 900: 1 to 7;
DCS 1 800: 1 to 6;
PCS 1 900: 1 to 6;
Multiband 900/1 800: 1 to 7;
Multiband 450/900: 1 to 7;
Multiband 480/900: 1 to 7;
Multiband 450/1 800: 1 to 7;
Multiband 480/1 800: 1 to 7;
Multiband 850/1 900: 1 to 7.
Max retrans = 01 2 retransmissions
Tx-integer = 0111 (10) slots for spreading
CB, Cell Barred = 0 access is allowed
RE = 1 re-establishment not allowed
AC C00 to AC C15 = 0 access is not barred
In cell:
GSM 400: 8;
GSM710: 8;
GSM 750: 8;
GSM 810: 8;
GSM 850: 8;
GSM 900: 8;
DCS 1 800: 7;
PCS 1 900: 7;
Multiband 900/1 800: 8;
Multiband 450/900: 8;
Multiband 480/900: 8;
Multiband 450/1 800: 8;
Multiband 480/1 800: 8.
Max retrans = 01 2 retransmissions
Tx-integer = 0111 (10) slots for spreading
CB, Cell Barred = 1 access is not allowed
RE = 1 re-establishment not allowed
AC C00 to AC C15 = 0 access is not barred
GSM 900
DCS 1 800
Cell
PLMN
perm.
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
7
39
65
66
85
97
124
520
580
610
702
703
830
885
2
00000100
8
40
67
68
86
98
123
521
581
612
704
705
831
884
3
00000100
9
41
69
70
87
99
122
522
582
614
706
707
832
883
4
00000100
10
42
71
72
88
100
121
523
583
616
708
709
833
882
5
00000100
11
43
73
74
89
101
120
524
584
618
710
711
844
881
6
00000100
12
44
75
76
90
102
119
525
585
620
712
713
835
880
7
00000100
13
45
77
78
91
103
118
526
586
622
714
715
836
879
8
00000100
124
GSM 450
GSM 480
Cell
PLMN
perm.
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
261
267
268
281
288
291
293
308
314
315
328
335
338
340
2
00000100
260
269
270
282
289
264
275
307
316
317
329
336
311
322
3
00000100
262
271
272
283
290
265
277
309
318
319
330
337
312
324
4
00000100
263
273
274
284
292
266
279
310
320
321
331
339
313
326
5
00000100
264
275
276
285
260
269
270
311
322
323
332
307
316
317
6
00000100
265
277
278
286
262
271
272
312
324
325
333
309
318
319
7
00000100
266
279
280
287
263
273
274
313
326
327
334
310
320
321
8
00000100
293
340
GSM 710 OR GSM 750 OR T-GSM 810
GSM 850
Cell
PLMN
perm.
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
444
456
472
473
489
497
511
134
166
192
193
212
224
251
2
00000100
445
457
474
475
490
498
510
135
167
194
195
213
225
250
3
00000100
446
458
476
477
491
499
509
136
168
196
197
214
226
249
4
00000100
447
459
478
479
492
500
508
137
169
198
199
215
227
248
5
00000100
448
460
480
481
493
501
507
138
170
200
201
216
228
247
6
00000100
449
461
482
483
494
502
506
139
171
202
203
217
229
246
7
00000100
450
462
484
485
495
503
505
140
172
204
205
218
230
245
8
00000100
511
251
PCS 1 900
Multiband 850/1900
Cell
PLMN
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
512
520
580
610
702
703
800
134
166
610
193
212
810
251
2
00000100
513
521
581
612
704
705
801
135
167
194
195
213
225
250
3
00000100
514
522
582
614
706
707
802
136
168
196
197
214
226
249
4
00000100
515
523
583
616
708
709
803
523
583
524
585
616
708
709
5
00000100
516
524
584
618
710
711
804
520
170
200
702
216
805
247
6
00000100
517
525
585
620
712
713
805
139
171
202
203
217
229
246
7
00000100
518
526
586
622
714
715
806
526
586
622
714
715
786
808
8
00000100
251
Multiband 900/1800
Cell
PLMN
perm.
BA - ARFCN bit = 1
1
00000100
7
39
702
66
85
885
124
2
00000100
8
40
67
68
86
98
123
3
00000100
9
41
69
70
87
99
122
4
00000100
523
583
616
708
709
833
882
5
00000100
520
7
39
702
85
885
124
6
00000100
12
44
75
76
90
102
119
7
00000100
526
586
622
714
715
836
879
8
00000100
124
Multiband 450/900
Multiband 480/900
Cell
PLMN
perm.
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
261
267
65
281
288
124
293
308
314
65
328
335
124
340
2
00000100
260
269
270
282
289
264
275
307
316
317
329
336
311
322
3
00000100
262
271
272
283
290
265
277
309
318
319
330
337
312
324
4
00000100
10
42
71
72
88
100
121
10
42
71
72
88
100
121
5
00000100
7
260
267
65
288
124
293
7
307
314
65
335
124
340
6
00000100
265
277
278
286
262
271
272
312
324
325
333
309
318
319
7
00000100
13
45
77
78
91
103
118
13
45
77
78
91
103
118
8
00000100
293
340
Multiband 450/1800
Multiband 480/1800
Cell
PLMN
perm.
BA - ARFCN bit = 1
BA - ARFCN bit = 1
1
00000100
261
267
702
281
288
885
293
308
314
702
328
335
885
340
2
00000100
260
269
270
282
289
264
275
307
316
317
329
336
311
322
3
00000100
262
271
272
283
290
265
277
309
318
319
330
337
312
324
4
00000100
523
583
616
708
709
833
882
523
583
616
708
709
833
882
5
00000100
520
260
267
702
288
885
293
520
307
314
702
335
885
340
6
00000100
265
277
278
286
262
271
272
312
324
325
333
309
318
319
7
00000100
526
586
622
714
715
836
879
526
586
622
714
715
836
879
8
00000100
293
340
Location area identification
GSM 400, GSM 710, GSM 750, T-GSM 810, GSM 850 and GSM 900 only - begin
Cell
MCC1
MCC2
MCC3
MNC1
MNC2
LAC
1
0
0
2
0
F
x
2
0
0
3
2
F
x
3
0
0
4
3
F
x
4
0
0
5
4
F
x
5
0
0
6
5
F
x
6
0
0
7
6
F
x
7
0
0
8
7
F
x
8
0
0
1
0
1
x
The HPLMN of the MS
GSM 400, GSM 710, GSM 750, T-GSM 810, GSM 850 and GSM 900 only - end
DCS 1 800 only - begin
Cell
MCC1
MCC2
MCC3
MNC1
MNC2
LAC
1
0
0
2
0
F
x
2
0
0
3
2
F
x
3
0
0
4
3
F
x
4
0
0
5
4
F
x
5
0
0
6
5
F
x
6
0
0
7
6
F
x
7
0
0
1
0
1
x
The HPLMN of the MS
DCS 1 800 only – end
PCS 1 900 only – begin
Cell
MCC1
MCC2
MCC3
MNC1
MNC2
MNC3
LAC
1
0
0
2
0
F
F
x
2
0
0
3
2
F
F
x
3
0
0
4
3
F
F
x
4
0
0
5
4
F
F
x
5
0
0
6
5
F
F
x
6
0
0
7
6
F
F
x
7
0
0
1
0
1
1
x
The HPLMN of the MS
GSM 1900 only - end
Any Multiband MS - begin
Cell
MCC1
MCC2
MCC3
MNC1
MNC2
LAC
1
0
0
2
0
F
x
2
0
0
3
2
F
x
3
0
0
4
3
F
x
4
0
0
5
4
F
x
5
0
0
2
0
F
x
6
0
0
7
6
F
x
7
0
0
8
7
F
x
8
0
0
1
0
1
x
The HPLMN of the MS
Any Multiband MS - end
NOTE 1: 'x' denotes any value.
NOTE 2: The MS representation of the MCC, MNC on the handset can be manufacturer dependant.
NOTE 3: The NCC values of each cell must be different.
Control channel description and BS options
All:
GSM 400: 8 cells;
GSM 710: 8 cells;
GSM 750: 8 cells;
T-GSM 810: 8 cells;
GSM 850: 8 cells;
GSM 900: 8 cells;
DCS 1 800: 7 cells;
PCS 1 900: 7 cells;
Any Multiband MS: 8 cells.
CELL_RESELECT_HYSTERESIS = 010 4dB RXLEV hysteresis
MS_TXPWR_MAX_CCH = value corresponding to the maximum
available output power from MS
RXLEV_ACCESS_MIN = 30
ATT = 0 no IMSI attach and detach
DTX = 0 no discontinuous transmission
BS_AG_BLKS_RES = 1 1 block reserved for access grant
CCCH_CONF = 001 1 SDCCH combined with the CCCH
RADIO_LINK_TIMEOUT = 5 10 s time-out
BS_PA_MFRMS = 010 4 multiframes periods for paging
T3212 time-out value = H'00
GSM 900
DCS 1 800
Cell
level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
1
+65
520
2
+63
7
+63
580
3
+61
39
+61
610
4
+55
65
+55
702
5
+59
66
+59
703
6
+57
85
+57
830
7
+55
97
+55
885
8
+53
124
GSM 450
DCS 480
Cell
level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
259
+65
306
2
+63
261
+63
308
3
+61
267
+61
314
4
+55
268
+55
315
5
+59
281
+59
328
6
+57
288
+57
335
7
+55
291
+55
338
8
+53
293
+53
340
Multiband 900/1800
PCS 1 900
Cell
level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
520
+65
512
2
+63
7
+63
520
3
+61
39
+61
580
4
+55
702
+55
610
5
+59
66
+59
702
6
+57
85
+57
703
7
+55
885
+55
800
8
+53
124
Multiband 450/900
Multiband 480/900
Cell
level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
1
+65
1
2
+63
261
+63
308
3
+61
267
+61
314
4
+55
65
+55
65
5
+59
281
+59
328
6
+57
288
+57
335
7
+55
124
+55
124
8
+53
293
+53
340
Multiband 450/1800
Multiband 480/1800
Cell
level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
520
+65
520
2
+63
261
+63
308
3
+61
267
+61
314
4
+55
702
+55
702
5
+59
281
+59
328
6
+57
288
+57
335
7
+55
885
+55
885
8
+53
293
+53
340
GSM 710 or GSM 750 or T-GSM 810
GSM0 850
Cell
Level
dBVemf( )
BCCH ARFCN
level
dBVemf( )
BCCH ARFCN
1
+65
438
+65
128
2
+63
444
+63
134
3
+61
456
+61
166
4
+55
472
+55
192
5
+59
473
+59
193
6
+57
489
+57
212
7
+55
497
+55
224
8
+53
511
+53
251
GSM 850/1900
Cell
level
dBVemf( )
BCCH ARFCN
1
+65
512
2
+63
134
3
+61
166
4
+55
610
5
+59
193
6
+57
212
7
+55
810
8
+53
251
For testing an E-GSM Mobile station (see PICS/PIXIT), the BCCH ARFCN of cell 7 at GSM 900 column shall be 985 (instead of 97). For testing an R-GSM or an ER-GSM Mobile station (see PICS/PIXIT), the BCCH ARFCN od cell 7 at GSM 900 column shall be 965 (instead of 97).
NOTE 4: The SIM should contain a PLMN-Selector that contains only the HPLMN of the MS, and an empty forbidden PLMN list.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.2 MS indication of available PLMNs
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.2.1 Test purpose
|
To verify that a MS can present the available PLMNs to the user when asked to do so in manual mode according to the requirements of 3GPP TS 05.08 and 3GPP TS 02.11.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.2.2 Method of test
|
a) The MS is switched on, equipped with a SIM containing default values except for those values listed under subclause 26.3.1 (initial conditions).
b) The MS is put into manual network selection mode (see PIXIT).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.2.3 Test requirements
|
1) On entering manual network selection mode, the MS shall present a list of available PLMNs in all its bands of operation (MCC and MNC values, or any other valid indications, see PIXIT), within 2 minutes. Any PLMN shall only be presented once. The list shall include the MCC and MNC of:
GSM 400, GSM 710, GSM 750, T-GSM 810 , GSM 850 and GSM 900: cells 1 to 7, but not of cell 8.
DCS 1 800: cells 1 to 6, but not of cell 7.
PCS 1 900: cells 1 to 6, but not of cell 7.
Multiband: cells 2, 3, 4, 6, 7 and 1 or 5 (cell 1 and 5 have the same MCC and MNC), but not of cell 8.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3 MS will send only if BSS is "on air"
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.1 Test purpose
|
To verify that the MS will not produce any RF transmission if no BSS is received.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.2 Method of test
|
a) The RF-signal for the BCCHs of:
GSM 400, GSM 710, GSM 750, T-GSM 810, GSM 850 and GSM 900: cell 1 to 8 is switched off.
DCS 1 800: cell 1 to 7 is switched off.
PCS 1 900: cell 1 to 7 is switched off.
Any Multiband: cell 1 to 8 is switched off.
b) The SS shall wait 20 s to allow the MS to detect the loss of cells.
c) By MMI, an attempt to originate a call is made.
d) By MMI, an attempt to originate an emergency call is made.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.3 Test requirements
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.3.1 General test requirements
|
1) The MS must not give "service indication".
2) In steps c) and d) the MS shall not produce any RF output.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.3.2 Test Procedures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.3.2.1 Test Procedure 1
|
For MS not supporting speech (see PICS) perform steps a, b, and c.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.3.3.2.2 Test Procedure 2
|
For MS supporting speech (see PICS) perform steps a, b, c and d.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.4 Manual mode of PLMN selection
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.4.1 Conformance requirements
|
In manual mode, the MS can try to obtain normal service on any available VPLMN and it shall try to obtain normal service on a VPLMN if and only if the user makes a manual selection of this VPLMN.
Reference
3GPP TS 03.22 subclause 3.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.4.2 Test purpose
|
To check that in manual mode the MS is able to obtain normal service on a PLMN which is neither the better nor a preferred PLMN and that it tries to obtain service on VPLMN if and only if the user selects it manually.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.3.4.3 Method of test
|
Initial conditions
System Simulator:
2 cells, defaults parameter unless otherwise specified.
The SS transmits 2 BCCH carriers in the supported band(s) of the mobile station (for a multiband MS carrier A and B shall be in different bands) with the initial following parameters:
level (dBVemf)
carrier A
PLMN 1
38
carrier B
PLMN 2
33
Mobile Station:
The MS is "idle updated" on PLMN1 (HPLMN) and is in manual mode.
The preferred PLMN list does not contain PLMN2, it contains PLMN 3.
Specific PICS statements:
- Support of multiband functionality (TSPC_Type_MB_Simul)
PIXIT Statements:
- Description of the manual PLMN selector.
Foreseen final state of the MS
The MS is "idle updated".
Test procedure
For the different networks and during the whole test, "IMSI attach" flag is set in the BCCH data.
Carrier A is turned off. The MS does not attempt a location updating during 2 minutes.
Carrier A is turned back on with a different MCC-MNC (indicating PLMN 3) and with a higher level (48 dBmVemf) than PLMN 2. The MS does not attempt a location updating during 2 minutes.
PLMN 2 is selected manually. The MS performs a location updating on PLMN 2. Carrier B is turned off. The MS does not attempt a location updating during 2 minutes.
Maximum duration of test
10 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS
carrier A is turned off
2
wait 2 min: the MS shall not send any CHANNEL REQUEST messages during this time
3
SS
carrier A is turned on with a different MNC-NCC (PLMN3) and with a high level (48dBmVemf)
4
wait 2 min: the MS shall not send any CHANNEL REQUEST messages during this time
5
MS
PLMN 2 selected manually
6
MS -> SS
CHANNEL REQUEST
7
SS -> MS
IMMEDIATE ASSIGNMENT
8
MS -> SS
LOCATION UPDATING REQUEST
on carrier B
9
SS -> MS
LOCATION UPDATING ACCEPT
10
SS -> MS
CHANNEL RELEASE
11
SS
carrier B is turned off
12
wait 2 min: the MS shall not send any CHANNEL REQUEST messages during this time
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.4 Lower layer failures in layer 3 testing
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.4.1 Introduction
|
The text in this subclause is intended to develop a standardized way of creating lower layer failures whilst testing the performance of Layer 3 signalling.
There are two groups of lower layer failures:
1) Detected by analysis of reception at Layer 1 (3GPP TS 05.08, 3GPP TS 04.08 / 3GPP TS 44.018),
2) Data link layer failures.
References
3GPP TS 04.08 / 3GPP TS 44.018, 3GPP TS 04.06, 3GPP TS 05.08
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.