10 Generic call set up procedures
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
10.1 Generic call set-up procedure for mobile terminating speech calls
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Terminating Speech call set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.1.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.1.2 Definition of system information messages
The following parameters shall be coded into the system information messages. Parameters shall be coded according to 3GPP TS 04.08 / 3GPP TS 44.018.
The RACH Control Parameters IE shall be the same in SYSTEM INFORMATION TYPE 1, TYPE 2, TYPE 3 and TYPE 4 messages.
The Location Area Identification IE, Cell Selection Parameters IE, and P1 bit shall be the same in SYSTEM INFORMATION TYPE 3 and TYPE 4 messages.
SYSTEM INFORMATION TYPE 1
|
Information Element |
Value/remark |
|
Cell channel description |
Includes the hopping sequence ARFCNs, if hopping is used |
|
RACH control parameters |
|
|
MAX RETRANS |
Any Value |
|
TX-INTEGER |
Any Value |
|
CELL BAR ACCESS |
Not barred |
|
CALL RE-ESTABLISHMENT |
Not Allowed |
|
EMERGENCY CALL |
Allowed |
|
ACCESS CONTROL CLASS |
None Barred |
|
(0…9, 11…15) |
|
|
SI1 rest octets |
Spare Octets |
SYSTEM INFORMATION TYPE 2
|
Information Element |
Value/remark |
|
BCCH Frequency list |
Indicates seven surrounding cells on any ARFCN of the supported band, excluding ARFCNs in or immediately adjacent to those specified in subclause 6.2 |
|
NCC permitted |
|
|
NCC PERMITTED |
e.g. all NCCs permitted |
|
RACH control parameters |
|
|
MAX RETRANS |
Any Value |
|
TX-INTEGER |
Any Value |
|
CELL BAR ACCESS |
Not barred |
|
CALL RE-ESTABLISHMENT |
Not Allowed |
|
EMERGENCY CALL |
Allowed |
|
ACCESS CONTROL CLASS |
None Barred |
|
(0…9, 11…15) |
SYSTEM INFORMATION TYPE 3
|
Information Element |
Value/remark |
|
Cell identity |
|
|
CI VALUE |
0001 hex (not relevant) |
|
Location Area Identification |
|
|
MCC |
001 decimal (not relevant) |
|
MNC |
01 or 011 (see Table 3.1) decimal (not relevant) |
|
LAC |
0001 hex (not relevant) |
|
Control Channel Description |
|
|
MSCR |
1 MSC is Release ’99 onwards |
|
ATT (IMSI att/det) |
MS shall not apply (not relevant) |
|
BS-AG-BLKS-RES |
0 blocks reserved (not relevant) |
|
CCCH-CONF |
Combined CCCH/SDCCH (not relevant) |
|
BS-PA-MFRMS |
5 multiframes (not relevant) |
|
T3212 |
Infinite |
|
Cell options |
|
|
PWRC |
power control not set |
|
DTX |
MS must not use DTX |
|
RADIO LINK TIME-OUT |
8 |
|
Cell selection parameters |
|
|
CELL RESELECT HYSTERESIS |
0 dB |
|
MS-TXPWR-MAX-CCH |
Max. output power of MS |
|
RXLEV-ACCESS-MIN |
‑90 dBm |
|
ACS |
There are no additional cell parameters included in SI7 and SI8 |
|
NECI |
New establishment cause not supported |
|
RACH control parameters |
|
|
MAX RETRANS |
Any Value |
|
TX-INTEGER |
Any Value |
|
CELL BAR ACCESS |
Not barred |
|
CALL RE-ESTABLISHMENT |
Not Allowed |
|
EMERGENCY CALL |
Allowed |
|
ACCESS CONTROL CLASS |
None Barred |
|
(0…9, 11…15) |
|
|
SI3 rest octets |
|
|
P1 |
C2 parameters not present |
SYSTEM INFORMATION TYPE 4
|
Information Element |
Value/remark |
|
Location Area Identification |
|
|
MCC |
001 decimal (not relevant) |
|
MNC |
01 or 011 (see Table 3.1) decimal (not relevant) |
|
LAC |
0001 hex (not relevant) |
|
Cell selection parameters |
|
|
CELL RESELECT HYSTERESIS |
0 dB |
|
MS-TXPWR-MAX-CCH |
Max. output power of MS |
|
RXLEV-ACCESS-MIN |
‑90 dBm |
|
RACH control parameters |
|
|
MAX RETRANS |
Any Value |
|
TX-INTEGER |
Any Value |
|
CELL BAR ACCESS |
Not barred |
|
CALL RE-ESTABLISHMENT |
Not Allowed |
|
EMERGENCY CALL |
Allowed |
|
ACCESS CONTROL CLASS |
None Barred |
|
(0…9, 11…15) |
|
|
CBCH Channel Description |
Omitted |
|
CBCH Mobile Allocation |
Omitted |
|
SI4 rest octets |
|
|
P1 |
C2 parameters not present |
SYSTEM INFORMATION TYPE 5
|
Information Element |
Value/remark |
|
Neighbour cell description |
As BCCH Frequency list in SI 2 |
SYSTEM INFORMATION TYPE 6
|
Information Element |
Value/remark |
|
Cell identity |
|
|
CI VALUE |
0001 hex (not relevant) |
|
Location Area Identification |
|
|
MCC |
001 decimal (not relevant) |
|
MNC |
01 or 011 (see Table 3.1) decimal (not relevant |
|
LAC |
0001 hex (not relevant) |
|
Cell options |
|
|
PWRC |
power control not set |
|
DTX |
MS must not use DTX |
|
RADIO LINK TIME-OUT |
8 |
|
NCC permitted |
|
|
NCC PERMITTED |
e.g. all NCCs permitted |
10.1.3 Procedure
An MS terminating call on a TCH/FS shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "answer to paging" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
9 |
SS |
SS starts ciphering |
|
|
10 |
SS -> MS |
SETUP |
Message contains the signal IE |
|
11 |
MS -> SS |
CALL CONFIRMED |
|
|
A12 |
MS -> SS |
CONNECT |
|
|
B12 |
MS -> SS |
ALERTING |
|
|
B13 |
MS |
An alerting indication as defined in a PICS/PIXIT statement given by the MS |
|
|
B14 |
MS |
The MS is made to accept the call in a way described in a PICS/PIXIT statement |
|
|
B15 |
MS -> SS |
CONNECT |
|
|
16 |
SS -> MS |
ASSIGNMENT COMMAND |
|
|
17 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
18 |
MS |
The TCH is through connected in both directions |
|
|
19 |
SS -> MS |
CONNECT ACKNOWLEDGE |
10.1.4 Specific message contents
PAGING REQUEST TYPE 1 (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.22) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal Paging |
|
Channel Needed |
spare, any channel |
|
Mobile Identity 1 |
|
|
Odd/even no of digits |
As applicable for TMSI |
|
Type of Identity |
TMSI |
|
Identity digits |
As applicable |
|
Mobile Identity 2 |
Omitted |
|
P1 rest octets |
Spare octets |
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH/SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrary |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
SETUP (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.23) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
|
|
Signal |
any non-reserved value |
|
Bearer capability 1 |
Appropriate for the basic service selected for the test or omitted |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Channel Description |
|
|
Channel type |
Bm + ACCHs |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Channel mode |
Speech full rate |
CONNECT ACKNOWLEDGE (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.6) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
10.1a Generic call set-up procedure for mobile terminating signalling only connection
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.1a.1 Initial conditions
See subclause 10.1.1
PIXIT Statements
– Way in the MS to avoid the disconnect of the RR connection due to MM or higher layer timers.
10.1a.2 Definition of system information messages
See subclause 10.1.2
10.1a.3 Procedure
An RR connection on TCH in signalling only mode shall be established under ideal radio conditions with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "answer to paging" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
Note: To allow testing on TCH (signalling only) during a long period the MS manufacturer has to provide a way to avoid the disconnect of the RR connection due to MM or higher layer timers. |
|||
10.1a.4 Specific message contents
PAGING REQUEST TYPE 1 (3GPP TS 44.018, subclause 9.1.22) to the MS
Same as section 10.1.4
IMMEDIATE ASSIGNMENT (3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
TCH/F + ACCHs (Note 1) |
|
Time slot number |
Default or as defined by the test case |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
Default or as defined by the test case |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
NOTE 1: Channel mode is ‘signalling only’ after Immediate Assignment.
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
Same as section 10.1.4
10.2 Generic call set-up procedure for mobile originating speech calls
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Originating Speech (MOC) call set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.2.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.2.2 Definition of system information messages
See subclause 10.1.2.
10.2.3 Procedure
An MS originating call on a TCH/FS shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
"called number" entered |
|
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "originating call, NECI <> 1" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
9 |
SS |
SS starts ciphering |
|
|
10 |
MS -> SS |
SETUP |
|
|
11 |
SS -> MS |
CALL PROCEEDING |
|
|
12 |
SS -> MS |
ALERTING |
|
|
13 |
MS |
An alerting indication as defined in an PICS/PIXIT statement is given by the MS |
|
|
14 |
SS -> MS |
ASSIGNMENT COMMAND |
|
|
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
16 |
SS -> MS |
CONNECT |
|
|
17 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
18 |
MS |
The TCH is through connected in both directions |
10.2.4 Specific message contents
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH/SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrary |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
CALL PROCEEDING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.3) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Repeat Indicator |
Omitted |
|
Bearer Capability 1 |
Omitted |
|
Bearer Capability 2 |
Omitted |
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
ALERTING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.1) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
User-user |
Omitted |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Channel Description |
|
|
Channel type |
Bm + ACCHs |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Channel mode |
Speech full rate |
CONNECT (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.5) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
Connected number |
Omitted |
|
Connected Subaddress |
Omitted |
|
User-user |
Omitted |
10.2a Generic call set-up procedure for mobile originating signalling only connection
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.2a.1 Initial conditions
See subclause 10.1.1
PIXIT Statements
– Description of the procedure how to initiate a mobile originated connection.
– Way in the MS to avoid the disconnect of the RR connection due to MM or higher layer timers.
10.2a.2 Definition of system information messages
See subclause 10.1.2
10.2a.3 Procedure
An RR connection on TCH in signalling only mode shall be established under ideal radio conditions with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
MS |
A connection is initiated according to the PIXIT statement |
||
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
|
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
Note: To allow testing on TCH (signalling only) during a long period the MS manufacturer has to provide a way to avoid the disconnect of the RR connection due to MM or higher layer timers. |
|||
10.2a.4 Specific message contents
PAGING REQUEST TYPE 1 (3GPP TS 44.018, subclause 9.1.22) to the MS
Same as section 10.1.4
IMMEDIATE ASSIGNMENT (3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
TCH/F + ACCHs (Note 1) |
|
Time slot number |
Default or as defined by the test case |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
Default or as defined by the test case |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
NOTE 1: Channel mode is ‘signalling only’ after Immediate Assignment.
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
Same as section 10.1.4
10.3 Generic call set-up procedure for mobile terminating data calls
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Terminating Data call set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.3.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1).
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.3.2 Definition of system information messages
See subclause 10.1.2.
10.3.3 Procedure
An MS terminating call on a TCH shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "answer to paging" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
9 |
SS |
SS starts ciphering |
|
|
10 |
SS -> MS |
SETUP |
A call is set up according to the required characteristics of the test procedure. Bearer Capability and Signal IEs included |
|
11 |
MS -> SS |
CALL CONFIRMED |
Bearer Capability shall or shall not be included according to the rules given in 3GPP TS 04.08 / 3GPP TS 24.008 and 3GPP TS 07.01 |
|
A12 |
MS -> SS |
CONNECT |
|
|
B12 |
MS -> SS |
ALERTING |
|
|
B13 |
MS |
An alerting indication as defined in a PICS/PIXIT statement given by the MS |
|
|
B14 |
MS |
The MS is made to accept the call in a way described in a PICS/PIXIT statement |
|
|
B15 |
MS -> SS |
CONNECT |
|
|
16 |
SS -> MS |
ASSIGNMENT COMMAND |
|
|
17 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
18 |
MS |
The TCH is through connected in both directions |
|
|
19 |
SS -> MS |
CONNECT ACKNOWLEDGE |
10.3.4 Specific message contents
PAGING REQUEST TYPE 1 (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.22) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal Paging |
|
Channel Needed |
spare, any channel |
|
Mobile Identity 1 |
|
|
Odd/even no of digits |
As applicable for TMSI |
|
Type of Identity |
TMSI |
|
Identity digits |
As applicable |
|
Mobile Identity 2 |
Omitted |
|
P1 rest octets |
Spare octets |
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH/SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrarily selected |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
SETUP (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.23) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
|
|
Bearer Capability |
|
|
Radio Channel Requirement |
|
|
Connection Element |
T or NT and declared as supported by the MS (Not "Both …") |
|
NIRR |
No meaning |
|
Other parameters |
Declared as supported by the MS |
|
Signal |
any non-reserved value |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Channel Description |
|
|
Channel type |
Bm + ACCHs |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Channel mode |
Proper data rate, according to BC-IE included in the Set-Up and to the following table |
Table 10-1: Correspondence between User rate (UR) and Channel Mode (CM)
for transparent (T) and non transparent (NT) connections
|
UR |
9,6kbit/s |
4,8kbit/s |
2,4kbit/s |
1,2kbit/s |
1,2/0,075kbit/s |
0,3kbit/s |
|
CM T FR |
12 FR |
6 FR |
3,6 FR |
3,6 FR |
3,6 FR |
3,6 FR |
|
CM T HR |
n.a |
6 HR |
3,6 HR |
3,6 HR |
3,6 HR |
3,6 HR |
|
CM NT FR |
12 FR |
12 FR |
12 FR |
12 FR |
12 FR |
12 FR |
|
CM NT HR |
n.a |
6 HR |
6 HR |
6 HR |
6 HR |
6 HR |
CONNECT ACKNOWLEDGE (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.6) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
10.4 Generic call set-up procedure for mobile originating data calls
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Originating Data call set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.4.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.4.2 Definition of system information messages
See subclause 10.1.2.
10.4.3 Procedure
An MS originating call on a TCH shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
"called number" entered |
|
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "originating call, NECI <> 1" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM |
|
5 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
6 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
7 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
8 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
9 |
SS |
SS starts ciphering |
|
|
10 |
MS -> SS |
SETUP |
|
|
11 |
SS -> MS |
CALL PROCEEDING |
|
|
12 |
SS -> MS |
ALERTING |
|
|
13 |
MS |
An alerting indication as defined in an PICS/PIXIT statement is given by the MS |
|
|
14 |
SS -> MS |
ASSIGNMENT COMMAND |
|
|
15 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
|
16 |
SS -> MS |
CONNECT |
|
|
17 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
18 |
MS |
The TCH is through connected in both directions |
10.4.4 Specific message contents
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH/SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrarily selected |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
CALL PROCEEDING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.3) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Repeat Indicator |
Present if and only if Bearer Capability 1 and Bearer Capability 2 are present in this message |
|
Bearer Capability 1 |
Present if negotiation of BC 1 or BC 2 necessary (e.g. reception of "Both" for CE parameter in SETUP), else omitted |
|
Radio Channel Requirement |
spare |
|
Connection element |
T (in case of "Both T (NT) preferred" received) |
|
NIRR |
No meaning |
|
Other parameters |
Same as sent by the MS in the SETUP, where applicable |
|
Bearer Capability 2 |
Present if dual BC-IE received and negotiation of either BC 1 or BC 2 necessary, else omitted |
|
Radio Channel Requirement |
spare |
|
Connection element |
T in case of "Both, T (NT) preferred" in the SETUP message else same as in the SETUP message |
|
NIRR |
No meaning |
|
Other parameters |
Same as sent by the MS in the SETUP, where applicable |
|
NOTE: If both BC 1 and BC 2 are present, then one and only one of them shall indicate speech. |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
ALERTING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.1) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
User-user |
Omitted |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Transaction Identifier |
Not used |
|
Message Type |
|
|
Channel Description |
|
|
Channel type |
Bm + ACCHs |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
FB no |
Band no 0 |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Channel mode |
If no negotiation took place: – Speech FR (resp. HR) if first BC IE in the SETUP indicated speech FR (resp. HR); – Set according to the table below if first BC – IE in the SETUP indicates data or fax If negotiation took place; – Speech FR (resp. HR) if first BC-IE in the CALL PROCEEDING indicated speech FR (resp. HR); – Set according to the table below if first BC – IE in the CALL PROCEEDING indicates data or fax |
Table 10-2: Correspondence between User rate (UR) and Channel Mode (CM)
for transparent (T) and non transparent (NT) connections
|
UR |
9,6kbit/s |
4,8kbit/s |
2,4kbit/s |
1,2kbit/s |
1,2/0,075kbit/s |
0,3kbit/s |
|
CM T FR |
12FR |
6 FR |
3,6 FR |
3,6 FR |
3,6 FR |
3,6 FR |
|
CM T HR |
n.a |
6 HR |
3,6 HR |
3,6 HR |
3,6 HR |
3,6 HR |
|
CM NT FR |
12 FR |
12 FR |
12 FR |
12 FR |
12 FR |
12 FR |
|
CM NT HR |
n.a |
6 HR |
6 HR |
6 HR |
6 HR |
6 HR |
CONNECT (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.5) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
Connected number |
Omitted |
|
Connected Subaddress |
Omitted |
|
User-user |
Omitted |
10.5 Generic call set-up procedure for mobile terminating multislot configuration, minimum number of timeslots allocated
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Terminating multislot connection set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.5.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.5.2 Definition of system information messages
See subclause 10.1.2.
10.5.3 Procedure
An MS terminating multislot connection shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
Sent on the correct paging subchannel |
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "answer to paging" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
PAGING RESPONSE |
Message is contained in SABM |
|
5 |
MS -> SS |
CLASSMARK CHANGE |
Multislot class |
|
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
10 |
SS |
SS starts ciphering |
|
|
11 |
SS -> MS |
SETUP |
A multislot connection is set up according to the required characteristics of the test procedure. Bearer Capability and Signal IEs included |
|
12 |
MS -> SS |
CALL CONFIRMED |
Bearer Capability shall or shall not be included according to the rules given in 3GPP TS 04.08 / 3GPP TS 24.008 and 3GPP TS 07.01 |
|
A12 |
MS -> SS |
CONNECT |
|
|
B13 |
MS -> SS |
ALERTING |
|
|
B14 |
MS |
An alerting indication as defined in a PICS/PIXIT statement given by the MS |
|
|
B15 |
MS |
The MS is made to accept the call in a way described in a PICS/PIXIT statement |
|
|
B16 |
MS -> SS |
CONNECT |
|
|
17 |
SS -> MS |
ASSIGNMENT COMMAND |
In multislot allocation only one timeslot is allocated. |
|
18 |
MS -> SS |
ASSIGNMENT COMPLETE |
Sent on the TCH/Sm channel |
|
19 |
MS |
The TCH(s) is through connected in both directions |
|
|
20 |
SS -> MS |
CONNECT ACKNOWLEDGE |
10.5.4 Specific message contents
PAGING REQUEST TYPE 1 (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.22) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal Paging |
|
Channel Needed |
spare, any channel |
|
Mobile Identity 1 |
|
|
Odd/even no of digits |
As applicable for TMSI |
|
Type of Identity |
TMSI |
|
Identity digits |
As applicable |
|
Mobile Identity 2 |
Omitted |
|
P1 rest octets |
Spare octets |
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH/SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrarily selected |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
SETUP (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.23) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
|
|
Bearer Capability |
|
|
Radio Channel Requirement |
|
|
Connection Element |
T or NT and declared as supported by the MS (Not "Both …") |
|
NIRR |
No meaning |
|
Other parameters |
Declared as supported by the MS |
|
Signal |
any non-reserved value |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Channel Description 2 |
|
|
Channel type |
TCH/F + FACCH/F and SACCH/M |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Multislot allocation |
|
|
– Downlink assignment |
Only one timeslot is assigned in downlink direction. |
|
– Uplink assignment |
Only one timeslot is assigned in uplink direction. |
CONNECT ACKNOWLEDGE (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.6) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
SS orig. |
|
Message Type |
10.6 Generic call set-up procedure for mobile originating multislot configuration, minimum number of timeslots allocated
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Originating multislot connection set-up procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.6.1 Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is "idle, updated", with a TMSI assigned and listening to the BCCH/CCCH of the active cell.
10.6.2 Definition of system information messages
See subclause 10.1.2.
10.6.3 Procedure
An MS originating multislot connection shall be established under ideal radio conditions and with Timing advance set to 0, as follows:
|
Step |
Direction |
Message |
Comments |
|
1 |
MS |
"called number" entered |
|
|
2 |
MS -> SS |
CHANNEL REQUEST |
Establishment cause indicates "originating call, NECI <> 1" |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
|
4 |
MS -> SS |
CM SERVICE REQUEST |
Message is contained in SABM |
|
5 |
MS -> SS |
CLASSMARK CHANGE |
Multislot class |
|
6 |
SS -> MS |
AUTHENTICATION REQUEST |
|
|
7 |
MS -> SS |
AUTHENTICATION RESPONSE |
SRES specifies correct value |
|
8 |
SS -> MS |
CIPHERING MODE COMMAND |
SS starts deciphering after sending the message |
|
9 |
MS -> SS |
CIPHERING MODE COMPLETE |
Shall be sent enciphered. All following messages shall be sent enciphered |
|
10 |
SS |
SS starts ciphering |
|
|
11 |
MS -> SS |
SETUP |
A multislot connection is set up according to the required characteristics of the test procedure. |
|
12 |
SS -> MS |
CALL PROCEEDING |
|
|
13 |
SS -> MS |
ALERTING |
|
|
14 |
MS |
An alerting indication as defined in an PICS/PIXIT statement is given by the MS |
|
|
15 |
SS -> MS |
ASSIGNMENT COMMAND |
In multislot allocation only one timeslot is allocated. |
|
16 |
MS -> SS |
ASSIGNMENT COMPLETE |
Sent on TCH/Sm channel. |
|
17 |
SS -> MS |
CONNECT |
|
|
18 |
MS -> SS |
CONNECT ACKNOWLEDGE |
|
|
19 |
MS |
The TCH(s) is through connected in both directions |
10.6.4 Specific message contents
IMMEDIATE ASSIGNMENT (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.18) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Page Mode |
Normal |
|
Channel Description |
|
|
Channel Type |
SDCCH / SACCH 1(4) |
|
Time slot number |
zero |
|
Training seq. code |
same as BCCH |
|
Hopping |
No |
|
ARFCN |
ARFCN of the BCCH |
|
Random Reference |
|
|
Random access info |
As in CHAN REQ |
|
N51, N32, N26 |
As applicable |
|
Timing Advance |
0 |
|
Mobile allocation |
length 0 due to hopping |
|
IA rest octets |
Spare octets |
AUTHENTICATION REQUEST (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.2.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
MM |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering key seq. number |
Arbitrary |
|
Authent. parameter RAND |
Arbitrarily selected |
CIPHERING MODE COMMAND (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.1.9) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Skip Indicator |
0000 |
|
Message Type |
|
|
Ciphering mode setting |
Start ciphering |
|
Algorithm Identifier |
Supported by the MS |
|
Cipher Response |
IMEISV shall not be included |
CALL PROCEEDING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.3) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Repeat Indicator |
Present if and only if Bearer Capability 1 and Bearer Capability 2 are present in this message |
|
Bearer Capability 1 |
Present if negotiation of BC 1 necessary (e.g. reception of "Both" for CE parameter in SETUP), else omitted |
|
Radio Channel Requirement |
spare |
|
Connection element |
T (in case of "Both T (NT) preferred" received) |
|
NIRR |
No meaning |
|
Other parameters |
Same as sent by the MS in the SETUP, where applicable |
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
ALERTING (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.1) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
User-user |
Omitted |
ASSIGNMENT COMMAND (3GPP TS 04.08 / 3GPP TS 44.018, subclause 9.1.2) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
RR |
|
Transaction Identifier |
Not used |
|
Message Type |
|
|
Channel Description 2 |
|
|
Channel type |
TCH/F + FACCH/F + SACCH/M |
|
Time slot number |
Arbitrary |
|
Training seq. code |
Default |
|
Hopping |
No |
|
FB no |
Band no 0 |
|
ARFCN |
Default |
|
Power level |
Power control level 7 |
|
Multislot allocation |
|
|
– Downlink assignment |
Only one timeslot is assigned in downlink direction. |
|
– Uplink assignment |
Only one timeslot is assigned in uplink direction. |
CONNECT (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.5) to the MS
|
Information Element |
Value/remark |
|
Protocol Discriminator |
CC |
|
Transaction Identifier |
As derived from SETUP |
|
Message Type |
|
|
Facility |
Omitted |
|
Progress Indicator |
Omitted |
|
Connected number |
Omitted |
|
Connected Subaddress |
Omitted |
|
User-user |
Omitted |
10.7 Generic procedure for GPRS downlink data transfer
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Terminating Data transfer procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.7.1 Initial conditions
System Simulator:
– 1 cell, default parameters as specified in clause 40;
– ideal radio conditions and Timing advance set to 0.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is GPRS attached with a P-TMSI allocated and the test PDP context2 activated.
10.7.2 Definition of system information messages
See clause 40.
10.7.3 Procedure
|
Step |
Direction |
Message |
Comments |
|
1 |
Start an application in the MS that continually reads all received data |
||
|
2 |
SS -> MS |
PAGING REQUEST |
Contains P-TMSI of the MS. Sent on PCH. |
|
3 |
MS -> SS |
CHANNEL REQUEST |
ACCESS TYPE = " Page Response ". Received on RACH. |
|
4 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
Random Reference = pertaining to the message received in step 3. Sent on AGCH. Single block assignment. |
|
5 |
MS -> SS |
UPLINK RLC DATA BLOCK |
LLC PDU implicitly indicating paging response, containing TLLI in the RLC/MAC header. . |
|
6 |
SS -> MS |
PACKET UPLINK ACK/NACK |
Acknowledge the received RLC data block. Sent on PACCH. Poll bit in the MAC header is set to indicate a valid RRBP. |
|
7 |
MS -> SS |
PACKET CONTROL ACKNOWLEDGEMENT |
As RLC/MAC control block. Received on PACCH. |
|
8 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
Poll bit in the MAC header is set to indicate a valid RRBP. Sent on PCH. |
|
9 |
MS -> SS |
PACKET CONTROL ACKNOWLEDGEMENT |
Received on PACCH. |
NOTE: The MS is always granted a USF whenever the MS is expected to send.
10.7.4 Specific message contents
See clause 40.
10.8 Generic procedure for GPRS uplink data transfer
In the test procedures described in the present document, unless otherwise stated in the test description, the Mobile Originated Data transfer procedure shall be as described in this subclause.
NOTE: In test cases where a fading profile is required, a different and appropriate ARFCN may be selected, for instance if the fading simulator bandwidth does not allow use of the default ARFCN.
10.8.1 Initial conditions
System Simulator:
– 1 cell, default parameters as specified in clause 40;
– ideal radio conditions and Timing advance set to 0.
Mobile Station:
– the MS shall be operated under normal test conditions (see annex 1 TC.2.1);
– the special Test-SIM (see annex 4) shall be inserted;
– the MS is GPRS attached with a P-TMSI allocated and the test PDP context3 activated.
10.8.2 Definition of system information messages
See clause 40.
10.8.3 Procedure
|
Step |
Direction |
Message |
Comments |
|
1 |
Start an application in the MS that continually sends data |
||
|
2 |
MS -> SS |
CHANNEL REQUEST |
Received on RACH. |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
Single block assignment, to order the MS to follow the two phase access procedure. Sent on AGCH. |
|
4 |
MS -> SS |
PACKET RESOURCE REQUEST |
Two phase access procedure. Received on the single block assigned in step 3. |
|
5 |
SS -> MS |
PACKET UPLINK ASSIGNMENT |
Sent on PACCH of the same PDCH assigned in step 2. TIMESLOT_ALLOCATION arbitrarily chosen but shall not exceed the multislot capabilities of the MS. Open ended assignment. |
|
6 |
SS -> MS |
PACKET DOWNLINK DUMMY CONTROL BLOCK |
Sent on PACCH containing USF assigned to the MS. |
NOTE: The MS is always granted a USF whenever the MS is expected to send.
10.8.4 Specific message contents
PACKET UPLINK ACK/NACK message:
|
MESSAGE_TYPE |
001001 |
|
PAGE_MODE |
Normal Paging |
|
UPLINK_TFI |
00, same as the TFI value of the TBF which the message applies |
|
0, message escape |
|
|
CHANNEL_CODING_COMMAND |
Same coding scheme as in the assigned TBF which the message applies to |
|
Ack/Nack Description |
|
|
– FINAL_ACK_INDICATION |
0 (not a final ACK) |
|
– STARTING_SEQUENCE_NUMBER |
V( R ) |
|
– RECEIVED_BLOCK_BITMAP |
Acknowledge the all data blocks transmitted by the MS |
|
{0|1<CONTENTION_RESOLUTION_TLLI>} |
0 (no contention resolution TLLI) |
|
{0|1<Packet Timing Advance>} |
0 (no packet timing advance) |
|
{0|1<Power Control Parameters>} |
0 (no power control parameters) |
|
{0|1<Extension bits>} |
0 (no extension bits present) |
|
{0|1<Fixed Allocation parameters>} |
0 (no fixed allocation parameters present) |
|
spare padding |
Spare Padding |
PACKET UPLINK ASSIGNMENT message (two-phase dynamic allocation assigning a TBF):
|
MESSAGE_TYPE |
001010 |
|
PAGE_MODE |
Normal Paging |
|
{0|1<PERSISTENCE_LEVEL>} |
0 (no persistence level present) |
|
– Address information |
10 (TLLI) |
|
– TLLI |
The value received from the MS |
|
0, message escape |
|
|
CHANNEL_CODING_COMMAND |
Arbitrarily chosen from the valid values (default CS-1) |
|
TLLI_BLOCK_CHANNEL_CODING |
‘0’B, cs-1 |
|
Packet Timing Advance |
|
|
– {0|1<TIMING_ADVANCE_VALUE>} |
1 (timing advance value) |
|
– TIMING_ADVANCE_VALUE |
0 bit periods |
|
– {0|1<TIMING_ADVANCE_INDEX> <TIMING_ADVANCE_TIMESLOT_NUMBER >} |
0 (no timing advance index) |
|
{0|1<Frequency Parameters>} |
1 (Frequency Parameters present) |
|
– Frequency Parameters |
|
|
< TSC > |
Arbitrarily chosen |
|
{ 00< ARFCN >} |
00 (ARFCN no hopping) |
|
– ARFCN } |
As for “Serving cell, PDTCH, SDCCH ” in section 40.1.1 for the current cell |
|
Dynamic allocation |
01 |
|
– Extended Dynamic Allocation |
0 ( Dynamic allocation) |
|
– {0|1<P0><PR_MODE>} |
0 |
|
– USF_GRANULARITY |
0, one block |
|
– {0|1<UPLINK_TFI_ASSIGNMENT>} |
1 ( uplink TFI assignment) |
|
– UPLINK_TFI_ASSIGNMENT |
Arbitrarily chosen (default 00101) |
|
– {0|1<RLC_DATA_BLOCKS_GRANTED>} |
0 (no RLC_DATA_BLOCKS_GRANTED, open-ended TBF) |
|
– {0|1<TBF_STARTING_TIME>} |
0 (no starting time) |
|
– |
1 (Timeslot Allocation with Power Control Parameters) one slot arbitrarily chosen and the following USF_TNx and GAMMA_TNx shall be corresponding to the chosen value, default timeslot 2 assigned) |
|
– ALPHA |
0.5 |
|
– {0|1<USF_TN0><GAMMA_TN0>} |
0 (timeslot 0 not assigned) |
|
– {0|1<USF_TN1><GAMMA_TN1>} |
0 (timeslot 1 not assigned) |
|
– {0|1<USF_TN2><GAMMA_TN2>} |
1 (timeslot 2 assigned) |
|
– USF_TN2 |
Arbitrarily chosen (default 101) |
|
– GAMMA_TN2 |
For DCS 1800, +6 dBmPCS 1 900, +6 dBm For other bands +9 dBm |
|
– {0|1<USF_TN3><GAMMA_TN3>} |
0 (timeslot 3 not assigned) |
|
– {0|1<USF_TN4><GAMMA_TN4>} |
0 (timeslot 4 not assigned) |
|
– {0|1<USF_TN5><GAMMA_TN5>} |
0 (timeslot 5 not assigned) |
|
– {0|1<USF_TN6><GAMMA_TN6>} |
0 (timeslot 6 not assigned) |
|
– {0|1<USF_TN7><GAMMA_TN7>} |
0 (timeslot 7 not assigned) |
|
spare padding |
Spare Padding |
See also clause 40.