7.1.9 E-DCH MAC-is/i for Dual-Cell HSUPA

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

7.1.9.1 MAC-i/is multiplexing for Dual-Cell HSUPA

7.1.9.1.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is, DC-HSDPA and DC-HSUPA

7.1.9.1.2 Conformance Requirement

From 25.321 clause 9.1.5:

When MAC-i/is is configured, there are two MAC sublayers, MAC-i and MAC-is. MAC-is sits on top of MAC-i and receives PDUs directly from MAC-d. When MAC-i/is is configured, a MAC PDU for E-DCH consists of one MAC-i header and one or more MAC-is PDUs. Each MAC-is PDU consists of one or more MAC-is SDUs belonging to the same logical channel. Each MAC-is SDU equals a complete or a segment of a MAC-d PDU. The MAC-is SDUs can have different sizes. The LCH-ID and L fields are repeated per MAC-is SDU. The TSN and SS fields are repeated per MAC-is PDU. Multiple MAC-is PDUs from multiple logical channels, but only one MAC-i PDU can be transmitted in a TTI. In case sufficient space is left in the E-DCH transport block or if Scheduling Information needs to be transmitted, an SI will be included at the end of the MAC-i PDU (see subclause 9.2.4.2).

[…]

From 25.321 clause 4.2.3.6:

– Multiplexing and TSN setting:
The multiplexing and TSN setting entity is responsible for concatenating multiple MAC-d PDUs into MAC-is PDUs, and to multiplex one or multiple MAC-is PDUs into a single MAC-i PDU, or, when more than one uplink frequency is activated, one or two MAC-i PDUs, to be transmitted in the next TTI, as instructed by the E-TFC selection function. It is also responsible for managing and setting the TSN per logical channel for each MAC-is PDU.

[…]

From 25.321 clause 11.8.1.2.1:

When one uplink frequency is configured, after each MAC-es PDU or MAC-is PDU is multiplexed:

– increment CURRENT_TSN by 1;

– if CURRENT_TSN > 63:

– set CURRENT_TSN = 0.

When more than one uplink frequency is configured, after each MAC-is PDU is multiplexed:

– increment CURRENT_TSN by 1;

– if CURRENT_TSN > 16383:

– set CURRENT_TSN = 0.

[…]

From 25.331 clause 8.6.5.18:

1> if the IE "E-DCH MAC-d flow multiplexing list" is included:

2> only multiplex MAC-d PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from E-DCH MAC-d flows with which multiplexing in the same MAC-e or MAC-i PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list".

Reference(s)

TS 25.321 clause 9.1.5, 4.2.3.6, 11.8.1.2.1, TS 25.331 clause 8.6.5.18

7.1.9.1.3 Test purpose

1. To verify that the UE, when Dual-Cell E-DCH is configured, multiplex multiple MAC-is PDUs into two MAC-i PDUs.

2. To verify that the UE, when Dual-Cell E-DCH is configured, use the extended TSN range (0 to 16383).

7.1.9.1.4 Method of test

Initial conditions

System Simulator:

2 cells –Cell 1/2 DC HSDPA and DC HSUPA cell(s) with Cell 1 (Serving HS.DSCH cell/Primary uplink frequency) and Cell 2 (Secondary serving HS.DSCH cell /Secondary uplink frequency) and Ciphering Off.

User Equipment:

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the Radio Bearers according to clause 6.11.4k.4 (Flexible RLC + MAC-i/is + MAC-ehs), but with downlink SRBs mapped to HS-DSCH instead of DCH for 2 PS RABs using condition A25c to configure Dual-Cell E-DCH operation.

The MAC-d flows are configured for scheduled transmissions. The following parameters are specific for this test case with the logical channel, transport channel and queue identities set to:

Logical Channel ID

MAC-d flow (UL)

Priority

Comment

7 (LCH1)

2

6

RB26

8 (LCH2)

3

7

RB27

Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the test case

The following parameters are specific for this test case.

Parameter

Value

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99) (FDD)

E-DCH MAC-d flow multiplexing list

Flow 2 = 00100000

Flow 3 = 00010000

See 25.331 10.3.5.1b

Reference E-TFCIs

11 and 125

Secondary uplink frequency is activated using HS-SCCH Order as specified in the TS 25.212, clause 4.6C.2.2.2.

The UE is placed into UE test loop mode 1 with the UL SDU size for LCH 1 and LCH2 set to 40 octets.

Test procedure

a) The SS has not issued any scheduling grant for E-DCH to the UE

b) The SS transmits one RLC SDU of size 40 bytes on LCH1

c) The SS transmits one RLC SDU of size 40 bytes on LCH2

d) The SS waits for UE to send a SI indicating that all data received in steps b and c is available for transmission.

e) The SS issues an absolute grant on both the uplink frequency that allows the UE to loopback the received data (signalling value 8 )

f) The SS checks that the UE returns one RLC SDU for LCH1 and one RLC SDU for LCH2 in 2 MAC-i PDUs in the same TTI. The SS checks the TSN value for each LCH. For the first iteration the TSN value shall be ‘0’. For each successive iteration the UE shall increment the TSN value by 1 modulo 16383.

g) The SS removes the scheduling grant for E-DCH for the UE.

h) The SS repeats step b to step g 65 times.

NOTE: The UE may send an SI after step 1 or step 2 indicating that only part of the data is available for transmission. These SIs will be ignored by the SS.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

1 RLC SDU on LCH 1

2

1 RLC SDU on LCH 2

3

SI

SS waits until UE sends a SI indicating that all data sent in steps 1 and 2 are available for transmission in uplink. This can be verified from the indicated fraction of data on LCH1 and LCH2. The SS ignores any SI indicating that only part of the data sent in step 1 and 2 is available for transmission in uplink.

4

Absolute grant

Absolute grant allowing UE to transmit all data on both E-DCH (signalling value 8 )

5

2 MAC-i PDUs

Two MAC-i PDUs shall be received in the same TTI containing one RLC PDU on LCH 1 and one RLC PDU on LCH 2.

SS check the TSN value for MAC-I PDU.

6

SS removes the scheduling grant

7

SS

Repeat steps 1 to 65 times

Specific Message Contents

None

7.1.9.1.5 Test requirements

1. At step 5 the SS shall receive 2 MAC-i PDU in the same TTI containing one RLC PDU on LCH1 and one RLC PDU on LCH2.

2. At step 5 the TSN value for both MAC-I PDUs shall be:

– Frist iteration: ‘0’;

– Iteration 2 to 65: ‘1’ to ‘64’

7.1.9.2 Happy bit setting and SI handling for Dual-Cell HSUPA

7.1.9.2.1 Definition and applicability

All UEs which support Dual-Cell HSDPA and Dual-Cell E-DCH.

7.1.9.2.2 Conformance requirement

The happy bit is a single bit field that is passed from MAC to the physical layer for inclusion on the E-DPCCH. This field takes two values, "Not Happy" and "Happy" indicating respectively whether the UE could use more resources or not. The setting of the Happy Bit is defined in subclause [TS 25.321] 11.8.1.5.

A happy bit is reported on each of the Activated Uplink Frequencies.

[…]

The Happy Bit is included on the E-DPCCH for every E-DCH transmission on each Activated Uplink Frequency. E-DCH transmissions shall not be triggered specifically to allow the transmission of the happy bit.

RRC configures MAC with the duration Happy_Bit_Delay_Condition, over which to evaluate the current grant relative to the TEBS after application of the E-TFC selection procedure described in subclause 11.8.1.4.

For every E-DCH transmission and for each Activated Uplink Frequency, the Happy Bit on a frequency shall be set to "unhappy" if the three following criteria are met on that frequency:

1) UE is transmitting as much scheduled data as allowed by the current Serving_Grant in E-TFC selection on that frequency; and

2) UE has enough power available to transmit at higher data rate on that frequency; and

3) Based on the same power offset as the one selected in E-TFC selection to transmit data in the same TTI as the Happy Bit, TEBS would require more than Happy_Bit_Delay_Condition ms to be transmitted with the current Serving_Grant × the ratio of active processes to the total number of processes.

If there is more than one Activated Uplink Frequency, based on the same power offset as the one selected in E-TFC selection on each Activated Uplink Frequency to transmit data in the same TTI as the Happy Bit, TEBS would require more than Happy_Bit_Delay_Condition ms to be transmitted with the current (Serving_Grant × the ratio of active processes to the total number of processes on the Primary Uplink Frequency) plus (Serving_Grant × the ratio of active processes to the total number of processes on the Secondary Uplink Frequency).

The first criteria is always true for a deactivated process and the ratio of the third criteria is always 1 for 10ms TTI.

Otherwise, the Happy Bit shall be set to "happy". When the UE has more than one Activated Uplink Frequency, the power used to assess whether the UE has enough power to transmit at a higher data rate on one Activated Uplink Frequency is based on the maximum remaining power allowed for E-DCH transmission on that Activated Uplink Frequency as determined by E-TFC selection described in subclause 11.8.1.4 and in [12].

In order to assess if it has enough power available to transmit at higher data rate on an Activated Uplink Frequency, the UE shall:

1) If MAC-i/is is configured, identify the E-TFC that has a transport block size at least 32 bits larger than the transport block size of the E-TFC selected for transmission in the same TTI as the Happy Bit. Otherwise, identify the E-TFC that has a transport block size at least x bits larger than the transport block size of the E-TFC selected for transmission in the same TTI as the Happy Bit, where x is the smallest RLC PDU size configured among all the logical channels that do not belong to non-scheduled MAC-d flows and which have data in the buffer; and

2) Based on the same power offset as the one selected in E-TFC selection to transmit data in the same TTI as the Happy Bit, check that the identified E-TFC is supported i.e. not blocked.

[…]

The Scheduling Information is located at the end of the MAC-e or MAC-i PDU and is used to provide the serving Node B with a better view of the amount of system resources needed by the UE and the amount of resources it can actually make use of. The transmission of this information will be initiated due to the quantization of the transport block sizes that can be supported or based on the triggers defined in subclause 11.8.1.6. When a Scheduling Information is transmitted, its contents shall always be updated in new transmissions with the buffer status after application of the E-TFC selection procedure described in subclause 11.8.1.4. The logical channels for which a non-scheduled grant is configured shall never be taken into account when putting together this information. In addition, the RRC may restrict applicability for logical channels for which no non-scheduled grant was configured.

A Scheduling Information is reported independently on each of the Activated Uplink Frequencies.

This information includes the following fields:

– Highest priority Logical channel ID (HLID):
The HLID field identifies unambiguously the highest priority logical channel with available data. If multiple logical channels exist with the highest priority, the one corresponding to the highest buffer occupancy will be reported. The length of the HLID is 4 bits. In case the TEBS is indicating index 0 (0 byte), the HLID shall indicate the value "0000".

– Fields related to amount of available data:

– Total E-DCH Buffer Status (TEBS):
The TEBS field identifies the total amount of data available across all logical channels for which reporting has been requested by the RRC and indicates the amount of data in number of bytes that is available for transmission and retransmission in RLC layer. If MAC-i/is is configured, it also includes the amount of data that is available for transmission in the MAC-i/is segmentation entity. When MAC is connected to an AM RLC entity, control PDUs to be transmitted and RLC PDUs outside the RLC Tx window shall also be included in the TEBS. RLC PDUs that have been transmitted but not negatively acknowledged by the peer entity shall not be included in the TEBS.

The length of this field is 5 bits. The values taken by TEBS are shown in Table 9.2.5.3.2.1.

Table 9.2.5.3.2-1: TEBS Values

Index

TEBS Value (bytes)

0

TEBS = 0

1

0 < TEBS ≤ 10

2

10 < TEBS ≤ 14

3

14 < TEBS ≤ 18

4

18 < TEBS ≤ 24

5

24 < TEBS ≤ 32

6

32 < TEBS ≤ 42

7

42 < TEBS ≤ 55

8

55 < TEBS ≤ 73

9

73 < TEBS ≤ 97

10

97 < TEBS ≤ 129

11

129 < TEBS ≤ 171

12

171 < TEBS ≤ 228

13

228 < TEBS ≤ 302

14

302 < TEBS ≤ 401

15

401 < TEBS ≤ 533

16

533 < TEBS ≤ 708

17

708 < TEBS ≤ 940

18

940 < TEBS ≤ 1248

19

1248 < TEBS ≤ 1658

20

1658 < TEBS ≤ 2202

21

2202 < TEBS ≤ 2925

22

2925 < TEBS ≤ 3884

23

3884 < TEBS ≤ 5160

24

5160 < TEBS ≤ 6853

25

6853 < TEBS ≤ 9103

26

9103 < TEBS ≤ 12092

27

12092 < TEBS ≤ 16062

28

16062 < TEBS ≤ 21335

29

21335 < TEBS ≤ 28339

30

28339 < TEBS ≤ 37642

31

37642 < TEBS
  • Highest priority Logical channel Buffer Status (HLBS):
    The HLBS field indicates the amount of data available from the logical channel identified by HLID, relative to the highest value of the buffer size range reported by TEBS when the reported TEBS index is not 31, and relative to 50000 bytes when the reported TEBS index is 31. The length of HLBS is 4 bits. The values taken by HLBS are shown in table 9.2.5.3.2.2. In case the TEBS field is indicating index 0 (0 byte), the HLBS field shall indicate index 0.

Table 9.2.5.3.2-2: HLBS Values

Index

HLBS values (%)

0

0 < HLBS ≤ 4

1

4 < HLBS ≤ 6

2

6 < HLBS ≤ 8

3

8 < HLBS ≤ 10

4

10 < HLBS ≤ 12

5

12 < HLBS ≤ 14

6

14 < HLBS ≤ 17

7

17 < HLBS ≤ 21

8

21 < HLBS ≤ 25

9

25 < HLBS ≤ 31

10

31 < HLBS ≤ 37

11

37 < HLBS ≤ 45

12

45 < HLBS ≤ 55

13

55 < HLBS ≤ 68

14

68 < HLBS ≤ 82

15

82 < HLBS

– UE Power Headroom (UPH):
The UPH field of a frequency indicates the ratio of the maximum UE transmission power and the corresponding DPCCH code power of that frequency defined in [17]. The length of UPH is 5 bits.

The Scheduling Information message is represented in figure 9.2.5.3.2-1 where for each field, the LSB is the rightmost bit in the figure and the MSB is the leftmost bit.

Figure 9.2.5.3.2-1: Scheduling Information format

Reference(s)

TS 25.321 clause 9.2.5.3.1, 11.8.1.5 and 9.2.5.3.2

7.1.9.2.3 Test purpose

1 To verify that UE makes the correct settings of happy bit for the primary and secondary frequency.

2. To verify that UE makes the correct settings of scheduling information for the primary and secondary frequency.

7.1.9.2.4 Method of test

Initial conditions

System Simulator:

2 cell – Cell 1/2 DC HSDPA and DC HSUPA cell(s) with Cell 1 (Serving HS-DSCH cell/Primary uplink frequency) and 2 (Secondary serving HS-DSCH/Secondary uplink frequency), Ciphering Off.

User Equipment:

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the Radio Bearers according to clause 6.11.4k.4 (Flexible RLC + MAC-i/is + MAC-ehs), but with downlink SRBs mapped to HS-DSCH instead of DCH for 1 PS RAB using condition A25c to configure Dual-Cell E-DCH operation.

The MAC-d flows are configured for scheduled transmissions. The following parameters are specific for this test case with the logical channel, transport channel and queue identities set to:

Logical Channel ID

MAC-d flow (UL)

Priority

Comment

7

2

6

RB26

Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the test case

The following parameters are specific for this test case

Parameter

Value

Happy bit delay condition

10 ms (see 25.331 10.3.6.98)

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99) (FDD)

Reference E-TFCIs

11 and 125

Secondary uplink frequency is activated using HS-SCCH Order as specified in the TS 25.212, clause 4.6C.2.2.2.

The UE is placed into UE test loop mode 1 with the UL RLC SDU size set to 39 octets.

Test procedure

In this test procedure the UE is configured with one logical channel with Id 7.

a) The SS has not issued any scheduling grant for E-DCH to the UE.

b) The SS transmits 5 RLC SDUs of size 39 bytes to the UE

c) The SS waits for the UE to send a SI on each Activated Uplink Frequency indicating that all data received in step b is available for transmission

d) The SS issues an absolute grant on each Activated Uplink Frequencies allowing the UE to transmit 3 RLC SDUs of size 39 bytes per TTI (signalling value 7 for FDD). This enables the UE to loopback all the received data.

e) The SS waits until all data is received in uplink and checks the happy bit on both E-DPCCH

f) The SS removes the scheduling grant for the UE (Signalling value 1 for FDD).

g) The SS transmits 200 RLC SDUs of size 39 bytes to the UE.

h) The SS waits for the UE to send a SI indicating that all data received in step g is available for transmission

i) The SS issues an absolute grant on both Activated Uplink Frequencies allowing the UE to transmit 1 RLC SDU of size 39 bytes per TTI on both uplink frequency (signalling value 3 for FDD).

j) The SS waits until data is received in uplink and checks the happy bit on both E-DPCCH

k) The SS issues an absolute grant allowing UE to transmit the remaining RLC SDUs (signalling value 31 for FDD)

l) The SS waits until all data has been received in uplink and checks the happy bit on both E-DPCCH

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

5 RLC SDUs

2

à

SI

Scheduling Information on each Activated Uplink Frequency indicating that data received in step 1 is available for transmission

3

ß

Absolute grants

Absolute grant on each Activated Uplink Frequency allowing the UE to transmit at least 3 RLC SDUs of size 39 bytes per TTI. Signalling value 7.

Note : Grant on each Activated uplink frequency is sent on a specific activation time (i.e

ACT_CFN_Step3 = (8 + Current CFN) MOD 256)

4

à

Data, happy bit

Happy bit on both E-DPCCH shall be set to happy in the first TTI containing data.

5

ß

Removal of absolute grant

Signalling value 1 on each Activated Uplink Frequency

6

ß

200 RLC SDUs

7

à

SI

Scheduling Information on each Activated Uplink Frequency indicating that data received in step 6 is available for transmission

8

ß

Absolute grants

Absolute grant on each Activated Uplink Frequency allowing the UE to transmit 1 RLC SDU of size 39 bytes per TTI. Signalling value 3.

Grant on each Activated uplink frequency is sent on a specific activation time (i.e ACT_CFN_Step8 = (8 + Current CFN) MOD 256)

9

à

Data, happy bit

Happy bit on both E-DPCCH shall be set to unhappy in the first TTI containing data.

10

ß

Absolute grants

Absolute grant on each Activated Uplink Frequency allowing the UE to transmit remaining RLC SDUs. Signalling value 31.

Grant on each Activated uplink frequency is sent on a specific activation time (i.e

ACT_CFN_Step10 = (8 + ACT_CFN_Step8 )

Note : Step 10 is pre configured before step 9 to ensure activation times are co-ordinated.

11

à

Data, happy bit

Happy bit on both E-DPCCH shall be set to happy in the first TTI containing data.

Specific Message Contents

None

7.1.9.2.5 Test requirements

1. In step 2 the SS shall receive a Scheduling Information on both Activated Uplink Frequencies indicating a total E-DCH Buffer Status (TEBS) Index > 0

2. In step 4 the SS shall for each Activated Uplink Frequency receive data and happy bit information. For each E-DPCCH the happy bit shall be set to happy in the first TTI containing data.

3. In step 9 the SS shall receive data and the happy bit from both E-DPCCH shall be set to unhappy in the first TTI containing data.

4. In step 11 the SS shall receive data and the happy bit from both E-DPCCH shall be set to happy in the first TTI containing data.

7.1.9.3 Void

7.1.9.4 Void

7.1.9.5 Deactivation and activation of secondary uplink frequency using HS-SCCH orders

7.1.9.5.1 Definition and applicability

This test apply for Release 9 and later releases for the FDD UE that supports HSDPA and Dual Cell E-DCH.

7.1.9.5.2 Conformance requirement

If the UE receives:

– a HS-SCCH order for secondary uplink frequency activation/deactivation

it shall:

1> if the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to TRUE and the HS-SCCH order is to activate the secondary uplink frequency:

2> consider the secondary uplink frequency as activated;

2> initiate the physical dedicated channel establishment procedure on the downlink frequency associated with the secondary uplink frequency according to the stored configuration;

2> configure the serving grant on the secondary uplink frequency in accordance with the IE "Serving Grant Value" configuration.

1> if the HS-SCCH order is to deactivate the secondary uplink frequency:

2> consider the secondary uplink frequency as not activated.

1> determine the value for the SECONDARY_CELL_E_DCH_TRANSMISSION and take the corresponding actions as described in subclause 8.5.58.

…

Whenever the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to TRUE, and the secondary uplink frequency is an activated uplink frequency, the UE shall:

1> perform E_AGCH reception procedures on the secondary serving E-DCH cell according to the stored E_AGCH configuration as stated in:

2> subclause 8.6.3.14 for the IE "Primary E-RNTI" and the IE "Secondary E-RNTI" for secondary serving E-DCH cell.

1> perform E-HICH reception procedures for all radio links in the secondary E-DCH active set;

1> perform E-RGCH reception procedures for all radio links in the secondary E-DCH active set for which an E-RGCH configuration has been provided;

1> perform uplink DPCCH transmission on the secondary uplink frequency according to the stored uplink DPCH info configuration as stated in:

2> subclause 8.6.6.6 for the IE "Uplink DPCH info";

2> subclause 8.6.6.49 for the IE "Uplink Secondary Cell Info FDD".

1> perform E-DPCCH transmission procedures on the secondary uplink frequency according to the stored E-DPCCH configuration as stated in:

2> subclause 8.6.6.37 for the IE "E-DPCCH Info";

2> subclause 8.6.6.49 for the IE "Uplink Secondary Cell Info FDD".

1> perform E-DPDCH transmission procedures on the secondary uplink frequency according to the stored E-DPDCH configuration as stated in:

2> subclause 8.6.5.16 for the IE "E-DCH Transmission Time Interval";

2> subclause 8.6.5.17 for the IE "HARQ info for E-DCH";

2> subclause 8.6.6.37 for the IE "E-DPDCH Info";

2> subclause 8.6.6.49 for the IE "Uplink Secondary Cell Info FDD".

1> inclusion of MAC-d PDU’s in a MAC-i PDU for logical channels on the secondary uplink frequency shall:

2> be performed in accordance with the received scheduling grant on E-AGCH/E-RGCH (see [15]) on the downlink frequency associated with the secondary uplink frequency; and

2> obey the scheduling restrictions as specified for scheduled transmissions (see subclause 8.6.6.37).

Whenever the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to FALSE, or the secondary uplink frequency is not an activated uplink frequency, the UE shall:

1> not perform F-DPCH, E-AGCH, E-HICH and E-RGCH reception procedures on the downlink frequency associated with the secondary uplink frequency;

  1. not perform DPCCH, E-DPCCH and E-DPDCH transmission procedures on the secondary uplink frequency

…

If the UE is configured with multiple uplink frequencies, HS-SCCH ordered deactivation or activation of the secondary serving HS-DSCH cell(s) is applied by the UE 18 slots after the end of the HS-SCCH subframe delivering the order, and any transient behaviour related to this change should take place before this point in time. If:

  • the activation statuses of all secondary serving HS-DSCH cells in a frequency band (as defined in [7]) remain unaffected by the HS-SCCH ordered deactivation or activation and the serving HS-DSCH cell is not configured in this band or
  • the activation statuses of all secondary serving HS-DSCH cells and the secondary uplink frequency in a frequency band remain unaffected by the HS-SCCH ordered deactivation or activation and the serving HS-DSCH cell is configured in this band

…

Figure 34 shows the timing offset between the uplink DPCH, the HS-PDSCH and the HS-DPCCH at the UE. An HS-DPCCH sub-frame starts chips after the start of an uplink DPCH frame that corresponds to the DL DPCH or F-DPCH frame from the HS-DSCH serving cell containing the beginning of the related HS-PDSCH subframe with m calculated as

m = (TTX_diff /256 ) + 101

where TTX_diff is the difference in chips (TTX_diff =0, 256, ….., 38144), between

– the transmit timing of the start of the related HS-PDSCH subframe (see sub-clauses 7.8 and 7.1)

and

– the transmit timing of the start of the downlink DPCH or F-DPCH frame from the HS-DSCH serving cell that contains the beginning of the HS-PDSCH subframe (see sub-clause 7.1).

At any one time, m therefore takes one of a set of five possible values according to the transmission timing of HS-DSCH sub-frame timings relative to the DPCH or F-DPCH frame boundary. The UE and Node B shall only update the set of values of m in connection to UTRAN reconfiguration of downlink timing.

More information about uplink timing adjustments can be found in [5].

Figure 34: Timing structure at the UE for HS-DPCCH control signalling

…

Figure 35 shows the relative timing between the HS-SCCH and the associated HS-PDSCH for one HS-DSCH sub-frame. The HS-PDSCH starts HS-PDSCH = 2Tslot = 5120 chips after the start of the HS-SCCH.

Figure 35: Timing relation between the HS-SCCH and the associated HS-PDSCH

Reference

3GPP TS 25.331 clause 8.5.58, 8.5.59. TS 25.214 clause 6A.1. TS 25.211 clause 7.7, 7.8.

7.1.9.5.3 Test purpose

1. To verify that UE deactivates the secondary uplink frequency when deactivation command is received on the HS-SCCH.

2. To verify that UE activates the secondary uplink frequency when activation command is received on the HS-SCCH.

7.1.9.5.4 Method of test

Initial Condition

System Simulator:

2 cells –Cell 1/2 DC HSDPA and DC HSUPA cell(s) with Cell 1 (Serving HS-DSCH cell/Primary uplink frequency) and Cell 2 (Secondary serving HS-DSCH cell /Secondary uplink frequency) and Ciphering Off.

UE:

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the Radio Bearers according to clause 6.11.4k.4 (Flexible RLC + MAC-i/is + MAC-ehs), but with downlink SRBs mapped to HS-DSCH instead of DCH for 1 PS RAB using condition A25c to configure Dual-Cell E-DCH operation.

The UE is in secondary uplink frequency deactivation state after the establishment of the secondary uplink carrier.

UE is configured with DC-HSDPA in downlink and Flexible RLC, MAC-i/is in uplink.

The MAC-d flows are configured for scheduled transmissions. The following parameters are specific for this test case with the logical channel, transport channel and queue identities set to:

Logical Channel ID

MAC-d flow (UL)

Priority

Comment

7 (LCH1)

2

6

RB26

Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the test case

The following parameters are specific for this test case.

Parameter

Value

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99) (FDD)

Reference E-TFCIs

11 and 125

Secondary uplink frequency is activated using HS-SCCH Order as specified in the TS 25.212, clause 4.6C.2.2.2.

The UE is placed into UE test loop mode 1 with the UL SDU size for LCH 1 set to 40 octets.

Test Procedure

The UE is configured with one logical channel. The logical channel is mapped to MAC-d flow 2.

  1. The SS transmits an activation HS-SCCH order to the UE to activate secondary uplink carrier.
  2. The UE shall respond with ACK on HS-DPCCH. SS check the ACK on HS-DPCCH.
  3. The UE is in secondary uplink frequency activation state. SS should sent zero absolute grant to primary uplink carrier to restrict the data transfer on primary uplink carrier
  4. The SS transmits one RLC SDU of size 40 bytes on LCH1
  5. The SS waits for an SI to be received that indicates that data is available on LCH1
  6. SS should send absolute grant on secondary uplink carrier allowing UE to transmit on secondary E-DCH(Signalling value 4)
  7. The SS waits until data is received on the secondary uplink carrier to check that the UE has activated the secondary uplink frequency.
  8. The SS transmits deactivation HS-SCCH order to the UE.
  9. The UE shall respond with ACK on HS-DPCCH. SS check the ACK on HS-DPCCH.
  10. The SS transmits one RLC SDU of size 40 bytes on LCH1
  11. The SS waits for an SI to be received that indicates that data is available on LCH1
  12. The data will not be received by the SS, if the UE has de-activated the secondary uplink frequency and there is one zero grant on primary carrier.

Expected sequence

Step

Direction

Message

Comment

UE

SS

1

HS-SCCH order(Activation Command)

The UE is in secondary uplink frequency deactivation state after the establishment of the secondary uplink frequency.

The HS-SCCH order is used to activate the secondary uplink frequency.

2

ACK

3

Zero absolute grant on primary carrier

Disable the uplink data transmitting on primary uplink carrier

4

1 RLC SDU on LCH 1

5

SI indicating data on LCH 1

6

Absolute grant on secondary uplink carrier allowing UE to transmit on secondary E-DCH

signalling value 4

7

MAC-i PDUs containing 1 RLC PDU on LCH 1

MAC-I PDU should be received on the secondary uplink carrier

8

HS-SCCH order(De-Activation Command)

9

ACK

10

1 RLC SDU on LCH 1

11

SI indicating data on LCH 1

SI should be received on the primary uplink carrier

12

SS check that no uplink data will be received during 10 TTIs

Specific Message Contents

HS-SCCH order

The following information is transmitted by means of the HS-SCCH order physical channel. The content of HS-SCCH order in this test case is specified in the TS 25.212, clause 4.6C.2.2.2.

– Order type (3 bits): 001

– Order (3 bits): 011(Activation) / 001(Deactvation)

– UE identity (16 bits): H-RNTI

7.1.9.5.4 Test requirement

At step 2 the UE shall transmit a HS-DPCCH ACK to respond the Activation Command.

At step 7 the UE shall transmit data to SS on the secondary uplink carrier.

At step 9 the UE shall transmit a HS-DPCCH ACK to respond the De-Activation Command.

After step 11 the UE should not send any data on the primary or secondary uplink carrier during the check time e.g. 10 TTIs.