58b.1 Downlink Dual Carrier Reconfiguration

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

58b.1.1 Single Carrier Uplink TBF with no Downlink TBF/ DLDC TBF established / No change in Uplink TBF

58b.1.1.1 Conformance requirement

If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If this message is sent to a mobile station in packet idle mode, the assignment message shall include frequency parameters for both carriers.

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent assignment messages, that carrier shall be considered carrier 1. A subsequent assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration.

In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. A mobile station with a Downlink Dual Carrier configuration shall not be allocated radio blocks on both radio frequency channels during any given radio block period.

3GPP TS 44.060; subclause 5.5.1.7, 8.1.1.1

58b.1.1.2 Test purpose

To verify that the MS:

– decodes correctly the Packet downlink Assignment that assigns dual downlink carrier

– is able to correctly receive data simultaneously on both the carriers assigned

58b.1.1.3 Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Dual Carrier supported.

Mobile Station:

Support for Downlink Dual Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.

Specific PICS Statements

The GPRS multislot class supported (TSPC_Type_GPRS_Multislot_ClassX, where X = 1..45)

Multislot Capability Reduction for Downlink Dual Carrier of 0 or 1 Timeslots (TSPC_Type_Multislot_Capability_Reduction_for_Downlink_Dual_Carrier_of_0_or_1_Timeslots)

Multislot Capability Reduction for Downlink Dual Carrier of 2 or more Timeslots (TSPC_Type_Multislot_Capability_Reduction_for_Downlink_Dual_Carrier_of_2_or_more_Timeslots)

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. Then MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH, instructing a Dual Carrier Downlink configuration. The SS sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by SS.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 1000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

5

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 1.

Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned. See specific message contents

6

SS

Wait for at least 3 block periods

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (Start with BSN 0). USF Assigned. MCS-1

8

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1. MCS-1

9

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

10

Repeat Steps 7 to 9 10 Times

11

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

With next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field, sent on Carrier 1. MCS-1

12

MS -> SS

EGPRS DOWNLINK PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

13

{Completion of uplink RLC data block transfer}

Specific Message Contents

PACKET DOWNLINK ASSIGNMENT message in step 5:

Information Element

value/ remark

MESSAGE_TYPE

000010

PAGE_MODE

00 Normal Paging

Persistence Level

0 (no Persistence Level Present)

Referenced Address

Referenced by UL TFI

1

Message Escape Sequence for dual carrier…

00

RLC_MODE

0 Acknowledged mode

CONTROL_ACK

0

<Assignment Info>

Assignment Info Struct

0

BTTI Mode

TIMESLOT_ALLOCATION_C1

arbitrarily chosen (default timeslot 4)

1

Carrier 2 explicitly assigned

TIMESLOT_ALLOCATION_C2

arbitrarily chosen (default timeslot 4)

Packet Timing Advance

{ 0|1< TIMING_ADVANCE_VALUE >

1 (timing advance value)

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

0 (no timing advance index)

01

Legacy IEs Used

1< Frequency Parameters_C1>

Frequency Parameters_C1 Present

1< Frequency Parameters_C2>

Frequency Parameters_C2 Present

0

P0_C1 not present

{0|1<DOWNLINK_TFI_ASSIGNMENT>}

1 (assign downlink TFI)

– DOWNLINK_TFI_ASSIGNMENT

00001

{0|1<Power Control Parameters_C1>}

1 (Power Control Parameters present for Carrier1)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

(default timeslot 4)

{0|1<Power Control Parameters_C2>}

1 (Power Control Parameters present for Carrier2)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

(default timeslot 4)

0

EGPRS Window IE not present

0

Packet Extended Timing Advance not present

0

No PFI

0

No NPM transfer Time

0

Fast Ack/Nack Reporting not activated

Spare padding

Spare Padding

58b.1.1a Single Carrier Uplink TBF with no Downlink TBF/ DLMC TBF established / No change in Uplink TBF

58b.1.1a.1 Conformance requirement

If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration..

In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration or a DLMC configuration shall not be allocated radio blocks on more than one radio frequency channel during any given radio block period..

3GPP TS 44.060; subclause 5.5.1.7, 8.1.1.1

58b.1.1a.2 Test purpose

To verify that the MS:

– decodes correctly the Packet downlink Assignment that assigns downlink multi carrier

– is able to correctly receive data simultaneously on both the carriers assigned

58b.1.1a.3 Method of test

Initial Conditions

System Simulator (SS):

1 cell, EGPRS supported, DownlinkMulti Carrier supported.

Mobile Station:

Support for Downlink Multi Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated,, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. Then MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH, instructing it to enter a Downlink Multi Carrier configuration. The SS sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks sent by SS.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 1000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

3

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

4

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 1.

Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned. See specific message contents

5

SS

Wait for at least 3 block periods

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (Start with BSN 0). USF Assigned. MCS-1

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1. MCS-1

8

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

9

Repeat Steps 6 to 8 10 Times

10

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

With next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field, sent on Carrier 1. MCS-1

11

MS -> SS

EGPRS DOWNLINK PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

12

{Completion of uplink RLC data block transfer}

Specific Message Contents

PACKET DOWNLINK ASSIGNMENT message in step 4:

Information Element

value/ remark

MESSAGE_TYPE

000010

PAGE_MODE

00 Normal Paging

Persistence Level

0 (no Persistence Level Present)

Referenced Address

Referenced by UL TFI

1

Message Escape Sequence for DLMC…

01

RLC_MODE

0 Acknowledged mode

CONTROL_ACK

0

1 < UFPS : < UFPS struct >

1st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 1st DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 1st Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

1 TIMESLOT_ALLOCATION

arbitrarily chosen (default timeslot 4)

0

MAIO

1 < P0

0000 0dB

1 PR_MODE

0 PR mode A

1

DOWNLINK_TFI_ASSIGNMENT assign

00001

downlink tfi assigned value

1

<Power Control Parameters>}

1 (Power Control Parameters present for Carrier1)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

(default timeslot 4)

0

EMST is not used on this carrier

0

EMSR is not used on this carrier

1 < UFPS : < UFPS struct >

2nd UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 2nd DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 2nd Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

0

same timeslots as the lowest numbered carrier

0

MAIO

0

same P0 and PR_MODE as the lowest numbered carrier

0

same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier

0

same Power Control Parameters as the lowest numbered carrier

0

EMST is not used on this carrier

0

EMSR is not used on this carrier

0

End of CARRIER_SPECIFIC_INFO

0

End of UFPS struct

DLMC Measurement Type

0

< LINK_QUALITY_MEASUREMENT_MODE

00

0

Carrier for Interference Measurements

Packet Timing Advance

1

1 (timing advance value)

100000}

32 bit periods indicated

0

0 (no timing advance index or timing advance timeslot number)

0

< Packet Extended Timing Advance

0

< PTCCH_CARRIER

0

< PDAN Coding >

0

< Extended SNS >

0

< BEP_PERIOD2

0

< PFI

0

< NPM Transfer Time

0

Fast Ack/Nack Reporting

00

< Downlink EGPRS Level

0

< Indication of Upper Layer PDU Start for RLC UM

0

< EGPRS Packet Downlink Ack/Nack Type 3 Support

Spare padding

Spare Padding

58b.1.2 Single Carrier concurrent TBF to DLDC TBF/ Uplink DLDC TBF (on both carrier 1 and carrier 2)/ Reconfigured back to single Carrier Concurrent TBF

58b.1.2.1 Conformance requirement

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent assignment messages, that carrier shall be considered carrier 1. A subsequent assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration.

Downlink Dual Carrier enables downlink TBFs and uplink TBFs to use allocated resources on one or more assigned PDCHs on two different radio frequency channels. Uplink RLC/MAC blocks shall not be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period. Downlink RLC/MAC blocks may be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period.

If the network initially assigns a mobile station radio resources on only one carrier, it can extend this assignment to a downlink dual carrier configuration by sending a new single carrier assignment to the mobile station including assigned radio resources for the second carrier, without changing the resources already assigned for the initial carrier. Alternatively the network can include radio resources for two carriers in an initial or subsequent assignment message.

If the network and mobile station both support Downlink Dual Carrier, the network may send a downlink assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION) to a mobile station assigning one or more TBFs with packet resources on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration.

If the assignment message contains the Assignment Info IE indicating an assignment type other than ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs on the carrier identified by the Carrier ID field. In this case, if the assignment message addresses TBFs that currently have packet resources assigned on the other carrier (i.e. the carrier not identified by the Carrier ID field) then these packet resources shall be treated as follows:

– these resources are implicitly released, if the ASSIGNMENT TYPE field (carried in the Assignment Info IE) indicates that the assignment is an ‘Assignment on single carrier only’;

– these resources are unchanged, if the ASSIGNMENT TYPE field indicates that the assignment is a ‘Modification of existing assignment’.

If the assignment message contains the Assignment Info IE indicating an assignment type of ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs.

In the case of a mobile station with a Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Downlink Dual Carrier configuration receives an assignment message which results in the mobile station no longer being in a

Downlink Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned

When the MS receives the updated value of TA from the BTS on the downlink PTCCH, it shall always use

the last received TA value for the uplink transmission.

Within the packet resource assignments (see 3GPP TS 04.08 / 3GPP TS 24.008 and 3GPP TS 04.60) for

uplink or downlink messages the MS gets the Timing Advance Index (TAI). The MS shall send access bursts

on the subchannel defined by the TAI on the PTCCH using TA=0.

References

3GPP TS 44.060; subclause 5.5.1.7, 7.1.2.5, 5.9 and 8.1.1.1.3

3GPP TS 45.10, subclause 6.5.2.

58b.1.2.2 Test purpose

To verify that:

– the MS is able to change from single carrier concurrent TBF to dual carrier configuration and operate downlink dual carrier downlink and uplink TBF.

– the MS is able to change from single carrier concurrent TBF to dual carrier configuration and operate downlink dual carrier downlink and uplink TBF.

– in Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1. To verify that the mobile station uses the continuous update timing advance mechanism and sends access bursts on the PTCCH slots as determined by the Timing Advance Index sent in the PACKET UPLINK ASSIGNMENT message.

– the MS is able to change from dual carrier to a single carrier assignment and continue to use the same Timing advance parameters if the values are not changed.

58b.1.2.3 Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Dual Carrier supported.

Mobile Station:

Support for Downlink Dual Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.

Specific PICS Statements

The GPRS multislot class supported (TSPC_Type_GPRS_Multislot_ClassX, where X = 1..45)

Multislot Capability Reduction for Downlink Dual Carrier of 0 or 1 Timeslots (TSPC_Type_Multislot_Capability_Reduction_for_Downlink_Dual_Carrier_of_0_or_1_Timeslots)

Multislot Capability Reduction for Downlink Dual Carrier of 2 or more Timeslots (TSPC_Type_Multislot_Capability_Reduction_for_Downlink_Dual_Carrier_of_2_or_more_Timeslots)

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The timing advance value is included in the PACKET UPLINK ASSIGNMENT. The MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH with assignment type set to dual carrier assignment. This configures the MS in Dual Carrier Downlink configuration. The SS sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. The MS receives a PACKET UPLINK ASSIGNMENT with assignment type set to dual carrier assignment. The timing advance parameter values are assigned. Timing advanced Index is set to 2. Frequency parameters are specified separately. The SS sends PACKET UPLINK ACK/NACK on both carriers assigning USF. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 1 such that (FN mod

(8*52)) = 64 (TAI =2).

The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C1. The timing advance parameters are unchanged. The MS is polled to see if MS responds on C2. The uplink and downlink data transfer is initiated on both directions simultaneously. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 1 such that (FN mod (8*52)) = 64 (TAI =2) same as before.

The SS sends a PACKET DOWNLINK ASSIGNMENT and a PACKET UPLINK ASSIGNMENT to re establish the concurrent dual carrier TBF. The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C2. The timing advance parameters are unchanged. The MS is polled to see if MS responds on C1. The uplink and downlink data transfer is initiated on both directions simultaneously. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 2 such that (FN mod (8*52)) = 64 (TAI =2) same as before as the timing advance parameter is unchanged.

The MS is configured back to dual carrier configuration mode as it has been done previously.(PACKET UPLINK and DONWLINK ASSIGNMENT). The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C1. The timing advance parameters are changed to an arbitrarily chosen value. The MS is polled to see if MS responds on C2. The uplink and downlink data transfer is initiated on both directions simultaneously. The SS monitors the access burst on PTCCH on carrier 1SS shall verify that the access burst are sent in the correct idle slots as specified in 3GPP TS 05.02 table 6.

MS is reconfigured in dual carrier configuration mode. The SS sends PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C1. New frequency and timeslot values are assigned and new timeslot allocations are assigned. The timing advance index is set to 0. The MS completes the uplink and downlink data transfer. During the uplink data transfer the SS monitors the access burst on PTCCH which are located on slots with numbers FN, such that (FN mod (8*52)) = 12 for Timing Advance Index = 0 (3GPP TS 03.64 subclause 6.5.7.2 and 3GPP TS 05.02 table 6). The access burst contents shall be MESSAGE_TYPE = 011111 and CTRL_ACK = 11.

Maximum Duration of Test

10 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 10000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

Timing advance values included.

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

5

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 1. Addressing the MS using the UL TFI assigned in Step 1. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included. Including Timing Advance Index = 2 Assignment Type = Dual carrier Assignment

6

SS

Wait for at least 3 block periods

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (Start with BSN 0). USF not Assigned to MS.

8

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field. USF not Assigned to MS.

9

MS -> SS

PACKET DOWNLINK ACK/NACK

Sent on PACCH of the PDTCH assigned in Step 5. Addressing the MS using the UL TFI assigned in Step 1MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 10.

12

SS -> MS

PACKET UPLINK ASSIGNMENT

Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step1. See specific message contents 58b.1.2. Timing advance values included. Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

11

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

12

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

13

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN and MCS-1. USF assigned to the MS.

14

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

15

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

SS acknowledges all received RLC data Block

16

Repeat steps 11-15 10 times. During uplink transfer in the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks that timing advance from PTCCH allocation on carrier1 used for both carriers.

17

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 10 .Addressing the MS using the UL TFI assigned in Step 1.: Assignment type = Single Carrier (C1) Assigned. See specific message contents section of this test case

18

SS

Wait for at least 3 block periods

19

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence. USF not Assigned to MS

20

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to MS

21

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 20

22

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, USF not assigned to the MS and with a valid RRBP field

23

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

24

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

25

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

26

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

27

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

28

SS

Repeat steps 19 – 27 10 times. During uplink transfer in steps the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks the timing advance from PTCCH allocation is on carrier1.

29

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 17. Addressing the MS using the UL TFI assigned in Step 1 .Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included. Including Timing Advance Index = 2: Assignment Type = Dual carrier Assignment

30

SS

Wait for at least 3 block periods

31

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned to MS.

32

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field. USF not Assigned to MS.

33

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 32.

34

SS -> MS

PACKET UPLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 29. Addressing the MS using the UL TFI assigned in Step 1

Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step29

See specific message contents 58b.1.2

Timing advance values included. Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

35

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, USF assigned to the MS.

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

37

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

38

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

39

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH

40

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 34. Addressing the MS using the UL TFI assigned. Assignment type = Single Carrier (C2) Assigned. See specific message contents section of this test

41

SS

Wait for at least 3 block periods

42

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN. USF not Assigned with MCS-1

43

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to the MS.

44

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 43.

45

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF not assigned to the MS with a valid RRBP field

46

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C1 from MS

47

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

48

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

49

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

50

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

51

SS

Repeat steps 42 – 50 10 times. During uplink transfer the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks the timing advance from PTCCH allocation is on carrier2. The SS makes sure that PTCCH slot and TA values from Carrier1 are still applied on Carrier2.

52

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 40 .Addressing the MS using the UL TFI assigned. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included.

Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

53

SS

Wait for at least 3 block periods

54

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned to the MS.

55

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field USF not assigned to the MS.

56

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data

Blocks. Sent on PACCH on the valid RRBP specified in step 57.

57

SS -> MS

PACKET UPLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 52. Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step 52

See specific message contents 58b.1.2

Timing advance values included. Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

58

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

59

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

60

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

61

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

62

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

63

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 57. Addressing the MS using the UL TFI assigned in step 1. Assignment type = Single Carrier (C1) Assigned. See specific message contents section of this test

64

SS

Wait for at least 3 block periods

65

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN with MCS-1 with valid RRBP field. USF not Assigned to the MS.

66

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to the MS.

67

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data. Blocks. Sent on PACCH on the valid RRBP specified in step 66.

68

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF not assigned to the MS with a valid RRBP field

69

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

70

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

71

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

72

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

73

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

74

SS

Repeat steps 66 – 73 10 times. During uplink transfer the SS continues monitoring the access burst on PTCCH and SS shall verify that the access burst are sent in the correct idle slots as specified in 3GPP TS 05.02 table 6.SS checks the timing advance from PTCCH allocation is on carrier1.

75

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 64 .Addressing the MS using the UL TFI. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included.

Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

76

SS

Wait for at least 3 block periods

77

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not assigned to the MS.

78

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field

79

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 78.

80

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS. Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step 1. See specific message contents 58b.1.2. Timing advance values included. Including Timing Advance Index = 2. Assignment Type = Dual carrier Assignment

81

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

82

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

83

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

84

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

85

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

86

SS -> MS

PACKET TIMESLOT RECONFIGURE

Legacy Rel-6 PDU. Sent on PACCH of the PDTCH assigned in Step 80. Addressing the MS using the UL TFI

Timing Advance Index = 0.

Assignment type = Single Carrier (C1) Assigned.

New frequency parameters, New timeslots and new USF parameters specified. See specific message contents section of this test

87

SS

Wait for at least 3 block periods

88

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned.

89

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field

90

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data. Blocks. Sent on PACCH on the valid RRBP specified in step 89.

91

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF not assigned to the MS with a valid RRBP field.

92

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

93

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

94

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

95

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

96

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

97

{Completion of Uplink and downlink data transfer}{ C98

completion of downlink and downlink data transfer }

SS

During the uplink data transfer (steps 96 to 99) the SS monitors the access burst on PTCCH which are located on slots with numbers FN, such that (FN mod (8*52)) = 12 for Timing Advance Index = 0 (3GPP TS 03.64 subclause 6.5.7.2 and 3GPP TS 05.02 table 6). The access burst contents shall be MESSAGE_TYPE = 011111 and CTRL_ACK = 11.

Specific Message Contents

PACKET DOWNLINK ASSIGNMENT message in step 5, 29, 52, 75:

Information Element

value/ remark

MESSAGE_TYPE

000010

PAGE_MODE

00 Normal Paging

Persistence Level

0 (no Persistence Level Present)

Referenced Address

Referenced by UL TFI

1

Message Escape Sequence for dual carrier…

00

RLC_MODE

0 Acknowledged mode

CONTROL_ACK

0

<Assignment Info>

Assignment Info Struct

0

BTTI Mode

TIMESLOT_ALLOCATION_C1

arbitrarily chosen (default timeslot 4)

1

Carrier 2 explicitly assigned

TIMESLOT_ALLOCATION_C2

arbitrarily chosen (default timeslot 4)

Packet Timing Advance

{ 0|1< TIMING_ADVANCE_VALUE >

1 (timing advance value)

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

2 (timing advance index)

01

Legacy IEs Used

1< Frequency Parameters_C1>

Frequency Parameters_C1 Present

1< Frequency Parameters_C2>

Frequency Parameters_C2 Present

0

P0_C1 not present

{0|1<DOWNLINK_TFI_ASSIGNMENT>}

1 (assign downlink TFI)

– DOWNLINK_TFI_ASSIGNMENT

00001

{0|1<Power Control Parameters_C1>}

1 (Power Control Parameters present for Carrier1)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

(default timeslot 4)

{0|1<Power Control Parameters_C2>}

1 (Power Control Parameters present for Carrier2)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBmFor all other bands: +8 dBm

(default timeslot 4)

0

EGPRS Window IE not present

0

Packet Extended Timing Advance not present

0

No PFI

0

No NPM transfer Time

0

Fast Ack/Nack Reporting not activated

Spare padding

Spare Padding

PACKET UPINK ASSIGNMENT message in step 10:

Information Element

value/ remark

MESSAGE_TYPE

001010

PAGE_MODE

00 Normal Paging

Persistence Level

0 No Persistence Level Present

GLOBAL_TFI

UL_TFI assigned in Step 1

– Resegment

0 Retransmitted RLC data blocks shall not be re-segmented

<Assignment Info>

Assignment Info struct

Assignment Type

10 (Dual carrier assignment )

Carrier ID

1 (carrier 2)

– EGPRS Window Size

Dependent upon test case (Default 64)

– {0|1 Access Technologies Request}

0 Access technology Request Info not present

– ARAC RETRANSMISSION REQUEST

0 retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested

TLLI_BLOCK_CHANNEL_CODING

1

{0|1 BEP_PERIOD2}

0 BEP_PERIOD2 not present

Packet Timing Advance

{ 0|1 < TIMING_ADVANCE_VALUE >

1 Timing Advance Value present

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

0 (no timing advance index)

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

0

{0 | 1 … }

0 (BTTI)

< Dynamic Allocation 2 struct > :

See below

EGPRS Modulation and Coding Scheme

Dependant upon test case (Default MCS_1)

{00 | 01…

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

1 Frequency Parameters_C2 Present

}

P0_C1 not present

{ 0 | 1 < PFI : bit (7) > }

0 not present

{ 0 | 1 < RLC_MODE : bit (1) > }

0 not present

{ 0 | 1 < NPM Transfer Time : bit (5) > }

0 not present

{ 0 | 1 — 1 indicates FANR is activated

0 FANR not activated

}

< Uplink EGPRS Level: < EGPRS Level IE > >

00 (EGPRS)

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

0 not present

Dynamic Allocation 2 struct:

EXTENDED_DYNAMIC_ALLOCATION

0 dynamic allocation only

{ 0 | 1 < P0 > …}

0 downlink power control is not used

USF_GRANULARITY

0 MS shall transmit only one RLC/MAC block

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT >}

1 assign uplink TFI

– UPLINK_TFI_ASSIGNMENT

00000

{0 | 1 (with/without power control parameters)

0 allocation without power control parameters

N_USF

1100 (13 USFs signalled)

{ 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1)

0 USF not assigned on C1 / TN0

0 USF not assigned on C1 / TN1

0 USF not assigned on C1 / TN2

0 USF not assigned on C1 / TN3

1 USF assigned on C1 / TN4

– USF

Arbitrarily chosen (default 000)

0 USF not assigned on C1 / TN5

0 USF not assigned on C1 / TN6

0 USF not assigned on C1 / TN7

0 USF not assigned on C2 / TN0

0 USF not assigned on C2 / TN1

0 USF not assigned on C2 / TN2

0 USF not assigned on C2 / TN3

1 USF assigned on C2 / TN4

– USF

Arbitrarily chosen (default 000)

(note: it is allowed to truncate the list; no USFs assigned on remaining timeslots)

PACKET TIMESLOT RECONFIGURE message in step 17, 64

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Assignment of Single carrier only)

Carrier ID

0 (carrier 1)

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

1

0 | 1 <TIMESLOT ALLOCATION_C2>

0

01

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

0 Frequency Parameters_C2 Absent

TSC

arbitrarily chosen

0 | 1 < Uplink Control Timeslot C1>

0 (Not present)

0 | 1 < Uplink Control Timeslot C2>

0 (Not present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

PACKET UPINK ASSIGNMENT message in step 34:

Information Element

value/ remark

MESSAGE_TYPE

001010

PAGE_MODE

00 Normal Paging

Persistence Level

0 No Persistence Level Present

GLOBAL_TFI

UL_TFI assigned in Step 1

– Resegment

0 Retransmitted RLC data blocks shall not be re-segmented

<Assignment Info>

Assignment Info struct

Assignment Type

10 (Dual carrier assignment )

Carrier ID

1 (carrier 2)

– EGPRS Window Size

Dependent upon test case (Default 64)

– {0|1 Access Technologies Request}

0 Access technology Request Info not present

– ARAC RETRANSMISSION REQUEST

0 retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested

TLLI_BLOCK_CHANNEL_CODING

1

{0|1 BEP_PERIOD2}

0 BEP_PERIOD2 not present

Packet Timing Advance

{ 0|1 < TIMING_ADVANCE_VALUE >

1 Timing Advance Value present

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

0 (no timing advance index)

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

0

{0 | 1 … }

0 (BTTI)

< Dynamic Allocation 2 struct > :

See below

EGPRS Modulation and Coding Scheme

Dependant upon test case (Default MCS_1)

{00 | 01…

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

1 Frequency Parameters_C2 Present

}

P0_C1 not present

{ 0 | 1 < PFI : bit (7) > }

0 not present

{ 0 | 1 < RLC_MODE : bit (1) > }

0 not present

{ 0 | 1 < NPM Transfer Time : bit (5) > }

0 not present

{ 0 | 1 — 1 indicates FANR is activated

0 FANR not activated

}

< Uplink EGPRS Level: < EGPRS Level IE > >

00 (EGPRS)

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

0 not present

Dynamic Allocation 2 struct:

EXTENDED_DYNAMIC_ALLOCATION

0 dynamic allocation only

{ 0 | 1 < P0 > …}

0 downlink power control is not used

USF_GRANULARITY

0 MS shall transmit only one RLC/MAC block

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT >}

1 assign uplink TFI

– UPLINK_TFI_ASSIGNMENT

00000

{0 | 1 (with/without power control parameters)

0 allocation without power control parameters

N_USF

1011 (11 USFs signalled)

{ 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1)

0 USF not assigned on C1 / TN0

0 USF not assigned on C1 / TN1

0 USF not assigned on C1 / TN2

1 USF assigned on C1 / TN3

0 USF not assigned on C1 / TN4

– USF

Arbitrarily chosen (default 000)

0 USF not assigned on C1 / TN5

0 USF not assigned on C1 / TN6

0 USF not assigned on C1 / TN7

0 USF not assigned on C2 / TN0

0 USF not assigned on C2 / TN1

0 USF not assigned on C2 / TN2

1 USF assigned on C2 / TN3

– USF

Arbitrarily chosen (default 000)

(note: it is allowed to truncate the list; no USFs assigned on remaining timeslots)

PACKET TIMESLOT RECONFIGURE message in step 40:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Assignment of Single carrier only)

Carrier ID

1 (carrier 2)

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

1

0 | 1 <TIMESLOT ALLOCATION_C2>

0

01

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

0 Frequency Parameters_C2 Absent

TSC

arbitrarily chosen

0 | 1 < Uplink Control Timeslot C1>

0 (Not present)

0 | 1 < Uplink Control Timeslot C2>

0 (Not present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

PACKET UPINK ASSIGNMENT message in step 57:

Information Element

value/ remark

MESSAGE_TYPE

001010

PAGE_MODE

00 Normal Paging

Persistence Level

0 No Persistence Level Present

GLOBAL_TFI

UL_TFI assigned in Step 1

– {0|1 CONTENTION_RESOLUTION_TLLI}

0 not present

– Resegment

0 Retransmitted RLC data blocks shall not be re-segmented

<Assignment Info>

Assignment Info struct

Assignment Type

10 (Dual carrier assignment )

Carrier ID

1 (carrier 2)

– EGPRS Window Size

Dependent upon test case (Default 64)

– {0|1 Access Technologies Request}

0 Access technology Request Info not present

– ARAC RETRANSMISSION REQUEST

0 retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested

TLLI_BLOCK_CHANNEL_CODING

1

{0|1 BEP_PERIOD2}

0 BEP_PERIOD2 not present

Packet Timing Advance

{ 0|1 < TIMING_ADVANCE_VALUE >

1 Timing Advance Value present

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

0 (no timing advance index)

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

0

{0 | 1 … }

0 (BTTI)

< Dynamic Allocation 2 struct > :

See below

EGPRS Modulation and Coding Scheme

Dependant upon test case (Default MCS_1)

{00 | 01…

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

1 Frequency Parameters_C2 Present

}

P0_C1 not present

{ 0 | 1 < PFI : bit (7) > }

0 not present

{ 0 | 1 < RLC_MODE : bit (1) > }

0 not present

{ 0 | 1 < NPM Transfer Time : bit (5) > }

0 not present

{ 0 | 1 — 1 indicates FANR is activated

0 FANR not activated

}

< Uplink EGPRS Level: < EGPRS Level IE > >

00 (EGPRS)

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

0 not present

Dynamic Allocation 2 struct:

EXTENDED_DYNAMIC_ALLOCATION

0 dynamic allocation only

{ 0 | 1 < P0 > …}

0 downlink power control is not used

USF_GRANULARITY

0 MS shall transmit only one RLC/MAC block

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT >}

1 assign uplink TFI

– UPLINK_TFI_ASSIGNMENT

00000

{0 | 1 (with/without power control parameters)

0 allocation without power control parameters

N_USF

1110 (14 USFs signalled)

{ 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1)

0 USF not assigned on C1 / TN0

0 USF not assigned on C1 / TN1

0 USF not assigned on C1 / TN2

0 USF not assigned on C1 / TN3

0 USF not assigned on C1 / TN4

– USF

Arbitrarily chosen (default 000)

1 USF assigned on C1 / TN5

0 USF not assigned on C1 / TN6

0 USF not assigned on C1 / TN7

0 USF not assigned on C2 / TN0

0 USF not assigned on C2 / TN1

0 USF not assigned on C2 / TN2

0 USF not assigned on C2 / TN3

0 USF not assigned on C2 / TN4

1 USF assigned on C2 / TN5

– USF

Arbitrarily chosen (default 000)

(note: it is allowed to truncate the list; no USFs assigned on remaining timeslots)

PACKET UPINK ASSIGNMENT message in step 81:

Information Element

value/ remark

MESSAGE_TYPE

001010

PAGE_MODE

00 Normal Paging

Persistence Level

0 No Persistence Level Present

GLOBAL_TFI

UL_TFI assigned in Step 1

– Resegment

0 Retransmitted RLC data blocks shall not be re-segmented

<Assignment Info>

Assignment Info struct

Assignment Type

10 (Dual carrier assignment )

Carrier ID

1 (carrier 2)

– EGPRS Window Size

Dependent upon test case (Default 64)

– {0|1 Access Technologies Request}

0 Access technology Request Info not present

– ARAC RETRANSMISSION REQUEST

0 retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested

TLLI_BLOCK_CHANNEL_CODING

1

{0|1 BEP_PERIOD2}

0 BEP_PERIOD2 not present

Packet Timing Advance

{ 0|1 < TIMING_ADVANCE_VALUE >

1 Timing Advance Value present

– TIMING_ADVANCE_VALUE }

30 bit periods

{ 0|1< TIMING_ADVANCE_INDEX > <TIMING_ADVANCE_TIMESLOT_NUMBER > }

0 (no timing advance index)

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

0

{0 | 1 … }

0 (BTTI)

< Dynamic Allocation 2 struct > :

See below

EGPRS Modulation and Coding Scheme

Dependant upon test case (Default MCS_1)

{00 | 01…

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present

0 | 1< Frequency Parameters_C2>

1 Frequency Parameters_C2 Present

}

P0_C1 not present

{ 0 | 1 < PFI : bit (7) > }

0 not present

{ 0 | 1 < RLC_MODE : bit (1) > }

0 not present

{ 0 | 1 < NPM Transfer Time : bit (5) > }

0 not present

{ 0 | 1 — 1 indicates FANR is activated

0 FANR not activated

}

< Uplink EGPRS Level: < EGPRS Level IE > >

00 (EGPRS)

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

0 not present

Dynamic Allocation 2 struct:

EXTENDED_DYNAMIC_ALLOCATION

0 dynamic allocation only

{ 0 | 1 < P0 > …}

0 downlink power control is not used

USF_GRANULARITY

0 MS shall transmit only one RLC/MAC block

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT >}

1 assign uplink TFI

– UPLINK_TFI_ASSIGNMENT

00000

{0 | 1 (with/without power control parameters)

0 allocation without power control parameters

N_USF

1011 (11 USFs signalled)

{ 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1)

0 USF not assigned on C1 / TN0

0 USF not assigned on C1 / TN1

0 USF not assigned on C1 / TN2

0 USF not assigned on C1 / TN3

1 USF assigned on C1 / TN4

– USF

Arbitrarily chosen (default 000)

0 USF not assigned on C1 / TN5

0 USF not assigned on C1 / TN6

0 USF not assigned on C1 / TN7

0 USF not assigned on C2 / TN0

0 USF not assigned on C2 / TN1

0 USF not assigned on C2 / TN2

1 USF assigned on C2 / TN3

– USF

Arbitrarily chosen (default 000)

(note: it is allowed to truncate the list; no USFs assigned on remaining timeslots)

PACKET TIMESLOT RECONFIGURE message in step 88:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Assignment of Single carrier only)

Carrier ID

0 (carrier 1)

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

1

0 | 1 <TIMESLOT ALLOCATION_C2>

1(new time slot assignment)

01

01 (Legacy IEs Used)

0 | 1< Frequency Parameters_C1>

1 Frequency Parameters_C1 Present (new frequency assigned)

0 | 1< Frequency Parameters_C2>

0 Frequency Parameters_C2 Absent

TSC

arbitrarily chosen

N_TS

New TS and USF assigned

0 | 1 < Uplink Control Timeslot C1>

0 (Not present)

0 | 1 < Uplink Control Timeslot C2>

0 (Not present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

58b.1.2a Single Carrier concurrent TBF to DLMC TBF/ Uplink DLMC TBF (on both carrier 1 and carrier 2)/ Reconfigured back to single Carrier Concurrent TBF

58b.1.2a.1 Conformance requirement

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration.

A mobile station that supports DLMC configuration may be assigned one or more UFPS (see 3GPP TS 45.008 [15]) where the assigned UFPS(s) and their associated carriers are numbered as described in sub-clause 8.1.1.1.3. For the case where a UFPS is defined by a mobile allocation (see sub-clause 12.10a) a mobile station in DLMC configuration will perform carrier selection to determine the set of downlink carriers it can receive during any given radio block period as described in 3GPP TS 45.002 [13].

In DLMC configuration RLC/MAC blocks shall not be scheduled on multiple uplink carriers in the same radio block period whereas RLC/MAC blocks may be scheduled on one or more downlink carriers in the same radio block period.

If the network and mobile station both support Downlink Multi Carrier, the network may send a downlink assignment message (PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE) to a mobile station assigning a downlink TBF with packet resources on multiple downlink carriers and thereby establish a DLMC configuration. In this case a mobile station is assigned a set of one or more UFPSs (see 3GPP TS 45.008 [15]) that in total provide up to 16 carriers. The carriers assigned to a given UFPS shall belong to the same frequency band and Mobile Allocation. If the MS has indicated it supports inter-band reception (see 3GPP TS 24.008) the set of provided carriers shall belong to a maximum of two of the supported frequency bands. The set of UFPS in a DLMC configuration are numbered UFPS1, UFPS2, and so on, ending with UFPSM where UFPS numbering is managed as follows:

– If an assignment message is sent to a mobile station with an ongoing downlink TBF for which only a single carrier is assigned then that carrier shall be considered as UFPS1 for the case where the assignment message establishes a DLMC configuration information.

– An assignment message that assigns one or more new UFPS results in each new UFPS being numbered according to the order in which it was assigned. For example, if UFPS1 and UFPS2 are currently assigned and two new UFPS are added then the first new UFPS becomes UFPS3 and the second new UFPS becomes UFPS4.

– An assignment message that deletes one or more existing UFPS results in the remaining UFPS being renumbered to ensure sequential UFPS numbering. For example, if UFPS1, UFPS2 …UFPS5 are currently assigned and UFPS3 is deleted then UFPS4 becomes UFPS3 and UFPS5 becomes UFPS4.

In the case of a mobile station in a DLMC configuration where the continuous timing advance procedure is used the assignment message indicates the carrier on which the PTCCH is allocated. If a mobile station in a DLMC configuration subsequently receives an assignment message that results in the mobile station no longer being in a DLMC configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned. When the MS receives the updated value of TA from the BTS on the downlink PTCCH, it shall always use the last received TA value for the uplink transmission.

Within the packet resource assignments (see 3GPP TS 44.018 and 3GPP TS 44.060) for uplink or downlink messages the MS gets the Timing Advance Index (TAI). The MS shall send access bursts on the subchannel defined by the TAI on the PTCCH. These access bursts received on PTCCH are used by the BTS to derive the timing advance.

References

3GPP TS 44.060; subclause 5.5.1.7, 7.1.2.5, 5.13 and 8.1.1.1.3

3GPP TS 45.10, subclause 6.5.2.

58b.1.2a.2 Test purpose

To verify that:

– the MS is able to change from single carrier uplink TBF to a downlink multi carrier configuration and operate downlink multi carrier TBF and an uplink TBF.

– in Downlink Multi Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1.

– the mobile station uses the continuous update timing advance mechanism and sends access bursts on the PTCCH slots as determined by the Timing Advance Index sent in the PACKET UPLINK ASSIGNMENT message.

– the MS is able to change from multi carrier to a single carrier assignment and continue to use the same Timing advance parameters if the values are not changed.

58b.1.2a.3 Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Multi Carrier supported.

Mobile Station:

Support for Downlink Multi Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated , and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The timing advance value is included in the PACKET UPLINK ASSIGNMENT. The MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH with assignment type set to multi carrier assignment. This configures the MS in Multi Carrier Downlink configuration. The SS sends RLC data blocks on downlink Carrier 1 and Carrier 2 simultaneously. The MS receives a PACKET UPLINK ASSIGNMENT with assignment type set to multi carrier assignment where the existing single UL carrier will correspond to downlink Carrier1 with no changed parameters and an the uplink carrier corresponding to downlink Carrier 2 will be activated such that UL carriers will be activated for both existing DL carriers. The timing advance parameter values are assigned. Timing advanced Index is set to 2. Frequency parameters are specified separately. The SS sends PACKET UPLINK ACK/NACK on both carriers assigning USF. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 1 such that (FN mod (8*52)) = 64 (TAI =2).

The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single downlink carrier assignment designated as carrier C1 meaning the MS leaves DLMC mode as Carrier2 and its corresponding uplink carrier removed. The timing advance parameters are unchanged. The MS is polled to see if MS responds on C2. The uplink and downlink data transfer is initiated on both directions simultaneously. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 1 such that (FN mod (8*52)) = 64 (TAI =2) same as before.

The SS sends a PACKET DOWNLINK ASSIGNMENT and a PACKET UPLINK ASSIGNMENT to re-establish the concurrent multi carrier TBF meaning the MS enters DLMC mode where downlink Carrier 1 and 2 are configured and uplink carriers corresponding to Carrier 1 and Carrier 2 are activated. The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single downlink carrier assignment on carrier C2. The timing advance parameters are unchanged. The MS is polled to see if MS responds on C1. The uplink and downlink data transfer is initiated on both directions simultaneously. During uplink transfer the SS continues monitoring the access burst on PTCCH on carrier 2 such that (FN mod (8*52)) = 64 (TAI =2) same as before as the timing advance parameter is unchanged.

The MS is configured back to multi carrier configuration mode as it has been done previously.(PACKET UPLINK and DONWLINK ASSIGNMENT). The SS sends a PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C1. The timing advance parameters are changed to an arbitrarily chosen value. The MS is polled to see if MS responds on C2. The uplink and downlink data transfer is initiated on both directions simultaneously. The SS monitors the access burst on PTCCH on carrier 1SS shall verify that the access burst are sent in the correct idle slots as specified in 3GPP TS 05.02 table 6.

MS is reconfigured in multi carrier configuration mode. The SS sends PACKET TIMESLOT RECONFIGURE message assigning a single carrier assignment on carrier C1. New frequency and timeslot values are assigned and new timeslot allocations are assigned. The timing advance index is set to 0. The MS completes the uplink and downlink data transfer. During the uplink data transfer the SS monitors the access burst on PTCCH which are located on slots with numbers FN, such that (FN mod (8*52)) = 12 for Timing Advance Index = 0 (3GPP TS 03.64 subclause 6.5.7.2 and 3GPP TS 05.02 table 6). The access burst contents shall be MESSAGE_TYPE = 011111 and CTRL_ACK = 11.

Maximum Duration of Test

10 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 10000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

Timing advance values included.

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

5

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDCH assigned in Step 1. Addressing the MS using the UL TFI assigned in Step 1. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2a. Timing advance values included. Including Timing Advance Index = 2 Assignment Type = DLMC Assignment

6

SS

Wait for at least 3 block periods

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (Start with BSN 0). USF not Assigned to MS.

8

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field. USF not Assigned to MS.

9

MS -> SS

PACKET DOWNLINK ACK/NACK

Sent on PACCH of the PDCH assigned in Step 5. Addressing the MS using the UL TFI assigned in Step 1MS acknowledges the previously received RLC data

Blocks. Sent on PACCH on the valid RRBP specified in step 5.

10

SS -> MS

PACKET UPLINK ASSIGNMENT

Two Carriers Assigned. New PDCH assigned for carrier2 and carrier 1 will use assigned PDCH in step1. See specific message contents 58b.1.2. Timing advance values included. Including Timing Advance Index = 2

Assignment Type = DLMC Assignment

11

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

12

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

13

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN and MCS-1. USF assigned to the MS.

14

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

15

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

SS acknowledges all received RLC data Block

16

Repeat steps 11-15 10 times. During uplink transfer in the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks that timing advance from PTCCH allocation on carrier1 used for both carriers.

17

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDCH assigned in Step 10 .Addressing the MS using the UL TFI assigned in Step 1.: Assignment type = Single Carrier (C1) Assigned. See specific message contents section of this test case

18

SS

Wait for at least 3 block periods

19

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence. USF not Assigned to MS

20

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to MS

21

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 20

22

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, USF not assigned to the MS and with a valid RRBP field

23

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

24

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

25

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

26

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

27

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

28

SS

Repeat steps 19 – 27 10 times. During uplink transfer in steps the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks the timing advance from PTCCH allocation is on carrier1.

29

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDCH assigned in Step 17. Addressing the MS using the UL TFI assigned in Step 1 .Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included. Including Timing Advance Index = 2: Assignment Type = DLMCAssignment

30

SS

Wait for at least 3 block periods

31

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned to MS.

32

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field. USF not Assigned to MS.

33

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 32.

34

SS -> MS

PACKET UPLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 29. Addressing the MS using the UL TFI assigned in Step 1

Two Carriers Assigned. New PDCH assigned for carrier2 and carrier 1 will use assigned PDCH in step29

See specific message contents 58b.1.2

Timing advance values included. Including Timing Advance Index = 2

Assignment Type = Dual carrier Assignment

35

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, USF assigned to the MS.

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

37

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

38

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

39

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

40

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDCH assigned in Step 34. Addressing the MS using the UL TFI assigned. Assignment type = Single Carrier (C2) Assigned. See specific message contents section of this test

41

SS

Wait for at least 3 block periods

42

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN. USF not Assigned with MCS-1

43

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to the MS.

44

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 43.

45

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF not assigned to the MS with a valid RRBP field

46

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C1 from MS

47

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

48

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

49

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

50

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

51

SS

Repeat steps 42 – 50 10 times. During uplink transfer the SS continues monitoring the access burst on PTCCH such that (FN mod

(8*52)) = 64 (TAI =2). SS checks the timing advance from PTCCH allocation is on carrier2. The SS makes sure that PTCCH slot and TA values from Carrier1 are still applied on Carrier2.

52

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDCH assigned in Step 40 .Addressing the MS using the UL TFI assigned. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included.

Including Timing Advance Index = 2

Assignment Type = DLMCAssignment

53

SS

Wait for at least 3 block periods

54

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned to the MS.

55

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field USF not assigned to the MS.

56

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data

Blocks. Sent on PACCH on the valid RRBP specified in step 57.

57

SS -> MS

PACKET UPLINK ASSIGNMENT

Sent on PACCH of the PDCH assigned in Step 52. Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step 52

See specific message contents 58b.1.2

Timing advance values included. Including Timing Advance Index = 2

Assignment Type = DLMCAssignment

58

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

59

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

60

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

61

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

62

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

63

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDCH assigned in Step 57. Addressing the MS using the UL TFI assigned in step 1. Assignment type = Single Carrier (C1) Assigned. See specific message contents section of this test

64

SS

Wait for at least 3 block periods

65

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN with MCS-1 with valid RRBP field. USF not Assigned to the MS.

66

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field. USF not Assigned to the MS.

67

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data. Blocks. Sent on PACCH on the valid RRBP specified in step 66.

68

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF not assigned to the MS with a valid RRBP field

69

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

70

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

71

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

72

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

73

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

74

SS

Repeat steps 66 – 73 10 times. During uplink transfer the SS continues monitoring the access burst on PTCCH and SS shall verify that the access burst are sent in the correct idle slots as specified in 3GPP TS 05.02 table 6.SS checks the timing advance from PTCCH allocation is on carrier1.

75

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 64 .Addressing the MS using the UL TFI. Two Carriers Assigned. See specific message contents of sub-clause 58b.1.2. Timing advance values included.

Including Timing Advance Index = 2

Assignment Type = DLMCAssignment

76

SS

Wait for at least 3 block periods

77

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not assigned to the MS.

78

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1 with valid RRBP field

79

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data Blocks. Sent on PACCH on the valid RRBP specified in step 78.

80

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS. Two Carriers Assigned. New PDTCH assigned for carrier2 and carrier 1 will use assigned PDTCH in step 1. See specific message contents 58b.1.2. Timing advance values included. Including Timing Advance Index = 2. Assignment Type = DLMCAssignment

81

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

82

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

83

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

84

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

85

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH,

86

SS -> MS

PACKET TIMESLOT RECONFIGURE

Legacy Rel-6 PDU. Sent on PACCH of the PDTCH assigned in Step 80. Addressing the MS using the UL TFI

Timing Advance Index = 0.

Assignment type = Single Carrier (C1) Assigned.

New frequency parameters, New timeslots and new USF parameters specified. See specific message contents section of this test

87

SS

Wait for at least 3 block periods

88

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF not Assigned.

89

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

with MCS-1 with valid RRBP field

90

MS -> SS

PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data. Blocks. Sent on PACCH on the valid RRBP specified in step 89.

91

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF not assigned to the MS with a valid RRBP field.

92

SS

SS monitors that no EGPRS PACKET DOWNLINK ACK/NACK is sent on C2 from MS

93

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

94

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

95

SS -> MS

PACKET UPLINK ACK/NACK

Sent on the PACCH, USF assigned to the MS.

96

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

97

{Completion of Uplink and downlink data transfer}{ C98

completion of downlink and downlink data transfer }

SS

During the uplink data transfer (steps 96 to 99) the SS monitors the access burst on PTCCH which are located on slots with numbers FN, such that (FN mod (8*52)) = 12 for Timing Advance Index = 0 (3GPP TS 03.64 subclause 6.5.7.2 and 3GPP TS 05.02 table 6). The access burst contents shall be MESSAGE_TYPE = 011111 and CTRL_ACK = 11.

Specific Message Contents

PACKET DOWNLINK ASSIGNMENT message in step 5, 29, 52, 75:

Information Element

value/ remark

MESSAGE_TYPE

000010

PAGE_MODE

00 Normal Paging

Persistence Level

0 (no Persistence Level Present)

Referenced Address

Referenced by UL TFI

1

Message Escape Sequence for DLMC…

01

RLC_MODE

0 Acknowledged mode

CONTROL_ACK

0

1 < UFPS : < UFPS struct >

1st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 1st DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 1st Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

1 TIMESLOT_ALLOCATION

arbitrarily chosen (default timeslot 4)

0

MAIO

1 < P0

0000 0dB

1 PR_MODE

0 PR mode A

1

DOWNLINK_TFI_ASSIGNMENT assign

00001

downlink tfi assigned value

1

<Power Control Parameters>}

1 (Power Control Parameters present for Carrier1)

– ALPHA

0.5

– GAMMA for allocated timeslots

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

(default timeslot 4)

0

EMST is not used on this carrier

0

EMSR is not used on this carrier

1 < UFPS : < UFPS struct >

2nd UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 2nd DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 2nd Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

0

same timeslots as the lowest numbered carrier

0

MAIO

0

same P0 and PR_MODE as the lowest numbered carrier

0

same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier

0

same Power Control Parameters as the lowest numbered carrier

0

EMST is not used on this carrier

0

EMSR is not used on this carrier

0

End of CARRIER_SPECIFIC_INFO

0

End of UFPS struct

DLMC Measurement Type

0

< LINK_QUALITY_MEASUREMENT_MODE

00

0

Carrier for Interference Measurements

Packet Timing Advance

1

1 (timing advance value)

100000}

32 bit periods indicated

1

1 (present timing advance index or timing advance timeslot number)

0010

2 timing advance index

0

< Packet Extended Timing Advance

0

< PTCCH_CARRIER

0

< PDAN Coding >

0

< Extended SNS >

0

< BEP_PERIOD2

0

< PFI

0

< NPM Transfer Time

0

Fast Ack/Nack Reporting

00

< Downlink EGPRS Level

0

< Indication of Upper Layer PDU Start for RLC UM

0

< EGPRS Packet Downlink Ack/Nack Type 3 Support

Spare padding

Spare Padding

PACKET UPINK ASSIGNMENT message in step 10,34:

Information Element

value/ remark

MESSAGE_TYPE

001010

PAGE_MODE

00 Normal Paging

Persistence Level

0 No Persistence Level Present

GLOBAL_TFI

UL_TFI assigned in Step 1

– Resegment

0 Retransmitted RLC data blocks shall not be re-segmented

< DLMC UL Carrier Info >

DLMC UL Carrier Info struct

01

1st UL Carrier::Carrier remains unchanged (no information 2st UL Carrier::provided) Carrier 1 use existing

10

Assigned carrier modified or new carrier assigned Carrier 2 added

– BTTI mode

0

– {0 | 1 < UPLINK_TIMESLOT_ALLOCATION }

1 arbitrarily chosen timeslot

< Dynamic Allocation 3 struct > :

See below

EXTENDED_DYNAMIC_ALLOCATION

USF_GRANULARITY

0 MS shall transmit only one RLC/MAC block

0 | 1 < ALPHA

1 Alpha 0.5

{ 0 | 1 < TSC :

1 TSC arbitrarily chosen

0

BTTI mode

USF

1 USF Arbitrarily chosen (default 000)

GAMMA

For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm

EMST

0

EMSR Additional PFCs 1 :

0

EMSR Additional PFCs 2 :

0

EMSR Additional PFCs 3 :

0

EGPRS Window Size

Dependent upon test case (Default 64)

UPLINK_TFI_ASSIGNMENT

00000

Packet Timing Advance IE

(timing advance value

1 1

100000

32 bit periods indicated

timing advance index

1 (present)

timing advance index

2

Packet Extended Timing Advance

0

BEP_PERIOD2

0

PFI

0

RLC_MODE

0

NPM Transfer Time

0

indicates that FANR is activated

0

< Uplink EGPRS Level: < EGPRS Level IE > >

00 (EGPRS)

< Pulse Format IE

0 not present

EGPRS Channel Coding Command 

0000 (MCS-1)

PACKET TIMESLOT RECONFIGURE message in step 17, 63

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

10

escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI

DOWNLINK_RLC_MODE

0

CONTROL_ACK

0

1 < UFPS : < UFPS struct >

1st UFPS struct

| 01

Existing UFPS remains unchanged (no information provided)

1 < UFPS : < UFPS struct >

2st UFPS struct

| 00

Existing UFPS released

DLMC Measurement Type

0

< LINK_QUALITY_MEASUREMENT_MODE

00

Carrier for Interference Measurements

0

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

Packet Extended Timing Advance

0

PTCCH_CARRIER

0

CONTROL_ACK

0

PDAN Coding

0

Extended SNS

0

BEP_PERIOD2

0

PFI of downlink TBF

0

Downlink NPM Transfer Time

0

indicates Fast Ack/Nack Reporting is activated for downlink TBF

0

Downlink EGPRS Level

No change

Indication of Upper Layer PDU Start for RLC UM

0

EGPRS Packet Downlink Ack/Nack Type 3 Support

0

EGPRS Channel Coding Command

0 MCS1

RESEGMENT

0

1 < DLMC UL Carrier struct >

1st DLMC UL struct

| 01

Carrier remains unchanged (no information provided

1 < DLMC UL Carrier struct >

2st DLMC UL struct

| 00

Assigned carrier released

UPLINK EGPRS Window Size 

0

UPLINK_TFI_ASSIGNMENT

PFI of uplink TBF

0

UPLINK_RLC_MODE

0

Uplink NPM Transfer Time

0

indicates that FANR is activated

0

Uplink EGPRS Level

default

Pulse Format

0

Enhanced Flexible Timeslot Assignment

0

Uplink Control Timeslot

0

PACKET TIMESLOT RECONFIGURE message in step 40:

Based on message at step 17 with below deviation:

Information Element

value/ remark

1 < UFPS : < UFPS struct >

1st UFPS struct

| 00

Existing UFPS released

1 < UFPS : < UFPS struct >

2st UFPS struct

| 01

Existing UFPS remains unchanged (no information provided)

….

1 < DLMC UL Carrier struct >

1st DLMC UL struct

| 00

Assigned carrier released

1 < DLMC UL Carrier struct >

| 01

Carrier remains unchanged (no information provided

PACKET UPINK ASSIGNMENT message in step 57:

Based on message at step 10 with below deviation:

Information Element

value/ remark

< DLMC UL Carrier Info >

DLMC UL Carrier Info struct

10

1st UL Carrier:Assigned carrier modified or new carrier assigned Carrier 1 added

01

2st UL Carrier::Carrier remains unchanged (no information provided) Carrier21 use existing

PACKET UPINK ASSIGNMENT message in step 80:

Based on message at step 10 with deviation USF and timeslot is arbitrarily chosen different from message at step 10

PACKET TIMESLOT RECONFIGURE message in step 88:

Based on message at step 17 with deviation new arbitrarily chosen frequency and timeslot number.

58b.1.3 Single Carrier Concurrent TBF/Downlink TBF reconfigured to DLDC configuration / Uplink single carrier TBF reallocated to Carrier 2/Uplink modified to Dual Carrier

58b.1.3.1 Conformance requirement

If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If this message is sent to a mobile station in packet idle mode, the assignment message shall include frequency parameters for both carriers.

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent assignment messages, that carrier shall be considered carrier 1. A subsequent assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration.

If the assignment message contains the Assignment Info IE indicating an assignment type other than ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs on the carrier identified by the Carrier ID field. In this case, if the assignment message addresses TBFs that currently have packet resources assigned on the other carrier (i.e. the carrier not identified by the Carrier ID field) then these packet resources shall be treated as follows:

– these resources are implicitly released, if the ASSIGNMENT TYPE field (carried in the Assignment Info IE) indicates that the assignment is an ‘Assignment on single carrier only’;

– these resources are unchanged, if the ASSIGNMENT TYPE field indicates that the assignment is a ‘Modification of existing assignment’.

If the assignment message contains the Assignment Info IE indicating an assignment type of ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs.

Subsequent assignment messages may be sent to a mobile station operating in a Downlink Dual Carrier configuration as described in sub-clause 8.1.1.1.3.

3GPP TS 44.060; subclause 5.5.1.7, 8.1.1.1.3 and 7.1.2.5

58b.1.3.2 Test purpose

To verify that:

– the MS can change from single carrier concurrent TBF to a DLDC TBF with the uplink reallocated to carrier 2.

– re-assignment with different Assignment type for downlink and uplink.

58b.1.3.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Dual Carrier supported.

Mobile Station:

Support for Downlink Dual Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks. MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH. MS receives another PACKET DOWNLINK ASSIGNMENT message on its PACCH with dual carrier assignment type. SS transmits downlink RLC data blocks for on both carriers. MS sends uplink data block on carrier 1. SS sends packet downlink assignment message (assignment type single carrier) to establish single carrier configuration on the downlink side on carrier 1. SS sends downlink blocks on carrier 1 and MS sends acknowledgment. MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH with dual carrier assignment type. Frequency parameters for both carriers are specified. Carrier 1 is specified for all other parameters and this applies to both carriers. SS sends another PACKET DOWNLINK ASSIGNMENT message. All the parameters for carrier 1 and 2 are specified separately. SS sends a PACKET UPLINK ASSIGNMENT (assignment of single carrier only) message. Uplink TBF is reallocated to carrier 2. SS sends another PACKET UPLINK ASSIGNMENT (modification of existing assignment) message. Uplink TBF is reallocated to carrier 1. MS receives another PACKET UPLINK ASSIGNMENT (dual carrier assignment) message. Both carriers are assigned on uplink side. MS completes uplink data transfer.

After each assignment SS checks:

– that the MS is sending uplink data block only on the uplink assigned carrier

– that the MS answers to the polled downlink data block only on the downlink assigned carrier

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 500 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 1.

Addressing the MS using the UL TFI assigned in Step 1.

5

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type “Modification of existing assignment”

Carrier 2 assigned.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (start with BSN 0)

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

7

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

8

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

MCS-1. A valid RRBP is indicated.

9

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

10

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned.

11

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

12

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

13

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

14

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type “Dual Carrier assignment”

Both Carriers assigned.

15

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

Send with MCS-1, USF assigned to MS in step 13.

16

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on carrier 1 with MCS-1. A valid RRBP is indicated.

17

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on carrier 1.

18

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

19

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 2 assigned.

20

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

21

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

22

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS

23

SS checks that the MS does not answer

24

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 1 is assigned.

25

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1,

26

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

27

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

28

SS checks that the MS does not answer

29

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Dual Carrier assignment ”

Both Carriers are assigned.

30

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

Send with MCS-1. USF assigned to the MS.

With next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field

31

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on carrier 1.

32

MS -> SS

EGPRS DOWNLINK PACKET DOWNLINK ACK/NACK

On carrier 1, in the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

33

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS-> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

36

{Completion of uplink RLC data block transfer}

Specific Message Contents

None.

58b.1.3a Single Carrier Concurrent TBF/Downlink TBF reconfigured to DLMC configuration / Uplink single carrier TBF reallocated to Carrier 2/Uplink modified to Multi Carrier

58b.1.3a.1 Conformance requirement

If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may:

– provide new frequency parameters for all newly assigned and existing carriers

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration. If an assignment message is sent to a mobile station with an ongoing downlink TBF for which only a single carrier is assigned then that carrier shall be considered as UFPS1 for the case where the assignment message establishes a DLMC configuration information.

Subsequent assignment messages may be sent to a mobile station operating in a Downlink Dual Carrier configuration or DLMC configuration as described in sub-clause 8.1.1.1.3.

3GPP TS 44.060; subclause 5.5.1.7, 8.1.1.1.3 and 7.1.2.5

58b.1.3a.2 Test purpose

To verify that:

– the MS can change from single carrier concurrent TBF to a DLMC TBF with the uplink reallocated to carrier 2.

– re-assignment with different Assignment type for downlink and uplink.

58b.1.3a.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Multi Carrier supported.

Mobile Station:

Support for Downlink Multi Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks. MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH. MS receives another PACKET DOWNLINK ASSIGNMENT message on its PACCH with DLMC assignment type. SS transmits downlink RLC data blocks for on both carriers. MS sends uplink data block on carrier 1. SS sends packet downlink assignment message (assignment type single carrier) to establish single carrier configuration on the downlink side on carrier 1. SS sends downlink blocks on carrier 1 and MS sends acknowledgment. MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH with DLMC assignment type. Frequency parameters for both carriers are specified. Carrier 1 is specified for all other parameters and this applies to both carriers. SS sends another PACKET DOWNLINK ASSIGNMENT message. All the parameters for carrier 1 and 2 are specified separately. SS sends a PACKET UPLINK ASSIGNMENT (assignment of single carrier only) message. Uplink TBF is reallocated to carrier 2. SS sends another PACKET UPLINK ASSIGNMENT (modification of existing assignment) message. Uplink TBF is reallocated to carrier 1. MS receives another PACKET UPLINK ASSIGNMENT (DLMC assignment) message. Both carriers are assigned on uplink side. MS completes uplink data transfer.

After each assignment SS checks:

– that the MS is sending uplink data block only on the uplink assigned carrier

– that the MS answers to the polled downlink data block only on the downlink assigned carrier

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 500 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH assigned in Step 1.

Addressing the MS using the UL TFI assigned in Step 1.

5

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type DLMC

Carrier 2 added meaning 2nd UPFS added with” Existing UFPS changed/new UFPS provided”.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (start with BSN 0)

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

7

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

8

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

MCS-1. A valid RRBP is indicated.

9

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

10

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned.

11

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

12

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

13

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

14

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1.

Assignment type DLMC

Both Carriers/UFPS assigned.

15

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

Send with MCS-1, USF assigned to MS in step 13.

16

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on carrier 1 with MCS-1. A valid RRBP is indicated.

17

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on carrier 1

18

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

19

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 2 assigned.

20

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

21

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

22

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS

23

SS checks that the MS does not answer

24

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only” Carrier 1 is assigned.

25

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1,

26

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

27

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

28

SS checks that the MS does not answer

29

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type DLMC

Both Carriers/UFPS are assigned.

30

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

Send with MCS-1. USF assigned to the MS.

With next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field

31

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on carrier 1.

32

MS -> SS

EGPRS DOWNLINK PACKET DOWNLINK ACK/NACK

On carrier 1, in the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

33

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS-> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

36

{Completion of uplink RLC data block transfer}

Specific Message Contents

None.

58b.1.4 Single Carrier Uplink TBF with no Downlink TBF / DLDC TBF established / Uplink DLDC TBF (on both carrier 1 and carrier 2)/ Uplink TBF Reconfigured to Single Carrier TBF

58b.1.4.1 Conformance requirement

If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If this message is sent to a mobile station in packet idle mode, the assignment message shall include frequency parameters for both carriers. If this message is sent to a mobile station which is in packet transfer mode (and is not in a Downlink Dual Carrier configuration) the assignment message shall either:

– provide new frequency parameters for both carriers, or

– provide frequency parameters for only one carrier (carrier 2) in which case the frequency parameters for carrier 1 remain unchanged.

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent assignment messages, that carrier shall be considered carrier 1. A subsequent assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration.

When assigning resources on one carrier to a mobile station which is currently in a Downlink Dual Carrier configuration using a format of the message which does not include the Carrier ID field, the network shall always include frequency parameters;

If the assignment message contains the Assignment Info IE indicating an assignment type other than ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs on the carrier identified by the Carrier ID field. In this case, if the assignment message addresses TBFs that currently have packet resources assigned on the other carrier (i.e. the carrier not identified by the Carrier ID field) then these packet resources shall be treated as follows:

– these resources are implicitly released, if the ASSIGNMENT TYPE field (carried in the Assignment Info IE) indicates that the assignment is an ‘Assignment on single carrier only’;

– these resources are unchanged, if the ASSIGNMENT TYPE field indicates that the assignment is a ‘Modification of existing assignment’.

If the assignment message contains the Assignment Info IE indicating an assignment type of ‘Dual Carrier assignment’, then the packet resources specified in this message replace any existing assignment for the addressed TBFs.

3GPP TS 44.060; subclause 5.5.1.7 and 8.1.1.1.3

58b.1.4.2 Test purpose

To verify that the MS:

-the MS can change from single carrier uplink TBF to (with no downlink TBF) to downlink dual carrier TBF with additional resources on new frequency and resources for uplink TBF being allocated on both carriers.

-the MS is able to change from dual carrier configuration in uplink and downlink direction and operate a single carrier TBF in uplink.

58b.1.4.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Dual Carrier supported.

Mobile Station:

Support for Downlink Dual Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. MS receives a PACKET TIMESLOT RECONFIGURE (Assignment type “Dual Carrier assignment”) message on its PACCH, instructing a Dual Carrier configuration for both uplink and downlink. SS sends downlink data block simultaneously on both carriers and MS sends uplink data block.

SS sends another PACKET TIMESLOT RECONFIGURE (Assignment type “Dual Carrier assignment”) to change the USF and timeslot assignment on both carriers in both uplink and downlink direction. MS sends PACKET DOWNLINK DUMMY CONTROL BLOCK on USF not assigned to MS to verify MS does not response to old USF assignment. MS sends uplink data blocks on both carriers on newly assigned USF. The SS sends downlink RLC data blocks on carrier 1 and carrier 2 under new assignment.

MS then receives a PACKET UPLINK ASSIGNMENT message (with assignment type single carrier assignment) to establish single carrier operation on uplink side (carrier 1). MS should not send any data on carrier 2.

SS sends PACKET UPLINK ASSIGNMENT message (Assignment type “Dual Carrier assignment”) to change uplink side from single carrier to dual carrier. MS then receives a PACKET UPLINK ASSIGNMENT message (with assignment type single carrier assignment) to establish single carrier operation on uplink side (carrier 1). This is a legacy Rel-6 message. MS finishes uplink data transfer.

Maximum Duration of Test

8 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 4000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

5

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 1.

Assignment type “Dual Carrier assignment”

Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned for both uplink and downlink.

See specific message contents.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (start with BSN 0)

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. USF assigned to the MS. MCS-1.

8

MS ->SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1 SS verifies that the correct BSN is received and the correct MCS is used.

9

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

10

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 containing USF assigned to the MS.

11

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

12

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

13

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

14

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 1.

Assignment type “Dual Carrier assignment”

New assignment of timeslot and usf for both uplink and downlink.

See specific message contents.

15

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 containing USF assigned to the MS in step 5.

16

SS

SS should check MS does not send any data on carrier 1.

17

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, USF assigned to the MS.

18

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

19

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to MS in step 5.

20

SS

SS should check MS does not send any data on carrier 2.

21

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, USF assigned to the MS.

22

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

23

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

24

SS-> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN MCS-1. A valid RRBP is indicated.

25

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. MCS-1

26

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

27

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned.

28

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

29

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

31

SS

SS should check no data is send on USF on carrier 2 from MS

32

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Dual Carrier assignment”

Both carrier 1 and 2 assigned.

33

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2

SS verifies that the correct BSN is received and the correct MCS is used.

37

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned. Legacy Rel-6 message.

See specific message contents.

38

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

39

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

40

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. A valid RRBP is indicated.

41

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. MCS-1

42

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

43

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

44

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

45

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 with next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field, sent on Carrier 1. MCS-1

46

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

Received on the assigned PDTCH on carrier1

In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

47

SS-> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

48

{Completion of uplink RLC data block transfer}

Specific Message Contents

PACKET TIMESLOT RECONFIGURE message in step 5:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

DL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Dual Carrier Assignment)

Carrier ID

0 (carrier 1)

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

1

0 | 1 <TIMESLOT ALLOCATION_C2>

1 (new assignment)

10

Optimized Dual Carrier frequency parameters used

Dual Carrier Frequency Parameters

Dual Carrier Frequency Parameters IE

TSC

arbitrarily chosen

0 | 1 < Uplink Control Timeslot C1>

0 (Not present)

0 | 1 < Uplink Control Timeslot C2>

0 (Not present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

0 | 1 < UPLINK_RLC_MODE >

0 (Not present)

0 | 1 < NPM Transfer Time) >

0 (Not present)

0

Fast Ack/Nack Reporting not activated

< Uplink EGPRS Level>

00 (EGPRS)

< Downlink EGPRS Level >

00 (EGPRS)

0 | 1 < Pulse Format>

0 (Not present)

< padding bits >

PACKET TIMESLOT RECONFIGURE message in step 14:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

DL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Dual Carrier Assignment)

Carrier ID

arbitrarily chosen

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

Different from step 1

0 | 1 <TIMESLOT ALLOCATION_C2>

1 (new assignment)

10

Optimized Dual Carrier frequency parameters used

Dual Carrier Frequency Parameters

Dual Carrier Frequency Parameters IE

TSC

arbitrarily chosen

0 | 1 < Uplink Control Timeslot C1>

1 (present)

0 | 1 < Uplink Control Timeslot C2>

1 (present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

0 | 1 < UPLINK_RLC_MODE >

0 (Not present)

0 | 1 < NPM Transfer Time) >

0 (Not present)

0

Fast Ack/Nack Reporting not activated

< Uplink EGPRS Level>

00 (EGPRS)

< Downlink EGPRS Level >

00 (EGPRS)

0 | 1 < Pulse Format>

0 (Not present)

< padding bits >

PACKET UPLINK ASSIGNMENT message in step 27:

Information Element

value/ remark

MESSAGE_TYPE

001110

PAGE_MODE

Normal Paging

Referenced Address

1 (not Global TFI)

1 (not TLLI)

1 (not TQI)

1 (Packet Request Reference)

– Packet Request Reference

information field sent in PACKET CHANNEL REQUEST and frame number in which PACKET CHANNEL REQUEST was received

CHANNEL_CODING_COMMAND

MCS-2 coding

TLLI_BLOCK_CHANNEL_CODING

MCS-1 coding

{L|H<UPLINK_TFI_ASSIGNMENT>}

H (assign an uplink TFI)

– UPLINK_TFI_ASSIGNMENT

0000110 (uplink TBF identifier)

Packet Timing Advance

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

0 (no timing advance index)

{L|H<Frequency Parameters>}

H (Frequency Parameters present)

– Frequency Parameters

– TSC

5

00 (no hopping)

– ARFCN

For GSM 700, T-GSM 810: 460

For GSM 850: 150

For GSM 900: 30

For DCS 1 800: 650

For PCS 1 900: 650

{0|1<List of Reference Frequency lists>}

0 (no reference frequencies)

{0|1<Mobile Allocation list>}

0 (no MA)

LL (Dynamic Allocation)

Dynamic Allocation

H (Contention Resolution TLLI is present)

– CONTENTION_RESOLUTION_TLLI

As allocated to the MS

H (power control parameters)

– ALPHA

0.5

– GAMMA_TN0

0 (not present)

– GAMMA_TN1

0 (not present)

– GAMMA_TN2

1

– GAMMA_TN2

8 dBm (GSM 700), 8 dBm (T-GSM 810), 8 dBm (GSM 850), 8 dBm (GSM 900), 6 dBm (DCS 1 800), 6 dBm (PCS 1 900)

– GAMMA_TN3

0 (not present)

– GAMMA_TN4

0 (not present)

– GAMMA_TN5

0 (not present)

– GAMMA_TN6

0 (not present)

– GAMMA_TN7

0 (not present)

58b.1.4a Single Carrier Uplink TBF with no Downlink TBF / DLMC TBF established / Uplink DLMC TBF (on both carrier 1 and carrier 2)/ Uplink TBF Reconfigured to Single Carrier TBF

58b.1.4a.1 Conformance requirement

If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may:

– provide new frequency parameters for all newly assigned and existing carriers, or

– provide new frequency parameters for all newly assigned carriers, modify the frequency parameters for a subset of the existing carriers and leave the frequency parameters for the remaining existing carriers unchanged. When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration.

Subsequent assignment messages may be sent to a mobile station operating in a Downlink Dual Carrier configuration or DLMC configuration as described in sub-clause 8.1.1.1.3.

3GPP TS 44.060; subclause 5.5.1.7 and 8.1.1.1.3

58b.1.4a.2 Test purpose

To verify that the MS:

– the MS can change from single carrier uplink TBF to (with no downlink TBF) to downlink dual carrier TBF with additional resources on new frequency and resources for uplink TBF being allocated on both carriers.

– the MS is able to change from dual carrier configuration in uplink and downlink direction and operate a single carrier TBF in uplink.

58b.1.4a.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, DLMC supported.

Mobile Station:

Support for DLMC indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. MS receives a PACKET TIMESLOT RECONFIGURE (Assignment type “DLMC assignment”) message on its PACCH, instructing a DLMC configuration for both uplink and downlink. SS sends downlink data block simultaneously on both carriers and MS sends uplink data block.

SS sends another PACKET TIMESLOT RECONFIGURE (Assignment type “DLMC assignment”) to change the USF and timeslot assignment on both carriers in both uplink and downlink direction. MS sends PACKET DOWNLINK DUMMY CONTROL BLOCK on USF not assigned to MS to verify MS does not response to old USF assignment. MS sends uplink data blocks on both carriers on newly assigned USF. The SS sends downlink RLC data blocks on carrier 1 and carrier 2 under new assignment.

MS then receives a PACKET UPLINK ASSIGNMENT message (with assignment type single carrier assignment) to establish single carrier operation on uplink side (carrier 1). MS should not send any data on carrier 2.

SS sends PACKET UPLINK ASSIGNMENT message (Assignment type DLMC) to change uplink side from single carrier to DLMC. MS then receives a PACKET UPLINK ASSIGNMENT message (with assignment type single carrier assignment) to establish single carrier operation on uplink side (carrier 1). This is a legacy Rel-6 message. MS finishes uplink data transfer.

Maximum Duration of Test

8 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

{Uplink dynamic allocation two phase access}

N = 4000 octets

USF_GRANULARITY = 1 block

EGPRS Channel Coding Command: MCS-1

2

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.

3

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH

SS verifies that the BSN starts from 0, and the correct MCS is used.

4

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

5

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 1.

Assignment type “DLMC assignment”

Addressing the MS using the UL TFI assigned in Step 1.

Two Carriers Assigned for both uplink and downlink.

See specific message contents.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN (start with BSN 0)

USF assigned to the MS. MCS-1. A valid RRBP is indicated.

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. USF assigned to the MS. MCS-1.

8

MS ->SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1 SS verifies that the correct BSN is received and the correct MCS is used.

9

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

10

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 containing USF assigned to the MS.

11

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

12

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

13

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

14

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH assigned in Step 1.

Assignment type “DLMC assignment”

New assignment of timeslot and usf for both uplink and downlink.

See specific message contents.

15

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 containing USF assigned to the MS in step 5.

16

SS

SS should check MS does not send any data on carrier 1.

17

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, USF assigned to the MS.

18

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

19

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to MS in step 5.

20

SS

SS should check MS does not send any data on carrier 2.

21

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, USF assigned to the MS.

22

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier2

SS verifies that the correct BSN is received and the correct MCS is used.

23

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

24

SS-> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN MCS-1. A valid RRBP is indicated.

25

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. MCS-1

26

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

27

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned.

28

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

29

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

31

SS

SS should check no data is send on USF on carrier 2 from MS

32

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Dual Carrier assignment”

Both carrier 1 and 2 assigned.

33

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to the MS.

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2

SS verifies that the correct BSN is received and the correct MCS is used.

37

SS -> MS

PACKET UPLINK ASSIGNMENT

Addressed to the MS.

Assignment type “Assignment of single carrier only”

Carrier 1 assigned. Legacy Rel-6 message.

See specific message contents.

38

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

39

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

40

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. A valid RRBP is indicated.

41

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as data block sent on carrier 1. MCS-1

42

MS->SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field.

43

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1, containing USF assigned to the MS.

44

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier1

SS verifies that the correct BSN is received and the correct MCS is used.

45

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on the PACCH of the PDCH assigned on carrier 1 with next in sequence BSN. FBI bit set to ‘1’ and valid RRBP field, sent on Carrier 1. MCS-1

46

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

Received on the assigned PDTCH on carrier1

In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

47

SS-> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received.

48

{Completion of uplink RLC data block transfer}

Specific Message Contents

PACKET TIMESLOT RECONFIGURE message in step 5:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

10

escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI

DOWNLINK_RLC_MODE

0

CONTROL_ACK

0

1 < UFPS : < UFPS struct >

1st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

Arbitrarily chosen based on existing UL carrier 1

1 < UFPS : < UFPS struct >

2st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

Arbitrarily chosen

DLMC Measurement Type

0

< LINK_QUALITY_MEASUREMENT_MODE

00

Carrier for Interference Measurements

0

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

Packet Extended Timing Advance

0

PTCCH_CARRIER

0

CONTROL_ACK

0

PDAN Coding

0

Extended SNS

0

BEP_PERIOD2

0

PFI of downlink TBF

0

Downlink NPM Transfer Time

0

indicates Fast Ack/Nack Reporting is activated for downlink TBF

0

Downlink EGPRS Level

No change

Indication of Upper Layer PDU Start for RLC UM

0

EGPRS Packet Downlink Ack/Nack Type 3 Support

0

EGPRS Channel Coding Command

0 MCS1

RESEGMENT

0

1 < DLMC UL Carrier struct >

1st DLMC UL struct

| 01

Carrier remains unchanged (no information provided

1 < DLMC UL Carrier struct >

2st DLMC UL struct

| 10

Assigned carrier modified or new carrier assigned Carrier 2 Arbitrarily chosen value’s for Carrier 2

UPLINK EGPRS Window Size 

0

UPLINK_TFI_ASSIGNMENT

PFI of uplink TBF

0

UPLINK_RLC_MODE

0

Uplink NPM Transfer Time

0

indicates that FANR is activated

0

Uplink EGPRS Level

default

Pulse Format

0

Enhanced Flexible Timeslot Assignment

0

Uplink Control Timeslot

0

PACKET TIMESLOT RECONFIGURE message in step 14:

Based on message at step 5 with below deviation:

Information Element

value/ remark

1 < UFPS : < UFPS struct >

1st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 1st DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 1st Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

1 TIMESLOT_ALLOCATION

arbitrarily chosen timeslot and usf different from step 5

1 < UFPS : < UFPS struct >

2st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

| 1 < DLMC Frequency Para

< 1st DLMC Frequency Parameters IE > Present

{ 1 < CARRIER_SPECIFIC_INFO

< 1st Carrier Specific Info struct >

| 10

Existing carrier changed/new carrier provided

0

BTTI mode

1 TIMESLOT_ALLOCATION

arbitrarily chosen timeslot and usf different from step 5

< DLMC UL Carrier Info >

DLMC UL Carrier Info struct

10

1st UL Assigned carrier modified or new carrier assigned Carrier 1 added

– BTTI mode

0

– {0 | 1 < UPLINK_TIMESLOT_ALLOCATION }

1 arbitrarily chosen timeslot but different from step 5

USF

1 arbitrarily chosen but different from step 5

10

Assigned carrier modified or new carrier assigned Carrier 2 added

– BTTI mode

0

– {0 | 1 < UPLINK_TIMESLOT_ALLOCATION }

1 arbitrarily chosen timeslot but different from step 5

USF

1 arbitrarily chosen but different from step 5

PACKET UPLINK ASSIGNMENT message in step 27:

Information Element

value/ remark

MESSAGE_TYPE

001110

PAGE_MODE

Normal Paging

Referenced Address

1 (not Global TFI)

1 (not TLLI)

1 (not TQI)

1 (Packet Request Reference)

– Packet Request Reference

information field sent in PACKET CHANNEL REQUEST and frame number in which PACKET CHANNEL REQUEST was received

CHANNEL_CODING_COMMAND

MCS-2 coding

TLLI_BLOCK_CHANNEL_CODING

MCS-1 coding

{L|H<UPLINK_TFI_ASSIGNMENT>}

H (assign an uplink TFI)

– UPLINK_TFI_ASSIGNMENT

0000110 (uplink TBF identifier)

Packet Timing Advance

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

0 (no timing advance index)

{L|H<Frequency Parameters>}

H (Frequency Parameters present)

– Frequency Parameters

– TSC

5

00 (no hopping)

– ARFCN

For GSM 700, T-GSM 810: 460

For GSM 850: 150

For GSM 900: 30

For DCS 1 800: 650

For PCS 1 900: 650

{0|1<List of Reference Frequency lists>}

0 (no reference frequencies)

{0|1<Mobile Allocation list>}

0 (no MA)

LL (Dynamic Allocation)

Dynamic Allocation

H (Contention Resolution TLLI is present)

– CONTENTION_RESOLUTION_TLLI

As allocated to the MS

H (power control parameters)

– ALPHA

0.5

– GAMMA_TN0

0 (not present)

– GAMMA_TN1

0 (not present)

– GAMMA_TN2

1

– GAMMA_TN2

8 dBm (GSM 700), 8 dBm (T-GSM 810), 8 dBm (GSM 850), 8 dBm (GSM 900), 6 dBm (DCS 1 800), 6 dBm (PCS 1 900)

– GAMMA_TN3

0 (not present)

– GAMMA_TN4

0 (not present)

– GAMMA_TN5

0 (not present)

– GAMMA_TN6

0 (not present)

– GAMMA_TN7

0 (not present)

58b.1.5 Single Carrier Downlink TBF with No Uplink TBF/ Downlink reconfigured to DLDC TBF/ Uplink TBF established

58b.1.5.1 Conformance requirement

If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If this message is sent to a mobile station in packet idle mode, the assignment message shall include frequency parameters for both carriers. If this message is sent to a mobile station which is in packet transfer mode (and is not in a Downlink Dual Carrier configuration) the assignment message shall either:

– provide new frequency parameters for both carriers, or

– provide frequency parameters for only one carrier (carrier 2) in which case the frequency parameters for carrier 1 remain unchanged.

In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. A mobile station with a Downlink Dual Carrier configuration shall not be allocated radio blocks on both radio frequency channels during any given radio block period.

3GPP TS 44.060; subclause 5.5.1.7 and 8.1.1.1

58b.1.5.2 Test purpose

To verify:

The MS is able to change from Single Carrier downlink TBF (no uplink TBF in process) to operate a DLDC TBF.

– new (additional resources) frequency parameters can be allocated to both carriers

– when frequency parameters are allocated for only one carrier the other carrier remain unchanged.

58b.1.5.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink Dual Carrier supported.

Mobile Station:

Support for Downlink Dual Carrier indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

MS receives an IMMEDIATE ASSIGNMENT message on its PCH allocating resources for carrier 1. SS transmits downlink RLC data blocks. MS responds by sending a PACKET DOWNLINK ACK/NACK. An uplink data transfer is triggered, the MS insert the Channel Request Description in a PDAN and the SS sends a PACKET TIMESLOT RECONFIGURE message to the MS instructing a Dual Carrier Downlink configuration and single carrier on the uplink side (carrier 1). SS starts to send downlink data and MS sends uplink data blocks. SS sends ACK/NACK message to the MS. MS receives a PACKET DOWNLINK ASSIGNMENT message instructing a single carrier assignment for downlink side and brings back it to the initial state (step 1).

SS sends another PACKET TIMESLOT RECONFIGURE message to the MS instructing a dual carrier configuration on downlink side and single carrier on the uplink side (carrier 2). SS starts to send downlink data and MS sends uplink data blocks. SS sends ACK/NACK message to the MS. MS receives a PACKET DOWNLINK ASSIGNMENT message instructing a single carrier assignment for downlink side and brings back it to the initial state (step 1).

SS sends a PACKET TIMESLOT RECONFIGURE message to the MS instructing a dual carrier configuration on both downlink and uplink side. SS starts to send downlink data and MS sends uplink data blocks. SS completes sending downlink data blocks and the MS completes sending uplink data blocks..

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

SS -> MS

IMMEDIATE ASSIGNMENT

Sent on PCH triggers the MS to assigned PDTCH. Carrier C1 is assigned.

2

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS.

A valid RRBP is indicated.

3

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges the previously received RLC data blocks.

4

MS

MS trigger an uplink data transfer of 1000 octets.

Step 2 to 3 are repeated until the Channel Request Description is included into the PACKET DONWLINK ACK/NACK

5

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Dual Carrier assignment”

Two carriers assigned for downlink and carrier 1 is assigned in uplink side.

See specific message contents.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence. USF Assigned with MCS-1. A valid RRBP is indicated.

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1.

8

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

9

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 1.

10

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to MS.

11

SS should check MS does not send any data on carrier 2

12

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2..

13

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Assignment of single carrier only”

Carrier 1 is assigned in downlink side.

14

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS.

A valid RRBP is indicated.

15

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data blocks.

16

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Dual Carrier assignment”

Two carriers assigned for downlink and carrier 2 is assigned in uplink side.

17

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF Assigned with MCS-1.

18

SS

SS should check MS does not send any data on carrier 1.

19

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

with MCS-1. A valid RRBP is indicated. USF Assigned with MCS-1.

20

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

21

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 2.

22

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2..

23

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Assignment of single carrier only”

Carrier 1 is assigned in downlink side.

24

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS on carrier 1. A valid RRBP is indicated.

25

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges the previously received RLC data blocks in carrier 1.

26

SS -> MS

PACKET TIMESLOT RECONFIGURE

Assignment type “Dual Carrier assignment”

Reconfigure downlink TBF from single carrier to DLDC configuration. Establish uplink TBF on carrier 1 and carrier 2. USF specified for both carriers.

27

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN with MCS-1. USF assigned to MS.

A valid RRBP is indicated.

28

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

29

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 1 in step 27.

30

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

USF assigned to MS.

31

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

32

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 1.

33

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN with MCS-1. USF assigned to MS.

A valid RRBP is indicated.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

USF assigned to MS. FBI bit set to ‘1’ and valid RRBP field

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

37

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 2. Acknowledges receipt of the downlink data block sent on step 31. In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

38

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2.

39

{Completion of uplink }

Specific Message Contents

PACKET TIMESLOT RECONFIGURE message in step 4:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

DL_TFI assigned in Step 1

01

Message escape for Downlink Dual Carrier, BTTI using FANR, EGPRS 2, RTTI

EGPRS Channel Coding Command 

0000 (MCS-1)

<RESEGMENT 

1

Assignment Info

Assignment Info Struct

Assignment Type

10 (Dual Carrier Assignment)

Carrier ID

0 (carrier 1)

0|1 <DOWNLINK EGPRS Window Size>

0 (Not present)

0|1 <UPLINK EGPRS Window Size>

0 (Not present)

0

BTTI mode

<TIMESLOT ALLOCATION_C1>

1

0 | 1 <TIMESLOT ALLOCATION_C2>

1 (new assignment)

10

Optimized Dual Carrier frequency parameters used

Dual Carrier Frequency Parameters

Dual Carrier Frequency Parameters IE

TSC

arbitrarily chosen

0 | 1 < Uplink Control Timeslot C1>

0 (Not present)

0 | 1 < Uplink Control Timeslot C2>

0 (Not present)

0 | 1 < PFI of downlink TBF >

0 (Not present)

0 | 1 < UPLINK_RLC_MODE >

0 (Not present)

0 | 1 < NPM Transfer Time) >

0 (Not present)

0

Fast Ack/Nack Reporting not activated

< Uplink EGPRS Level>

00 (EGPRS)

< Downlink EGPRS Level >

00 (EGPRS)

0 | 1 < Pulse Format>

0 (Not present)

< padding bits >

58b.1.5a Single Carrier Downlink TBF with No Uplink TBF/ Downlink reconfigured to DLMC TBF/ Uplink TBF established

58b.1.5a.1 Conformance requirement

If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may:

– provide new frequency parameters for all newly assigned and existing carriers, or

– provide new frequency parameters for all newly assigned carriers, modify the frequency parameters for a subset of the existing carriers and leave the frequency parameters for the remaining existing carriers unchanged. In a Downlink Dual Carrier configuration, one or more PDCHs are assigned to a single mobile station on each of two different radio frequency channels. In a DLMC configuration, one or more PDCHs are assigned to a single mobile station on one or more of the uplink radio frequency channels that correspond to the downlink radio frequency channels assigned for the DLMC configuration. A mobile station with a Downlink Dual Carrier configuration shall not be allocated radio blocks on more than one radio frequency channels during any given radio block period.

3GPP TS 44.060; subclause 5.5.1.7 and 8.1.1.1

58b.1.5a.2 Test purpose

To verify:

The MS is able to change from Single Carrier downlink TBF (no uplink TBF in process) to operate a DLMC TBF:
– new (additional resources) frequency parameters can be allocated to both carriers
– when frequency parameters are allocated for only one carrier the other carrier remain unchanged.

58b.1.5a.3. Method of test

Initial Conditions

System Simulator:

1 cell, EGPRS supported, Downlink DLMC supported.

Mobile Station:

Support for DLMC indicated in MS Radio Access Capabilities IE.

The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, and PDP context 2 activated.

Specific PICS Statements

PIXIT Statements

Test Procedure

MS receives an IMMEDIATE ASSIGNMENT message on its PCH allocating resources for carrier 1. SS transmits downlink RLC data blocks. MS responds by sending a PACKET DOWNLINK ACK/NACK. An uplink data transfer is triggered, the MS insert the Channel Request Description in a PDAN and the SS sends a PACKET TIMESLOT RECONFIGURE message to the MS instructing a DLMC Downlink configuration and single carrier on the uplink side (carrier 1). SS starts to send downlink data and MS sends uplink data blocks. SS sends ACK/NACK message to the MS. MS receives a PACKET DOWNLINK ASSIGNMENT message instructing a single carrier assignment for downlink side and brings back it to the initial state (step 1).

SS sends another PACKET TIMESLOT RECONFIGURE message to the MS instructing a DLMC configuration on downlink side and single carrier on the uplink side (carrier 2). SS starts to send downlink data and MS sends uplink data blocks. SS sends ACK/NACK message to the MS. MS receives a PACKET DOWNLINK ASSIGNMENT message instructing a single carrier assignment for downlink side and brings back it to the initial state (step 1).

SS sends a PACKET TIMESLOT RECONFIGURE message to the MS instructing a dual carrier configuration on both downlink and uplink side. SS starts to send downlink data and MS sends uplink data blocks. SS completes sending downlink data blocks and the MS completes sending uplink data blocks.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

SS -> MS

IMMEDIATE ASSIGNMENT

Sent on PCH triggers the MS to assigned PDTCH. Carrier C1 is assigned.

2

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS.

A valid RRBP is indicated.

3

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges the previously received RLC data blocks.

4

MS

MS trigger an uplink data transfer of 1000 octets.

Step 2 to 3 are repeated until the Channel Request Description is included into the PACKET DONWLINK ACK/NACK

5

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “DLMC assignment”

Two carriers assigned for downlink and carrier 1 is assigned in uplink side.

See specific message contents.

6

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence. USF Assigned with MCS-1. A valid RRBP is indicated.

7

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

Send on same Radio Block as Data Block Send on Carrier 1 with MCS-1.

8

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

9

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 1.

10

SS -> MS

PACKET DOWNLINK DUMMY CONTROL BLOCK

Sent on the PACCH of the PDCH assigned on carrier 2, containing USF assigned to MS.

11

SS should check MS does not send any data on carrier 2

12

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2..

13

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Assignment of single carrier only”

Carrier 1 is assigned in downlink side.

14

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS.

A valid RRBP is indicated.

15

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

MS acknowledges the previously received RLC data blocks.

16

SS -> MS

PACKET TIMESLOT RECONFIGURE

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Dual Carrier assignment”

Two carriers assigned for downlink and carrier 2 is assigned in uplink side.

17

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN. USF Assigned with MCS-1.

18

SS

SS should check MS does not send any data on carrier 1.

19

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

with MCS-1. A valid RRBP is indicated. USF Assigned with MCS-1.

20

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

21

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 2.

22

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2..

23

SS -> MS

PACKET DOWNLINK ASSIGNMENT

Sent on PACCH of the PDTCH addressing the MS assigned in step 1. Assignment type “Assignment of single carrier only”

Carrier 1 is assigned in downlink side.

24

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

Sent on assigned PDCH with MCS-1 assigned to the MS on carrier 1. A valid RRBP is indicated.

25

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges the previously received RLC data blocks in carrier 1.

26

SS -> MS

PACKET TIMESLOT RECONFIGURE

Assignment type “DLMC”

Reconfigure downlink TBF from single carrier to DLMC configuration. Establish uplink TBF on carrier 1 and carrier 2. USF specified for both carriers.

27

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN with MCS-1. USF assigned to MS.

A valid RRBP is indicated.

28

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

29

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 1 in step 27.

30

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN

USF assigned to MS.

31

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

32

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 1.

33

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 2 with next in sequence BSN with MCS-1. USF assigned to MS.

A valid RRBP is indicated.

34

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 2.

SS verifies that the correct BSN is received and the correct MCS is used.

35

SS -> MS

EGPRS DOWNLINK RLC DATA BLOCK

On carrier 1 with next in sequence BSN

USF assigned to MS. FBI bit set to ‘1’ and valid RRBP field

36

MS -> SS

EGPRS UPLINK RLC DATA BLOCK

Received on the assigned PDTCH on carrier 1.

SS verifies that the correct BSN is received and the correct MCS is used.

37

MS -> SS

EGPRS PACKET DOWNLINK ACK/NACK

In the uplink block specified by the RRBP field, MS acknowledges receiving all the data blocks on carrier 2. Acknowledges receipt of the downlink data block sent on step 31. In the uplink block specified by the RRBP field. Final Ack Indicator bit set to ‘1’ .

38

SS -> MS

PACKET UPLINK ACK/NACK

SS acknowledges RLC data block received on carrier 2.

39

{Completion of uplink }

Specific Message Contents

PACKET TIMESLOT RECONFIGURE message in step 5:

Information Element

value/ remark

MESSAGE_TYPE

0 00111

PAGE_MODE

00 Normal Paging

GLOBAL_TFI

UL_TFI assigned in Step 1

10

escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI

DOWNLINK_RLC_MODE

0

CONTROL_ACK

0

1 < UFPS : < UFPS struct >

1st UFPS struct

| 01

Existing UFPS remains unchanged (no information provided) existing carrier 1

1 < UFPS : < UFPS struct >

2st UFPS struct

| 10

Existing UFPS changed/new UFPS provided

Arbitrarily chosen for Carrier 2

DLMC Measurement Type

0

< LINK_QUALITY_MEASUREMENT_MODE

00

Carrier for Interference Measurements

0

Global Packet Timing advance

– {0|1 <TIMING_ADVANCE_VALUE>}

1 (timing advance value)

– TIMING_ADVANCE_VALUE

30 bit periods

Packet Extended Timing Advance

0

PTCCH_CARRIER

0

CONTROL_ACK

0

PDAN Coding

0

Extended SNS

0

BEP_PERIOD2

0

PFI of downlink TBF

0

Downlink NPM Transfer Time

0

indicates Fast Ack/Nack Reporting is activated for downlink TBF

0

Downlink EGPRS Level

No change

Indication of Upper Layer PDU Start for RLC UM

0

EGPRS Packet Downlink Ack/Nack Type 3 Support

0

EGPRS Channel Coding Command

0 MCS1

RESEGMENT

0

1 < DLMC UL Carrier struct >

1st DLMC UL struct

| 10

Assigned carrier modified or new carrier assigned Carrier 2 Arbitrarily chosen value’s for Carrier 2

UPLINK EGPRS Window Size 

0

UPLINK_TFI_ASSIGNMENT

PFI of uplink TBF

0

UPLINK_RLC_MODE

0

Uplink NPM Transfer Time

0

indicates that FANR is activated

0

Uplink EGPRS Level

default

Pulse Format

0

Enhanced Flexible Timeslot Assignment

0

Uplink Control Timeslot

0