7.1.6 E-DCH MAC-es/e

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.1.6.1 MAC-es/e multiplexing

7.1.6.1.1 MAC-es/e multiplexing without RRC restrictions

7.1.6.1.1.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.1.1.2 Conformance requirement

From 25.321 clause 9.1.5:

In the case of E-DCH there are two MAC sublayers, MAC-e and MAC-es. MAC-es sits on top of MAC-e and receives PDUs directly from MAC-d. MAC-es SDUs (i.e. MAC-d PDUs) of the same size, coming from a particular logical channel can be multiplexed together into a single MAC-es payload. To this payload is prepended the MAC-es header (see subclause 9.2.4.1). The number of PDUs, as well as the DDI value identifying the logical channel, the MAC-d flow and the MAC-es SDU size are included as part of the MAC-e header. 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-e PDU (see subclause 9.2.4.2). Multiple MAC-es PDUs, but only one MAC-e PDU can be transmitted in a TTI.

[…]

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 PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list".

[…]

Reference(s)

TS 25.321 clause 9.1.5, TS 25.331 clause 8.6.5.18

7.1.6.1.1.3 Test purpose

The purpose of this test case is to verify that the UE multiplexes data from different logical channels in the same TTI when no restriction on the multiplexing is configured by RRC.

7.1.6.1.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4d(FDD) /6.11.5.4.7.7(1.28Mcps TDD) using condition A15(FDD) /A14(1.28Mcps TDD) as specified in clause 9.1 of TS 34.108. The logical channel, transport channel and queue identities are set to:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the testcase

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)
T-WAIT	200 ms (see 25.331 10.3.6.103)( 1.28Mcps TDD)
E-DCH MAC-d flow multiplexing list	11111111 (See 25.331 10.3.5.1b) Note 1
Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

The UE is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB25 and RB17.

Test procedure

The UE is configured with two logical channels, LCH1 (with priority 1) and LCH2 (with priority 2). LCH1 is mapped to MAC-d flow 2 and LCH2 is mapped to MAC-d flow 3.

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

b) The SS transmits one SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

c) The SS transmits one SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

d) The SS waits for an SI to be received that indicates that data is available on both logical channels (can be identified from the content of the SI)

e) The SS issues an absolute grant that allows the UE to send with a high rate (signalling value 10, allowing a rate well above 2 SDUs/TTI)

f) The SS waits until data is received and verifies that data from the two LCHs is received in the same TTI

NOTE: The UE may send an SI after step 1 but this SI would only indicate data on LCH2. This SI will be ignored.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		1 RLC PDU on LCH 2
2	ß		1 RLC PDU on LCH 1
3	à		Potential SI indicating data on LCH 2	This SI is ignored by the SS
4	à		SI indicating data on LCH 1 and LCH 2	This can be verified from the indicated fraction of data on LCH1
5	ß		Absolute grant allowing UE to transmit on E-DCH	This grant must be sufficiently high to allow a rate corresponding to at least 2 RLC PDUs/TTI, signalling value 10
6	à		MAC e/es PDU containing 1 RLC PDU on LCH 1 and one RLC PDU on LCH 2

Specific Message Contents

None

7.1.6.1.1.5 Test requirements

1. After step 2 the SS shall receive an SI indicating that data is available on LCH 1 and LCH 2 but no RLC PDUs shall be received

2. In step 6, the SS shall receive 1 RLC PDU on LCH 1 and one RLC PDU on LCH 2 in the same TTI

7.1.6.1.2 MAC-es/e multiplexing with RRC restrictions

7.1.6.1.2.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.1.2.2 Conformance requirement

From 25.321 clause 9.1.5:

[…]

From 25.331 clause 8.6.5.18:

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

[…]

Reference(s)

TS 25.321 clause 9.1.5, TS 25.331 clause 8.6.5.18

7.1.6.1.2.3 Test purpose

The purpose of this test case is to verify that the UE does not multiplex data from different logical channels in the same TTI when the multiplexing has been restricted by RRC.

7.1.6.1.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4d(FDD) /6.11.5.4.7.7(1.28Mcps TDD) using condition A15(FDD) /A14(1.28Mcps TDD) as specified in clause 9.1 of TS 34.108.The logical channel, transport channel and queue identities are set to:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
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)
T-WAIT	200 ms (see 25.331 10.3.6.103)( 1.28Mcps TDD)
E-DCH MAC-d flow multiplexing list	00000000 (See 25.331 10.3.5.1b) Note 1
Note 1: This configuration means that no multiplexing is allowed

The UE is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB25 and RB17.

Test procedure

The UE is configured with two logical channels, LCH1 (with priority 1) and LCH2 (with priority 2). LCH1 is mapped to MAC-d flow 2 and LCH2 is mapped to MAC-d flow 3.

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

b) The SS transmits one SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

c) The SS transmits one SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

d) The SS waits for an SI to be received that indicates that data is available on both logical channels (can be identified from the content of the SI)

e) The SS issues an absolute grant that allows the UE to send with a high rate (signalling value 10, allowing rates well above 2 SDUs/TTI)

f) The SS waits until data is received and verifies that only data from LCH1 is received in the first TTI

g) The SS verifies that data from LCH2 is received (in a separate TTI from the data from LCH1)

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		1 RLC PDU on LCH 2
2	ß		1 RLC PDU on LCH 1
3	à		Potential SI indicating data on LCH 2	This SI is ignored by the SS
4	à		SI indicating data on LCH 1 and LCH 2	This can be verified from the indicated fraction of data on LCH1
5	ß		Absolute grant allowing UE to transmit on E-DCH	This grant must be sufficiently high to allow a rate corresponding to at least 2 RLC PDUs/TTI, signalling value 10
6	à		MAC e/es PDU containing 1 RLC PDU on LCH 1
7	à		MAC e/es PDU containing 1 RLC PDU on LCH 2

Specific Message Contents

None

7.1.6.1.2.5 Test requirements

1. After step 2 the SS shall receive an SI indicating that data is available on LCH 1 and LCH 2 but no RLC PDUs shall be received

2. In step 6, the SS shall receive 1 RLC PDU on LCH 1 but no data from LCH 2

3. In step 7, the SS shall receive 1 RLC PDU on LCH 2 but no data from LCH 1

7.1.6.1.3 Correct settings of MAC-es/e header fields

7.1.6.1.3.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.1.3.2 Conformance requirement

Extract from 25.321:

[…]

– Transmission Sequence Number (TSN):
The TSN field provides the transmission sequence number for the MAC-es PDU. This information is used for reordering purposes to support in-sequence delivery to higher layers. The length of the TSN field is 6 bits.

[…]

– For FDD: Data description indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d PDUs concatenated into the associated MAC-es PDU. The mapping between the DDI values and the logical channel ID, MAC-d flow and PDU size is provided by higher layers. The length of the DDI field is 6 bits. When, due to the quantization in the transport block sizes that can be supported or triggering of the Scheduling Information, the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 24 bits, the DDI value [111111] shall be appended at the end of the MAC-e header and a Scheduling Information shall be concatenated into this MAC-e PDU, where DDI value [111111] indicates that there is a Scheduling Information concatenated in this MAC-e PDU. Otherwise, if the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 18 bits, a Scheduling Information shall be concatenated into this MAC-e PDU. In any other case it is understood that another MAC-es PDU or Scheduling Information does not fit and it is therefore not necessary to reserve room in the transport block for an additional DDI field.

– For TDD: When, due to the quantization in the transport block sizes that can be supported or triggering of the Scheduling Information (due to timer expiry, see subclauses 11.9.1.4a and 11.9.1.5), the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 29bits, the DDI value [111111] shall be appended at the end of the MAC-e header and a Scheduling Information shall be concatenated into this MAC-e PDU, where DDI value [111111] indicates that there is a Scheduling Information concatenated in this MAC-e PDU. Otherwise, if the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 23 bits, a Scheduling Information shall be concatenated into this MAC-e PDU. In any other case it is understood that another MAC-es PDU or Scheduling Information does not fit and it is therefore not necessary to reserve room in the transport block for an additional DDI field.

– Number of MAC-d PDUs (N):
The number of consecutive MAC-d PDUs corresponding to the same DDI value. The length of the N field is 6 bits.

Reference(s)

TS 25.321 clauses 9.2.4.1, 9.2.4.2

7.1.6.1.3.3 Test purpose

The purpose of this test case is to verify that the UE sets the MAC-es/e header fields in a correct way.

7.1.6.1.3.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the testcase

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)
T-WAIT	200 ms (see 25.331 10.3.6.103)( 1.28Mcps TDD)
E-DCH MAC-d flow multiplexing list	11111111 (See 25.331 10.3.5.1b) Note 1
Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

The UE is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB25 and RB17.

Test procedure

The UE is configured with two logical channels, LCH1 (with priority 1) and LCH2 (with priority 2). LCH1 is mapped to MAC-d flow 2 and LCH2 is mapped to MAC-d flow 3.

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

b) The SS transmits 4 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

c) The SS issues an absolute grant that allows the UE to send with a high rate (signalling value 10, allowing rates well above 5 SDUs/TTI)

d) The SS waits until data is received and checks the values of the header parameters

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

f) The SS transmits three SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

g) The SS transmits two SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

h) The SS issues an absolute grant that allows the UE to send with a high rate (signalling value 10, allowing rates well above 5 SDUs/TTI)

i) The SS waits until data is received and checks the values of the header parameters

j) The SS transmits two SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

k) The SS waits until data is received and checks the values of the header parameters

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	ß		4 RLC PDUs on LCH 2
2	à		SI indicating data on LCH 2
3	ß		Absolute grant allowing UE to transmit on E-DCH	This grant must be sufficiently high to allow a rate corresponding to at least 5 RLC PDUs/TTI, signalling value 10
4	à		1 MAC-es PDU containing 4 RLC PDUs on LCH 2	SS checks header fields
5	ß		Removal of scheduling grant for UE
6	ß		3 RLC PDUs on LCH 2
7	ß		2 RLC PDUs on LCH 1
8	à		Potential SI indicating data on LCH 2	This SI is ignored by the SS
8a			SI indicating data on LCH1 and LCH 2
9	ß		Absolute grant allowing UE to transmit on E-DCH	This grant must be sufficiently high to allow a rate corresponding to at least 5 RLC PDUs/TTI, signalling value 10
10	à		2 MAC-es PDUs containing 2 RLC PDUs on LCH 1 and 3 RLC PDUs on LCH 2 respectively	SS checks header fields
11	ß		2 RLC PDUs on LCH 2
12	à		1 MAC-es PDU containing 2 RLC PDUs on LCH 2	SS checks header fields

Specific Message Contents

None

7.1.6.1.3.5 Test requirements

1. After step 4, the SS shall receive 1 MAC-es PDU shall be received where:

– The TSN is set to 0, DDI is set to 6 and N is set to 4

2. After step 10, the SS shall receive 2 MAC-es PDUs shall be received where:

– For MAC-es PDU 1: The TSN is set to 0, DDI is set to 5 and N is set to 2

– For MAC-es PDU 2: The TSN is set to 1, DDI is set to 6 and N is set to 3

3. After step 12, the SS shall receive 1 MAC-es PDU where:

– The TSN is set to 2, DDI is set to 6 and N is set to 2

7.1.6.2 MAC-es/e – Scheduling

7.1.6.2.1 Correct settings of MAC-es/e scheduling information

7.1.6.2.1.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.1.2 Conformance requirement

Extract From 25.321 clause 9.2.5.3.2:

This information includes the following fields:

The Scheduling Information shall not be transmitted if the Total E-DCH Buffer Status is zero, even if it was triggered by one of the configured triggering mechanisms.

[…]

If data with higher priority than the data already in the transmission buffer arrives, the transmission of a Scheduling Information shall be triggered.

[…]

– 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 bits), 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. The length of this field is 5 bits. The values taken by TEBS are shown in [Ts 25.321] Table 9.2.5.3.2.1.

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 bits when the reported TEBS index is 31. The length of HLBS is 4 bits. The values taken by HLBS are shown in [TS 25.321] table 9.2.5.3.2.2. In case the TEBS field is indicating index 0 (0 bits), the HLBS field shall indicate index 0.

[…]

Extract From 25.321 clause 9.2.4.2:

– Data description indicator (DDI):
The DDI field identifies the logical channel, MAC-d flow and size of the MAC-d PDUs concatenated into the associated MAC-es PDU. The mapping between the DDI values and the logical channel ID, MAC-d flow and PDU size is provided by higher layers. The length of the DDI field is 6 bits.

– For FDD: When, due to the quantization in the transport block sizes that can be supported or triggering of the Scheduling Information, the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 24 bits, the DDI value [111111] shall be appended at the end of the MAC-e header and a Scheduling Information shall be concatenated into this MAC-e PDU, where DDI value [111111] indicates that there is a Scheduling Information concatenated in this MAC-e PDU. Otherwise, if the size of the data plus header is less than or equal to the TB size of the E-TFC selected by the UE minus 18 bits, a Scheduling Information shall be concatenated into this MAC-e PDU. In any other case it is understood that another MAC-es PDU or Scheduling Information does not fit and it is therefore not necessary to reserve room in the transport block for an additional DDI field.

[…]

Extract From 25.321 clause 9.2.6.3:

This control information is used by UEs to indicate to the Node B the amount of resources they require. Scheduling Information is sent via the E-PUCH in the MAC-e header when the UE is granted resource and by the E-RUCCH when no resource has been granted. Scheduling Information consists of three components as defined in subclause 9.2.6.3.3.

– Buffer Information: This consists of:

– Highest priority Logical Channel (HLID)

– Total E-DCH Buffer Status (TEBS)

– Highest priority Logical channel Buffer Status (HLBS)

– UE Power Headroom (UPH): The UPH field indicates the ratio of the maximum UE transmission power and the calculated UE transmit power defined as in [18] that would result for _e equal to 0. The length of UPH is 5 bits.

– Serving and Neighbour Cell Pathloss (SNPL): This may be used by the Node-B to assist with its estimation of the degree of inter cell interference each UE will generate and hence the absolute grant power value and physical resources to assign . The length of SNPL is 5 bits.

The length of TEBS field is 5 bits, the values taken by TEBS are shown in Table 9.2.5.3.2-1. The length of HLBS is 4 bits, the values taken by HLBS are shown in table 9.2.5.3.2-2.

The Scheduling Information message is represented in figure 9.2.6.3-1.

SNPL

(5 bits)

UPH

(5 bits)

TEBS

(5 bits)

HLBS

(4 bits)

HLID

(4 bits)

Figure 9.2.6.3.-1: Scheduling Information format

If Scheduling Information is sent via the E-RUCCH then the E-RNTI is also sent via the E-RUCCH, as shown by Figure 9.2.6.3-2:

Scheduling Information (23 bits)

E-RNTI (16 bits)

Figure 9.2.6.3-2: Format of information sent on E-RUCCH

[…]

Scheduling information reports will be triggered differently depending on the value of the variable Serving_Grant after the Serving Grant Update function. The triggering of a report shall be indicated to the E-TFC selection function at the first new transmission opportunity (this process may be delayed in case the HARQ processes are occupied with re-transmissions).

Extract From 25.321 clause 11.9.1.5:

[…]

If a UE has no Grant and the TEBS becomes larger than zero, the transmission of Scheduling Information shall be triggered via E-RUCCH.

If the UE has a Grant, the scheduling information needs to be included in the MAC-e PDU according to subclause 9.2.4.2, and it shall be transmitted regardless of TEBS status. Additional timer mechanism is used to avoid long pause duration of scheduling information reporting (period defined by RRC and set the same value as below T_WAIT). When the scheduling information is included in MAC-e PDU and sent, the timer will be reset and restarted immediately; when the timer expires, scheduling information shall be sent in a new MAC-e PDU.

RRC can configure MAC with a delay timer to be used when the UE transits from having a Grant to not having a Grant and the TEBS is still larger than zero. The delay timer T_WAIT shall be started once the Grant expires and shall be stopped and reset when a Grant is received. When T_WAIT expires, the transmission of a Scheduling Information shall be triggered via E-RUCCH (T_WAIT shall be stopped and reset).

Reference(s)

TS 25.321 clause 9.2.5.3.2, 9.2.4.2, 9.2.6.3, 11.8.1.6, 11.9.1.5

7.1.6.2.1.3 Test purpose

The purpose of this test case is to verify that the UE sends the E-DCH scheduling information with correct content and with correct triggers.

7.1.6.2.1.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the testcase

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)
Periodicity for Scheduling Info – grant	100ms (FDD)
T-WAIT	200 ms (see 25.331 10.3.6.103)( 1.28Mcps TDD)
T-RUCCH	600 ms (see 25.331 10.3.6.103)( 1.28Mcps TDD)
E-DCH MAC-d flow multiplexing list	11111111 (See 25.331 10.3.5.1b) Note 1
E-DCH Transport Block Size Table	0
Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

The UE is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB25 and RB17.

Test procedure

The UE is configured with two logical channels, LCH1 (with priority 1) and LCH2 (with priority 2). LCH1 is mapped to MAC-d flow 2 and LCH2 is mapped to MAC-d flow 3.

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

b) The SS waits for at least 1000 ms and verifies that no SI is received

c) The SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH2

d) The SS waits until an SI is received at time T0

e) The SS waits until the next SI is received at time T1 and checks the content

f) The SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1 at time T2

g) The SS waits until the next SI is received at time T3 and checks the content

h) The SS issues an absolute grant that allows the UE to transmit 1 SDUs/TTI (absolute grant signalling value 4)

i) The SS waits until all data has been received

j) The SS removes the scheduling grant for the UE

k) The SS transmits 24 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1

l) The SS issues an absolute grant that allows the UE to transmit 1 SDUs/TTI (absolute grant signalling value 4)

m) The SS waits until the next SI is received with payload at time T4

n) The SS waits until the next SI is received with payload at time T5

o) The SS waits until all data is received

p) Void

q) The SS issues an absolute grant that allows the UE to transmit 5 SDUs/TTI (absolute grant signalling value 8)

r) The SS transmits 5 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

s) The SS waits until the 5 SDUs are received and checks that contain both a regular SI and the special DDI (value = 63) NOTE

NOTE: 5 336 bit PDUs and 18 bit Mac-e/es header require a TB size of 1698 bits. The nearest higher TB size is 1749, which easily holds an SI + the special length indicator.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	SS			After the radio bearer has been established the SS waits 1000 ms. No SI shall be received during this time
2	ß		1 RLC PDUs on LCH 2
3	à		SI indicating data on LCH 2	Time T0
4	à		SI indicating data on LCH 2	Time T1
5	ß		1 RLC PDUs on LCH 1	Time T2
6	à		SI indicating data on LCH 1 and LCH 2	Time T3. Presence of data on LCH 1 and LCH 2 can be verified from the indicated fraction of data on LCH1
7	ß		Absolute grant allowing the UE to transmit 1 RLC PDUs per TTI	Signalling value 4
8	à		Data on LCH 1 and LCH 2
8a	ß		Removal of absolute grant	Signalling value 1
9	ß		24 RLC PDUs on LCH 1
9a	ß		Absolute grant allowing the UE to transmit 1 RLC PDUs per TTI	Signalling value 4
10	à		Data and SI	Time T4
11	à		Data only
12	à		Data and SI	Time T5
13	à		Data only
14	SS			After all data has been received, SS waits 1000ms. No SI shall be received during this time.
15	ß		void
16	à		void
17	ß		Absolute grant allowing the UE to transmit 5 RLC PDUs per TTI	Signalling value 8
18	ß		5 RLC PDUs on LCH 1
19	à		Data and SI	The received transport block shall in addition to the 5 PDUs contain a regular SI and the special DDI (value = 63). As there is no data left in buffers, TEBS is set as 0, HLID is set as ‘0000’ and HLBS is set as 0.
NOTE 1: General timer tolerance as defined by 34.108 sub-clause 4.2.3 applies. NOTE 2: Step 10 and 11 can occur in any order. SS should accept these PDUs in any order and verify the time difference between T5 and T4 as per the test requirement.

Specific Message Contents

None

7.1.6.2.1.5 Test requirements

1. In step 1 the SS shall not receive any SI since the UE buffer is empty

2. In step 3 the SS shall receive an SI (content ignored)

3. In step 4 the SS shall receive an SI indicating

– Total E-DCH Buffer Status (TEBS) Index = 6 (32 < TEBS ≤ 42).

– Highest priority Logical channel ID (HLID) = LCH 2.

– Highest Priority Logical Channel Buffer Status (HLBS) Index = 15 (82% < HLBS ≤ 100%).

4. In step 6 the SS shall receive an SI indicating

– Total E-DCH Buffer Status (TEBS) Index = 9 (73 < TEBS ≤ 97).

– Highest priority Logical channel ID (HLID) = LCH 1.

– Highest Priority Logical Channel Buffer Status (HLBS) Index =11(37 < HLBS ≤ 45).

5. T1-T0 shall equal 500 ms

6. T3-T2 shall be less then 120 ms. Note 1.

7. T5-T4 shall equal 100ms

8. In step 14, the SS shall not receive any SI since the UE buffer is empty.

9. In step 19, the received transport block shall in addition to the payload include a regular SI and the special DDI (value = 63). TEBS, HLID and HLBS shall be set as zero.

NOTE 1. 120ms = 2 TTI(for Data to be transmitted from RLC to MAC) + Maximum UE test loop delay ( 10*TTI according to 34.109=100ms).

7.1.6.2.2 Happy bit setting

7.1.6.2.2.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.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.

[…]

The Happy Bit is included on the E-DPCCH for every E-DCH transmission. 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 [TS 25.321] subclause 11.8.1.4.

For every E-DCH transmission, the Happy Bit shall be set to "unhappy" if the three following criteria are met:

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

2) UE has enough power available to transmit at higher data rate; 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.

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

Reference(s)

TS 25.321 clause 9.2.5.3.1, 11.8.1.5

7.1.6.2.2.3 Test purpose

The purpose of this test case is to verify that the UE sets the happy bit correctly.

7.1.6.2.2.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4c using condition A12 as specified in clause 9.1 of TS 34.108.

The following parameters are specific for this test case:

Parameter	Value
Periodicity for Scheduling Info	No periodic SI transmission
Happy bit delay condition	20 ms
E-DCH MAC-d flow maximum number of retransmissions	15
HARQ RV Configuration	rv0

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

Test procedure

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

a) The SS transmits 2 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

b) The SS issues an absolute grant corresponding to 2 RLC PDUs of size 41 octets per TTI (signalling value 5)

c) The SS waits until all data is received in uplink and checks the happy bit

d) The SS removes the scheduling grant for the UE

e) The SS transmits 8 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

f) The SS issues an absolute grant corresponding to 2 RLC SDUs of size 40 octets per TTI (signalling value 5)

g) SS waits until data is receive in uplink and checks the happy bit

h) The SS waits until all data is received in uplink

i) The SS is configured to always send a NACK on every HARQ process, when data is received in uplink, and to pass the received data to the higher layers.

j) The SS transmits 2 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

k) The SS waits until data is received in uplink. The SS stores the HARQ process ID[x] of the HARQ process used for this transmission and checks the happy bit

l) The SS is reconfigured to normal ACK/NACK operation mode on all HARQ processes, except HARQ process ID[x]

m) The SS transmits 10 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

n) The SS waits for the data to be received in uplink and checks the happy bit every time data is re-transmitted on HARQ process ID[x]

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	ß		2 RLC PDUs on LCH 1
2	ß		Absolute grant allowing the UE to transmit 2 RLC PDUs per TTI	Signalling value 5
3	à		Data and happy bit	Happy bit should be set to happy
4	ß		Removal of absolute grant	Signalling value 1
5	ß		8 RLC PDUs on LCH 1
6	ß		Absolute grant allowing the UE to transmit 2 RLC PDUs per TTI	Signalling value 5
7	à		Data and happy bit	Happy bit should be set to unhappy
8	SS			The SS always NACK the received data on all HARQ processes
9	ß		2 RLC PDUs on LCH 1
10	à		Data and happy bit	Happy bit should be set to happy for the data received by the SS on HARQ process ID[x]
11	SS			The SS is set to normal ACK/NACK operation mode on all HARQ processes, except HARQ process ID[x]
12	ß		10 RLC PDUs on LCH 1
12a	ß		10 RLC PDUs on LCH1
13	à		Data and happy bit	Happy bit for the retransmissions of the MAC es PDU received on HARQ process ID[x] should change from happy to unhappy, and become happy again when buffered data has been processed by the other HARQ processes.

Specific Message Contents

None

7.1.6.2.2.5 Test requirements

1. In step 3 the SS shall receive data and the happy bit shall be set to happy in the first TTI containing data

2. In step 7 the SS shall receive data and the happy bit shall be set to unhappy in the first TTI containing data

3. In step 10 the SS shall receive data and the happy bit shall be set to happy in the first TTI containing data

4. In step 13 the SS shall receive data and the happy bit, on the same HARQ process as in step 10, shall change status from happy to unhappy, and later change status from unhappy to happy.

7.1.6.2.3 MAC-es/e non-scheduled transmissions

7.1.6.2.3.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.3.2 Conformance requirement

Extract From 25.321 clause 11.8.1.4:

[…]

RRC can allocate non-scheduled transmission grants to individual MAC-d flows in order to reduce the transmission delays. When a 2ms TTI is configured each non-scheduled grant is applicable to the specific set of HARQ processes indicated by RRC. The applicability of scheduled grants can be also restricted to a specific set of HARQ processes when a 2ms TTI is configured. HARQ process restriction and reservation is under the control of the serving cell Node B and indicated to the UE by RRC.

[…]

For all logical channels, if the logical channel belongs to a non-scheduled MAC-d flow, its data shall be considered as available up to the corresponding non-scheduled grant, if the logical channel does not belong to a non-scheduled MAC-d flow, its data shall be considered as available up to the Serving Grant;

[…]

The amount of data from MAC-d flows for which non-scheduled grants were configured shall not exceed the value of the non-scheduled grant;

[…]

Extract From 25.321 clause11.9.1.4:

In TDD, rules for E-TFC selection shall be applied as provided below.

UEs shall apply E-TFC selection when invoked by the HARQ entity (see subclause 11.9.1.1.1).

For each MAC-d flow, RRC configures MAC-e with a HARQ profile and multiplexing list. Additionally, RRC configures MAC with a power offset in case the Scheduling Information needs to be transmitted without any higher- layer data. The HARQ profile includes the power offset and maximum number of HARQ transmissions to use for this MAC-d flow. For 1.28 Mcps TDD, the HARQ profile also includes a retransmission timer attribute. The multiplexing list identifies for each MAC-d flow(s), the other MAC-d flows for which data can be multiplexed in a transmission that uses the power offset included in its HARQ profile.

RRC can control the scheduling of uplink data by giving each logical channel a priority between 1 and 8, where 1 is the highest priority and 8 the lowest. E-TFC selection in the UE shall be done in accordance with the priorities indicated by RRC. Logical channels have absolute priority, i.e. the UE shall maximise the transmission of higher priority data.

RRC can allocate non-scheduled transmission grants to individual MAC-d flows in order to reduce the transmission delays.

The UE shall determine whether to take scheduled or non-scheduled grants into account in the upcoming transmission. If neither are supposed to be taken into account (i.e. the TTI is not available for non-scheduled transmission and no Grant for scheduled transmission has been received) then no grant shall be assumed to exist. If a grant exists then the transmission format and data allocation shall follow the requirements below.

For each configured MAC-d flow, a given E-TFC can be in any of the following states:

– Supported state;

– Blocked state.

The E-TFC states are derived according to the following:

If the transmission is a retransmission then only the E-TFC with the same block size as the original transmission may be in the supported state.
For 1.28Mcps TDD, only E-TFCs from the E-TFCS (the table of TB sizes) which are consistent with the UE’s E-DCH capability category shall be considered for the transmission;
Only E-TFCs from the E-TFCS (the table of TB sizes) which can be supported by (exactly) the number of slots assigned by the grant shall be considered for the transmission;
Only E-TFCs which result (for the granted timeslot and code physical resources) in a code rate lying between the maximum and minimum (inclusive) allowable code rates set by RRC [7] shall be considered for the transmission {note: the definition of the term “coderate” as used here is the same as that provided by [18]}. This shall be evaluated for both QPSK and 16-QAM modulation;
P_HARQ, the HARQ profile power offset is selected (the HARQ profile for the transmission shall be selected among the HARQ profiles of MAC-d flows on which the highest priority logical channels with available data are mapped; Scheduling Information power offset shall be used when Scheduling Information is transmitted without any higher-layer data.)
Only E-TFCs whose calculated transmission power requirement P_E-PUCH (see [18]) is less than or equal to the available or granted power shall be considered for the transmission (note: this requirement does not apply in the case of a retransmission on non-scheduled resources).

For 3.84Mcps/7.68Mcps TDD, from those E-TFCs in the supported state the UE determines the largest block size that it is permitted to transmit within the given constraints.

For 1.28Mcps TDD, from those E-TFCs in the supported state, UE determines a candidate set with up to 64 E-TFCs, including the largest 63 E-TFCs, in addition to the E-TFC dedicated for SI. If the number of E-TFCs in the supported state is not greater than 63, all the E-TFCs in the supported state shall be included in the candidate set. The E-TFCs in the candidate set shall then be re-indexed in an ascending order and numbered from 0 to (Nmax -1), where Nmax is the number of E-TFC in the candidate set. From the candidate set the UE determines the largest block size that is permitted to transmit within the given constraints.

The UE shall select the modulation type associated with the determined E-TFC (note: if an E-TFC is supported by both QPSK and 16-QAM then 16-QAM modulation shall be used if its power requirement (P_E-PUCH) is lower than the power requirement for QPSK, otherwise QPSK modulation shall be used).

Data allocation shall then be performed in accordance with the following:

– For all logical channels, if the logical channel belongs to a non-scheduled MAC-d flow, its data shall be considered as available up to the largest block size determined for the corresponding non-scheduled grant. If the logical channel does not belong to a non-scheduled MAC-d flow, its data shall be considered as available up to the largest block size determined for the Serving Grant;

– The data allocation shall maximise the transmission of higher priority data;

– The UE shall select the E-TFC, SF and modulation which minimises the power used (3.84/7.68 Mcps TDD only);

– The UE shall select the E-TFC and modulation which minimises the power used (1.28 Mcps TDD only);

Once an appropriate E-TFC and data allocation are found according to the rules above, the "Multiplexing and TSN Setting" entity shall generate the corresponding MAC-e PDU.

In 1.28Mcps TDD, when Scheduling Information is triggered by timer per subclause 11.9.1.5, the E-TFC selection and data-allocation process shall assume that Scheduling Information has a priority higher than any other logical channel.

The E-TFC selection function shall provide this MAC-e PDU and transmission HARQ profile to the HARQ entity. The selected E-TFC is also provided (Note: for 1.28Mcps TDD, the signalled transport block size index, i.e. E-TFCI, is the index of the selected E-TFC in the candidate set.). The maximum number of HARQ transmissions and the power offset in this profile shall be set respectively to the maximum of both the Max Number of HARQ Transmissions and of the power offset of the HARQ profiles from all the MAC-d flows from which data is multiplexed into the transmission. For 1.28 Mcps TDD, the retransmission timer shall be set to the maximum of the retransmission timer value of the HARQ profiles that are permitted to be multiplexed into the transmission. Each HARQ process which is associated with a buffer holding a MAC-e PDU for potential retransmission shall maintain the HARQ profile and the number of re-transmissions that have occurred. For 1.28 Mcps TDD, the HARQ process shall also maintain the value of RTX_TIMER.

Further information on E-TFC selection is provided in Annex CA.

Reference(s)

TS 25.321 clause 11.8.1.4, 11.9.1.4

7.1.6.2.3.3 Test purpose

To verify that the UE when RRC is configured for non-scheduled transmissions sends data without scheduling grant. To verify that no SI is sent for non-scheduled transmissions.

7.1.6.2.3.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4c(FDD) /6.11.5.4.7.6(1.28Mcps TDD) using condition A12(FDD) /A11(1.28Mcps TDD) as specified in clause 9.1 of TS 34.108. The following parameters are specific for this test case:

Parameter	Value
Periodicity for scheduling info	No periodic scheduling info
E-TFCI table	Table 0 for 10 ms TTI(FDD)
E-TFCI table	5ms TTI E-DCH Transport Block Size Table 0(1.28Mcps TDD)

The UE is placed into UE test loop mode 1 with the UL SDU size set to (10*41)-2 octets.

Test procedure

LCH 1 is mapped to MAC-d flow 2 which is configured for non-scheduled transmission allowing one SDU/TTI to be sent.

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

b) The SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1

c) The SS waits until data is received and checks that only 1 PDU/TTI is transmitted

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		1 RLC PDU on LCH 1
2	à		MAC-es PDU containing 1 RLC PDU	This step is repeated 10 times until the complete SDU is transmitted

Specific Message Contents

None

7.1.6.2.3.5 Test requirements

1. After step 1, the SS shall not receive any SI.

2. In step 2, the SS shall receive 1 MAC-es PDU containing 1 RLC PDU in each TTI until the complete SDU has been received.

7.1.6.2.4 MAC-es/e correct handling of scheduled transmissions when absolute grant varies

7.1.6.2.4.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.4.2 Conformance requirement

Extract from 25.321 clause 9.2.5.2.2:

The absolute grant message is sent on downlink, on the configured E-AGCH, from the serving E-DCH cell and allows the Node B scheduler to directly adjust the granted rate of UEs under its control.

[…]

Absolute Grant Value:
This field indicates the maximum E-DCH traffic to pilot ratio (E-DPDCH/DPCCH) that the UE is allowed to use in the next transmission. The length of the Absolute Grant Value field is 5 bits

[…]

Extract From 25.321 clause 9.2.6.2.1:

The Absolute Grant is sent on downlink on a set of configured E-AGCHs from the serving E-DCH cell and allows the Node B scheduler to directly adjust the granted rate and assigned physical resources for UEs under its control. The physical resource assignment indicates to the UE the maximum amount of uplink resources that it may use for a scheduled transmission.

The E-AGCH is a shared channel that uses an E-RNTI specific CRC in order to address messages to specific UEs (see [19]). For TDD, the RRC shall configure the MAC with a primary E-RNTI only.

A UE is required to monitor a set of E-AGCHs. The RRC signals to the UE details of the set of E-AGCHs that are to be monitored. The UE decodes an Absolute Grant intended for it on the basis of the E-RNTI sent to it by the Node B via the SRNC and by RRC. The following information will be conveyed in an absolute grant message:

Absolute Grant Value – maximum power granted per resource unit (per slot)

The physical resources to be used for transmission

– Channelisation Code

– Timeslots

– Resource Duration (optional)

The absolute grant message itself includes multiple fields that are multiplexed together into between 14 and 28 bits for 3.84/7.68 Mcps TDD and between 23 and 26 bits for 1.28 Mcps TDD (depending on the system configuration) inside the MAC-e of the Node B and then submitted to the physical layer for transmission on the E-AGCH. These fields are:

– Absolute Grant Value:
For TDD, this field indicates the maximum E-DCH traffic to reference power ratio (E-PUCH/P_e-base) per TDD resource unit that the UE is allowed to use on the E-DCH resources associated with the Absolute Grant. A TDD resource unit is defined as one sixteenth of the OVSF code space in one timeslot. The length of the Absolute Grant Value field for TDD is 5 bits.

– Channelisation Code:
This field describes the code component of the physical resource grant. For 1.28/3.84 Mcps TDD it comprises an enumerated value of length 5 bits indicating which node on the OVSF code tree has been allocated. For 7.68 Mcps TDD it comprises an enumerated value of length 6 bits indicating which node on the OVSF tree has been allocated. The mapping between the allocated OVSF and the enumerated node 0…30 for 1.28/3.84 Mcps and 0…62 for 7.68 Mcps is as given in [19].

– Timeslot Resource Related Information:
This field describes the timeslot component of the physical resource grant and comprises a bitmap of length n_TRRI indicating which of the timeslots configured for E-DCH use by RRC have been allocated with the LSB corresponding to the lowest numbered E-DCH timeslot and the MSB corresponding to the highest numbered timeslot. The length of the TRRI field (n_TRRI) is 5 bits for 1.28 Mcps TDD and is configurable by RRC on a per-cell basis between 1 and 12 bits for 3.84/7.68 Mcps TDD.

– Resource Duration Indicator:
Optionally, RRC may configure, on a per-cell basis the presence of a resource duration indicator field on E-AGCH for TDD. If configured as present in a cell, 3 bits are used to indicate the number of TTI’s allocated and the spacing between the allocated TTIs via a single grant according to table 9.2.6.2.1-2. If the field is configured as not present on E-AGCH in the cell, a value of 0 is implicitly assumed by the UE corresponding to 1 TTI.

Table 9.2.6.2.1-2 – Resource Duration Indicator (RDI) interpretation

Resource Duration Indicator (3 bits)	TTIs allocated	TTI spacing
0	1	1
1	2	1
2	2	2
3	2	4
4	4	1
5	4	2
6	4	4
7	8	1

– E-AGCH Cyclic Sequence Number (ECSN):
The ECSN is a 3-bit field used to assist the UE with outer-loop power control of E-AGCH (cf. HCSN for HS-SCCH).

E-HICH Indicator(EI) (1.28 Mcps TDD only)
The E-HICH indicator (EI) consists of 2 bits and is used to indicate which E-HICH will convey the acknowledgement indicator for the scheduled UEs.
E-UCCH Number Indicator (ENI) (1.28 Mcps TDD only)
The E-UCCH Number Indicator (ENI) is a 3-bit field used to indicate the detailed number of E-UCCH.

[…]

UEs in CELL_DCH state, configured with an E-DCH transport channel shall maintain a Serving Grant and the list of active HARQ processes based on the absolute and relative grant commands decoded on the configured E-AGCH and E-RGCH(s).

[…]

Reference(s)

TS 25.321 clauses 9.2.5.2.2, 9.2.6.2.1, 11.8.1.3

7.1.6.2.4.3 Test purpose

To verify that the UE transmits different amount of data when the absolute grant varies.

7.1.6.2.4.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

Parameter	Value
Periodicity for scheduling info	No periodic scheduling info
E-TFCI table	Table 0 for 10 ms TTI (FDD)
E-TFCI table	5ms TTI E-DCH Transport Block Size Table 0(1.28Mcps TDD)

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

Test procedure

Logical Channel with Id 7 (LCH 1) is mapped to MAC-d flow 2 with priority 1.

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

b) The SS transmits 4 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1

c) SS waits until an SI is received

d) The SS issues an absolute grant that allows the UE to transmit 1 SDU/TTI (absolute grant signalling value 4)

e) The SS waits until data is received and checks that only 1 SDU/TTI is transmitted

f) The SS waits until all 4 SDUs have been received

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

h) The SS transmits 8 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1

i) SS waits until an SI is received

j) The SS issues an absolute grant that allows the UE to transmit 4 SDUs/TTI (absolute grant signalling value 7)

k) The SS waits until data is received and checks that only 4 SDUs/TTI is transmitted

l) The SS waits until all 8 SDUs have been received

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

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		4 RLC PDUs on LCH 1
1a	à		SI indicating data on LCH 1
2	ß		Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 4
3	à		MAC es PDU containing 1 RLC PDU, 4 TTIs in a row
4	ß		Removal of absolute grant	Signalling value 1
5	ß		8 RLC PDUs on LCH 1
5a	à		SI indicating data on LCH 1
6	ß		Absolute grant allowing the UE to transmit 4 RLC PDUs per TTI	Signalling value 7
7	à		MAC es PDU containing 4 RLC PDUs, 2 TTIs in a row
8	ß		Removal of absolute grant	Signalling value 1

Specific Message Contents

None

7.1.6.2.4.5 Test requirements

1. In step 3, the SS shall receive 1 MAC-es PDU containing 1 RLC PDU. This shall happen 4 TTIs in a row.

2. In step 7, the SS shall receive 1 MAC-es PDU containing 4 RLC PDUs. This shall happen 2 TTIs in a row.

7.1.6.2.5 MAC-es/e de-activation and re-activation of HARQ processes

7.1.6.2.5.1 Definition and applicability

All UEs which support E-DCH and support 2 ms TTI.

7.1.6.2.5.2 Conformance requirement

The Serving Grant Update procedure shall be applied at every TTI boundary and shall take into account the Absolute Grant message, Serving Relative Grant and non-serving Relative Grants that apply to the TTI.

The UE shall:

1> set reference_ETPR to the E-DPDCH to DPCCH power ratio as defined in subclause 3.1.2;

1> if an Absolute Grant was received for this TTI:

2> if the Identity type is “Primary”, and the Absolute Grant value is set to "INACTIVE":

3> if Absolute Grant Scope indicates "Per HARQ process" and a 2ms TTI is configured:

4> de-activate the process given by the value of CURRENT_HARQ_PROCESS.

3> if Absolute Grant Scope indicates "All HARQ processes" and a secondary E-RNTI was configured by higher layers:

4> activate all HARQ processes;

4> set Serving_Grant = Stored_Secondary_Grant;

4> set Primary_Grant_Available to "False".

3> if Absolute Grant Scope indicates "All HARQ processes", a 2ms TTI is configured and a secondary E-RNTI was not configured by higher layers:

4> deactivate all HARQ processes (if a process was inactive it remains inactive, if a process was active it becomes inactive).

2> else if the Absolute Grant Value is different from "INACTIVE":

3> if the Identity Type is "Secondary":

4> set Stored_Secondary_Grant = Absolute Grant Value.

3> if the Identity Type is "Primary" or Primary_Grant_Available is set to "False":

4> set Serving_Grant = Absolute Grant Value.

4> if the Identity Type is "Primary":

5> set Primary_Grant_Available to "True";

5> if Absolute Grant Scope indicates "Per HARQ process":

6> activate the process given by the value of CURRENT_HARQ_PROCESS.

5> if Absolute Grant Scope indicates "All HARQ processes":

6> activate all HARQ processes;

5> if AG_Timer is not active, it shall be started, otherwise it shall be restarted.

Reference(s)

TS 25.321 clause 11.8.1.3.1

7.1.6.2.5.3 Test purpose

The purpose of this test case is to verify the selective de-activation and re-activation of a HARQ process

7.1.6.2.5.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4c using condition A12 as specified in clause 9.1 of TS 34.108. The logical channel, transport channel and queue identities are set to:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25

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)
E-DCH TTI	2 ms

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to (10*41)-2 octets.

Test procedure

In this test procedure The UE is configured with one logical channels, with an UL SDU size of 39 octets.

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

b) SS transmits 5 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

c) SS waits until an SI is received.

d) SS issues an absolute grant that allows the UE to send 1 RLC PDU per TTI (signalling value 4)

e) SS starts receiving loop backed RLC PDU’s. SS checks all 8 Harq processes are used.

f) SS transmits an absolute grant, with Absolute Grant Value set to "INACTIVE" and Absolute Grant Scope indicating "Per HARQ process" corresponding to HARQ process 0 & 4.

g) SS transmits 5 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

h) SS starts receiving loop backed RLC PDU’s. SS checks Harq processes 0 and 4 are not used.

i) SS transmits an absolute grant, with Absolute Grant Value that allows UE to send 1 RLC PDU per TTI (signalling value 4) and Absolute Grant Scope indicating " All HARQ processes ".

j) SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

k) SS starts receiving loop backed RLC PDU’s. SS checks all 8 Harq processes are used.

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		5 RLC PDUs on LCH 1
2	à		SI indicating data on LCH 1
3	ß		Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 4
4	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until all 5 RLC SDU’s are received
5	ß		Absolute grant de-activating HARQ Process 0
6	ß		Absolute grant de-activating HARQ Process 4
7	ß		5 RLC PDUs on LCH 1
8	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until all 5 RLC SDU’s are received.
9	ß		Absolute grant activating All HARQ Process 0	Signalling value 4
10	ß		5 RLC PDUs on LCH 1
11	à		MAC es PDU’s containing 1 RLC PDU from LCH 1	This step is repeated until all 5 RLC SDU’s are received

Specific Message Contents

None

7.1.6.2.5.5 Test requirements

1. In step 4 all 8 HARQ processes shall be used to transmit RLC PDU’s

2. In step 8 HARQ processes 0 and 4 shall not be used to transmit RLC PDU’s

3. In step 11 all 8 HARQ processes shall be used to transmit RLC PDU’s

7.1.6.2.6 MAC-es/e correct handling of relative grants

7.1.6.2.6.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.6.2 Conformance requirement

The UE shall:

1> set reference_ETPR2 to reference_ETPR as defined in subclause 3.1.2;

1> set reference_ETPR to the E-DPDCH to DPCCH power ratio as defined in subclause 3.1.2;

1> if an Absolute Grant was received for this TTI:

…..

1> else (no Absolute Grant received):

2> if the HARQ process given by the value of CURRENT_HARQ_PROCESS is active; and

2> if Primary_Grant_Available is equal to "True"; and

2> if Serving_Grant <> "Zero_Grant" ; and

2> if AG_Timer has expired; and2> if there was a scheduled transmission (see Note) in the previous TTI of the HARQ process given by the value of CURRENT_HARQ_PROCESS:

3> if the Serving Relative Grant indicates "UP":

4> determine the Serving_Grant in accordance with subclause 9.2.5.2.1.

3> else, if the Serving Relative Grant indicates "DOWN":

4> determine the Serving_Grant in accordance with subclause 9.2.5.2.1.

1> if any Non-Serving Relative Grants indicate "DOWN" for this TTI and Serving_Grant <> "Zero_Grant":

2> Serving_Grant = MIN(Serving_Grant, Serving_Grant determined in accordance with subclause 9.2.5.2.1);

2> Maximum_Serving_Grant = Serving_Grant.

2> if Non_Serving_RG_Timer is not active it shall be started, otherwise it shall be restarted;

1> else if no Non-Serving Relative Grants indicate "DOWN" for this TTI:

2> if Non_Serving_RG_Timer has not expired:

3> Serving_Grant = MIN(Maximum_Serving_Grant, Serving_Grant).NOTE: Scheduling Information sent alone is not considered as a scheduled transmission.

Reference(s)

TS 25.321 clause 11.8.1.3.1

7.1.6.2.6.3 Test purpose

The purpose of this test case is

1. To verify that the UE acts on serving and non-serving relative grants when the UE is using the Primary E-RNTI.

2. To verify that the UE only acts on non-serving relative grants when the UE is using the Secondary E-RNTI

3. To verify that the UE does not use a Serving_Grant value greater than Maximum_Serving_Grant when the Non_Serving_RG_Timer has not expired.

7.1.6.2.6.4 Method of test

Initial conditions

System Simulator:

2 cells, default parameters, Ciphering Off.

User Equipment:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25

Cell 1 is the serving E-DCH cell.

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)
E-DCH TTI	10 ms
New Secondary E-RNTI	‘1010 1111 1010 1111’
3-Index-Step Threshold	20
2-Index-Step Threshold	37

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to (10*41)-2 octets.

Test procedure

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

0) SS waits for the Measurement report from the UE with event set to “1a” and then adds the Radio link on the second cell by sending an Active Set Update message.

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

b) SS transmits 10 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

c) SS waits until an SI is received.

d) SS issues a primary absolute grant that allows the UE to send 1 RLC PDU per TTI (signalling value 4)

e) SS starts receiving loop backed RLC PDU’s.

f) After receiving data once on all HARQ processes in a HARQ-RTT, SS transmits a relative grant in cell 1(serving cell) as ‘UP’.

g) SS continues receiving loop back PDU’s and checks that UE has started using the serving grant corresponding to more than one RLC PDU’s transmitted per TTI.

h) SS transmits 10 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

i) SS starts receiving loop backed RLC PDU’s.

j) After receiving data once on all HARQ processes in a HARQ-RTT, SS transmits a relative grant in cell 2(non serving) as ‘Down’.

k) SS continues receiving loop back PDU’s and checks that the UE has reduced the serving grant corresponding to one RLC PDU transmitted per TTI.

l) SS transmits a primary absolute grant, with Absolute Grant Value set to "INACTIVE" and Absolute Grant Scope indicating "All HARQ process" . The UE starts using the Secondary Grant.

m) SS transmits 10 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

n) SS waits until an SI is received.

o) SS issues a secondary absolute grant corresponding to 1 RLC PDU of size 41 octets per TTI (signalling value 4)

p) After receiving data once on all HARQ processes in a HARQ-RTT, SS transmits a relative grant in cell 1(serving cell) as ‘UP’.

q) SS continues receiving loop back PDU’s and checks that the UE has ignored the previous relative grant.

r) SS issues a secondary absolute grant corresponding to 2 RLC PDU’s of size 41 octets per TTI (signalling value 5)

s) SS transmits 10 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

t) SS starts receiving loop backed RLC PDU’s. SS checks that the UE is using a serving grant corresponding to 2 RLC PDU’s transmitted per TTI.

u) After receiving data on all HARQ processes for two HARQ-RTTs, SS transmits a relative grant in cell 2 (non serving) as ‘Down’. (*Note)

v) SS continues receiving loop back PDU’s and checks that UE has reduced the serving grant corresponding to 1 RLC PDU’s transmitted per TTI.

w) SS issues a secondary absolute grant corresponding to 2 RLC PDU’s of size 41 octets per TTI (signalling value 5)

wa) SS transmits 10 SDU’s of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

wb) SS starts receiving loop backed RLC PDU’s. SS checks that the UE is using a serving grant corresponding to 2 RLC PDU’s transmitted per TTI.

x) After receiving data on all HARQ processes for two HARQ-RTTs, SS transmits a relative grant in cell 2 (non serving) as ‘Down’.

y) In the following TTI, SS transmits a secondary absolute grant that allows the UE to send 2 RLC PDU’s of size 41 octets per TTI (signalling value 5).

za) Void

aa) SS continues receiving loop back PDU’s and checks that UE has reduced the serving grant corresponding to 1 RLC PDU’s transmitted per TTI.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
0a	à		Measurement Report	See specific message contents for this message
0b	ß		ACTIVE SET UPDATE	The SS instructs the UE to add cell 2 in the active set
0c	à		ACTIVE SET UPDATE COMPLETE
1	ß		10 RLC PDUs on LCH 1
2	à		SI indicating data on LCH 1
3	ß		Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 4
4	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated for one HARQ RTT
5	ß		Relative Grant in cell 1 with ‘UP’
6	à		MAC es PDU containing more than one RLC PDU from LCH 1	This step is repeated until all RLC SDU’s are received.
7	ß		10 RLC PDUs on LCH 1
8	à		MAC es PDU containing more than one RLC PDU from LCH 1	This step is repeated for one HARQ RTT
9	ß		Relative Grant in cell 2 with ‘DOWN’
10	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until all RLC SDU’s are received.
11	ß		Primary Absolute grant set to ‘INACTIVE’ and scope ‘All HARQ Processes’	UE serving grant to Stored_Secondary_Grant which is initialised to ‘Zero_grant’.
12	ß		10 RLC PDUs on LCH 1
13	à		SI indicating data on LCH 1
14	ß		Secondary Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 4
15	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated for one HARQ RTT
16	ß		Relative Grant in cell 1 with ‘UP’
17	à		MAC es PDU containing one RLC PDU from LCH 1	This step is repeated until all RLC SDU’s are received.
18	ß		Secondary Absolute grant allowing the UE to transmit 2 RLC PDU per TTI	Signalling value 5
19	ß		10 RLC PDUs on LCH 1
20	à		MAC es PDU containing 2 RLC PDU from LCH 1	This step is repeated for two HARQ RTTs
21	ß		Relative Grant in cell 2 with ‘DOWN’
22	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until all RLC SDU’s are received.
23	ß		Secondary Absolute grant allowing the UE to transmit 2 RLC PDUs per TTI	Signalling value 5 SG_LUPR corresponding to 19/15
23a	ß		10 RLC PDUs on LCH 1
23b	à		MAC es PDU containing 2 RLC PDU from LCH 1	This step is repeated for two HARQ RTTs
24	ß		Relative Grant in cell 2 with ‘DOWN’	SG_LUPR corresponding to 17/15 sufficient for 1 RLC PDU per TTI
25	ß		1 TTI after step 24, Absolute grant allowing the UE to transmit 2 RLC PDUs per TTI	Signalling value 5
26	ß		Void
27	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until all RLC SDU’s are received.

Specific Message Contents

MEASUREMENT REPORT (Step 0a)

Use the same message as specified in 34.108 except for the following:

Information Element	Value/remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
Measurement identity	1
Measured Results
– Intra-frequency measured results	Check to see if measurement results for 2 cells are included (the order in which the different cells are reported is not important)
– Cell measured results
– Cell Identity	Checked that this IE is absent
– Cell synchronisation information	Checked that this IE is present and includes IE COUNT-C-SFN frame difference
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1 of TS 34.108
– CPICH Ec/N0	Checked that this IE is absent
– CPICH RSCP	Checked that this IE is present
– Pathloss	Checked that this IE is absent
– Cell measured results
– Cell Identity	Checked that this IE is absent
– Cell synchronisation information	Checked that this IE is absent
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1 of TS 34.108
– CPICH Ec/N0	Checked that this IE is absent
– CPICH RSCP	Checked that this IE is present
– Pathloss	Checked that this IE is absent
Measured results on RACH	Checked that this IE is absent
Additional measured results	Checked that this IE is absent
Event results
– Intra-frequency measurement event results
– Intra-frequency event identity	1a
– Cell measurement event results
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1 of TS 34.108

ACTIVE SET UPDATE (Step 0b)

The message to be used in this test is defined in TS 34.108, clause 9, with the following exceptions:

Information Element	Value/remark
Activation time	Not Present
Radio link addition information
– Primary CPICH Info
– Primary Scrambling Code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1 of TS 34.108
– Downlink DPCH info for each RL
– CHOICE mode	FDD
– Primary CPICH usage for channel estimation	P-CPICH can be used.
– DPCH frame offset	Calculated value from Cell synchronisation information
– Secondary CPICH info	Not Present
– DL channelisation code	This IE is repeated for all existing downlink DPCHs allocated to the UE
– Secondary scrambling code	1
– Spreading factor	Refer to TS 34.108 clause 6.10.2.4 "Typical radio parameter sets"
– Code Number	For each DPCH, assign the same code number in the current code given in cell 1.
– Scrambling code change	Not Present
– TPC Combination Index	1
– Close loop timing adjustment mode	Not Present
– TFCI Combining Indicator	FALSE
– E-HICH Information
– Channelisation code	4
– Signature sequence	1
– CHOICE E-RGCH Information
– E-RGCH Information
– Signature Sequence	0
– RG combination index	1

7.1.6.2.6.5 Test requirements

1. After step 5 UE will start sending 2 RLC PDU’s per TTI.

2. After step 9, UE will reduce number of RLC PDU’s per TTI to 1.

3. After step 16, UE will not change its rate of RLC PDU’s per TTI.

4. After step 21, UE will reduce number of RLC PDU’s per TTI to 1.

4a After Step 23,UE will start sending 2 RLC PDU’s per TTI

4b. After step 24, UE will reduce number of RLC PDU’s per TTI to 1

5. After step 25, UE will not change its SG_LUPR and hence in step 27 will loop back PDU’s at the rate of 1 RLC PDU per TTI.

7.1.6.2.7 MAC-es/e correct handling of absolute grants on Primary and Secondary E-RNTI

7.1.6.2.7.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.7.2 Conformance requirement

The UE shall:

1> set reference_ETPR to the E-DPDCH to DPCCH power ratio as defined in subclause 3.1.2;

1> if an Absolute Grant was received for this TTI:

2> if the Identity type is “Primary”, and the Absolute Grant value is set to "INACTIVE":

3> if Absolute Grant Scope indicates "Per HARQ process" and a 2ms TTI is configured:

4> de-activate the process given by the value of CURRENT_HARQ_PROCESS.

3> if Absolute Grant Scope indicates "All HARQ processes" and a secondary E-RNTI was configured by higher layers:

4> activate all HARQ processes;

4> set Serving_Grant = Stored_Secondary_Grant;

4> set Primary_Grant_Available to "False".

3> if Absolute Grant Scope indicates "All HARQ processes", a 2ms TTI is configured and a secondary E-RNTI was not configured by higher layers:

4> deactivate all HARQ processes (if a process was inactive it remains inactive, if a process was active it becomes inactive).

2> else if the Absolute Grant Value is different from "INACTIVE":

3> if the Identity Type is "Secondary":

4> set Stored_Secondary_Grant = Absolute Grant Value.

3> if the Identity Type is "Primary" or Primary_Grant_Available is set to "False":

4> set Serving_Grant = Absolute Grant Value.

4> if the Identity Type is "Primary":

5> set Primary_Grant_Available to "True";

5> if Absolute Grant Scope indicates "Per HARQ process":

6> activate the process given by the value of CURRENT_HARQ_PROCESS.

5> if Absolute Grant Scope indicates "All HARQ processes":

6> activate all HARQ processes;

5> if AG_Timer is not active, it shall be started, otherwise it shall be restarted. Reference(s)

TS 25.321 clause 11.8.1.3.1

7.1.6.2.7.3 Test purpose

The purpose of this test case is to verify that the UE acting on absolute grants given on the Primary and Secondary E-RNTI and switching between the 2 cases.

7.1.6.2.7.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25

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)
New Secondary E-RNTI	‘1010 1111 1010 1111’

The UE is placed into UE test loop mode 1 with the UL SDU size set to (4*41)-2 octets.

Test procedure

In this test procedure The UE is configured with one logical channel.

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

b) SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1

c) SS waits until an SI is received.

d) The SS issues primary absolute grant corresponding to 4 RLC PDUs of size 41 octets per TTI (signalling value 7)

e) SS starts receiving loop backed RLC PDU’s.

f) SS transmits primary absolute grant, with Absolute Grant Value set to "INACTIVE" and Absolute Grant Scope indicating "All HARQ process" . UE starts using Secondary Grant.

g) SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

h) SS waits until an SI is received.

i) The SS issues secondary absolute grant corresponding to 1 RLC PDU of size 41 octets per TTI (signalling value 4)

j) SS starts receiving loop backed RLC PDU’s.

k) SS issues secondary absolute grant of ‘ZERO_GRANT’.

l) SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

m) SS waits until an SI is received.

n) The SS issues primary absolute grant corresponding to 4 RLC PDUs of size 41 octets per TTI (signalling value 7), with Absolute Grant Scope set as "All HARQ processes". UE starts using primary grant.

o) SS starts receiving loop backed RLC PDU’s.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	ß		1 RLC PDUs on LCH 1
2	à		SI indicating data on LCH 1
3	ß		Primary Absolute grant allowing the UE to transmit 4 RLC PDU per TTI	Signalling value 7
4	à		MAC es PDU containing 4 RLC PDU’s from LCH 1
5	ß		Primary Absolute grant set to ‘INACTIVE’ and scope ‘All HARQ Processes’	UE serving grant to Stored_Secondary_Grant which is initialised to ‘Zero_grant’.
6	ß		1 RLC PDUs on LCH 1
7	à		SI indicating data on LCH 1
8	ß		Secondary Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 4
9	à		MAC es PDU containing 1 RLC PDU from LCH 1	This step is repeated until the whole RLC SDU is transmitted
10	ß		Secondary Absolute grant set to ‘Zero_Grant’
11	ß		1 RLC PDUs on LCH 1
12	à		SI indicating data on LCH 1
13	ß		Primary Absolute grant allowing the UE to transmit 4 RLC PDU per TTI	Signalling value 7
14	à		MAC es PDU containing 4 RLC PDU’s from LCH 1

Specific Message Contents

None

7.1.6.2.7.5 Test requirements

1. In step 4, the SS shall receive 1 MAC-es PDU containing 4 RLC PDU’s

1a. In step 7 UE shall transmit SI, as an indication that it has stopped using previous absolute grant.

2. After step 8, UE shall start sending loop backed PDU, with one RLC PDU per TTI.

3. In step 12 UE shall transmit SI.

4. After step 13, UE shall loop back all 4 RLC PDU’s in one TTI.

7.1.6.2.8 MAC-es/e combined non-scheduled and scheduled transmissions

7.1.6.2.8.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.8.2 Conformance requirement

From 25.321 clause 11.8.1.4:

The transmission format and data allocation shall follow the requirements below:

[…]

– For all logical channels, if the logical channel belongs to a non-scheduled MAC-d flow, its data shall be considered as available up to the corresponding non-scheduled grant, if the logical channel does not belong to a non-scheduled MAC-d flow, its data shall be considered as available up to the Serving Grant;

[…]

– The amount of data from MAC-d flows for which non-scheduled grants were configured shall not exceed the value of the non-scheduled grant;

[…]

– When not in a power limited condition the maximum amount of data from MAC-d flows for which no non-scheduled grants were configured shall be quantized to the next smaller supported E-TFC based on the Serving Grant (after adjustment for compressed frames), the power offset from the selected HARQ profile, the non-scheduled grants (if any) and Scheduling Information (if any); In the case a 2ms TTI is configured and the HARQ process is inactive, the UE shall not include any such data in the transmission;

From 25.321 clause 11.9.1.4:

In TDD, rules for E-TFC selection shall be applied as provided below.

UEs shall apply E-TFC selection when invoked by the HARQ entity (see subclause 11.9.1.1.1).

For each MAC-d flow, RRC configures MAC-e with a HARQ profile and multiplexing list. Additionally, RRC configures MAC with a power offset in case the Scheduling Information needs to be transmitted without any higher- layer data. For 1.28 Mcps TDD, RRC also configures MAC with a retransmission timer and the maximum number of HARQ transmissions in case the Scheduling Information needs to be transmitted without any higher-layer data. The HARQ profile includes the power offset and maximum number of HARQ transmissions to use for this MAC-d flow. For 1.28 Mcps TDD, the HARQ profile also includes a retransmission timer attribute. The multiplexing list identifies for each MAC-d flow(s), the other MAC-d flows for which data can be multiplexed in a transmission that uses the power offset included in its HARQ profile.

RRC can allocate non-scheduled transmission grants to individual MAC-d flows in order to reduce the transmission delays.

For each configured MAC-d flow, a given E-TFC can be in any of the following states:

– Supported state;

– Blocked state.

The E-TFC states are derived according to the following:

– If the transmission is a retransmission then only the E-TFC with the same block size as the original transmission may be in the supported state.

– For 1.28Mcps TDD, only E-TFCs from the E-TFCS (the table of TB sizes) which are consistent with the UE’s E-DCH capability category shall be considered for the transmission;

– Only E-TFCs from the E-TFCS (the table of TB sizes) which can be supported by (exactly) the number of slots assigned by the grant shall be considered for the transmission;

– Only E-TFCs which result (for the granted timeslot and code physical resources) in a coderate lying between the maximum and minimum (inclusive) allowable code rates set by RRC [7] shall be considered for the transmission {note: the definition of the term “coderate” as used here is the same as that provided by [18]}. This shall be evaluated for both QPSK and 16-QAM modulation;

– P_HARQ, the HARQ profile power offset is selected (for 3.84/7.68Mcps TDD the HARQ profile for the transmission shall be selected among the HARQ profiles of MAC-d flows on which the highest priority logical channels with available data are mapped, for 1.28Mcps TDD the HARQ power offset shall be set to the maximum of HARQ power offset of all the MAC-d flows mapped to the same type of resource (scheduled or non-scheduled resource); Scheduling Information power offset shall be used when Scheduling Information is transmitted without any higher-layer data.)

– Only E-TFCs whose calculated transmission power requirement P_E-PUCH (see [18]) is less than or equal to both the available and the granted power shall be considered for the transmission (note: this requirement does not apply in the case of a retransmission on non-scheduled resources). For TDD, the smallest E-TFC is considered always in the supported state. The granted power is defined as the calculated E-PUCH transmission power of [18] with β_e = (Absolute Grant Value + α_e). The available power is the maximum UE transmission power.

From those E-TFCs in the supported state the UE determines the largest block size that it is permitted to transmit within the given constraints.

Data allocation shall then be performed in accordance with the following:

– The data allocation shall maximise the transmission of higher priority data;

– The UE shall select the E-TFC, SF and modulation which minimises the power used (3.84/7.68 Mcps TDD only);

– The UE shall select the E-TFC and modulation which minimises the power used (1.28 Mcps TDD only);

Once an appropriate E-TFC and data allocation are found according to the rules above, the "Multiplexing and TSN Setting" entity shall generate the corresponding MAC-e PDU.

The E-TFC selection function shall provide this MAC-e PDU and transmission HARQ profile to the HARQ entity. For 3.84Mcps TDD and 7.68Mcps TDD the selected E-TFC is also provided (Note: for 1.28Mcps TDD, the signalled transport block size index, i.e. E-TFCI, is the index of the selected E-TFC in the candidate set.). The maximum number of HARQ transmissions and the power offset in this profile shall be set respectively to the maximum of both the Max Number of HARQ Transmissions and of the power offset of the HARQ profiles from all the MAC-d flows from which data is multiplexed into the transmission. For 1.28 Mcps TDD, the maximum number of HARQ transmissions shall be set to the maximum of the Max Number of HARQ Transmissions of the HARQ profiles from all the MAC-d flows from which data is multiplexed into the transmission, the HARQ power offset shall be set to the maximum of HARQ power offset of all the MAC-d flows mapped to the same type of resource (scheduled or non-scheduled resource), and the retransmission timer shall be set to the maximum of the retransmission timer value of the HARQ profiles that are permitted to be multiplexed into the transmission. For 1.28Mcps TDD, when the Scheduling Information needs to be transmitted without any higher-layer data, the specific HARQ profile should be applied. Each HARQ process which is associated with a buffer holding a MAC-e PDU for potential retransmission shall maintain the HARQ profile and the number of re-transmissions that have occurred. For 1.28 Mcps TDD, the HARQ process shall also maintain the value of RTX_TIMER.

Further information on E-TFC selection is provided in Annex CA.

From 25.331 clause 8.6.5.18:

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

[…]

1> for FDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> if the TTI configured on the E-DCH equals 2ms, and the IE "2ms non-scheduled transmission grant HARQ process allocation" is configured for this MAC-d flow:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e PDU transmitted by HARQ processes allowed by the IE "2ms non-scheduled transmission grant HARQ process allocation", with a total contribution from this MAC-d flow not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

3> else:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall be included in a MAC-e PDU transmitted by any HARQ process, with a total contribution from this MAC-d flow not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

1> for TDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e PDU transmitted by HARQ processes designated as non scheduled (Ids 4 – 7) in the TTIs indicated (as determined from the IEs "Activation Time", "Resource Duration" and "Resource Periodicity").

2> if the IE "Scheduled transmission grant info" is included:

3> transmission of MAC-d PDUs for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH (see [15]).

Reference(s)

TS 25.321 clause 11.8.1.4, 11.9.1.4, TS 25.331 clause 8.6.5.18

7.1.6.2.8.3 Test purpose

To verify that the UE is able to handle combined non-scheduled and scheduled transmissions.

7.1.6.2.8.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4d (FDD) /6.11.5.4.7.7(1.28Mcps TDD) using condition A15 (FDD) /A14 (1.28Mcps TDD) as specified in clause 9.1 of TS 34.108. The following parameters are specific for this test case with the logical channel, transport channel and queue identities are set to:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
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
E-DCH MAC-d flow multiplexing list	11111111 (See 25.331 10.3.5.1b) Note 1
E-TFCI table	Table 0 for 10 ms TTI (FDD)
E-TFCI table	5ms TTI E-DCH Transport Block Size Table 0(1.28Mcps TDD)
Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

The UE is placed into UE test loop mode 1 with the UL SDU size for LCH 1 set to (25*41)-2 octets and LCH 2 size set to 39 octets.

Test procedure

The UE is configured with a non-scheduled grant on MAC-d flow 2, and the value of the “Max MAC-e PDU contents size” is 500 bits. The UE is not given any grant to transmit on MAC-d flow 3 (LCH 2).

a) The SS has not issued any grant for E-DCH on MAC-d flow 3 (LCH 2)

b) The SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH 2

c) The SS transmits 1 SDU of size 40 bytes (plus 1 byte RLC length indicator) on LCH 1

d) The SS waits until data is received and checks that the first TTI contains only data on LCH 1

e) The SS issues an absolute grant that allows the UE to send with a high rate on LCH 2 (well above 1 SDU/TTI) immediately after the previous step (i.e. not more than one TTI after the first data on LCH 1 has been looped back).

f) The SS receives data from the two logical channels LCH 1 and LCH 2 in one TTI.

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

Expected sequence

Step	Direction		Message	Comments
	UE	SS
1	ß		1 RLC PDU on LCH 2	SDU size is 40 bytes
2	ß		1 RLC PDU on LCH 1	SDU size is 40 bytes
2a	à		SI indicating data on LCH 2	Step 2a and 3 can happen in any order
3	à		MAC es PDU containing 1 RLC PDU on LCH 1
4	ß		Absolute grant allowing the UE to transmit with high data rate on LCH 2	Signalling value 31
5	à		MAC es PDU containing 1 RLC PDU on LCH 1 and 1 RLC PDU on LCH 2	Before and after this step, SS continues to receive 1 RLC PDU on LCH 1 per TTI, until complete SDU consisting of 25 PDU’s is received.
6	ß		Removal of absolute grant	Signalling value 1

Specific Message Contents

None

7.1.6.2.8.5 Test requirements

1. In step 3, the SS shall receive 1 MAC-es PDU containing 1 RLC PDU on LCH 1.

2. In step 5, the SS shall receive 1 MAC-es PDU containing 1 RLC PDU on LCH 1 and 1 RLC PDU on LCH 2 within the same TTI.

7.1.6.2.9 MAC-es/e Correct handling of HARQ profile power offsets

7.1.6.2.9.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.9.2 Conformance requirement

In FDD mode, the rules for E-TFC selection provided below shall apply to UEs in CELL_DCH state with an E-DCH transport channel configured. These UEs shall apply the E-TFC selection procedure when invoked by the HARQ entity (see subclause 11.8.1.1.1). In the case where a 2ms TTI is configured, E-TFC selection shall not be performed for TTIs that overlap with an uplink compressed mode gap. The E-TFC restriction procedure described in [12] shall always be applied before the E-TFC selection process below. Furthermore, for UEs that are also configured with a DCH transport channel on uplink, the TFC selection procedure shall be applied before either of these.

For each MAC-d flow, RRC configures MAC with a HARQ profile and a multiplexing list. Additionally, RRC configures MAC with a power offset for "Control-only" transmissions. This power offset and a maximum number of HARQ transmissions of 8 will be used to define a HARQ profile for "Control-only" transmissions which will be used, in case the Scheduling Information needs to be transmitted without any higher-layer data. The HARQ profile includes the power offset and maximum number of HARQ transmissions to use for this MAC-d flow. The multiplexing list identifies for each MAC-d flow(s), the other MAC-d flows from which data can be multiplexed in a transmission that uses the power offset included in its HARQ profile.

For each configured MAC-d flow, a given E-TFC can be in any of the following states:

– Supported state;

– Blocked state.

At each TTI boundary, UEs in CELL_DCH state with an E-DCH transport channel configured shall determine the state of each E-TFC for every MAC-d flow configured based on its required transmit power versus the maximum UE transmit power (see [7] and [12]). If no DCH transport channel is configured or if a DCH transport channel is configured and the selected TFC is "empty" (see [3]), the UE shall consider that E-TFCs included in the minimum set of E-TFCs are always in supported state (see [7]).

At every TTI boundary for which a new transmission is requested by the HARQ entity (see subclause 11.8.1.1.1), the UE shall perform the operations described below. UEs configured both with DCH and E-DCH transport channels shall perform TFC selection before performing E-TFC selection.

The Serving Grant Update function provides the E-TFC selection function with the maximum E-DPDCH to DPCCH power ratio that the UE is allowed to allocate for the upcoming transmission for scheduled data (held in the Serving Grant state variable – see subclause 11.8.1.3).

The HARQ process ID for the upcoming transmission is determined using the following formulae:

– For 2ms TTI: CURRENT_HARQ_PROCESS_ID = [5*CFN + subframe number] mod HARQ_RTT

– For 10ms TTI: CURRENT_HARQ_PROCESS_ID = [CFN] mod HARQ_RTT

Based on this current HARQ process ID and the RRC configuration, the UE shall determine whether to take the scheduled and non-scheduled grants into account in the upcoming transmission. If they are not supposed to be taken into account, then the corresponding grant shall be assumed to not exist. If the variable Serving_Grant has the value "Zero_Grant" after the Serving Grant Update, then the Serving Grant shall not be taken into account in the upcoming transmission.

When Scheduling Information is triggered per subclause 11.8.1.6, the E-TFC selection and data-allocation process shall assume that a non-scheduled grant is available for its transmission and that Scheduling Information has a priority higher then any other logical channel. Furthermore the HARQ process used for the upcoming transmission shall be assumed to be active and not L3 restricted for the transmission of the Scheduling Information, i.e. transmission of Scheduling Information can take place on this process.

The transmission format and data allocation shall follow the requirements below:

– Only E-TFCs from the configured E-TFCS shall be considered for the transmission;

– The power offset for the transmission is the one from the HARQ profile of the MAC-d flow that allows highest-priority data to be transmitted. If more than one MAC-d flow allows data of the same highest priority to be transmitted, it is left to implementation to select which MAC-d flow to prefer);

– In case the variable Serving_Grant has the value "Zero_Grant" after the Serving Grant Update function and there is no data available for MAC-d flows for which non-scheduled grants were configured and the transmission of Scheduling Information has been triggered, the "Control-only" HARQ profile configured by the higher layers shall be used.

– The Nominal Power Offset shall be set to the power offset included in the transmission HARQ profile;

– The data allocation shall maximize the transmission of higher priority data;

– The amount of data from MAC-d flows for which non-scheduled grants were configured shall not exceed the value of the non-scheduled grant;

– If a 10ms TTI is configured and the TTI for the upcoming transmission overlaps with a compressed mode gap, the Serving_Grant provided by the Serving Grant Update function shall be scaled back as follows:

where SG’ represents the modified serving grant considered by the E-TFC selection algorithm and N_C represents the number of non DTX slots in the compressed TTI;

– The Scheduling Information is always sent when triggered;

– Only E-TFCs in supported state shall be considered;

– The E-TFC resulting in the smallest amount of padding for the selected MAC-es PDUs and corresponding MAC-e/es headers, shall be selected including the case when the Scheduling Information needs to be transmitted.

Once an appropriate E-TFC and data allocation are found according to the rules above, the "Multiplexing and TSN Setting” entity shall generate the corresponding MAC-e PDU.

The E-TFC selection function shall provide this MAC-e PDU and transmission HARQ profile to the HARQ entity. The maximum number of HARQ transmissions and the power offset in this profile, shall be set respectively to the maximum of the Max Number of HARQ Transmissions of the HARQ profiles from all the MAC-d flows from which data is multiplexed into the transmission and to the Nominal Power Offset. The HARQ entity shall also be informed of whether the transmission includes Scheduling Information and whether this information is sent by itself or with higher-layer data.

Reference(s)

TS 25.321 clause 11.8.1.4

7.1.6.2.9.3 Test purpose

The purpose of this test case is to verify that the UE applies different HARQ profiles from different MAC-d flows to E-DCH transmissions accordingly and in case data from two MAC-d flows is transmitted in the same E-DCH transmission, the UE selects the correct power offset.

7.1.6.2.9.4 Method of test

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4d using condition A15 as specified in clause 9.1 of TS 34.108. The logical channel, transport channel and queue identities are set to:

Logical Channel ID	MAC-d flow (UL)	Priority	Comment
7 (LCH1)	2	1	RB25
8 (LCH2)	3	2	RB17
Note: The RAB combination also includes SRBs on E-DCH on MAC-d flow 1 which is not used in the testcase

The following parameters are specific for this test case:

Parameter	Value
E-DCH MAC-d flow multiplexing list for MAC-d flow 2	11111111 (See 25.331 10.3.5.1b) Note 1
E-DCH MAC-d flow multiplexing list for MAC-d flow 3	11111111 (See 25.331 10.3.5.1b) Note 1
Power offset for MAC-d flow 2	3dB (see 25.331 subclause 10.3.5.1b)
Power offset for MAC-d flow 3	0dB (see 25.331 subclause 10.3.5.1b)
Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

The radio bearer is placed into UE test loop mode 1 with the UL SDU size set to 39 octets for RB 25 and RB17.

Test procedure

The UE is configured with two logical channels, LCH1 (with priority 1) and LCH2 (with priority 2). LCH1 is mapped to MAC-d flow 2 and LCH2 is mapped to MAC-d flow 3.

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

b) SS transmits 2 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

c) SS waits until an SI is received.

d) The SS issues primary absolute grant corresponding to 1 RLC PDU of size 41 octets per TTI when the Mac-d flow power offset is 3dB (signalling value 5), with Absolute Grant Scope set as "All HARQ processes".

e) SS starts receiving loop backed RLC PDU’s.

f) The SS issues primary absolute grant corresponding to “ZERO GRANT”, with Absolute Grant Scope set as "All HARQ processes".

g) SS transmits 4 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH2.

h) SS waits until an SI is received.

i) The SS issues primary absolute grant corresponding to 2 RLC PDUs of size 41 octets per TTI when the Mac-d flow power offset is 0dB (signalling value 5), with Absolute Grant Scope set as "All HARQ processes".

j) SS starts receiving loop backed RLC PDU’s.

k) The SS issues primary absolute grant corresponding to “ZERO GRANT”, with Absolute Grant Scope set as "All HARQ processes".

l) SS transmits 2 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH2.

m) SS waits until an SI is received.

n) SS transmits 2 SDUs of size 40 bytes (plus 1 byte RLC length indicator) on LCH1.

o) SS waits until an SI is received.

p) The SS issues primary absolute grant corresponding to 3 RLC PDUs of size 41 octets per TTI when the Mac-d flow power offset is 3dB (signalling value 9), with Absolute Grant Scope set as "All HARQ processes".

q) SS starts receiving loop backed RLC PDU’s.

Expected sequence

Step	Direction		Message	Comments
Step	UE	SS	Message	Comments
1	ß		2 RLC PDUs on LCH 1
2	à		SI indicating data on LCH 1
3	ß		Primary Absolute grant allowing the UE to transmit 1 RLC PDU per TTI	Signalling value 5
4	à		MAC es PDU containing 1 RLC SDU from LCH 1	This step is repeated until all the RLC SDUs are transmitted
5	ß		Primary Absolute grant set to ‘ZERO GRANT’ and scope ‘All HARQ Processes’
6	ß		4 RLC PDUs on LCH 2
7	à		SI indicating data on LCH 2
8	ß		Primary Absolute grant allowing the UE to transmit 2 RLC PDU per TTI	Signalling value 5
9	à		MAC es PDU containing 2 RLC SDU from LCH 2	This step is repeated until all the RLC SDUs are transmitted
10	ß		Primary Absolute grant set to ‘ZERO GRANT’ and scope ‘All HARQ Processes’
11	ß		2 RLC PDUs on LCH 2
12	à		SI indicating data on LCH 2
13	ß		2 RLC PDUs on LCH 1
14	à		SI indicating data on LCH 1
15	ß		Primary Absolute grant allowing the UE to transmit 3 RLC PDUs per TTI	Signalling value 9
16	à		MAC es PDU containing 2 RLC PDU’s from LCH 1 and MAC es PDU containing 1 RLC PDU from LCH 2
17	à		MAC es PDU containing 1 RLC PDU from LCH 2

Specific Message Contents

None

7.1.6.2.9.5 Test requirements

1. In step 4, UE shall loop back PDUs for two TTIs, with one RLC PDU per TTI.

2. In step 9, UE shall loop back PDUs for two TTIs, with two RLC PDUs per TTI.

3. In step 16, UE shall loop back PDUs for one TTI, with three RLC PDU per TTI (2 RLC PDU’s from LCH1 and 1 RLC PDU from LCH 2).

4. In step 17, UE shall loop back PDU for one TTI, with one RLC PDU per TTI (1 RLC PDU from LCH 2).

7.1.6.2.9a MAC-es/e Correct handling of HARQ profile (1.28Mcps TDD)

7.1.6.2.9a.1 Definition and applicability

All UEs which support E-DCH.

7.1.6.2.9a.2 Conformance requirement