hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.7 Handover / successful / active call / non-synchronized / reporting of observed time difference requested
|
If an MS does not report the observed time difference between cells correctly then pseudo synchronized handovers might not be possible for any MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.7.1 Conformance requirements
|
1 The MS shall correctly apply the handover procedure from a TCH/F without frequency hopping to a TCH/F without frequency hopping in the non-synchronized case while a call is active.
2 When requested to do so in the HANDOVER COMMAND message, the MS shall return the Mobile Time Difference IE in the HANDOVER COMPLETE message indicating the sum of the observed time difference between the cells and the timing advance used on the old cell.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.4.4.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018, subclause 10.5.2.39.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.7.2 Test purpose
|
To verify that when the MS is ordered to make a non-synchronized handover to another cell and is ordered to report on the time difference between the cells, that it does so correctly.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.7.3 Method of test
|
Initial Conditions
System Simulator:
2 cells, A and B with default parameters except the LAI of cell B has MNC = 02 (PCS 1 900: MNC = 021) decimal,
MCC = 315 decimal, and LAC = 5344 H.
The BCCH of cell A is sent k bit periods before the BCCH of cell B.
The MS is commanded to use a timing advance of y bit periods on cell A.
Mobile Station:
The MS is in the active state (U10) of a call (on cell A) using a full rate TCH in non-hopping mode.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
The active state (U10) of a mobile call (on cell B) using a full rate TCH in non-hopping mode.
Test Procedure
The MS is in the active state (U10) of a call on cell A. The SS sends a HANDOVER COMMAND on the main DCCH. The HANDOVER COMMAND includes a Synchronization Indication IE that instructs the MS to supply the observed time difference between the cells. The MS shall begin to send access bursts on the new DCCH (and otionally the SACCH) to cell B and the SS sends one PHYSICAL INFORMATION message. The MS shall activate the channel in sending and receiving mode and establish a signalling link using the correct timing advance. The MS shall transmit a HANDOVER COMPLETE message containing the Mobile Time Difference IE with a correct value.
Maximum Duration of Test
5 s.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
HANDOVER COMMAND
See specific message contents below.
2
MS -> SS
HANDOVER ACCESS
Repeated on every burst of the uplink main DCCH until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND.
3
SS -> MS
PHYSICAL INFORMATION
4
MS -> SS
SABM
Sent without information field.
5
SS -> MS
UA
6
MS -> SS
HANDOVER COMPLETE
Shall include the Mobile Time Difference IE with value (2k+y) mod 2,097,152 half bit periods. A tolerance of ±2 half bit periods is allowed.
Specific Message Contents
HANDOVER COMMAND
as default message contents, except:
Synchronization Indication
"not synchronized"; ROT=1; NCI=0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.8 Handover / layer 3 failure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.8.1 Conformance requirements
|
The MS shall return to the old channel in the case of an handover failure caused by the non reception of the PHYSICAL INFORMATION message. On the old channel the MS shall use the Power Level that it was previously using on that channel.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.8.2 Test purpose
|
To verify the function of timer T3124 and the contents in the message HANDOVER FAILURE and in the layer 1 header on the SACCH.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.8.3 Method of test
|
Initial Conditions
System Simulator:
2 cells with same LAI, default parameters.
Mobile Station:
The MS is in the active state (U10) of a call (on cell A). Used power level is the maximum supported by the MS.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
The active state (U10) of a mobile call (on cell A). Used power level is the maximum supported by the MS.
Test Procedure
The MS is in the active state (U10) of a call on cell A. The SS sends a HANDOVER COMMAND with Power Command set to 8 on the main DCCH. The MS shall begin to send access bursts on the new DCCH (and optionally the SACCH) to cell B. The SS activates the SACCH, but does not send PHYSICAL INFORMATION (thus causing a time-out of T3124). The MS shall re-establish the old link on cell A and send a HANDOVER FAILURE within 3 s from the transmission of HANDOVER COMMAND, using the old Power Control Level.
Maximum Duration of Test
5 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
Step
Direction
Message
Comments
0
SS
-
The SS records the Power Control Level in the layer 1 header of the last SACCH message sent by the MS before step 1.
1
SS -> MS
HANDOVER COMMAND
Channel description: non-hopping, full rate Power Command: 8. Synchronization Indication: non synchronized.
2
MS -> SS
HANDOVER ACCESS
Several messages are sent, all with correct Handover References.
3
MS -> SS
HANDOVER FAILURE
Sent on old channel, RR cause value = "Abnormal release, unspecified", "Abnormal release, channel unacceptable", "Abnormal release, timer expired", "Abnormal release, no activity on the radio path" or "Protocol error unspecified". Shall be sent within 3 s from the transmission of HANDOVER COMMAND.
4
SS
-
The SS checks that the Power Control Level reported in the layer 1 header of the SACCH message that is sent in the first SACCH multiframe following the SABM is the same as in step 0.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.9 Handover / layer 1 failure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.9.1 Conformance requirements
|
The MS shall return to the old channel in the case of an handover failure caused by a layer 1 failure on the target cell. On the old channel the MS shall use the Power Level that it was previously using on that channel.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.9.2 Test purpose
|
To verify the function of timer T3124 and the contents in the message HANDOVER FAILURE and in the layer 1 header on the SACCH.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.5.9.3 Method of test
|
Initial Conditions
System Simulator:
2 cells with same LAI, default parameters.
Mobile Station:
The MS is in the active state (U10) of a call (on cell A). Used power level is the maximum supported by the MS.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
The active state (U10) of a mobile call (on cell A). Used power level is the maximum supported by the MS.
Test Procedure
The MS is in the active state (U10) of a call on cell A. The SS sends a HANDOVER COMMAND on the main DCCH. The MS shall begin to send access bursts at the commanded Power Control Level on the new DCCH (and optionally the SACCH) to cell B ( the commanded Power Control Level must be different than that already used for Cell A). With the exception of normal BCCH signalling, the SS does not transmit anything on cell B (thus causing a time-out of T3124). The MS shall re-establish the old link on cell A and send a HANDOVER FAILURE within 3 s from the transmission of HANDOVER COMMAND, using the old Power Control Level.
Maximum Duration of Test
5 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
Step
Direction
Message
Comments
0
SS
-
The SS records the Power Control Level in the layer 1 header of the last SACCH message sent by the MS before step 1.
1
SS -> MS
HANDOVER COMMAND
Channel description: non-hopping, full rate. Synchronization Indication: non synchronized.
Power Level: different than that recorded in step 0.
2
MS -> SS
HANDOVER ACCESS
Several messages are sent, all with correct Handover References.
3
MS -> SS
HANDOVER FAILURE
Sent on old channel, RR cause value = "Abnormal release, unspecified", "Abnormal release, channel unacceptable", "Abnormal release, timer expired", "Abnormal release, no activity on the radio path" or "Protocol error unspecified". Shall be sent within 3 s from the transmission of HANDOVER COMMAND.
4
SS
-
The SS checks that the Power Control Level reported in the layer 1 header of the SACCH message that is sent in the first SACCH multiframe following the SABM is the same as in step 0.
Specific Message Contents
None.
26.6.6 Test of frequency redefinition
The Frequency Redefinition procedure is used by the network to change the frequencies and hopping sequences of the allocated channels.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.6.1 Frequency redefinition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.6.1.1 Conformance requirements
|
An MS, after receiving a FREQUENCY REDEFINITION message, shall start using the new frequencies and hopping sequence in the correct time slot when the MS is allocated a dedicated channel.
The behaviour described in the test purpose is applied for each combination of the value T(k) (k = 1,2,3) and for each supported dedicated channel type.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.4.5, 9.1.13 and 10.5.2.13.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.6.1.2 Test purpose
|
To verify that the MS, after receiving a Frequency Redefinition message, starts using the new frequencies and hopping sequence at the time indicated in the message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.6.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, CCCH_CONF set to 1 basic physical channel used for CCCH, not combined with SDCCHs. The cell allocation is set to CA (1) , depending on the band of operation of the Mobile Station before each execution of this test.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
- MS supports GSM HR (TSPC_AddInfo_Halfrate)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
Test parameters:
ca (1) is set according to the column ca(1) of table below.
An arbitrary subset CA(1) of the set in the column CA Range of the table below containing ca(1) elements is drawn. CA(1) is then coded using the coding scheme from the table below.
An element B of the set CA(1) is arbitrarily chosen.
An arbitrary value ca(2) in the range indicated in column ca(2) of the table below is chosen.
An arbitrary subset CA(2) of the set in the column CA Range of the table below with ca(2) elements and containing B is chosen.
An arbitrary value ca(3) in the range indicated in column ca(3) of the table below is chosen.
An arbitrary subset CA(3) of the set in the column CA Range of the table below with ca(3) elements and containing B is chosen.
For j = 1,2,3, values ma(j) in the range j,...,ca(j)‑1 and values MAIO(j) in the range 0,...,ma(j)‑1 are arbitrarily chosen.
Subsets MA(j) of CA(j) not containing B and having ma(j) elements are arbitrarily chosen.
Band
ca(1)
CA Range
ca(2)
ca(3)
Coding
GSM 450
32
259,…,293
17,…,31
4,…,16
Range 128
GSM 480
32
306,…,340
17,…,31
4,…,16
Range 128
GSM 710
64
438,…,511
19,…,62
3,…,18
Range 128
GSM 750
64
438,…,511
19,…,62
3,…,18
Range 128
T-GSM 810
64
438,…,511
19,…,62
3,…,18
Range 128
GSM 850
64
128,…,251
19,…,62
3,…,18
Variable bitmap
GSM 900
64
1,…,124
20,…,63
4,…,19
Bitmap 0
DCS 1 800
64
700,…,812
17,…,63
4,…,16
Variable bitmap
PCS 1 900
64
700,…,810
17,…,63
4,…,16
Variable bitmap
Let T(1) = 91, T(2) = 42 000.
An arbitrary value T(3) in the range 92,...,29999 is chosen.
The System Simulator pages the MS and after the MS has responded with a CHANNEL REQUEST, the simulator assigns a dedicated channel (TCH/F, TCH/H or SDCCH, as defined by the execution counter R). Then the SS sends a FREQUENCY REDEFINITION message, which modifies the frequencies/hopping sequence to be used by the MS. The MS shall then, at the TDMA frame defined by the contents of the "Starting Time" information element , use the new frequencies/hopping sequence. (The value of T(2) ensures that the MS believes the Starting Time has passed and so the MS shall start transmitting immediately. Immediately being in the scope of this test no later than 73 Frames for SDCCH/8 or TCH/F and 90 Frames for TCH/H after the SS sends the last burst of the first L2 frame containing the beginning of the FREQUENCY REDEFINITION message. The range for T(3) ensures that the MS has to wait until the designated frame before starting transmission on the new frequencies.)
The verification is performed at the RF burst level. The MS transmits the standard test signal C1 (annex 5), and for the TCH case, the SS checks the received pattern with the expected pattern. For the SDCCH case the MS transmits fill frames, and the SS checks for each burst whether the burst is transmitted at the right frequency.
Maximum Duration of Test
3 * (number of supported channels * T(3) + 7)
Expected Sequence
This sequence is performed for every combination of execution counters K = 1,2,3 and R = 1,2,3:
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
4A
SS -> MS
IDENTITY REQUEST
Identity type : IMSI
4B
MS -> SS
IDENTITY RESPONSE
The response is not checked by the SS
5
--------
--------
The SS checks that the MS is transmitting on the correct frequencies without delay.
6
SS -> MS
FREQUENCY REDEFINITION
See description 1 below.
7
--------
--------
The SS checks that the MS is transmitting on the correct frequencies and that the transmissions started in the correct frame.
7A
SS -> MS
IDENTITY REQUEST
Identity type : IMSI
7B
MS -> SS
IDENTITY RESPONSE
The response is not checked by the SS
8
SS -> MS
FREQUENCY REDEFINITION
See description 2 below.
9
--------
--------
The SS checks that the MS is transmitting on the correct frequencies and that the transmissions started in the correct frame.
10
SS -> MS
CHANNEL RELEASE
For: K=1, R = 1,2,3 T(K) = T(1);
K=2, R = 1,2,3 T(K) = T(2);
K=3, R = 1,2,3 T(K) = T(3).
Specific Message Contents
IMMEDIATE ASSIGNMENT
Information Element
value/remark
L2 pseudo length
value dependent on the length of the Mobile Allocation and thus on the number of channels in CA (1).
Channel Description
Channel type
SDCCH/8 arbitrary offset, for R=1
and TDMA offset
Bm + ACCHs for R=2
Lm + ACCHs arbitrary offset, for R=3
Timeslot number
arbitrarily selected by
TSC
arbitrarily selected
Hopping channel
RF hopping channel
MAIO
MAIO(1)
HSN
0
Request reference
corresponds to the Channel Request
Timing advance
30 bit periods
Mobile Allocation
corresponds to set MA(1)
Starting Time
not present
IA rest octets
all bits are set to spare
FREQUENCY REDEFINITION (Description 1)
Information Element
value/remark
Protocol Discriminator
RR Management
Skip Indicator
0000
Message Type
00101011
Channel Description
Channel type
SDCCH/8 offset not changed, for R=1
and TDMA offset
Bm + ACCHs for R=2
Lm + ACCHs offset not changed, for R=3
Timeslot number
not changed
TSC
not changed
Hopping channel
RF hopping channel
MAIO
MAIO(2)
HSN
0
Mobile Allocation
corresponds to set MA(2)
Starting Time
The last burst of the first L2 frame containing the beginning of this message is transmitted in frame number X. The starting time is set to frame number (X plus T(K) modulo 42 432).
Cell Channel Description
Information element identifier
62H
contents
corresponds to set CA(2) encoded according to the table below.
Band
Cell Channel Description – coding format
Step 6
Step 8
GSM 450
Range 128
Range 128
GSM 480
Range 128
Range 128
GSM 710
Range 128
Range 128
GSM 750
Range 128
Range 128
T-GSM 810
Range 128
Range 128
GSM 850
Range 128
Range 128
GSM 900
Bitmap 0
Bitmap 0
DCS 1 800
Variable bitmap
K=1: Range 1 024
K=2: Range 256
K=3: Range 512
PCS 1 900
Variable bitmap
K=1: Range 1 024
K=2: Range 256
K=3: Range 512
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7 Test of the channel mode modify procedure
|
The channel mode modify procedure allows the network to request the MS to change the channel mode for one channel. If the mobile station does not correctly respond to the CHANNEL MODE MODIFY message (with a positive acknowledgement if the new channel mode is supported, with a negative acknowledgement if the new channel mode is not supported), the network may try to repeat the procedure, release the connection, or continue to wait for the acknowledgement (the maximum time resulting from layer two re-transmissions and MS reaction time being around 5 s).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.1 Test of the channel mode modify procedure / full rate
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.1.1 Conformance requirement
|
When the MS has received the CHANNEL MODE MODIFY message, the mobile station changes the mode for the indicated channel and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the new channel mode.
If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message.
References
3GPP TS 04.08 / 3GPP TS 44.018, subclauses 3.4.6.1.2 and 3.4.6.1.3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.1.2 Test purpose
|
To verify that the MS, in an RR connected state, acknowledges a CHANNEL MODE MODIFY message by sending a CHANNEL MODE MODIFY ACKNOWLEDGEMENT message specifying and switching to the correct mode.
- the new mode if that mode is supported.
- the old mode if the new mode is not supported.
This shall be verified for the channel modes
- signalling only.
- speech full rate version 1.
- data 9,6 Kb/s.
- data 4,8 Kb/s full rate.
- data 2,4 Kb/s full rate.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cells, default parameters.
Mobile Station:
The MS is "idle updated", with TMSI allocated.
Specific PICS statements
• GSM FR (TSPC_AddInfo_Full_rate_version_1)
• 9.6 k full rate data mode (TSPC_AddInfo_96Data)
• 4.8 k full rate data mode (TSPC_AddInfo_48DataF)
• 2.4 k full rate data mode (TSPC_AddInfo_24DataF)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test procedure
A Mobile Terminated call is initiated , however following the Channel Request received from the Mobile Station, the SS sends an Immediate Assignment to the MS commanding it to go to a TCH/F. This sets the Channel Mode automatically to "Signalling Only".
The SS then sends a series of CHANNEL MODE MODIFY messages to the MS. Each time it is checked that the MS responds with a CHANNEL MODE MODIFY ACKNOWLEDGE message specifying:
- the channel mode that has been specified in the CHANNEL MODE MODIFY message, if the MS supports that mode (this mode then becomes the "channel mode in use");
- the channel mode that was in use when the CHANNEL MODE MODIFY message has been received, if the MS does not support the channel mode specified in the CHANNEL MODE MODIFY message.
Maximum Duration of Test
30 s.
Expected Sequence
Step
Direction
Message
Comments
1
SS->MS
PAGING REQUEST TYPE 1
Sent on correct paging subchannel.
2
MS->SS
CHANNEL REQUEST
Establishment cause indicates "answer to paging".
3
SS->MS
IMMEDIATE ASSIGNMENT
Assignment to a non hopping TCH/F.
4
MS->SS
PAGING RESPONSE
5
SS->MS
CHANNEL MODE MODIFY
6
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
7
SS->MS
CHANNEL MODE MODIFY
8
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
9
SS->MS
CHANNEL MODE MODIFY
10
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
11
SS->MS
CHANNEL MODE MODIFY
12
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
13
SS->MS
CHANNEL MODE MODIFY
14
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
15
SS->MS
CHANNEL RELEASE
Specific Message Contents
CHANNEL MODE MODIFY
Information Element
value/remark
Channel description
describes the already assigned dedicated channel.
Channel mode
Mode
in step 5: speech full rate version 1
in step 7: data 9,6 Kb/s
in step 9: data 4,8 Kb/s full rate
in step 11: data 2,4 Kb/s full rate
in step 13 signalling only
CHANNEL MODE MODIFY ACKNOWLEDGE
Information Element
value/remark
Channel mode
Mode
in step 6:
if TSPC_AddInfo_Full_rate_version_1: speech full rate version 1
else: signalling only
in step 8:
if TSPC_AddInfo_96Data: data 9.6 Kb/s
else: same as in step 6
in step 10:
if TSPC_AddInfo_48DataF: data 4.8 Kb/s full rate
else: same as in step 8
in step 12:
if TSPC_AddInfo_24DataF: data 2.4 Kb/s full rate
else: same as in step 10
in step 14:
signalling only
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.2 Test of the channel mode modify procedure / half rate
|
This test is only applicable to an dual rate MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.2.1 Conformance requirement
|
When the MS has received the CHANNEL MODE MODIFY message, the mobile station changes the mode for the indicated channel and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the new channel mode.
If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message.
References
3GPP TS 04.08 / 3GPP TS 44.018, subclauses 3.4.6.1.2 and 3.4.6.1.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.2.2 Test purpose
|
To verify that the MS, in an RR connected state, acknowledges a CHANNEL MODE MODIFY message by sending a CHANNEL MODE MODIFY ACKNOWLEDGEMENT message specifying and switches to the correct mode:
- the new mode if that mode is supported;
- the old mode if the new mode is not supported.
This shall be verified for the channel modes:
- signalling only;
- speech half rate version 1;
- data 4,8 Kb/s half rate;
- data 2,4 Kb/s half rate;
- speech half rate version 3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.7.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cells, default parameters.
Mobile Station:
The MS is "idle updated", with TMSI allocated.
Specific PICS statements
• GSM HR (TSPC_AddInfo_Half_rate_version_1)
• 4.8 k half rate data mode (TSPC_AddInfo_48DataH)
• 2.4 k half rate data mode (TSPC_AddInfo_24DataH)
• HR AMR (TSPC_AddInfo_Half_rate_version_3)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test procedure
A Mobile Terminated call is initiated , however following the Channel Request received from the Mobile Station, the SS sends an Immediate Assignment to the MS commanding it to go to a TCH/H. This sets the Channel Mode automatically to "Signalling Only".
The SS then sends a series of CHANNEL MODE MODIFY messages to the MS. Each time it is checked that the MS responds with a CHANNEL MODE MODIFY ACKNOWLEDGE message specifying:
- the channel mode that has been specified in the CHANNEL MODE MODIFY message, if the MS supports that mode (this mode then becomes the "channel mode in use");
- the channel mode that was in use when the CHANNEL MODE MODIFY message has been received, if the MS does not support the channel mode specified in the CHANNEL MODE MODIFY message.
Maximum Duration of Test
30 s.
Expected Sequence
Step
Direction
Message
Comments
1
SS->MS
PAGING REQUEST TYPE 1
Sent on the correct paging subchannel.
2
MS->SS
CHANNEL REQUEST
Establishment cause indicates "answer to paging".
3
SS->MS
IMMEDIATE ASSIGNMENT
Assignment to a non hopping TCH/H.
4
MS->SS
PAGING RESPONSE
5
SS->MS
CHANNEL MODE MODIFY
6
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
7
SS->MS
CHANNEL MODE MODIFY
8
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
9
SS->MS
CHANNEL MODE MODIFY
10
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
11
SS->MS
CHANNEL MODE MODIFY
12
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
13
SS->MS
CHANNEL MODE MODIFY
14
MS->SS
CHANNEL MODE MODIFY ACKNOWLEDGE
15
SS->MS
CHANNEL RELEASE
Specific Message Contents
CHANNEL MODE MODIFY
Information Element
value/remark
Channel description
describes the already assigned dedicated channel.
Channel mode
Mode
in step 5: speech half rate version 1
in step 7: data 4,8 Kb/s half rate
in step 9: data 2,4 Kb/s half rate
in step 11: speech half rate version 3
in step 13: signalling only
Multi-Rate Configuration
Arbitrarily chosen
CHANNEL MODE MODIFY ACKNOWLEDGE
Information Element
value/remark
Channel mode
Mode
in step 6:
if TSPC_AddInfo_Half_rate_version_1: Speech half rate version 1
else: signalling only
in step 8:
if TSPC_AddInfo_48DataH: data 4,8 Kb/s half rate
else: same as in step 6
in step 10:
if TSPC_AddInfo_24DataH: data 2,4 Kb/s half rate
else: same as in step 8
in step 12:
if TSPC_AddInfo_Half_rate_version_3: speech half rate version 3
else: same as in step 10.
in step 14:
signalling only
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8 Test of ciphering mode setting
|
The Ciphering Mode Setting Procedure can be used by the network to trigger the start and stop of stream ciphering.
The SS shall start and synchronize ciphering and deciphering according to 3GPP TS 03.20 / 3GPP TS 33.102, 3GPP TS 33.220. The bit stream shall be generated by algorithm A5 (A5/1, A5/3 and A5/4 as defined by the test case) using the encryption key Kc (A5/1, A5/3) or Kc128 (A5/4).
For test cases using algorithm A5/4 Test USIM as specified in Annex 4A is required.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.1 Ciphering mode / start ciphering
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.1.1 Conformance requirements
|
1. When the MS receives the CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "start ciphering", the MS starts ciphering and deciphering with the algorithm indicated by the "algorithm identifier" field:
- the MS responds with a CIPHERING MODE COMPLETE message in ciphered mode;
- the ciphering uses the cipher key determined during the authentication procedure.
2. The MS responds to the AUTHENTICATION REQUEST message with an AUTHENTICATION RESPONSE message and continues to use the ciphering key obtained from the previous authentication procedure.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.1.2 Test purpose
|
To verify that the MS starts ciphering when it receives a CIPHERING MODE COMMAND message with Cipher Mode Setting = "Start Ciphering". To verify that it continues to use the old cipher key after it receives an AUTHENTICATION REQUEST whilst in ciphered mode.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cells, Radio_Link_Timeout set to 64.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
- Support for A5/3 (TSPC_Feat_A53)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is made to originate a call. It shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a CM SERVICE REQUEST. The SS sends an AUTHENTICATION REQUEST and the MS shall answer with AUTHENTICATION RESPONSE. Then the SS sends a CIPHERING MODE COMMAND, ordering the MS to start ciphering with an algorithm supported by the MS. After transmission of this command the SS starts deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in ciphered mode using the cipher key determined during the authentication procedure, and continue to establish the call with a SETUP message. After reception of the CIPHERING MODE COMPLETE the SS starts enciphering.
The SS then sends another AUTHENTICATION REQUEST and the MS shall respond with an AUTHENTICATION RESPONSE. The MS shall continue to use the old cipher key.
Finally the SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
5 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
This sequence is performed for execution counter, K=1 and optionally when the MS supports A5/3 for K=3.
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establ. Cause = "Originating Call" NECI not set to 1
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
AUTHENTICATION REQUEST
5
MS -> SS
AUTHENTICATION RESPONSE
6
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/K". The SS starts deciphering.
7
MS -> SS
CIPHERING MODE COMPLETE
Sent in ciphered mode using the cipher key determined in between steps 4&5. The SS start enciphering.
8
MS -> SS
SETUP
9
SS -> MS
AUTHENTICATION REQUEST
10
MS -> SS
AUTHENTICATION RESPONSE
New cipher key has been calculated.
Sent in ciphered mode using the cipher key determined in between steps 4&5.
11
SS -> MS
CHANNEL RELEASE
Specific Message Contents
CIPHERING MODE COMMAND
For
K = 1, A5/K = A5/1
K = 3, A5/K = A5/3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.2 Ciphering mode / no ciphering
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.2.1 Conformance requirements
|
When the MS receives a CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "no ciphering" the MS shall respond in non ciphered mode with a CIPHERING MODE COMPLETE message.
When the CIPHERING MODE COMMAND with Ciphering Mode Setting information element set to "no ciphering" is received as a response to a CM SERVICE REQUEST, the MS shall continue the establishment of the CM service.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.2.2 Test purpose
|
To verify that the MS does not start ciphering when it receives a CIPHERING MODE COMMAND message with Cipher Mode Setting = "No Ciphering".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cells, Radio_Link_Timeout set to 64.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is made to originate a call. It shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a CM SERVICE REQUEST. The SS sends an AUTHENTICATION REQUEST and the MS shall answer with an AUTHENTICATION RESPONSE. Then the SS sends a CIPHERING MODE COMMAND, ordering the MS not to start ciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in non-ciphered mode and continue to establish the call with a SETUP message.
Finally the SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
5 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establ. Cause = "Originating call; NECI not equal to 1.
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
AUTHENTICATION REQUEST
5
MS -> SS
AUTHENTICATION RESPONSE
6
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "No Ciphering".
7
MS -> SS
CIPHERING MODE COMPLETE
Sent in non-ciphered mode.
8
MS -> SS
SETUP
11
SS -> MS
CHANNEL RELEASE
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.3 Ciphering mode / old cipher key
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.3.1 Conformance requirements
|
When the MS receives the CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "start ciphering", the MS starts ciphering and deciphering with the algorithm indicated by the "algorithm identifier" field. Also;
- the MS responds with a CIPHERING MODE COMPLETE message in the correct ciphered mode;
- the ciphering shall use the previously stored cipher key;
- in the case of a mobile originating speech call, the MS shall send a SETUP message after the completion of the ciphering procedure.
References
3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.3.2 Test purpose
|
To verify that the MS uses the stored cipher key when it receives a CIPHERING MODE COMMAND without a preceding authentication procedure.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cells, Radio_Link_Timeout = 64.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated and a known cipher key stored.
Specific PICS statements
- Support for A5/3 (TSPC_Feat_A53)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is made to originate a call. It shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a CM SERVICE REQUEST. The SS sends a CIPHERING MODE COMMAND, ordering the MS to start ciphering with a supported algorithm. After transmission of this command the SS starts deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in the commanded ciphered mode using the stored cipher key and continue to establish the call with a SETUP message. After reception of the CIPHERING MODE COMPLETE the SS starts enciphering.
Finally the SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
5 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establ. Cause = "Originating Call: NECI not equal to 1.
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering", algorithm A5/1 or A5/3, if supported, is arbitrarily selected. The SS starts deciphering.
5
MS -> SS
CIPHERING MODE COMPLETE
Sent in commanded ciphered mode with the stored cipher key. The SS starts enciphering.
6
MS -> SS
SETUP
7
SS -> MS
CHANNEL RELEASE
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.4 Ciphering mode / change of mode, algorithm and key
|
Networks can be implemented that do not have the same ciphering algorithms on all base stations. In such networks changes of algorithms and ciphering mode may occur and calls will fail if MSs incorrectly handle commands or use an incorrect cipher key.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.4.1 Conformance requirements
|
1 When the MS in the "not ciphered" mode, receives a CIPHERING MODE COMMAND message with the Ciphering Mode Setting information element set to "start ciphering", the MS shall load the cipher key stored in the SIM into the ME, use this key to start ciphering and deciphering with the algorithm indicated by the "algorithm identifier" field and, respond with a CIPHERING MODE COMPLETE message.
2 If the last timeslot of the message block containing a CIPHERING MODE COMMAND message occurs at time T, then the MS shall be ready to transmit the CIPHERING MODE COMPLETE message before T+500 ms.
3 When the MS receives an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE after receipt of a CIPHERING MODE COMMAND message, the MS shall perform the assignment, use the commanded mode and/or algorithm on the new channel, and not change the ciphering key.
4 When the MS receives a HANDOVER COMMAND message containing a Cipher Mode Setting IE after receipt of a CIPHERING MODE COMMAND message, the MS shall perform the handover, use the commanded mode and/or algorithm on the new channel, and not change the ciphering key.
5 When the MS in the "ciphered" mode receives a CIPHERING MODE COMMAND message with Cipher Mode Setting IE set to "no ciphering", the MS shall load the cipher key stored in the SIM into the ME, load the cipher key stored in the SIM into the ME, stop ciphering and deciphering and, respond with a CIPHERING MODE COMPLETE message.
6 When the MS receives an AUTHENTICATION REQUEST message, it shall process the challenge information and send back an AUTHENTICATION RESPONSE message to the network. The new ciphering key calculated from the challenge information shall overwrite the previous one and be stored on the SIM before the AUTHENTICATION RESPONSE message is transmitted. The ciphering key stored in the SIM shall be loaded in to the ME when any valid CIPHERING MODE COMMAND is received.
7 When the MS in the not ciphered mode receives a CIPHERING MODE COMMAND message with Cipher Mode Setting IE set to "no ciphering", the MS shall load the cipher key stored in the SIM into the ME, stop ciphering and deciphering and, respond with a CIPHERING MODE COMPLETE message.
8 If a handover fails then the operational parameters used when returning to the old channel are those applied before the HANDOVER COMMAND message was received.
9 If an assignment fails then the operational parameters used when returning to the old channel are those applied before the ASSIGNMENT COMMAND message was received.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.4.7.2 and 4.3.2.2.
Conformance requirement 2: 3GPP TS 04.13 subclause 5.2.7.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3.1.
Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.4.1.
Conformance requirement 5: 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.4.7.2 and 4.3.2.2.
Conformance requirement 6: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 4.3.2.2.
Conformance requirement 7: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.7.2.
Conformance requirement 8: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.4.4.
Conformance requirement 9: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.3.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.4.2 Test purpose
|
1 To verify that when the MS is in the "not ciphered" mode and receives the CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "start ciphering", the MS uses the cipher key stored in the SIM to start ciphering and deciphering with the algorithm indicated by the "algorithm identifier" field and that the MS responds with a CIPHERING MODE COMPLETE message.
2 To verify that the MS is ready to transmit the CIPHERING MODE COMPLETE message before 500 ms after the end of the CIPHERING MODE COMMAND message.
3 To verify that when the MS receives an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE after receipt of a CIPHERING MODE COMMAND message, the MS shall perform the assignment, use the commanded mode and/or algorithm on the new channel, and not change the ciphering key.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
4 To verify that when the MS receives a HANDOVER COMMAND message containing a Cipher Mode Setting IE after receipt of a CIPHERING MODE COMMAND message, the MS shall perform the handover, use the commanded mode and/or algorithm on the new channel, and not change the ciphering key
|
5 To verify that when the MS is in the "ciphered" mode and receives the CIPHERING MODE COMMAND message with Cipher Mode Setting IE set to "no ciphering", the MS loads the cipher key stored in the SIM into the ME, stops ciphering and deciphering and, responds with a CIPHERING MODE COMPLETE message.
6 To verify that the MS responds to an AUTHENTICATION REQUEST message with an AUTHENTICATION RESPONSE message and continues to use the cipher key obtained from the previous authentication procedure.
7 To verify that when the MS is in the "not ciphered" mode and receives the CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "no ciphering", the does not start ciphering or deciphering, but does respond with a CIPHERING MODE COMPLETE message.
8 To verify that when the MS receives a HANDOVER COMMAND message and the handover fails, the MS sends a HANDOVER FAILURE message on the old channel using the old ciphering mode and (if ciphered) the old algorithm and old key.
9 To verify that when the MS receives an ASSIGNMENT COMMAND message and the assignment fails, the MS sends an ASSIGNMENT FAILURE message on the old channel using the old ciphering mode and (if ciphered) the old algorithm and old key.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.4.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, with a legal combination of CCCH_CONF with SDCCH/4s or SDCCH/8s is chosen arbitrarily by the SS.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated and a known cipher key, K, stored in the SIM.
Specific PICS statements
• Support for A5/3 (TSPC_Feat_A53)
• TSPC_Type_xxx (all appropriate power classes)
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is paged. The MS shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a PAGING RESPONSE message.
The SS sends a CIPHERING MODE COMMAND, ordering the MS to start ciphering with a supported algorithm. After transmission of this command the SS starts deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in the commanded ciphered mode using the cipher key K. After reception of the CIPHERING MODE COMPLETE the SS starts enciphering. The MS shall be ready to transmit the CIPHERING MODE COMPLETE message before 500 ms after the end of the CIPHERING MODE COMMAND message.
The term "ready to transmit" is defined in 3GPP TS 04.13.
The SS sends an AUTHENTICATION REQUEST message to the MS. Cipher key L is calculated. The MS shall send an AUTHENTICATION RESPONSE message to the SS.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) with the Cipher Mode Setting IE set to "no ciphering". The MS shall transmit the HANDOVER COMPLETE on the commanded channel in non ciphered mode.
The SS sends an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE set to "start ciphering". The MS shall start transmitting on the commanded channel using the commanded algorithm and cipher key K. The MS shall transmit the ASSIGNMENT COMPLETE message.
The SS sends a CIPHERING MODE COMMAND, ordering the MS to stop ciphering. After transmission of this command the SS stops deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in non ciphered mode. After reception of the CIPHERING MODE COMPLETE the SS stops enciphering.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) with the Cipher Mode Setting IE set to "start ciphering". The MS shall transmit the HANDOVER COMPLETE on the commanded channel in ciphered mode using cipher key L and command algorithm.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) with the Cipher Mode Setting IE set to "start ciphering" and the algorithm identifier indicating the algorithm currently in use. The MS shall transmit the HANDOVER COMPLETE on the commanded channel in ciphered mode using the same algorithm as before the handover.
The SS sends an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE set to "no ciphering". The MS shall start transmitting on the commanded channel in non-ciphered mode. The MS shall transmit the ASSIGNMENT COMPLETE message.
The SS sends a CIPHERING MODE COMMAND, containing a Cipher Mode Setting IE set to "no ciphering". The MS shall respond with a CIPHERING MODE COMPLETE message.
The SS sends an AUTHENTICATION REQUEST message to the MS. Cipher key M is calculated. The MS shall send an AUTHENTICATION RESPONSE message to the SS.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) with the Cipher Mode Setting IE set to "start ciphering". The MS shall transmit the HANDOVER COMPLETE on the commanded channel using the commanded algorithm and cipher key L.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) with the Cipher Mode Setting IE set to "no ciphering". The SS does not activate the commanded channel. The MS's transmissions on the new channel need not be monitored. The MS shall transmit the HANDOVER FAILURE message on the "old" channel using the "old" algorithm and cipher key L and commanded algorithm.
The SS sends an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE set to "start ciphering". The SS does not activate the commanded channel. The MS's transmissions on the new channel need not be monitored. The MS shall transmit the ASSIGNMENT FAILURE message on the "old" channel using the "old" algorithm and cipher key L.
If the MS only supports one ciphering algorithm then the SS sends a CHANNEL RELEASE message.
If the MS supports more than one ciphering algorithm then the following steps are performed:
The SS sends an ASSIGNMENT COMMAND message containing a Cipher Mode Setting IE set to "start ciphering" and the Algorithm Identifier indicating a different supported algorithm to the one in use. The MS shall start transmitting on the commanded channel using the commanded algorithm. The MS shall transmit the ASSIGNMENT COMPLETE message.
The SS sends a HANDOVER COMMAND (for a finely synchronized intra-BTS handover) containing a Cipher Mode Setting IE set to "start ciphering" and the Algorithm Identifier indicating a different supported algorithm to the one in use. The MS shall transmit the HANDOVER COMPLETE on the commanded channel using the commanded algorithm.
The SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
3 minutes.
Expected Sequence
For MSs that only support one ciphering algorithm, the SS shall use step 61A. For MSs that support more than one ciphering algorithm, the SS shall use step 61B and the subsequent steps.
NOTE: 3GPP TS 04.08 / 3GPP TS 44.018 appears to be unclear as to whether timer T3240 shall or shall not be started as a result of the AUTHENTICATION REQUEST messages sent in steps 8 and 44. To allow a variety of test equipment implementations, the IDENTITY REQUEST messages are included in order to avoid an unexpected expiry of timer T3240 prior to the end of the expected sequence.
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
To either SDCCH4 or SDCCH8 depending upon CCCH_CONF arbitrarily chosen.
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering", algorithm arbitrarily selected from those supported by the MS. The SS starts deciphering with the selected algorithm.
6
MS -> SS
CIPHERING MODE COMPLETE
Sent in ciphered mode using key "K", the stored cipher key, and the commanded algorithm. This message shall be ready to be transmitted before 500 ms after the completion of step 5.
7
SS
- The SS starts enciphering using key "K".
8
SS -> MS
AUTHENTICATION REQUEST
Contains a new Ciphering Key Sequence Number which is associated with the new cipher key, "L".
9
MS -> SS
AUTHENTICATION RESPONSE
10
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "No Ciphering".
11
SS
-
The SS activates the new channel without ciphering.
12
MS -> SS
HANDOVER ACCESS
These four HANDOVER ACCESS messages are
13
MS -> SS
HANDOVER ACCESS
sent on the new channel in non ciphered
14
MS -> SS
HANDOVER ACCESS
mode.
15
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
16
MS -> SS
HANDOVER COMPLETE
Sent in non ciphered mode on the new channel.
17
SS -> MS
ASSIGNMENT COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering", with algorithm arbitrarily selected from those supported by the MS.
18
SS
The SS activates the new channel with enciphering and deciphering enabled and using cipher key "K".
19
MS -> SS
ASSIGNMENT COMPLETE
Sent on the new channel in ciphered mode using key "K" and the commanded algorithm.
20
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "No Ciphering". The SS starts receiving in non ciphered mode.
21
MS -> SS
CIPHERING MODE COMPLETE
Sent in non ciphered mode. This message shall be ready to be transmitted before 500 ms after the completion of step 20.
22
SS
-
The SS starts transmitting in non ciphered mode.
23
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering", with algorithm "X" arbitrarily selected from those supported by the MS.
24
SS
The SS activates the new channel with enciphering and deciphering enabled and using cipher key "L".
25
MS -> SS
HANDOVER ACCESS
These four HANDOVER ACCESS messages are
26
MS -> SS
HANDOVER ACCESS
sent on the new channel in the non ciphered
27
MS -> SS
HANDOVER ACCESS
mode.
28
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
29
MS -> SS
HANDOVER COMPLETE
Sent on the new channel in ciphered mode using key "L" and algorithm "X".
30
SS -> MS
IDENTITY REQUEST
31
MS -> SS
IDENTITY RESPONSE
32
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering", with algorithm identifier set to "X".
33
SS
The SS activates the new channel with enciphering and deciphering enabled.
34
MS -> SS
HANDOVER ACCESS
These four HANDOVER ACCESS messages are
35
MS -> SS
HANDOVER ACCESS
sent on the new channel in the non ciphered
36
MS -> SS
HANDOVER ACCESS
mode.
37
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
38
MS -> SS
HANDOVER COMPLETE
Sent on the new channel in ciphered mode using algorithm "X".
39
SS -> MS
ASSIGNMENT COMMAND
Includes Cipher Mode Setting IE set to "No Ciphering".
40
SS
The SS activates the new channel without ciphering.
41
MS -> SS
ASSIGNMENT COMPLETE
Sent in non-ciphered mode on the new channel.
42
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "No Ciphering".
43
MS -> SS
CIPHERING MODE COMPLETE
Sent in non ciphered mode. This message shall be ready to be transmitted before 500 ms after the completion of step 42.
44
SS -> MS
AUTHENTICATION REQUEST
Contains a new Ciphering Key Sequence Number which is associated with the new cipher key, "M".
45
MS -> SS
AUTHENTICATION RESPONSE
46
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering", with algorithm "Y" arbitrarily selected from those supported by the MS.
47
SS
The SS activates the new channel with enciphering and deciphering enabled and using cipher key "L".
48
MS -> SS
HANDOVER ACCESS
These four HANDOVER ACCESS messages are
49
MS -> SS
HANDOVER ACCESS
sent on the new channel in the non ciphered
50
MS -> SS
HANDOVER ACCESS
mode.
51
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
52
MS -> SS
HANDOVER COMPLETE
Sent on the new channel in ciphered mode using key "L"
53
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "No Ciphering".
54
SS, MS
The SS does not activate the new channel The MS's transmissions on the new channel need not be monitored.
55
MS -> SS
HANDOVER FAILURE
sent on old channel using algorithm "Y" and key "L".
56
SS -> MS
IDENTITY REQUEST
57
MS -> SS
IDENTITY RESPONSE
58
SS -> MS
ASSIGNMENT COMMAND
Includes Cipher Mode Setting IE set to "No Ciphering".
59
SS, MS
The SS does not activate the new channel The MS's transmissions on the new channel need not be monitored.
60
MS -> SS
ASSIGNMENT FAILURE
sent on old channel using algorithm "Y" and key "L".
61A
SS -> MS
CHANNEL RELEASE
61B
SS -> MS
ASSIGNMENT COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering", with algorithm "Z" arbitrarily selected from those supported by the MS but different to algorithm "Y".
62B
SS
The SS activates the new channel with enciphering and deciphering enabled.
63B
MS -> SS
ASSIGNMENT COMPLETE
Sent on the new channel in ciphered mode using key "L" and algorithm "Z".
64B
SS -> MS
HANDOVER COMMAND
Includes Cipher Mode Setting IE set to "Start Ciphering" and the algorithm identifier set to "Y".
65B
SS
The SS activates the new channel with enciphering and deciphering enabled.
66B
MS -> SS
HANDOVER ACCESS
These four HANDOVER ACCESS messages are
67B
MS -> SS
HANDOVER ACCESS
sent on the new channel in the non ciphered
68B
MS -> SS
HANDOVER ACCESS
mode.
69B
MS -> SS
HANDOVER ACCESS
Before completion of the 4 access bursts on the new DCCH, additional access bursts may also be sent on the SACCH
70B
MS -> SS
HANDOVER COMPLETE
Sent on the new channel in ciphered mode using key "L" and algorithm "Y".
71B
SS -> MS
CHANNEL RELEASE
Specific Message Contents
ASSIGNMENT COMMAND
Information Element
value/remark
Protocol Discriminator
RR Management.
Skip Indicator
0000
Message Type
00101110
Channel Description
- Channel Type
SDCCH/8 or SDCCH4 (same type as old channel)
- TDMA offset
Chosen arbitrarily, but different to the one in use (SDCCH4), otherwise arbitrary..
- Timeslot Number
Chosen arbitrarily, but different to the one in use (SDCCH8) or Timeslot zero.(SDCCH4)
- Training Sequence Code
5 (same as the BCC).
- Hopping
Single RF channel.
- ARFCN
See table below.
Power Command
- Power level
Chosen arbitrarily but within the range supported by the MS.
Cipher Mode Setting
As specified above.
All other information elements:
Not present.
HANDOVER COMMAND
Information Element
value/remark
Protocol Discriminator
RR Management.
Skip Indicator
0000
Message Type
00101011
Cell Description
- Network Colour Code
1
- Base station Colour Code
5
- BCCH Carrier Number
See table below.
Channel Description
- Channel Type
SDCCH/8 or SDCCH4(same type as old channel)
- TDMA offset
Chosen arbitrarily, but different to the one in use (SDCCH4), otherwise arbitrary.
- Timeslot Number
Chosen arbitrarily, but different to the one in use (SDCCH8) or Timeslot zero.(SDCCH4
- Training Sequence Code
5 (same as the BCC).
- Hopping
Single RF channel.
- ARFCN
See table below.
Handover Reference
- Handover Reference Value
Chosen arbitrarily.
Power Command
- Power level
Chosen arbitrarily, but within the range supported by the MS.
Synchronization Indication
- Synchronization indication
synchronized.
- Report observed time difference
not included.
- Normal cell indication
out of range ignored.
Cipher Mode setting
As specified above.
All other information elements:
Not present.
Band
ARFCN
GSM 450
265
GSM 480
315
GSM 710
467
GSM 750
467
T-GSM 810
467
GSM 850
157
GSM 900
30
DCS 1 800
650
PCS 1 900
650
CIPHER MODE COMMAND
Information Element
value/remark
As default message contents, except:
Cipher Mode Setting
- Algorithm Identifier
As specified above.
- Cipher Mode Set
As specified above.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.5 Ciphering mode / IMEISV request
|
If the MS does not supply the IMEISV when requested, the network will not know whether or not the MS is type approved, i.e. whether or not it has passed any tests.
If the MS supplies its IMEISV when not requested, this may cause calls to systematically fail.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.5.1 Conformance requirements
|
1. When the MS receives the CIPHERING MODE COMMAND message with Cipher Response bit set to "IMEISV shall be included" and the Cipher Mode Setting is “no ciphering”, the MS shall include the IMEISV in the Mobile Identity IE in the CIPHERING MODE COMPLETE message.
2. When the MS receives the CIPHERING MODE COMMAND message with Cipher Response bit set to "IMEISV shall not be included", the MS shall not include the Mobile Identity IE in the CIPHERING MODE COMPLETE message.
3. When the MS receives the CIPHERING MODE COMMAND message with Cipher Response bit set to "IMEISV shall be included" and the Cipher Mode Setting is “Ciphering required”, the MS shall include the IMEISV in the Mobile Identity IE in the CIPHERING MODE COMPLETE message.
4. When the MS receives a IDENTITY REQUEST message with ciphering enabled and the Identity Type IE set to “IMEISV”, the MS shall return its IMEISV in the Mobile Identity IE contained within the IDENTITY RESPONSE message.
5. To verify that the SVN portion of the IMEISV value returned by the MS is coded using binary coded decimal digits and does not use the reserved value “99”.
References
Conformance requirement 1: 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.4.7.2 and 9.1.10.1.
Conformance requirement 2: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 9.1.10.1.
Conformance requirement 3: 3GPP TS 04.08 / 3GPP TS 44.018 subclause 9.1.10.1.
Conformance requirement 4: 3GPP TS 24.008 subclauses 4.4.3.1, 4.7.1.2 and 4.7.8
Conformance requirement 5: 3GPP TS 23.003 subclause 6.2.2 / 3GPP TS 24.008 table 10.5.1.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.5.2 Test purpose
|
To verify that the MS supplies its IMEISV in the CIPHERING MODE COMPLETE message when it receives a CIPHERING MODE COMMAND message with a Cipher Response bit set to "IMEISV shall be included" and ciphering is not active/required.
To verify that the MS does not supply any Mobile Identity IE in the CIPHERING MODE COMPLETE message when it receives a CIPHERING MODE COMMAND message with a Cipher Response bit set to "IMEISV shall not be included".
To verify that the MS supplies its IMEISV in the CIPHERING MODE COMPLETE message when it receives a CIPHERING MODE COMMAND message with a Cipher Response bit set to "IMEISV shall be included" and ciphering is active/required.
To verify that the MS supplies its IMEISV in the IDENTITY RESPONSE message when it receives a IDENTITY REQUEST message with the Identity Type IE set to "IMEISV". The IDENTITY REQUEST and IDENTITY RESPONSE messages should not be ciphered (refer to 3GPP TS 24.008 clause 4.7.1.2).
To verify that the MS codes the SVN portion of the IMEISV using binary coded decimal (BCD) digits and does not use the reserved value “99”.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell.
Mobile Station:
The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
-
PIXIT statements
- IMEISV of the MS.
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is paged. It shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a PAGING RESPONSE. Then the SS sends a CIPHERING MODE COMMAND indicating "No ciphering" and with the Cipher Response bit set to "IMEISV shall not be included". The MS shall respond with a CIPHERING MODE COMPLETE message that does not include the Mobile Identity IE.
Then the SS sends a CIPHERING MODE COMMAND indicating "No ciphering" and with the Cipher Response bit set to "IMEISV shall be included". The MS shall respond with a CIPHERING MODE COMPLETE message that carries the IMEISV in the Mobile Identity IE. The SS checks the IMEISV value and verifies that the SVN IE is coded using BCD and does not equal the reserved value “99”.
The SS sends an IDENTITY REQUEST message with the Identity Type IE set to request the IMEISV value from the MS. The MS shall respond with an IDENTITY RESPONSE message that carries the IMEISV in the Mobile Identity IE. The SS then checks the IMEISV value and verifies that the SVN IE is coded using BCD and does not equal the reserved value “99”.
The IDENTITY REQUEST and IDENTITY RESPONSE messages shall not be ciphered.
The SS sends a third CIPHERING MODE COMMAND indicating "ciphering required" and with the Cipher Response bit set to "IMEISV shall be included". The MS shall respond with a CIPHERING MODE COMPLETE message that carries the IMEISV in the Mobile Identity IE. The SS checks the IMEISV value and verifies that the SVN IE is coded using BCD and does not equal the reserved value “99”..
Finally the SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
20 s.
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
CIPHERING MODE COMMAND
Cipher Mode Setting = "No Ciphering".
Cipher Response = "IMEISV shall not be included".
6
MS -> SS
CIPHERING MODE COMPLETE
Shall not include Mobile Identity IE.
7
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "No Ciphering".
Cipher Response = "IMEISV shall be included".
8
MS -> SS
CIPHERING MODE COMPLETE
Shall include one Mobile Identity IE carrying the MS's IMEISV.
The SS checks the IMEISV value is coded in BCD digits and does not equal 99.
9
SS -> MS
IDENTITY REQUEST
Identity Type = “IMEISV”
The IDENTITY REQUEST message shall not be ciphered.
10
MS -> SS
IDENTITY RESPONSE
Shall include Mobile Identity IE carrying the MS's IMEISV.
The SS checks the IMEISV value is coded in BCD digits and does not equal 99.
The IDENTITY RESPONSE message shall not be ciphered.
11
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering".
Cipher Response = "IMEISV shall be included".
12
MS -> SS
CIPHERING MODE COMPLETE
Shall include one Mobile Identity IE carrying the MS's IMEISV.
The SS checks the IMEISV value is coded in BCD digits and does not equal 99. The SVN portion of the IMEISV shall not be ciphered.
13
SS -> MS
CHANNEL RELEASE
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.6 Ciphering mode / Non support of algorithm A5/2
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.6.1 Conformance requirements
|
For the MS it is prohibited to implement algorithm A5/2.
References
3GPP TS 43.020 subclause 4.9
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.6.2 Test purpose
|
To verify that the MS does not start ciphering when it receives a CIPHERING MODE COMMAND message with Cipher Mode Setting = "Start Ciphering" and algorithm identifier set to "A5/2".
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.6.3 Method of test
|
Initial Conditions
System Simulator:
1 cell. ATT=1.
Mobile Station:
Power off.
Specific PICS statements
-
PIXIT statements
-
Test Procedure
The MS is powered on. The MS sends CHANNEL REQUEST for doing location update procedure. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a LOCATION UPDATING REQUEST. SS checks that MS does not support A5/2 algorithm by CLASSMARK ENQUIRY Procedure. Then SS sends an AUTHENTICATION REQUEST and the MS shall answer with AUTHENTICATION RESPONSE. Then the SS sends a CIPHERING MODE COMMAND, ordering the MS to start ciphering with algorithm A5/2 which is prohibited for the MS. After transmission of this command the SS starts deciphering. The MS shall not respond with a CIPHERING MODE COMPLETE message in ciphered mode using the cipher key determined during the authentication procedure.
Maximum Duration of Test
3 minutes, including 1 minute for any necessary operator actions.
Expected Sequence
Step
Direction
Message
Comments
MS is switched on or powered on
1
MS -> SS
CHANNEL REQUEST
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
LÖCATION UPDATING REQUEST
4
SS->MS
CLASSMARK ENQUIRY
CLASSMARK CHANGE message is requested
5
MS->SS
CLASSMARK CHANGE
A5/2 algorithm = “encryption algorithm A5/2 not available” in Mobile Station Classmark 2 IE
6
SS -> MS
AUTHENTICATION REQUEST
7
MS -> SS
AUTHENTICATION RESPONSE
8
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/2". The SS starts deciphering.
SS checks that there is no valid L3 message received using algorithm A5/2 (e.g. CIPHERING MODE COMPLETE) within 10s.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.7 Ciphering mode with cipher key Kc128
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.7.1 Conformance requirements
|
1. When the MS receives the CIPHERING MODE COMMAND message with Ciphering Mode Setting information element set to "start ciphering", the MS starts ciphering and deciphering with the algorithm indicated by the "algorithm identifier" field:
- the MS responds with a CIPHERING MODE COMPLETE message in ciphered mode;
- the ciphering uses the cipher key determined during the authentication procedure.
2. The MS responds to the AUTHENTICATION REQUEST message with an AUTHENTICATION RESPONSE message and continues to use the ciphering key obtained from the previous authentication procedure.
3 The ASSIGNMENT COMMAND message may contain a cipher mode setting IE. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel. In either case the ciphering key shall not be changed as long as the key length remains unchanged.
References
3GPP TS 44.018 subclause 3.4.3, 3.4.7.
3GPP TS 24.008 subclause 4.3.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.7.2 Test purpose
|
To verify that the MS calculates the correct Kc128 and starts ciphering using cipher algorithm A5/4 when it receives a CIPHERING MODE COMMAND message with Cipher Mode Setting = "Start Ciphering".
To verify that the correct Kc128 key is used after ASSIGNMENT COMMAND including cipher mode setting for A5/4 algorithm.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.7.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default settings.
Mobile Station:
Test USIM is plugged into the MS. The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
CC state U10-call active.
Test Procedure
The MS is made to originate a call. It shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a CM SERVICE REQUEST. The SS sends an AUTHENTICATION REQUEST with AUTN Information Element present and the MS shall answer with AUTHENTICATION RESPONSE with correct RES. Then the SS sends a CIPHERING MODE COMMAND ordering the MS to start ciphering with algorithm A5/4. After transmission of this command the SS starts deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in ciphered mode using the 128 bit cipher key calculated during the authentication procedure and continue to establish the call with a SETUP message.
The SS sends CALL PROCEEDING and initiates a new authentication procedure by sending AUTHENTICATION REQUEST with AUTN Information Element present and different RAND value. The MS shall respond with AUTHENTICATION RESPONSE with correct RES.
The call setup is proceeded with ALERTING. SS sends ASSIGNMENT COMMAND including cipher mode setting indicating A5/4. The MS shall respond with an ASSIGNMENT COMPLETE message in ciphered mode using the 128 bit cipher key calculated during the first authentication procedure. The call establishment is finished on the ciphered channel with CONNECT and CONNECT ACKNOWLEDGEMENT.
Maximum Duration of Test
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establ. Cause = "Originating Call" NECI not set to 1
2
SS -> MS
IMMEDIATE ASSIGNMENT
3
MS -> SS
CM SERVICE REQUEST
4
SS -> MS
AUTHENTICATION REQUEST
5
MS -> SS
AUTHENTICATION RESPONSE
Cipher key Kc128 has been calculated.
"Auth. Response Parameter" IE shall be bit exact with the value as produced by the authentication algorithm (RES in this case)
"Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.
6
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/4". The SS starts deciphering.
7
MS -> SS
CIPHERING MODE COMPLETE
Sent in ciphered mode using the cipher key determined in step 5. The SS start enciphering.
8
MS -> SS
SETUP
9
SS -> MS
CALL PROCEEDING
10
SS -> MS
AUTHENTICATION REQUEST
11
MS -> SS
AUTHENTICATION RESPONSE
A new cipher key Kc128 has been calculated.
"Auth. Response Parameter" IE shall be bit exact with the value as produced by the authentication algorithm (RES in this case)
"Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.
12
SS -> MS
ALERTING
13
MS
Depending on the PIXIT, an alerting indication is given.
14
SS -> MS
ASSIGNMENT COMMAND
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/4"
15
MS -> SS
ASSIGNMENT COMPLETE
Sent in ciphered mode using the cipher key determined in step 5.
16
SS -> MS
CONNECT
17
MS -> SS
CONNECT ACKNOWLEDGE
Specific Message Contents
AUTHENTICATION REQUEST step 4
Information Element
value/remark
AUTN Information Element
present
- Length = 16
- Calculated as defined for Test USIM
CIPHERING MODE COMMAND step 6
Information Element
value/remark
Algorithm identifier
A5/4
AUTHENTICATION REQUEST step 10
Information Element
value/remark
RAND
different than in step 4
AUTN Information Element
present
- Length = 16
- Calculated as defined for Test USIM
ASSIGNMENT COMMAND step 14
Information Element
value/remark
Cipher Mode Setting
A5/4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.8 Ciphering mode with cipher key Kc128 and algorithm changes
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.8.1 Conformance requirements
|
1. A ME supporting UMTS authentication challenge may support the following procedure: In order to avoid a synchronisation failure, if the same RAND is received twice, the mobile station shall store the received RAND together with the RES returned from the USIM in the volatile memory and compare it with any subsequently received RAND values, until the RAND value stored in the mobile station is deleted. If the stored RAND value is equal to the new received value in the AUTHENTICATION REQUEST message, then the mobile station shall not pass the RAND to the USIM, but shall immediately send the AUTHENTICATION RESPONSE message with the stored RES. If there is no valid stored RAND in the mobile station or the stored RAND is different from the new received value in the AUTHENTICATION REQUEST message, the mobile station shall pass the RAND to the USIM, shall override any previously stored RAND and RES with the new ones and start, or reset and restart timer T3218.
2 The ME with a USIM in use shall compute a new GSM Kc128 using the UMTS ciphering key and the UMTS integrity key from an established UMTS security context as specified in 3GPP TS 33.102 [5a]. The new GSM Kc128 shall be stored only in the ME.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
3 The ASSIGNMENT COMMAND message may contain a cipher mode setting IE. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel. In either case the ciphering key shall not be changed as long as the key length remains unchanged. However, in case of a switch between ciphering algorithms requiring different key lengths, i.e. 64 or 128 bits, a change from the 64 bit key to the 128 bit key or vice versa must be performed
|
4 In a UMTS authentication challenge, the new UMTS ciphering key, the new GSM ciphering key and the new UMTS integrity key calculated from the challenge information shall overwrite the previous UMTS ciphering key, GSM ciphering key and UMTS integrity key. The new UMTS ciphering key, GSM ciphering key and UMTS integrity key are stored on the USIM together with the ciphering key sequence number. Furthermore, in A/Gb mode when after the authentication procedure an A5 ciphering algorithm that requires a 128-bit ciphering key is taken into use, then a new GSM Kc128 shall also be calculated as described in the subclause 4.3.2.3a.
References
3GPP TS 44.018 subclause 3.4.3
3GPP TS 24.008 subclause 4.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.8.2 Test purpose
|
To verify that the MS handles correctly key length changes when the SS orders the MS to change from A5/1 to A5/4 and vice versa.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.8.8.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default settings.
Mobile Station:
Test USIM is plugged into the MS. The MS is in the "idle, updated" state, with a TMSI allocated.
Specific PICS statements
-
PIXIT statements
-
Foreseen Final State of the MS
"Idle, updated", with TMSI allocated.
Test Procedure
The MS is paged. The MS shall send at least one CHANNEL REQUEST message. The SS sends an IMMEDIATE ASSIGNMENT and the MS shall answer with a PAGING RESPONSE message .The SS sends an AUTHENTICATION REQUEST with AUTN Information Element present and the MS shall answer with AUTHENTICATION RESPONSE with correct RES. Then the SS sends a CIPHERING MODE COMMAND ordering the MS to start ciphering with algorithm A5/1. After transmission of this command the SS starts deciphering. The MS shall respond with a CIPHERING MODE COMPLETE message in ciphered mode using the 64 bit key Kc calculated during the authentication procedure.
The SS then sends another AUTHENTICATION REQUEST with AUTN Information Element present and the MS shall respond with AUTHENTICATION RESPONSE with correct RES The MS shall continue to use the old cipher key. Then the SS sends an ASSIGNMENT COMMAND with CIPHER MODE SETTING information element indicating to use algorithm A5/4. The MS shall respond with a ASSIGNMENT COMPLETE message in ciphered mode using the 128 bit cipher key Kc128 calculated during the previous authentication procedure.
After an identity procedure the SS then sends another AUTHENTICATION REQUEST with AUTN and the MS shall answer with an AUTHENTICATION RESPONSE with correct RES. Then the SS sends an ASSIGNMENT COMMAND with CIPHER MODE SETTING information element indicating to use algorithm A5/1. The MS completes the procedure by sending an ASSIGNMENT COMPLETE message in ciphered mode using the key calculated during the previous authentication.
After an identity procedure the SS sends a CHANNEL RELEASE to end the test.
Maximum Duration of Test
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns a SDCCH8
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
Cipher keys Kc and Kc128 have been calculated.
"Auth. Response Parameter" IE shall be bit exact with the value as produced by the authentication algorithm (RES in this case)
"Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.
7
SS -> MS
CIPHERING MODE COMMAND
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/1". The SS starts deciphering.
8
MS -> SS
CIPHERING MODE COMPLETE
Sent in ciphered mode using the cipher key Kc determined in step 6. The SS start enciphering.
9
SS -> MS
AUTHENTICATION REQUEST
10
MS -> SS
AUTHENTICATION RESPONSE
New cipher keys Kc and Kc128 have been calculated
Sent in ciphered mode using the cipher key Kc determined in step 6.
"Auth. Response Parameter" IE shall be bit exact with the value as produced by the authentication algorithm (RES in this case)
"Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.
11
SS -> MS
ASSIGNMENT COMMAND
SS assigns SDCCH4
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/4"
12
MS -> SS
ASSIGNMENT COMPLETE
Sent in ciphered mode using the cipher key Kc128 determined in step 6.
13
SS -> MS
IDENTITY REQUEST
14
MS -> SS
IDENTITY RESPONSE
15
SS -> MS
AUTHENTICATION REQUEST
16
MS -> SS
AUTHENTICATION RESPONSE
New cipher keys Kc and Kc128 have been calculated
Sent in ciphered mode using the cipher key Kc128 determined in step 6.
"Auth. Response Parameter" IE shall be bit exact with the value as produced by the authentication algorithm (RES in this case)
"Auth. Response Parameter (extension)" IE might be included if the RES value is more than 4 octets long.
17
SS -> MS
ASSIGNMENT COMMAND
SS assigns SDCCH8
Cipher Mode Setting = "Start Ciphering; cipher with algorithm A5/1"
18
MS -> SS
ASSIGNMENT COMPLETE
Sent in ciphered mode using cipher algorithm A5/1 and the cipher key Kc determined in step 6.
19
SS -> MS
IDENTITY REQUEST
20
MS -> SS
IDENTITY RESPONSE
21
SS -> MS
CHANNEL RELEASE
Specific Message Contents
AUTHENTICATION REQUEST step 5
Information Element
value/remark
RAND
Arbitrarily chosen
AUTN Information Element
present
- Length = 16
- Calculated as defined for Test USIM
CIPHERING MODE COMMAND step 7
Information Element
value/remark
Algorithm identifier
A5/1
AUTHENTICATION REQUEST step 9
Information Element
value/remark
RAND
different than in step 5
AUTN Information Element
present
- Length = 16
- Calculated as defined for Test USIM
ASSIGNMENT COMMAND step 11
Information Element
value/remark
Channel Description
- Channel Type
SDCCH4 (same type as old channel)
- TDMA offset
Chosen arbitrarily, but different to the one in use.
- Timeslot Number
Chosen arbitrarily, but different to the one in use.
Cipher Mode Setting
A5/4.
ASSIGNMENT COMMAND step 17
Information Element
value/remark
Channel Description
- Channel Type
SDCCH8
- TDMA offset
Chosen arbitrarily, but different to the one in use.
- Timeslot Number
Chosen arbitrarily, but different to the one in use.
- Training Sequence Code
5 (same as the BCC).
Cipher Mode Setting
A5/1
IDENTITY REQUEST step 17 and 19
Information Element
value/remark
Algorithm identifier
001 IMSI
AUTHENTICATION REQUEST step 15
Information Element
value/remark
RAND
different than in step 9
AUTN Information Element
present
- Length = 16
- Calculated as defined for Test USIM
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.9 Test of additional assignment
|
The Additional Assignment procedure is used to change an MS's channel configuration from Lm + ACCH to Lm + Lm + ACCH. It is therefore only relevant to those mobiles which perform such an operation.
No tests are specified at the moment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.10 Test of partial release
|
The Partial Release procedure is used to change an MS's channel configuration from Lm + Lm + ACCH to Lm + ACCH. It is therefore only relevant to those mobiles which perform such an operation.
No tests are specified at the moment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
26.6.11 Test of classmark
|
References to Class Mark related PICS values are provided in the table 26.6.11a and 26.6.11b.
Table 26.6.11a: Mobile Station Classmark 2 information element
Item
IE
Values
Mnemonic
1
Revision level
Revision level Bits
7
6
0
0
GSM Phase 1
0
1
GSM Phase 2 MS
1
0
MS supporting R99 or later
1
1
Reserved for Future
TSPC_Revision_Level_GSM_Phase_1
TSPC_Revision_Level_GSM_Phase_2
TSPC_Revision_Level_MS_supporting_R99_or_later
2
ES IND
Bit 5
0
"Controlled Early Classmark Sending" option is not implemented in the MS
1
"Controlled Early Classmark Sending" option is implemented in the MS
TSPC_Controlled_Early_Classmark_Sending
3
A5/1
0
A5/1 Available
1
A5/1 not Available
TSPC_Feat_A51
4
RF power capability
When T-GSM 380, T-GSM 410, GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, GSM 900 P, E T [or R] band is used
Bits
3
2
1
0
0
0
Class 1
0
0
1
Class 2
0
1
0
Class 3
0
1
1
Class 4
1
0
0
Class 5
Other values are reserved
When the GSM 1800 or GSM 1900 band is used
Bits
3
2
1
0
0
0
Class 1
0
0
1
Class 2
0
1
0
Class 3
Other values are reserved
When UMTS is used, an MS not supporting any GSM band or a multiband GSM MS
Bits
3
2
1
1
1
1
RF Power capability is irrelevant in this information element
Other values are reserved
TSPC_Type_GSM_Class2
TSPC_Type_GSM_Class3
TSPC_Type_GSM_Class4
TSPC_Type_GSM_Class5
TSPC_Type_DCS_Class1
TSPC_Type_DCS_Class2
TSPC_Type_DCS_Class3
TSPC_Type_PCS_Class1
TSPC_Type_PCS_Class2
TSPC_Type_PCS_Class3
5
PS capability
Bit 7
0
PS capability not present
1
PS capability present
TSPC_AddInfo_PseudoSynch
6
SS Screening Indicator
Bits
6
5
0
0
defined in 3GPP TS 24.080 [24]
0
0
defined in 3GPP TS 24.080 [24]
0
1
defined in 3GPP TS 24.080 [24]
1
1
defined in 3GPP TS 24.080 [24]
TSPC_SS_Screening_Indictator_in_CM2
7
SM capability
Bit 4
0
MS not support mobile terminated point to point SMS
1
MS support mobile terminated point to point SMS
TSPC_Serv_TS21
8
VBS notification reception
Bit 3
0
No VBS capability or no notifications wanted
1
VBS capability and notifications wanted
TSPC_VBS_Notification_Reception
9
VGCS notification reception
Bit 2
0
No VGCS capability or no notifications wanted
1
VGCS capability and notifications wanted
TSPC_VCGS_Notification_Reception
10
Frequency Capability
When a GSM 900 band is used
Bit 1
0
The MS does not support the E-GSM or R-GSM band
1
The MS does support the E-GSM or R-GSM
TSPC_Type_GSM_E_Band
TSPC_Type_GSM_R_Band
11
CM3
Bit 8
0
The MS does not support any options that are indicated in CM3
1
The MS supports options that are indicated in classmark 3 IE
TSPC_ClassMK3_Info_available
12
LCS VA Capability
Bit 6
0
location request notification via CS domain not supported
1
location request notification via CS domain supported
TSPC_Location_Request_via_CS_Domain
13
UCS2 treatment
Bit 5
0
the ME has a preference for the default alphabet (defined in 3GPP TS 23.038 [8b]) over UCS2.
1
the ME has no preference between the use of the default alphabet and the use of UCS2.
TSPC_UCS2_treatment
14
SoLSA
Bit 4
0
The ME does not support SoLSA.
1
The ME supports SoLSA.
TSPC_SoLSA
15
CM Service Prompt
Bit 3
0
"Network initiated MO CM connection request" not supported.
1
"Network initiated MO CM connection request" supported for at least one CM protocol.
TSPC_CM_Service_Prompt
16
A5/3
Bit 2
0
encryption algorithm A5/3 not available
1
encryption algorithm A5/3 available
TSPC_Feat_A53
17
A5/2
Bit 1
0
encryption algorithm A5/2 not available
1
Not used.
Shall not be supported anymore
Table 26.6.11b: Mobile Station Classmark 3 Information Element
Item
IE
Values
Mnemonic
1
Multiband supported
000
101
110
001
010
100
Band 1 supported
Bit 1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 P-GSM not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 P-GSM supported
|
Band 2 supported
Bit 2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 E-GSM or R-GSM not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 E-GSM or R-GSM supported
|
Band 3 supported
Bit 3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 GSM 1800 not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 GSM 1800 supported
|
TSPC_Type_GSM_P_Band
TSPC_Type_GSM_E_Band
TSPC_Type_GSM_R_Band
TSPC_Type_DCS_Band
Note: Due to the shared radio frequency channel numbers between DCS 1800 and PCS 1900, even if both DCS_1800_BAND and PCS_1900_BAND are set to TRUE, the MS can only ever indicate support for one of these bands
2
A5 bits
A5/4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 Encryption algorithm A5/4 not available
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 Encryption algorithm A5/4 available
|
A5/5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 Encryption algorithm A5/5 not available
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 Encryption algorithm A5/5 available
|
A5/6
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 Encryption algorithm A5/6 not available
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 Encryption algorithm A5/6 available
|
A5/7
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 Encryption algorithm A5/7 not available
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 Encryption algorithm A5/7 available
|
TSPC_Feat_A54
A5/5 Feature is not available and should set to 0
A5/6 Feature is not available and should set to 0
A5/7 Feature is not available and should set to 0
3
Associated Radio capability 1 and 2
4 bit fields
If either of P-GSM or E-GSM or R-GSM is supported, the radio capability 1 field indicates the radio capability for P-GSM, E-GSM or R-GSM, and the radio capability 2 field indicates the radio capability for GSM 1800 if supported, and is spare otherwise.
If none of P-GSM or E-GSM or R-GSM are supported, the radio capability 1 field indicates the radio capability for GSM 1800, and the radio capability 2 field is spare.
The radio capability contains the binary coding of the power class associated with the band indicated in multiband support bits (see 3GPP TS 45.005 [33]).
TSPC_Type_GSM_Class2
TSPC_Type_GSM_Class3
TSPC_Type_GSM_Class4
TSPC_Type_GSM_Class5
TSPC_Type_DCS_Class1
TSPC_Type_DCS_Class2
TSPC_Type_DCS_Class3
4
R-GSM band Associated Radio Capability
3 bit field
In case where the R-GSM band is supported the R-GSM band associated radio capability field contains the binary coding of the power class associated (see 3GPP TS 45.005) (regardless of the number of GSM bands supported). A mobile station supporting the R-GSM band shall also when appropriate, (see 10.5.1.6) indicate its support in the 'FC' bit in the Mobile Station Classmark 2 information element.
NOTE: The coding of the power class for P-GSM, E-GSM, R-GSM and GSM 1800 in radio capability 1 and/or 2 is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_GSM_Class2 TSPC_Type_GSM_Class3 TSPC_Type_GSM_Class4 TSPC_Type_GSM_Class5
5
HSCSD Multi Slot Class
5 bit field
In case the MS supports the use of multiple timeslots for HSCSD then the HSCSD Multi Slot Class field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002 [32].
TSPC_Type_HSCSD_Multislot
6
UCS2 treatment
0 the ME has a preference for the default alphabet over UCS2.
1 the ME has no preference between the use of the default alphabet and the use of UCS2.
TSPC_UCS2_treatment
7
Extended Measurement Capability
0 the MS does not support Extended Measurements
1 the MS supports Extended Measurements
TSPC_Extended_Measurement_Capability
8
SMS_VALUE (Switch-Measure-Switch)
Bits
4 3 2 1
0 0 0 0 1/4 timeslot (~144
microseconds)
0 0 0 1 2/4 timeslot (~288
microseconds)
0 0 1 0 3/4 timeslot (~433
microseconds)
. . .
1 1 1 1 16/4 timeslot (~2307
microseconds)
TSPC_SMS_VALUE_SMS
9
SM_VALUE (Switch-Measure)
Bits
4 3 2 1
0 0 0 0 1/4 timeslot (~144
microseconds)
0 0 0 1 2/4 timeslot (~288
microseconds)
0 0 1 0 3/4 timeslot (~433
microseconds)
. . .
1 1 1 1 16/4 timeslot (~2307
microseconds)
TSPC_SMS_VALUE_SM
10
MS Positioning Method
MS assisted E-OTD
Bit 5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 MS assisted E-OTD not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 MS assisted E-OTD supported
|
MS based E-OTD
Bit 4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 MS based E-OTD not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 MS based E-OTD supported
|
MS assisted GPS
Bit 3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 MS assisted GPS not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 MS assisted GPS supported
|
MS based GPS
Bit 2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 MS based GPS not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 MS based GPS supported
|
MS Conventional GPS
Bit 1
0 conventional GPS not supported
1 conventional GPS supported
TSPC_EOTD_ASSIST TSPC_EOTD_MS_BASED
TSPC_A-GPS_Assist
TSPC_A-GPS_Based
TSPC_Conv-GPS
11
ECSD Multi Slot class
An MS that supports ECSD shall include this field to indicate its ECSD capability. Whether the MS is capable of 8-PSK modulation in uplink is indicated by the value of the Modulation Capability field in the 8-PSK struct. The ECSD Multi Slot Class field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002 [32].
TSPC_Type_ECSD_Multislot_Class
12
8-PSK struct
0 8-PSK struct not present
1 8-PSK struct present
Note: The MS shall include the 8-PSK struct if it supports ECSD or DTM EGPRS or both
TSPC_8-PSK_Struct
13
Modulation Capability
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 8-PSK supported for downlink
|
reception only
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 8-PSK supported for uplink transmission and downlink reception
|
TSPC_8-PSK_Struct
TSPC_Type_DTM_EGPRS_8PSK_uplink TSPC_Type_ECSD_8PSK_uplink
14
8-PSK RF Power Capability 1
Bits 2 1
0 0 Reserved
0 1 Power class E1
1 0 Power class E2
1 1 Power class E3
TSPC_8-PSK_Struct
TSPC_8-PSK_PowerCap1
TSPC_Type_GSM_ClassE1
TSPC_Type_GSM_ClassE2
TSPC_Type_GSM_ClassE3
TSPC_Type_GSM_850_ClassE1
TSPC_Type_GSM_850_ClassE2
TSPC_Type_GSM_850_ClassE3
15
8-PSK RF Power Capability 2
Bits 2 1
0 0 Reserved
0 1 Power class E1
1 0 Power class E2
1 1 Power class E3
TSPC_8-PSK_Struct
TSPC_8-PSK_PowerCap2
TSPC_Type_DCS_ClassE1
TSPC_Type_DCS_ClassE2
TSPC_Type_DCS_ClassE3
TSPC_Type_PCS_ClassE1
TSPC_Type_PCS_ClassE2
TSPC_Type_PCS_ClassE3
16
GSM 400 Bands Supported
Bits
2 1
0 1 GSM 480 supported,
GSM 450 not supported
1 0 GSM 450 supported,
GSM 480 not supported
1 1 GSM 450 supported,
GSM 480 supported
TSPC_Type_GSM_450_Band
TSPC_Type_GSM_480_Band
17
GSM 400 Associated Radio Capability
4 Bit field
If either GSM 450 or GSM 480 or both is supported, the GSM 400 Associated Radio Capability field indicates the radio capability for GSM 450 and/or GSM 480.
The radio capability contains the binary coding of the power class associated with the band indicated in GSM 400 Bands Supported bits (see 3GPP TS 45.005 [33]).
NOTE: The coding of the power class for GSM 450 and GSM 480 in GSM 400 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_GSM_400_Class2
TSPC_Type_GSM_400_Class3
TSPC_Type_GSM_400_Class4
TSPC_Type_GSM_400_Class5
18
GSM 850 Associated Radio Capability
4 Bit field
See the semantic rule for the sending of this field.
This field indicates whether GSM 850 band is supported and its associated radio capability.
The radio capability contains the binary coding of the power class associated with the GSM 850 band (see 3GPP TS 45.005 [33]).
Note: the coding of the power class for GSM 850 in GSM 850 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_GSM_850_Class2
TSPC_Type_GSM_850_Class3
TSPC_Type_GSM_850_Class4
TSPC_Type_GSM_850_Class5
19
GSM 1900 Associated Radio Capability
4 Bit field
See the semantic rule for the sending of this field.
This field indicates whether GSM 1900 band is supported and its associated radio capability.
The radio capability contains the binary coding of the power class associated with the GSM 1900 band (see 3GPP TS 45.005 [33]).
Note: the coding of the power class for GSM 1900 in GSM 1900 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_PCS_Class1
TSPC_Type_PCS_Class2
TSPC_Type_PCS_Class3
20
UMTS FDD Radio Access Technology Capability
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 UMTS FDD not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 UMTS FDD supported
|
TSPC_Type_UTRAN_FDD
21
UMTS 3.84 Mcps TDD Radio Access Technology Capability
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 UMTS 3.84 Mcps TDD not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 UMTS 3.84 Mcps TDD supported
|
TSPC_Type_UTRAN3.84_TDD
22
CDMA 2000 Radio Access Technology Capability
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 CDMA2000 not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 CDMA2000 supported
|
TSPC_CDMA2000
23
DTM GPRS Multi Slot Class
Bit
2 1
0 0 Unused. If received, the
network shall interpret
this as ‘01’
0 1 Multislot class 5
supported
1 0 Multislot class 9
supported
1 1 Multislot class 11
supported
TSPC_DTM_GPRS_Multislot_Class_1
TSPC_DTM_GPRS_Multislot_Class_5
TSPC_DTM_GPRS_Multislot_Class_9
TSPC_DTM_GPRS_Multislot_Class_11
24
Single Slot DTM
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 Single Slot DTM not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 Single Slot DTM supported
|
TSPC_DTM_GPRS_Singleslot_Allocation
TSPC_DTM_EGPRS_Singleslot_Allocation
25
DTM EGPRS Multi Slot Class
This field indicates the DTM GPRS multislot capabilities of the MS. It is coded as follows:
Bit
2 1
0 0 Unused. If received, the network shall interpret this as ‘01’
0 1 Multislot class 5 supported
1 0 Multislot class 9 supported
1 1 Multislot class 11 supported
If a multislot class type 1 MS indicates the support of a DTM GPRS multislot class for which three uplink timeslots can be assigned, the mobile station shall support Extended Dynamic Allocation.
This field shall contain one of the following values if the DTM GPRS High Multi Slot Class field is present:
• Multislot class 9 if DTM GPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41;
• Multislot class 11 if DTM GPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44.
The same multislot capability is applicable also for EGPRS2 if supported.
TSPC_DTM_EGPRS_Multislot_Class_5
TSPC_DTM_EGPRS_Multislot_Class_9
TSPC_DTM_EGPRS_Multislot_Class_11
26
Single Band Support
This field shall be sent if the mobile station supports UMTS and one and only one GSM band with the exception of R-GSM; this field shall not be sent otherwise
TSPC_SingleBand_Support
27
GSM Band
Bits
4 3 2 1
0 0 0 0 E-GSM supported
0 0 0 1 P-GSM supported
0 0 1 0 GSM 1800 supported
0 0 1 1 GSM 450 supported
0 1 0 0 GSM 480 supported
0 1 0 1 GSM 850 supported
0 1 1 0 GSM 1900 supported
0 1 1 1 GSM 750 supported
1 0 0 0 GSM 710 supported
1 0 0 1 T-GSM 810 supported
TSPC_Type_GSM_P_Band
TSPC_Type_GSM_E_Band
TSPC_Type_DCS_Band
TSPC_Type_GSM_450_Band
TSPC_Type_GSM_480_Band
TSPC_Type_PCS_Band
TSPC_Type_GSM_750_Band
TSPC_Type_GSM_850_Band
TSPC_Type_GSM_710_Band
TSPC_Type_T_GSM_810_Band
28
GSM 750 Associated Radio Capability
See the semantic rule for the sending of this field.
This field indicates whether GSM 750 band is supported and its associated radio capability.
The radio capability contains the binary coding of the power class associated with the GSM 750 band (see 3GPP TS 45.005 [33]).
NOTE: The coding of the power class for GSM 750 in GSM 750 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_GSM_750_Class2
TSPC_Type_GSM_750_Class3
TSPC_Type_GSM_750_Class4
TSPC_Type_GSM_750_Class5
29
UMTS 1.28 Mcps TDD Radio Access Technology Capability
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 UMTS 1.28 Mcps TDD not supported
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 UMTS 1.28 Mcps TDD supported
|
TSPC_Type_UTRAN1.28_TDD
30
GERAN Feature Package 1
0 GERAN feature package 1 not supported.
1 GERAN feature package 1 supported.
TSPC_GERAN_FEATURE_PACKAGE_1
31
Extended DTM GPRS Multi Slot Class
DGMSC Bit 2 1 Bit 2 1
0 0 0 0 Unused. If received, it shall be interpreted as ‘01 00’
0 0 0 1 Unused. If received, it shall be interpreted as ‘01 00’
0 0 1 0 Unused. If received, it shall be interpreted as ‘01 00’
0 0 1 1 Unused. If received, it shall be interpreted as ‘01 00’
0 1 0 0 Multislot class 5 supported
0 1 0 1 Multislot class 6 supported
0 1 1 0 Unused. If received, it shall be interpreted as ‘01 00’
0 1 1 1 Unused. If received, it shall be interpreted as ‘01 00’
1 0 0 0 Multislot class 9 supported
1 0 0 1 Multislot class 10 supported
1 0 1 0 Unused. If received, it shall be interpreted as ‘10 00’
1 0 1 1 Unused. If received, it shall be interpreted as ‘10 00’
1 1 0 0 Multislot class 11 supported
1 1 0 1 Unused. If received, it shall be interpreted as ’11 00’
1 1 1 0 Unused. If received, it shall be interpreted as ’11 00’
1 1 1 1 Unused. If received, it shall be interpreted as ’11 00’
The presence of this field indicates that the MS supports combined fullrate and halfrate GPRS channels in the downlink.When this field is not present, the MS supports the multislot class indicated by the DTM GPRS Multi Slot Class field.
If this field is included, it shall contain one of the following values if the DTM GPRS High Multi Slot Class field is present:
• Multislot class 10 if DTM GPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41;
Multislot class 11 if DTM GPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44.
TSPC_DTM_GPRS_Multislot_Class_5
TSPC_DTM_GPRS_Multislot_Class_6
TSPC_DTM_GPRS_Multislot_Class_9
TSPC_DTM_GPRS_Multislot_Class_10
TSPC_DTM_GPRS_Multislot_Class_11
TSPC_DTM_GPRS_Multislot_Class31
Or
TSPC_DTM_GPRS_Multislot_Class36
Or
TSPC_DTM_GPRS_Multislot_Class41
TSPC_DTM_GPRS_Multislot_Class32
Or
TSPC_DTM_GPRS_Multislot_Class37
TSPC_DTM_GPRS_Multislot_Class33
Or
TSPC_DTM_GPRS_Multislot_Class38
or
TSPC_DTM_GPRS_Multislot_Class42
TSPC_DTM_GPRS_Multislot_Class43
TSPC_DTM_GPRS_Multislot_Class44
32
Extended DTM EGPRS Multi Slot Class
This field is not considered when the DTM EGPRS Multi Slot Class field is not included. This field indicates the extended DTM EGPRS multislot capabilities of the MS and shall be interpreted in conjunction with the DTM EGPRS Multi Slot Class field. This field is coded as the Extended DTM GPRS Multi Slot Class field. The presence of this field indicates that the MS supports combined fullrate and halfrate GPRS channels in the downlink. When this field is not present, the MS supports the multislot class indicated by the DTM EGPRS Multi Slot Class field.
If this field is included, it shall contain one of the following values if the DTM EGPRS High Multi Slot Class field is present:
- Multislot class 10 if DTM EGPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41;
- Multislot class 11 if DTM EGPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44.
TSPC_DTM_EGPRS_Multislot_Class_10
TSPC_DTM_EGPRS_Multislot_Class_11
TSPC_DTM_EGPRS_Multislot_Class_31
TSPC_DTM_EGPRS_Multislot_Class_36
TSPC_DTM_EGPRS_Multislot_Class_41
TSPC_DTM_EGPRS_Multislot_Class_32
TSPC_DTM_EGPRS_Multislot_Class_37
TSPC_DTM_EGPRS_Multislot_Class_33
TSPC_DTM_EGPRS_Multislot_Class_38
TSPC_DTM_EGPRS_Multislot_Class_42
TSPC_DTM_EGPRS_Multislot_Class_43
TSPC_DTM_EGPRS_Multislot_Class_44
33
High Multislot Capability
This field indicates the support of multislot classes 30 to 45, see 3GPP TS 45.002 [32].
The High Multislot Capability is individually combined with each multislot class field sent by the MS (the possible multislot class fields are: GPRS multislot class, EGPRS multislot class) to extend the related multislot class with the rule described in the MS Radio Access Capability IE. The same capability is applicable also to EGPRS2 if supported.
TSPC_Type_GPRS_Multislot_Class30
to
TSPC_Type_GPRS_Multislot_Class45
TSPC_Type_EGPRS_Multislot_Class30
to
TSPC_Type_EGPRS_Multislot_Class45
34
GERAN Iu Mode Capabilities
This field indicates if the mobile station supports GERAN Iu mode. Furthermore, it indicates the GERAN Iu mode capabilities of the mobile station. The field shall be included if the mobile station supports GERAN Iu mode. If the field is not present, the mobile station does not support GERAN Iu mode.
TSPC_GERAN_IuMode_Capability
35
FLO Iu Capability
0 FLO in GERAN Iu mode not supported
1 FLO in GERAN Iu mode supported
TSPC_FLO_Iu_Capability
36
GERAN Feature Package 2
0 GERAN feature package 2 not supported.
1 GERAN feature package 2 supported.
TSPC_GERAN_FEATURE_PACKAGE_2
37
Void
38
GMSK Multislot Power Profile
Bits
2 1
0 0 GMSK_MULTISLOT_POWER_PROFILE 0
0 1 GMSK_MULTISLOT_POWER_PROFILE 1
1 0 GMSK_MULTISLOT_POWER_PROFILE 2
1 1 GMSK_MULTISLOT_POWER_PROFILE 3
TSPC_Type_GMSK_Multislot_Power_Profile_0
TSPC_Type_GMSK_Multislot_Power_Profile_1
TSPC_Type_GMSK_Multislot_Power_Profile_2
TSPC_Type_GMSK_Multislot_Power_Profile_3
39
8-PSK Multislot Power Profile
Bits
2 1
0 0 8-PSK_MULTISLOT_POWER_PROFILE 0
0 1 8-PSK_MULTISLOT_POWER_PROFILE 1
1 0 8-PSK_MULTISLOT_POWER_PROFILE 2
1 1 8-PSK_MULTISLOT_POWER_PROFILE 3
TSPC_Type_8-PSK_Multislot_Power_Profile_0
TSPC_Type_8-PSK_Multislot_Power_Profile_1
TSPC_Type_8-PSK_Multislot_Power_Profile_2
TSPC_Type_8-PSK_Multislot_Power_Profile_3
40
T-GSM 400 Bands Supported
Bits
2 1
0 1 T-GSM 380 supported, T-GSM 410 not supported
1 0 T-GSM 410 supported, T-GSM 380 not supported
1 1 T-GSM 410 supported, T-GSM 380 supported
TSPC_Type_T_GSM_380_Band
TSPC_Type_T_GSM_410_Band
41
T-GSM 400 Associated Radio Capability
If either T-GSM 410 or T-GSM 380 or both is supported, the T-GSM 400 Associated Radio Capability field indicates the radio capability for T-GSM 410 and/or T-GSM 380.
The radio capability contains the binary coding of the power class associated with the band indicated in T-GSM 400 Bands Supported bits (see 3GPP TS 45.005 [33]).
NOTE: The coding of the power class for T-GSM 410 and T-GSM 380 in T-GSM 400 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
TSPC_Type_T_GSM_400_Class2
TSPC_Type_T_GSM_400_Class3
TSPC_Type_T_GSM_400_Class4
TSPC_Type_T_GSM_400_Class5
42
T-GSM 900 Associated Radio Capability
See the semantic rule for the sending of this field.
This field indicates whether T-GSM 900 band is supported and its associated radio capability.
The radio capability contains the binary coding of the power class associated with the T-GSM 900 band (see 3GPP TS 45.005 [33]).
Note: the coding of the power class for T-GSM 900 in T-GSM 900 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements.
Shall not be supported anymore
43
Downlink Advanced Receiver Performance
Bits
2 1
0 0 Downlink Advanced Receiver Performance not supported
0 1 Downlink Advanced Receiver Performance – phase I supported
1 0 Downlink Advanced Receiver Performance – phase II supported
NOTE 1)
TSPC_DARP_Phase1
TSPC_DARP_Phase2
44
DTM Enhancements Capability
This field indicates whether the mobile station supports enhanced DTM CS establishment and enhanced DTM CS release or not. It is coded as follows:
0 The mobile station does not support enhanced DTM CS establishment and enhanced DTM CS release procedures.
1 The mobile station supports enhanced DTM CS establishment and enhanced DTM CS release procedures.
TSPC_Enhanced_DTM_CS
45
DTM GPRS High Multi Slot Class
Bit
3 2 1
0 0 0 Unused. If received, the network shall interpret this as ‘0 0 1’
0 0 1 Multislot class 31 or 36 supported
0 1 0 Multislot class 32 or 37 supported
0 1 1 Multislot class 33 or 38 supported
1 0 0 Multislot class 41 supported
1 0 1 Multislot class 42 supported
1 1 0 Multislot class 43 supported
1 1 1 Multislot class 44 supported
TSPC_DTM_GPRS_Multislot_Class_31
TSPC_DTM_GPRS_Multislot_Class_32
TSPC_DTM_GPRS_Multislot_Class_33
TSPC_DTM_GPRS_Multislot_Class_36
TSPC_DTM_GPRS_Multislot_Class_37
TSPC_DTM_GPRS_Multislot_Class_38
TSPC_DTM_GPRS_Multislot_Class_41
TSPC_DTM_GPRS_Multislot_Class_42
TSPC_DTM_GPRS_Multislot_Class_43
TSPC_DTM_GPRS_Multislot_Class_44
46
Offset required
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 The mobile station does not require the offset
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
1 The mobile station requires the offset
|
TSPC_Offset_Required
47
DTM EGPRS High Multi Slot Class
This field indicates the DTM EGPRS multislot capabilities of the MS. This field may be included only if the mobile station supports EGPRS DTM. This field is coded as the DTM GPRS High Multi Slot Class field. When this field is not present, the MS supports the DTM multislot class indicated by the DTM EGPRS Multi Slot Class field.
The values '0 0 1', '0 1 0' and '0 1 1' shall be interpreted as indicating DTM EGPRS multislot class 36, 37 or 38 respectively if the Offset required field indicates that the Timing Advance offset t0 is required; in all other cases those codepoints shall be interpreted as indicating DTM EGPRS multislot class 31, 32 or 33 respectively.
The same multislot capability is applicable also for EGPRS2 if supported
TSPC_DTM_EGPRS_Multislot_Class_31
TSPC_DTM_EGPRS_Multislot_Class_32
TSPC_DTM_EGPRS_Multislot_Class_33
TSPC_DTM_EGPRS_Multislot_Class_36
TSPC_DTM_EGPRS_Multislot_Class_37
TSPC_DTM_EGPRS_Multislot_Class_38
48
Repeated ACCH Capability
1 bit field
This field indicates whether the MS supports Repeated SACCH and Repeated Downlink FACCH (see 3GPP TS 44.006 [76]). It is coded as follows:
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
0 The mobile station does not support Repeated SACCH
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.