26.22 Test of other features
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.22.1 Layer 2 fill bits randomisation
26.22.1.1 Conformance requirements
The end of the useful part of the frame, i.e. the octets following the length indicator field in type A frames and the octets following the information field in type B frames, is determined by a length indicator contained in the length indicator field. The useful part of a Bbis frames takes all N201 octets of that frame. The useful part of a Bter frame takes all N201 octets of that frame except those bits of octet 1 which contain the short L2 header type 1. The useful part of a B4 frame takes all N201 octets of that frame except those octets which contain the address field and the control field.
If a frame contains a length indicator that has a value less than N201, the frame contains fill bits. Each fill bit shall be set to a random value when sent by the mobile station. Except for the first octet containing fill bits which shall be set to the binary value "00101011", each fill bit should be set to a random value when sent by the network. Otherwise, the network shall set all octets containing fill bits to the binary value "00101011".
References
3GPP TS 44.006 subclause 5.2.
26.22.1.2 Test purpose
An MS shall correctly decode all LAPDm frames with randomised fill bits.
An MS supporting randomisation of fill bits in the Uplink direction shall a) correctly encode the first octet of a frame containing fill bytes and b) send a random sequence of bits during a signalling sequence.
26.22.1.3 Method of Test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is switched off.
Specific PICS statements:
– L2 fill bits randomisation in uplink (TSPC_UL_L2_Fill_Bits_Randomisation)
– at least one short message service (TSPC_AddInfo_SMS)
– MSsupporting at least one bearer capability service (TSPC_AddInfo_CCprotocol_oneBC)
– Immediate connect supported for all circuit switched basic services. (TSPC_AddInfo_ImmConn)
PIXIT statements:
– Way to indicate alerting.
– Way to make the MS accept an incoming call after alerting.
Foreseen Final State of MS
"Idle, updated", with TMSI allocated.
Test Procedure
During the following procedures:
– the SS randomises the fill bits in all layers 2 frames in downlink frames sent to the MS.
– If MS supports fill bits randomisation in uplink all fill bits from l2 frames sent from the MS are recorded by the SS.
MS is powered on. A normal location updating with TMSI reallocation is performed on Cell A. The channel is released.
If the MS supports SMS, the MS triggers MO-SMS. The SS responds to the channel request message by allocating an SDCCH. The SS answers correctly to the SABM on SAPI 0 and then performs the authentication and ciphering procedures. The SS responds with a UA frame SAPI 3 to the MS and continues with the SMS procedures. The SS sends a channel release message.
If the MS supports CC protocol for at least one Bearer Capability, the MS is paged and MT-call is established. Having reached the active state, the MS is made to clear the call.
If the MS supports L2 fill bits randomisation in uplink, the SS will
– Verify that the L2 fill bits in uplink message do not contain only “00101011” pattern
– Concatenate all random fill bits sent by MS into sequence buffer
– Verify in this buffer, that there is no repeated occurrence of 32 bit pattern
Maximum Duration of Test
3 minutes
Expected Sequence
Step |
Direction |
Message |
Comments |
SS |
The SS sends random fill bytes as specified in 44.006 sub-clause 5.2 on SDCCH and/or FACCH channels throughout the test. |
||
MS |
If the MS supports randomisation of fill bits, during the expected sequence, the MS sends random fill bytes as specified in 44.006 sub-clause 5.2. The SS records all random fill bits in the sequence on the SDCCH and/or FACCH from all L2 frames with coded fill bits where L < N201 (UI, I, RR, etc) and stores for post analysis. |
||
1 |
MS |
The MS is switched on. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
LOCATION UPDATING REQUEST |
Message is contained in SABM. Location Updating Type = "Normal location updating" or "IMSI Attach". |
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
9 |
SS starts ciphering |
||
10 |
SS -> MS |
LOCATION UPDATING ACCEPT |
|
11 |
MS -> SS |
TMSI REALLOCATION COMPLETE |
|
12 |
SS -> MS |
CHANNEL RELEASE |
|
13 |
SS |
If the MS supports randomisation of fill bits, the SS verifies the received fill bits are random for this signalling sequence. |
|
14a |
Steps 14b – 30 will be executed only if the MS supports at least one short message service |
||
14b |
MS |
MS is made to initiate a MO SMS. |
|
15 |
MS->SS |
CHANNEL REQUEST |
Establishment cause indicates the relevant cause value (see 3GPP TS 44.018 Table 9.1.8.1). |
16 |
SS->MS |
IMMEDIATE ASSIGNMENT |
|
17 |
MS -> SS |
CM SERVICE REQUEST |
CM Service Type = "Short message service". |
18 |
SS -> MS |
AUTHENTICATION REQUEST |
|
19 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
20 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
21 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered. |
22 |
SS |
SS starts ciphering. |
|
23 |
MS -> SS |
SABM (SAPI=3) |
MS establishes SAPI 3 |
24 |
SS -> MS |
UA (SAPI=3) |
|
25 |
MS -> SS |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
26 |
SS -> MS |
CP-ACK |
|
27 |
SS -> MS |
CP-DATA |
Contains RP-ACK RPDU. |
28 |
MS -> SS |
CP-ACK |
|
29 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
30 |
SS |
If the MS supports randomisation of fill bits, the SS verifies the received fill bits are random for this signalling sequence. |
|
31 |
Steps 32 -55 will be executed only if the MS supports mobile terminating calls. |
||
32 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging sub-channel. |
33 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates the relevant answer to paging cause value (see 3GPP TS 44.018 Table 9.1.8.1). |
34 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
35 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM |
36 |
SS -> MS |
AUTHENTICATION REQUEST |
|
37 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value. |
38 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message. |
39 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
40 |
SS |
SS starts ciphering |
|
41 |
SS -> MS |
SETUP |
Message contains the signal IE. |
42 |
MS -> SS |
CALL CONFIRMED |
|
43A |
MS -> SS |
CONNECT |
|
43B |
MS -> SS |
ALERTING |
|
44B |
MS |
An alerting indication as defined in a PICS/PIXIT statement given by the MS |
|
45B |
MS |
The MS is made to accept the call in a way described in a PICS/PIXIT statement |
|
46B |
MS -> SS |
CONNECT |
|
47 |
SS -> MS |
ASSIGNMENT COMMAND |
|
48 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
49 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
50 |
MS |
The MS is made to release the call. |
|
51 |
MS -> SS |
DISCONNECT |
|
52 |
SS -> MS |
RELEASE |
|
53 |
MS -> SS |
RELEASE COMPLETE |
|
54 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
55 |
SS |
If the MS supports randomisation of fill bits, the SS verifies the received fill bits are random for this signalling sequence. |