7.1.7 E-DCH MAC-i/is

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

7.1.7.1 MAC-i/is multiplexing (multiple PDUs from different LC in one TTI)

7.1.7.1.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is.

7.1.7.1.2 Conformance Requirement

From 25.321 clause 9.1.5:

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

[…]

From 25.331 clause 8.6.5.18:

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

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

Reference(s)

TS 25.321 clause 9.1.5, TS 25.331 clause 8.6.5.18

7.1.7.1.3 Test purpose

1. To verify that the UE multiplexes data from multiple PDUs from different logical channels in the same TTI

7.1.7.1.4 Method of test

Initial conditions

System Simulator:

1 cells, default parameters, Ciphering Off

User Equipment:

The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the Radio Bearers according to clause 6.11.4k.4 (FDD) / 6.11.5.4.9.4(1.28Mcps TDD) (Flexible RLC + MAC-i/is + MAC-ehs) using condition A26 (FDD) / A22(1.28Mcps TDD). The MAC-d flows are configured for scheduled transmissions. The following parameters are specific for this test case with the logical channel, transport channel and queue identities set to:

Logical Channel ID

MAC-d flow (UL)

Priority

Comment

7 (LCH1)

2

6

RB26

8 (LCH2)

3

7

RB27

9 (LCH3)

4

8

RB21

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

The following parameters are specific for this test case

Parameter

Value

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99) (FDD)

E-DCH MAC-d flow multiplexing list

Flow 2 = 00101000

Flow 3 = 00010000

Flow 4 = 00101000

See 25.331 10.3.5.1b

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

Test procedure

The UE is configured with three logical channels, LCH1 (with priority 6), LCH2 (with priority 7) and LCH3 (with priority 8). LCH1 is mapped to MAC-d flow 2, LCH2 is mapped to MAC-d flow 3 and LCH3 is mapped to MAC-d flow 4.

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 LCH3

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

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

e) The SS waits for an SI to be received that indicates that data is available on all three 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 (FDD only), allowing a rate well above 3 SDUs/TTI)

f) The SS waits until data is received and verifies that data from LCH1 and LCH3 are received in the same TTI and data from LCH2 is received in the next TTI

NOTE: The UE may send an SI after step 1 or step 2 but these SI’s would only indicate data on LCH3, LCH2 or LCH2 and LCH3. These will be ignored.

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

1 RLC PDU on LCH 3

2

ß

1 RLC PDU on LCH 2

3

ß

1 RLC PDU on LCH 1

4

à

Potential SI indicating data on LCH3, LCH2 or LCH2 and LCH3

These SI are ignored by the SS

5

à

SI indicating data on LCH 1 LCH 2 and LCH3

This can be verified from the indicated fraction of data on LCH1, LCH2 and LCH3

6

ß

Absolute grant allowing UE to transmit on E-DCH

This grant must be sufficiently high to allow a rate corresponding to at least 3 RLC PDUs/TTI, signalling value 10 for FDD

7

à

MAC-i PDU containing 1 RLC PDU on LCH 1 and 1 RLC PDU on LCH 3

Data on LCH1 and LCH2 should be received in the same TTI

8

à

MAC-i PDU containing 1 RLC PDU on LCH 2

Data on LCH2 in the next TTI

Specific Message Contents

None.

7.1.7.1.5 Test requirements

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

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

3. In step 8, the SS shall receive 1 RLC PDU on LCH2 in the next TTI

7.1.7.2 MAC-i/is segmentation / Correct Usage of Segmentation Status Field

7.1.7.2.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is.

7.1.7.2.2 Conformance requirement

The transmitting UM RLC entity segments the RLC SDU into UMD PDUs of appropriate size, if the RLC SDU is larger than the length of available space in the UMD PDU. The size of the UMD PDUs after segmentation and/or concatenation shall be smaller than or equal to the largest UL UMD PDU size. If MAC-i/is has been configured and the RLC PDU size is set to "flexible size", the size of the UMD PDUs after segmentation and/or concatenation shall be larger than or equal to the Minimum UL RLC PDU size. If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size. The UMD PDU may contain segmented and/or concatenated RLC SDUs. UMD PDU may also contain padding to ensure that it is of a valid length. Length Indicators are used to define boundaries between RLC SDUs within UMD PDUs unless the "Extension bit" already indicates that a UMD PDU contains exactly one complete SDU. Length Indicators are also used to define whether Padding is included in the UMD PDU.

…

– in uplink, the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. It is allowed to concatenate up to the largest UL AMD PDU size for Acknowledged mode data and largest UMD PDU size for Unacknowledged mode data. The "Length Indicator" field is used to point the borders between RLC SDUs (see subclause 9.2.2.8). If data to be transmitted is not enough to create a UMD PDU of the minimum size, it is allowed to create a UMD PDU including all data to be transmitted, even if the resulting size is smaller than the Minimum UL RLC PDU size.

– in uplink, if MAC-i/is has been configured:

– if the UE pre-generates RLC PDUs for transmission in a later TTI:

– provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen so that each RLC PDU to be multiplexed to the MAC-i/is PDU matches the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.

– RLC PDUs may only be pre-generated if the amount of data in outstanding pre-generated RLC PDUs for this logical channel is less than or equal to four times the maximum amount of data allowed to be transmitted by the applicable current grant (scheduled or non-scheduled) for the current TTI.

– if the UE generates RLC PDUs for transmission in the current TTI:

– the size of the data field of the RLC PDU shall be chosen so that the RLC PDU size matches the data requested for this logical channel by the current E-TFC selection.

…

There are two different MAC PDU formats for E-DCH. Depending on configuration by upper layers the format is either MAC-e/es or MAC-i/is. The MAC PDU format is determined by upper layer signalling [7].

…

– Segmentation Status (SS):
The Segmentation Status (SS) field provides indication of the segmentation status of the MAC SDU or segment of MAC SDU belonging to the logical channel identified by the LCH-ID field. The length of the SS field is 2 bits.

Table 9.2.4.3-1: Structure of the SS field

SI Field

Segmentation indication

00

The first MAC-is SDU of the MAC-is PDU is a complete MAC-d PDU.

The last MAC-is SDU of the MAC-is PDU is a complete MAC-d PDU.

01

If there are more than one MAC-is SDUs in the MAC-is PDU, the last MAC-is SDU of the MAC-is PDU is a complete MAC-d PDU.

The first MAC-is SDU of the MAC-is PDU is the last segment of a MAC-d PDU.

10

If there are more than one MAC-is SDUs in the MAC-is PDU, the first MAC-is SDU of the MAC-is PDU is a complete MAC-d PDU.

The last MAC-is SDU of the MAC-is PDU is the first segment of a MAC-d PDU.

11

If there are more than one MAC-is SDUs in the MAC-is PDU, the first MAC-is SDU of the MAC-is PDU is the last segment of a MAC-d PDU and the last MAC-is SDU of MAC-is PDU is the first segment of a MAC-d PDU.

If there is only one MAC-is SDU in the MAC-is PDU, the MAC-is SDU is a middle segment of a MAC-d PDU.

[…]

There is one segmentation entity per logical channel in the UE.

When the MAC-d PDU size, the untransmitted part of the MAC-d PDU, the MAC-c PDU size (FDD only) or the untransmitted part of the MAC-c PDU (FDD only) exceeds available space in the transport block according to the E-TFC selection, the segmentation entity shall:

– segment the MAC-d PDU, the untransmitted part of the MAC-d PDU, the MAC-c PDU or the untransmitted part of the MAC-c PDU to fit the available space in the transport block according to the E-TFC selection and store the untransmitted part of the MAC-d PDU or MAC-c PDU;

– set the segmentation status (SS) field of the transmission to indicate the segmentation status as described in subclause 9.2.4.3.

Reference(s)

TS 25.322 clause 4.2.1.2.1, 9.2.2.9

TS 25.321 clauses 9.1.5, 9.2.4.3, 11.8.1.2a

7.1.7.2.3 Test purpose

To test UE is able to segment data at MAC layer and use all 4 SS values in MAC-is header.

7.1.7.2.4 Method of test

Initial conditions

Downlink length indicators of size 15 shall be used

Uplink length indicator of size 15 shall be used

Test procedure

The following parameters are specific for this test case:

Parameter

Value

Minimum UL RLC PDU

1600 bits

Largest UL RLC PDU size

1600 bits

Max_RLC_PDU_size

200 octets

Periodicity for scheduling info

No periodic scheduling info

E-TFCI table

Table 0 for 10 ms TTI (FDD), 5ms TTI E-DCH Transport Block Size Table 0(1.28Mcps TDD)

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

  1. The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed with all the parameters as specified in the procedure, with the exception that the default Radio Bearer is replaced with the RB according to clause 6.11.4k.2 (FDD) /6.11.5.4.9.2 (1.28Mcps TDD) (UM Flexible RLC + MAC-i/is + MAC-ehs) using condition A27 (FDD) /A23 (1.28Mcps TDD) with RB mapping to HS-DSCH and E-DCH. The MAC-d flow of the RB is configured for scheduled transmissions.
  2. The radio bearer is placed into UE test loop mode 1 and configured to return UL RLC SDUs of the same size as received in DL.
  3. The SS transmits two RLC SDUs (SDU1, SDU2) of size 40 and 60 octets respectively. The SDUs are concatenated into a single RLC PDU. Length indicators are used to indicate the end of each SDU.
  4. The SS waits for an SI to be received that indicates that data is available (can be identified from the content of the SI).
  5. The SS issues a scheduled grant that allows the UE to transmit SDU1 and the first segment of the SDU2.
  6. UE loops back SDU1 and a segment of SDU2 in first TTI and the remainder of SDU2 in the next TTI.

TSN = 0, SS = 10, for MAC-is header in first TTI, TSN = 1, SS = 01 for MAC-is header in the next TTI.

  1. The SS removes the scheduling grant for the UE.
  2. The SS transmits three RLC SDUs (SDU3, SDU4, SDU5) of size 20, 30, 10 octets, respectively. The SDUs are concatenated into a single RLC PDU. Length indicators are used to indicate the end of each SDU.
  3. The SS waits for an SI to be received that indicates that data is available.
  4. The SS issues a scheduled grant that allows the UE to transmit the 3 SDUs.
  5. UE loops back SDU3, SDU4, SDU5 in the same TTI.

TSN = 2, SS = 00, for MAC-is header.

  1. The SS removes the scheduling grant for the UE.
  2. SS transmits one RLC (SDU6) of size 198 octets with no Length Indicator and Alternative E-bit interpretation (bit value 0) in the UM header.
  3. The SS waits for an SI to be received that indicates that data is available.
  4. The SS issues an absolute grant (grant value 5) which restricts the UE to transmit less than 300 bits per TTI. The current grant is less than the minimum UL RLC PDU size.
  5. UE loops back the contents of SDU6 in consecutive MAC-i PDUs.

SS = 10, and MAC-is PDU4 containing first segment of SDU6.

SS = 11, and MAC-is PDUs containing the middle segments of SDU6.

SS = 01, and MAC-is PDU containing the last segment of SDU6.

All MAC-is PDUs should have sequential sequence numbers starting from TSN = 3 for MAC-is PDU4

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

RB ESTABLISHMENT

See generic procedures

2

Close UE test loop

3

DOWNLINK RLC SDUs (SDU1, SDU2)

SDU1 = 40 octets, SDU2 = 60 octets

4

à

SI indicating data

5

Absolute grant allowing the UE to transmit SDU1 and a segment of SDU2

Grant value 4 for FDD

6

MAC-is PDU1, TSN = 0

TSN = 0, SS = 10

MAC-is PDU consisting of SDU1 and the first segment of SDU2

7

MAC-is PDU2, TSN = 1

TSN = 1, SS = 01

MAC-is PDU consisting of last segment of SDU2

8

Removal of absolute grant

Signalling value 1 (FDD only)

9

DOWNLINK RLC SDUs (SDU3, SDU4, SDU5)

SDU3 size = 20, SDU4 size = 30, SDU5 size = 10

10

à

SI indicating data

11

Absolute grant of sufficient value to allow the UE to transmit SDU3, SDU4 and SDU5

Grant value 10 for FDD

12

MAC-is PDU3, TSN = 2

TSN=2, SS=00, MAC-is PDU consisting of SDU3, SDU4, SDU5.

Removal of absolute grant

Signalling value 1 (FDD only)

13

DOWNLINK RLC SDU6

DL RLC SDU size = 198 Octets

14

à

SI indicating data

15

Absolute grant allowing the UE to transmit segments of SDU6.

Grant value 5 for FDD

The current grant is less than the minimum UL PDU size

16

UPLINK MACis PDUs

TSN = 3, SS = 10 for MAC-is PDU 4 contains first segment of SDU6. The last MAC-is PDU contains the final segment of SDU6, SS = 01. The other MAC-is PDUs contain the middle segments of SDU6, SS = 11.

17

Open UE test loop

18

RB release

7.1.7.2.5 Test requirements

a) In step 6, UE loop backs RLC SDU1 and first segment of RLC SDU2 in MAC-i PDU.

b) In step 7, UE loop backs the final segment of RLC SDU2 in MAC-i PDU.

c) In step 12, UE loops back RLC SDU3, SDU4, SDU5 in a single MAC-i PDU.

d) In step 16, UE loops back RLC SDU6 in several TTIs. In the first MAC-i PDU has SS = 10, containing the first segment of SDU6, the succeeding MAC-i PDUs contain the middle segments of SDU6, SS = 11 and the final MAC-i PDU contains the final segment of SDU6, SS = 01.

7.1.7.3 Correct settings of MAC-i/is header fields

7.1.7.3.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is

7.1.7.3.2 Conformance requirement

Extract from 25.321:

[…]

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

[…]

– Transmission Sequence Number (TSN):
The TSN field provides the transmission sequence number for the MAC-is 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.

– Segmentation Status (SS):
The Segmentation Status (SS) field provides indication of the segmentation status of the MAC SDU or segment of MAC SDU belonging to the logical channel identified by the LCH-ID field. The length of the SS field is 2 bits.

[…]

– Length (L):
The L field provides the length of the MAC-is SDU in octets. The size can vary for each SDU in the MAC-is PDU, and is set for each SDU individually. The length of the Length field is 11 bits.

– Logical channel identifier (LCH-ID):
The LCH-ID field provides identification of the logical channel at the receiver and the re-ordering buffer destination of a MAC-is SDU. In FDD, one LCH-ID value is reserved to indicate that the UE’s E-RNTI is included in the MAC-i header. The length of the LCH-ID is 4 bits.

Table 9.2.4.4-1: Structure of the LCH-ID field (FDD only)

LCH-ID Field

Designation

0000

Logical channel 1

0001

Logical channel 2

…

…

1101

Logical channel 14

1110

Identification of CCCH (SRB0)

1111

Identification of E-RNTI being included.

Table 9.2.4.4-2: Structure of the LCH-ID field (1.28 Mcps TDD only)

LCH-ID Field

Designation

0000

Logical channel 1

0001

Logical channel 2

…

…

1101

Logical channel 14

1110

Identification of CCCH (SRB0)

1111

Reserved

– Flag (F):
The F field is a flag indicating if more fields are present in the MAC-i header or not. If the F field is set to "0" the F field is followed by an additional set of LCH-ID, L and F fields. If the F field is set to "1" the F field is followed by a MAC-is PDU. Each header extension corresponds to one MAC-is SDU.

Reference(s)

TS 25.321 clauses 9.1.5, 9.2.4.3, 9.2.4.4

7.1.7.3.3 Test purpose

The purpose of this test case is to verify that the UE sets the MAC-i/is header fields in the correct way for multiple logical channels on multiple flows mapped onto a single MAC-i PDU.

7.1.7.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.4k.4 (FDD) / 6.11.5.4.9.4(1.28Mcps TDD) using condition A26 (FDD) /A22 (1.28Mcps TDD) in UM 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

6

RB26

8 (LCH2)

3

7

RB27

9 (LCH3)

4

8

RB21

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)

E-DCH MAC-d flow multiplexing list

11111111 (See 25.331 10.3.5.1b) Note 1

Largest UL RLC PDU size

20 bytes (Note 2)

Note 1: This configuration means that all MAC-d flows can be multiplexed in the same TTI

Note 2: The actual value is (IE value * 8) + 16

The UE is placed into UE test loop mode 1 and the loopback is configured to return UL RLC SDUs of the same size as received the received DL RLC SDU for each radio bearer.

Test procedure

The UE is configured with three logical channels, LCH1 (with priority 6), LCH2 (with priority 7) and LCH3 (with priority 8). LCH1 is mapped to MAC-d flow 2, LCH2 is mapped to MAC-d flow 3 and LCH3 is mapped to MAC-d flow 4.

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

b) The SS transmits 4 SDUs of sizes 20, 60, 30, 40 bytes on LCH2 in the same TTI

c) The SS waits for an SI indicating data on LCH2

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

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

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

g) The SS transmits three SDUs of size 40, 30, 40 bytes respectively on LCH3 in the same TTI

h) The SS transmits two SDU of size 20, 15 bytes respectively on LCH2 in the same TTI

i) The SS transmits one SDU of size 50 bytes on LCH1

j) The SS waits for SI indicating data on the 3 logical channels

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

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

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

n) The SS transmits two SDUs of size 40 bytes, on LCH2 in the same TTI

o) The SS waits for SI indicating data on LCH2

p) 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)

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

Expected sequence

Step

Direction

Message

Comments

UE

SS

1

ß

4 RLC SDUs on LCH 2 with sizes 20, 60, 30, 40 bytes respectively in the same TTI

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 4 RLC PDUs/TTI, signalling value 10 for FDD

4

à

1 MAC-is PDU containing 8 RLC PDUs on LCH 2

SS checks header fields

5

ß

Removal of scheduling grant for UE

Grant value 1 (FDD only)

6

ß

3 RLC SDUs on LCH 3, size 40, 30, 40 bytes respectively

Data sent in the same TTI

7

ß

2 RLC SDUs on LCH 2, size 20 and 15 bytes respectively

Data sent in the same TTI

8

ß

1 RLC SDUs on LCH 1, size 50 byes

9

à

Potential SI indicating data on LCH 3, LCH2, LCH1 or any combination

SS waits for SI indicating data on all logical channels

10

ß

Absolute grant allowing UE to transmit on E-DCH

This grant must be sufficiently high to allow a rate corresponding to at least 6 RLC PDUs/TTI, signalling value 10

11

à

3 MAC-is PDUs containing 3 RLC PDUs on LCH 1, 2 RLC PDUs on LCH 2 and 6 RLC PDUs on LCH3 respectively

SS checks header fields

12

ß

Removal of scheduling grant for UE

Grant value 1 (FDD only)

13

ß

2 RLC SDUs on LCH 2, size 40 bytes each

Data sent in the same TTI

14

à

SI indicating data on LCH 2

15

ß

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 for FDD

16

à

1 MAC-is PDU containing 4 RLC PDUs on LCH 2

SS checks header fields

Specific Message Contents

None

7.1.7.3.5 Test requirements

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

– For MAC-is header content,, TSN = 0, SS = 00

– The content of MAC-i headers received shall be set to :

LCH-ID = 0111’B, L = 22’D or 21’D, F = 0 header for MAC-is SDU1

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU2

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU3

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU4

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU5

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU6

LCH-ID = 0111’B, L = 22’D, F = 0 header for MAC-is SDU7

LCH-ID = 0111’B, L = 12’D, F = 1 header for MAC-is SDU8

2. After step 11, the SS shall receive 3 MAC-is PDUs where:

– For MAC-is PDU1:

TSN = 0, SS = 00, for The Content of MAC-I Header received shall be set to

LCH-ID = 0110’B, L = 22’D, F = 0

LCH-ID = 0110’B, L = 22’D, F = 0

LCH-ID = 0110’B, L = 12’D, F = 0

– FOR MAC-is PDU2

TSN = 1, SS = 00, the content of MAC-i headers received shall be set to :

LCH-ID = 0111’B, L = 22’D or 21’D, F = 0

LCH-ID = 0111’B, L = 17’D or 16’D, F = 0

– FOR MAC-is PDU3

TSN = 0, SS = 00, the content of MAC-i headers received shall be set to :

LCH-ID = 1000’B, L = 22’D, F = 0

LCH-ID = 1000’B, L = 22’D, F = 0

LCH-ID = 1000’B, L = 22’D, F = 0

LCH-ID = 1000’B, L = 22’D, F = 0

LCH-ID = 1000’B, L = 22’D, F = 0

LCH-ID = 1000’B, L = 12’D, F = 1

3. After step 16, the SS shall receive 1 MAC-is PDU where:

– The TSN is set to 2, SS = 00, the content of MAC-i headers received shall be set to :

LCH-ID = 0111’B , L = 22’D, F = 0

LCH-ID = 0111’B , L = 22’D, F = 0

LCH-ID = 0111’B , L = 22’D, F = 0

LCH-ID = 0111’B , L = 22’D, F = 1

7.1.7.4 MAC-is/i transport block size selection/ UL QPSK

7.1.7.4.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is.

7.1.7.4.2 Conformance requirement

Extract from TS 25.321 clause 11.8.1.4

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 UE shall not use the following E-TFCIs;

– If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI, it shall not use E-TFCI 120 in the mapping defined in Annex B.1

– If the UE is configured with E-TFCI table 1 (see [7]) and 2ms TTI, it shall not use E-TFCI 115 in the mapping defined in Annex B.2

– If the UE is configured with E-TFCI table 2 (see [7]) and 2ms TTI, it shall not use E-TFCI 121 in the mapping defined in Annex B.2a

– If the UE is configured with E-TFCI table 3 (see [7]) and 2ms TTI, it shall not use E-TFCIs 101 and 102 in the mapping defined in Annex B.2b

[…]

[…]

Extract from TS 25.321 clause 9.2.5.4

[…]

RRC can configure the MAC-e or MAC-i to use one of two Transport block size sets for the 10ms TTI duration and one of four Transport block size sets for the 2ms TTI duration. The normative description of the mapping between the E-TFCI and the corresponding transport block size is provided in Annex B:

– If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.1

– If the UE is configured with E-TFCI table 1 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2

– If the UE is configured with E-TFCI table 2 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2a

– If the UE is configured with E-TFCI table 3 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2b

– If the UE is configured with E-TFCI table 0 (see [7]) and 10ms TTI, it shall use the mapping defined in Annex B.3

– If the UE is configured with E-TFCI table 1 (see [7]) and 10ms TTI, it shall use the mapping defined in Annex B.4

[…]

Reference(s)

TS 25.321 clause 11.8.1.4, 9.2.5.4

7.1.7.4.3 Test purpose

To verify that the UE is able to transmit all possible transport block sizes when MAC-i/is is configured and within the UE capability.

7.1.7.4.4 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE in idle mode

The following parameters are specific for this test case:

Common for all UE HS-DSCH categories:

Parameter

Value

MAC-d PDU size

336 bits

MAC-ehs receiver window size

16

Number of HARQ processes

1

Number of reordering queues

1

Common for all UE E-DCH categories:

Parameter

Value

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99)

Specific depending on E-DCH category:

Parameter

E-DCH

Category

Value

RLC Transmission window size

1 to 5

512

6

1536

E-TFCI table

1 to 6

See table 7.1.6.3.2.5

Specific depending on HS-DSCH category:

Parameter

HS-DSCH

Category

Value

RLC Receiving window size

1 to 6

512

7 and 8

1536

9 and 10

2047

11 and 12

1024

Definition of test variables:

IE-TFCI

Index value used by SS to lock up the TB size used for the different test points

The mapping between the chosen E-TFC index and the corresponding E-DCH transport block size is given in the following tables:

Table 7.1.7.4.1: Test points for 2ms TTI E-DCH Transport Block Size Table 0

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

30

342

60

1015

90

3008

120

8913

Note

1

120

31

355

61

1053

91

3119

121

9241

2

124

32

368

62

1091

92

3234

122

9582

3

129

33

382

63

1132

93

3353

123

9935

4

133

34

396

64

1173

94

3477

124

10302

5

138

35

410

65

1217

95

3605

125

10681

6

143

36

426

66

1262

96

3738

126

11075

7

149

37

441

67

1308

97

3876

127

11484

8

154

38

458

68

1356

98

4019

9

160

39

474

69

1406

99

4167

10

166

40

492

70

1458

100

4321

11

172

41

510

71

1512

101

4480

12

178

42

529

72

1568

102

4645

13

185

43

548

73

1626

103

4816

14

192

44

569

74

1685

104

4994

15

199

45

590

75

1748

105

5178

16

206

46

611

76

1812

106

5369

17

214

47

634

77

1879

107

5567

18

222

48

657

78

1948

108

5772

19

230

49

682

79

2020

109

5985

20

238

50

707

80

2094

110

6206

21

247

51

733

81

2172

111

6435

22

256

52

760

82

2252

112

6672

23

266

53

788

83

2335

113

6918

24

275

54

817

84

2421

114

7173

25

286

55

847

85

2510

115

7437

26

296

56

878

86

2603

116

7711

27

307

57

911

87

2699

117

7996

28

318

58

944

88

2798

118

8290

29

330

59

979

89

2901

119

8596

Note: E-TFCI index 120 shall not be used by the UE (see TS 25.321 clause 11.8.1.4). The reason to include this test point is to verify that UE comply to this requirement and is not using E-TFCI index value 120.

Table 7.1.7.4.2: Test points for 2ms TTI E-DCH Transport Block Size Table 1

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

43

2724

86

7252

1

186

44

2742

87

7288

2

204

45

3042

88

7428

3

354

46

3060

89

7464

4

372

47

3078

90

7764

5

522

48

3298

91

7800

6

540

49

3316

92

7908

7

674

50

3334

93

7944

8

690

51

3378

94

8100

9

708

52

3396

95

8136

10

726

53

3414

96

8436

11

858

54

3732

97

8472

12

876

55

3750

98

8564

13

1026

56

3972

99

8600

14

1044

57

3990

100

8772

15

1062

58

4068

101

8808

16

1194

59

4086

102

9108

17

1212

60

4404

103

9144

18

1330

61

4422

104

9220

19

1348

62

4628

105

9256

20

1362

63

4646

106

9444

21

1380

64

4740

107

9480

22

1398

65

4758

108

9780

23

1530

66

5076

109

9816

24

1548

67

5094

110

9876

25

1698

68

5284

111

9912

26

1716

69

5302

112

10116

27

1734

70

5412

113

10152

28

1866

71

5430

114

10452

29

1884

72

5748

115

10488

Note

30

1986

73

5766

116

10532

31

2004

74

5940

117

10568

32

2022

75

5958

118

10788

33

2034

76

6084

119

10824

34

2052

77

6102

120

11124

35

2070

78

6420

121

11178

36

2370

79

6438

122

11188

37

2388

80

6596

123

11242

38

2406

81

6614

124

11460

39

2642

82

6756

125

11478

40

2660

83

6774

41

2678

84

7092

42

2706

85

7110

Note: E-TFCI index 115 shall not be used by the UE (see TS 25.321 clause 11.8.1.4). The reason to include this test point is to verify that UE comply to this requirement and is not using E-TFCI index value 115.

Table 7.1.7.4.3: Test points for 10ms TTI E-DCH Transport Block Size Table 0

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

30

389

60

1316

90

4452

120

15051

1

120

31

405

61

1371

91

4636

121

15675

2

124

32

422

62

1428

92

4828

122

16325

3

130

33

440

63

1487

93

5029

123

17001

4

135

34

458

64

1549

94

5237

124

17706

5

141

35

477

65

1613

95

5454

125

18440

6

147

36

497

66

1680

96

5680

126

19204

7

153

37

517

67

1749

97

5915

127

20000

8

159

38

539

68

1822

98

6161

9

166

39

561

69

1897

99

6416

10

172

40

584

70

1976

100

6682

11

180

41

608

71

2058

101

6959

12

187

42

634

72

2143

102

7247

13

195

43

660

73

2232

103

7547

14

203

44

687

74

2325

104

7860

15

211

45

716

75

2421

105

8186

16

220

46

745

76

2521

106

8525

17

229

47

776

77

2626

107

8878

18

239

48

809

78

2735

108

9246

19

249

49

842

79

2848

109

9629

20

259

50

877

80

2966

110

10028

21

270

51

913

81

3089

111

10444

22

281

52

951

82

3217

112

10877

23

293

53

991

83

3350

113

11328

24

305

54

1032

84

3489

114

11797

25

317

55

1074

85

3634

115

12286

26

331

56

1119

86

3784

116

12795

27

344

57

1165

87

3941

117

13325

28

359

58

1214

88

4105

118

13877

29

374

59

1264

89

4275

119

14453

Table 7.1.7.4.4: Test points for 10ms TTI E-DCH Transport Block Size Table 1

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

41

5076

82

11850

1

186

42

5094

83

12132

2

204

43

5412

84

12186

3

354

44

5430

85

12468

4

372

45

5748

86

12522

5

522

46

5766

87

12804

6

540

47

6084

88

12858

7

690

48

6102

89

13140

8

708

49

6420

90

13194

9

858

50

6438

91

13476

10

876

51

6756

92

13530

11

1026

52

6774

93

13812

12

1044

53

7092

94

13866

13

1194

54

7110

95

14148

14

1212

55

7428

96

14202

15

1362

56

7464

97

14484

16

1380

57

7764

98

14556

17

1530

58

7800

99

14820

18

1548

59

8100

100

14892

19

1698

60

8136

101

15156

20

1716

61

8436

102

15228

21

1866

62

8472

103

15492

22

1884

63

8772

104

15564

23

2034

64

8808

105

15828

24

2052

65

9108

106

15900

25

2370

66

9144

107

16164

26

2388

67

9444

108

16236

27

2706

68

9480

109

16500

28

2724

69

9780

110

16572

29

3042

70

9816

111

17172

30

3060

71

10116

112

17244

31

3378

72

10152

113

17844

32

3396

73

10452

114

17916

33

3732

74

10488

115

18516

34

3750

75

10788

116

18606

35

4068

76

10824

117

19188

36

4086

77

11124

118

19278

37

4404

78

11178

119

19860

38

4422

79

11460

120

19950

39

4740

80

11514

40

4758

81

11796

Table 7.1.7.4.5: Applicable E-TFS indexes for sub-tests 1 to 4 and UE E-DCH categories 1 to 6.

Applicable E-TFS indexes

Sub-test

E-DCH TTI

E-DCH Transport Block Size Table

Category 1

Category 2

Category 3

Category 4

Category 5

Category 6

1

10ms

10ms TTI Table 0,
Table 7.1.7.4.3

1..101

1..119

1..119

1..127

1..127

1..127

2

10ms

10ms TTI Table 1,
Table 7.1.7.4.4

1..54

1..99

1..99

1..120

1..120

1..120

3

2ms

2ms TTI Table 0,
Table 7.1.7.4.1

N/A

1..88

N/A

1..108

N/A

1..127

4

2ms

2ms TTI Table 1,
Table 7.1.7.4.2

N/A

1..44

N/A

1..73

N/A

1..125

NOTE 1: Applicable indexes depends on the UE capability of “Maximum number of bits of an E-DCH transport block transmitted within a 10 ms E-DCH TTI” and “Maximum number of bits of an E-DCH transport block transmitted within a 2 ms E-DCH TTI” as specified in TS 25.306 clause 5 and Table 5.1g. E-TFCI index=0 not tested as TB size for this E-TFCI value is 18 bits, which would only fit the MAC-i/is header used by the SS in the test procedure 1.

NOTE 2: For E-DCH categories beyond 6, E-TFS indices for category 6 are applicable.

Table 7.1.7.4.6: E-TFCI values causing degradation due to turbo coder irregularities

E-DCH Transport Block Size Tables

E-TFCI

Reference

2 ms TTI, Table 0

120

[6], Annex B.1

2 ms TTI, Table 1

115

[6], Annex B.2

Test procedure

The following test specs shall be executed for each applicable sub-test in Table 7.1.7.4.5:

a) The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4k.2 (UM, Flexible RLC + MAC-i/is + MAC-ehs) using conditions A27 as specified in clause 9.1 of TS 34.108. See Note 1.

b) The SS closes the test loop using UE test loop mode 1 and configuring the UL RLC SDU size to be equal to the received DL SDU size (i.e. not setting the UL RLC SDU size parameter).

c) The SS sets IE-TFCI =1.

d) The SS look up the TB Size based on the IE-TFCI value in the table used for the sub-test according to Table 7.1.7.4.5.

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

f) If the transport block size TBsize is >12040 bits then SS creates 2 DL RLC SDUs of size 8*FLOOR ((TBsize – 104 bit)/16) (largest possible RLC SDU size considering octet alignment and MAC-i/is and RLC UM headers). If the transport block size TBsize is ≤ 12040 bits the SS creates 1 DL RLC SDUs of size 8*FLOOR((TBsize – 32 bit)/8). The SS creates a DL RLC PDU for each DL RLC SDU using Alternative E-bit interpretation (‘0’) in the RLC PDU header and transmits in downlink. See note 2.

g) The SS waits for an SI to be received that indicates that there is data available for transmission (can be identified from the content of the SI). The SS checks that TEBS have the correct values. See Note 3.

h) The SS issues an absolute grant that allows the UE to send at maximum bit rate (signalling value 31)

i) The SS waits until data is received and verifies that the looped back SDU data has the correct content and is sent in the same TTI.

j) The SS verifies that the received E-TFC used by the UE is correct. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.4.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

k) The SS increments the IE-TFCI by 1. If the IE-TFCI value is less than maximum value for the actual sub-test and UE category according to Table 7.1.7.4.5 then continue with step d else continue with step l.

l) The SS opens the UE test loop.

m) The SS release the radio bearer.

n) The SS may optionally deactivate the radio bearer test mode.

NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test.

NOTE 2: The test data for DTCHs mapped on HS-DSCH is divided into 2 RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM). To allow for testing of the smallest TB sizes a single RLC PDU is used when the TB size is equal or below 12032 bits to reduce the L2 header overhead. 12032 bits corresponds to maximum RLC SDU size of 1500 octets (12000 bits) plus MAC-i/is header size of 24 bits and UMD PDU header size (8 bits).

The SS is using one RLC PDU per RLC SDU. The RLC SDU size is calculated as:
RLC SDU size = 8*FLOOR((TBsize – MAC-i/is header size)/N – UMD PDU header size)/8
= 8*FLOOR((TBsize – 24 – (N-1)*16)/N – UMD PDU header size)/8 bits.

For N=1 UMD PDU header size =8, this gives RLC SDU size = 8*FLOOR(TB size – 32)/8 bits.
For N=2 UMD PDU header size = 64(taking into account possible use of length indicators), this gives RLC SDU size = 8*FLOOR(TB size – 104)/16 bits

NOTE 3: The SS calculates the TEBS value using the E-TFC TB size determined by the E-TFCI value tested according to 25.321 Table 9.2.5.3.2-1.

Expected sequence

The expected sequence is repeated for each applicable sub-test in Table 7.1.7.4.5:

Step

Direction

Message

Comments

UE

SS

1

<–

SYSTEM INFORMATION (BCCH)

Broadcast

2

<–

PAGING TYPE 1 (PCCH)

Paging (PS domain, P-TMSI)

3

–>

RRC CONNECTION REQUEST (CCCH)

RRC

4

<–

RRC CONNECTION SETUP (CCCH)

RRC

5

–>

RRC CONNECTION SETUP COMPLETE (DCCH)

RRC

6

–>

SERVICE REQUEST (DCCH)

GMM

7

<–

SECURITY MODE COMMAND

RRC see note 1

8

–>

SECURITY MODE COMPLETE

RRC see note 1

9

<–

ACTIVATE RB TEST MODE (DCCH)

TC

10

–>

ACTIVATE RB TEST MODE COMPLETE (DCCH)

TC

11

<–

RADIO BEARER SETUP (DCCH)

RRC. For the PS radio bearer the ‘pdcp info’ IE shall be omitted.

12

–>

RADIO BEARER SETUP COMPLETE (DCCH)

RRC

13

<–

CLOSE UE TEST LOOP (DCCH)

TC

UE test mode 1 with no "LB Setup RB IE#k" parameter set (UE shall return an UL RLC SDU with the same size as the received RLC SDU in downlink)

14

–>

CLOSE UE TEST LOOP COMPLETE (DCCH)

TC

15

SS

The SS sets IE-TFCI = 1 and look up the transport block size from the relevant Transport Block Size Table for the sub-test.

16

ß

Removal of absolute grant

Signalling value 1

17

<–

DOWNLINK RLC SDU(s)

The SS creates and transmit one or 2 RLC SDUs. The number of RLC SDUs and their size depends on TB size under test.

18

à

SI indicating data for transmission

This can be verified from the indicated Total E-DCH Buffer Status (TEBS)

19

<–

Absolute grant allowing the UE to transmit at maximum bit rate.

Signalling value 31

20

–>

UPLINK RLC SDU(s)

The SS checks E-TFC from the UE and checks that the content of the received UL RLC SDU(s) are correct and sent in the same TTI.

The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.4.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

21

SS

The SS increments IE-TFCI by 1 and look up transport block size from the relevant Transport Block Size Table for the sub-test. If E-TFC TB size is supported by the E-DCH category then repeat steps 16 to 21 else continue with step 22.

22

<–

OPEN UE TEST LOOP (DCCH)

TC

23

–>

OPEN UE TEST LOOP COMPLETE (DCCH)

TC

24

RB RELEASE

RRC

25

<–

DEACTIVATE RB TEST MODE

TC

Optional step

26

–>

DEACTIVATE RB TEST MODE COMPLETE

TC

Optional step

Note 1: In addition to activate integrity protection Step 7 and Step 8 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.

7.1.7.4.5 Test requirements

1. In step 20, the SS verifies that the received E-TFC has the correct size. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.4.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

2. In step 20, the SS shall receive the RLC SDUs in the same TTI and with the same content as sent in downlink.

7.1.7.5 MAC-is/i transport block size selection/ UL 16QAM

7.1.7.5.1 Definition and applicability

Applicable for all UEs supporting MAC-i/is and UL 16QAM.

7.1.7.5.1 Conformance requirement

Extract from TS 25.321 clause 11.8.1.4

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 UE shall not use the following E-TFCIs;

– If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI, it shall not use E-TFCI 120 in the mapping defined in Annex B.1

– If the UE is configured with E-TFCI table 1 (see [7]) and 2ms TTI, it shall not use E-TFCI 115 in the mapping defined in Annex B.2

– If the UE is configured with E-TFCI table 2 (see [7]) and 2ms TTI, it shall not use E-TFCI 121 in the mapping defined in Annex B.2a

– If the UE is configured with E-TFCI table 3 (see [7]) and 2ms TTI, it shall not use E-TFCIs 101 and 102 in the mapping defined in Annex B.2b

[…]

[…]

Extract from TS 25.321 clause 9.2.5.4

[…]

RRC can configure the MAC-e or MAC-i to use one of two Transport block size sets for the 10ms TTI duration and one of four Transport block size sets for the 2ms TTI duration. The normative description of the mapping between the E-TFCI and the corresponding transport block size is provided in Annex B:

– If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.1

– If the UE is configured with E-TFCI table 1 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2

– If the UE is configured with E-TFCI table 2 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2a

– If the UE is configured with E-TFCI table 3 (see [7]) and 2ms TTI, it shall use the mapping defined in Annex B.2b

– If the UE is configured with E-TFCI table 0 (see [7]) and 10ms TTI, it shall use the mapping defined in Annex B.3

– If the UE is configured with E-TFCI table 1 (see [7]) and 10ms TTI, it shall use the mapping defined in Annex B.4

[…]

Reference(s)

TS 25.321 clause 11.8.1.4, 9.2.5.4

7.1.7.5.3 Test purpose

To verify that the UE is able to transmit all possible transport block sizes when 16QAM uplink and MAC-i/is is configured.

7.1.7.5.4 Method of test

NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-7 IE “E-DCH physical layer category extension”.

NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.

Initial conditions

System Simulator:

1 cell, default parameters, Ciphering Off.

User Equipment:

UE in idle mode

The following parameters are specific for this test case:

Common for all UE HS-DSCH categories:

Parameter

Value

MAC-d PDU size

336 bits

MAC-ehs receiver window size

16

Number of HARQ processes

1

Number of reordering queues

1

Common for all UE E-DCH categories:

Parameter

Value

Periodicity for Scheduling Info – no grant

500 ms (see 25.331 10.3.6.99)

RLC Poll Timer

1000ms

RLC Reset Timer

1000ms

Specific depending on E-DCH category:

Parameter

E-DCH

Category

Value

RLC Transmission window size

7

1536

E-TFCI table

7

See table 7.1.5.1.3

Specific depending on HS-DSCH category:

Parameter

HS-DSCH

Category

Value

RLC Receiving window size

1 to 6

512

7 and 8

1536

9 and 10

2047

11 and 12

1024

Definition of test variables:

IE-TFCI

Index value used by SS to lock up the TB size used for the different test points

The mapping between the chosen E-TFC index and the corresponding E-DCH transport block size is given in the following tables:

Table 7.1.7.5.1: Test points for 2ms TTI E-DCH Transport Block Size Table 2

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

30

402

60

1405

90

4913

120

17173

1

120

31

419

61

1465

91

5122

121

17904

Note

2

125

32

437

62

1528

92

5341

122

18667

3

130

33

455

63

1593

93

5568

123

19462

4

135

34

475

64

1661

94

5805

124

20291

5

141

35

495

65

1731

95

6053

125

21155

6

147

36

516

66

1805

96

6310

126

22056

7

154

37

538

67

1882

97

6579

127

22995

8

160

38

561

68

1962

98

6859

9

167

39

585

69

2046

99

7152

10

174

40

610

70

2133

100

7456

11

182

41

636

71

2224

101

7774

12

189

42

663

72

2319

102

8105

13

197

43

691

73

2417

103

8450

14

206

44

721

74

2520

104

8810

15

215

45

752

75

2628

105

9185

16

224

46

784

76

2740

106

9577

17

233

47

817

77

2856

107

9985

18

243

48

852

78

2978

108

10410

19

254

49

888

79

3105

109

10853

20

265

50

926

80

3237

110

11316

21

276

51

965

81

3375

111

11798

22

288

52

1007

82

3519

112

12300

23

300

53

1049

83

3669

113

12824

24

313

54

1094

84

3825

114

13370

25

326

55

1141

85

3988

115

13940

26

340

56

1189

86

4158

116

14534

27

354

57

1240

87

4335

117

15153

28

370

58

1293

88

4520

118

15798

29

385

59

1348

89

4712

119

16471

Note: E-TFCI index 121 shall not be used by the UE (see TS 25.321 clause 11.8.1.4). The reason to include this test point is to verify that UE comply to this requirement and is not using E-TFCI index value 121.

Table 7.1.7.5.2: Test points for 2ms TTI E-DCH Transport Block Size Table 3

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

IE-TFCI

TB Size (bits)

0

18

30

1902

60

6614

90

14184

120

21966

1

186

31

1986

61

6774

91

14538

121

22302

2

204

32

2004

62

7110

92

14874

122

22430

3

354

33

2034

63

7270

93

15210

123

22638

4

372

34

2052

64

7446

94

15546

124

22996

5

522

35

2370

65

7782

95

15882

6

540

36

2388

66

7926

96

16218

7

558

37

2642

67

8118

97

16554

8

674

38

2660

68

8454

98

16890

9

692

39

2706

69

8582

99

17226

10

708

40

2724

70

8790

100

17562

11

858

41

3042

71

9126

101

17802

Note

12

876

42

3060

72

9238

102

17898

Note

13

894

43

3298

73

9462

103

18252

14

1026

44

3316

74

9798

104

18476

15

1044

45

3378

75

9894

105

18588

16

1194

46

3396

76

10134

106

18924

17

1212

47

3750

77

10470

107

19132

18

1230

48

3990

78

10550

108

19260

19

1330

49

4086

79

10806

109

19596

20

1348

50

4422

80

11160

110

19788

21

1362

51

4646

81

11224

111

19932

22

1380

52

4758

82

11496

112

20268

23

1530

53

5094

83

11880

113

20444

24

1548

54

5302

84

12168

114

20604

25

1566

55

5430

85

12536

115

20940

26

1698

56

5766

86

12840

116

21100

27

1716

57

5958

87

13192

117

21276

28

1866

58

6102

88

13512

118

21612

29

1884

59

6438

89

13848

119

21774

Note: E-TFCI indices 101 and 102 shall not be used by the UE (see TS 25.321 clause 11.8.1.4). The reason to include this test point is to verify that UE comply to this requirement and is not using E-TFCI index values 101 and 102.

Table 7.1.7.5.3: Applicable E-TFS indexes for sub-tests 1 to 2 and UE E-DCH category 7.

Sub-test

E-DCH TTI

E-DCH Transport Block Size Table

Applicable E-TFS indexes

1

2ms

2ms TTI Table 2,
Table 7.1.7.4.2a

1..127

2

2ms

2ms TTI Table 3,
Table 7.1.7.4.2b

1..124

Table 7.1.7.5.4: E-TFCI values causing degradation due to turbo coder irregularities

E-DCH Transport Block Size Tables

E-TFCI

Reference

2 ms TTI, Table 2

121

[6], Annex B.2a

2 ms TTI, Table 3

101

[6], Annex B.2b

2 ms TTI, Table 3

102

[6], Annex B.2b

Test procedure

The following test specs shall be executed for each applicable sub-test in Table 7.1.7.5.5:

a) The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4k.2 (UM, Flexible RLC + MAC-i/is + MAC-ehs) using conditions A27a (16QAM) as specified in clause 9.1 of TS 34.108. See Note 1.

b) The SS closes the test loop using UE test loop mode 1 and configuring the UL RLC SDU size to be equal to the received DL SDU size (i.e. not setting the UL RLC SDU size parameter).

c) The SS sets IE-TFCI =1.

d) The SS look up the TB Size based on the IE-TFCI value in the table used for the sub-test according to Table 7.1.7.5.5.

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

f) If the transport block size TBsize is >12040 bits then SS creates 2 DL RLC SDUs of size 8*FLOOR ((TBsize – 56 bit)/16) (largest possible RLC SDU size considering octet alignment and MAC-i/is and minimum RLC UM headers). If the transport block size TBsize is ≤ 12040 bits the SS creates 1 DL RLC SDUs of size 8*FLOOR((TBsize – 32 bit)/8). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header and transmits in downlink. See note 2.

g) The SS waits for an SI to be received that indicates that there is data available for transmission (can be identified from the content of the SI). The SS checks that TEBS have the correct values. See Note 3.

h) The SS issues an absolute grant that allows the UE to send at maximum bit rate (signalling value 31)

i) The SS waits until data is received and verifies that the looped back SDU data has the correct content and is sent in the same TTI.

j) The SS verifies that the received E-TFC used by the UE is correct. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.5.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

k) The SS increments the IE-TFCI by 1. If the IE-TFCI value is less than maximum value for the actual sub-test and UE category according to Table 7.1.7.5.5 then continue with step d else continue with step l.

l) The SS opens the UE test loop.

m) The SS release the radio bearer.

n) The SS may optionally deactivate the radio bearer test mode.

NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test.

NOTE 2: The test data for DTCHs mapped on HS-DSCH is divided into 2 RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM). To allow for testing of the smallest TB sizes a single RLC PDU is used when the TB size is equal or below 12032 bits to reduce the L2 header overhead. 12032 bits corresponds to maximum RLC SDU size of 1500 octets (12000 bits) plus MAC-i/is header size of 24 bits and UMD PDU header size (8 bits).

The SS is using one RLC PDU per RLC SDU. The RLC SDU size is calculated as:
RLC SDU size = 8*FLOOR((TBsize – MAC-i/is header size)/N – UMD PDU header size)/8
= 8*FLOOR((TBsize – 24 – (N-1)*16)/N – 8)/8 bits.

For N=1 this gives RLC SDU size = 8*FLOOR(TB size – 32)/8 bits.
For N=2 this gives RLC SDU size = 8*FLOOR(TB size – 56)/16 bits

NOTE 3: The SS calculates the TEBS value using the E-TFC TB size determined by the E-TFCI value tested according to 25.321 Table 9.2.5.3.2-1.

Expected sequence

The expected sequence is repeated for each applicable sub-test in Table 7.1.7.5.5:

Step

Direction

Message

Comments

UE

SS

1

<–

SYSTEM INFORMATION (BCCH)

Broadcast

2

<–

PAGING TYPE 1 (PCCH)

Paging (PS domain, P-TMSI)

3

–>

RRC CONNECTION REQUEST (CCCH)

RRC

4

<–

RRC CONNECTION SETUP (CCCH)

RRC

5

–>

RRC CONNECTION SETUP COMPLETE (DCCH)

RRC

6

–>

SERVICE REQUEST (DCCH)

GMM

7

<–

SECURITY MODE COMMAND

RRC see note 1

8

–>

SECURITY MODE COMPLETE

RRC see note 1

9

<–

ACTIVATE RB TEST MODE (DCCH)

TC

10

–>

ACTIVATE RB TEST MODE COMPLETE (DCCH)

TC

11

<–

RADIO BEARER SETUP (DCCH)

RRC. For the PS radio bearer the ‘pdcp info’ IE shall be omitted.

12

–>

RADIO BEARER SETUP COMPLETE (DCCH)

RRC

13

<–

CLOSE UE TEST LOOP (DCCH)

TC

UE test mode 1 with no "LB Setup RB IE#k" parameter set (UE shall return an UL RLC SDU with the same size as the received RLC SDU in downlink)

14

–>

CLOSE UE TEST LOOP COMPLETE (DCCH)

TC

15

SS

The SS sets IE-TFCI = 1 and look up the transport block size from the relevant Transport Block Size Table for the sub-test.

16

ß

Removal of absolute grant

Signalling value 1

17

<–

DOWNLINK RLC SDU(s)

The SS creates and transmit one or 2 RLC SDUs. The number of RLC SDUs and their size depends on TB size under test.

18

à

SI indicating data for transmission

This can be verified from the indicated Total E-DCH Buffer Status (TEBS)

19

<–

Absolute grant allowing the UE to transmit at maximum bit rate.

Signalling value 31

20

–>

UPLINK RLC SDU(s)

The SS checks E-TFC from the UE and checks that the content of the received UL RLC SDU(s) are correct and sent in the same TTI.

The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.5.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

21

SS

The SS increments IE-TFCI by 1 and look up transport block size from the relevant Transport Block Size Table for the sub-test. If E-TFC TB size is supported by the E-DCH category then repeat steps 16 to 21 else continue with step 22.

22

<–

OPEN UE TEST LOOP (DCCH)

TC

23

–>

OPEN UE TEST LOOP COMPLETE (DCCH)

TC

24

RB RELEASE

RRC

25

<–

DEACTIVATE RB TEST MODE

TC

Optional step

26

–>

DEACTIVATE RB TEST MODE COMPLETE

TC

Optional step

Note 1: In addition to activate integrity protection Step 7 and Step 8 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.

7.1.7.5.5 Test requirements

1. In step 20, the SS verifies that the received E-TFC has the correct size. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.5.4, but instead used the transport block size correspondent to the next possible larger E-TFCI value.

2. In step 20, the SS shall receive the RLC SDUs in the same TTI and with the same content as sent in downlink.

7.1.7.6 MAC-is/i transport block size selection (1.28Mcps TDD)

7.1.7.6.1 Definition and applicability

Applicable for all UEs supporting 1.28Mcps TDD and MAC-i/is.

7.1.7.6.2 Conformance requirement

Extract from TS 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 CELL-DCH state in TDD, 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.

For 1.28 Mcps TDD in CELL_FACH state and idle mode, for common MAC flows, RRC configures MAC with a HARQ profile and multiplexing list. The HARQ profile includes the power offset/maximum number of HARQ transmissions to use for this common MAC flows and a retransmission timer attribute.

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.

For 1.28 Mcps TDD in CELL_FACH state and idle mode, CCCH shall not be multiplexed with any other logical channel, and the CCCH data shall have higher priority than that of any other logical channel.

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 or common flow (1.28 Mcps TDD only), 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 “code rate” as used here is the same as that provided by [18]}. This shall be evaluated for both QPSK and 16-QAM modulation;

– PHARQ, 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 or common 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 PE-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.

– For 1.28Mcps TDD, if the E-PUCH coexists with other physical channel within one timeslot, the sum of calculated transmission power requirement PE-PUCH and the transmission power requirement for the other physical channel shall be less than or equal to the available power.

– If only scheduling information is included in MAC-e PDU, the transmission power shall be equal to the granted power (the available maximum E-PUCH power shall be considered too). And the UE shall select QPSK modulation. (1.28 Mcps TDD only);

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.

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 (PE-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. QPSK shall be used in the case of E-PUCH allocated with other physical channel in the same timeslot of one TTI for one UE, otherwise modulation shall be selected, which minimises the power used (1.28 Mcps TDD only);

While respecting all the above listed requirements, for each logical channel using RLC-UM or RLC-AM when new data to be transmitted, at every TTI, the UE may select the RLC PDU size so as to maximise the amount of data of this logical channel that can 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 or MAC-i 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 or MAC-i PDU and transmission HARQ profile to the HARQ entity. The selected E-TFC is also provided. For 3.84Mcps TDD and 7.68Mcps TDD 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 or MAC-i 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.

[…]

For 1.28 Mcps TDD, the mapping of transport block size L to TB index k (k = {0,1,…63};) (see Annex BC.1) is given by the formula:

Table 9.2.6.4.3: formula used to calculate the Transport Block Size

Category 1-2

Category 3-6

1 Timeslot

2 Timeslots

3 Timeslots

1 Timeslot

2 Timeslots

3 Timeslots

4&5 Timeslots

NOTE: When in CELL FACH state with E-DCH transmission, the formula used to calculate the Transport Block Size according to the E-DCH physical layer category 3 shall be used.

Reference(s)

TS 25.321 clause 11.9.1.4, 9.2.6.4.3

7.1.7.6.3 Test purpose

To verify that the UE is able to transmit all possible transport block sizes when MAC-i/is is configured and within the UE capability.

7.1.7.6.4 Method of test

Initial Condition

Same initial conditions as in clause 7.1.6.3.5.

Test Procedure

Same test procedure as in clause 7.1.6.3.5.

Expected sequence

Same expected sequence as in clause 7.1.6.3.5.

Specific Message Contents

Same specific message contents as in clause 7.1.6.3.5.

7.1.7.6.5 Test requirement

Same test requirements as in clause 7.1.6.3.5.