7.1.4 UL-SCH data transfer

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

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

7.1.4.1 Correct handling of UL assignment / Dynamic case

7.1.4.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives for a TTI an uplink grant with valid C-RNTI }

then { UE transmits data and associated HARQ information to the HARQ entity for this TTI }

}

7.1.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 5.4.1.

[TS 36.321, clause 5.4.1]

In order to transmit on the UL-SCH the UE must have a valid uplink grant (except for non-adaptive HARQ retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be configured semi-persistently. To perform requested transmissions, the MAC layer receives HARQ information from lower layers.

When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI :

– if an uplink grant for this TTI has been received in a Random Access Response:

– set NDI to the value 0 and consider the NDI to have been toggled.

– if an uplink grant for this TTI has been received on the PDCCH for the UE’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– if the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was either an uplink grant received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured uplink grant:

– consider the NDI to have been toggled regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else, if an uplink grant for this TTI has been received on the PDCCH for the UE’s Semi-Persistent C-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI not to have been toggled;

– indicate a valid uplink grant and the associated HARQ information to the HARQ entity for this TTI.

…

NOTE 1: The period of configured uplink grants is expressed in TTIs.

NOTE 2: If the UE receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi persistent scheduling C-RNTI requiring transmissions in the same UL subframe, the UE may choose to continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling C-RNTI.

NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.

7.1.4.1.3 Test description

7.1.4.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.1.3.2 Test procedure sequence

Table 7.1.4.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	SS transmits a MAC PDU including a RLC SDU	<–	MAC PDU	1	–
3	Void	–>	–	–	–
–	EXCEPTION: Step 4 runs in parallel with behaviour in table 7.1.4.1.3.2-2	–	–	–	–
4	The SS is configured for Uplink Grant Allocation Type 2. For 400 ms SS transmits an UL Grant every 10 ms, allowing the UE to return the RLC SDU as received in step 2, on PDCCH, but with the C-RNTI different from the C-RNTI assigned to the UE. Note 1.	<–	(UL Grant (unknown C-RNTI))	–	–
5	Check: Does the UE transmit a MAC PDU corresponding to grant in step 4?	–>	MAC PDU	1	F
6	The SS is configured for Uplink Grant Allocation Type 2. SS transmits an UL Grant, allowing the UE to return the RLC SDU as received in step 2, on PDCCH with the C-RNTI assigned to the UE.	<–	(UL Grant (C-RNTI))	–	–
7	Check: Does the UE transmit a MAC PDU corresponding to grant in step 6?	–>	MAC PDU	1	P
Note 1: Note 400 ms corresponding to 40 frames is selected to be sufficiently large than loop back delay and small than the time needed for Scheduling Request to be repeated dsr-TransMax times( {64-1}* 20 milliseconds).

Table 7.1.4.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a Scheduling Request.	–>	(SR)	–	–

7.1.4.1.3.3 Specific message contents.

Table 7.1.4.1.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration in preamble

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 7.1.4.1.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

7.1.4.1a Correct handling of UL assignment / Dynamic case / Skip padding transmissions

7.1.4.1a.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with skipUplinkTxDynamic not configured and there is no data in the UL buffer }

ensure that {

when { UE receives an uplink grant with a valid C-RNTI }

then { UE transmits a MAC PDU }

}

(2)

with { UE in RRC_CONNECTED state with periodic BSR and skipUplinkTxDynamic configured and the periodic BSR timer has expired and there is no data in the UL buffer }

ensure that {

when { UE receives an uplink grant with a valid C-RNTI }

then { UE does not transmit a MAC PDU }

}

7.1.4.1a.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in TS 36.306, clause 4.3.19.7, TS 36.321 clause 5.4.3.1 and TS 36.331 clause 6.3.2.

[TS 36.306, clause 4.3.19.7 (skipUplinkDynamic-r14)]

This field indicates whether the UE supports skipping of UL transmission for an uplink grant indicated on PDCCH if no data is available for transmission as specified in TS 36.321 [4].

[TS 36.321, clause 5.4.3.1]

The Logical Channel Prioritization procedure is applied when a new transmission is performed.

…

If the MAC PDU includes only the MAC CE for padding BSR or periodic BSR with zero MAC SDUs and there is no aperiodic CSI requested for this TTI [2], the MAC entity shall not generate a MAC PDU for the HARQ entity in the following cases:

– in case the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was addressed to a C-RNTI; or

– in case the MAC entity is configured with skipUplinkTxSPS and the grant indicated to the HARQ entity is a configured uplink grant;

[TS 36.331, clause 6.3.2]

– MAC-MainConfig

The IE MAC-MainConfig is used to specify the MAC main configuration for signalling and data radio bearers. All MAC main configuration parameters can be configured independently per Cell Group (i.e. MCG or SCG), unless explicitly specified otherwise.

….

MAC-MainConfig field descriptions
….
*skipUplinkTxDynamic* If configured, the UE skips UL transmissions for an uplink grant other than a configured uplink grant if no data is available for transmission in the UE buffer as described in TS 36.321 [6].
….

MAC-MainConfig field descriptions

….

skipUplinkTxDynamic

If configured, the UE skips UL transmissions for an uplink grant other than a configured uplink grant if no data is available for transmission in the UE buffer as described in TS 36.321 [6].

….

7.1.4.1a.3 Test description

7.1.4.1a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18].

7.1.4.1a.3.2 Test procedure sequence

Table 7.1.4.1a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS sends an uplink grant of size 32 bits	–	–	–	–
3	Check: Does UE transmit a MAC PDU?	–>	MAC PDU	1	P
4	The SS transmits an RRCConnectionReconfiguration message activating periodic BSR and with skipUplinkTxDynamic set to true	<–	–	–	–
5	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	–	–	–
6	SS waits 150ms for the periodic BSR timer to expiry
7	The SS sends an uplink grant of size 32 bits	–	–	–	–
8	Check: Does UE transmit a MAC PDU?	–>	MAC PDU	2	F

7.1.4.1a.3.3 Specific message contents

Table 7.1.4.1a.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration in preamble

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 7.1.4.1a.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicit SEQUENCE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}
}

Table 7.1.4.1a.3.3-3: MAC-MainConfig-RBC (Table 7.1.4.1a.3.2-1, Step 4)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
periodicBSR-Timer	sf10
}
skipUplinkTx-r14 CHOICE {
setup SEQUENCE {
skipUplinkTxSPS-r14	Not present
skipUplinkTxDynamic-r14	true
}
}
}

7.1.4.2 Correct handling of UL assignment / Semi-persistent case

7.1.4.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state with DRB established and SPS Configuration in UL is enabled }

ensure that {

when { UE receives a UL grant addressed to its stored SPS-CRNTI in SF-Num y and with NDI set as 0 }

then { UE starts transmitting UL MAC PDU in SF-Num F1 }

}

(2)

with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC PDU at SF-Num F1 }

ensure that {

when { UE receives a UL grant addressed to its SPS-CRNTI in SF-Num-frame p and with NDI set as 0, where p+4!=F1(FDD) or p+k(p)!=F1(TDD) }

then { UE starts transmitting UL MAC PDU in SF-Num F2 and stops transmitting UL MAC PDU at SF-Num F1 }

}

(3)

with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC PDU at SF-Num F1 }

ensure that {

when { UE receives a UL grant [for retransmission] addressed to its SPS-CRNTI in SF-Num z and with NDI set as 1, for the corresponding HARQ Process, where z+4!=F1(FDD) or z+k(z)!=F1(TDD) }

then { UE re-transmits MAC PDU in SF-Num z+4(FDD) or z+k(z)(TDD) as per the new grant for SPS-CRNTI }

}

(4)

with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC PDU at SF-Num F3 }

ensure that {

when { UE receives a UL grant addressed to its CRNTI in SF-Num p, such that in SF-Num p+4=F3(FDD) or p+k(p)=F3(TDD) }

then { UE transmits MAC PDU in SF-Num p+4(FDD) or p+k(p)(TDD) as per grant addressed to its C-RNTI }

}

(5)

with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC PDU at SF-Num F3 }

ensure that {

when { UE receives a RRCConnectionReconfiguration including SPS Configuration with sps-ConfigUL set as ‘disable’ and hence resulting in UL SPS grant deactivation }

then { UE deletes the stored SPS Configuration UL parameters and stops transmitting UL MAC PDU’s as per stored SPS grant in SF-Num F3 }

}

(6)

with { UE in E-UTRA RRC_Connected state with DRB established and configured UL SPS grant }

ensure that {

when { UE transmits ‘implicitReleaseAfter‘ MAC PDU’s on SPS-Grant containing zero MAC SDU }

then { UE clears configured SPS grant }

}

(7)

with { UE in E-UTRA RRC_Connected state with DRB established and stored UL SPS grant to transmit MAC PDU at SF-Num F3 }

ensure that {

when { UE receives a PDCCH [for UL SPS explicit release according to Table 9.2-1A in TS 36.213] addressed to its SPS C-RNTI in SF-Num p and with NDI set as 0, where p+4!=F3(FDD) or p+k(p)!=F3(TDD) }

then { UE releases the configured SPS grant and stops transmitting UL MAC PDU in SF-Num F3 as per grant addressed to its SPS C-RNTI }

}

NOTE: SF-Num = [10*SFN + subframe] modulo 10240.

NOTE 2: The value of the k(y), k(p), k(z) is k value determined according to the table 8-2 in the TS 36.213, given that UL grant is in subframe y, p, z.

NOTE 3: The Subframe_Offset(y+k(y)), Subframe_Offset(p+k(p)), Subframe_Offset(z+k(z)) is subframe_offset value determined according to the clause 5.10.2 in the TS36.321, given the position of initial Semi-Persistent grant on subframe y+k(y), p+k(p), z+k(z).

NOTE 4: To simply the TP description, following abbreviations are defined:

For FDD:

F1 = y+4+n*[semiPersistSchedIntervalUL]

F2 = p+4+n*[semiPersistSchedIntervalUL]

F3 = z+4+n*[semiPersistSchedIntervalUL]

For TDD:

F1 = y+k(y)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(y+k(y))*(n modulo 2)

F2 = p+k(p)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(p+k(p))*(n modulo 2)

F3 = z+k(z)+n*[semiPersistSchedIntervalUL]+ Subframe_Offset(z+k(z))*(n modulo 2)

n >= 0

7.1.4.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.1, 5.10, 5.10.2, 7.4, 36.331 clause 5.3.10.5, 36.213 clause 8, 9.2 and 36.300 clause 11.1.2.

[TS 36.321, clause 5.4.1]

When timeAlignmentTimer is running and the UE has a C-RNTI, Semi-Persistent Scheduling C-RNTI, or Temporary C-RNTI, the UE shall for each TTI:

– if an uplink grant for this TTI has been received in a Random Access Response:

– set NDI to the value 0 and consider the NDI to have been toggled.

– if an uplink grant for this TTI has been received on the PDCCH for the UE’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– if the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was the uplink grant is for UE’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was either an uplink grant received for the UE’s Semi-Persistent Scheduling C-RNTI or a configured uplink grant:

– consider the NDI to have been toggled regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else, if an uplink grant for this TTI has been received on the PDCCH for the UE’s Semi-Persistent Scheduling C-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else if the NDI in the received HARQ information is 0:

– if PDCCH contents indicate SPS release:

– clear the configured uplink grant (if any).

– else:

– store the uplink grant and the associated HARQ information as configured uplink grant;

– initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI and to recur according to rules in subclause 5.10.2;

– consider the NDI bit to have been toggled;

– deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else, if an uplink grant for this TTI has been configured:

– consider the NDI bit to have been toggled;

– deliver the configured uplink grant, and the associated HARQ information to the HARQ entity for this TTI.

NOTE 1: The period of configured uplink grants is expressed in TTIs.

NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH transmission during a measurement gap, the UE processes the grant but does not transmit on UL-SCH.

[TS 36.321, clause 5.10]

When Semi-Persistent Scheduling is enabled by RRC, the following information is provided:

– Semi-Persistent Scheduling C-RNTI;

– Uplink Semi-Persistent Scheduling Interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the uplink;

– Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;

– Downlink Semi-Persistent Scheduling Interval semiPersistSchedIntervalDL and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink;

When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded.

[TS 36.321, clause 5.10.2]

After a Semi-Persistent Scheduling uplink grant is configured, the UE shall:

– if twoIntervalsConfig is enabled by upper layer;

– set the Subframe_Offset according to Table 7.4-1.

– else:

– set Subframe_Offset to 0.

– consider that the grant recurs in each subframe for which:

– (10 * SFN + subframe) = [(10 * SFN_{start time} + subframe_{start time}) + N * semiPersistSchedIntervalUL + Subframe_Offset * (N modulo 2)] modulo 10240, for all N>0.

Where SFN_{start time} and subframe_{start time} are the SFN and subframe, respectively, at the time the configured uplink grant were (re-)initialised.

The UE shall clear the configured uplink grant immediately after implicitRelease after number of consecutive new MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the Semi-Persistent Scheduling resource.

NOTE 4: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink grant.

[TS 36.321, clause 7.4]

Subframe_Offset values are presented in Table 7.4-1.

Table 7.4-1: Subframe_Offset values

TDD UL/DL configuration	Position of initial Semi-Persistent grant	Subframe_Offset value (ms)
0	N/A	0
1	Subframes 2 and 7	1
1	Subframes 3 and 8	-1
2	Subframe 2	5
2	Subframe 7	-5
3	Subframes 2 and 3	1
3	Subframe 4	-2
4	Subframe 2	1
4	Subframe 3	-1
5	N/A	0
6	N/A	0

[TS 36.331, clause 5.3.10.5]

The UE shall:

1> reconfigure the semi-persistent scheduling in accordance with the received sps-Config:

[TS 36.213, clause 8]

…

For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k given in Table 8-2, according to the PDCCH and PHICH information.

…

Table 8-2 k for TDD configurations 0-6

TDD UL/DL Configuration	DL subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

…

[TS 36.213, clause 9.2]

A UE shall validate a Semi-Persistent Scheduling assignment PDCCH only if all the following conditions are met:

– the CRC parity bits obtained for the PDCCH payload are scrambled with the Semi-Persistent Scheduling C-RNTI

– the new data indicator field is set to ‘0’. In case of DCI formats 2 and 2A, the new data indicator field refers to the one for the enabled transport block.

Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1 or Table 9.2-1A.

If validation is achieved, the UE shall consider the received DCI information accordingly as a valid semi-persistent activation or release.

If validation is not achieved, the received DCI format shall be considered by the UE as having been received with a non-matching CRC.

Table 9.2-1: Special fields for Semi-Persistent Scheduling Activation PDCCH Validation

	DCI format 0	DCI format 1/1A	DCI format 2/2A
TPC command for scheduled PUSCH	set to ‘00’	N/A	N/A
Cyclic shift DM RS	set to ‘000’	N/A	N/A
Modulation and coding scheme and redundancy version	MSB is set to ‘0’	N/A	N/A
HARQ process number	N/A	FDD: set to ‘000’ TDD: set to ‘0000’	FDD: set to ‘000’ TDD: set to ‘0000’
Modulation and coding scheme	N/A	MSB is set to ‘0’	For the enabled transport block: MSB is set to ‘0’
Redundancy version	N/A	set to ‘00’	For the enabled transport block: set to ‘00’

Table 9.2-1A: Special fields for Semi-Persistent Scheduling Release PDCCH Validation

	DCI format 0	DCI format 1A
TPC command for scheduled PUSCH	set to ‘00’	N/A
Cyclic shift DM RS	set to ‘000’	N/A
Modulation and coding scheme and redundancy version	set to ‘11111’	N/A
Resource block assignment and hopping resource allocation	Set to all ‘1’s	N/A
HARQ process number	N/A	FDD: set to ‘000’ TDD: set to ‘0000’
Modulation and coding scheme	N/A	set to ‘11111’
Redundancy version	N/A	set to ‘00’
Resource block assignment	N/A	Set to all ‘1’s

[TS 36.300, clause 11.1.2]

In addition, E-UTRAN can allocate a semi-persistent uplink resource for the first HARQ transmissions and potentially retransmissions to UEs:

– RRC defines the periodicity of the semi-persistent uplink grant;

– PDCCH indicates whether the uplink grant is a semi-persistent one i.e. whether it can be implicitly reused in the following TTIs according to the periodicity defined by RRC.

In the sub-frames where the UE has semi-persistent uplink resource, if the UE cannot find its C-RNTI on the PDCCH(s), an uplink transmission according to the semi-persistent allocation that the UE has been assigned in the TTI can be made. The network performs decoding of the pre-defined PRBs according to the pre-defined MCS. Otherwise, in the sub-frames where the UE has semi-persistent uplink resource, if the UE finds its C-RNTI on the PDCCH(s), the PDCCH allocation overrides the persistent allocation for that TTI and the UE’s transmission follows the PDCCH allocation, not the semi-persistent allocation. Retransmissions are either implicitly allocated in which case the UE uses the semi-persistent uplink allocation, or explicitly allocated via PDCCH(s) in which case the UE does not follow the semi-persistent allocation.

7.1.4.2.3 Test description

7.1.4.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL of same size.

7.1.4.2.3.2 Test procedure sequence

Table 7.1.4.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	SS transmits RRCConnectionReconfiguration to configure UL SPS	<–	–	–	–
0B	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
1	The SS transmits a DL MAC PDU containing 10 RLC SDU’s on UM DRB.	<–	MAC PDU	–	–
2	The UE transmits a Scheduling Request, indicating that loop back PDUs are ready for transmission in UL RLC	–>	(SR)	–	–
3	The SS transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘4’, NDI=0, allowing the UE to transmit one loop back PDU per MAC PDU.	<–	(UL SPS Grant)	–	–
4	Check: Does the UE transmit a MAC PDU in SF-Num ‘8’ as per grant in step 3?	–>	MAC PDU	1	P
5	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
6	Check: Does the UE transmit a MAC PDU in SF-Num ‘48(FDD)/47(TDD)’ as per grant in step 3?	–>	MAC PDU	1	P
7	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
8	The SS Transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘64’, NDI=0 and allowing the UE to transmit two loop back PDUs per MAC PDU.	<–	(UL SPS Grant)	–	–
9	Check: Does the UE transmit a MAC PDU in SF-Num ‘68’ as per grant in step 8?	–>	MAC PDU	2	P
10	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
11	Check: Does the UE transmit a MAC PDU in SF-Num ‘88’ as per grant in step 3?	–>	MAC PDU	2	F
12	Check: Does the UE transmit a MAC PDU in SF-Num ‘108(FDD)/107(TDD)’ as per grant in step 8?	–>	MAC PDU	2	P
13	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
14	The SS Transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘120 (FDD)/121 (TDD)’, NDI=1; the UL HARQ process is the same as in step 12	<–	(UL SPS Grant)	–	–
15	Check: Does the UE transmit in SF-Num ‘124 (FDD)/127 (TDD)’ a MAC PDU as in step 12?	–>	MAC PDU	3	P
16	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
17	Check: Does the UE transmit a MAC PDU in SF-Num ‘148’ as per grant in step 8?	–>	MAC PDU	1	P
18	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
19	The SS Transmits an UL Grant using UE’s C-RNTI in SF-Num ‘164(FDD)/161(TDD)’; allowing UE to transmit a MAC PDU containing two RLC SDU’s	<–	(UL Grant)	–	–
20	Check: Does the UE transmit a MAC PDU in SF-Num ‘168(FDD)/167(TDD)’ as per grant in step 19?	–>	MAC PDU	4	P
21	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
22	The SS transmits a PDCCH [for UL SPS explicit release] using UE’s SPS C-RNTI in SF-Num ‘180’ with NDI=0.	<–	PDCCH [for UL SPS explicit release]	–	–
23	Check: Does the UE transmit a MAC PDU in SF-Num ‘188’ as per grant in step 8 containing zero MAC SDU?	–>	MAC PDU	7	F
24	The SS transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘399’, NDI=0, transmit one loop back PDU per MAC PDU	<–	(UL SPS Grant)	–	–
25	Check: Does the UE transmit a MAC PDU in SF-Num ‘403’ as per grant in step 24 containing zero MAC SDU?	–>	MAC PDU	1	P
26	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
27	Check: Does the UE transmit a MAC PDU in SF-Num ‘443 (FDD)/442 (TDD)’ as per grant in step 24 containing zero MAC SDU?	–>	MAC PDU	1	P
28	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
29	Check: Does the UE transmit a MAC PDU in SF-Num ‘483’ as per grant in step 24?	–>	MAC PDU	6	F
30	The SS Transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘604’, NDI=0, transmit one loop back PDU per MAC PDU.	<–	(UL SPS Grant)	–	–
31	Check: Does the UE transmit a MAC PDU in SF-Num ‘608’ as per grant in step 30 containing zero MAC SDU?	–>	MAC PDU	1	P
32	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
33	SS Transmits RRCConnectionReconfiguration to disable SPS Configuration UL.	<–	–	–	–
34	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
35	The SS transmits a DL MAC PDU containing 1 RLC SDU	<–	MAC PDU	–	–
36	Void	–	–	–	–
37	Check: Does the UE transmit a MAC PDU in SF-Num ‘648 (FDD)/647 (TDD)’ as per grant in step 30?	–>	MAC PDU	5	F

7.1.4.2.3.3 Specific message contents

Table 7.1.4.2.3.3-1: RRCConnectionReconfiguration. RadioResourceConfigDedicated (Step 0A)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	‘FFF0’H
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
enable SEQUENCE {
semiPersistSchedIntervalUL	sf40	40 Subframe
implicitReleaseAfter	e2
p0-Persistent	Not Present
twoIntervalConfig	Not Present		FDD
twoIntervalConfig	true		TDD
}
}
}
}

Table 7.1.4.2.3.3-2: RRCConnectionReconfiguration. RadioResourceConfigDedicated (step 33 of table 7.1.4.2.3.2-1)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	Not Present
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
disable	NULL
}
}
}

Table 7.1.4.2.3.3-3: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
drx-Config	Not Present
}
}
}
}
}

7.1.4.2a Correct handling of UL assignment / Semi-persistent case / Skip padding transmissions / SPS activation and de-activation confirmation

7.1.4.2a.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled and skipUplinkTxSPS not configured and there is no data in the UL buffer }

ensure that {

when { UE receives an UL grant addressed to its SPS-CRNTI with NDI set as 0 }

then {UE transmits MAC PDUs in subframes correspondent to the configured semiPersistSchedIntervalUL }

}

(2)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled with skipUpLinkTxSPS configured }

ensure that {

when { UE receives a UL grant addressed to its SPS-CRNTI with NDI set as 0 }

then { UE transmits a SPS confirmation MAC Control Element in a MAC PDU in a subframe correspondent to the configured semiPersistSchedIntervalUL }

}

(3)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled and with periodic BSR and skipUplinkTxSPS configured and there is no data in the UL buffer }

ensure that {

when { UE has semi-persistent uplink resource in the sub-frame }

then { UE does not transmit any data }

}

(4)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled and skipUplinkTxSPS configured and no data have been available in the UL buffer for the time longer than configured implicitReleaseAfter * semiPersistSchedIntervalUL }

ensure that {

when { UE receives data in the UL buffer }

then {UE transmits a MAC PDUs in a subframe correspondent to the configured semiPersistSchedIntervalUL }

}

(5)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled with skipUpLinkTxSPS configured }

ensure that {

when { UE receives an SPS release on PDCCH addressed to its SPS-CRNTI with NDI set to 0 }

then {UE transmits a SPS confirmation MAC Control Element in a MAC PDU in a subframe correspondent to the configured semiPersistSchedIntervalUL }

}

7.1.4.2a.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in TS 36.306, clause 4.3.19.8, TS 36.321 clauses 5.4.1, 5.4.3.1, 5.10.2, 6.3.1.11, 6.2.1 and TS 36.331 clause 6.3.2.

[TS 36.306, clause 4.3.19.8 (skipUplinkSPS-r14)]

This field indicates whether the UE supports skipping of UL transmission for a configured uplink grant if no data is available for transmission as specified in TS 36.321 [4].

[TS 36.321, clause 5.4.1]

If the MAC entity has a C-RNTI, a Semi-Persistent Scheduling C-RNTI, a UL Semi-Persistent Scheduling V-RNTI, or a Temporary C-RNTI, the MAC entity shall for each TTI and for each Serving Cell belonging to a TAG that has a running timeAlignmentTimer and for each grant received for this TTI and for each SPS configuration that is indicated by the PDCCH addressed to UL Semi-Persistent Scheduling V-RNTI:

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

….

– else, if this Serving Cell is the SpCell and if an uplink grant for this TTI has been received for the SpCell on the PDCCH of the SpCell for the MAC entity’s Semi-Persistent Scheduling C-RNTI or for the MAC entity’s UL Semi-Persistent Scheduling V-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else if the NDI in the received HARQ information is 0:

– if PDCCH contents indicate SPS release:

– if the MAC entity is configured with skipUplinkTxSPS:

– trigger an SPS confirmation;

– if an uplink grant for this TTI has been configured:

– consider the NDI bit for the corresponding HARQ process to have been toggled;

– deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI;

– else:

– clear the corresponding configured uplink grant (if any).

– else:

– if the MAC entity is configured with skipUplinkTxSPS:

– trigger an SPS confirmation;

– store the uplink grant and the associated HARQ information as configured uplink grant;

– initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI and to recur according to rules in subclause 5.10.2;

– if UL HARQ operation is asynchronous, set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit for the corresponding HARQ process to have been toggled;

– deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI.

[TS 36.321, clause 5.4.3.1]

The Logical Channel Prioritization procedure is applied when a new transmission is performed.

…

– in case the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was addressed to a C-RNTI; or

– in case the MAC entity is configured with skipUplinkTxSPS and the grant indicated to the HARQ entity is a configured uplink grant;

[TS 36.321, clause 5.10.2]

If the MAC entity is not configured with skipUplinkTxSPS, the MAC entity shall clear the configured uplink grant immediately after implicitReleaseAfter [8] number of consecutive new MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing and Assembly entity, on the Semi-Persistent Scheduling resource.

[TS 36.321, clause 6.3.1.11]

The SPS confirmation MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2.

It has a fixed size of zero bits.

[TS 36.321, clause 6.2,1]

The MAC header is of variable size and consists of the following fields:

– LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or padding as described in tables 6.2.1-1, 6.2.1-2 and 6.2.1-4 for the DL-SCH, UL-SCH and MCH respectively. There is one LCID field for each MAC SDU, MAC control element or padding included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU, when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU. A UE of Category 0 [12] except when in enhanced coverage, and unicastFreqHoppingInd-r13 is indicated in the BR version of SI message carrying SystemInformationBlockType2, and UE supports frequency hopping for unicast [12] shall indicate CCCH using LCID "01011", a BL UE with support for frequency hopping for unicast [12] and a UE in enhanced coverage with support for frequency hopping for unicast [12] shall if unicastFreqHoppingInd-r13 is indicated in the BR version of SI message carrying SystemInformationBlockType2 indicate CCCH using LCID "01100", otherwise the UE shall indicate CCCH using LCID "00000". The LCID field size is 5 bits;

– L: The Length field indicates the length of the corresponding MAC SDU or variable-sized MAC control element in bytes. There is one L field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements. The size of the L field is indicated by the F field and F2 field;

– F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements and except for when F2 is set to 1. The size of the F field is 1 bit. If the F field is included; if the size of the MAC SDU or variable-sized MAC control element is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1;

– F2: The Format2 field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F2 field per MAC PDU subheader. The size of the F2 field is 1 bit. If the size of the MAC SDU or variable-sized MAC control element is larger than 32767 bytes, and if the corresponding subheader is not the last subheader, the value of the F2 field is set to 1, otherwise it is set to 0.

– E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate another set of at least R/F2/E/LCID fields. The E field is set to "0" to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte;

– R: Reserved bit, set to "0".

The MAC header and subheaders are octet aligned.

…

Table 6.2.1-2 Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011	CCCH
01100	CCCH
01101-10011	Reserved
10100	Recommended bit rate query
10101	SPS confirmation
10110	Truncated Sidelink BSR
10111	Sidelink BSR
11000	Dual Connectivity Power Headroom Report
11001	Extended Power Headroom Report
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

[TS 36.331, clause 6.3.2]

– MAC-MainConfig

….

MAC-MainConfig field descriptions
….
*skipUplinkTxSPS* If configured, the UE skips UL transmissions for a configured uplink grant if no data is available for transmission in the UE buffer as described in TS 36.321 [6]. E-UTRAN always configures skipUplinkTxSPS when semiPersistSchedIntervalUL is shorter than sf10.
….

MAC-MainConfig field descriptions

….

skipUplinkTxSPS

If configured, the UE skips UL transmissions for a configured uplink grant if no data is available for transmission in the UE buffer as described in TS 36.321 [6]. E-UTRAN always configures skipUplinkTxSPS when semiPersistSchedIntervalUL is shorter than sf10.

….

7.1.4.2a.3 Test description

7.1.4.2a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.2a.3.2 Test procedure sequence

Table 7.1.4.2a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits RRCConnectionReconfiguration to configure UL SPS and skipUplinkTxSPS not configured	<–	–	–	–
1A	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	–	–	–
2	The SS transmits an UL Grant using UE’s SPS C-RNTI, NDI=0, allowing the UE to transmit a RLC SDU of size 10 bytes per MAC PDU.	<–	(UL SPS Grant)	–	–
3	Check: Does UE transmit a MAC PDU in a subframe correspondent to the configured semiPersistSchedIntervalUL?	–>	MAC PDU	1	P
4	SS transmits RRCConnectionReconfiguration to configure UL SPS with skipUplinkTxSPS set to true and activating periodic BSR	<–	–	–	–
4A	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	–	–	–
5	Check: Does UE transmit a MAC PDU including a MAC CE with LCID set to ‘10101’ in a subframe correspondent to the configured semiPersistSchedIntervalUL? Note: UE indicates SPS activation.	–>	MAC PDU	2	P
6	Void	–	–	–	–
7	Check: Does UE transmit a MAC PDU during next 210ms? (Note 1)	–>	MAC PDU	3	F
8	The SS transmits a DL MAC PDU containing 1 RLC SDU of size 10 bytes	<–	MAC PDU	–	–
9	Check: Does UE transmit a MAC PDU in a subframe correspondent to the configured semiPersistSchedIntervalUL	–>	MAC PDU	4	P
10	The SS transmits a SPS release on PDCCH using UE’s SPS C-RNTI and NDI=0.	–	(SPS Release)	–	–
11	Check: Does UE transmit a MAC PDU including a MAC CE with LCID set to ‘10101’ in a subframe correspondent to the configured semiPersistSchedIntervalUL? Note: UE indicates SPS de-activation.	–>	MAC PDU	5	P
Note 1: 210ms correspond to time greater than implicitReleaseAfter * semiPersistSchedIntervalUL = e2 * sf10 * 10ms = 200ms and also enables a periodic BSR to be triggered.

7.1.4.2a.3.3 Specific message contents

Table 7.1.4.2a.3.3-1: RadioResourceConfigDedicated (Table 7.1.4.2a.3.2-1, Step 1)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	‘FFF0’H
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
setup SEQUENCE {
semiPersistSchedIntervalUL	sf10	10 Subframes
implicitReleaseAfter	e8
p0-Persistent	Not Present
twoIntervalConfig	Not Present		FDD
twoIntervalConfig	true		TDD
p0-PersistentSubframeSet2-r12	Not Present
numberOfConfUlSPS-Processes-r13	Not Present
fixedRV-NonAdaptive-r14	Not Present
sps-ConfigIndex-r14	Not Present
semiPersistSchedIntervalUL-v1430	Not Present
}
}
}
}

Table 7.1.4.2a.3.3-2: RadioResourceConfigDedicated (Table 7.1.4.2a.3.2-1, Step 4)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	‘FFF0’H
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
setup SEQUENCE {
semiPersistSchedIntervalUL	sf10	10 Subframes
implicitReleaseAfter	e2
p0-Persistent	Not Present
twoIntervalConfig	Not Present		FDD
twoIntervalConfig	true		TDD
p0-PersistentSubframeSet2-r12	Not Present
numberOfConfUlSPS-Processes-r13	Not Present
fixedRV-NonAdaptive-r14	Not Present
sps-ConfigIndex-r14	Not Present
semiPersistSchedIntervalUL-v1430	Not Present
}
}
}
}

Table 7.1.4.2a.3.3-3: MAC-MainConfig-RBC (Table 7.1.4.2a.3.2-1, Step 4)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
periodicBSR-Timer	sf10
}
skipUplinkTx-r14 CHOICE {
setup SEQUENCE {
skipUplinkTxSPS-r14	true
skipUplinkTxDynamic-r14	Not present
}
}
}

7.1.4.2b Correct handling of UL assignment / Semi-persistent case / SPS interval shorter than 10 subframes

7.1.4.2b.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled with semiPersistSchedIntervalUL set to shorter than 10 subframes }

ensure that {

when { UE has data available in the UL buffer and the next UL SPS subframe is not a downlink subframe nor a special subframe }

then {UE transmits MAC PDUs in subframes correspondent to the configured semiPersistSchedIntervalUL }

}

(2)

with { UE in RRC_CONNECTED state in TDD with SPS configuration in UL enabled with semiPersistSchedIntervalULshorter than 10 subframes }

ensure that {

when { UE has data available in the UL buffer and the next UL SPS subframe is a downlink subframe }

then {UE does not transmit a MAC PDU in the subframe }

}

(3)

with { UE in RRC_CONNECTED state in TDD with SPS configuration in UL enabled with semiPersistSchedIntervalULshorter than 10 subframes }

ensure that {

when { UE has data available in the UL buffer and the next UL SPS subframe is a special subframe }

then {UE does not transmit a MAC PDU in the subframe }

}

7.1.4.2b.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in TS 36.211: 4.2, TS 36.312: 8, TS 36.321: 5.4.1, 5.10, 5.10.2 and TS 36.331:6.3.2.

[TS 36.211, clause 4.2]

Frame structure type 2 is applicable to TDD only. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. Each subframe is defined as two slots, and, of length each. Subframe in frame has an absolute subframe number where is the system frame number.

The uplink-downlink configuration in a cell may vary between frames and controls in which subframes uplink or downlink transmissions may take place in the current frame. The uplink-downlink configuration in the current frame is obtained according to Section 13 in [4].

The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, "D" denotes a downlink subframe reserved for downlink transmissions, "U" denotes an uplink subframe reserved for uplink transmissions and "S" denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to where X is the number of additional SC-FDMA symbols in UpPTS provided by the higher layer parameter srs-UpPtsAdd if configured otherwise X is equal to 0. The UE is not expected to be configured with 2 additional UpPTS SC-FDMA symbols for special subframe configurations {3, 4, 7, 8} for normal cyclic prefix in downlink and special subframe configurations {2, 3, 5, 6} for extended cyclic prefix in downlink and 4 additional UpPTS SC-FDMA symbols for special subframe configurations {1 2, 3, 4, 6, 7, 8} for normal cyclic prefix in downlink and special subframe configurations {1, 2, 3, 5, 6} for extended cyclic prefix in downlink.

Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported.

In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames.
In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only.

Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission.

…

Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity)

…

Table 4.2-2: Uplink-downlink configurations

Uplink-downlink configuration	Downlink-to-Uplink Switch-point periodicity	Subframe number
Uplink-downlink configuration	Downlink-to-Uplink Switch-point periodicity	0	1	2	3	4	5	6	7	8	9
0	5 ms	D	S	U	U	U	D	S	U	U	U
1	5 ms	D	S	U	U	D	D	S	U	U	D
2	5 ms	D	S	U	D	D	D	S	U	D	D
3	10 ms	D	S	U	U	U	D	D	D	D	D
4	10 ms	D	S	U	U	D	D	D	D	D	D
5	10 ms	D	S	U	D	D	D	D	D	D	D
6	5 ms	D	S	U	U	U	D	S	U	U	D

[TS 36.213, clause 8]

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	DL subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

…

[TS 36.321, clause 5.4.1]

In order to transmit on the UL-SCH the MAC entity must have a valid uplink grant (except for non-adaptive HARQ retransmissions) which it may receive dynamically on the PDCCH or in a Random Access Response or which may be configured semi-persistently or preallocated by RRC. To perform requested transmissions, the MAC layer receives HARQ information from lower layers. When the physical layer is configured for uplink spatial multiplexing, the MAC layer can receive up to two grants (one per HARQ process) for the same TTI from lower layers.

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– if the uplink grant is for MAC entity’s C-RNTI and if the previous uplink grant delivered to the HARQ entity for the same HARQ process was either an uplink grant received for the MAC entity’s Semi-Persistent Scheduling C-RNTI, for the MAC entity’s UL Semi-Persistent Scheduling V-RNTI, or a configured uplink grant:

– consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else if the NDI in the received HARQ information is 0:

– if PDCCH contents indicate SPS release:

– if the MAC entity is configured with skipUplinkTxSPS:

– trigger an SPS confirmation;

– if an uplink grant for this TTI has been configured:

– consider the NDI bit for the corresponding HARQ process to have been toggled;

– deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI;

– else:

– clear the corresponding configured uplink grant (if any).

– else:

– if the MAC entity is configured with skipUplinkTxSPS:

– trigger an SPS confirmation;

– store the uplink grant and the associated HARQ information as configured uplink grant;

– initialise (if not active) or re-initialise (if already active) the configured uplink grant to start in this TTI and to recur according to rules in subclause 5.10.2;

– if UL HARQ operation is asynchronous, set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit for the corresponding HARQ process to have been toggled;

– deliver the configured uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else, if this Serving Cell is the SpCell and an uplink grant for this TTI has been configured or preallocated for the SpCell:

– if UL HARQ operation is asynchronous, set the HARQ Process ID to the HARQ Process ID associated with this TTI;

– consider the NDI bit for the corresponding HARQ process to have been toggled;

– deliver the configured or preallocated uplink grant, and the associated HARQ information to the HARQ entity for this TTI.

NOTE: The period of configured uplink grants is expressed in TTIs.

NOTE: If the MAC entity receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi persistent scheduling C-RNTI requiring transmissions on the SpCell in the same UL subframe, the MAC entity may choose to continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling C-RNTI.

NOTE: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH transmission during a measurement gap, the MAC entity processes the grant but does not transmit on UL-SCH. When a configured uplink grant is indicated during a Sidelink Discovery gap for reception and indicates an UL-SCH transmission during a Sidelink Discovery gap for transmission with a SL-DCH transmission, the MAC entity processes the grant but does not transmit on UL-SCH.

For configured uplink grants, the HARQ Process ID associated with this TTI is derived from the following equation for asynchronous UL HARQ operation:

HARQ Process ID = [floor(CURRENT_TTI/semiPersistSchedIntervalUL)] modulo numberOfConfUlSPS-Processes,

where CURRENT_TTI=[(SFN * 10) + subframe number] and it refers to the subframe where the first transmission of a bundle takes place.

For preallocated uplink grants, the HARQ Process ID associated with this TTI is derived from the following equation for asynchronous UL HARQ operation:

HARQ Process ID = [floor(CURRENT_TTI/ul-SchedInterval)] modulo numberOfConfUL-Processes,

where CURRENT_TTI=subframe number and it refers to the subframe where the first transmission of a bundle takes place.

[TS 36.321, clause 5.10]

When Semi-Persistent Scheduling is enabled by RRC, the following information is provided [8]:

– Semi-Persistent Scheduling C-RNTI or UL Semi-Persistent Scheduling V-RNTI;

– Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling with Semi-Persistent Scheduling C-RNTI is enabled for the uplink;

– Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter for each SPS configuration, if Semi-Persistent Scheduling with UL Semi-Persistent Scheduling V-RNTI is enabled for the uplink;

– Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;

– Downlink Semi-Persistent Scheduling interval semiPersistSchedIntervalDL and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink;

When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded.

Semi-Persistent Scheduling is supported on the SpCell only.

Semi-Persistent Scheduling is not supported for RN communication with the E-UTRAN in combination with an RN subframe configuration.

[TS 36.321, clause 5.10.2]

After a Semi-Persistent Scheduling uplink grant is configured, the MAC entity shall:

– if twoIntervalsConfig is enabled by upper layer:

– set the Subframe_Offset according to Table 7.4-1.

– else:

– set Subframe_Offset to 0.

– consider sequentially that the N^th grant occurs in the subframe for which:

– (10 * SFN + subframe) = [(10 * SFN_{start time} + subframe_{start time}) + N * semiPersistSchedIntervalUL + Subframe_Offset * (N modulo 2)] modulo 10240.

Where SFN_{start time} and subframe_{start time} are the SFN and subframe, respectively, at the time the configured uplink grant were (re-)initialised.

For TDD, the MAC entity is configured with semiPersistSchedIntervalUL shorter than 10 subframes, the N^th grant shall be ignored if it occurs in a downlink subframe or a special subframe.

If SPS confirmation has been triggered and not cancelled:

– if the MAC entity has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate an SPS confirmation MAC Control Element as defined in subclause 6.1.3.11;

– cancel the triggered SPS confirmation.

The MAC entity shall clear the configured uplink grant immediately after first transmission of SPS confirmation MAC Control Element triggered by the SPS release.

NOTE: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink grant.

[TS 36.331, clause 6.3.2]

– SPS-Config

The IE SPS-Config is used to specify the semi-persistent scheduling configuration.

— ASN1START

SPS-Config ::= SEQUENCE {

semiPersistSchedC-RNTI C-RNTI OPTIONAL, — Need OR

sps-ConfigDL SPS-ConfigDL OPTIONAL, — Need ON

sps-ConfigUL SPS-ConfigUL OPTIONAL — Need ON

}

….

SPS-ConfigUL ::= CHOICE {

release NULL,

setup SEQUENCE {

semiPersistSchedIntervalUL ENUMERATED {

sf10, sf20, sf32, sf40, sf64, sf80,

sf128, sf160, sf320, sf640, sf1-v1430,

sf2-v1430, sf3-v1430, sf4-v1430, sf5-v1430,

spare1},

….

}

….

semiPersistSchedIntervalUL

Semi-persistent scheduling interval in uplink, see TS 36.321 [6]. Value in number of sub-frames. Value sf10 corresponds to 10 sub-frames, sf20 corresponds to 20 sub-frames and so on. For TDD, when the configured Semi-persistent scheduling interval is greater than or equal to 10 sub-frames, the UE shall round this parameter down to the nearest integer (of 10 sub-frames), e.g. sf10 corresponds to 10 sub-frames, sf32 corresponds to 30 sub-frames, sf128 corresponds to 120 sub-frames. If semiPersistSchedIntervalUL-v1430 is configured, the UE only considers this extension (and ignores semiPersistSchedIntervalUL i.e. without suffix).

7.1.4.2b.3 Test description

7.1.4.2b.3.1 Pre-test conditions

Note: Test case 7.1.4.2 uses UM DRB representing real time services suitable for semi-persistent scheduling. This test case uses semi-persistent scheduling intervals shorter than 10 subframes use AM DRB representing interactive services where the shorter scheduling interval is used to reduce latency.

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.2b.3.2 Test procedure sequence

Table 7.1.4.2b.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits RRCConnectionReconfiguration to configure UL SPS	<–	–	–	–
2	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
3	The SS transmits a DL MAC PDU containing 3 RLC SDU’s on UM DRB.	<–	MAC PDU	–	–
4	The UE transmits a Scheduling Request, indicating that loop back PDUs are ready for transmission in UL RLC	–>	(SR)	–	–
5	The SS transmits an UL Grant using UE’s SPS C-RNTI in SF-Num ‘4’, NDI=0, allowing the UE to transmit one loop back PDU per MAC PDU. (Note 1)	<–	(UL SPS Grant)	–	–
6	Check: Does the UE transmit a MAC PDU in SF-Num ‘8’ as per grant in step 5? (Note 1)	–>	MAC PDU	1	P
7	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
–	EXCEPTION: Steps 8a1 to 8a4 and steps 8b1 to 8b7 describe alternative behaviours; the "lower case letter" identifies a step sequence that take place depending if mode is FDD or TDD.	–	–	–	–
8a1	IF FDD mode THEN Check: Does the UE transmit a MAC PDU in SF-Num ‘10’ as per grant in step 5? (Note 1)	–>	MAC PDU	1	P
8a2	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
8a3	Check: Does the UE transmit a MAC PDU in SF-Num ‘12’ as per grant in step 5? (Note 1)	–>	MAC PDU	1	P
8a4	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
8b1	ELSE IF TDD mode THEN Check: Does the UE transmit a MAC PDU in SF-Num ‘10’ as per grant in step 5? (Note 1, Note 2)	–>	MAC PDU	2	F
8b2	Check: Does the UE transmit a MAC PDU in SF-Num ‘12’ as per grant in step 5? (Note 1)	–>	MAC PDU	1	P
8b3	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
8b4	Check: Does the UE transmit a MAC PDU in SF-Num ‘14’ as per grant in step 5? (Note 1, Note 2)	–>	MAC PDU	2	F
8b5	Check: Does the UE transmit a MAC PDU in SF-Num ‘16’ as per grant in step 5? (Note 1, Note 3)	–>	MAC PDU	3	F
8b6	Check: Does the UE transmit a MAC PDU in SF-Num ‘18’ as per grant in step 5? (Note 1)	–>	MAC PDU	1	P
8b7	The SS transmits a HARQ ACK	<–	HARQ ACK	–	–
Note 1: SF-Num = [10*SFN + subframe] modulo 10240. Note 2: Subframes correspondent to SF-Num ’10’ (subframe 0) and SF-Num ’14’ (subframe 4) are downlink subframes for TDD uplink-downlink configuration 1 (TS 36.211, Table 4.2-2). Note 3: Subframe correspondent to SF-Num ’16’ (subframe 6) is a special subframe for TDD uplink-downlink configuration 1 (TS 36.211, Table 4.2-2).

7.1.4.2b.3.3 Specific message contents

Table 7.1.4.2b.3.3-1: RadioResourceConfigDedicated (Step 1)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	‘FFF0’H
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
setup SEQUENCE {
semiPersistSchedIntervalUL	sf2	2 subframes
implicitReleaseAfter	e2
p0-Persistent	Not Present
twoIntervalConfig	Not Present
}
}
}
}

7.1.4.3 Logical channel prioritization handling

7.1.4.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { sending data on the uplink }

then { UE serves the logical channels according to their priority and configured PBR }

}

7.1.4.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clauses 5.4.3.1.

[TS 36.321, clause 5.4.3.1]

The Logical Channel Prioritization procedure is applied when a new transmission is performed.

RRC controls the scheduling of uplink data by signalling for each logical channel: priority where an increasing priority value indicates a lower priority level, prioritisedBitRate which sets the Prioritized Bit Rate (PBR), bucketSizeDuration which sets the Bucket Size Duration (BSD).

The UE shall maintain a variable Bj for each logical channel j. Bj shall be initialized to zero when the related logical channel is established, and incremented by the product PBR × TTI duration for each TTI, where PBR is Prioritized Bit Rate of logical channel j. However, the value of Bj can never exceed the bucket size and if the value of Bj is larger than the bucket size of logical channel j, it shall be set to the bucket size. The bucket size of a logical channel is equal to PBR × BSD, where PBR and BSD are configured by upper layers.

The UE shall perform the following Logical Channel Prioritization procedure when a new transmission is performed:

– The UE shall allocate resources to the logical channels in the following steps:

– Step 1: All the logical channels with Bj > 0 are allocated resources in a decreasing priority order. If the PBR of a radio bearer is set to “infinity”, the UE shall allocate resources for all the data that is available for transmission on the radio bearer before meeting the PBR of the lower priority radio bearer(s);

– Step 2: the UE shall decrement Bj by the total size of MAC SDUs served to logical channel j in Step 1

NOTE: The value of Bj can be negative.

– Step 3: if any resources remain, all the logical channels are served in a strict decreasing priority order (regardless of the value of Bj) until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally.

– The UE shall also follow the rules below during the scheduling procedures above:

– the UE should not segment an RLC SDU (or partially transmitted SDU or retransmitted RLC PDU) if the whole SDU (or partially transmitted SDU or retransmitted RLC PDU) fits into the remaining resources;

– if the UE segments an RLC SDU from the logical channel, it shall maximize the size of the segment to fill the grant as much as possible;

– UE should maximise the transmission of data.

The UE shall not transmit data for a logical channel corresponding to a radio bearer that is suspended (the conditions for when a radio bearer is considered suspended are defined in [8]).

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

7.1.4.3.3 Test description

7.1.4.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] with the exceptions listed in table 7.1.4.3.3.1-2 applicable for the configured UM DRBs and table 7.1.4.3.3.1-3 for SR configuration.

– The condition SRB2-DRB(1,3) is used for step 8 in 4.5.3A.3 according to [18].

– The 3 UM DRBs are configured according to table 7.1.4.3.3.1-1.

Table 7.1.4.3.3.1-1: Priority, PBR and Bucket Delay settings

DRB	priority	prioritizedBitRate (kbytes/s)	bucketSizeDuration (ms)
DRB1	6	8	100
DRB2	7	16	100
DRB3	8	32	100

Table 7.1.4.3.3.1-2: PDCP Settings

Parameter	Value
Discard_Timer	ms1500

Table 7.1.4.3.3.1-3: SchedulingRequest-Config

Derivation Path: 36.508 Table 4.6.3-20
Information Element	Value/remark	Comment	Condition
dsr-TransMax	n16

7.1.4.3.3.2 Test procedure sequence

Table 7.1.4.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 0 to 4 are run 4 times using the parameters specified for each run in table 7.1.4.3.3.2-3.	–	–	–	–
0	Void	–	–	–	–
1	The SS transmits N1 320-octet RLC SDUs on DRB1, N2 320-octet RLC SDUs on DRB2, and N3 320-octet RLC SDUs on DRB3.	<–	(RLC SDUs)	–	–
–	EXCEPTION: In parallel to the event described in step 2 the events specified in Table 7.1.4.3.3.2-2 shall take place.	–	–	–	–
2	The SS is configured for Uplink Grant Allocation Type 2. 150 ms after Step 1 (Note1), for a duration of T2, the SS transmits an UL grant of D octets every T1.	<–	(UL grants)	–	–
3	Check: are the total number of octets of the UL RLC SDUs received at the SS for each DRB as follows? – the total number of octets received for DRB1 is D1 octets +/- 10% – the total number of octets received for DRB2 is D2 octets +/- 10% – the total number of octets received for DRB3 is D3 octets +/- 10%	–	–	1	P
4	The SS re-establishes the RLC for each RB at the UE by sending an RRCConnectionReconfiguration for intra-cell handover with SR configuration set as per Table 7.1.4.3.3.1-3.	–	–	–	–
Note 1: This wait time will ensure that a) all octets have been completely received by the UE on all 3 DRBs before the first UL grant is received and b) the Bjs for each logical channel have reached their maximum value i.e. the bucket size of the corresponding logical channel before the first UL grant is received.

Table 7.1.4.3.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit the RLC SDUs back to the SS?	–>	–	1	P

Table 7.1.4.3.3.2-3: Test parameter values

Parameter	First run	Second run	Third run	Fourth run
N1 (SDUs)	13	13	7	104
N2 (SDUs)	25	25	50	25
N3 (SDUs)	50	50	50	50
D (octets)	1143	573	1143	1143
T1 (ms)	20	20	20	10
T2 (ms)	500	700	500	500
D1 (octets)	4160	4160	2240	33000 (Note 1)
D2 (octets)	8000	8000	10260 (Note 1)	8000
D3 (octets)	16000	7790 (Note 1)	16000	16000
Note 1: It is calculated from the following equation for the case of the least header size. (D1 + D2 + D3) = (D – 3) * T2 / T1

NOTE: the numbers above and the test procedure assume that the UE has a loopback buffer of at least 57280 octets.

7.1.4.3.3.3 Specific message contents

Table 7.1.4.3.3.3-1: RRCConnectionReconfiguration (step 4, table 7.1.4.3.3.2-1)

Derivation Path: 36.508 table 4.6.1-8: RRCConnectionReconfiguration, condition HO
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInfo SEQUENCE {
targetPhysCellId	Set to the physical cell identity of cell 1
carrierFreq	Not present
}
}
}
}
}

7.1.4.3a Logical channel prioritization handling / UE with limited TB size

7.1.4.3a.1 Test Purpose (TP)

Same as 7.1.4.3.1.

7.1.4.3a.2 Conformance requirements

Same as sub-clause 7.1.4.3.2.

7.1.4.3a.3 Test description

7.1.4.3a.3.1 Pre-test conditions

Same as the pre-test conditions in sub-clause 7.1.4.3.1 with the following exceptions in the preamble:

– The 3 UM DRBs are configured according to table 7.1.4.3a.3.1-1 instead of table 7.1.4.3.3.1-1.

Table 7.1.4.3a.3.1-1: Priority, PBR and Bucket Delay settings

DRB	Priority	prioritizedBitRate (kbytes/s)	bucketSizeDuration (ms)
DRB1	6	8	50
DRB2	7	8	50
DRB3	8	32	50

7.1.4.3a.3.2 Test procedure sequence

Same as the test procedure in sub-clause 7.1.4.3.2 with the following exceptions:

– Step 1: 120 octet-RLC SDUs are used instead of 320 octet-RLC SDUs.

– Test parameters according to Table 7.1.4.3a.3.2-3 replace the test parameters in Table 7.1.4.3.3.2-3.

Table 7.1.4.3a.3.2-3: Test parameter values

Parameter	First run	Second run	Third run	Fourth run
N1 (SDUs)	7	7	4	24
N2 (SDUs)	7	7	20	3
N3 (SDUs)	10	10	4	3
D (octets)	125	97	125	125
T1 (ms)	10	10	10	10
T2 (ms)	250	250	250	250
D1 (octets)	840	840	480	2280 (Note 1)
D2 (octets)	840	840	2040 (Note 1)	360
D3 (octets)	1200	620 (Note 1)	480	360
Note 1: It is calculated from the following equation for the case of the estimated minimum RLC+MAC header size. (D1 + D2 + D3) = (D 5) * T2 / T1

NOTE: The numbers above and the test procedure assume that the UE has a loopback buffer of at least 3600 octets (forth run: 30 SDUs * 120 octets per SDU).

7.1.4.3a.3.3 Specific message contents

Same as sub-clause 7.1.4.3.3.

7.1.4.4 Correct handling of MAC control information / Scheduling requests and PUCCH

7.1.4.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { PUCCH is configured and UE has UL data available for transmission and UE has no UL-SCH resources available and SR_COUNTER is less than dsr-TransMax }

then { the UE transmits a SR on every available PUCCH until resources are granted }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and has pending SR(s) }

ensure that {

when { UE receives an UL grant for a new transmission }

then { UE cancels all pending SR(s) }

}

7.1.4.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.4.

[TS 36.321, clause 5.4.4]

The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.

When an SR is triggered, it shall be considered as pending until it is cancelled.

If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.

As long as one SR is pending, the UE shall for each TTI:

– if no UL-SCH resources are available for a transmission in this TTI:

– if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs;

– else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a measurement gap:

– if SR_COUNTER < dsr-TransMax:

– increment SR_COUNTER by 1;

– instruct the physical layer to signal the SR on PUCCH;

– else:

– notify RRC to release PUCCH/SRS;

– clear any configured downlink assignments and uplink grants;

– initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.

– else if UL-SCH resources for new transmission are granted in this TTI, cancel all pending SR(s).7.1.4.4.3 Test description

7.1.4.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.4.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

Table 7.1.4.4.3.1-1: RLC settings

Parameter	Value
t-PollRetransmit	250 ms

7.1.4.4.3.2 Test procedure sequence

Table 7.1.4.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a MAC PDU containing 10 MAC SDUs each containing a RLC SDU	<–	MAC PDU (containing 10 MAC SDUs)	–	–
–	EXCEPTION: Step 2 runs in parallel with behaviour in table 7.1.4.4.3.2-2.	–	–	–	–
2	Check: Does the UE transmit 6 Scheduling Requests separately on 6 consecutively available PUCCHs? (Note 1)	–>	(SR)	1	P
3	The SS is configured for Uplink Grant Allocation Type 3. The SS transmits an UL grant to allocate UL-SCH resources that are enough to transmit MAC PDU containing 10 MAC SDUs	<–	(UL Grant )	–	–
4	Check: Does the UE transmit a MAC PDU containing 10 RLC PDUs?	–>	MAC PDU (containing 10 MAC SDUs)	1	P
5	Check: For 1 second, does the UE transmit a Scheduling Request?	–>	(SR)	1,2	F
Note 1: The UE repeats the scheduling requests on every available PUCCH as long as SR_COUNTER < dsr-TransMax and there is UL data available for transmission and there are no resources available to transmit it. At the reception of first Scheduling Request from the UE, SS will be scheduled to transmit a grant after 100ms. Hence SS will receive 6 Scheduling Requests as sr-ConfigIndex = 30.

Table 7.1.4.4.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a MAC PDU?	–>	MAC PDU	1	F

7.1.4.4.3.3 Specific Message Contents

Table 7.1.4.4.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration in preamble

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration::= CHOICE {
enable SEQUENCE {
dsr-TransMax	n64
}
}

7.1.4.4.3.3 Specific Message Contents

None.

7.1.4.5 Correct handling of MAC control information / Scheduling requests and random access procedure

7.1.4.5.1 Test Purpose (TP)

(1)

with { The UE is in E-UTRA RRC_CONNECTED state and no PUCCH resource for SR is configured }

ensure that {

when { UE has UL data available for transmission, UE has no UL-SCH resources available and time alignment timer expires }

then { the UE initiates the random access procedure }

}

(2)

with { The UE in E-UTRA RRC_CONNECTED state )

ensure that {

when { PUCCH Configured and UE has UL data available for transmission and UE has no UL-SCH resources available and SR_COUNTER becomes equal to dsr-TransMax }

then { the UE transmits a PRACH Preamble to initiate a Random Access procedure }

7.1.4.5.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 , clause 5.4.4.

[TS 36.321 clause 5.4.4]

The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.

When an SR is triggered, it shall be considered as pending until it is cancelled.

If an SR is triggered and there is no other SR pending, the UE shall set the SR_COUNTER to 0.

As long as one SR is pending, the UE shall for each TTI:

– if no UL-SCH resources are available for a transmission in this TTI:

– if the UE has no valid PUCCH resource for SR configured in any TTI: initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs;

– else if the UE has a valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a measurement gap:

– if SR_COUNTER < dsr-TransMax:

– increment SR_COUNTER by 1;

– instruct the physical layer to signal the SR on PUCCH;

– else:

– notify RRC to release PUCCH/SRS;

– clear any configured downlink assignments and uplink grants;

– initiate a Random Access procedure (see subclause 5.1) and cancel all pending SRs.

– else if UL-SCH resources for new transmission are granted in this TTI, cancel all pending SR(s).

7.1.4.5.3 Test description

7.1.4.5.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.5.3.2 Test procedure sequence

Table 7.1.4.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a MAC PDU containing a Timing Advance Command MAC Control Element, but does not send any subsequent alignments.	<–	MAC PDU (Timing Advance Command)	–	–
1A	The SS transmits a MAC PDU containing a MAC SDU	<–	MAC PDU (MAC SDU)	–	–
–	EXCEPTION: Step 2B is repeated less than 64 times (dsr-TransMax)	–	–	–	–
2B	The UE may transmit Scheduling Requests before time alignment timer expires. The SS shall not respond to the Scheduling Requests in this step. (Note 5)	–>	(SR)	–	–
2	Check: does the UE transmit a preamble on PRACH? (Note 1)	–>	(PRACH Preamble)	1	P
3	The SS transmits a Random Access Response including an UL grant to enable UE to transmit C-RNTI MAC Control Element and the MAC SDU as received in step 1A.	<–	Random Access Response	–	–
4	The UE transmit a MAC PDU including a C-RNTI MAC Control Element and a MAC SDU. (Note 2)	–>	MAC PDU (C-RNTI control element, MAC SDU)	–	–
5	The SS sends PDCCH transmission for UE C-RNTI	<–	–	–	–
5A	The SS transmits RRCConnectionReconfiguration containing a radioResourceConfiguration with a physical channel reconfiguration	<–		–	–
–	EXCEPTION: Steps 5A1 to 5A4 are optionally executed. (Note 6)	–		–	–
5A1	The UE transmits a preamble on PRACH. (Note 6)	–>	(PRACH Preamble)	–	–
5A2	The SS transmits a Random Access Response including an UL grant of 7 bytes. (Note 7)	<–	Random Access Response	–	–
5A3	The UE transmit a MAC PDU including a C-RNTI MAC Control Element	–>	–	–	–
5A4	The SS sends PDCCH transmission for UE C-RNTI of 5 bytes (Note 9)	<–	–	–	–
5B	The UE transmits a Scheduling Request on PUCCH. (Note 8)	–>	(SR)	–	–
5C	The SS transmits an UL grant to enable UE to transmit the RRCConnectionReconfigurationComplete message. (Note 10)	<–	(UL Grant)	–	–
5D	The UE transmits RRCConnectionReconfigurationComplete message.	–>	–	–	–
5E	Void	–	–	–	–
6	The SS ignores any Scheduling Requests from the UE.	–	–	–	–
7	The SS transmits a MAC PDU containing one MAC SDU containing a RLC SDU	<–	MAC PDU MAC SDU)	–	–
–	EXCEPTION: Step 8 shall be repeated 8 times.	–	–	–	–
8	The UE transmits a Scheduling Request on PUCCH (Note 3)	–>	(SR)	–	–
9	Check: does the UE transmit a preamble on PRACH? (Note 4)	–>	(PRACH Preamble)	2	P
10	The SS transmits a Random Access Response including an UL grant to enable UE to transmit C-RNTI MAC Control Element and the MAC SDU as received in step 7.	<–	Random Access Response	–	–
11	The UE transmit a MAC PDU including a C-RNTI MAC Control Element and a MAC SDU. (Note 2)	–>	MAC PDU (C-RNTI control element, MAC SDU)	–	–
12	The SS sends PDCCH transmission for UE C-RNTI	<–	–	–	–
Note 1: When UL time alignment timer expires in the UE then "UL synchronization" is lost and the UE initiates a Random Access Procedure. Note 2: The UE transmission of the MAC PDU ensures that the random access procedure was successful. Note 3: The UE repeats the scheduling requests as long as SR_COUNTER < dsr-TransMax and there is data in the transmission buffer and there are no resources available to transmit it. Note 4: Reception of PRACH Preamble by the SS verifies that UE has initiated a Random Access procedure triggered by SR_COUNTER having reached dsr-TransMax. Note 5: In step 2B, SR repetition of 63 times (dsr-TransMax (64)) will take at least 63*20 = 1260 ms which is much larger than TA timer 750ms. Note 6: RLC status PDU may trigger the UE to transmit PRACH Preamble. Note 7: UL grant of 56 bits (ITBS=4, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen to allow the UE to transmit C-RNTI MAC Control Element but not allowing the UE to transmit RRCConnectionReconfiguration Complete. 7 bytes allow transmission of C-RNTI + Short BSR or C-RNTI + STATUS PDU. Note 8: If RRCConnectionReconfigurationComplete was not ready for transmission in step 5A3 then SR is triggered when RRC message arrives in the transmission buffer. Otherwise (RRCConnectionReconfigurationComplete was ready for the transmission in step 5A3) the SR is triggered because expiry of the retxBSR-Timer. Note 9: 5 bytes are assigned so that STATUS PDU can be included if it was not transmitted by the UE in step 5A3 (see Note 7) (5 bytes assignment allow transmission of Short BSR + STATUS PDU) Note 10: STATUS PDU is included if optional test steps 5A1 to 5A4 were not executed.

7.1.4.5.3.3 Specific Message Contents

Table 7.1.4.5.3.3-1: SchedulingRequest-Config to be used in RRCConnectionReconfiguration ( preamble, Table 7.1.4.5.3.2-1)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Config-DEFAULT::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64
}
}

Table 7.1.4.5.3.3-2: RRCConnectionReconfiguration (step 5A, Table 7.1.4.5.3.2-1)

Derivation Path: 36.331 clause 6.2.2
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
measConfig	Not present
mobilityControlInfo	Not present
dedicatedInfoNASList	Not present
radioResourceConfigDedicated	RadioResourceConfigDedicated-Step5a
securityConfigHO	Not present
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

Table 7.1.4.5.3.3-3: RadioResourceConfigDedicated-Step5A (Table 7.1.4.5.3.3-2)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-HO ::= SEQUENCE {
srb-ToAddModList	Not present
drb-ToAddModList	Not present
drb-ToReleaseList	Not present
mac-MainConfig	Not present
sps-Config	Not present
physicalConfigDedicated	PhysicalConfigDedicated-Step5a
}

Table 7.1.4.5.3.3-4: PhysicalConfigDedicated-Step5A (Table 7.1.4.5.3.3-3)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pdsch-ConfigDedicated	Not present
pucch-ConfigDedicated	Not present
pusch-ConfigDedicated	Not present
uplinkPowerControlDedicated	Not present
tpc-PDCCH-ConfigPUCCH	Not present
tpc-PDCCH-ConfigPUSCH	Not present
cqi-ReportConfig	CQI-ReportConfig- DEFAULT using condition CQI_PERIODIC	See subclause 4.6.3 of 36.508
soundingRS-LU-ConfigDedicated	SoundingRS-ULl-ConfigDedicated-DEFAULT	See subclause 4.6.3 of 36.508
antennaInfo	Not present
schedulingRequestConfig	SchedulingRequest-Config- Config-Step5a
}

Table 7.1.4.5.3.3-5: SchedulingRequest-Config-Step5A (Table 7.1.4.5.3.3-4)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Config::= CHOICE {
enable SEQUENCE {
dsr-TransMax	n8
}
}

Table 7.1.4.5.3.3-6: MAC-MainConfig-RBC in RRCConnectionReconfiguration(preamble)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
retxBSR-Timer	sf320
}
}

7.1.4.6 Correct handling of MAC control information / Buffer status / UL data arrive in the UE Tx buffer and retransmission of BSR / Regular BSR

7.1.4.6.1 Test Purpose (TP)

(1)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

when { UL data arrives in the UE transmission buffer and the data belongs to a logical channel with higher priority than those for which data is already available for transmission and the new logical channel and the existing logical channels belongs to the different LCG }

then { UE Reports a Long Buffer Status Reporting (BSR) }

}

(2)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

when { UL data arrives in the UE transmission buffer and there is no data available for transmission for any of the logical channels which belong to a LCG }

then { UE Reports a Short Buffer Status Reporting (BSR) }

}

(3)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

then { UE Reports a Short Buffer Status Reporting (BSR) }

}

(4)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure t hat {

when{RETX_BSR_TIMER expires and only one LCG has data available for transmission }

then { UE triggers a regular BSR and Reports a Short Buffer Status Reporting ( BSR)}

}

(5)

with (UE in E-UTRA RRC_CONNECTED stat e)

ensure that {

when { a Regular BSR has been triggered and UE has pending data for transmission and UE has only resources to send either BSR report or data }

then { UE transmits the BSR report }

}

(6)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

when { UE determines that a BSR has been triggered since the last transmission of a BSR and UE has no UL resources allocated for new transmission for this TTI }

then { UE transmits a scheduling request }

}

(7)

with (UE in E-UTRA RRC_CONNECTED state)

ensure that {

when { a Regular BSR has been triggered and UE has pending data on several logical channels for transmission and UE has only UL resources to send all pending data available for transmission, but UL grant is not sufficient to additionally accommodate the BSR MAC control element}

then { UE cancels the triggered BSR report and transmits the UL data}

}

(8)

with (UE in E-UTRA RRC_CONNECTED state)

ensure that {

when { a Regular BSR has been triggered and UE has pending data on several logical channels for transmission and UE has UL resources to send all pending data including BSR }

then { UE transmits the UL data and reports buffer status reporting (BSR) that indicates there is no more data in the buffer}

}

7.1.4.6.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5, 6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323 clause 4.5.

[TS 36.321 clause 5.4.3.1]

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

[TS 36.321 clause 5.4.4]

The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.

[TS 36.321 clause 5.4.5]

The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers of the UE. RRC controls BSR reporting by configuring the two timers periodicBSR-Timer and retxBSR-Timer and by, for each logical channel, optionally signalling logicalChannelGroup which allocates the logical channel to an LCG [8].

For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

– UL data, for a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or in the PDCP entity (the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively) and either the data belongs to a logical channel with higher priority than the priorities of the logical channels which belong to any LCG and for which data is already available for transmission, or there is no data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR";

– UL resources are allocated and number of padding bits is equal to or larger than the size of the Buffer Status Report MAC control element plus its subheader, in which case the BSR is referred below to as "Padding BSR";

– retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR";

– periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

For Regular and Periodic BSR:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR;

– else report Short BSR.

For Padding BSR:

– if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Truncated BSR of the LCG with the highest priority logical channel with data available for transmission;

– else report Short BSR.

– else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report Long BSR.

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the UE has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;

– start or restart periodicBSR-Timer except when the BSR is a Truncated BSR;

– start or restart retxBSR-Timer.

– else if a Regular BSR has been triggered:

– a Scheduling Request shall be triggered.

A MAC PDU shall contain at most one MAC BSR control element, even when multiple events trigger a BSR by the time a BSR can be transmitted in which case the Regular BSR and the Periodic BSR shall have precedence over the padding BSR.

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.

All triggered BSRs shall be cancelled in case the UL grant can accommodate all pending data available for transmission but is not sufficient to additionally accommodate the BSR MAC control element plus its subheader. All triggered BSRs shall be cancelled when a BSR is included in a MAC PDU for transmission.

[TS 36.321 clause 6.1.2]

MAC control elements are always placed before any MAC SDU.

[TS 36.321 clause 6.1.3.1]

Buffer Status Report (BSR) MAC control elements consist of either:

– Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or

– Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).

The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1.-1.

The fields LCG ID and Buffer Size are defined as follow:

– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;

– Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a logical channel group after the MAC PDU has been built. The amount of data is indicated in number of bytes. It shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits. The values taken by the Buffer Size field are shown in Table 6.1.3.1-1.

Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element

Figure 6.1.3.1-2: Long BSR MAC control element

Table 6.1.3.1-1: Buffer size levels for BSR

Index	Buffer Size (BS) value [bytes]	Index	Buffer Size (BS) value [bytes]
0	BS = 0	32	1132 < BS <= 1326
1	0 < BS <= 10	33	1326 < BS <= 1552
2	10 < BS <= 12	34	1552 < BS <= 1817
3	12 < BS <= 14	35	1817 < BS <= 2127
4	14 < BS <= 17	36	2127 < BS <= 2490
5	17 < BS <= 19	37	2490 < BS <= 2915
6	19 < BS <= 22	38	2915 < BS <= 3413
7	22 < BS <= 26	39	3413 < BS <= 3995
8	26 < BS <= 31	40	3995 < BS <= 4677
9	31 < BS <= 36	41	4677 < BS <= 5476
10	36 < BS <= 42	42	5476 < BS <= 6411
11	42 < BS <= 49	43	6411 < BS <= 7505
12	49 < BS <= 57	44	7505 < BS <= 8787
13	57 < BS <= 67	45	8787 < BS <= 10287
14	67 < BS <= 78	46	10287 < BS <= 12043
15	78 < BS <= 91	47	12043 < BS <= 14099
16	91 < BS <= 107	48	14099 < BS <= 16507
17	107 < BS <= 125	49	16507 < BS <= 19325
18	125 < BS <= 146	50	19325 < BS <= 22624
19	146 < BS <= 171	51	22624 < BS <= 26487
20	171 < BS <= 200	52	26487 < BS <= 31009
21	200 < BS <= 234	53	31009 < BS <= 36304
22	234 < BS <= 274	54	36304 < BS <= 42502
23	274 < BS <= 321	55	42502 < BS <= 49759
24	321 < BS <= 376	56	49759 < BS <= 58255
25	376 < BS <= 440	57	58255 < BS <= 68201
26	440 < BS <= 515	58	68201 < BS <= 79846
27	515 < BS <= 603	59	79846 < BS <= 93479
28	603 < BS <= 706	60	93479 < BS <= 109439
29	706 < BS <= 826	61	109439 < BS <= 128125
30	826 < BS <= 967	62	128125 < BS <= 150000
31	967 < BS <= 1132	63	BS > 150000

[TS 36.321 clause 6.2.1]

Table 6.2.1-2: Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

[TS 36.323 clause 4.5]

For the purpose of MAC buffer status reporting, the UE shall consider the following as data available for transmission in the PDCP layer:

For SDUs for which no PDU has been submitted to lower layers:

– the SDU itself, if the SDU has not yet been processed by PDCP, or

– the PDU (control or data) if the SDU has been processed by PDCP.

7.1.4.6.3 Test description

7.1.4.6.3.1 Pre-test conditions

System Simulator :

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.6.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(3,0) is used for step 8 in 4.5.3A.3 according to [18].

– 3 AM DRBS are configured with the following parameters:

Table 7.1.4.6.3.1-1: Logical Channel Configuration Settings

Parameter	Value DRB1	Value DRB2	Value DRB3
LogicalChannel-Identity	3	4	5
Priority	8	7	6
prioritizedBitRate	0 kB/s	0 kB/s	0 kB/s
logicalChannelGroup	2 (LCG ID#2)	2 (LCG ID#2)	1 (LCG ID#1)

7.1.4.6.3.2 Test procedure sequence

Table 7.1.4.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU containing two RLC SDUs of size 10 bytes on LC 3	<–	MAC PDU (2 RLC SDUs on LC 3)	–	–
3	SS allocates an UL Grant of 32 bits. (Note 1)	<–	(UL Grant, 32 bits)	–	–
4	Check: Does the UE transmit a Short BSR with ‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field set to value ‘6’ or bigger? (Note 2)	–>	MAC PDU (MAC Short BSR (LCG ID=‘2’, Buffer Size=’6’ or bigger))	2,5	P
5	Wait for retxBSR-Timer expiry on UE side.	–	–	–	–
6	Check: Does the UE transmit a scheduling request?	–>	(SR)	6	P
7	The SS respond to the scheduling request in step 6 by an UL Grant of 32 bits. (Note 1)	<–	(UL Grant, 32 bits)	–	–
8	Check: Does the UE transmit a Short BSR with ‘LCG ID’ field set to ‘2’ and ‘Buffer size’ field set to value ‘6’ or bigger? (Note 2)	–>	MAC PDU (MAC Short BSR (LCG ID=‘2’, Buffer Size=’6’ or bigger))	4,5	P
9	The SS transmits a MAC PDU containing one RLC SDUs of size 10 bytes on LC 4	<–	MAC PDU (1 RLC SDUs on LC 4)	–	–
10	Check: Does the UE transmit a scheduling request?	–>	(SR)	6	P
11	The SS respond to the scheduling request in step 10 by an UL Grant of 32 bits. (Note 1)	<–	(UL Grant, 32 bits)	–	–
12	Check: Does the UE transmit a Short BSR with ‘LCG ID’ field set to ‘2’ and ‘Buffer size#1’ field set to value ‘8’ or bigger? (Note 2)	–>	MAC PDU (MAC Short BSR (LCG ID=‘2’, Buffer Size=’8’ or bigger))	3,5	P
13	The SS transmits a MAC PDU containing two RLC SDUs of size 4 bytes on LC 5	<–	MAC PDU (2 RLC SDUs on LC 5)	–	–
14	Check: Does the UE transmit a scheduling request?	–>	(SR)	6	P
15	The SS respond to the scheduling request in step 14 by one UL Grant of 32 bits. (Note 1)	<–	(UL Grant, 32 bits)	–	–
16	Check: Does the UE transmit a Long BSR with ‘Buffer size#1’ field set to value ‘1’, ‘Buffer size#2’ field set to value ‘8’ or bigger? (Note 3)	–>	MAC PDU (MAC Long BSR (Buffer size#1=’1’ or bigger, Buffer size#2=’8’ or bigger)	1,5	P
17	Wait for retxBSR-Timer expiry on the UE side.	–		–	–
18	Check: Does the UE transmit a scheduling request?	–>	(SR)	6	P
19	SS allocates an UL Grant of 424 bits. (Note 4)	<–	(UL Grant, 424 bits)	–	–
20	Check: Does the UE transmit a MAC PDU including five RLC SDUs and not including any BSR? (Note 5)	–>	MAC PDU (SDU subheader, AMD PDU header and 2 RLC SDUs on LC 3, SDU subheader, AMD PDU header and 1 RLC SDUs on LC 4, SDU subheader, AMD PDU header and 2 RLC SDUs on LC 5)	7	P
21	The SS transmits a MAC PDU containing two MAC SDUs, the first containing a 8 byte RLC SDU with LCID set to ‘00011’ and the second containing a 7 byte RLC SDU with LCID set to ‘00101’.	<–	MAC PDU (MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’10’), MAC sub-header (E=’0’, LCID=’00101’,), AMD PDU, AMD PDU)	–	–
22	The UE sends Scheduling Request	–>	(SR)	–	–
23	The SS transmits an uplink grant of size 256 bits. (Note 6)	<–	(UL grant)	–	–
24	Check: Does the UE return a MAC PDU of length 256 bits including 2 RLC SDUs, Padding and Short BSR or LongBSR with Buffer size(s) set to ‘0’? (Note 5) (Note 7)	–>	MAC PDU (Short BSR MAC sub-header (E=’1’, LCID=’11101’, MAC sub-header (E=’1’, F=’0’), MAC sub-header (E=’1’, F=’0’), F=’0’), padding MAC sub-header (E=’0’, LCID=’11111’), Short BSR ( Buffer Size=’0’), AMD PDU, AMD PDU, padding) Or MAC PDU (Long BSR MAC sub-header (E=’1’, LCID=’11101’, MAC sub-header (E=’1’, F=’0’), MAC sub-header (E=’1’, F=’0’), F=’0’), padding MAC sub-header (E=’0’, LCID=’11111’), LongBSR ( Buffer Size=’0’), AMD PDU, AMD PDU, padding)	8	P
25	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00011’)	<–	RLC STATUS PDU (ACK_SN=1)
26	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00101’)	<–	RLC STATUS PDU (ACK_SN=1)
Note 1: 32 bits enables UE to transmit a MAC PDU with a MAC BSR header and a Short BSR (1 bytes) or a Long BSR (3 byte). Note 2: UE triggers a Short BSR of type "Regular BSR" to report buffer status for one LCG for that TTI. The UE should not send any of the received RLC SDUs (segmented) due to Regular BSR has higher priority than U-plane logical channels. Note 3: UE triggers and transmit a Long BSR of type "Regular BSR". The UL grant would be enough for UE to transmit one RLC SDU as received in step 8, but Regular BSR has higher priority than U-plane logical channels. Note 4: The UE has 38 bytes of user data (received in steps 2, 9 and 13) in the transmission buffer. 424 bits enables UE to transmit user data in MAC PDU with 2 bytes SDU subheader for LC 3, 2 bytes SDU subheader for LC 4 and 1 byte SDU subheader for LC 5, 24 bytes MAC SDU for LC 3 (2 RLC SDUs, 10 bytes each and 4 bytes AMD PDU header), 12 bytes MAC SDU for LC 4 (1 RLC SDU, 10 bytes and 2 bytes AMD PDU header, 12 bytes MAC SDU for LC 5 (2 RLC SDUs, 4 bytes each and 4 bytes AMD PDU header)) equals to 424 bits (53 bytes). Note 5 The MAC SDUs for the different logical channels may be in any order in the MAC PDU. Note 6: UL grant of 256 bits (I_TBS=6, N_PRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two MAC SDUs of size 10 and 9 bytes in a MAC PDU (8 bytes RLC SDU + 2 bytes AMD PDU header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) + 1 byte Short BSR+6 byte padding + one byte BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256 bits) or UL grant of 256 bits (I_TBS=6, N_PRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two MAC SDUs of size 10 and 9 bytes in a MAC PDU (8 bytes RLC SDU + 2 bytes AMD PDU header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) + 3 byte LongBSR + 4 byte padding + one byte BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256 bits). Note 7: It is left up to UE implementation whether ShortBSR or LongBSR is reported.

7.1.4.6.3.3 Specific Message Contents

Table 7.1.4.6.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
Explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n5
periodicBSR-Timer	Infinity
retxBSR-Timer	sf320
ttiBundling	FALSE
}
}
}
}
}
}
}
}

7.1.4.7 Correct handling of MAC control information / Buffer status / UL resources are allocated / Padding BSR

7.1.4.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the UE has available data for transmission from more than one LCG in the TTI where the BSR is transmitted }

then { UE reports a Truncated BSR of the LCG with the highest priority logical channel with data available for transmission }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of a Short BSR plus its subheader but smaller than the size of a Long BSR plus its subheader and the UE has available data for transmission form only one LCG in the TTI where the BSR is transmitted }

then { UE reports a Short BSR }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of a Long BSR plus its subheader }

then { UE reports a long BSR }

}

7.1.4.7.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5, 6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323, clause 4.5.

[TS 36.321 clause 5.4.3.1]

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

[TS 36.321 clause 5.4.5]

For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

…

For padding BSR:

– if the number of padding bits is equal to or larger than the size of the Short BSR plus its sub header but smaller than the size of the Long BSR plus its subheader:

– else report Short BSR.

– else if the number of padding bits is equal to or larger than the size of the Long BSR plus its sub header, report Long BSR.

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the UE has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;

– start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;

– start or restart retxBSR-Timer.

– else if a Regular BSR has been triggered:

– a Scheduling Request shall be triggered.

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.

[TS 36.321 clause 6.1.2]

MAC control elements are always placed before any MAC SDU.

[TS 36.321 clause 6.1.3.1]

Buffer Status Report (BSR) MAC control elements consist of either:

– Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or

– Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).

The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.

The fields LCG ID and Buffer Size are defined as follow:

– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;

Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element

Figure 6.1.3.1-2: Long BSR MAC control element

[TS 36.321 clause 6.2.1]

Table 6.2.1-2: Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

[TS 36.323 clause 4.5]

For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as data available for transmission in the PDCP layer:

For SDUs for which no PDU has been submitted to lower layers:

– the SDU itself, if the SDU has not yet been processed by PDCP, or

– the PDU (control or data) if the SDU has been processed by PDCP.

7.1.4.7.3 Test description

7.1.4.7.3.1 Pre-test conditions

System Simulator:

Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.7.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(2,0) is used for step 8 in 4.5.3A.3 according to [18].

– 2 AM DRBS are configured with the parameters specified in table 7.1.4.7.1-1.

Table 7.1.4.7.1-1: Logical Channel Configuration Settings

Parameter	DRB1	DRB2
LogicalChannel-Identity	3	4
Priority	7	6
prioritizedBitRate	0kbs	0kbs
logicalChannelGroup	2 (LCG ID#2)	1 (LCG ID#1)

7.1.4.7.3.2 Test procedure sequence

Table 7.1.4.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
–	EXCEPTION: Step 2 shall be repeated for 2 times	–	–	–	–
2	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes on logical channel 4.	<–	MAC PDU (RLC SDU on LC 4)	–
3	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes on logical channel 3.	<–	MAC PDU (RLC SDU on LC 3)	–	–
4	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
5	The SS sends an uplink grant of size 32 bits. (Note 1)	<–	(UL grant)	–	–
6	The UE transmit a Long BSR report	–>	MAC PDU (Long BSR header (LCID=’11110’), Long BSR)	–	–
7	The SS is configured for Uplink Grant Allocation Type 3. The SS sends an uplink grant of size 136 bits. (Note 2)	<–	(UL grant)	–	–
8	Check: Does UE transmit a MAC PDU containing an RLC SDU and a Truncated BSR indicating pending data (‘Buffer size’ field > ‘0’) for logicalChannelGroup 1 (‘LCG ID’ field set to ‘01’)?	–>	MAC PDU (Truncated BSR header (LCID=’11100’), Truncated BSR(LCG ID =’01’, Buffer size>’0’), RLC SDU)	1	P
9	Void	–	–	–	–
10	The SS is configured for Uplink Grant Allocation Type 3. The SS sends an uplink grant of size 136 bits (Note 2)	<–	(UL grant)	–	–
11	Check: Does UE transmit a MAC PDU containing an RLC SDU and with a Short BSR indicating pending data (‘Buffer size’ field > ‘0’) for logicalChannelGroup 2 (‘LCG ID’ field =’10’)?	–>	MAC PDU (Short BSR header(LCID=’11101’), Short BSR(LCG ID =’10’,Buffer size>’0’), RLC SDU)	2	P
12	Void	–	–	–	–
13	Void	–	–	–	–
14	The SS is configured for Uplink Grant Allocation Type 3. The SS sends an uplink grant of size 152 bits. (Note 3)	<–	(UL grant)	–	–
15	Check: Does UE transmit a MAC PDU containing a RLC SDU and a Long BSR?	–>	MAC PDU (Long BSR header (LCID=’11110’), Long BSR), RLC SDU)	3	P
Note 1: SS transmit an UL grant of 32 bits (I_TBS=0, N_PRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a Regular BSR triggered by the new data received logicalChannelGroup 1 and 2 in steps 2 and 3. This to enable testing of Padding BSR which has lower priority than Regular BSR. Note 2: UL grant of 136 bits (I_TBS=9, N_PRB=1, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR. RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include Short/Truncated BSR. Note 3: UL grant of 152 bits (I_TBS=0, N_PRB=6, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits will be equal to or larger than the size of Long BSR. RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of Long BSR is 3 bytes, i.e. setting UL grant to 19 bytes (152 bits) enable UE to include padding Long BSR.

7.1.4.7.3.3 Specific Message Contents

None

7.1.4.7a Correct handling of MAC control information / Buffer status / UL resources are allocated / Cancellation of Padding BSR

7.1.4.7a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE has transmitted a MAC PDU with a Regular BSR and padding such that a padding BSR is triggered AND UE has remaining data causing continuous data transmission while periodicBSR-Timer is running without causing any Regular BSR or padding BSR to be triggered }

then { UE reports a Periodic BSR }

}

7.1.4.7a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5, 6.1.2, 6.1.3.1 and 6.2.1 and in TS 36.323, clause 4.5.

[TS 36.321 clause 5.4.3.1]

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

[TS 36.321 clause 5.4.5]

For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

– retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR";

– periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

For Regular and Periodic BSR:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR;

– else report Short BSR.

For padding BSR:

– if the number of padding bits is equal to or larger than the size of the Short BSR plus its sub header but smaller than the size of the Long BSR plus its subheader:

– else report Short BSR.

– else if the number of padding bits is equal to or larger than the size of the Long BSR plus its sub header, report Long BSR.

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the UE has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;

– start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;

– start or restart retxBSR-Timer.

– else if a Regular BSR has been triggered:

– a Scheduling Request shall be triggered.

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.

[TS 36.321 clause 6.1.2]

MAC control elements are always placed before any MAC SDU.

[TS 36.321 clause 6.1.3.1]

Buffer Status Report (BSR) MAC control elements consist of either:

– Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or

– Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).

The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.

The fields LCG ID and Buffer Size are defined as follow:

– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;

Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element

Figure 6.1.3.1-2: Long BSR MAC control element

[TS 36.321 clause 6.2.1]

Table 6.2.1-2: Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

[TS 36.323 clause 4.5]

For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as data available for transmission in the PDCP layer:

For SDUs for which no PDU has been submitted to lower layers:

– the SDU itself, if the SDU has not yet been processed by PDCP, or

– the PDU (control or data) if the SDU has been processed by PDCP.

7.1.4.7a.3 Test description

7.1.4.7a.3.1 Pre-test conditions

System Simulator:

Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Tables 7.1.4.7a.3.3-1-3.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(3,0) is used for step 8 in 4.5.3A.3 according to [18].

– 3 AM DRBS are configured with the parameters specified in table 7.1.4.7a.1-1.

Table 7.1.4.7a.1-1: Logical Channel Configuration Settings

Parameter	Value DRB1	Value DRB2	Value DRB3
LogicalChannel-Identity	3	4	5
Priority	8	7	6
prioritizedBitRate	0 kB/s	0 kB/s	0 kB/s
logicalChannelGroup	2 (LCG ID#2)	1 (LCG ID#1)	1 (LCG ID#1)

7.1.4.7a.3.2 Test procedure sequence

Table 7.1.4.7a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU including an RLC SDU of size 11 bytes on logical channel 5.	<–	MAC PDU (RLC SDU on LC 5)	–
–	EXCEPTION: Step 3 shall be repeated 4 times	–	–	–	–
3	The SS transmits a MAC PDU including an RLC SDU of size 10 bytes on logical channel 4.	<–	MAC PDU (RLC SDU on LC 4)	–	–
–	EXCEPTION: Step 4 shall be repeated 5 times	–	–	–	–
4	The SS transmits a MAC PDU including an RLC SDU of size 10 bytes on logical channel 3.	<–	MAC PDU (RLC SDU on LC 3)	–	–
5	Void	–	–	–	–
6	60 ms after step 4, t he SS sends an uplink grant of size 176 bits. (Note 1)	<–	(UL grant)	–	–
7	The UE transmits a longBSR triggered by a Regular BSR report	–>	MAC PDU (Long BSR header (LCID=’11110’), MAC SDU header, Long BSR, RLC SDU, padding)	–	–
8	20 ms after step 6, the SS sends an uplink grant of 104 bits for every 10^th uplink TTI 11 times. (Note 2)	–	–	–	–
–	EXCEPTION: In parallel with step 9, the parallel behaviour in table 7.1.4.7a.3.2-2 is running until the periodic BSR is received in step 9.	–	–	–	–
9	Check: Does UE transmit a MAC PDU containing a periodic BSR? (Note 3 and Note 4)	–>	MAC PDU (Long BSR header, ,MAC SDU header, Long BSR RLC SDU segment)	1	P
–	EXCEPTION: In parallel with step 10, the parallel behaviour in table 7.1.4.7a.3.2-3 is running. Step 10 shall occur at least once. (Note 4)	–	–	–	–
10	CHECK: Does UE transmit a MAC PDU containing a MAC SDU	–>	MAC PDU (RLC SDU segments)	1	P
Note 1: UL grant of 176 bits (I_TBS=3, N_PRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits (padding header + padding payload) will be equal to or larger to trigger a padding BSR (Short BSR), i.e. 2 bytes or more (one byte for BSR sub-header and 1 bytes for a Short BSR). RLC SDU size is 11 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 4 bytes (1 byte for BSR sub header, 2 byte for MAC SDU sub-header using R/R/E/LCID/F/L and 1 byte for R/R/E padding sub header) and size of Long BSR (Regular BSR) is 3 bytes and padding is 2 bytes, i.e. setting UL grant to 22 bytes (176 bits). The remaining 3 bytes would have enabled the UE to segment a second RLC SDU if the RLC SDU belongs to the same logical channel. However, as there is only one RLC SDU available for transmission for LC5 (highest priority) then would the UE have to add a second MAC SDU to transmit a segment of an additional RLC SDU from LC4. This would require 4 bytes or more and the UE will instead add 3 bytes of padding, which will trigger a padding BSR. Note 2: UL grant of 104 bits (I_TBS=3, N_PRB=2, TS 36.213 Table 7.1.7.2.1-1) is chosen such that UE is able to transmit a MAC PDU that fits exactly a PDCP SDU to enable periodic BSR to be triggered when periodicBSR-Timer expires. RLC SDU size is 10 bytes, size of AMD PDU header is 2 bytes and size of MAC header is 1 byte (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header), i.e. setting UL grant to 13 bytes (104 bits). The UL grant is sent by the SS 11 times (every 10^th TTI) to enable UE to transmit the remaining 9 RLC SDUs and at least one periodic BSR, Note 3: The Periodic BSR is triggered by the expiry of the periodiBSR-Timer (32 sub-frames, see Table 7.1.4.7a.3.3-1) and verifies that the triggered padding BSR in step 7 in Table 7.1.4.7a.3.2-1 is cancelled by the UE. If the UE would not have cancelled the triggered padding BSR then would the UE reset the periodicBSR-Timer after each transmission causing the timer to not expire. Note 4: If UE has cancelled the triggered padding BSR in step 7 in Table 7.1.4.7a.3.2-1 then the periodicBSR-Timer will expire before all data in the transmission buffer has been sent by the UE. This verifies that the received BSR report in step 9 is triggered by a periodic BSR report and not due to a regular or padding BSR.

Table 7.1.4.7a.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a MAC PDU containing an RLC SDU	–>	MAC PDU (RLC SDU)	–	–

Table 7.1.4.7a.3.2-3: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a MAC PDU containing an RLC SDU	–>	MAC PDU (Long BSR header, ,MAC SDU header, Long BSR RLC SDU segment) or MAC PDU (Short BSR header, ,MAC SDU header, Short BSR RLC SDU segment)	–	–
2	UE transmit a MAC PDU containing a MAC SDU	–>	MAC PDU (Padding header, Long BSR header,MAC SDU header, SDU segment)	–	–

7.1.4.7a.3.3 Specific Message Contents

Table 7.1.4.7a.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
Explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n5
periodicBSR-Timer	Sf32	32 subframes
retxBSR-Timer	sf320
ttiBundling	FALSE
}
}
}
}
}
}
}
}

Table 7.1.4.7a.3.3-2: SchedulingRequest-Configuration (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 7.1.4.7a.3.3-3: RLC-Config-DRB-AM (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms500
}
}
}

7.1.4.8 Correct handling of MAC control information / Buffer status / Periodic BSR timer expires

7.1.4.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { periodicBSR-Timer expires and more than one LCG has buffered data in a TTI }

then { UE triggers a Periodic BSR and reports Long BSR }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { periodicBSR-Timer expires and one LCG has buffered data in a TTI }

then { UE triggers a Periodic BSR and reports Short BSR and restarts the periodicBSR-Timer}

}

7.1.4.8.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.5, 6.1.2, 6.1.3.1 and 6.2.1; TS 36.323 clause 4.5.

[TS 36.321 clause 5.4.5]

For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

…

– periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

For Regular and Periodic BSR:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR;

– else report Short BSR.

…

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the UE has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate a BSR MAC control element;

– start or restart the periodicBSR-Timer except when the BSR is a Truncated BSR;

– start or restart retxBSR-Timer.

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on UL-SCH.

[TS 36.321 clause 6.1.2]

MAC control elements are always placed before any MAC SDU.

[TS 36.321 clause 6.1.3.1]

Buffer Status Report (BSR) MAC control elements consist of either:

– Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or

– Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).

The BSR formats are identified by MAC PDU sub headers with LCIDs as specified in table 6.2.1.-2.

The fields LCG ID and Buffer Size are defined as follow:

– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;

Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element

Figure 6.1.3.1-2: Long BSR MAC control element

[TS 36.321 clause 6.2.1]

Table: 6.2.1-2 Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

[TS 36.323 clause 4.5]

For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as data available for transmission :

For SDUs for which no PDU has been submitted to lower layers:

– the SDU itself, if the SDU has not yet been processed by PDCP, or

– the PDU if the SDU has been processed by PDCP.

7.1.4.8.3 Test description

7.1.4.8.3.1 Pre-test conditions

System Simulator:

Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.8.3.3-1

UE:

None.

Preamble;

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(2,0) is used for step 8 in 4.5.3A.3 according to [18].

– 2 AM DRBS are configured with the parameters specified in table 7.1.4.8.1-1.

Table 7.1.4.8.1-1: Logical Channel Configuration Settings

Parameter	DRB1	DRB2
LogicalChannel-Identity	3	4
priority	7	6
prioritizedBitRate	0kbs	0kbs
logicalChannelGroup	2	1

7.1.4.8.3.2 Test procedure sequence

Table 7.1.4.8.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU containing an RLC PDU on logical channel 4 (LCG ID 1), which contains 1 RLC SDU of size 14 bytes.	<–	MAC PDU (RLC PDU)
3	The SS is configured for Uplink Grant Allocation Type 2. The SS sends an uplink grant of size 32 bits. (Note 2)	<–	(UL grant)	–	–
4	The UE transmits a short BSR report. (Note 6)	–>	MAC PDU ((LCID=’11101’, LCG ID=’01’, Buffer size index > 0)	–	–
–	EXCEPTION: Steps 5 to 6 shall be repeated two times (Note 4)	–	–	–	–
5	Wait for periodicBSR-Timer expiry.	–	–	–	–
5A	The SS sends an uplink grant of size 32 bits	–	–	–	–
6	Check: Does UE transmit a MAC PDU containing a Short BSR with ‘LCG ID’ field set to ‘01’ (logicalChannelGroup 1) and Buffer Size Index > 0?	–>	MAC PDU (LCID=’11101’, LCG ID=’01’, Buffer Size index > 0)	2	P
7	Void
8	The SS transmits a MAC PDU containing an RLC PDU on logical channel 3 (LCG ID 2), which contains 1 RLC SDU of size 14 bytes.	<–	MAC PDU (RLC PDU)	–	–
8A	The SS sends an uplink grant of size 32 bits (Note 3)	<–	(UL grant)	–	–
8B	The UE transmits a long BSR report with ‘Buffer size#1’ (LCG ID=1) and ‘Buffer size#2’ (LCG ID=2) fields set to value > ‘0’	–>	MAC PDU (( ‘Buffer size#1 index’ > 0, ‘Buffer size#2 index=’ >0’)	–	–
9	Void
–	EXCEPTION: Step 9A to 10 shall be repeated twice. (Note 5)	–	–	–	–
10	Check: Does UE transmit a MAC PDU containing a Long BSR with ‘Buffer size#1’ (LCG ID=1) and ‘Buffer size#2’ (LCG ID=2) fields set to value > ‘0’?	–>	MAC PDU	1	P
10A	The SS is configured for Uplink Grant Allocation Type 3. The SS transmits 1 UL grant of size 328 bits to enable the UE to loopback RLC SDU on LCG ID = 1 and LCG = 2. (Note 7)			–	–
11	The UE transmits MAC PDU containing the remaining RLC SDUs as sent by the SS in steps 2 and 8.	–>	MAC PDU	–	–
Note 1: Void Note 2: SS transmits an UL grant of 32 bits (I_TBS=0, N_PRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a Regular BSR triggered by the new data received logicalChannelGroup 1 in step 2. Note 3: SS transmits an UL grant of 32 bits (I_TBS=0, N_PRB=2, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a Regular BSR triggered by the new data received logicalChannelGroup 2 in step 8. Note 4: One short BSR due to first expiry of periodicBSR-Timer and one short BSR due to second expire of periodicBSR-Timer. Note 5: One long BSR due to expire of periodicBSR-Timer and one long BSR due to second expiry of periodicBSR-Timer. Note 6: The UE starts periodicBSR-Timer. Note 7: SS transmits an UL grant of 328 bits (I_TBS=7, N_PRB=3, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit RLC SDU on LCG =1 (14 bytes) and LCG = 2 (14 bytes) and a minimum MAC header of 3 bytes.

7.1.4.8.3.3 Specific Message Contents

Table 7.1.4.8.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n5
periodicBSR-Timer	sf10
retxBSR-Timer	sf10240
ttiBundling	FALSE
}
}
}
}
}
}
}
}

7.1.4.9 Void

7.1.4.10 MAC padding

7.1.4.10.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is to transmit a MAC PDU with padding exceeding 2 bytes }

then { Padding goes to the end of the MAC PDU }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is to transmit a MAC PDU with single-byte padding and there is a data MAC PDU sub-header present }

then { UE is inserting padding MAC PDU subheader before any other MAC PDU sub-header }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is to transmit a MAC PDU with two-byte padding and there is a data MAC PDU sub-header }

then { UE is inserting two padding MAC PDU subheaders before any other MAC PDU sub-header or one padding MAC PDU subheader as a last MAC PDU subheader }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is to transmit a MAC PDU with single-byte padding and there is no data MAC PDU sub-header but a MAC Control element is present }

then { UE is inserting a padding MAC PDU subheader before any other MAC PDU sub-header }

}

(5)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE is to transmit a MAC PDU with two-byte padding and there is no data MAC PDU sub-header but a MAC Control element is present}

then { UE is inserting two padding MAC PDU subheaders before any other MAC PDU sub-header or one padding MAC PDU subheader as a last MAC PDU subheader and one byte padding at the end of the MAC PDU

}

7.1.4.10.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.321, clause 6.1.2.

[TS 36.321 clause 6.1.2]

Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the UE shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed.

When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader.

A maximum of one MAC PDU can be transmitted per TB per UE.

Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding

7.1.4.10.3 Test description

7.1.4.10.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.10.3.2 Test procedure sequence

Table 7.1.4.10.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU with 10 bytes MAC SDU.	<–	MAC PDU(AMD PDU)	–	–
3	The UE transmits a Scheduling Request on PUCCH.	–	(SR)	–	–
4	The SS transmits an uplink grant of size 176 bits. (Note 1)	<–	(UL grant)	–	–
5	Check: Does the UE transmit a MAC PDU with a MAC SDU of length 10 bytes and where the last MAC sub-header has the Extension field ‘E’ set to ‘0’ and the Logical Channel ID field ‘LCID’ set to ‘11111’?	–>	MAC PDU (BSR sub-header, MAC SDU sub-header, Padding MAC sub-header (E=’0’, LCID=’11111’),Short BSR, MAC SDU, padding)	1	P
6	The SS transmits a MAC PDU with 13 bytes MAC SDU.	<–	MAC PDU(AMD PDU)	–	–
7	The UE transmits a Scheduling Request on PUCCH.	–	(SR)	–	–
8	The SS transmits an uplink grant of size 120 bits. (Note 2)	<–	(UL grant)	–	–
9	Check: Does the UE transmit a MAC PDU with a MAC SDU of length 13 bytes and with a padding MAC sub-header, with Extension field ‘E’ is set to ‘1’ and the Logical Channel ID field ‘LCID’ is set to ‘11111’, inserted before the MAC SDU sub-header?	–>	MAC PDU (Padding MAC-sub-header (E=’1’, LCID=’11111’), MAC SDU sub-header, MAC SDU)	2	P
10	The SS transmits a MAC PDU with 10 bytes MAC SDU.	<–	MAC PDU (AMD PDU)	–	–
11	The UE transmits a Scheduling Request on PUCCH.	–	(SR)	–	–
12	The SS transmits an uplink grant of size 120 bits. (Note 3)	<–	(UL grant)	–	–
13	Check: Does the UE transmit a MAC PDU with two padding MAC sub-headers, with Extension field ‘E’ is set to ‘1’ and the Logical Channel ID field ‘LCID’ is set to ‘11111’, inserted before the BSR sub-header and the MAC SDU sub-header Or a MAC PDU with BSR sub-header with Extension field ‘E’ is set to ‘1’ and MAC SDU sub-header (R/R/E/LCID/F/L) inserted before the Padding MAC sub-header?	–>	MAC PDU (Padding MAC-sub-header#1 (E=’1’, LCID=’11111’), Padding MAC-sub-header#2 (E=’1’, LCID=’11111’), BSR sub-header, MAC SDU sub-header, Short BSR, MAC-SDU) Or MAC PDU(BSR sub-header, MAC SDU sub-header, Padding MAC-sub-header(E=’0’, LCID=’11111’), Short BSR, MAC-SDU)	3	P
14	The SS transmits a Timing Advance command and does not send any subsequent timing alignments. Start Timer_T1 = Time Alignment timer value on SS.	<–	MAC PDU (Timing Advance Command)	–	–
15	40 to 50 TTI before Timer_T1 expires the SS transmits a MAC PDU containing an RLC AMD PDU.	<–	MAC PDU (AMD PDU)	–	–
16	The SS ignores scheduling requests and waits until the UE transmits a preamble on PRACH.	–>	(PRACH preamble)	–	–
17	The SS transmits a Random Access Response, with an UL Grant of 56-bits. (Note 4)	<–	Random Access Response	–	–
18	Check: Does the UE transmit a MAC PDU with a BSR sub-header (8-bits), a Control sub-header (8-bits) , a short BSR (8-bits) and a C-RNTI MAC Control Element (16-bits) ? (Note 6)	–>	MAC PDU (BSR sub-header, MAC Control sub-header, Padding MAC sub-header (E=’0’, LCID=’11111’), Short BSR, C-RNTI control element, padding) Or MAC PDU ( Padding MAC-sub-header#1 (E=’1’, LCID=’11111’), Padding MAC-sub-header#2 (E=’1’, LCID=’11111’), BSR sub-header, MAC Control sub-header, Short BSR, C-RNTI control element)	–	–
19	The SS transmits an UL grant of 24 bits. (Note 5)	<–	(UL grant)	–	–
19A	Check: Does the UE transmit a MAC PDU with a padding MAC sub header with Extension field ‘E’ is set to ‘1’ and ‘LCID’ field set to ‘11111’ (8-bits) inserted before a BSR sub-header (8bits) and a short BSR (8 bits)?	–>	MAC PDU (Padding MAC-sub-header (E=’1’, LCID=’11111’), BSR sub-header, Short BSR)	4	P
20	The SS transmits an uplink grant enabling UE to transmit loop back PDU.	<–	(UL grant)	–	–
21	The UE transmits Loop back PDU.	–>	MAC PDU(AMD PDU)	–	–
Note 1: UL grant of 176 bits (I_TBS=3, N_PRB=3, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding will be larger than 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 4 bytes (2 bytes for MAC SDU sub-header using 7-bit LI, 1 byte for BSR sub-header and 1 byte for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and resulting into 56 bits padding. Note 2: UL grant of 120 bits (I_TBS=0, N_PRB=5, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding will be a single byte. RLC SDU size is 11 bytes, size of AMD PDU header is 2 bytes and size of MAC header is 1 byte for MAC SDU sub-header, equals to 112 bits (14 bytes) and resulting into 1 single byte padding. Note 3: UL grant of 120 bits (I_TBS=0, N_PRB=5, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding will be equal to 2 bytes. RLC SDU size is 8 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 4 bytes (1 bytes for MAC SDU sub-header, 1 byte for Short BSR sub-header and 2 bytes for padding MAC sub-header) and size of Short BSR is 1 byte, equals to 120 bits (15 bytes) and resulting no padding at the end of the MAC PDU. Note 4: UL grant of 56 bits (I_TBS=0, N_PRB=3, see TS 36.213 Table 7.1.7.2.1-1) is as 36.321 clause 5.1.4 states that the eNB should not provide a grant smaller than 56 bits in the Random Access Response. Note 5: UL grant of 24 bits (ITBS=1, NPRB=1, see TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding will be equal to a single byte. Note 6: The order of short BSR and C-RNTI control element is not restricted, i.e. the short BSR can be placed before the C-RNTI control element and vice versa. The same applies for the related sub-headers.

7.1.4.10.3.3 Specific Message Contents

None.

7.1.4.11 Correct HARQ process handling

7.1.4.11.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { UE receives an UL Grant with toggled NDI and has data available for transmission }

then { UE transmits a new MAC PDU using redundancy version 0 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE performs non-adaptive retransmission of the MAC PDU with redundancy version toggled by one of the last (re)transmission [0,2,3,1 order] }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with old NDI [not toggled], irrespective of ACK/NACK is received for previous (re)transmission }

then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received on PDCCH }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not retransmit the MAC PDU }

}

(5)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with not toggled NDI }

then { UE does not retransmit the MAC PDU but transmit a MAC Padding PDU}

}

(6)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with toggled NDI, and data are not available for transmission }

then { UE transmits any MAC Padding PDU }

}

(7)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not transmit any MAC PDU }

}

7.1.4.11.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1 & 5.4.2.2.

[TS 36.321, clause 5.4.2.1]

There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to take place continuously while waiting for the feedback on the successful or unsuccessful reception of previous transmissions.

The number of parallel HARQ processes is specified in [2], clause 8.

At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a transmission should take place. It also routes the received feedback (ACK/NACK information), MCS and resource, relayed by the physical layer, to the appropriate HARQ process.

If TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for feedback from previous transmissions according to TTI_BUNDLE_SIZE. The feedback for a bundle is only received for the last TTI of the bundle (i.e. the TTI corresponding to TTI_BUNDLE_SIZE ), regardless of whether a transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is also a TTI bundle.

For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply. For each TTI, the HARQ entity shall:

– identify the HARQ process associated with this TTI;

– if an uplink grant has been indicated for this TTI:

– if the received grant was not addressed to a Temporary C-RNTI on PDCCH and if the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this HARQ process; or

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or- if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

Each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established, CURRENT_TX_NB shall be initialized to 0.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

New transmissions are performed on the resource and with the MCS indicated on PDCCH or Random Access Response. Adaptive retransmissions are performed on the resource and, if provided, with the MCS indicated on PDCCH. Non-adaptive retransmission is performed on the same resource and with the same MCS as was used for the last made transmission attempt,

The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

When the HARQ feedback is received for this TB, the HARQ process shall:

– set HARQ_FEEDBACK to the received value.

If the HARQ entity requests a new transmission, the HARQ process shall:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.

NOTE: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer:

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

– if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer.

7.1.4.11.3 Test description

7.1.4.11.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information takes into account the parameters in table 7.1.2.11.3.1-1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table 7.1.4.11.3.3-1 and 7.1.4.11.3.3-2.

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.11.3.2 Test procedure sequence

Table 7.1.4.11.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS Transmits a valid MAC PDU containing RLC PDU	<–	MAC PDU	–	–
2	Void	–	–	–	–
3	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates an UL Grant for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU, in HARQ process X, redundancy version 0? (Note 1)	–>	MAC PDU	1	P
5	The SS transmits a NACK	<–	HARQ NACK	–	–
6	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 2? (Note 1)	–>	MAC PDU	2	P
7	The SS transmits a NACK	<–	HARQ NACK	–	–
8	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 3? (Note 1)	–>	MAC PDU	2	P
9	The SS transmits a NACK	<–	HARQ NACK	–	–
10	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 1? (Note 1)	–>	MAC PDU	2	P
11	The SS transmits a NACK	<–	HARQ NACK	–	–
12	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 0? (Note 1)	–>	MAC PDU	2	P
13	Void	–	–	–	–
14	Void	–	–	–	–
15	The SS transmits an ACK	<–	HARQ ACK	–	–
16	Check: Does the UE retransmit the MAC PDU for HARQ process X?	–>	MAC PDU	4	F
17	The SS transmits an UL grant corresponding to TTI for HARQ process X, with NDI not toggled and redundancy version to be used as ‘1’	<–	Uplink Grant	–	–
18	Check: Does the UE retransmit the MAC PDU in for HARQ process X, using redundancy version 1? (Note 1)	–>	MAC PDU	3	P
19	The SS transmits a NACK	<–	HARQ NACK	–	–
20	The SS transmits an UL grant corresponding to next TTI for HARQ process X, with NDI not toggled and redundancy version to be used as ‘3’	<–	Uplink Grant	–	–
21	Check: Does the UE retransmit the MAC PDU for HARQ process X, using next redundancy version 3? (Note 1)	–>	MAC PDU	3	P
22	The SS transmits a NACK	<–	HARQ NACK	–	–
23	Check: Does the UE retransmit the MAC PDU in the next TTIs corresponding to HARQ process X?	–>	MAC PDU	7	F
24	The SS transmits an UL grant corresponding to TTI for HARQ process X, with NDI not toggled	<–	Uplink Grant	–	–
	EXCEPTION: In parallel with step 25, UE executes parallel behaviour defined in table 7.1.4.11.3.2-2	–	–	–	–
25	Check: Does the UE retransmit the MAC PDU in the next TTIs corresponding to HARQ process X?	–>	MAC PDU	5	F
25A	The SS transmits an RLC STATUS PDU to the UE	<–	RLC STATUS PDU (ACK_SN=1)	–	–
26	The SS transmits a valid MAC PDU containing RLC PDU	<–	MAC PDU	–	–
27	Void	–	–	–	–
28	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates UL Grant for one HARQ process Y, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
29	Check: Does the UE transmit a MAC PDU including one RLC SDU, in HARQ process Y, redundancy version 0? (Note 1)	–>	MAC PDU	1	P
30	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates UL Grant for one HARQ process Y, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
	EXCEPTION: In parallel with step 31, UE executes parallel behaviour defined in table 7.1.4.11.3.2-2.	–	–	–	–
31	Check: Does the UE retransmit the MAC PDU in the next TTIs corresponding to HARQ process Y?	–>	MAC PDU	6	F
32	The SS transmits an RLC STATUS PDU to the UE	<–	RLC STATUS PDU (ACK_SN=2)	–	–
Note 1: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

Table 7.1.4.11.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a MAC Padding PDU	–>	MAC PDU	–	–

7.1.4.11.3.3 Specific message contents

Table 7.1.4.11.3.3-1: MAC-MainConfig {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)}

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n8
}
}

Table 7.1.4.11.3.3-2: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)}

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

7.1.4.11a Correct HARQ process handling / Semi-persistent case / Non-adaptive retransmission / Fixed Redundancy Version

7.1.4.11a.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state with SPS configuration in UL enabled and skipUplinkSPS and fixedRV-NonAdaptive configured and having transmitted a MAC PDU while there are remaining data in the UL buffer }

ensure that {

when { UE receives a NACK for the next TTI corresponding to the HARQ process }

then {UE retransmit the MAC PDU using redundancy version 0 }

}

7.1.4.11a.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.306, clause 4.3.19.8, TS 36.321 clauses 5.4.2.1, 5.4.2.2 and TS 36.331 clause 6.3.2.

[TS 36.306, clause 4.3.19.8 (skipUplinkSPS-r14)]

This field indicates whether the UE supports skipping of UL transmission for a configured uplink grant if no data is available for transmission as specified in TS 36.321 [4].

[TS 36.321, clause 5.4.2.1]

…

At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process(es) for which a transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and resource, relayed by the physical layer, to the appropriate HARQ process(es).

…

For each TTI, the HARQ entity shall:

– identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:

– if an uplink grant has been indicated for this process and this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

…

– else:

…

– else, if the HARQ buffer of this HARQ process is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

For synchronous HARQ, each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established, CURRENT_TX_NB shall be initialized to 0.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4. For serving cells configured with pusch-EnhancementsConfiguration, BL UEs or UEs in enhanced coverage see subclause 8.6.1 in [2] for the sequence of redundancy versions and redundancy version determination. For NB-IoT UEs see subclause 16.5.1.2 in [2] for the sequence of redundancy versions and redundancy version determination.

…

If the HARQ entity requests a retransmission, the HARQ process shall:

– if UL HARQ operation is synchronous:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

…

– else if the HARQ entity requests a non-adaptive retransmission:

– if UL HARQ operation is asynchronous or HARQ_FEEDBACK = NACK:

– if both skipUplinkTxSPS and fixedRV-NonAdaptive are configured and the uplink grant of the initial transmission of this HARQ process was performed on a configured grant; or

– if the uplink grant is a preallocated uplink grant:

– set CURRENT_IRV to 0;

– generate a transmission as described below.

[TS 36.331, clause 6.3.2]

– SPS-Config

The IE SPS-Config is used to specify the semi-persistent scheduling configuration.

…

SPS-Config field descriptions

fixedRV-NonAdaptive

If this field is present and skipUplinkTxSPS is configured, non-adaptive retransmissions on configured uplink grant uses redundancy version 0, otherwise the redundancy version for each retransmission is updated based on the sequence of redundancy versions as described in TS 36.321 [6].

7.1.4.11a.3 Test description

7.1.4.11a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.11a.3.2 Test procedure sequence

Table 7.1.4.11a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits RRCConnectionReconfiguration to configure UL SPS and skipUplinkTxSPS configured	<–	–	–	–
1A	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	–	–	–
2	The SS transmits an UL Grant for one HARQ process X using UE’s SPS C-RNTI, NDI=0, allowing the UE to transmit a RLC SDU of size 10 bytes per MAC PDU.	<–	(UL SPS Grant)	–	–
2A	UE transmits a MAC PDU. Note: UE indicates SPS activation.	–>	MAC PDU	–	–
3	The SS Transmits a valid MAC PDU containing a RLC SDU of size 10 bytes	<–	MAC PDU	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU, in HARQ process X using redundancy version 0?	–>	MAC PDU	1	P
5	The SS transmits a NACK	<–	HARQ NACK	–	–
6	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 0?	–>	MAC PDU	1	P
7	The SS transmits a ACK	<–	HARQ ACK	–	–

7.1.4.11a.3.3 Specific message contents

Table 7.1.4.11a.3.3-1: RadioResourceConfigDedicated (Table 7.1.4.11a.3.2-1, Step 1)

Derivation path: 36.508 table 4.6.3-16
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated::= SEQUENCE {
sps-Config ::= SEQUENCE {
semiPersistSchedC-RNTI	‘FFF0’H
sps-ConfigDL	Not Present
sps-ConfigUL::=CHOICE{
setup SEQUENCE {
semiPersistSchedIntervalUL	sf10	10 Subframes
implicitReleaseAfter	e8
p0-Persistent	Not Present
twoIntervalConfig	Not Present		FDD
twoIntervalConfig	true		TDD
p0-PersistentSubframeSet2-r12	Not Present
numberOfConfUlSPS-Processes-r13	Not Present
fixedRV-NonAdaptive-r14	true
sps-ConfigIndex-r14	Not Present
semiPersistSchedIntervalUL-v1430	Not Present
}
}
}
}

Table 7.1.4.11a.3.3-2: MAC-MainConfig-RBC (Table 7.1.4.11a.3.2-1, Step 1)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
skipUplinkTx-r14 CHOICE {
setup SEQUENCE {
skipUplinkTxSPS-r14	true
skipUplinkTxDynamic-r14	Not present
}
}
}

7.1.4.12 MAC reset / UL

7.1.4.12.1 Test Purpose (TP)

(1)

with(UE in E-UTRA RRC_CONNECTED state, with Scheduling Request procedure triggered)

ensure that {

when{ UE MAC is reset, due to handover to a new cell }

then { UE cancels Scheduling Request procedure }

}

(2)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

when{ UE MAC is reset, due to handover to a new cell }

then { UE flushes UL HARQ buffer }

}

(3)

with (UE in E-UTRA RRC_CONNECTED state )

ensure that {

when{ UE MAC is reset, due to handover to a new cell }

then { UE Considers the next transmission for each UL HARQ process as very first }

}

7.1.4.12.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.

[TS 36.321 clause 5.9]

If a reset of the MAC entity is requested by upper layers, the UE shall:

– initialize Bj for each logical channel to zero;

– stop (if running) all timers;

– consider timeAlignmentTimer as expired and perform the corresponding actions in subclause 5.2;

– stop, if any, ongoing RACH procedure;

– discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;

– flush Msg3 buffer;

– cancel, if any, triggered Scheduling Request procedure;

– cancel, if any, triggered Buffer Status Reporting procedure;

– cancel, if any, triggered Power Headroom Reporting procedure;

– flush the soft buffers for all DL HARQ processes;

– for each DL HARQ process, consider the next received transmission for a TB as the very first transmission;

– release, if any, Temporary C-RNTI.

7.1.4.12.3 Test description

7.1.4.12.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

7.1.4.12.3.2 Test procedure sequence

Table 7.1.4.12.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 7.1.4.12.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 2	Remark
T0	Cell-specific RS EPRE	dBm/15Khz	-85	Off
T1	Cell-specific RS EPRE	dBm/15Khz	-91	-85
T2	Cell-specific RS EPRE	dBm/15Khz	-85	-91

Table 7.1.4.12.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU containing one RLC SDU on LC 4	<–	MAC PDU (1 RLC SDU of 40 bytes on DRB)	–	–
3	The UE transmit a scheduling request	–>	(SR)	–	–
4	Wait for 50ms [Discard timer] to expire at UE.	–	–	–	–
5	The SS changes power level according to the row "T1" in table 7.1.4.12.3.2-1	–	–	–	–
6	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2.	<–	–	–	–
7	The UE transmits on cell 2, RRCConnectionReconfigurationComplete	–>	–	–	–
8	Check: For 2 seconds, if UE transmits a scheduling request?	–>	(SR)	1	F
9	The SS transmits a MAC PDU containing RLC SDU on LC 4	<–	MAC PDU (1 RLC SDU of 40 bytes on DRB)	–	–
10	The UE transmit a scheduling request	–>	(SR)	–	–
11	The SS allocate UL Grant sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
12	The UE transmit a MAC PDU including one RLC SDU	–>	MAC PDU	–	–
13	The SS transmits a NACK	<–	HARQ NACK	–	–
13A	The SS changes power level according to the row "T2" in table 7.1.4.12.3.2-1	–	–	–	–
14	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 1	<–	–	–	–
15	The UE transmits on cell 1, RRCConnectionReconfigurationComplete	–>	–	–	–
16	Check: For 2 seconds, does UE transmit MAC PDU containing Loop Back PDU?	–>	MAC PDU (1 RLC SDU of 40 bytes on DRB)	2	F
17	The SS transmits a MAC PDU containing RLC SDU on LC 4	<–	MAC PDU (1 RLC SDU of 40 bytes on DRB)	–	–
18	The UE transmit a scheduling request	–>	(SR)	–	–
19	The SS allocate UL Grant sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
20	Check: Does UE transmit a MAC PDU including one RLC SDU?	–>	MAC PDU	3	P

7.1.4.12.3.3 Specific Message Contents

Table 7.1.4.12.3.3-1: MAC-MainConfiguration {RRCConnectionReconfiguration (preamble)}

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfiguration-RBC ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28
}
}

Table 7.1.4.12.3.3-2: PDCP-Configuration-DRB-UM {RRCConnectionReconfiguration (preamble)}

Derivation Path: 36.508 clause 4.8.2.1.2.1-1
Information Element	Value/remark	Comment	Condition
PDCP-Configuration-DRB-UM ::= SEQUENCE {
discardTimer	ms50	Lowest value
}

Table 7.1.4.12.3.3-3: SchedulingRequest-Configuration {RRCConnectionReconfiguration (preamble)}

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration::= CHOICE {
enable SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 7.1.4.12.3.3-4: RRCConnectionReconfiguration (step 6, table 7.1.4.12.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6, condition RBC-HO
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInformation SEQUENCE {	MobilityControlInformation-HO
targetCellIdentity	PhysicalCellIdentity of Cell 2 (see 36.508 clause 4.4.4.2)
eutra-CarrierFreq	Not present
}
}
}
}
}

Table 7.1.4.12.3.3-5: RRCConnectionReconfiguration (step 14, table 7.1.4.12.3.2-2)

Derivation Path: 36.508, Table 4.6.1-6, condition RBC-HO
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
mobilityControlInformation SEQUENCE {	MobilityControlInformation-HO
targetCellIdentity	PhysicalCellIdentity of Cell 1 (see 36.508 clause 4.4.4.2)
eutra-CarrierFreq	Not present
}
}
}
}
}

7.1.4.12a MAC Partial reset / UL for Voice and Video Enhancement

7.1.4.12a.1 Test Purpose (TP)

(1)

with(UE in E-UTRA RRC_CONNECTED state, with Scheduling Request procedure triggered)

ensure that {

when{ UE MAC is partial reset, due to PUSCH enhancement mode setup}

then { UE continues Scheduling Request procedure }

}

(2)

with ( UE in E-UTRA RRC_CONNECTED state )

ensure that {

when{ UE MAC is partial reset, due to PUSCH enhancement mode release }

then { UE flushes UL HARQ buffer }

}

(3)

with (UE in E-UTRA RRC_CONNECTED state )

ensure that {

when{ UE MAC is partial reset, due to PUSCH enhancement mode setup }

then { UE Considers the next transmission for each UL HARQ process as very first }

}

7.1.4.12a.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.9.

[TS 36.321 clause 5.9]

If a reset of the MAC entity is requested by upper layers, the MAC entity shall:

– initialize Bj for each logical channel to zero;

– stop (if running) all timers;

– consider all timeAlignmentTimers as expired and perform the corresponding actions in subclause 5.2;

– set the NDIs for all uplink HARQ processes to the value 0;

– stop, if any, ongoing RACH procedure;

– discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;

– flush Msg3 buffer;

– cancel, if any, triggered Scheduling Request procedure;

– cancel, if any, triggered Buffer Status Reporting procedure;

– cancel, if any, triggered Power Headroom Reporting procedure;

– flush the soft buffers for all DL HARQ processes;

– for each DL HARQ process, consider the next received transmission for a TB as the very first transmission;

– release, if any, Temporary C-RNTI.

If a partial reset of the MAC entity is requested by upper layers, for a serving cell, the MAC entity shall for the serving cell:

– set the NDIs for all uplink HARQ processes to the value 0;

– flush all UL HARQ buffers;

– stop all running drx-ULRetransmissionTimers;

– stop all running UL HARQ RTT timers;

– stop, if any, ongoing RACH procedure;

– discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any;

– flush Msg3 buffer;

– release, if any, Temporary C-RNTI.

7.1.4.12a.3 Test description

7.1.4.12a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].

– The condition SRB2-DRB (1, 1) is used for step 8 in 4.5.3A.3 according to [18].

7.1.4.12a.3.2 Test procedure sequence

Table 7.1.4.12a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU containing one RLC SDU on LC 4	<–	MAC PDU (1 RLC SDU of 40 bytes on DRB)	–	–
3	The UE transmit a scheduling request	–>	(SR)	–	–
4	SS does not respond to any SR to transmit a UL grant.	–	–	–	–
5	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform PUSCH Enhancement Mode Setup.	<–	–	–	–
6	The UE transmits on RRCConnectionReconfigurationComplete	–>	–	–	–
7	Check: For 1 second, if UE transmits a scheduling request?	–>	(SR)	1	P
8	The SS allocate UL Grant sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
9	The UE transmit a MAC PDU including one RLC SDU	–>	MAC PDU	–	–
10	The SS transmits a NACK	<–	HARQ NACK	–	–
11	The SS transmits an RRCConnectionReconfiguration message to order the UE to perform PUSCH Enhancement Mode Release.	<–	–	–	–
12	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
13	Check: For 1.5 seconds, Wait for discard timer (1.5seconds from step3) to expire at UE, does UE transmit MAC PDU containing Loop Back PDU?	–>	MAC PDU (1 RLC SDU of 40 bytes on DRB)	2	F
14	The SS transmits a MAC PDU containing RLC SDU on LC 4	<–	MAC PDU (1 RLC SDU of 40 bytes on DRB)	–	–
15	The UE transmit a scheduling request	–>	(SR)	–	–
16	The SS allocate UL Grant sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission	<–	Uplink Grant	–	–
17	Check: Does UE transmit a MAC PDU including one RLC SDU?	–>	MAC PDU	3	P

7.1.4.12a.3.3 Specific Message Contents

RRCConnectionReconfiguration is referred to 36.508[] Table 4.6.1-8, and RRCConnectionReconfigurationComplete is referred to 36.508[] table 4.6.1-9 with the following exceptions.

Table 7.1.4.12a.3.3-1: MAC-MainConfiguration {RRCConnectionReconfiguration (preamble) }

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfiguration-RBC ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
retxBSR-Timer	sf320	Less than the discard timer so that SR will be retransmitted before SDU discarded after MAC partial reset.
maxHARQ-Tx	n28
sr-ProhibitTimer-r9	1	SR is retransmitted every SR period.
}
}

Table 7.1.4.12a.3.3-2: PDCP-Configuration-DRB-UM {RRCConnectionReconfiguration(preamble) }

Derivation Path: 36.508 clause 4.8.2.1.2.1-1
Information Element	Value/remark	Comment	Condition
PDCP-Configuration-DRB-UM ::= SEQUENCE {
discardTimer	ms1500	Making sure the SDU is discarded only after PUSCH mode reconfiguration complete in step12
}

Table 7.1.4.12a.3.3-3: SchedulingRequest-Configuration {RRCConnectionReconfiguration (preamble)}

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration::= CHOICE {
enable SEQUENCE {
dsr-TransMax	n64	Max value allowed
}
}

Table 7.1.4.12a.3.3-4: PhysicalConfigDedicated-DEFAULT in (step 5, table 7.1.4.12a.3.2-2)

Derivation Path: 36.508 Table 4.8.2.1.6-1, condition [eVolte]
Information Element	Value/remark	Comment	Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pusch-EnhancementsConfig-r14	PUSCH-EnhancementsConfig-r14-DEFAULT		PuschEnhancement _Setup
}
}

Table 7.1.4.12a.3.3-5: PhysicalConfigDedicated-DEFAULT in (step 11, table 7.1.4.12a.3.2-2)

Derivation Path: 36.508 Table 4.8.2.1.6-1, condition [eVolte]
Information Element	Value/remark	Comment	Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pusch-EnhancementsConfig-r14	PUSCH-EnhancementsConfig-r14-DEFAULT		PuschEnhancement _Release
}
}

7.1.4.13 MAC PDU header handling

7.1.4.13.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and UE is not Category 0 or Category M1}

ensure that {

when { UE has a MAC SDU to be transmitted that is less smaller 128 bytes }

then { UE sets F field to 0 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and UE is not Category 0 or Category M1}

ensure that {

when { UE has a MAC SDU to be transmitted that is larger than 128 bytes }

then { UE sets F field to 1 }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE inserts a R/R/E/LCID field in the MAC header and there is a subsequent R/R/E/LCID field to be inserted }

then { UE sets E field to 1 }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE inserts a R/R/E/LCID field in the MAC header and a MAC SDU or a MAC control element starts at the next byte }

then { UE sets E field to 0 }

}

(5)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE inserts the last MAC sub-header in the MAC PDU }

then { UE inserts a MAC sub-header consist solely of the four header fields R/R/E/LCID }

}

(6)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE inserts padding at the end of a MAC PDU }

then { UE inserts the last MAC sub-header as a padding MAC subheader consisting solely of the four header fields R/R/E/LCID with LCID set to Padding }

}

7.1.4.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.321 clause 6.1.2 and 6.2.1.

[TS 36.321, clause 6.1.2]

A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC control elements, and optionally padding; as described in Figure 6.1.2-3.

Both the MAC header and the MAC SDUs are of variable sizes.

A MAC PDU header consists of one or more MAC PDU sub-headers; each sub header corresponding to either a MAC SDU, a MAC control element or padding.

A MAC PDU sub header consists of the six header fields R/R/E/LCID/F/L but for the last sub header in the MAC PDU and for fixed sized MAC control elements. The last sub header in the MAC PDU and sub-headers for fixed sized MAC control elements consist solely of the four header fields R/R/E/LCID. A MAC PDU subheader corresponding to padding consists of the four header fields R/R/E/LCID.

Figure 6.1.2-1: R/R/E/LCID/F/L MAC sub header

Figure 6.1.2-2: R/R/E/LCID MAC sub header

MAC PDU sub-headers have the same order as the corresponding MAC SDUs, MAC control elements and padding.

MAC control elements are always placed before any MAC SDU.

When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader.

A maximum of one MAC PDU can be transmitted per TB per UE.

Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding

[TS 36.321, clause 6.2.1]

The MAC header is of variable size and consists of the following fields:

– L: The Length field indicates the length of the corresponding MAC SDU or MAC control element in bytes. There is one L field per MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control elements. The size of the L field is indicated by the F field;

– F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per MAC PDU sub header except for the last sub header and sub-headers corresponding to fixed-sized MAC control elements. The size of the F field is 1 bit. If the size of the MAC SDU or MAC control element is less than 128 bytes, the UE shall set the value of the F field to 0, otherwise the UE shall set it to 1;

– E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate another set of at least R/R/E/LCID fields. The E field is set to "0" to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte;

– R: Reserved bits, set to "0".

The MAC header and sub-headers are octet aligned.

…

Table 6.2.1-2: Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

…

Table 6.2.1-3: Values of F field:

Index	Size of Length field (in bits)
0	7
1	15

7.1.4.13.3 Test description

7.1.4.13.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(2,0) is used for step 8 in 4.5.3A.3 according to [18].

– 2 AM DRBs are configured with the parameters specified in table 7.1.4.13.3.1-1.

Table 7.1.4.13.3.1-1: Logical Channel Configuration Settings

Parameter	DRB1	DRB2
LogicalChannel-Identity	3	4
Priority	7	6
prioritizedBitRate	0kbs	0kbs
logicalChannelGroup	2	1

7.1.4.13.3.2 Test procedure sequence

Table 7.1.4.13.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
–	EXCEPTION: For Category 0 or Category M1 UE skip steps 2 to 10. (Note 8)
2	The SS transmits a MAC PDU containing a MAC SDU of size 127 bytes (RLC SDU of size 125 bytes + AMD PDU header 2 bytes ) with the Logical Channel ID field ‘LCID’ set to ‘00011’, and 1 Byte Padding in the associated MAC SDU sub-header.	<–	MAC PDU (MAC sub-header ( LCID=’00011’), AMD PDU)	–	–
3	The UE sends Scheduling Request	–>	(SR)	–	–
4	The SS transmits an uplink grant of size 1096 bits. (Note 1)	<–	(UL grant)	–	–
5	Check: does the UE transmit a MAC PDU with a MAC SDU sub-header with Logical Channel ID field ‘LCID’ set to ‘00011’, Format field ‘F’ set to ‘0’ and Length field ‘L’ set to ‘127’? (Note 6)	–>	MAC PDU (MAC sub-header ( LCID=’00011’, F=’0’, L=’127’ bytes), AMD PDU)	1	P
5a	The SS transmits an RLC STATUS PDU to acknowledge correctly received data	<–	RLC STATUS PDU (ACK_SN=1)	–	–
6	The SS transmits a MAC PDU containing a MAC SDU of size 128 bytes (RLC SDU of 126 bytes + AMD PDU header 2 bytes) with the Logical Channel ID field ‘LCID’ set to ‘00011’.	<–	MAC PDU (MAC sub-header (LCID=’00011’), AMD PDU)	–	–
7	The UE send Scheduling Request	–>	(SR)	–	–
8	The SS transmits an uplink grant of size 1096 bits. (Note 2)	<–	(UL grant)	–	–
9	Check: Does the UE transmit a MAC PDU with a MAC SDU sub-header with Format field ‘F’ set to ‘1’ and Logical Channel ID field ‘LCID’ set to ‘00011’? (Note 6)	–>	MAC PDU (MAC sub-header (LCID=’00011’, F=’1’, L=128), AMD PDU)	2	P
10	The SS transmits an RLC STATUS PDU to acknowledge correctly received data	<–	RLC STATUS PDU (ACK_SN=2)	–	–
11	The SS transmits a MAC PDU containing two MAC SDUs, the first containing a 9 byte RLC SDU with LCID set to ‘00011’ and the second containing s 6 byte RLC SDU with LCID set to ‘00100’.	<–	MAC PDU (MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’11’), MAC sub-header (E=’0’, LCID=’00100’), AMD PDU, AMD PDU)	–	–
12	The UE sends Scheduling Request	–>	(SR)	–	–
13	The SS transmits an uplink grant of size 176 bits. (Note 3)	<–	(UL grant)	–	–
14	Check: Does the UE return a MAC PDU of length 176 bits containing two MAC sub-headers where the first MAC sub-header have the Expansion bit ‘E’ set to ‘1’ and the second MAC sub-header has the Expansion bit ‘E’ set to ‘0’ and no length field? (Note 5)	–>	MAC PDU (MAC sub-header (E=’1’, (LCID=’00011’, L=’11) or (LCID=’00100’,L=’8), MAC sub-header (E=’0’, no Length field present), AMD PDU, AMD PDU)	3,4,5	P
15	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00011’) k= 1 for Category 0 or Category M1 UE else k=3.	<–	RLC STATUS PDU (ACK_SN= k)	–	–
16	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00100’)	<–	RLC STATUS PDU (ACK_SN=1)
17	The SS transmits a MAC PDU containing two MAC SDUs, the first containing a 8 byte RLC SDU with LCID set to ‘00011’ and the second containing a 7 byte RLC SDU with LCID set to ‘00100’.	<–	MAC PDU (MAC sub-header (E=’1’, LCID=’00011’, F=’0’, L=’10’), MAC sub-header (E=’0’, LCID=’00100’,), AMD PDU, AMD PDU)	–	–
18	The UE sends Scheduling Request	–>	(SR)	–	–
19	The SS transmits an uplink grant of size 256 bits. (Note 4)	<–	(UL grant)	–	–
20	Check: Does the UE return a MAC PDU of length 256 bits containing four MAC sub-headers where the first three MAC sub-header have the Expansion bit ‘E’ set to ‘1’ and the last MAC sub-header has the Expansion bit ‘E’ set to ‘0’ and the LCID field set to ‘11111’? (Note 5) (Note 7)	–>	MAC PDU (Long BSR MAC sub-header (E=’1’, LCID=’11110’, MAC sub-header (E=’1’, F=’0’), MAC sub-header (E=’1’, F=’0’), F=’0’), padding MAC sub-header (E=’0’, LCID=’11111’), Long BSR, AMD PDU, AMD PDU, padding) Or MAC PDU (Short BSR MAC sub-header (E=’1’, LCID=’11101’, MAC sub-header (E=’1’, F=’0’), MAC sub-header (E=’1’, F=’0’), F=’0’), padding MAC sub-header (E=’0’, LCID=’11111’), Short BSR, AMD PDU, AMD PDU, padding)	3,4,6	P
21	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00011’)	<–	RLC STATUS PDU (ACK_SN= k+1)
22	SS transmits an RLC STATUS PDU to acknowledge correctly received data(LCID=’00100’)	<–	RLC STATUS PDU (ACK_SN=2)
Note 1: UL grant of 1096 bits (I_TBS=8, N_PRB=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a MAC SDU of size 127 bytes in a MAC PDU (125 bytes RLC SDU size + 2 bytes AMD PDU header + 2 bytes MAC header (7 bit LI) = 129 bytes = 1032 bits < 1096 bits. Note 2: UL grant of 1096 bits (I_TBS=8, N_PRB=8, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit a MAC SDU of size 128 bytes in a MAC PDU (126 bytes RLC SDU size + 2 bytes AMD PDU header + 3 bytes MAC header (15 bit LI) = 131 bytes = 1048 bits < 1096 bits. Note 3: UL grant of 176 bits (I_TBS=1, N_PRB=5, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two MAC SDUs, one of size 11 and one of size 8 bytes, in a MAC PDU (9 bytes RLC SDU + 2 bytes AMD PDU header + 6 bytes RLC SDU +2 bytes AMD PDU header + 2 bytes MAC sub-header (7 bit LI) + one byte MAC sub-header (R/R/E/LCID) = 22 bytes = 176 bits) Note 4: UL grant of 256 bits (I_TBS=6, N_PRB=3, TS 36.213 Table 7.1.7.2.1-1) is chosen to enable UE to transmit two MAC SDUs of size 10 and 9 bytes in a MAC PDU ( (8 bytes RLC SDU + 2 bytes AMD PDU header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) + 3 byte Long BSR+4 byte padding + one byte BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256 bits) or (8 bytes RLC SDU + 2 bytes AMD PDU header + 7 bytes RLC SDU+ 2 bytes AMD PDU header) + 1 byte Short BSR+6 byte padding + one byte BSR header+ 2 x 2 bytes MAC sub-header (7 bit LI) + one byte padding MAC sub-header (R/R/E/LCID) = 32bytes = 256 bits)) Note 5: MAC SDU for LCID 3 and 4 can come in any order Note 6: At this step UE shall include a BSR and report it on any of the configured Logical Channel Groups: 0 (SRB2), 1 (DRB2) and 2 (DRB1), Note 7: It is left up to UE implementation whether ShortBSR or LongBSR is reported. Note 8: Test steps 2 to 10 verifies test purposes 1 and 2, which are not applicable for Category 0 or Category M1 UE (maximum TB size for Category 0 or Category M1 UE is 1000 bits corresponding to MAC SDU size of less than 128 bytes).

7.1.4.13.3.3 Specific Message Contents

None.

7.1.4.14 Correct HARQ process handling / TTI bundling

7.1.4.14.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling configured }

ensure that {

when { UE receives an UL Grant with toggled NDI and has data available for transmission }

then { UE transmits a new MAC PDU and non-adaptive retransmissions for 3 additional consecutive UL subframes }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the bundled HARQ process }

then { UE performs non-adaptive retransmissions of the MAC PDU for 4 consecutive UL subframes }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with old NDI, irrespective of ACK/NACK is received for previous (re)transmission }

then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received on PDCCH in first UL subframe and non-adaptive retransmissions in 3 additional consecutive UL subframes }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not retransmit the TTI Bundle }

}

7.1.4.14.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1, 5.4.2.2 & 7.5, TS 36.213 clause 8, 8.3, 8.6.1 & 9.1.2.

[TS 36.321, clause 5.4.2.1]

There is one HARQ entity at the UE, which maintains a number of parallel HARQ processes allowing transmissions to take place continuously while waiting for HARQ the feedback on the successful or unsuccessful reception of previous transmissions.

The number of parallel HARQ processes is specified in [2], clause 8.

At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process for which a transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and resource, relayed by the physical layer, to the appropriate HARQ process.

When TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for feedback from previous transmissions according to TTI_BUNDLE_SIZE. The HARQ feedback of a bundle is only received for the last TTI of the bundle (i.e. the TTI corresponding to TTI_BUNDLE_SIZE), regardless of whether a transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is also a TTI bundle.

For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.

For each TTI, the HARQ entity shall:

– identify the HARQ process associated with this TTI;

– if an uplink grant has been indicated for this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

When the HARQ feedback is received for this TB, the HARQ process shall:

– set HARQ_FEEDBACK to the received value.

If the HARQ entity requests a new transmission, the HARQ process shall:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.

NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

– if there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer in this TTI:

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

– if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer;

[TS 36.321, clause 7.5]

The parameter TTI_BUNDLE_SIZE is 4.

[TS 36.213, clause 8]

For FDD, there shall be 8 HARQ processes in the uplink for non-subframe bundling operation, i.e. normal HARQ operation, and 4 HARQ processes in the uplink for subframe bundling operation. The subframe bundling operation is configured by the parameter ttiBundling provided by higher layers.

In case higher layers configure the use of subframe bundling for FDD and TDD, the subframe bundling operation is only applied to UL-SCH, such that four consecutive uplink subframes are used.

…

For FDD and subframe bundling operation, the UE shall upon detection of a PDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH and PHICH information.

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	DL subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

Table 8-2a: l for TDD configurations 0, 1 and 6

TDD UL/DL Configuration	DL subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	9	6				9	6
1		2			3		2			3
6	5	5				6	6			8

[TS 36.213, clause 8.3]

For Frame Structure type 1, an ACK/NACK received on the PHICH assigned to a UE in subframe i is associated with the PUSCH transmission in subframe i-4.

For Frame Structure type 2 UL/DL configuration 1-6, an ACK/NACK received on the PHICH assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-k as indicated by the following table 8.3-1.

…

Table 8.3-1 k for TDD configurations 0-6

TDD UL/DL Configuration	DL subframe number i
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	7	4				7	4
1		4			6		4			6
2				6					6
3	6								6	6
4									6	6
5									6
6	6	4				7	4			6

[TS 36.213, clause 8.6.1]

For, the modulation order () is determined as follows:

…

If the parameter ttiBundling provided by higher layers is set to TRUE, then the resource allocation size is restricted to and the modulation order is set to .

[TS 36.213, clause 9.1.2]

For scheduled PUSCH transmissions in subframe n, a UE shall determine the corresponding PHICH resource in subframe n+ k_PHICH, where k_PHICH is always 4 for FDD and is given in table 9.1.2-1 for TDD. For subframe bundling operation, the corresponding PHICH resource is associated with the last subframe in the bundle.

Table 9.1.2-1: k_PHICH for TDD

TDD UL/DL Configuration	UL subframe index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0			4	7	6			4	7	6
1			4	6				4	6
2			6					6
3			6	6	6
4			6	6
5			6
6			4	6	6			4	7

7.1.4.14.3 Test description

7.1.4.14.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.14.3.2 Test procedure sequence

Table 7.1.4.14.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	SS Transmits RRCConnectionReconfiguration to configure TTI bundling	<–	–	–	–
0B	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
1	The SS Transmits a valid MAC PDU containing RLC PDU of size 312 bits on UM Bearer.	<–	MAC PDU	–	–
2	The UE transmits a Scheduling Request	–>	Scheduling Request	–	–
3	The SS allocates an UL Grant of 328 bits with NDI indicating new transmission (i.e. Nprb=3 and Imcs=7)(Note 1)	<–	Uplink Grant	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU, with redundancy version 0, ‘k’ subframes after step 3? (Note 3)	–>	MAC PDU	1	P
5	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 4, for 3 consecutive UL subframes with redundancy version 2, 3 and 1 respectively? (Note 3)	–>	MAC PDU	1	P
6	The SS transmits a NACK, ‘kk’ subframes after last transmission in step 5.	<–	HARQ NACK	–	–
7	Check: Does the UE make non-adaptive retransmissions of the MAC PDU ‘m’ subframes after NACK in step 6, for 4 consecutive UL subframes with redundancy version 0, 2, 3 and 1 respectively? (Note 3)	–>	MAC PDU	2	P
8	The SS transmits an ACK, ‘kk’ subframes after last transmission in step 7.	<–	HARQ ACK	–	–
9	The SS allocates an UL Grant with NDI indicating retransmission, start redundancy version =2[i.e. Nprb=3 and Imcs=30], ‘l’ subframes after ACK in step 8.	<–	Uplink Grant	–	–
10	Check: Does the UE perform an adaptive retransmission of the MAC PDU ‘k’ subframes after grant in step 9, using redundancy version 2? (Note 3)	–>	MAC PDU	3	P
11	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 10, for 3 consecutive UL sub-frames with redundancy version 3, 1 and 0 respectively? (Note 3)	–>	MAC PDU	3	P
12	The SS transmits an ACK, ‘kk’ subframes after last transmission in step 11.	<–	HARQ ACK	–	–
13	Check: Does the UE make any retransmissions of the MAC PDU ‘m’ subframes after ACK in step 12, for 4 consecutive UL subframes?	–>	MAC PDU	4	F
Note 1: In step3, for TDD, the subframe number of allocating UL grant should be selected from {‘1’, ‘4’, ‘6’, ‘9’} based on TDD default UL/DL configuration 1. Note 2: For FDD value of ‘k’, ‘kk’ is 4, ‘l’ is 5 and ‘m’ is 9. For TDD UL/DL configuration 1, values of ‘k’, ‘l’, ‘m’ and ‘kk’ are given in table 7.1.4.14.3.2-2. Note 3: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

Table 7.1.4.14.3.2-2: Values for parameter ‘k’, ‘l’, ‘m’ and ‘kk’ in Main behaviour.

Parameter	DL sub-frame number n
Parameter	0	1	2	3	4	5	6	7	8	9
k		6			4		6			4
l		3			2		3			2
m		7			8		7			8
kk			4	6				4	6

7.1.4.14.3.3 Specific message contents

Table 7.1.4.14.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration(Step 0A)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28	Max value allowed
periodicBSR-Timer	Infinity
retxBSR-Timer	sf10240
ttiBundling	TRUE
}
}

7.1.4.14a Correct HARQ process handling / feedback for UL data

7.1.4.14a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling and mpdcch-UL-HARQ-ACK-FeedbackConfig configured and having transmitted a MAC PDU one time}

ensure that {

when { UE receives an ACK }

then { UE does not transmit any more repetitions of the bundle }

}

7.1.4.14a.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.321 clause 5.4.2.1 and TS 36.331 clause 6.3.2.

[TS 36.321, clause 5.4.2.1]

…

In asynchronous HARQ operation, a HARQ process is associated with a TTI based on the received UL grant except for UL grant in RAR. Except for NB-IoT UE configured with a single HARQ process, each asynchronous HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RAR, HARQ process identifier 0 is used. HARQ feedback is not applicable for asynchronous UL HARQ except if mpdcch-UL-HARQ-ACK-FeedbackConfig is configured.

…

For serving cells configured with pusch-EnhancementsConfig, NB-IoT UEs, BL UEs or UEs in enhanced coverage, the parameter UL_REPETITION_NUMBER provides the number of transmission repetitions within a bundle. For each bundle, UL_REPETITION_NUMBER is set to a value provided by lower layers. Bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and are triggered without waiting for feedback from previous transmissions according to UL_REPETITION_NUMBER. An uplink grant corresponding to a new transmission of the bundle is only received after the last repetition of the bundle if mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured. An uplink grant corresponding to a retransmission of the bundle is only received after the last repetition of the bundle. For UEs configured with mpdcch-UL-HARQ-ACK-FeedbackConfig, repetitions within a bundle are stopped if an UL HARQ-ACK feedback or an uplink grant corresponding to a new transmission of the bundle is received on PDCCH during the bundle transmission. A retransmission of a bundle is also a bundle.

[TS 36.331, clause 6.3.2]

– MAC-MainConfig

…

MAC-MainConfig field descriptions

mpdcch-UL-HARQ-ACK-FeedbackConfig

TRUE indicates E-UTRAN may send UL HARQ-ACK feedback or UL grant corresponding to a new transmission for early termination of PUSCH transmission, or positive acknowledgement of completed PUSCH transmissions as specified in TS 36.321 [6] and TS 36.212 [22]. In case of acknowledgement of RRC Connection Release, MPDCCH monitoring is terminated.

7.1.4.14a.3 Test description

7.1.4.14a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.14a.3.2 Test procedure sequence

Table 7.1.4.14a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS Transmits RRCConnectionReconfiguration to configure TTI bundling	<–	–	–	–
2	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
3	The SS Transmits a valid MAC PDU containing RLC PDU of size 312 bits on UM Bearer.	<–	MAC PDU	–	–
4	The UE transmits a Scheduling Request	–>	Scheduling Request	–	–
5	The SS allocates an UL Grant of 328 bits with NDI indicating new transmission (i.e. Nprb=3 and Imcs=7)	<–	Uplink Grant	–	–
6	Check: Does the UE transmit a MAC PDU including one RLC SDU?	–>	MAC PDU	1	P
7	The SS transmits an ACK on PDCCH	<–	HARQ ACK	–	–
8	Check: Does the UE repeat retransmission of MAC PDU in step 6?	–>	MAC PDU	1	F

7.1.4.14a.3.3 Specific message contents

Table 7.1.4.14a.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration (Table 7.1.4.14a.3.2-1, Step 1)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28	Max value allowed
periodicBSR-Timer	Infinity
retxBSR-Timer	sf10240
ttiBundling	TRUE
}
mpdcch-UL-HARQ-ACK-FeedbackConfig-r15	TRUE
}

7.1.4.15 UE power headroom reporting / Periodic reporting

7.1.4.15.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting configured }

ensure that {

when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedure }

then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic power headroom reporting configured }

ensure that {

when { periodicPHR-Timer expires and UL resources allocated for new transmission }

then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { power headroom reporting is disabled }

then { UE stops transmitting Power Headroom MAC Control Element }

}

7.1.4.15.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and 6.1.3.6, 36.331.

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of 3GPP TS 36.133 [9]. RRC controls Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– the prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB since the transmission of a PHR when UE has UL resources for new transmission;

– periodicPHR-Timer expires;

– upon configuration and reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function.

If the UE has UL resources allocated for new transmission for this TTI:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer.

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last transmission of a PHR r this is the first time that a PHR is triggered, and;

– if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of logical channel prioritization:

– obtain the value of the power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6]

The Power Headroom MAC control element is identified by a MAC PDU sub header with LCID as specified in table 6.2.1-2. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1):

– R: reserved bit, set to "0";

– Power Headroom(PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 below (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [19])

Figure 6.1.3.6-1: Power Headroom MAC control element

Table 6.1.3.6-1: Power Headroom levels for PHR

PH	Power Headroom Level
0	POWER_HEADROOM_0
1	POWER_HEADROOM_1
2	POWER_HEADROOM_2
3	POWER_HEADROOM_3
…	…
60	POWER_HEADROOM_60
61	POWER_HEADROOM_61
62	POWER_HEADROOM_62
63	POWER_HEADROOM_63

7.1.4.15.3 Test description

7.1.4.15.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

7.1.4.15.3.2 Test procedure sequence

Table 7.1.4.15.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS is configured for Uplink Grant Allocation Type 2. The SS transmits UL grant to the UE at every 10ms in a DL subframe. (Note 1)	–>	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message to provide Power Headroom parameters	<–	–	–	–
3	Check: does the UE transmit a MAC PDU containing Power Headroom MAC Control Element? (Note 2)	–>	MAC PDU	1	P
4	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Power Headroom parameters. (Note 2)	–>	–	–	–
5	Check: does the UE transmit a MAC PDU containing Power Headroom MAC Control Element 200ms after step 3?	–>	MAC PDU	2	P
6	The SS transmits an RRCConnectionReconfiguration message to disable Power Headroom reporting	<–	–	–	–
7	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the disabling of Power Headroom parameters	–>	–	–	–
8	Check: for 2 seconds, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	3	F
Note 1: The SS transmits UL grant to the UE at every 10 ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. See TS 36.523-3 sub-clause 7.26 for scheduling pattern for type B half-duplex FDD UE. Note 2: Steps 3 and 4 can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.

7.1.4.15.3.3 Specific message contents

Table 7.1.4.15.3.3-1: RRCConnectionReconfiguration (step 2, Table 7.1.4.15.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Confign CHOICE {
setup SEQUENCE {
periodicPHR-Timer	sf200
prohibitPHR-Timer	sf1000
dl-PathlossChange	infinity
}
}
}
}
}
}
}
}
}

Table 7.1.4.15.3.3-2: RRCConnectionReconfiguration (step 6, Table 7.1.4.15.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
release	NULL
}
}
}
}
}
}
}
}

7.1.4.16 UE power headroom reporting / DL pathloss change reporting

7.1.4.16.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for dl-PathlossChange configured }

ensure that {

when { the DL Pathloss has changed more than dl-PathlossChange dB and prohibitPHR-Timer is running }

then { UE does not transmit a MAC PDU containing Power Headroom MAC Control Element }

}

(2)

with { UE in E-UTRA RRC_Connected state with DRB established, Power headroom reporting for dl-PathlossChange configured }

ensure that {

when { prohibitPHR-Timer expires and power headroom report is triggered due to DL Pathloss change }

then { UE transmits a MAC PDU containing Power Headroom MAC Control Element }

}

7.1.4.16.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and 6.1.3.6

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission. The reporting period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-PathlossChange which sets the change in measured downlink pathloss to trigger a PHR [8].

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB since the transmission of a PHR when UE has UL resources for new transmission;

– periodicPHR-Timer expires;

– upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function.

If the UE has UL resources allocated for new transmission for this TTI:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last transmission of a PHR or this is the first time that a PHR is triggered, and;

– if the allocated UL resources can accommodate a PHR MAC control element plus its subheader as a result of logical channel prioritization:

– obtain the value of the power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6]

The Power Headroom MAC control element is identified by a MAC PDU sub header with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1):

– R: reserved bit, set to "0";

– Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6.1-1 below (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [17]).

Figure 6.1.3.6-1: Power Headroom MAC control element

Table 6.1.3.6-1: Power Headroom levels for PHR

PH	Power Headroom Level
0	POWER_HEADROOM_0
1	POWER_HEADROOM_1
2	POWER_HEADROOM_2
3	POWER_HEADROOM_3
…	…
60	POWER_HEADROOM_60
61	POWER_HEADROOM_61
62	POWER_HEADROOM_62
63	POWER_HEADROOM_63

7.1.4.16.3 Test description

7.1.4.16.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

7.1.4.16.3.2 Test procedure sequence

Table 7.1.4.16.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS is configured for Uplink Grant Allocation Type 2. SS is configured to transmit UL grant to UE at every 10ms in a DL subframe. (Note 1)	–	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message to provide Power Headroom parameters	<–	RRCConnectionReconfiguration	–	–
3	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Power Headroom parameters (Note 2)	–>	–	–	–
4	Wait for T1= 10% of prohibitPHR-Timer.	–	–	–	–
5	Reduce SS power level so as to cause a DL_Pathloss change at UE by 5dB.	–	–	–	–
6	Check: for 80% of prohibitPHR-Timer since step 3, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	1	F
7	Check: after prohibitPHR-Timer after step 3, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	2	P
8	Increase SS power level so as to cause a DL_Pathloss change at UE by 5dB.	–	–	–	–
9	Check: for 80% of prohibitPHR-Timer since step 7, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	1	F
10	Check: after prohibitPHR-Timer after step 7, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	2	P
Note 1: The SS transmits UL grant to the UE at every 10ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. Note 2: Steps 3 in main behaviour and step 1 in parallel behaviour can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.

Table 7.1.4.16.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a MAC PDU containing Power Headroom MAC Control Element.	–>	MAC PDU	–	–

7.1.4.16.3.3 Specific message contents

Table 7.1.4.16.3.3-1: RRCConnectionReconfiguration (step 2, Table 7.1.4.16.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer	infinity
prohibitPHR-Timer	sf1000
dl-PathlossChange	dB3
}
}
}
}
}
}
}
}
}

7.1.4.17 7.1.4.18 Correct handling of MAC control information / Buffer Status / UL data arrive in the UE Tx buffer / Extended buffer size

7.1.4.18.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, and ExtendedBSR-Sizes is configured in RRCConnectionReconfiguration procedure }

ensure that {

when { UL data arrives in the UE transmission buffer}

then { UE transmits a MAC PDU containing ‘Buffer Status Report’ MAC control element with Extended Buffer size }

}

7.1.4.18.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS36.321, clause 5.4.3 ,5.4.5 and 6.1.3.1.

[36.321, clause 5.4.3.1]

…

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR or Extended PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

…

[36.321, clause 5.4.5]

…

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.

All triggered BSRs shall be cancelled in case the UL grant(s) in this subframe can accommodate all pending data available for transmission but is not sufficient to additionally accommodate the BSR MAC control element plus its subheader. All triggered BSRs shall be cancelled when a BSR is included in a MAC PDU for transmission.

The UE shall transmit at most one Regular/Periodic BSR in a TTI. If the UE is requested to transmit multiple MAC PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR.

All BSRs transmitted in a TTI always reflect the buffer status after all MAC PDUs have been built for this TTI. Each LCG shall report at the most one buffer status value per TTI and this value shall be reported in all BSRs reporting buffer status for this LCG.

NOTE: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR. A Padding BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.

[36.321, clause 6.1.3.1]

Buffer Status Report (BSR) MAC control elements consist of either:

– Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or

– Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2).

The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2.

The fields LCG ID and Buffer Size are defined as follow:

– LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits;

– Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a logical channel group after all MAC PDUs for the TTI have been built. The amount of data is indicated in number of bytes. It shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of what data shall be considered as available for transmission is specified in [3] and [4] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits. If extendedBSR-Sizes is not configured, the values taken by the Buffer Size field are shown in Table 6.1.3.1-1. If extendedBSR-Sizes is configured, the values taken by the Buffer Size field are shown in Table 6.1.3.1-2.

…

Table 6.1.3.1-2: Extended Buffer size levels for BSR

Index	Buffer Size (BS) value [bytes]	Index	Buffer Size (BS) value [bytes]
0	BS = 0	32	4940 < BS <= 6074
1	0 < BS <= 10	33	6074 < BS <= 7469
2	10 < BS <= 13	34	7469 < BS <= 9185
3	13 < BS <= 16	35	9185 < BS <= 11294
4	16 < BS <= 19	36	11294 < BS <= 13888
5	19 < BS <= 23	37	13888 < BS <= 17077
6	23 < BS <= 29	38	17077 < BS <= 20999
7	29 < BS <= 35	39	20999 < BS <= 25822
8	35 < BS <= 43	40	25822 < BS <= 31752
9	43 < BS <= 53	41	31752 < BS <= 39045
10	53 < BS <= 65	42	39045 < BS <= 48012
11	65 < BS <= 80	43	48012 < BS <= 59039
12	80 < BS <= 98	44	59039 < BS <= 72598
13	98 < BS <= 120	45	72598 < BS <= 89272
14	120 < BS <= 147	46	89272 < BS <= 109774
15	147 < BS <= 181	47	109774 < BS <= 134986
16	181 < BS <= 223	48	134986 < BS <= 165989
17	223 < BS <= 274	49	165989 < BS <= 204111
18	274 < BS <= 337	50	204111 < BS <= 250990
19	337 < BS <= 414	51	250990 < BS <= 308634
20	414 < BS <= 509	52	308634 < BS <= 379519
21	509 < BS <= 625	53	379519 < BS <= 466683
22	625 < BS <= 769	54	466683 < BS <= 573866
23	769 < BS <= 945	55	573866 < BS <= 705666
24	945 < BS <= 1162	56	705666 < BS <= 867737
25	1162 < BS <= 1429	57	867737 < BS <= 1067031
26	1429 < BS <= 1757	58	1067031 < BS <= 1312097
27	1757 < BS <= 2161	59	1312097 < BS <= 1613447
28	2161 < BS <= 2657	60	1613447 < BS <= 1984009
29	2657 < BS <= 3267	61	1984009 < BS <= 2439678
30	3267 < BS <= 4017	62	2439678 < BS <= 3000000
31	4017 < BS <=4940	63	BS > 3000000

7.1.4.18.3 Test description

7.1.4.18.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB (1, 0) is used for step 8 in 4.5.3A.3 according to [18].

7.1.4.18.3.2 Definition of system information messages

Table 7.1.4.18.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Void	–	–	–	–
2	Void	–	–	–	–
3	The SS transmits a MAC PDU containing an RLC SDU of size 60 bytes.	<–	MAC PDU(RLC SDU)	–	–
4	The UE transmit a scheduling request.	–>	(SR)	–	–
5	The SS respond to the scheduling request in step 4 by an UL Grant of 32 bits.	<–	(UL Grant, 32 bits)	–	–
6	Check: Does The UE transmit a short BSR with ‘Buffer size’ field set to ‘10’?	–>	MAC PDU (MAC Short BSR (Buffer Size=’10’))	1	P
7	The SS is configured for Uplink Grant Allocation Type 3. The SS sends an uplink grant of size 520 bits.	<–	(UL grant)	–	–
8	UE transmits a MAC PDU containing a RLC SDU.	–>	MAC PDU(RLC SDU)	–	–

7.1.4.18.3.3 Specific message contents

Table 7.1.4.18.3.3-1: RRCConnectionReconfiguration (Preamble)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig-v1020 CHOICE {
extendedBSR-Sizes-r10	Setup
}
}
}
}
}
}

7.1.4.19 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting / Extended PHR

7.1.4.19.1 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting / Extended PHR / Intra-band Contiguous CA

7.1.4.19.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting and an SCell with uplink addition configured }

ensure that {

when { UE receives an Activation MAC Control Element activating the SCell }

then { UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element }

}

(2)

with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting for DL_Pathloss change configured }

ensure that {

when { the DL Pathloss changes and prohibitPHR-Timer is running }

then { UE does not transmit a MAC PDU containing Extended Power Headroom MAC Control Element }

}

(3)

with { UE in E-UTRA RRC_Connected state with DRB established, Extended Power headroom reporting for DL_Pathloss change configured }

ensure that {

when { prohibitPHR-Timer expires and extended power headroom report is triggered due to DL Pathloss change }

then { UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element }

}

7.1.4.19.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and 6.1.3.6a

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell and also with information about the difference between the nominal UE maximum power and the estimated power for UL-SCH and PUCCH transmission on PCell.

The reporting period, delay and mapping of Power Headroom are defined in subclause 9.1.8 of [9]. RRC controls Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-PathlossChange which sets the change in measured downlink pathloss and the required power backoff due to power management (as allowed by P-MPRc [10]) to trigger a PHR [8].

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB for at least one activated Serving Cell which is used as a pathloss reference since the last transmission of a PHR when the UE has UL resources for new transmission;

– periodicPHR-Timer expires;

– upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function;

– activation of an SCell with configured uplink.

– prohibitPHR-Timer expires or has expired, when the UE has UL resources for new transmission, and the following is true in this TTI for any of the active Serving Cells with configured uplink:

– there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the required power backoff due to power management (as allowed by P-MPR_c [10]) for this cell has changed more than dl-PathlossChange dB since the last transmission of a PHR when the UE had UL resources allocated for transmission or PUCCH transmission on this cell.

NOTE: The UE should avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such temporary decrease in the values of P_CMAX,c/PH when a PHR is triggered by other triggering conditions.

If the UE has UL resources allocated for new transmission for this TTI:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last transmission of a PHR or this is the first time that a PHR is triggered, and;

– if the allocated UL resources can accommodate a PHR MAC control element plus its subheader if extendedPHR is not configured, or the Extended PHR MAC control element plus its subheader if extendedPHR is configured, as a result of logical channel prioritization:

– if extendedPHR is configured:

– for each activated Serving Cell with configured uplink:

– obtain the value of the Type 1 power headroom;

– if the UE has UL resources allocated for transmission on this Serving Cell for this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the PCell;

– if the UE has a PUCCH transmission in this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element as defined in subclause 6.1.3.6a based on the values reported by the physical layer;

– else:

– obtain the value of the Type 1 power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element as defined in subclause 6.1.3.6 based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6a]

The Extended Power Headroom MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6a-2. When Type 2 PH is reported, the octet containing the Type 2 PH field is included first after the octet indicating the presence of PH per SCell and followed by an octet containing the associated P_CMAX,c field (if reported). Then follows in ascending order based on the ServCellIndex [8] an octet with the Type 1 PH field and an octet with the associated P_CMAX,c field (if reported), for the PCell and for each SCell indicated in the bitmap.

The Extended Power Headroom MAC Control Element is defined as follows:

– C_i: this field indicates the presence of a PH field for the SCell with SCellIndex i as specified in [8]. The C_i field set to "1" indicates that a PH field for the SCell with SCellIndex i is reported. The C_i field set to "0" indicates that a PH field for the SCell with SCellIndex i is not reported;

– R: reserved bit, set to "0";

– V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used. Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the associated P_CMAX,cfield, and V=1 indicates that the associated P_CMAX,cfield is omitted;

– Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [9]);

– P: this field indicates whether the UE applies power backoff due to power management (as allowed by P-MPR [10]). The UE shall set P=1 if the corresponding P_CMAX,c field would have had a different value if no power backoff due to power management had been applied;

– P_CMAX,c: if present, this field indicates the P_CMAX,c or [2] used for calculation of the preceding PH field. The reported P_CMAX,c and the corresponding nominal UE transmit power levels are shown in Table 6.1.3.6a-1 (the corresponding measured values in dBm can be found in subclause 9.6.1 of [9]).

Figure 6.1.3.6a-1: Void

Figure 6.1.3.6a-2: Extended Power Headroom MAC Control Element

Table 6.1.3.6a-1: Nominal UE transmit power level for Extended PHR

P_CMAX,c	Nominal UE transmit power level
0	PCMAX_C_00
1	PCMAX_C_01
2	PCMAX_C_02
…	…
61	PCMAX_C_61
62	PCMAX_C_62
63	PCMAX_C_63

7.1.4.19.1.3 Test description

7.1.4.19.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added

– Cell 3 is an Active SCell according to [18] cl. 6.3.4

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

7.1.4.19.1.3.2 Test procedure sequence

Table 7.1.4.19.1.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions after preamble. Subsequent configurations marked “T1”, “T2” etc are applied at the points indicated in the Main behaviour description in Table 7.1.4.19.1.3.2-1. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS36.508 Table 6.2.2.1-1.

Table 7.1.4.19.1.3.2-0: Cell configuration changes over time

	Parameter	Unit	Cell 1	Cell 3	Remarks
T0	Cell-specific RS EPRE	dBm/15kHz	-82	-82
T1	Cell-specific RS EPRE	dBm/15kHz	-89	-82
T2	Cell-specific RS EPRE	dBm/15kHz	-82	-82
T3	Cell-specific RS EPRE	dBm/15kHz	-82	-89
T4	Cell-specific RS EPRE	dBm/15kHz	-82	-82

Table 7.1.4.19.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) addition	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) addition.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS is configured for Uplink Grant Allocation Type 2. SS is configured to transmit UL grant for UE at every TTI for FDD, and every 5ms in a DL subframe for TDD.	–	–	–	–
4	The SS transmits an RRCConnectionReconfiguration message to provide Extended Power Headroom parameters	<–	RRCConnectionReconfiguration	–	–
	EXCEPTION: In parallel with step 5, UE executes parallel behaviour defined in table 7.1.4.19.1.3.2-2	–	–	–	–
5	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Extended Power Headroom parameters	–>	RRCConnectionReconfigurationComplete	–	–
6	The SS transmits an Activation MAC control element to activate SCell (Cell 3).	<–	MAC PDU (Activation (C₁=1))	–	–
7	Check: Does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	1	P
8	Wait for T1= 10% of prohibitPHR-Timer.	–	–	–	–
9	SS adjusts cell levels according to row T1 of table 7.1.4.19.1.3.2-0.	–	–	–	–
10	Check: for 80% of prohibitPHR-Timer since step 7, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	2	F
11	Check: after prohibitPHR-Timer after step 7, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	3	P
12	SS adjusts cell levels according to row T2 of table 7.1.4.19.1.3.2-0..	–	–	–	–
13	Check: for 80% of prohibitPHR-Timer since step 11, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	2	F
14	Check: after prohibitPHR-Timer after step 11, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	3	P
15	SS adjusts cell levels according to row T3 of table 7.1.4.19.1.3.2-0.	–	–	–	–
16	Check: for 80% of prohibitPHR-Timer since step 14, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	2	F
17	Check: after prohibitPHR-Timer after step 14, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	3	P
18	SS adjusts cell levels according to row T4 of table 7.1.4.19.1.3.2-0.	–	–	–	–
19	Check: for 80% of prohibitPHR-Timer since step 17, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	2	F
20	Check: after prohibitPHR-Timer after step 17, does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element?	–>	MAC PDU	3	P

Table 7.1.4.19.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element.	–>	MAC PDU	–	–

7.1.4.19.1.3.3 Specific message contents

Table 7.1.4.19.1.3.3-1: RRCConnectionReconfiguration (step 4, Table 7.1.4.19.1.3.2-1)

Derivation path: 36.508 table 4.6.1-8 condition SCell_AddMod
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer	infinity
prohibitPHR-Timer	sf1000
dl-PathlossChange	dB3
}
}
mac-MainConfig-v1020 SEQUENCE {
sCellDeactivationTimer-r10	Not Present
extendedBSR-Sizes-r10	Not Present
extendedPHR-r10	setup
}
}
}
}
}
}
}
}

7.1.4.19.2 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting / Extended PHR / Inter-band CA

The scope and description of the present TC is the same as test case 7.1.4.19.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Active SCell according to [18] cl. 6.3.4.

7.1.4.19.3 CA / UE power headroom reporting / SCell activation and DL pathloss change reporting / Extended PHR / Intra-band non-Contiguous CA

The scope and description of the present TC is the same as test case 7.1.4.19.1 with the following differences:

– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA

7.1.4.20 CA / Correct handling of MAC control information / Buffer status

7.1.4.20.1 CA / Correct handling of MAC control information / Buffer status / Intra-band Contiguous CA

7.1.4.20.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCell configured and activated }

ensure that {

when { UL data arrives in the UE transmission buffer and UE is scheduled to transmit on both PCell and SCell in a TTI }

then { UE transmits two MAC PDUs in a TTI, and one of the MAC PDU includes a Regular BSR, another MAC PDU includes a padding BSR }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when{ UE transmits a MAC PDU and the number of padding bits is equal to or larger than the size of a Long BSR plus its subheader }

then { UE reports a long BSR }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with SCell configured and activated }

ensure that {

when { periodicBSR-Timer expires and UE is scheduled to transmit on both PCell and SCell in a TTI }

then { UE transmits two MAC PDUs in a TTI, and one of the MAC PDU includes a Periodic BSR, another MAC PDU includes a padding BSR }

}

7.1.4.20.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1 and 5.4.5.

[TS 36.321 clause 5.4.3.1]

For the Logical Channel Prioritization procedure, the UE shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR or Extended PHR;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding.

NOTE: When the UE is requested to transmit multiple MAC PDUs in one TTI, steps 1 to 3 and the associated rules may be applied either to each grant independently or to the sum of the capacities of the grants. Also the order in which the grants are processed is left up to UE implementation. It is up to the UE implementation to decide in which MAC PDU a MAC control element is included when UE is requested to transmit multiple MAC PDUs in one TTI.

[TS 36.321 clause 5.4.5]

For the Buffer Status reporting procedure, the UE shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

– retxBSR-Timer expires and the UE has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR";

– periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

For Regular and Periodic BSR:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR;

– else report Short BSR.

For Padding BSR:

– if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

– else report Short BSR.

– else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report Long BSR.

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the UE has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate the BSR MAC control element(s);

– start or restart periodicBSR-Timer except when all the generated BSRs are Truncated BSRs;

– start or restart retxBSR-Timer.

– else if a Regular BSR has been triggered:

– if an uplink grant is not configured or the Regular BSR was not triggered due to data becoming available for transmission for a logical channel for which logical channel SR masking (logicalChannelSR-Mask) is setup by upper layers:

– a Scheduling Request shall be triggered.

The UE shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.

NOTE: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR. A Padding BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.

7.1.4.20.1.3 Test description

7.1.4.20.1.3.1 Pre-test conditions

System Simulator :

– Cell 1(PCell), Cell 3 (SCell)

– Cell 3 is an Active SCell according to [18] cl. 6.3.4.

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.20.1.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(2,0) is used for step 8 in 4.5.3A.3 according to [18].

– 2 AM DRBS are configured with the parameters specified in table 7.1.4.20.1-1.

Table 7.1.4.20.1-1: Logical Channel Configuration Settings

Parameter	DRB1	DRB2
LogicalChannel-Identity	3	4
Priority	7	6
prioritizedBitRate	0kbs	0kbs
logicalChannelGroup	2 (LCG ID#2)	2 (LCG ID#2)

7.1.4.20.1.3.2 Test procedure sequence

Table 7.1.4.20.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) addition	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) addition.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits an Activation MAC control element to activate SCell (Cell 3).	<–	MAC PDU (Activation (C₁=1))	–	–
–	EXCEPTION: Steps 4 and 5 shall be repeated for 2 times	–	–	–	–
4	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU (RLC SDU on LC3)	–
5	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU (RLC SDU on LC4)	–
6	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
7	The SS sends two uplink grants with same size of 136 bits for Cell 1 and Cell 3 in the same TTI (Note2)	<–	(UL grant)	–	–
8	Check: Does the UE transmit a MAC PDU containing an RLC SDU and a short BSR and another MAC PDU containing an RLC SDU and a padding BSR in a TTI?	–>	MAC PDU (Short BSR header (LCID=’11101’), MAC sub-header (E=’0’, F=’0’), Short BSR, AMD PDU), MAC PDU (Short BSR header (LCID=’11101’),MAC sub-header(E=’0’, F=’0’),, Short BSR, AMD PDU)	1	P
8a	The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 8	<–	MAC PDU	–	–
9	The SS sends two uplink grants with same size of 152 bits for both Cell 1 and Cell 3 in the same TTI (Note 3)	<–	(UL grant)	–	–
10	Check: Does the UE transmit two MAC PDUs, the second one containing an RLC SDU and a long padding BSR in a TTI?	–>	MAC PDU (Long BSR header (LCID=’11110’), MAC sub-header, Long BSR, RLC SDU) ( the scheduling procedures is applied to the sum of the capacities of the grants) Or MAC PDU (MAC sub-header, AMD PDU, RLC SDU) (the scheduling procedures is applied to each grant independently) MAC PDU (Long BSR header (LCID=’11110’), Long BSR, RLC SDU)	2	P
10a	The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 10	<–	MAC PDU	–	–
–	EXCEPTION: Steps 11 and 12 shall be repeated for 2 times	–	–	–	–
11	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU (RLC SDU on LC3)	–
12	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU (RLC SDU on LC4)	–
13	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
14	The SS is configured for Uplink Grant Allocation Type 2. The SS sends an uplink grant of size 16 bits.(Note 1)	<–	(UL grant)	–	–
15	The UE transmits a short BSR report with ‘Buffer size’ (LCG ID=2) set to value > ‘0’	–>	MAC PDU (‘Buffer size index’ > 0)	–	–
16	Wait for periodicBSR-Timer expiry.	–	–	–	–
17	The SS sends two uplink grants with same size of 136 bits for Cell 1 and Cell 3 in the same TTI (Note2)	<–	(UL grant)	–	–
18	Check: Does UE transmit a MAC PDU containing a Short BSR with ‘LCG ID’ field set to ‘10’ (logicalChannelGroup 1) and Buffer Size Index > 0 and another MAC PDU containing an RLC SDU and a padding BSR in a TTI?	–>	MAC PDU (Short BSR header (LCID=’11101’),’, Short BSR, (LCG ID= ’10’, Buffer Size index > 0), AMD PDU) MAC PDU (Short BSR, (LCID=’11101’),MAC sub-header, Short BSR,AMD PDU)	3	P
18a	The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 18	<–	MAC PDU	–	–
19	The SS sends two uplink grants with same size of 152 bits for both Cell 1 and Cell 3 in the same TTI (Note 3)	<–	(UL grant)	–	–
20	Check: Does the UE transmit two MAC PDUs, the second one containing an RLC SDU and a long padding BSR in a TTI??	–>	MAC PDU (Long BSR header (LCID=’11110’), Long BSR, RLC SDU) ( the scheduling procedures is applied to the sum of the capacities of the grants) Or MAC PDU (MAC sub-header, AMD PDU, RLC SDU) (the scheduling procedures is applied to each grant independently) MAC PDU (Long BSR header (LCID=’11110’), Long BSR, RLC SDU)	2	P
21	The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDUs in step 21	<–	MAC PDU	–	–
Note 1: SS transmit an UL grant of 16 bits (I_TBS=0, N_PRB=1, TS 36.213 Table 7.1.7.2.1-1) to allow UE to transmit a Regular BSR triggered by the new data received logicalChannelGroup 2 in step 15 This to enable testing of Padding BSR which has lower priority than Regular BSR. Note 2: UL grant of 136 bits (I_TBS=9, N_PRB=1, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR. RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include Short/Truncated BSR. Note 3: UL grant of 152 bits (I_TBS=0, N_PRB=6, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits will be equal to or larger than the size of Long BSR. RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of Long BSR is 3 bytes, i.e. setting UL grant to 19 bytes (152 bits) enable UE to include padding Long BSR.

7.1.4.20.1.3.3 Specific Message Contents

Table 7.1.4.20.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicit SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n5
periodicBSR-Timer	s128
retxBSR-Timer	sf10240
ttiBundling	FALSE
}
}
}
}
}
}
}
}

Table 7.1.4.20.1.3.3-2: RRCConnectionReconfiguration (Table 7.1.4.20.1.3.2-1, step 1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
radioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer	Infinity
prohibitPHR-Timer	sf1000
dl-PathlossChange	Infinity
}
}
mac-MainConfig-v1020 SEQUENCE {
extendedPHR-r10	Setup
}
}
}
}
}
}
}
}

7.1.4.20.2 CA / Correct handling of MAC control information / Buffer status / Inter-band CA

The scope and description of the present TC is the same as test case 7.1.4.20.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Active SCell according to [18] cl. 6.3.4

7.1.4.20.3 CA / Correct handling of MAC control information / Buffer status / Intra-band non-Contiguous CA

The scope and description of the present TC is the same as test case 7.1.4.20.1 with the following differences:

– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA

7.1.4.21 UE power headroom reporting / Extended PHR

7.1.4.21.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established Extended PHR reporting configured }

ensure that {

when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedure }

then { UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, Extended PHR reporting configured }

ensure that {

when { periodicPHR-Timer expires and UL resources allocated for new transmission }

then { UE transmits a MAC PDU containing Extended Power Headroom MAC Control Element }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { Extended power headroom reporting is disabled }

then { UE stops transmitting Extended Power Headroom MAC Control Element }

}

7.1.4.21.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and 6.1.3.6a.

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell and also with information about the difference between the nominal UE maximum power and the estimated power for UL-SCH and PUCCH transmission on PCell.

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– periodicPHR-Timer expires;

– upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function;

– activation of an SCell with configured uplink.

– prohibitPHR-Timer expires or has expired, when the UE has UL resources for new transmission, and the following is true in this TTI for any of the active Serving Cells with configured uplink:

If the UE has UL resources allocated for new transmission for this TTI:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered since the last transmission of a PHR or this is the first time that a PHR is triggered, and;

– if extendedPHR is configured:

– for each activated Serving Cell with configured uplink:

– obtain the value of the Type 1 power headroom;

– if the UE has UL resources allocated for transmission on this Serving Cell for this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the PCell;

– if the UE has a PUCCH transmission in this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element as defined in subclause 6.1.3.6a based on the values reported by the physical layer;

– else:

– obtain the value of the Type 1 power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element as defined in subclause 6.1.3.6 based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6a]

The Extended Power Headroom MAC Control Element is defined as follows:

– R: reserved bit, set to "0";

– Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [9]);

Figure 6.1.3.6a-1: Void

Figure 6.1.3.6a-2: Extended Power Headroom MAC Control Element

Table 6.1.3.6a-1: Nominal UE transmit power level for Extended PHR

P_CMAX,c	Nominal UE transmit power level
0	PCMAX_C_00
1	PCMAX_C_01
2	PCMAX_C_02
…	…
61	PCMAX_C_61
62	PCMAX_C_62
63	PCMAX_C_63

7.1.4.15.3 Test description

7.1.4.21.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

7.1.4.21.3.2 Test procedure sequence

Table 7.1.4.21.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS is configured for Uplink Grant Allocation Type 2. The SS transmits UL grant to the UE at every 10ms in a DL subframe. (Note 1)	–>	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message to provide Extended Power Headroom parameters	<–	–	–	–
3	Check: does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element? (Note 2)	–>	MAC PDU	1	P
4	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Extended Power Headroom parameters. (Note 2)	–>	–	–	–
5	Check: does the UE transmit a MAC PDU containing Extended Power Headroom MAC Control Element 200ms after step 3?	–>	MAC PDU	2	P
6	The SS transmits an RRCConnectionReconfiguration message to disable Extended Power Headroom reporting	<–	–	–	–
7	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the disabling of Extended Power Headroom parameters	–>	–	–	–
8	Check: for 2 seconds, does the UE transmit a MAC PDU containing Power Headroom MAC Control Element?	–>	MAC PDU	3	F
Note 1: The SS transmits UL grant to the UE at every 10ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. Note 2: Steps 3 and 4 can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.

7.1.4.21.3.3 Specific message contents

Table 7.1.4.21.3.3-1: RRCConnectionReconfiguration (step 2, Table 7.1.4.21.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Confign CHOICE {
setup SEQUENCE {
periodicPHR-Timer	sf200
prohibitPHR-Timer	sf1000
dl-PathlossChange	infinity
}
}
mac-MainConfig-v1020 SEQUENCE {
extendedPHR-r10	setup
}
}
}
}
}
}
}
}

Table 7.1.4.21.3.3-2: RRCConnectionReconfiguration (step 6, Table 7.1.4.21.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
release	NULL
}
}
}
}
}
}
}
}

7.1.4.22 Correct HARQ process handling / UL MIMO

7.1.4.22.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and UL MIMO configured }

ensure that {

when { UE receives one uplink grant (DCI format 4) with toggled NDI and two transport blocks enabled, and has data available for transmission }

then { UE transmits two new MAC PDUs both using redundancy version 0 for two HARQ processes in a TTI }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDUs less than maxHARQ-Tx times }

ensure that {

when { UE receives NACKs for two HARQ processes and no uplink grant is included for the next TTI corresponding to the two HARQ processes }

then { UE performs non-adaptive retransmission of the two MAC PDUs with redundancy version toggled by one of the last (re)transmission [0,2,3,1 order] }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDUs less than maxHARQ-Tx times }

ensure that {

when { UE receives NACK for one of the HARQ process and ACK for another HARQ process and no uplink grant is included for the next TTI corresponding to the HARQ processes }

then { UE performs non-adaptive retransmission of the MAC PDU with redundancy version toggled by one of the last (re)transmission [0,2,3,1 order] for the HARQ process that receives NACK and does not retransmit any MAC PDUs for another HARQ process that receives ACK }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDUs less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the two HARQ processes with old NDI [not toggled] for one HARQ process and with toggled NDI for another HARQ process, irrespective of ACK/NACK is received for previous (re)transmission }

then { UE performs an adaptive retransmission of the MAC PDU with redundancy version as received on PDCCH for HARQ process with old NDI and transmits a new MAC PDU for HARQ process with new NDI }

}

(5)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted two MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives ACKs and no uplink grant is included for the next TTI corresponding to the two HARQ processes }

then { UE does not retransmit any MAC PDUs for the two HARQ processes }

}

7.1.4.22.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1 & 5.4.2.2; TS 36.212, clause 5.3.3.1.8.

[TS 36.321, clause 5.4.2.1]

There is one HARQ entity at the UE for each Serving Cell with configured uplink, which maintains a number of parallel HARQ processes allowing transmissions to take place continuously while waiting for the HARQ feedback on the successful or unsuccessful reception of previous transmissions.

The number of parallel HARQ processes per HARQ entity is specified in [2], clause 8.

When the physical layer is configured for uplink spatial multiplexing [2], there are two HARQ processes associated with a given TTI. Otherwise there is one HARQ process associated with a given TTI.

TTI bundling is not supported for RN communication with the E-UTRAN in combination with an RN subframe configuration.

For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.

For each TTI, the HARQ entity shall:

– identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:

– if an uplink grant has been indicated for this process and this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of this HARQ process is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

When the HARQ feedback is received for this TB, the HARQ process shall:

– set HARQ_FEEDBACK to the received value.

If the HARQ entity requests a new transmission, the HARQ process shall:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.

NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

– if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer.

[TS 36.212, clause 5.3.3.1.8]

DCI format 4 is used for the scheduling of PUSCH in one UL cell with multi-antenna port transmission mode,

The following information is transmitted by means of the DCI format 4:

– Carrier indicator – 0 or 3 bits. The field is present according to the definitions in [3].

– Resource block assignment – bits,

– where P is the UL RBG size as defined in section 8.1.2 of [3]

– For resource allocation type 0:

– The LSBs provide the resource allocation in the UL subframe as defined in section 8.1.1 of [3]

– For resource allocation type 1:

– The LSBs provide the resource allocation in the UL subframe as defined in section 8.1.2 of [3]

– TPC command for scheduled PUSCH – 2 bits as defined in section 5.1.1.1 of [3]

– Cyclic shift for DM RS and OCC index – 3 bits as defined in section 5.5.2.1.1 of [2]

– UL index – 2 bits as defined in sections 5.1.1.1, 7.2.1, 8 and 8.4 of [3] (this field is present only for TDD operation with uplink-downlink configuration 0)

– Downlink Assignment Index (DAI) – 2 bits as defined in section 7.3 of [3] (this field is present only for TDD operation with uplink-downlink configurations 1-6)

– CSI request – 1 or 2 bits as defined in section 7.2.1 of [3]. The 2-bit field only applies to UEs that are configured with more than one DL cell.

– SRS request – 2 bits as defined in section 8.2 of [3]

– Resource allocation type – 1 bit as defined in section 8.1 of [3]

In addition, for transport block 1:

– Modulation and coding scheme and redundancy version – 5 bits as defined in section 8.6 of [3]

– New data indicator – 1 bit

In addition, for transport block 2:

– Modulation and coding scheme and redundancy version – 5 bits as defined in section 8.6 of [3]

– New data indicator – 1 bit

Precoding information and number of layers: number of bits as specified in Table 5.3.3.1.8-1. Bit field as shown in Table 5.3.3.1.8-2 and Table 5.3.3.1.8- 3. Note that TPMI for 2 antenna ports indicates which codebook index is to be used in Table 5.3.3A.2-1 of [2], and TPMI for 4 antenna ports indicates which codebook index is to be used in Table 5.3.3A.2-2, Table 5.3.3A.2-3, Table 5.3.3A.2-4 and Table 5.3.3A.2-5 of [2]. If both transport blocks are enabled, transport block 1 is mapped to codeword 0; and transport block 2 is mapped to codeword 1. In case one of the transport blocks is disabled, the transport block to codeword mapping is specified according to Table 5.3.3.1.5-2. For a single enabled codeword, indices 24 to 39 in Table 5.3.3.1.8-3 are only supported for retransmission of the corresponding transport block if that transport block has previously been transmitted using two layers.

Table 5.3.3.1.8-1: Number of bits for precoding information

Number of antenna ports at UE	Number of bits for precoding information
2	3
4	6

Table 5.3.3.1.8-2: Content of precoding information field for 2 antenna ports

One codeword: Codeword 0 enabled Codeword 1 disabled		Two codewords: Codeword 0 enabled Codeword 1 enabled
Bit field mapped to index	Message	Bit field mapped to index	Message
0	1 layer: TPMI=0	0	2 layers: TPMI=0
1	1 layer: TPMI=1	1-7	reserved
2	1 layer: TPMI=2
…	…
5	1 layer: TPMI=5
6-7	reserved

Table 5.3.3.1.8-3: Content of precoding information field for 4 antenna ports

One codeword: Codeword 0 enabled Codeword 1 disabled		Two codewords: Codeword 0 enabled Codeword 1 enabled
Bit field mapped to index	Message	Bit field mapped to index	Message
0	1 layer: TPMI=0	0	2 layers: TPMI=0
1	1 layer: TPMI=1	1	2 layers: TPMI=1
…	…	…	…
23	1 layer: TPMI=23	15	2 layers: TPMI=15
24	2 layers: TPMI=0	16	3 layers: TPMI=0
25	2 layers: TPMI=1	17	3 layers: TPMI=1
…	…	…	…
39	2 layers: TPMI=15	27	3 layers: TPMI=11
40-63	reserved	28	4 layers: TPMI=0
		29 – 63	Reserved

If the number of information bits in format 4 is equal to the payload size for DCI format 1, 2, 2A, 2B or 2C associated with the configured DL transmission mode in the same serving cell, one zero bit shall be appended to format 4.

7.1.4.22.3 Test description

7.1.4.22.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information takes into account the parameters in table 7.1.2.11.3.1-1.

UE:

UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18] using parameters as specified in Table 7.1.4.22.3.3-1 and 7.1.4.22.3.3-2.

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.22.3.2 Test procedure sequence

Table 7.1.4.22.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one MAC PDU including two RLC SDUs	<–	MAC PDU (2 RLC SDUs)	–	–
2	The SS transmits one UL Grant sufficient for transmitting loop back two RLC SDUs for two HARQ process X and Y, and both NDI indicate new transmission.	<–	Uplink Grant DCI: (DCI Format 4, redundancy version#1= 0, redundancy version#2= 0)	–	–
3	Check: Does the UE transmit two MAC PDUs both including one RLC SDU in HARQ process X and Y in a TTI, both redundancy version 0? (Note 1)	–>	Transport block 1: MAC PDU Transport block 2: MAC PDU	1	P
4	The SS transmits two NACKs for HARQ process X and Y	<–	HARQ NACK#X HARQ NACK#Y	–	–
5	Check: Does the UE retransmit the MAC PDUs for HARQ process X and Y, redundancy version 2? (Note 1)	–>	Transport block 1: MAC PDU Transport block 2: MAC PDU	2	P
6	The SS transmits a NACK for HARQ process X and ACK for HARQ process Y	<–	HARQ NACK#X HARQ ACK#Y	–	–
7	Check: Does the UE retransmit the MAC PDU for HARQ process X, redundancy version 3? (Note 1)	–>	Transport block 1: MAC PDU	3	P
8	The SS transmits ACK for HARQ process X	<–	HARQ ACK#X	–	–
9	Check: Does the UE retransmit the MAC PDUs for HARQ process X and Y?	–>	Transport block 1: MAC PDU Transport block 2: MAC PDU	5	F
10	The SS transmits one MAC PDU including one RLC SDU	<–	MAC PDU (1 RLC SDU)	–	–
11	The SS transmits one UL grant for HARQ process X and Y, with NDI not toggled and redundancy version to be used as ‘1’ for process X, with NDI toggled for process Y	<–	Uplink Grant	–	–
12	Check: Does the UE retransmit the MAC PDU for HARQ process X using redundancy version 1 and transmit a new MAC PDU sent by SS in step 10 for HARQ process Y? (Note 1)	–>	Transport block 1: MAC PDU (redundancy version 1) Transport block 2: MAC PDU	4	P
13	The SS transmits an RLC STATUS PDU to the UE.	<–	MAC PDU(RLC STATUS PDU (ACK_SN=3))	–	–
Note 1: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

7.1.4.22.3.3 Specific message contents

Table 7.1.4.22.3.3-1: MAC-MainConfig {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)}

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
maxHARQ-Tx	n6
}
}

Table 7.1.4.22.3.3-2: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)}

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

7.1.4.23 Correct HARQ process handling / TTI bundling with enhanced HARQ pattern

7.1.4.23.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling configured with e-HARQ-Pattern-r12 is set to TRUE }

ensure that {

when { UE receives an UL Grant with toggled NDI and has data available for transmission }

then { UE transmits a new MAC PDU and non-adaptive retransmissions for 3 additional consecutive UL subframes }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured with e-HARQ-Pattern-r12 is set to TRUE and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the bundled HARQ process }

then { UE performs non-adaptive retransmissions of the MAC PDU for 4 consecutive UL subframes }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured with e-HARQ-Pattern-r12 is set to TRUE and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with old NDI, irrespective of ACK/NACK is received for previous (re)transmission }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not retransmit the TTI Bundle }

}

7.1.4.23.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1, 5.4.2.2 & 7.5, TS 36.213 clause 8, 8.3, 8.6.1 & 9.1.2.

[TS 36.321, clause 5.4.2.1]

The number of parallel HARQ processes is specified in [2], clause 8.

For transmission of Msg3 during Random Access (see section 5.1.5) TTI bundling does not apply.

For each TTI, the HARQ entity shall:

– identify the HARQ process associated with this TTI;

– if an uplink grant has been indicated for this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of the HARQ process corresponding to this TTI is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission UE shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

The UE is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

When the HARQ feedback is received for this TB, the HARQ process shall:

– set HARQ_FEEDBACK to the received value.

If the HARQ entity requests a new transmission, the HARQ process shall:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the UE keeps the data in the HARQ buffer.

NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

– if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer;

[TS 36.321, clause 7.5]

The parameter TTI_BUNDLE_SIZE is 4.

[TS 36.213, clause 8]

When a UE is configured with higher layer parameter ttiBundling and configured with higher layer parameter e-HARQ-Pattern-r12 set to FALSE or not configured, for FDD and subframe bundling operation, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH/EPDCCH and PHICH information.

When a UE is configured with higher layer parameter ttiBundling and configured with higher layer parameter e-HARQ-Pattern-r12 set to TRUE, for FDD and subframe bundling operation, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission in subframe n-1 intended for the UE, adjust the corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH/EPDCCH and PHICH information.

7.1.4.23.3 Test description

7.1.4.23.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,1) is used for step 8 in 4.5.3A.3 according to [18].

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.23.3.2 Test procedure sequence

Table 7.1.4.23.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	SS Transmits RRCConnectionReconfiguration to configure TTI bundling	<–	–	–	–
0B	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
1	The SS Transmits a valid MAC PDU containing RLC PDU of size 312 bits on UM Bearer.	<–	MAC PDU	–	–
2	The UE transmits a Scheduling Request	–>	Scheduling Request	–	–
3	The SS allocates an UL Grant of 328 bits with NDI indicating new transmission (i.e. Nprb=3 and Imcs=7)	<–	Uplink Grant	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU, with redundancy version 0, 4 subframes after step 3? (Note 1)	–>	MAC PDU	1	P
5	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 4, for 3 consecutive UL subframes with redundancy version 2, 3 and 1 respectively? (Note 1)	–>	MAC PDU	1	P
6	The SS transmits a NACK, 4 subframes after last transmission in step 5.	<–	HARQ NACK	–	–
7	Check: Does the UE make non-adaptive retransmissions of the MAC PDU ‘5’ subframes after NACK in step 6, for 4 consecutive UL subframes with redundancy version 0, 2, 3 and 1 respectively? (Note 1)	–>	MAC PDU	2	P
8	The SS transmits an ACK, 4 subframes after last transmission in step 7.	<–	HARQ ACK	–	–
9	The SS allocates an UL Grant with NDI indicating retransmission, start redundancy version =2[i.e. Nprb=3 and Imcs=30], 1 subframes after ACK in step 8.	<–	Uplink Grant	–	–
10	Check: Does the UE perform an adaptive retransmission of the MAC PDU 4 subframes after grant in step 9, using redundancy version 2? (Note 1)	–>	MAC PDU	3	P
11	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 10, for 3 consecutive UL sub-frames with redundancy version 3, 1 and 0 respectively? (Note 1)	–>	MAC PDU	3	P
12	The SS transmits an ACK, 4 subframes after last transmission in step 11.	<–	HARQ ACK	–	–
13	Check: Does the UE make any retransmissions of the MAC PDU 5 subframes after ACK in step 12, for 4 consecutive UL subframes?	–>	MAC PDU	4	F
Note 1: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

7.1.4.23.3.3 Specific message contents

Table 7.1.4.23.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration (Step 0A)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28	Max value allowed
periodicBSR-Timer	Infinity
retxBSR-Timer	sf10240
ttiBundling	TRUE
}
e-HARQ-Pattern-r12	TRUE
}

7.1.4.24 Correct HARQ process handling / TTI bundling without resource allocation restriction

7.1.4.24.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and TTI bundling configured }

ensure that {

when { UE receives an UL Grant with toggled NDI indicating a resource block assignment correspondent to a physical resource block number of more than 3 and a modulation and coding scheme index of no less than 11 and has data available for transmission }

then { UE transmits a new MAC PDU on PUSCH on the granted resources using a transport block size correspondent to the read and and non-adaptive retransmissions for 3 additional consecutive UL subframes }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the bundled HARQ process }

then { UE performs non-adaptive retransmissions of the MAC PDU for 4 consecutive UL subframes }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, TTI bundling configured and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an uplink grant on PDCCH for the next TTI corresponding to the HARQ process with old NDI, irrespective of ACK/NACK is received for previous (re)transmission }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state with DRB established and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not retransmit the TTI Bundle }

}

7.1.4.24.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1, 5.4.2.2 & 7.5, TS 36.213 clause 8, 8.0, 8.3, 8.6.1 & 9.1.2.

[TS 36.321, clause 5.4.2.1]

There is one HARQ entity at the MAC entity for each Serving Cell with configured uplink, which maintains a number of parallel HARQ processes allowing transmissions to take place continuously while waiting for the HARQ feedback on the successful or unsuccessful reception of previous transmissions.

The number of parallel HARQ processes per HARQ entity is specified in [2], clause 8.

When the physical layer is configured for uplink spatial multiplexing [2], there are two HARQ processes associated with a given TTI. Otherwise there is one HARQ process associated with a given TTI.

TTI bundling is not supported for RN communication with the E-UTRAN in combination with an RN subframe configuration.

For transmission of Msg3 during Random Access (see subclause 5.1.5) TTI bundling does not apply.

For each TTI, the HARQ entity shall:

– identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:

– if an uplink grant has been indicated for this process and this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of this HARQ process is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

The MAC entity is configured with a Maximum number of HARQ transmissions and a Maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx.

When the HARQ feedback is received for this TB, the HARQ process shall:

– set HARQ_FEEDBACK to the received value.

If the HARQ entity requests a new transmission, the HARQ process shall:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the MAC entity keeps the data in the HARQ buffer.

NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

– if there is a measurement gap at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer;

[TS 36.321, clause 7.5]

The parameter TTI_BUNDLE_SIZE is 4.

[TS 36.213, clause 8]

For FDD and transmission mode 1, there shall be 8 uplink HARQ processes per serving cell for non-subframe bundling operation, i.e. normal HARQ operation, and 3 uplink HARQ processes for subframe bundling operation when parameter e-HARQ-Pattern-r12 is set to TRUE and 4 uplink HARQ processes for subframe bundling operation otherwise. For FDD and transmission mode 2, there shall be 16 uplink HARQ processes per serving cell for non-subframe bundling operation and there are two HARQ processes associated with a given subframe as described in [8]. The subframe bundling operation is configured by the parameter ttiBundling provided by higher layers.

In case higher layers configure the use of subframe bundling for FDD and TDD, the subframe bundling operation is only applied to UL-SCH, such that four consecutive uplink subframes are used.

[TS 36.213, clause 8.0]

When a UE is configured with higher layer parameter ttiBundling and configured with higher layer parameter e-HARQ-Pattern-r12 set to FALSE or not configured, for FDD and subframe bundling operation, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission in subframe n-5 intended for the UE, adjust the corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH/EPDCCH and PHICH information.

When a UE is configured with higher layer parameter ttiBundling and configured with higher layer parameter e-HARQ-Pattern-r12 set to TRUE, for FDD and subframe bundling operation, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission in subframe n-1 intended for the UE, adjust the corresponding first PUSCH transmission in the bundle in subframe n+4 according to the PDCCH/EPDCCH and PHICH information.

…

For TDD UL/DL configurations 1 and 6 and subframe bundling operation, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0 in subframe n intended for the UE, and/or a PHICH transmission intended for the UE in subframe n-l with l given in Table 8-2a, adjust the corresponding first PUSCH transmission in the bundle in subframe n+k, with k given in Table 8-2, according to the PDCCH/EPDCCH and PHICH information.

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

Table 8-2a: l for TDD configurations 0, 1 and 6

TDD UL/DL Configuration	subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	9	6				9	6
1		2			3		2			3
6	5	5				6	6			8

[TS 36.213, clause 8.3]

For FDD, and serving cell with frame structure type 1, an HARQ-ACK received on the PHICH assigned to a UE in subframe i is associated with the PUSCH transmission in subframe i-4.

…

For TDD, if the UE is not configured with EIMTA-MainConfigServCell-r12 for any serving cell and, if a UE is configured with one serving cell, or if the UE is configured with more than one serving cell and the TDD UL/DL configuration of all the configured serving cells is the same,

– For frame structure type 2 UL/DL configuration 1-6, an HARQ-ACK received on the PHICH assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-k as indicated by the following Table 8.3-1.

…

Table 8.3-1: k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number i
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	7	4				7	4
1		4			6		4			6
2				6					6
3	6								6	6
4									6	6
5									6
6	6	4				7	4			6

[TS 36.213, clause 8.6.1]

For, the modulation order () is determined as follows:

…

– If the parameter ttiBundling provided by higher layers is set to TRUE, then the modulation order is set to . Resource allocation size is restricted to applies in this case if the UE does not indicate support by higher layers to operate without it.

For the modulation order () is determined as follows:

…

– Otherwise, the modulation order shall be determined from the DCI transported in the latest PDCCH/EPDCCH with DCI format 0/4 for the same transport block using .

[TS 36.213, clause 9.1.2]

– For PUSCH transmissions scheduled from serving cell in subframe n, the UE shall determine the corresponding PHICH resource of serving cell in subframe , where

– is always 4 for FDD.

…

– For TDD, if the UE is not configured with EIMTA-MainConfigServCell-r12 for any serving cell and, if the UE is configured with one serving cell, or if the UE is configured with more than one serving cell and the TDD UL/DL configuration of all the configured serving cells is the same, for PUSCH transmissions scheduled from serving cell in subframe n, the UE shall determine the corresponding PHICH resource of serving cell in subframe , where is given in table 9.1.2-1.

…

For subframe bundling operation, the corresponding PHICH resource is associated with the last subframe in the bundle.

Table 9.1.2-1: for TDD

TDD UL/DL Configuration	subframe index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0			4	7	6			4	7	6
1			4	6				4	6
2			6					6
3			6	6	6
4			6	6
5			6
6			4	6	6			4	7

7.1.4.24.3 Test description

7.1.4.24.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.24.3.2 Test procedure sequence

Table 7.1.4.24.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0A	SS Transmits RRCConnectionReconfiguration to configure TTI bundling	<–	–	–	–
0B	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
1	The SS Transmits a valid MAC PDU containing RLC PDU of size 1248bits.	<–	MAC PDU	–	–
2	The UE transmits a Scheduling Request	–>	Scheduling Request	–	–
3	The SS allocates an UL Grant of 1256 bits with NDI indicating new transmission (i.e. Nprb=5 and Imcs=14) (Note 1)	<–	Uplink Grant	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU, using Nprb=5, QPSK modulation and TB_size=1256, with redundancy version 0, ‘k’ subframes after step 3? (Note 2 and 3)	–>	MAC PDU	1	P
5	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 4, for 3 consecutive UL subframes with redundancy version 2, 3 and 1 respectively? (Note 3)	–>	MAC PDU	1	P
6	The SS transmits a NACK, ‘kk’ subframes after last transmission in step 5. (Note 2)	<–	HARQ NACK	–	–
7	Check: Does the UE make non-adaptive retransmissions of the MAC PDU ‘m’ subframes after NACK in step 6, for 4 consecutive UL subframes with redundancy version 0, 2, 3 and 1 respectively? (Note 2 and 3)	–>	MAC PDU	2	P
8	The SS transmits an ACK, ‘kk’ subframes after last transmission in step 7. (Note 2)	<–	HARQ ACK	–	–
9	The SS allocates an UL Grant with NDI indicating retransmission, start redundancy version =2 [i.e. Nprb=5 and Imcs=30], ‘l’ subframes after ACK in step 8. (Note 2)	<–	Uplink Grant	–	–
10	Check: Does the UE perform an adaptive retransmission of the MAC PDU ‘k’ subframes after grant in step 9, using Nprb=5, QPSK modulation, TB_size=1256 and redundancy version 2? (Note 2 and 3)	–>	MAC PDU	3	P
11	Check: Does UE repeat non-adaptive retransmission of MAC PDU in step 10, for 3 consecutive UL sub-frames with redundancy version 3, 1 and 0 respectively? (Note 3)	–>	MAC PDU	3	P
12	The SS transmits an ACK, ‘kk’ subframes after last transmission in step 11. (Note 2)	<–	HARQ ACK	–	–
13	Check: Does the UE make any retransmissions of the MAC PDU ‘m’ subframes after ACK in step 12, for 4 consecutive UL subframes? (Note 2)	–>	MAC PDU	4	F
Note 1: In step3, for TDD, the subframe number of allocating UL grant should be selected from {‘1’, ‘4’, ‘6’, ‘9’} based on TDD default UL/DL configuration 1. Note 2: For FDD value of ‘k’, ‘kk’ is 4, ‘l’ is 5 and ‘m’ is 9. For TDD UL/DL configuration 1, values of ‘k’, ‘l’, ‘m’ and ‘kk’ are given in table 7.1.4.24.3.2-2. Note 3: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

Table 7.1.4.24.3.2-2: Values for parameter ‘k’, ‘l’, ‘m’ and ‘kk’ in Main behaviour.

Parameter	DL sub-frame number n
Parameter	0	1	2	3	4	5	6	7	8	9
k		6			4		6			4
l		3			2		3			2
m		7			8		7			8
kk			4	6				4	6

7.1.4.24.3.3 Specific message contents

Table 7.1.4.24.3.3-1: MAC-MainConfig-RBC in RRCConnectionReconfiguration (Step 0A)

Derivation Path: 36.508 Table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28	Max value allowed
periodicBSR-Timer	Infinity
retxBSR-Timer	sf10240
ttiBundling	TRUE
}
}

Table 7.1.4.24.3.3-2: RLC-Config-DRB-AM in RRCConnectionReconfiguration (Step 0A)

Derivation path: 36.508 Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

7.1.4.24a Correct HARQ process handling / TTI bundling without resource allocation restriction / UE with limited TB size

7.1.4.24a.1 Test Purpose (TP)

Same as sub-clause 7.1.4.24.1.

7.1.4.24a.2 Conformance requirements

Same as sub-clause 7.1.4.24.2.

7.1.4.24a.3 Test description

7.1.4.24a.3.1 Pre-test conditions

Same as sub-clause 7.1.4.24.3.

7.1.4.24a.3.2 Test procedure sequence

Same as test procedure in sub-clause 7.1.4.24.3.2 with the following exceptions:

– In step 1 use RLC PDU of size 888 bits instead of 1976 bits

– In step 3 use UL grant of 904 bits (Nprb=4 and Imcs=13) instead of 1992 bits (Nprb=5 and Imcs=19)

In steps 4 and 10 check that Nprb=4 and TB_size=904 instead of Nprb=5 and TB_size=1992

7.1.4.24a.3.3 Specific message contents

Same as sub-clause 7.1.4.24.3.

7.1.4.24b Correct HARQ process handling / Enhanced Coverage / CE Mode A

7.1.4.24b.1 Test Purpose (TP)

(1)

with { Enhanced coverage UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { UE receives an UL Grant on MPDCCH corresponding to the HARQ process x, with toggled NDI and has data available for transmission }

then { UE transmits a new MAC PDU and non-adaptive retransmissions for ‘repetition number -1’additional consecutive UL subframes }

}

(2)

with { Enhanced coverage UE in E-UTRA RRC_CONNECTED state with DRB established, and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an UL Grant on MPDCCH corresponding to the HARQ process x, with non toggled NDI }

then { UE performs adaptive retransmission of a MAC PDU with redundancy version as received on MPDCCH on first UL subframe and non-adaptive retransmissions for ‘repetition number -1’ additional consecutive UL subframes }

}

7.1.4.24b.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1 & 5.4.2.2, TS 36.213 clause 8.0

[TS 36.321, clause 5.4.2.1]

The number of parallel HARQ processes per HARQ entity is specified in [2], clause 8.

…

In asynchronous HARQ operation, HARQ process is associated with TTI based on the received UL grant. Each asynchronous HARQ process is associated with a HARQ process identifier. HARQ feedback is not applicable for asynchronous UL HARQ.

…

Uplink HARQ operation is asynchronous for BL UEs or UEs in enhanced coverage except for the repetitions within a bundle.

For BL UEs or UEs in enhanced coverage, the parameter UL_REPETITION_NUMBER provides the number of transmission repetitions within a bundle. For each bundle, UL_REPETITION_NUMBER is set to a value provided by lower layers. Bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle in consecutive subframes. Within a bundle HARQ retransmissions are non-adaptive and are triggered without waiting for feedback from previous transmissions according to UL_REPETITION_NUMBER. An uplink grant corresponding to a new transmission or a retransmission of the bundle is only received after the last repetition of the bundle. A retransmission of a bundle is also a bundle.

…

For each TTI, the HARQ entity shall:

– identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:

– if an uplink grant has been indicated for this process and this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of this HARQ process is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4.

…

For BL UEs or UEs in enhanced coverage for UL_REPETITION_NUMBER for Mode B operation, the same redundancy version is used multiple times before cycling to the next redundancy version as specified in Subclause 8.6.1 and 7.1.7.1 in [2].

…

If the HARQ entity requests a new transmission, the HARQ process shall:

– if UL HARQ operation is synchronous:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– if UL HARQ operation is synchronous:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– if UL HARQ operation is synchronous:

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if UL HARQ operation is asynchronous or HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the MAC entity keeps the data in the HARQ buffer.

NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap or a Sidelink Discovery Gap for Transmission, no HARQ feedback can be received and a non-adaptive retransmission follows.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

…

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

…

– if UL HARQ operation is synchronous:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, if UL HARQ operation is synchronous the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer;

[TS 36.213, clause 8.0]

A BL/CE UE shall upon detection on a given serving cell of an MPDCCH with DCI format 6-0A/6-0B intended for the UE, adjust the corresponding PUSCH transmission in subframe(s) n+k_i with i = 0, 1, …, N-1 according to the MPDCCH, where

– subframe n is the last subframe in which the MPDCCH is transmitted; and

– x≤k₀<k₁<…,k_N-1 and the value of is determined by the repetition number field in the corresponding DCI, where are given in Table 8-2b and Table 8-2c; and

– in case N>1, subframe(s) n+k_i with i=0,1,…,N-1 are N consecutive BL/CE UL subframe(s) starting with subframe n+x, and in case N=1, k₀=x;

– for FDD, x = 4;

– for TDD UL/DL configurations 1-6, or for TDD UL/DL configuration 0 and a BL/CE UE in CEModeB, the value of x is given as the value of k in Table 8-2 for the corresponding TDD UL/DL configuration; If the value x is not given in Table 8-2 for subframe n, denote subframe n’ as the first downlink/special subframe which has a value in Table 8-2 after subframe n, and substitute n with n’ in the above procedure for adjusting the PUSCH transmission.

– for TDD UL/DL configuration 0 and a BL/CE UE in CEModeA and N=1, if the MSB of the UL index in the MPDCCH with DCI format 6-0A is set to 1, the value of x is given as the value of k in Table 8-2 for the corresponding TDD UL/DL configuration; if the LSB of the UL index in the MPDCCH with DCI format 6-0A is set to 1, x = 7. The UE is not expected to receive DCI format 6-0A with both the MSB and LSB of the UL index set to 1 when N>1. In case both the MSB and LSB of the UL index are set to 1, the HARQ process number of the PUSCH corresponding the MSB of the UL index is and the HARQ process number of the PUSCH corresponding the LSB of the UL index is , where is determined according to the HARQ process number field in DCI format 6-0A

– The higher layer parameter ttiBundling is not applicable to BL/CE UEs.

– For a BL/CE UE, in case a PUSCH transmission with a corresponding MPDCCH collides with a PUSCH transmission without a corresponding MPDCCH in a subframe n, the PUSCH transmission without a corresponding MPDCCH is dropped from subframe n.

– For a BL/CE UE, in case of collision between at least one physical resource block to be used for PUSCH transmission and physical resource blocks corresponding to configured PRACH resources for BL/CE UEs or non-BL/CE UEs (defined in [3]) in a same subframe, the PUSCH transmission is dropped.

Table 8.2b: PUSCH repetition levels (DCI Format 6-0A)

Higher layer parameter ‘pusch-maxNumRepetitionCEmodeA’
Not configured	{1,2,4,8}
16	{1,4,8,16}
32	{1,4,16,32 }

7.1.4.24b.3 Test description

7.1.4.24b.3.1 Pre-test conditions

System Simulator:

Cell 1

– System information combination c1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

– SystemInformationBlockType2 (preamble: Table 4.5.3AA.3, step 1) using parameters as specified in Table 7.1.4.24b.3.3-1

UE:

None.

Preamble:

– The UE is in state Loopback Activation in cell supporting BL/CE UE (state 4-CE) according to [18].

7.1.4.24b.3.2 Test procedure sequence

Table 7.1.4.24b.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 1 to 10 are run 8[FDD]/4[TDD] times using test parameter values as given for each iteration in table 7.1.4.24b.3.2.-2.	–	–	–	–
1	The SS Transmits a valid MAC PDU containing RLC PDU	<–	MAC PDU	–	–
2	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates an UL Grant DCI format 6 0A, for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission, Repetition number is set as ‘00’B, redundancy version 0	<–	Uplink Grant	–	–
3	Check: Does the UE transmit a MAC PDU including one RLC SDU, in HARQ process X? (Note)	–>	MAC PDU	1	P
4	The SS allocates an UL Grant DCI format 6 0A, for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates re transmission, Repetition number is set as ‘01’B, redundancy version 1	<–	Uplink Grant	–	–
–	EXCEPTION: Step 5 is repeated 4 (Repetition number) times	–	–	–
5	Check: Does the UE retransmit the MAC PDU for HARQ process X? (Note)	–>	MAC PDU	2	P
6	The SS allocates an UL Grant DCI format 6 0A, for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates re transmission, Repetition number is set as ‘10’B, redundancy version 2	<–	Uplink Grant	–	–
–	EXCEPTION: Step 7 is repeated 8 (Repetition number) times	–	–	–
7	Check: Does the UE retransmit the MAC PDU for HARQ process X? (Note)	–>	MAC PDU	2	P
8	The SS allocates an UL Grant DCI format 6 0A, for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates re transmission, Repetition number is set as ‘11’B, redundancy version 3	<–	Uplink Grant	–	–
–	EXCEPTION: Step 9 is repeated 16 (Repetition number) times	–	–	–
9	Check: Does the UE retransmit the MAC PDU for HARQ process X? (Note)	–>	MAC PDU	2	P
10	The SS transmits an RLC STATUS PDU to the UE	<–	RLC STATUS PDU (ACK_SN=X+1)	–	–
Note: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

7.1.4.24b.3.2-2: Test Parameters

Iteration	UL HARQ process (X)
1	0
2	1
3	2
4	3
5	4[only for FDD]
6	5[only for FDD]
7	6[only for FDD]
8	7[only for FDD]
Note: The maximum UL HARQ process is 4 for TDD configuration 1 for BL UE.

7.1.4.24b.3.3 Specific message contents

Table 7.1.4.24b.3.3-1: SystemInformationBlockType2 (preamble)

Derivation Path: 36.508 clause 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {}	Not present
radioResourceConfigCommon SEQUENCE {}	RadioResourceConfigCommonSIB-DEFAULT	See subclause 4.6.3
}

Table 7.1.4.24b.3.3-2: RadioResourceConfigCommonSIB-DEFAULT (Table 7.1.4.24b.3.3-1)

Derivation Path : 36.508 table 4.6.3-14with condition CEmodeA

Table 7.1.4.24b.3.3-3: PUSCH-ConfigCommon-v1310-DEFAULT (Table 7.1.4.24b.3.3-2)

Derivation Path: 36.508 Table 4.6.3-10A
Information Element	Value/remark	Comment	Condition
PUSCH-ConfigCommon ::= SEQUENCE {
PUSCH-ConfigCommon-v1310 ::= SEQUENCE {
pusch-maxNumRepetitionCEmodeA-r13	r16
}

Table 7.1.4.24b.3.3-4: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3AA.3-1, step 8)}

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

Table 7.1.4.24b.3.3-5: PhysicalConfigDedicated-DEFAULT (all steps incl. preamble)

Derivation Path: 36.508 clause 4.8.2.1.6, Table 4.8.2.1.6-1 with CQI-Report related details from Table 4.6.3-2 (CQI-ReportConfig-DEFAULT)
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
CQI-ReportConfig-DEFAULT ::= SEQUENCE {
cqi-ReportModeAperiodic	rm20
nomPDSCH-RS-EPRE-Offset	0
cqi-ReportPeriodic	Not present
}
}

7.1.4.24c Correct HARQ process handling / Enhanced Coverage / CE Mode B

7.1.4.24c.1 Test Purpose (TP)

(1)

with { Enhanced coverage Mode B UE in E-UTRA RRC_CONNECTED state with DRB established }

ensure that {

when { UE receives an UL Grant for HARQ process x, with toggled NDI and has data available for transmission }

then { UE transmits a new MAC PDU and adaptive retransmissions for ‘repetition number -1’additional consecutive UL subframes and changes redundancy version every Nacc =4FDD/5TDD subframes as 0,1,2,3,0,1,2,3 }

}

7.1.4.24c.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1 & 5.4.2.2, TS 36.213 clause 8.0 & 8.6.1.

[TS 36.321, clause 5.4.2.1]

The number of parallel HARQ processes per HARQ entity is specified in [2], clause 8.

…

Uplink HARQ operation is asynchronous for BL UEs or UEs in enhanced coverage except for the repetitions within a bundle.

…

For each TTI, the HARQ entity shall:

– identify the HARQ process(es) associated with this TTI, and for each identified HARQ process:

– if an uplink grant has been indicated for this process and this TTI:

– if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or

– if the uplink grant was received in a Random Access Response:

– if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response:

– obtain the MAC PDU to transmit from the Msg3 buffer.

– else:

– obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity;

– deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process;

– instruct the identified HARQ process to trigger a new transmission.

– else:

– deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process;

– instruct the identified HARQ process to generate an adaptive retransmission.

– else, if the HARQ buffer of this HARQ process is not empty:

– instruct the identified HARQ process to generate a non-adaptive retransmission.

When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI.

[TS 36.321, clause 5.4.2.2]

Each HARQ process is associated with a HARQ buffer.

…

If the HARQ entity requests a new transmission, the HARQ process shall:

– if UL HARQ operation is synchronous:

– set CURRENT_TX_NB to 0;

– set CURRENT_IRV to 0;

– store the MAC PDU in the associated HARQ buffer;

– store the uplink grant received from the HARQ entity;

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

If the HARQ entity requests a retransmission, the HARQ process shall:

– if UL HARQ operation is synchronous:

– increment CURRENT_TX_NB by 1;

– if the HARQ entity requests an adaptive retransmission:

– store the uplink grant received from the HARQ entity;

– set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information;

– if UL HARQ operation is synchronous:

– set HARQ_FEEDBACK to NACK;

– generate a transmission as described below.

– else if the HARQ entity requests a non-adaptive retransmission:

– if UL HARQ operation is asynchronous or HARQ_FEEDBACK = NACK:

– generate a transmission as described below.

NOTE 1: When receiving a HARQ ACK alone, the MAC entity keeps the data in the HARQ buffer.

To generate a transmission, the HARQ process shall:

– if the MAC PDU was obtained from the Msg3 buffer; or

…

– instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value;

– increment CURRENT_IRV by 1;

…

– if UL HARQ operation is synchronous:

– set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission.

After performing above actions, if UL HARQ operation is synchronous the HARQ process then shall:

– if CURRENT_TX_NB = maximum number of transmissions – 1:

– flush the HARQ buffer;

[TS 36.213, clause 8.0]

– subframe n is the last subframe in which the MPDCCH is transmitted; and

– x≤k₀<k₁<…,k_N-1 and the value of is determined by the repetition number field in the corresponding DCI, where are given in Table 8-2b and Table 8-2c; and

– in case N>1, subframe(s) n+k_i with i=0,1,…,N-1 are N consecutive BL/CE UL subframe(s) starting with subframe n+x, and in case N=1, k₀=x;

– for FDD, x = 4;

– The higher layer parameter ttiBundling is not applicable to BL/CE UEs.

…

Table 8.2c: PUSCH repetition levels (DCI Format 6-0B)

Higher layer parameter ‘pusch-maxNumRepetitionCEmodeB’
Not configured	{4,8,16,32,64,128,256,512}
192	{1,4,8,16,32,64,128,192}
256	{4,8,16,32,64,128,192,256}
384	{4,16,32,64,128,192,256,384}
512	{4,16,64,128,192,256,384,512}
768	{8,32,128,192,256,384,512,768}
1024	{4,8,16,64,128,256,512,1024}
1536	{4,16,64,256,512,768,1024,1536}
2048	{4,16,64,128,256,512,1024,2048}

[TS 36.213, clause 8.6.1]

For a BL/CE UE, the modulation order is determined according to table 8.6.1-2. A BL/CE UE configured with CEModeB is not expected to receive a DCI format 6-0B indicating .

For BL/CE UEs, the same redundancy version is applied to PUSCH transmitted in a given block of consecutive subframes. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . Denote as the subframe number of the first uplink subframe intended for PUSCH. The PUSCH transmission spans consecutive subframes including non-BL/CE subframes where the PUSCH transmission is postponed. For the block of consecutive subframes, the redundancy version (rv_idx) for PUSCH is determined according to Table 7.1.7.1-2 using , where and. The blocks of subframes are sequential in time, starting with to which subframe belongs. For a BL/CE UE configured in CEModeA, and is determined by the ‘Redundancy version’ field in DCI format 6-0A. For a BL/CE UE configured with CEModeB, for FDD and for TDD, and .

Table 8.6.1-2: Modulation and TBS index table for PUSCH

MCS Index	Modulation Order	TBS Index
0	2	0
1	2	1
2	2	2
3	2	3
4	2	4
5	2	5
6	2	6
7	2	7
8	2	8
9	2	9
10	2	10
11	4	10
12	4	11
13	4	12
14	4	13
15	4	14

7.1.4.24c.3 Test description

7.1.4.24c.3.1 Pre-test conditions

System Simulator:

Cell 1

– System information combination c1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

– SystemInformationBlockType2 (preamble: Table 4.5.3AA.3, step 1) using parameters as specified in Table 7.1.4.24c.3.3-1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.24c.3.2 Test procedure sequence

Table 7.1.4.24c.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
–	EXCEPTION: Steps 1 to 4 are run 2 times using test parameter values as given for each iteration in table 7.1.4.24c.3.2.-2.	–	–	–	–
1	The SS Transmits a valid MAC PDU containing RLC PDU	<–	MAC PDU	–	–
2	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates an UL Grant DCI format 6 0B, for one HARQ process X, sufficient for one RLC SDU to be loop backed in a TTI, and NDI indicates new transmission, Repetition number is set as ‘100’B(32 transmissions	<–	Uplink Grant	–	–
	EXCEPTION: Step 3 is repeated 32 (Repetition number) times.
3	Check: Does the UE transmit a MAC PDU including one RLC SDU, in HARQ process X, The redundancy version used by UE changes every Nacc =4[FDD]/5[TDD] transmission as {0,1,2,3,0,1,2…}. The correct usage of redundancy version is implicitly tested by correct reception of PDU in TTCN?	–>	MAC PDU	1	P
4	The SS transmits an RLC STATUS PDU to the UE	<–	RLC STATUS PDU (ACK_SN=X+1)	–	–

7.1.4.24c.3.2-2: Test Parameters

Iteration	UL HARQ process (X)
1	0
2	1
Note: The maximum UL HARQ process is 2 for CE Mode B UE

7.1.4.24c.3.3 Specific message contents

Table 7.1.4.24c.3.3-1: SystemInformationBlockType2 (preamble)

Derivation Path: 36.508 clause 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
ac-BarringInfo SEQUENCE {}	Not present
radioResourceConfigCommon SEQUENCE {}	RadioResourceConfigCommonSIB-DEFAULT	See subclause 4.6.3
}

Table 7.1.4.24c.3.3-2: RadioResourceConfigCommonSIB-DEFAULT (Table 7.1.4.24c.3.3-1)

Derivation Path : 36.508 table 4.6.3-14 with condition CEmodeB

Table 7.1.4.24c.3.3-3: PUSCH-ConfigCommon-v1310-DEFAULT (Table 7.1.4.24c.3.3-2)

Derivation Path: 36.508 Table 4.6.3-5
Information Element	Value/remark	Comment	Condition
PUSCH-ConfigCommon ::= SEQUENCE {
PUSCH-ConfigCommon-v1310 ::= SEQUENCE {
pusch-maxNumRepetitionCEmodeB-r13	r192
}

Table 7.1.4.24c.3.3-4: RLC-Config-DRB-AM {RRCConnectionReconfiguration (preamble: Table 4.5.3AA.3-1, step 8)}

Derivation path: 36.508 clause 4.8.2.1.3.2, Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

7.1.4.24d Correct HARQ process handling / Repetition with asynchronous PUSCH enhancement

7.1.4.24d.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state configured with pusch-EnhancementsConfig and Repetition configured }

ensure that {

when { UE receives UL Grant DCI format 0C }

then { UE transmits a new MAC PDU on PUSCH and retransmissions with same redundancy version for ‘UE_REPETITION_NUMBER-1’additional consecutive UL subframes}

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with pusch-EnhancementsConfig, Repetition configured and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives a NACK and no uplink grant is included for the next TTI corresponding to the repetition HARQ process }

then { UE performs retransmits MAC PDU according to the next redundancy version index followed by retransmissions with same redundancy version for ‘UE_REPETITION_NUMBER-1’additional consecutive UL subframes }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with pusch-EnhancementsConfig and having transmitted a MAC PDU less than maxHARQ-Tx times }

ensure that {

when { UE receives an ACK and no uplink grant is included for the next TTI corresponding to the HARQ process }

then { UE does not retransmit the repetition }

}

7.1.4.24d.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.2.1，5.4.2.2, TS 36.213, clause 8.0.

[TS 36.321, clause 5.4.2.1]

Uplink HARQ operation is asynchronous for NB-IoT UEs, BL UEs or UEs in enhanced coverage except for the repetitions within a bundle, and in serving cells configured with pusch-EnhancementsConfig, and serving cells operating according to Frame Structure Type 3.

[TS 36.321, clause 5.4.2.2]

The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4. For serving cells configured with pusch-EnhancementsConfig, BL UEs or UEs in enhanced coverage see subclause 8.6.1 in [2] for the sequence of redundancy versions and redundancy version determination. For NB-IoT UEs see subclause 16.5.1.2 in [2] for the sequence of redundancy versions and redundancy version determination.

For NB-IoT UEs, BL UEs or UEs in enhanced coverage for UL_REPETITION_NUMBER for Mode B operation, the same redundancy version is used multiple times before cycling to the next redundancy version as specified in Subclause 16.5.1.2, 8.6.1 and 7.1.7.1 in [2].

[TS 36.213, clause 8.0]

A UE configured with parameter pusch-EnhancementsConfig shall upon detection on a given serving cell of an PDCCH/EPDCCH with DCI Format 0C intended for the UE, perform a corresponding PUSCH transmission in subframe(s) n+k_i if a transport block corresponding to the HARQ process of the PUSCH transmission is generated as described in [8] with i = 0, 1, …, N-1 according to the PDCCH/EPDCCH, where

– subframe n is the last subframe in which the PDCCH/EPDCCH is transmitted; and

– x≤k₀<k₁<…,k_N-1 and the value of N is given by Table 8-2k based on the repetition number field in the corresponding DCI Format 0C; and

– in case N>1, subframe(s) n+k_i with i=0,1,…,N-1 are N consecutive UL subframe(s) starting with subframe n+x, and in case N=1, k₀=x;

– for FDD, x = 4;

– for TDD UL/DL configurations 1-6, the value of x is given as the value of k in Table 8-2 for the corresponding TDD UL/DL configuration; If the value x is not given in Table 8-2 for subframe n, denote subframe n’ as the first downlink/special subframe which has a value in Table 8-2 after subframe n, and substitute n with n’ in the above procedure for performing the PUSCH transmission.

– for TDD UL/DL configuration 0 and N=1, if the MSB of the UL index in the PDCCH with DCI format 0C is set to 1, the value of x is given as the value of k in Table 8-2 for the corresponding TDD UL/DL configuration; if the LSB of the UL index in the PDCCH with DCI format 0C is set to 1, x = 7. The UE is not expected to receive DCI format 0C with both the MSB and LSB of the UL index set to 1 when N>1. In case both the MSB and LSB of the UL index are set to 1, the HARQ process number of the PUSCH corresponding the MSB of the UL index is and the HARQ process number of the PUSCH corresponding the LSB of the UL index is , where is determined according to the HARQ process number field in DCI format 0C.

Table 8-2k: PUSCH repetition levels (DCI Format 0C)

Repetition Number field in DCI Format 0C	Number of repetitions N
000	1
001	2
010	4
011	8
100	12
101	16
110	24
111	32

7.1.4.24d.3 Test description

7.1.4.24d.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination c1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

UE:

– The eCall capable UE supports PUSCH enhancement.

Preamble:

The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.24d.3.2 Test procedure sequence

Table 7.1.4.24d.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS Transmits RRCConnectionReconfiguration to configure TTI bundling	<–	–	–	–
2	The UE transmits RRCConnectionReconfigurationComplete	–>	–	–	–
3	The SS Transmits a valid MAC PDU containing RLC PDU of size 1248bits.	<–	MAC PDU	–	–
4	The UE transmits a Scheduling Request	–>	Scheduling Request	–	–
5	The SS allocates an UL Grant of 1256 bits via DCI format 0C with NDI indicating new transmission (i.e. Nprb=5 and Imcs=14) (Note 1), ‘Frequency hopping flag’ set as 0, ‘Repetition number’ set as ‘011’, ‘Redundancy version’ set as ‘00’, ‘HARQ process number’ set as X.	<–	Uplink Grant	–	–
6	Check: Does the UE transmit a MAC PDU including one RLC SDU for HARQ process X, using Nprb=5, QPSK modulation and TB_size=1256, for 8 consecutive UL subframes from the ‘k’ subframes after step 3 with redundancy version 0, in HARQ process X? (Note 2 and 3)	–>	MAC PDU	1	P
7	The SS transmits a NACK, ‘kk’ subframes after last transmission in step 7. (Note 2)	<–	HARQ NACK	–	–
8	Check: Does the UE make non-adaptive retransmissions of the MAC PDU ‘m’ subframes after NACK in step 8, for 8 consecutive UL subframes with redundancy version 2, in HARQ process X? (Note 2 and 3)	–>	MAC PDU	2	P
9	The SS transmits an ACK, ‘kk’ subframes after last transmission in step 9. (Note 2)	<–	HARQ ACK	–	–
10	Check: Does the UE make any retransmissions of the MAC PDU ‘m’ subframes after ACK in step 11, for 8 consecutive UL subframes? (Note 2)	–>	MAC PDU	3	F
Note 1: In step5, for TDD, the subframe number of allocating UL grant should be selected from {‘1’, ‘4’, ‘6’, ‘9’} based on TDD default UL/DL configuration 1. Note 2: For FDD value of ‘k’, ‘kk’ is 4, ‘l’ is 5 and ‘m’ is 9. For TDD UL/DL configuration 1, values of ‘k’, ‘l’, ‘m’ and ‘kk’ are given in table 7.1.4.24d.3.2-2. Note 3: Transmission of a UL MAC PDU with a specific redundancy version by the UE is implicitly tested by receiving the UL MAC PDU correctly at SS.

Table 7.1.4.24d.3.2-2: Values for parameter ‘k’, ‘l’, ‘m’ and ‘kk’ in Main behaviour.

Parameter	DL sub-frame number n
Parameter	0	1	2	3	4	5	6	7	8	9
k		6			4		6			4
l		3			2		3			2
m		7			8		7			8
kk			4	6				4	6

7.1.4.24d.3.3 Specific message contents

Table 7.1.4.24d.3.3-1: RRCConnectionReconfiguration (Step 1)

Derivation Path: 36.508 clause 4.6.1-8, condition SRB2-DRB(2, 0)
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 ::= SEQUENCE {
radioResourceConfigDedicated ::= SEQUENCE {
physicalConfigDedicated ::= SEQUENCE {
pusch-EnhancementsConfig-r14 ::= CHOICE {
setup SEQUENCE {
pusch-HoppingOffsetPUSCH-Enh-r14	Not present
interval-ULHoppingPUSCH-Enh-r14	Not present
}
}
}
}
}
}
}
}

Table 7.1.4.24d.3.3-2: MAC-MainConfig-RBC in RRCConnectionReconfiguration (Step 1)

Derivation Path: 36.508 Table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfigRBC- ::= SEQUENCE {
ul-SCH-Configuration SEQUENCE {
maxHARQ-Tx	n28	Max value allowed
periodicBSR-Timer	Infinity
retxBSR-Timer	sf10240
ttiBundling	FALSE
}
}

Table 7.1.4.24d.3.3-3: RLC-Config-DRB-AM in RRCConnectionReconfiguration (Step 1)

Derivation path: 36.508 Table 4.8.2.1.3.2-1
Information Element	Value/Remark	Comment	Condition
RLC-Config-DRB-AM ::= CHOICE {
am SEQUENCE {
ul-AM-RLC SEQUENCE {
t-PollRetransmit	ms250
}
}
}

7.1.4.25 FDD-TDD CA / Correct HARQ process handling / PUSCH

7.1.4.25.1 FDD-TDD CA / Correct HARQ process handling / PUSCH / FDD PCell and TDD SCell

7.1.4.25.1.1 Test Purpose (TP)

(1)

with { UE supporting of TDD-FDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects a PDCCH UL Grant or PHICH NACK transmission in subframe n on FDD PCell for previous PUSCH transmission }

then { UE shall adjust the corresponding PUSCH transmission for the FDD PCell in subframe n+4 }

}

(2)

with { UE supporting of TDD-FDD CA with FDD PCell and TDD SCell in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects a PDCCH UL Grant or PHICH NACK transmission in subframe m on TDD SCell for previous PUSCH transmission }

then { UE shall adjust the corresponding PUSCH transmission in subframe m+k for the TDD SCell, with k given in Table 8-2 of TS 36.213 }

}

7.1.4.25.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 10.2. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 8.0]

…

For FDD-TDD and normal HARQ operation and a PUSCH for serving cell with frame structure type 1, the UE shall upon detection of a PDCCH/EPDCCH with DCI format 0/4 and/or a PHICH transmission in subframe n intended for the UE, adjust the corresponding PUSCH transmission for serving cell c in subframe n+4 according to the PDCCH/EPDCCH and PHICH information. [Test Point 1]

…

For FDD-TDD and primary cell frame structure type 2, if a serving cell is a primary cell, the serving cell UL/DL configuration is the UL-reference UL/DL configuration for the serving cell.

For FDD-TDD if the UE is not configured to monitor PDCCH/EPDCCH in another serving cell for scheduling a secondary serving cell with frame structure type 2, the serving cell UL/DL configuration is the UL-reference UL/DL configuration for the serving cell.

…

For TDD, if a UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two configured serving cells is not the same or if the UE is configured with EIMTA-MainConfigServCell-r12 for at least one serving cell, or FDD-TDD,

– For a serving cell with an UL-reference UL/DL configurations belonging to {1,2,3,4,5,6} and normal HARQ operation, the UE shall upon detection of a PDCCH/EPDCCH with uplink DCI format and/or a PHICH transmission in subframe n intended for the UE, adjust the corresponding PUSCH transmission in subframe n+k for the serving cell, with k given in Table 8-2, according to the PDCCH/EPDCCH and PHICH information, where the "TDD UL/DL Configuration" given in Table 8-2 refers to the UL-reference UL/DL configuration. [Test Point 2]

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

…

7.1.4.25.1.3 Test description

7.1.4.25.1.3.1 Pre-test conditions

System Simulator:

Cell 1 PCell (FDD), Cell 10 SCell (TDD)
Cell 10 is Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.25.1.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure.

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

7.1.4.25.1.3.2 Test procedure sequence

Table 7.1.4.25.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate SCell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS transmits a valid MAC PDU containing RLC PDU on PCell Cell 1	<–	MAC PDU	–	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI for PCell Cell1 in SF-Num ‘n’.	<–	Uplink Grant	–	–
7	Check: Does the UE transmit a MAC PDU including one RLC SDU in SF-Num ‘n+4’?	–>	MAC PDU	1	P
8	The SS transmits a NACK in SF-Num ‘n’.	<–	HARQ NACK	–	–
9	Check: Does the UE retransmit the MAC PDU for PCell Cell1 in SF-Num ‘n+4’?	–>	MAC PDU	1	P
10	The SS transmits a valid MAC PDU containing RLC PDU on SCell Cell 2.	<–	MAC PDU	–	–
11	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
12	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI for SCell Cell2 in SF-Num ‘m’.	<–	Uplink Grant	–	–
13	Check: Does the UE transmit a MAC PDU including one RLC SDU for SCell Cell 2 in SF-Num ‘m+k?	–>	MAC PDU	2	P
14	The SS transmits a NACK in SF-Num ‘m’.	<–	HARQ NACK	–	–
15	Check: Does the UE retransmit the MAC PDU for SCell Cell2 in SF-Num ‘m+k’?	–>	MAC PDU	2	P

7.1.4.25.2 FDD-TDD CA / Correct HARQ process handling / PUSCH / TDD PCell and FDD SCell

7.1.4.25.2.1 Test Purpose (TP)

(1)

with { UE supporting of TDD-FDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects a PDCCH UL Grant or PHICH NACK transmission in subframe m on FDD SCell }

then { UE shall adjust the corresponding PUSCH transmission in subframe m+4 for the FDD SCell }

}

(2)

with { UE supporting of TDD-FDD CA with TDD PCell and FDD SCell in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detects a PDCCH UL Grant or PHICH NACK transmission in subframe n on TDD PCell }

then { UE shall adjust the corresponding PUSCH transmission for the TDD PCell in subframe n+k with k given in Table 8-2 of TS 36.213 }

}

7.1.4.25.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 10.2. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 8.0]

…

For FDD-TDD and primary cell frame structure type 2, if a serving cell is a primary cell, the serving cell UL/DL configuration is the UL-reference UL/DL configuration for the serving cell.

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

…

7.1.4.25.2.3 Test description

7.1.4.25.2.3.1 Pre-test conditions

System Simulator:

Cell 1 PCell (TDD), Cell 10 SCell (FDD)
Cell 10 is Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.25.2.3.3-1

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure.

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

7.1.4.25.2.3.2 Test procedure sequence

Table 7.1.4.25.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate SCell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS transmits a valid MAC PDU containing RLC PDU on SCell (Cell 10).	<–	MAC PDU	–	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI for SCell (Cell 10) in SF-Num ‘n’.	<–	Uplink Grant	–	–
7	Check: Does the UE transmit a MAC PDU including one RLC SDU in SF-Num ‘n+4’?	–>	MAC PDU	1	P
8	The SS transmits a NACK in SF-Num ‘n’.	<–	HARQ NACK	–	–
9	Check: Does the UE retransmit the MAC PDU for SCell (Cell 10) in SF-Num ‘n+4’?	–>	MAC PDU	1	P
10	The SS transmits a valid MAC PDU containing RLC PDU on PCell (Cell 1).	<–	MAC PDU	–	–
11	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
12	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI for PCell (Cell 1) in SF-Num ‘m’.	<–	Uplink Grant	–	–
13	Check: Does the UE transmit a MAC PDU including one RLC SDU for PCell (Cell 1) in SF-Num ‘m+k?	–>	MAC PDU	2	P
14	The SS transmits a NACK in SF-Num ‘m’.	<–	HARQ NACK	–	–
15	Check: Does the UE retransmit the MAC PDU for PCell (Cell 1) in SF-Num ‘m+k’?	–>	MAC PDU	2	P
Note 1: Where k given in Table 8-2 of TS 36.213. As per the UL-reference UL/DL configuration 1 which is the primary cell1’s UL/DL configuration. SF-Num ‘m’ can be ‘1’, ‘4’, ‘6’ and ‘9’, the corresponding SF-Num ‘m+k’ is ‘7’, ‘8’, ‘2’ and ‘3’.

7.1.4.25.2.3.3 Specific Message Contents

Table 7.1.4.25.2.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.25.2.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.4.25.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.4.25.2.3.3-3: SCellToAddMod-r10 (Table 7.1.4.25.2.3.2-1)

Derivation Path: 36.508, Table 4.6.3-19D
Information Element	Value/remark	Comment	Condition
SCellToAddMod-r10 ::= SEQUENCE {
sCellIndex-r10	1
cellIdentification-r10 SEQUENCE {
physCellId-r10	PhysicalCellIdentity of Cell 10
dl-CarrierFreq-r10	Same downlink EARFCN as used for Cell 10
}
}

7.1.4.26 Dual Connectivity / Correct handling of MAC control information / Buffer status

7.1.4.26.1 Correct handling of MAC control information / Buffer status / Split DRB

7.1.4.26.1.1 Test Purpose (TP)

(1)

with { UE in connected mode with SCG activated with a Split DRB configured with the IE ul-DataSplitDRB-ViaSCG set to TRUE }

ensure that {

when { a BSR is triggered }

then { UE transmits a BSR indicating the data available for transmission to the MAC entity configured for SCG only }

}

(2)

with { UE in connected mode with SCG activation with a Split DRB configured with the IE ul-DataSplitDRB-ViaSCG set to FALSE }

ensure that {

when { a BSR is triggered }

then { UE transmits a BSR indicating the data available for transmission to the MAC entity configured for MCG only }

}

7.1.4.26.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.4.3.1, 5.4.5 and TS 36.323 clause 4.5.

[TS 36.321 clause 5.4.3.1]

For the Logical Channel Prioritization procedure, the MAC entity shall take into account the following relative priority in decreasing order:

– MAC control element for C-RNTI or data from UL-CCCH;

– MAC control element for BSR, with exception of BSR included for padding;

– MAC control element for PHR, Extended PHR, or Dual Connectivity PHR;

– MAC control element for Sidelink BSR, with exception of Sidelink BSR included for padding;

– data from any Logical Channel, except data from UL-CCCH;

– MAC control element for BSR included for padding;

– MAC control element for Sidelink BSR included for padding.

NOTE: When the MAC entity is requested to transmit multiple MAC PDUs in one TTI, steps 1 to 3 and the associated rules may be applied either to each grant independently or to the sum of the capacities of the grants. Also the order in which the grants are processed is left up to UE implementation. It is up to the UE implementation to decide in which MAC PDU a MAC control element is included when MAC entity is requested to transmit multiple MAC PDUs in one TTI. When the UE is requested to generate MAC PDU(s) in two MAC entities in one TTI, it is up to UE implementation in which order the grants are processed.

[TS 36.321 clause 5.4.5]

The Buffer Status reporting procedure is used to provide the serving eNB with information about the amount of data available for transmission in the UL buffers associated with the MAC entity. RRC controls BSR reporting by configuring the three timers periodicBSR-Timer, retxBSR-Timer and logicalChannelSR-ProhibitTimer and by, for each logical channel, optionally signalling logicalChannelGroup which allocates the logical channel to an LCG [8].

For the Buffer Status reporting procedure, the MAC entity shall consider all radio bearers which are not suspended and may consider radio bearers which are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the following events occur:

– retxBSR-Timer expires and the MAC entity has data available for transmission for any of the logical channels which belong to a LCG, in which case the BSR is referred below to as "Regular BSR";

– periodicBSR-Timer expires, in which case the BSR is referred below to as "Periodic BSR".

For Regular BSR:

– if the BSR is triggered due to data becoming available for transmission for a logical channel for which logicalChannelSR-ProhibitTimer is configured by upper layers:

– start or restart the logicalChannelSR-ProhibitTimer;

– else:

– if running, stop the logicalChannelSR-ProhibitTimer.

For Regular and Periodic BSR:

– if more than one LCG has data available for transmission in the TTI where the BSR is transmitted: report Long BSR;

– else report Short BSR.

For Padding BSR:

– if the number of padding bits is equal to or larger than the size of the Short BSR plus its subheader but smaller than the size of the Long BSR plus its subheader:

– else report Short BSR.

– else if the number of padding bits is equal to or larger than the size of the Long BSR plus its subheader, report Long BSR.

If the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled:

– if the MAC entity has UL resources allocated for new transmission for this TTI:

– instruct the Multiplexing and Assembly procedure to generate the BSR MAC control element(s);

– start or restart periodicBSR-Timer except when all the generated BSRs are Truncated BSRs;

– start or restart retxBSR-Timer.

– else if a Regular BSR has been triggered and logicalChannelSR-ProhibitTimer is not running:

– a Scheduling Request shall be triggered.

The MAC entity shall restart retxBSR-Timer upon indication of a grant for transmission of new data on any UL-SCH.

The MAC entity shall transmit at most one Regular/Periodic BSR in a TTI. If the MAC entity is requested to transmit multiple MAC PDUs in a TTI, it may include a padding BSR in any of the MAC PDUs which do not contain a Regular/Periodic BSR.

NOTE: A Padding BSR is not allowed to cancel a triggered Regular/Periodic BSR. A Padding BSR is triggered for a specific MAC PDU only and the trigger is cancelled when this MAC PDU has been built.

[TS 36.323 clause 4.5]

For the purpose of MAC buffer status reporting, the UE shall consider PDCP Control PDUs, as well as the following as data available for transmission in the PDCP layer:

For SDUs for which no PDU has been submitted to lower layers:

the SDU itself, if the SDU has not yet been processed by PDCP, or
the PDU if the SDU has been processed by PDCP.

In addition, for radio bearers that are mapped on RLC AM, if the PDCP entity has previously performed the re-establishment procedure, the UE shall also consider the following as data available for transmission in the PDCP layer:

For SDUs for which a corresponding PDU has only been submitted to lower layers prior to the PDCP re-establishment, starting from the first SDU for which the delivery of the corresponding PDUs has not been confirmed by the lower layer, except the SDUs which are indicated as successfully delivered by the PDCP status report, if received:

the SDU, if it has not yet been processed by PDCP, or
the PDU once it has been processed by PDCP.

For split bearers, when indicating the data available for transmission to the MAC entity for BSR triggering and Buffer Size calculation, the UE shall:

– if ul-DataSplitDRB-ViaSCG is set to TRUE by upper layer [3]:

– indicate the data available for transmission to the MAC entity configured for SCG only;

– else:

– indicate the data available for transmission to the MAC entity configured for MCG only.

7.1.4.26.1.3 Test description

7.1.4.26.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

Preamble:

– The UE is in state DC Split DRB Loopback Activated (state 6B) on Cell 1 and Cell 10 according to [18].

7.1.4.26.1.3.2 Test procedure sequence

Table 7.1.4.26.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
St		U – S	Message	TP	Verdict
1	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU	–	–
2	UE transmits a Scheduling Request on PUCCH via PCell	–>	(SR)	–	–
3	The SS sends uplink grants with size of 32 bits for Cell 10.	<–	(UL grant)	–	–
4	Check: Does the UE transmit a MAC PDU containing an RLC SDU and a short BSR via SCG (Cell 10)?	–>	MAC PDU (Short BSR header (LCID=’11101’), MAC sub-header (E=’0’, F=’0’), Short BSR),	1	P
5	The SS sends uplink grants with size of 136 bits for Cell 10 (Note1)	<–	(UL grant)	–	–
6	Check: Does the UE transmit a MAC PDU containing an RLC SDU and a short BSR via SCG (Cell 10)?	–>	MAC PDU (Short BSR header (LCID=’11101’), MAC sub-header (E=’0’, F=’0’), Short BSR, AMD PDU),	–	–
7	The SS transmits a RLC STATUS PDU acknowledge.	<–	RLC STATUS PDU(ACK_SN=0)	–	–
8	The SS transmits an RRCConnectionReconfiguration message	<–	RRCConnectionReconfiguration	–	–
9	The UE transmits an RRCConnectionReconfigurationComplete	–>	RRCConnectionReconfigurationComplete	–	–
10	The SS transmits a MAC PDU including an RLC SDU of size 12 bytes.	<–	MAC PDU	–	–
11	UE transmits a Scheduling Request on PUCCH via PCell.	–>	(SR)	–	–
12	The SS sends uplink grants with size of 32 bits for Cell 1.	<–	(UL grant)	–	–
13	Check: Does the UE transmit a MAC PDU containing an RLC SDU and a short BSR via MCG (Cell 1)?	–>	MAC PDU (Short BSR header (LCID=’11101’), MAC sub-header (E=’0’, F=’0’), Short BSR),	2	P
14	The SS sends uplink grants with size of 136 bits for Cell 1 (Note1)	<–	(UL grant)	–	–
15	Check: Does the UE transmit a MAC PDU containing an RLC SDU and a short BSR via MCG (Cell 1)?	–>	MAC PDU (Short BSR header (LCID=’11101’), MAC sub-header (E=’0’, F=’0’), Short BSR, AMD PDU),	–	–
16	The SS transmits a RLC STATUS PDU acknowledge.	<–	RLC STATUS PDU(ACK_SN=1)	–	–
Note 1: UL grant of 136 bits (I_TBS=9, N_PRB=1, TS 36.213 Table 7.1.7.2.1-1) is chosen such that the MAC PDU padding bits will be equal to or larger than the size of Short/Truncated BSR and smaller than Long BSR. RLC SDU size is 12 bytes, size of AMD PDU header is 2 bytes, size of MAC header is 2 bytes (1 byte for MAC SDU sub-header using R/R/E/LCID for last sub header and 1 byte for BSR sub-header) and size of Short BSR/Truncated BSR is one byte, i.e. setting UL grant to 17 bytes (136 bits) enable UE to include Short/Truncated BSR.

7.1.4.26.1.3.3 Specific message contents

Table 7.1.4.26.1.3.3-1: RRCConnectionReconfiguration (step 8, Table 7.1.4.26.1.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated-DRB {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {
pdcp-Config	PDCP-Config-DRB-AM
}
}
}
}
}
}

Table 7.1.4.26.1.3.3-2: PDCP-Config-DRB-AM (Table 7.1.4.26.1.3.3-1)

Derivation Path: 36.508 table 4.8.2.1.2.2-1
Information Element	Value/remark	Comment	Condition
PDCP-Config-DRB-AM ::= SEQUENCE {
discardTimer	Infinity
rlc-AM SEQUENCE {
statusReportRequired	TRUE
}
rlc-UM SEQUENCE {}	Not present
headerCompression CHOICE {
notUsed	NULL
}
ul-DataSplitDRB-ViaSCG-r12	FALSE	Uplink transmission of split DRB PDCP SDUs configured to be transmitted on the PSCell	DC_Setup_Split_DRB
t-Reordering-r12	ms200	ENUMERATED {ms0, ms20, ms40, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220, ms240, ms260, ms280, ms300, ms500, ms750}	DC_Setup_Split_DRB
}

7.1.4.27 Dual Connectivity headroom reporting

7.1.4.27.1 DC power headroom reporting / PSCell activation and DL pathloss change reporting / SCG DRB

7.1.4.27.1.1 Test Purpose (TP)

(1)

with { UE in connected mode on a PCell }

ensure that {

when { PSCell is added with a SCG bearer }

then { UE transmits a Dual Connectivity Power Headroom Report for the PCell and PSCell}

(2)

with { UE in connected mode with a SCG DRB established and with UE power headroom reporting by DL_Pathloss change configured }

ensure that {

when { DL Pathloss change is triggered while prohibitPHR-Timer is running }

then { the UE does not transmit any UE Power Headroom Report }

}

(3)

with { UE in connected mode with a SCG DRB established and with UE power headroom reporting by DL_Pathloss change configured }

ensure that {

when { the prohibitPHR-Timer has expired and DL Pathloss change is triggered }

then { UE transmits a Dual Connectivity Power Headroom Report }

}

7.1.4.27.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.321 clauses 5.4.6, 6.1.3.6b, 6.2.1.

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell and also with information about the difference between the nominal UE maximum power and the estimated power for UL-SCH and PUCCH transmission on SpCell.

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB for at least one activated Serving Cell of any MAC entity which is used as a pathloss reference since the last transmission of a PHR in this MAC entity when the MAC entity has UL resources for new transmission;

– periodicPHR-Timer expires;

– upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function;

– activation of an SCell of any MAC entity with configured uplink.

– addition of the PSCell

– prohibitPHR-Timer expires or has expired, when the MAC entity has UL resources for new transmission, and the following is true in this TTI for any of the activated Serving Cells of any MAC entity with configured uplink:

– there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the required power backoff due to power management (as allowed by P-MPR_c [10]) for this cell has changed more than dl-PathlossChange dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH transmission on this cell.

NOTE: The MAC entity should avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such temporary decrease in the values of P_CMAX,c/PH when a PHR is triggered by other triggering conditions.

If the MAC entity has UL resources allocated for new transmission for this TTI the MAC entity shall:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled, and;

– if the allocated UL resources can accommodate a PHR MAC control element plus its subheader if neither extendedPHR nor dualConnectivityPHR is configured, or the Extended PHR MAC control element plus its subheader if extendedPHR is configured, or the Dual Connectivity PHR MAC control element plus its subheader if dualConnectivityPHR is configured, as a result of logical channel prioritization:

– if extendedPHR is configured:

– for each activated Serving Cell with configured uplink:

– obtain the value of the Type 1 power headroom;

– if the MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the PCell;

– obtain the value for the corresponding P_CMAX,c field from the physical layer (see subclause 5.1.1.2 of [2]);

– instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element as defined in subclause 6.1.3.6a based on the values reported by the physical layer;

– else if dualConnectivityPHR is configured:

– for each activated Serving Cell with configured uplink associated with any MAC entity:

– obtain the value of the Type 1 power headroom;

– if this MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI or if the other MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI and phr-ModeOtherCG is set to real by upper layers:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the SpCell;

– obtain the value for the corresponding P_CMAX,c field for the SpCell from the physical layer (see subclause 5.1.1.2 of [2]);

– obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity;

– if phr-ModeOtherCG is set to real by upper layers:

– obtain the value for the corresponding P_CMAX,c field for the SpCell of the other MAC entity from the physical layer (see subclause 5.1.1.2 of [2]);

– instruct the Multiplexing and Assembly procedure to generate and transmit a Dual Connectivity PHR MAC control element as defined in subclause 6.1.3.6b based on the values reported by the physical layer;

– else:

– obtain the value of the Type 1 power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element as defined in subclause 6.1.3.6 based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6b]

The Dual Connectivity Power Headroom Report (PHR) MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6b-1. When Type 2 PH is reported for the PCell, the octet containing the Type 2 PH field is included first after the octet indicating the presence of PH per cell (PSCell and all SCells of all MAC entities) and followed by an octet containing the associated P_CMAX,c field (if reported). Then after that, when Type 2 PH is reported for the PSCell, the octet containing the Type 2 PH field is included followed by an octet containing the associated P_CMAX,c field (if reported). Then follows in ascending order based on the ServCellIndex [8] an octet with the Type 1 PH field and an octet with the associated P_CMAX,c field (if reported), for the PCell and for all other serving cells of all MAC entities indicated in the bitmap.

The Dual Connectivity PHR MAC Control Element is defined as follows:

– C_i: this field indicates the presence of a PH field for the serving cell of any MAC entity, except the PCell, with SCellIndex i as specified in [8]. The C_i field set to "1" indicates that a PH field for the serving cell with SCellIndex i is reported. The C_i field set to "0" indicates that a PH field for the serving cell with SCellIndex i is not reported;

– R: reserved bit, set to "0";

– V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used. Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the octet containing the associated P_CMAX,cfield, and V=1 indicates that the octet containing the associated P_CMAX,cfield is omitted;

– Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [9]);

– P: this field indicates whether power backoff due to power management is applied (as allowed by P-MPR_c [10]). The MAC entity shall set P=1 if the corresponding P_CMAX,c field would have had a different value if no power backoff due to power management had been applied;

Figure 6.1.3.6b-1: Dual Connectivity PHR MAC Control Element

[TS 36.321, clause 6.2.1]

The MAC header is of variable size and consists of the following fields:

– F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements. The size of the F field is 1 bit. If the size of the MAC SDU or variable-sized MAC control element is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1;

– R: Reserved bit, set to "0".

The MAC header and subheaders are octet aligned.

Table 6.2.1-1: Values of LCID for DL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011-11001	Reserved
11010	Long DRX Command
11011	Activation/Deactivation
11100	UE Contention Resolution Identity
11101	Timing Advance Command
11110	DRX Command
11111	Padding

Table 6.2.1-2: Values of LCID for UL-SCH

Index	LCID values
00000	CCCH
00001-01010	Identity of the logical channel
01011	CCCH
01100-10101	Reserved
10110	Truncated Sidelink BSR
10111	Sidelink BSR
11000	Dual Connectivity Power Headroom Report
11001	Extended Power Headroom Report
11010	Power Headroom Report
11011	C-RNTI
11100	Truncated BSR
11101	Short BSR
11110	Long BSR
11111	Padding

Table 6.2.1-3: Values of F field

Index	Size of Length field (in bits)
0	7
1	15

Table 6.2.1-4: Values of LCID for MCH

Index	LCID values
00000	MCCH (see note)
00001-11100	MTCH
11101	Reserved
11110	MCH Scheduling Information or Extended MCH Scheduling Information
11111	Padding
NOTE: If there is no MCCH on MCH, an MTCH could use this value.

7.1.4.27.1.3 Test description

7.1.4.27.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

Preamble:

– The UE is in state DC MCG/SCG Dedicated RB established (state 5A) on Cell 1 and Cell 10 according to [18]

7.1.4.27.1.3.2 Test procedure sequence

Table 7.1.4.27.1.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions after preamble. Subsequent configurations marked “T1”, “T2” etc are applied at the points indicated in the Main behaviour description in Table 7.1.4.27.1.3.2-1. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS36.508 Table 6.2.2.1-1.

Table 7.1.4.27.1.3.2-0: Cell configuration changes over time

	Parameter	Unit	Cell 1	Cell 10	Remarks
T0	Cell-specific RS EPRE	dBm/15kHz	-82	-82
T1	Cell-specific RS EPRE	dBm/15kHz	-89	-82
T2	Cell-specific RS EPRE	dBm/15kHz	-82	-82
T3	Cell-specific RS EPRE	dBm/15kHz	-82	-89
T4	Cell-specific RS EPRE	dBm/15kHz	-82	-82

Table 7.1.4.27.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS is configured for Uplink Grant Allocation Type 2 on cell 1. SS is configured to transmit UL grant for UE at every TTI for FDD, and every 5ms in a DL subframe for TDD.	–	–	–	–
2	The SS transmits an RRCConnectionReconfiguration message to provide Dual Connectivity Power Headroom parameters	<–	RRCConnectionReconfiguration	–	–
	EXCEPTION: In parallel with step 3, UE executes parallel behaviour defined in table 7.1.4.27.1.3.2-2	–	–	–	–
3	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Dual Connectivity Power Headroom parameters	–>	RRCConnectionReconfigurationComplete	–	–
4	Check: Does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	1	P
5	Wait for T= 10% of prohibitPHR-Timer.	–	–	–	–
6	SS adjusts cell levels according to row T1 of table 7.1.4.27.1.3.2-0.	–	–	–	–
7	Check: for 80% of prohibitPHR-Timer since step 4, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	2	F
8	Check: After prohibitPHR-Timer started at step 4 expires, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	3	P
9	SS adjusts cell levels according to row T2 of table 7.1.4.27.1.3.2-0..	–	–	–	–
10	Check: for 80% of prohibitPHR-Timer since step 8, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	2	F
11	Check: after prohibitPHR-Timer after step 8, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	3	P
12	SS adjusts cell levels according to row T3 of table 7.1.4.27.1.3.2-0.	–	–	–	–
13	Check: for 80% of prohibitPHR-Timer since step 11, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	2	F
14	Check: after prohibitPHR-Timer after step 11, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	3	P
15	SS adjusts cell levels according to row T4 of table 7.1.4.27.1.3.2-0.	–	–	–	–
16	Check: for 80% of prohibitPHR-Timer since step 14, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	2	F
17	Check: after prohibitPHR-Timer after step 14, does the UE transmit a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element?	–>	MAC PDU	3	P

Table 7.1.4.27.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The UE transmits a MAC PDU containing Dual Connectivity Power Headroom MAC Control Element.	–>	MAC PDU	–	–

7.1.4.27.1.3.3 Specific message contents

Table 7.1.4.27.1.3.3-1: RRCConnectionReconfiguration (step 2, Table 7.1.4.27.1.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
explicitValue SEQUENCE {
phr-Config CHOICE {
setup SEQUENCE {
periodicPHR-Timer	infinity
prohibitPHR-Timer	sf1000
dl-PathlossChange	dB3
}
}
dualConnectivityPHR CHOICE {
setup SEQUENCE {
phr-ModeOtherCG-r12	real
}
}
}
}
}
}
}
}

7.1.4.27.2 DC power headroom reporting/ PSCell addition and DL pathloss change reporting / Split DRB

7.1.4.27.2.1 Test Purpose (TP)

(1)

with { UE in connected mode on a PCell }

ensure that {

when { PSCell is added with a Split bearer }

then { UE transmits a Dual Connectivity Power Headroom Report for the PCell and PSCell}

(2)

with { UE in connected mode with a Split DRB established and with UE power headroom reporting by DL_Pathloss change configured }

ensure that {

when { DL Pathloss change is triggered while prohibitPHR-Timer is running }

then { the UE does not transmit any UE Power Headroom Report }

}

(3)

with { UE in connected mode with a Split DRB established and with UE power headroom reporting by DL_Pathloss change configured }

ensure that {

when { the prohibitPHR-Timer has expired and DL Pathloss change is triggered }

then { UE transmits a Dual Connectivity Power Headroom Report }

}

7.1.4.27.2.2 Conformance requirements

Same conformance requirements as in clause 7.1.4.27.1.2

7.1.4.27.2.3 Test description

7.1.4.27.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, and Cell 10 is the PSCell.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1 and Cell 10.

UE:

Preamble:

– The UE is in state DC Split Dedicated RB established (state 5B) on Cell 1 and Cell 10 according to [18]

7.1.4.27.2.3.2 Test procedure sequence

Same test procedure sequence as in 7.1.4.27.1.3.2

7.1.4.27.2.3.3 Specific message contents

Same Specific message contents as in 7.1.4.27.1.3.3

7.1.4.28 Correct handling of UL assignment / Dynamic case / eIMTA

7.1.4.28.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eIMTA configured and SS is sending eIMTA L1 signalling on PDCCH with CRC scrambled by eIMTA-RNTI }

ensure that {

when { { UE detects a valid PDCCH UL Grant or PHICH NACK transmission in subframe m for previous PUSCH transmission }

then { UE adjusts the corresponding PUSCH transmission according to eIMTA-UL/DL-configuration }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with eIMTA configured and SS is not sending eIMTA L1 signalling on PDCCH with CRC scrambled by eIMTA-RNTI }

ensure that {

when { UE detects a valid PDCCH UL Grant or PHICH NACK transmission for previous PUSCH transmission }

then UE adjusts the corresponding PUSCH transmission according to UL/DL-configuration signalled in subframeAssignment }

}

7.1.4.28.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 10.2 and 13. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 13]

…

For each serving cell

If the UE is not configured with the higher layer parameter EIMTA-MainConfigServCell-r12,

– the UE shall set the UL/DL configuration equal to the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers.

If the UE is configured by higher layers with the parameter EIMTA-MainConfigServCell-r12, then for each radio frame,

– the UE shall determine eIMTA-UL/DL-configuration as described in subclause 13.1.

– the UE shall set the UL/DL configuration for each radio frame equal to the eIMTA-UL/DL-configuration of that radio frame.

[TS 36.213, clause 13.1]

…

The subframes in which the UE monitors PDCCH with CRC scrambled by eIMTA-RNTI are configured by higher layers.

For each serving cell,

– if T= 10,

– if the UE detects PDCCH with CRC scrambled by eIMTA-RNTI in subframe 0 of a radio frame m or if the UE detects PDCCH with CRC scrambled by eIMTA-RNTI in a subframe other than subframe 0 of a radio frame m-1,

– the eIMTA-UL/DL-configuration for radio frame m is given by the UL/DL configuration indication signalled on the PDCCH as described in [4],

– the UE may assume that the same UL/DL configuration indication is indicated by PDCCH with CRC scrambled by eIMTA-RNTI in subframe 0 of radio frame m and in all the subframes other than subframe 0 of radio frame m-1 in which PDCCH with CRC scrambled by eIMTA-RNTI is monitored,

– otherwise

– the eIMTA-UL/DL-configuration for radio frame m is same as the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers;

– if T is a value other than 10,

– if the UE detects PDCCH with CRC scrambled by eIMTA-RNTI in a subframe in radio frame mT/10,

– the eIMTA-UL/DL-configuration for radio frames {mT/10+1 , mT/10+2,…. (m + 1)T/10} is given by the UL/DL configuration indication signalled on the PDCCH as described [4],

– the UE may assume that the same UL/DL configuration indication is indicated by PDCCH with CRC scrambled by eIMTA-RNTI in all the subframes of radio frame mT/10 in which PDCCH with CRC scrambled by eIMTA-RNTI is monitored,

– otherwise

– the eIMTA-UL/DL-configuration for radio frames {mT/10+1 , mT/10+2,…. (m +1) T/10} is same as the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers.

where T denotes the value of parameter eimta-CommandPeriodicity-r12.

[TS 36.213, clause 7.3.2]

For TDD and a UE not configured with the parameter EIMTA-MainConfigServCell-r12 for any serving cell, if the UE is configured with one serving cell, or if the UE is configured with more than one serving cell and the TDD UL/DL configuration of all the configured serving cells is the same, UE procedure for reporting HARQ-ACK is given in subclause 7.3.2.1.

For TDD, if a UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two configured serving cells is not the same, or if the UE is configured with the parameter EIMTA-MainConfigServCell-r12 for at least one serving cell, UE procedure for reporting HARQ-ACK is given in subclause 7.3.2.2.

[TS 36.213, clause 8.0]

…

For FDD-TDD and primary cell frame structure type 2, if a serving cell is a primary cell, the serving cell UL/DL configuration is the UL-reference UL/DL configuration for the serving cell.

…

Table 8-2: k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	4	6				4	6
1		6			4		6			4
2				4					4
3	4								4	4
4									4	4
5									4
6	7	7				7	7			5

7.1.4.28.3 Test description

7.1.4.28.3.1 Pre-test conditions

System Simulator:

– Cell 1 (TDD)

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8 [18]) using parameters as specified in Table 7.1.4.28.3.3-1 and 7.1.4.28.3.3-2.

UE:

None.

Preamble:

– The generic procedure to get UE in test state Loopback Activated (State 4) according to TS 36.508 clause 4.5 is executed, with all the parameters as specified in the procedure except that the RLC SDU size is set to return no data in uplink.

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

7.1.4.28.3.2 Test procedure sequence

Table 7.1.4.28.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a valid MAC PDU containing RLC PDU.	<–	MAC PDU	–	–
–	EXCEPTION: Step 2 runs in parallel with behaviour in table 7.1.4.28.3.2-2	–	–	–	–
2	SS is configured to transmits eIMTA L1 signalling on PDCCH with CRC scrambled by eIMTA-RNTI, on subframe 0 in every radio frame mT/10, where eIMTA-RNTI and T is signalled in preamble step 8	–	–	–	–
3	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI on subframe 3 in radio frame N.	<–	Uplink Grant	–	–
4	Check: Does the UE transmit a MAC PDU including one RLC SDU on the following subframe 7 in radio frame N?	–>	MAC PDU	1	P
5	The SS transmits a ACK in on subframe 1 in the radio frame N+1.	<–	HARQ ACK	–	–
6	The SS transmits a NACK in on subframe 3 in the radio frame N+1.	<–	HARQ NACK	–	–
7	Check: Does the UE retransmit the MAC PDU on subframe 7 in the radio frame N+1?	–>	MAC PDU	1	P
8	The SS transmits a ACK in on subframe 3 in the radio frame N+2.	<–	HARQ ACK	–	–
9	SS stops transmitting eIMTA L1 signalling on PDCCH.	–	–	–	–
10	The SS transmits a valid MAC PDU containing RLC PDU.	<–	MAC PDU	–	–
11	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
12	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI on subframe 9 in radio frame M.	<–	Uplink Grant	–	–
13	Check: Does the UE transmit a MAC PDU including one RLC SDU on the following subframe 3 in radio frame M+1?	–>	MAC PDU	2	P
14	The SS transmits a ACK in on subframe 9 in the radio frame M+1.	<–	HARQ ACK	–	–

Table 7.1.4.28.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a Scheduling Request.	–>	(SR)	–	–

7.1.4.28.3.3 Specific Message Contents

Table 7.1.4.28.3.3-1: MAC-MainConfig-RBC (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
timeAlignmentTimerDedicated	Infinity
}

Table 7.1.4.28.3.3-2: PhysicalConfigDedicated (Preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.8.2, Table 4.8.2.1.6-1A PhysicalConfigDedicated-eIMTA

7.1.4.28a CA / Correct handling of UL assignment / Dynamic case / eIMTA / Inter-band CA

7.1.4.28a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eIMTA configured and SCell activated and SS is sending eIMTA L1 signalling for SCell on PDCCH with CRC scrambled by eIMTA-RNTI }

ensure that {

when { { UE detects a valid PDCCH UL Grant or PHICH NACK transmission in subframe m for previous PUSCH transmission }

then { UE adjusts the corresponding PUSCH transmission according to eIMTA-UL/DL-configuration }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with eIMTA configured and SCell activated and SS is not sending eIMTA L1 signalling for SCell on PDCCH with CRC scrambled by eIMTA-RNTI }

ensure that {

when { UE detects a valid PDCCH UL Grant or PHICH NACK transmission for previous PUSCH transmission }

then { UE adjusts the corresponding PUSCH transmission according to UL/DL-configuration signalled in subframeAssignment }

}

7.1.4.28a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 8 and 13. Unless otherwise stated these are Rel-12 requirements.

[TS 36.213, clause 13]

…

For each serving cell

If the UE is not configured with the higher layer parameter EIMTA-MainConfigServCell-r12,

– the UE shall set the UL/DL configuration equal to the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers.

If the UE is configured by higher layers with the parameter EIMTA-MainConfigServCell-r12, then for each radio frame,

– the UE shall determine eIMTA-UL/DL-configuration as described in subclause 13.1.

– the UE shall set the UL/DL configuration for each radio frame equal to the eIMTA-UL/DL-configuration of that radio frame.

[TS 36.213, clause 13.1]

…

The subframes in which the UE monitors PDCCH with CRC scrambled by eIMTA-RNTI are configured by higher layers.

For each serving cell,

– if T= 10,

– the eIMTA-UL/DL-configuration for radio frame m is given by the UL/DL configuration indication signalled on the PDCCH as described in [4],

– otherwise

– the eIMTA-UL/DL-configuration for radio frame m is same as the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers;

– if T is a value other than 10,

– if the UE detects PDCCH with CRC scrambled by eIMTA-RNTI in a subframe in radio frame mT/10,

– the eIMTA-UL/DL-configuration for radio frames {mT/10+1 , mT/10+2,…. (m + 1)T/10} is given by the UL/DL configuration indication signalled on the PDCCH as described [4],

– otherwise

– the eIMTA-UL/DL-configuration for radio frames {mT/10+1 , mT/10+2,…. (m +1) T/10} is same as the UL/DL configuration (i.e., the parameter subframeAssignment) indicated by higher layers.

where T denotes the value of parameter eimta-CommandPeriodicity-r12.

[TS 36.213, clause 7.3.2]

[TS 36.213, clause 8.0]

The term “UL/DL configuration” in this subclause refers to the higher layer parameter subframeAssignment unless specified otherwise.

…

For TDD, if a UE is configured with the parameter EIMTA-MainConfigServCell-r12 for at least one serving cell, if the UE is configured with one serving cell or if the UE is configured with more than one serving cell and the TDD UL/DL configuration of all the configured serving cells is the same, then for a given serving cell, the serving cell UL/DL configuration is the UL-reference UL/DL configuration.

For TDD, if a UE is configured with more than one serving cell and if the UL/DL configurations of at least two serving cells are different, if the serving cell is a primary cell or if the UE is not configured to monitor PDCCH/EPDCCH in another serving cell for scheduling the serving cell, the serving cell UL/DL configuration is the UL-reference UL/DL configuration.

For TDD, if a UE is configured with more than one serving cell and if the UL/DL configurations of at least two serving cells are different and if the serving cell is a secondary cell and if the UE is configured to monitor PDCCH/EPDCCH in another serving cell for scheduling the serving cell, then for the serving cell, the UL reference UL/DL configuration is given in Table 8-0A corresponding to the pair formed by (other serving cell UL/DL configuration, serving cell UL/DL configuration).

…

Table 8-0A: UL-reference UL/DL Configuration for serving cell based on the pair formed by (other serving cell UL/DL configuration, serving cell UL/DL configuration)

Set #	(other serving cell UL/DL configuration, serving cell UL/DL configuration)	UL-reference UL/DL configuration
Set 1	(1,1),(1,2),(1,4),(1,5)	1
	(2,2),(2,5)	2
	(3,3),(3,4),(3,5)	3
	(4,4),(4,5)	4
	(5,5)	5
Set 2	(1,0),(2,0),(3,0),(4,0),(5,0)	0
	(2,1),(4,1),(5,1)	1
	(5,2)	2
	(4,3),(5,3)	3
	(5,4)	4
	(1,6),(2,6),(3,6),(4,6),(5,6)	6
Set 3	(3,1)	1
	(3,2),(4,2)	2
	(1,3),(2,3)	3
	(2,4)	4
Set 4	(0,0),(6,0)	0
	(0,1),(0,2),(0,4),(0,5),(6,1),(6,2),(6,5)	1
	(0,3),(6,3)	3
	(6,4)	4
	(0,6),(6,6)	6

If a UE is configured with the parameter EIMTA-MainConfigServCell-r12 for a serving cell, for a radio frame of the serving cell, PUSCH transmissions can occur only in subframes that are indicated by eIMTA-UL/DL-configuration as uplink subframe(s) for the serving cell unless specified otherwise.

[TS 36.213, clause 8.3]

…

For TDD, if a UE is configured with more than one serving cell and the TDD UL/DL configuration of at least two configured serving cells is not the same, or if the UE is configured with EIMTA-MainConfigServCell-r12 for at least one serving cell, or FDD-TDD and serving cell is frame structure type 2,

– For serving cell with an UL-reference UL/DL configuration (defined in subclause 8.0) belonging to {1,2,3,4,5,6}, an HARQ-ACK received on the PHICH assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-k for the serving cell as indicated by the following Table 8.3-1, where "TDD UL/DL Configuration" in Table 8.3-1 refers to the UL-reference UL/DL Configuration.

– For a serving cell with UL-reference UL/DL configuration 0 (defined in subclause 8.0), an HARQ-ACK received on the PHICH in the resource corresponding to , as defined in subclause 9.1.2, assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-k for the serving cell as indicated by the following Table 8.3-1, where "TDD UL/DL Configuration" in Table 8.3-1 refers to the UL-reference UL/DL configuration. For a serving cell with UL-reference UL/DL configuration 0, an HARQ-ACK received on the PHICH in the resource corresponding to , as defined in subclause 9.1.2, assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-6 for the serving cell.

– For FDD-TDD, if a serving cell is a secondary cell with UL-reference UL/DL configuration 0 and if the UE is configured to monitor PDCCH/EPDCCH in another serving cell with frame structure type 1 for scheduling the serving cell, for downlink subframe i, if a transport block was transmitted in the associated PUSCH subframe i-6 for the serving cell then PHICH resource corresponding to that transport block is not present in subframe i.

Table 8.3-1 k for TDD configurations 0-6

TDD UL/DL Configuration	subframe number i
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0	7	4				7	4
1		4			6		4			6
2				6					6
3	6								6	6
4									6	6
5									6
6	6	4				7	4			6

7.1.4.28a.3 Test description

7.1.4.28a.3.1 Pre-test conditions

System Simulator:

– TDD Cell 1 (PCell) and Cell 10(SCell)

– Cell 10 is an Active SCell according to [18] cl. 6.3.4

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8 [18]) using parameters as specified in Table 7.1.4.28a.3.3-1 and Table 7.1.4.28a.3.3-2.

UE:

None.

Preamble:

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

7.1.4.28a.3.2 Test procedure sequence

In Table 7.1.4.28a.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels and other changing parameters to be applied for the cells after preamble.

Table 7.1.4.28a.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 10
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-85

Table 7.1.4.28a.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmit an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	Wait for 100ms to handle any UE messages related to the completion of the HARQ process	–	–	–	–
5	The SS transmits a valid MAC PDU containing RLC PDU on SCell Cell 10.	<–	MAC PDU (CC₂)	–	–
–	EXCEPTION: Step 6 runs in parallel with behaviour in table 7.1.4.28a.3.2-3	–	–	–	–
6	SS is configured to transmits eIMTA L1 signalling on PDCCH (UL/DL configuration indication number 2 for SCell Cell 10) with CRC scrambled by eIMTA-RNTI, on subframe 0 in every radio frame mT/10, where eIMTA-RNTI and T is signalled in preamble step 8	–	–	–	–
7	The SS allocates an UL Grant on Cell 10 sufficient for one RLC SDU to be loop backed in a TTI for SCell Cell10 on subframe 3 in radio frame N.	<–	Uplink Grant	–	–
8	Check: Does the UE transmit a MAC PDU including one RLC SDU for SCell Cell 10 on the following subframe 7 in radio frame N?	–>	MAC PDU	1	P
9	The SS transmits a ACK in on subframe 1 in the radio frame N+1.	<–	HARQ ACK	–	–
10	The SS transmits a NACK in on subframe 3 in the radio frame N+1.	<–	HARQ NACK	–	–
11	Check: Does the UE retransmit the MAC PDU SCell Cell 10 on subframe 7 in the radio frame N+1?	–>	MAC PDU	1	P
12	The SS transmits a ACK in on subframe 3 in the radio frame N+2.	<–	HARQ ACK	–	–
13	SS stops transmitting eIMTA L1 signalling on PDCCH.	–	–	–	–
14	The SS transmits a valid MAC PDU containing RLC PDU.	<–	MAC PDU	–	–
15	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
16	The SS allocates an UL Grant sufficient for one RLC SDU to be loop backed in a TTI for SCell Cell10 on subframe 9 in radio frame M.	<–	Uplink Grant	–	–
17	Check: Does the UE transmit a MAC PDU including one RLC SDU SCell Cell 10 on the following subframe 3 in radio frame M+1?	–>	MAC PDU	2	P
18	The SS transmits a ACK in on subframe 9 in the radio frame M+1.	<–	HARQ ACK	–	–

Table 7.1.4.28a.3.2-3: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a Scheduling Request.	–>	(SR)	–	–

7.1.4.28a.3.3 Specific Message Contents

Table 7.1.4.28a.3.3-1: MAC-MainConfig-RBC (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
MAC-MainConfig-RBC ::= SEQUENCE {
timeAlignmentTimerDedicated	Infinity
}

Table 7.1.4.28a.3.3-2: PhysicalConfigDedicated (Preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.8.2, Table 4.8.2.1.6-1A PhysicalConfigDedicated-eIMTA

Table 7.1.4.28a.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.4.28a.3.3-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 7.1.4.28a.3.3-4: SCellToAddMod-r10 (Table 7.1.4.28a.3.3-3)

Derivation Path: 36.508, Table 4.6.3-19D
Information Element	Value/remark	Comment	Condition
SCellToAddMod-r10 ::= SEQUENCE {
sCellIndex-r10	1
cellIdentification-r10 SEQUENCE {
physCellId-r10	PhysicalCellIdentity of Cell 10
dl-CarrierFreq-r10	Same downlink EARFCN as used for Cell 10
dl-CarrierFreq-r10	maxEARFCN		Band>64
}
dl-CarrierFreq-v1090	Same downlink EARFCN as used for Cell 10		Band>64
}

Table 7.1.4.28a.3.3-5: MAC-MainConfig-RBC (Table 7.1.4.28a.3.3-3)

Derivation Path: 36.508, Table 4.8.2.1.5, condition SCell_AddMod
Information Element	Value/remark	Comment	Condition
mac-MainConfig-v1020
mac-MainConfig-v1020SEQUENCE {
sCellDeactivationTimer-r10	rf128
}

Table 7.1.4.28a.3.3-6: RadioResourceConfigDedicatedSCell-r10 (Table 7.1.4.28a.3.3-4)

Derivation Path: 36.508 Table 4.6.3-19AA
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {
physicalConfigDedicatedSCell-r10	PhysicalConfigDedicatedSCell-r10-eIMTA
}

Table 7.1.4.28a.3.3-7: PhysicalConfigDedicatedSCell-r10-eIMTA (Table 7.1.4.28a.3.3-6)

Derivation Path: 36.508 Table 4.6.3-6B
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicatedSCell-r10-eIMTA ::= SEQUENCE {
eimta-MainConfigSCell-r12	EIMTA-MainConfigServCell-r12
}

Table 7.1.4.28a.3.3-8: EIMTA-MainConfigServCell-r12 (Table 7.1.4.28a.3.3-7)

Derivation Path: 36.508 Table 4.6.3-32, condition TDD
Information Element	Value/remark	Comment	Condition
EIMTA-MainConfigServCell-r12 ::= CHOICE {
setup SEQUENCE {
eimta-UL-DL-ConfigIndex-r12	2
}
}

7.1.4.29 CA / PUCCH SCell

7.1.4.29.1 CA / PUCCH SCell / Correct handling of MAC control information / Scheduling requests and PUCCH

7.1.4.29.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and PUCCH SCell configured and activated}

ensure that {

when { PUCCH of PCell and SCell are both configured and UE has UL data available for transmission and UE has no UL-SCH resources available and SR_COUNTER is less than dsr-TransMax }

then { the UE transmits SR on every available PUCCH of PCell and SCell until resources are granted }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and has pending SR(s) }

ensure that {

when { UE receives an UL grant for a new transmission }

then { UE cancels all pending SR(s) }

}

7.1.4.29.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.4.

[TS 36.321, clause 5.4.4]

The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.

When an SR is triggered, it shall be considered as pending until it is cancelled. All pending SR(s) shall be cancelled and sr-ProhibitTimer shall be stopped when a MAC PDU is assembled and this PDU includes a BSR which contains buffer status up to (and including) the last event that triggered a BSR (see subclause 5.4.5), or, if all pending SR(s) are triggered by Sidelink BSR, when a MAC PDU is assembled and this PDU includes a Sidelink BSR which contains buffer status up to (and including) the last event that triggered a Sidelink BSR (see subclause 5.14.1.4), or, if all pending SR(s) are triggered by Sidelink BSR, when upper layers configure autonomous resource selection, or when the UL grant(s) can accommodate all pending data available for transmission.

If an SR is triggered and there is no other SR pending, the MAC entity shall set the SR_COUNTER to 0.

As long as one SR is pending, the MAC entity shall for each TTI:

– if no UL-SCH resources are available for a transmission in this TTI:

– if the MAC entity has no valid PUCCH resource for SR configured in any TTI and if rach-Skip for the MCG MAC entity or rach-SkipSCG for the SCG MAC entity is not configured: initiate a Random Access procedure (see subclause 5.1) on the SpCell and cancel all pending SRs;

– else if the MAC entity has at least one valid PUCCH resource for SR configured for this TTI and if this TTI is not part of a measurement gap or Sidelink Discovery Gap for Transmission and if sr-ProhibitTimer is not running:

– if SR_COUNTER < dsr-TransMax:

– increment SR_COUNTER by 1;

– instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

– start the sr-ProhibitTimer.

– else:

– notify RRC to release PUCCH for all serving cells;

– notify RRC to release SRS for all serving cells;

– clear any configured downlink assignments and uplink grants;

– initiate a Random Access procedure (see subclause 5.1) on the SpCell and cancel all pending SRs.

NOTE 1: The selection of which valid PUCCH resource for SR to signal SR on when the MAC entity has more than one valid PUCCH resource for SR in one TTI is left to UE implementation.

NOTE 2: SR_COUNTER is incremented for each SR bundle. sr-ProhibitTimer is started in the first TTI of an SR bundle.

7.1.4.29.1.3 Test description

7.1.4.29.1.3.1 Pre-test conditions

System Simulator:

Cell 1 and Cell 3

Cell 3 is an Active PUCCH SCell according to [18] clause 6.3.4.

– RRC Connection Reconfiguration using parameters as specified in Table 7.1.4.29.1.3.3-1 and Table 7.1.4.29.1.3.3-2.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

Table 7.1.4.29.1.3.1-1: RLC settings

Parameter	Value
t-PollRetransmit	250 ms

7.1.4.29.1.3.2 Test procedure sequence

Table 7.1.4.29.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) addition and configured as PUCCH SCell.	<–	RRCConnection Reconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) addition.	–>	RRCConnectionReconfiguration Complete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 3).	<–	MAC PDU (Activation (C₁=1))
4	The SS transmits a MAC PDU containing 10 MAC SDUs each containing a RLC SDU	<–	MAC PDU (containing 10 MAC SDUs)	–	–
–	EXCEPTION: Step 5 runs in parallel with behaviour in table 7.1.4.29.1.3.2-2.	–	–	–	–
5	Check: Does the UE transmit 6 Scheduling Requests separately on 6 consecutively available PUCCHs on Cell1 and transmit 6 Scheduling Requests separately on 6 consecutively available PUCCHs on Cell3? (Note 1)	–>	(SR)	1	P
6	The SS is configured for Uplink Grant Allocation Type 3. The SS transmits an UL grant to allocate UL-SCH resources that are enough to transmit MAC PDU containing 10 MAC SDUs	<–	(UL Grant )	–	–
7	Check: Does the UE transmit a MAC PDU containing 10 RLC PDUs?	–>	MAC PDU (containing 10 MAC SDUs)	1	P
8	Check: For 1 second, does the UE transmit a Scheduling Request?	–>	(SR)	1,2	F
Note 1: The UE repeats the scheduling requests on every available PUCCH as long as SR_COUNTER < dsr-TransMax and there is UL data available for transmission and there are no resources available to transmit it. At the reception of first Scheduling Request from the UE, SS will be scheduled to transmit a grant after 105ms. Hence SS will receive 6 Scheduling Requests on PCell as sr-ConfigIndex = 30 and receive 6 Scheduling Requests on SCell as sr-ConfigIndex = 34.

Table 7.1.4.29.1.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
	Procedure	U – S	Message
1	Check: Does the UE transmit a MAC PDU?	–>	MAC PDU	1	F

7.1.4.29.1.3.3 Specific Message Contents

Table 7.1.4.29.1.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration (Preamble)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Config-DEFAULT::= CHOICE {
enable SEQUENCE {
dsr-TransMax	n64
}
}

Table 7.1.4.29.1.3.3-2: SchedulingRequestConfigSCell-r13 to be used in RRCConnectionReconfiguration (Preamble)

Derivation Path: 36.508 clause 4.6.3-20B
Information Element	Value/remark	Comment	Condition
SchedulingRequestConfigSCell-r13::= CHOICE {
enable SEQUENCE {
sr-ConfigIndex-r13	34		FDD
sr-ConfigIndex-r13	31		TDD
dsr-TransMax-r13	n64
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment

Table 7.1.4.29.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 7.1.4.29.1.3.2-1)

Derivation path: 36.508 table 4.6.1-8, condition SCell_AddMod

Table 7.1.4.29.1.3.3-4: PhysicalConfigDedicatedSCell-r10-DEFAULT (step 1, Table 7.1.4.29.1.3.2-1)

Derivation path: 36.508 table 4.6.3-6A, condition PUCCH-SCell

7.1.4.29.2 CA / PUCCH SCell / UE power headroom reporting / Periodic reporting

7.1.4.29.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic reporting of type 2 power headroom configured, and PUCCH SCell configured and activated }

ensure that {

when { periodicPHR-Timer is configured in RRCConnectionReconfiguration procedure }

then { UE transmits a MAC PDU containing Extended PHR MAC Control Element supporting PUCCH on SCell }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic reporting of type 2 power headroom configured, and PUCCH SCell configured and activated }

ensure that {

when { periodicPHR-Timer expires and UL resources allocated for new transmission }

then { UE transmits a MAC PDU containing Extended PHR MAC Control Element supporting PUCCH on SCell }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state with DRB established, periodic reporting of type 2 power headroom configured, and PUCCH SCell configured and activated }

ensure that {

when { extendedPHR2 is released }

then { UE stops transmitting Extended PHR MAC Control Element supporting PUCCH on SCell }

}

7.1.4.29.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.321 clause 5.4.6 and TS 36.321 clause 6.1.3.6a.

[TS 36.321, clause 5.4.6]

The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated Serving Cell and also with information about the difference between the nominal UE maximum power and the estimated power for UL-SCH and PUCCH transmission on SpCell and PUCCH SCell.

A Power Headroom Report (PHR) shall be triggered if any of the following events occur:

– periodicPHR-Timer expires;

– upon configuration or reconfiguration of the power headroom reporting functionality by upper layers [8], which is not used to disable the function;

– activation of an SCell of any MAC entity with configured uplink;

– addition of the PSCell;

– there are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and the required power backoff due to power management (as allowed by P-MPR_c [10]) for this cell has changed more than dl-PathlossChange dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH transmission on this cell.

If the MAC entity has UL resources allocated for new transmission for this TTI the MAC entity shall:

– if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer;

– if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled, and;

– if the allocated UL resources can accommodate the MAC control element for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization:

– if extendedPHR is configured:

– for each activated Serving Cell with configured uplink:

– obtain the value of the Type 1 power headroom;

– if the MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the PCell;

– obtain the value for the corresponding P_CMAX,c field from the physical layer (see subclause 5.1.1.2 of [2]);

– instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element for extendedPHR as defined in subclause 6.1.3.6a based on the values reported by the physical layer;

– else if extendedPHR2 is configured:

– for each activated Serving Cell with configured uplink:

– obtain the value of the Type 1 power headroom;

– if the MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI:

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if a PUCCH SCell is configured and activated:

– obtain the value of the Type 2 power headroom for the PCell and PUCCH SCell;

– obtain the values for the corresponding P_CMAX,c fields from the physical layer (see subclause 5.1.1.2 of [2]);

– else:

– if simultaneousPUCCH-PUSCH is configured for the PCell:

– obtain the value of the Type 2 power headroom for the PCell;

– obtain the value for the corresponding P_CMAX,c field from the physical layer (see subclause 5.1.1.2 of [2]);

– instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element for extendedPHR2 according to configured ServCellIndex and the PUCCH(s) for the MAC entity as defined in subclause 6.1.3.6a based on the values reported by the physical layer;

– else if dualConnectivityPHR is configured:

– for each activated Serving Cell with configured uplink associated with any MAC entity:

– obtain the value of the Type 1 power headroom;

– obtain the value for the corresponding P_CMAX,c field from the physical layer;

– if simultaneousPUCCH-PUSCH is configured:

– obtain the value of the Type 2 power headroom for the SpCell;

– obtain the value for the corresponding P_CMAX,c field for the SpCell from the physical layer (see subclause 5.1.1.2 of [2]);

– obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity;

– if phr-ModeOtherCG is set to real by upper layers:

– obtain the value for the corresponding P_CMAX,c field for the SpCell of the other MAC entity from the physical layer (see subclause 5.1.1.2 of [2]);

– else:

– obtain the value of the Type 1 power headroom from the physical layer;

– instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element as defined in subclause 6.1.3.6 based on the value reported by the physical layer;

– start or restart periodicPHR-Timer;

– start or restart prohibitPHR-Timer;

– cancel all triggered PHR(s).

[TS 36.321, clause 6.1.3.6a]

For extendedPHR2, the Extended Power Headroom Report (PHR) MAC control elements are identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. They have variable sizes and are defined in Figure 6.1.3.6a-3, Figure 6.1.3.6a-4 and Figure 6.1.3.6a-5. One octet with C fields is used for indicating the presence of PH per SCell when the highest SCellIndex of SCell with configured uplink is less than 8, otherwise four octets are used. When Type 2 PH is reported for the PCell, the octet containing the Type 2 PH field is included first after the octet(s) indicating the presence of PH per SCell and followed by an octet containing the associated P_CMAX,c field (if reported). Then follows the Type 2 PH field for the PUCCH SCell (if PUCCH on SCell is configured and Type 2 PH is reported for the PUCCH SCell), followed by an octet containing the associated P_CMAX,c field (if reported). Then follows in ascending order based on the ServCellIndex [8] an octet with the Type 1 PH field and an octet with the associated P_CMAX,c field (if reported), for the PCell and for each SCell indicated in the bitmap.

The Extended PHR MAC Control Elements are defined as follows:

– R: reserved bit, set to "0";

– V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH and V=1 indicates that a PUCCH reference format is used. Furthermore, for both Type 1 and Type 2 PH, V=0 indicates the presence of the octet containing the associated P_CMAX,cfield, and V=1 indicates that the octet containing the associated P_CMAX,cfield is omitted;

– Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB can be found in subclause 9.1.8.4 of [9]);

– P: this field indicates whether the MAC entity applies power backoff due to power management (as allowed by P-MPR_c [10]). The MAC entity shall set P=1 if the corresponding P_CMAX,c field would have had a different value if no power backoff due to power management had been applied;

Figure 6.1.3.6a-1: Void

Figure 6.1.3.6a-2: Extended PHR MAC Control Element

Figure 6.1.3.6a1-3: Extended PHR MAC Control Element supporting PUCCH on SCell

Figure 6.1.3.6a2-4: Extended PHR MAC Control Element supporting 32 serving cells with configured uplink

Figure 6.1.3.6a3-5: Extended PHR MAC Control Element supporting 32 serving cells with configured uplink and PUCCH on SCell

Table 6.1.3.6a-1: Nominal UE transmit power level for Extended PHR and for Dual Connectivity PHR

P_CMAX,c	Nominal UE transmit power level
0	PCMAX_C_00
1	PCMAX_C_01
2	PCMAX_C_02
…	…
61	PCMAX_C_61
62	PCMAX_C_62
63	PCMAX_C_63

7.1.4.29.2.3 Test description

7.1.4.29.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3

– Cell 3 is an Active PUCCH SCell according to [18] cl. 6.3.4.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

7.1.4.29.2.3.2 Test procedure sequence

Table 7.1.4.29.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRCConnectionReconfiguration message with SCell (Cell 3) addition and configured as PUCCH SCell	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message to confirm SCell (Cell 3) addition.	–>	RRCConnectionReconfiguration Complete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 3).	<–	MAC PDU (Activation (C₁=1))
4	The SS is configured for Uplink Grant Allocation Type 2. The SS transmits UL grant to the UE at every 10ms in a DL subframe. (Note 1)	<–	(UL grant)	–	–
5	The SS transmits an RRCConnectionReconfiguration message to provide Extended Power Headroom parameters and extendedPHR2 is configured	<–	RRCConnectionReconfiguration	–	–
6	Check: does the UE transmit a MAC PDU containing type2 Power Headroom MAC Control Element of PCell and PUCCH SCell? (Note 2)	–>	MAC PDU	1	P
7	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of Extended Power Headroom parameters. (Note 2)	–>	RRCConnectionReconfiguration Complete	–	–
8	Check: does the UE transmit a MAC PDU containing type2 Power Headroom MAC Control Element of PCell and PUCCH SCell 200ms after step 6?	–>	MAC PDU	2	P
9	The SS transmits an RRCConnectionReconfiguration message to release extendedPHR2	<–	RRCConnectionReconfiguration	–	–
10	The UE transmits an RRCConnectionReconfigurationComplete message to confirm the disabling of Extended Power Headroom parameters	–>	RRCConnectionReconfiguration Complete	–	–
11	Check: for 2 seconds, does the UE transmit a MAC PDU containing type2 Power Headroom MAC Control Element of PCell and PUCCH SCell?	–>	MAC PDU	3	F
Note 1: The SS transmits UL grant to the UE at every 10 ms to provide the necessary time division of the UE DL receptions and UL transmissions for UE operating in FDD type B half-duplex mode. See TS 36.523-3 sub-clause 7.26 for scheduling pattern for type B half-duplex FDD UE. Note 2: Steps 6 and 7 can happen in 2 MAC PDU’s, or may be combined in one MAC PDU.

7.1.4.29.2.3.3 Specific Message Contents

Table 7.1.4.29.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 7.1.4.29.2.3.2-1)

Derivation path: 36.508 table 4.6.1-8, condition SCell_AddMod

Table 7.1.4.29.2.3.3-2: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 7.1.4.29.2.3.3-1)

Derivation path: 36.508 table 4.6.3-6A, condition PUCCH-SCell

Table 7.1.4.29.2.3.3-3: RRCConnectionReconfiguration (step 5, Table 7.1.4.29.2.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
phr-Confign CHOICE {
setup SEQUENCE {
periodicPHR-Timer	sf200
prohibitPHR-Timer	sf1000
dl-PathlossChange	infinity
}
}
extendedPHR2-r13	true
}
}
}
}
}
}

Table 7.1.4.29.2.3.3-4: RRCConnectionReconfiguration (step 9, Table 7.1.4.29.2.3.2-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
extendedPHR2-r13	false
}
}
}
}
}
}

7.1.4.30 Void

7.1.4.31 eLAA / Logical channel prioritization handling / laa-UL-Allowed

7.1.4.31.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated }

ensure that {

when { UL data arrives in the UE transmission buffer and grant is received only on eLAA cell }

then { UE transmits the data from the logical channel which is set to laa-UL-Allowed to True via eLAA SCells }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated }

ensure that {

when { UL data arrives in the UE transmission buffer and grant is received on Pcell }

then { UE transmits the data from the logical channel which is set to laa-UL-Allowed to true via Pcell }

}

7.1.4.31.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 6.3.2 and TS36.321 clauses 5.4.3.1

[TS 36.331 clause 5.2.2.7]

laa-UL-Allowed

Indicates whether the data of a logical channel is allowed to be transmitted via UL of LAA SCells. Value TRUE indicates that the logical channel is allowed to be sent via UL of LAA SCells. Value FALSE indicates that the logical channel is not allowed to be sent via UL of LAA SCells.

[TS 36.321 clause 5.4.3.1]

The Logical Channel Prioritization procedure is applied when a new transmission is performed.

…

– for transmissions on serving cells operating according to Frame Structure Type 3, the MAC entity shall only consider logical channels for which laa-UL-Allowed has been configured.

7.1.4.31.3 Test description

7.1.4.31.3.1 Pre-test conditions

System Simulator:

Cell 1 (PCell) and Cell 10 (SCell)
Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(2,0) is used for step 8 in 4.5.3A.3 according to [18].

– 2 AM DRBS are configured with the parameters specified in table 7.1.4.31.3.1-1.

Table 7.1.4.31.3.1-1: Logical Channel Configuration Settings

Parameter	DRB1	DRB2
LogicalChannel-Identity	3	4
Priority	7	6
prioritizedBitRate	0kbs	0kbs
logicalChannelGroup	2 (LCG ID#2)	2 (LCG ID#2)
laa-UL-Allowed	True	False

7.1.4.31.3.2 Test procedure sequence

Table 7.1.4.31.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmit an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU (containing an RLC PDU)	<–	MAC PDU (CC₁, RLC SDU on LC3)	–
5	The SS indicates a new transmission on PDCCH of CC₁ (Cell 1) and transmits a MAC PDU (containing an RLC PDU)	<–	MAC PDU (CC₁, RLC SDU on LC4)	–
6	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
7	The SS sends an UL grant suitable for transmitting loop back PDU on Cell 10.	<–	(UL Grant)	–	–
	EXCEPTION: Step 8 and 9 runs in parallel with behaviour in table 7.1.4.21.3.2-2
8	Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 4?	–>	MAC PDU (CC_2,RLC SDU on LC3)	P	1
9	Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 5?	–>	MAC PDU (CC_2,RLC SDU on LC4)	F	1
10	The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1.	<–	(UL Grant)	–	–
11	Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 5?	–>	MAC PDU (CC_1,RLC SDU on LC4)	P	1
12	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU (containing an RLC PDU)	<–	MAC PDU (CC₁, RLC SDU on LC3)	–
13	The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1.	<–	(UL Grant)	–	–
14	Check: Does the UE transmit a MAC PDU containing the loop back PDU corresponding to step 12?	–>	MAC PDU (CC_1,RLC SDU on LC3)	P	2

Table 7.1.4.31.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a Scheduling Request.	–>	(SR)	–	–

7.1.4.31.3.3 Specific message contents

Table 7.1.4.31.3.3-1: SchedulingRequest-Configuration to be used in RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 clause 4.6.3-20
Information Element	Value/remark	Comment	Condition
SchedulingRequest-Configuration ::= CHOICE {
setup SEQUENCE {
dsr-TransMax	n16
}
}

Table 7.1.4.31.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.31.3.3-3: RRCConnectionReconfiguration (Step 1, Table 7.1.4.31.3.2-1)

Derivation Path: 36.331 clause 6.2.2
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
rrc-TransactionIdentifier	RRC-TransactionIdentifier-DL
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
measConfig	Not present
mobilityControlInfo	Not present
dedicatedInfoNASList	Not present
radioResourceConfigDedicated	RadioResourceConfigDedicated-DEFAULT
securityConfigHO	Not present
nonCriticalExtension
nonCriticalExtension
nonCriticalExtension
sCellToAddModList-r10 SEQUENCE (SIZE (1..maxSCell-r10)) OF	1 entry
SCellToAddMod-r10[1]	SCellToAddMod-r10
}
}
}
}
}
}
}

Table 7.1.4.31.3.3-4: RadioResourceConfigDedicated-DEFAULT (Table 7.1.4.31.3.3-3)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-DEFAULT ::= SEQUENCE {
srb-ToAddModList	Not present
drb-ToAddModList	Not present
drb-ToReleaseList	Not present
mac-MainConfig	Not present
sps-Config	Not present
physicalConfigDedicated	PhysicalConfigDedicated -DEFAULT
}

Table 7.1.4.31.3.3-5: SCellToAddMod-r10 (Table 7.1.4.31.3.3-3)

Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D and Table 4.6.3-19AA
Information Element	Value/remark	Comment	Condition
SCellToAddMod-r10 ::= SEQUENCE {
sCellIndex-r10	1
cellIdentification-r10 SEQUENCE {
physCellId-r10	PhysicalCellIdentity of Cell 10
dl-CarrierFreq-r10	Same downlink EARFCN as used for Cell 10
dl-CarrierFreq-r10	maxEARFCN		Band > 64
}
radioResourceConfigDedicatedSCell-r10 SEQUENCE {
physicalConfigDedicatedScell-r10	PhysicalConfigDedicatedSCell-r10-DEFAULT		LAA, eLAA
}
dl-CarrierFreq-v1090	Same downlink EARFCN as used for Cell 10		Band > 64
}

Table 7.1.4.31.3.3-6: PhysicalConfigDedicated-DEFAULT (Table 7.1.4.31.3.3-4)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pucch-ConfigDedicated-v1020	PUCCH-ConfigDedicated-v1020-DEFAULT		2TX AND FDD, TDD
pucch-ConfigDedicated-v1130	PUCCH-ConfigDedicated-v1130
pusch-ConfigDedicated-v1130	Not present
uplinkPowerControlDedicated-v1130	Not present
}
Note: All other IE’s are not present

Table 7.1.4.31.3.3-7: PUCCH-ConfigDedicated-v1130 (Table 7.1.4.31.3.3-6)

Derivation Path: 36.508 clause 4.6.3-9AA
Information Element	Value/remark	Comment	Condition
PUCCH-ConfigDedicated-v1130 ::= SEQUENCE {
n1PUCCH-AN-CS-v1130 CHOICE {
setup SEQUENCE {	2 entries
n1PUCCH-AN-CS-ListP1-r11[1]	2
n1PUCCH-AN-CS-ListP1-r11[2]	2
}
}
nPUCCH-Param-r11 CHOICE {
setup SEQUENCE {
nPUCCH-Identity-r11	1
n1PUCCH-AN-r11	2
}
}
}

7.1.4.32 eLAA / SCell PUSCH / Correct handling of UL assignment

7.1.4.32.0 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 8.0, clause 13A, [36.331 Clause 6.3.6]

[36.213 Clause 8.0]

For a serving cell that is a LAA SCell, a UE shall

– upon detection of an PDCCH/ EPDCCH with DCI format 0A/0B/4A/4B and with ‘PUSCH trigger A’ field set to ‘0’ in subframe n intended for the UE, or

– upon detection of PDCCH/ EPDCCH with DCI format 0A/0B/4A/4B in subframe n–p with ‘PUSCH trigger A’ field set to ‘1’ intended for the UE for the serving cell and that has not been triggered by a ‘PUSCH trigger B’ field set to ‘1’ received prior to subframe n on the serving cell, with p>=1 and p<=v, and upon detection of PDCCH with DCI CRC scrambled by CC-RNTI and with ‘PUSCH trigger B’ field set to ‘1’ in subframe n on the serving cell

perform a corresponding PUSCH transmission, conditioned on the channel access procedures described in clause 15.2.1, in subframe(s) n+l+k+i with i = 0, 1, …, N-1 according to the PDCCH/EPDCCH and HARQ process ID , where

– N =1 for DCI format 0A/4A, and value of N is determined by the ‘number of scheduled subframes’ field in the corresponding DCI format 0B/4B.

– The UE is configured the maximum value of N by higher layer parameter maxNumberOfSchedSubframes-Format0B for DCI format 0B and higher layer parameter maxNumberOfSchedSubframes-Format4B for DCI format 4B;

– value of timing offset k is determined by the ‘Timing offset’ field in the corresponding DCI 0A/0B/4A/4B according to Table 8-2d if ‘PUSCH trigger A’ field set to ‘0’ or Table 8-2e otherwise;

– value of is determined by the HARQ process number field in the corresponding DCI format 0A/0B/4A/4B and ;

– for ‘PUSCH trigger A’ field set to ‘0’ in the corresponding DCI format 0A/0B/4A/4B,

– l = 3 if the UE is configured with higher layer parameter shortProcessingTime, and 4 otherwise

– otherwise

– value of l is the UL offset as determined by the ‘UL duration and offset’ field in the corresponding DCI with CRC scrambled by CC-RNTI according to the procedure in Subclause 13A, if ‘PUSCH trigger B’ field set to ‘1’,

– value of validation duration v is determined by the ‘Timing offset’ field in the corresponding PDCCH/ EPDCCH with DCI format 0A/0B/4A/4B according to Table 8-2f

– the smallest value of l+k supported by the UE is included in the UE-EUTRA-Capability

– the value of p+l+k is at least 3 if the UE is configured with higher layer parameter shortProcessingTime, and 4 otherwise.

Table 8-2d: Timing offset for DCI format 0A/0B/4A/4B with ‘PUSCH trigger A’ field set to ‘0’

Value of ‘Timing offset’ field
0000	0
0001	1
0010	2
0011	3
0100	4
0101	5
0110	6
0111	7
1000	8
1001	9
1010	10
1011	11
1100	12
1101	13
1110	14
1111	15

Table 8-2e: Timing offset for DCI format 0A/0B/4A/4B with ‘PUSCH trigger A’ field set to ‘1’

Value of the first two bits of ‘Timing offset’ field
00	0
01	1
10	2
11	3

Table 8-2f: Validation duration for DCI format 0A/0B/4A/4B with ‘PUSCH trigger A’ field set to ‘1’

Value of the last two bits of ‘Timing offset’ field
00	8
01	12
10	16
11	20

…

Transmission mode 1 is the default uplink transmission mode for a UE until the UE is assigned an uplink transmission mode by higher layer signalling.

When a UE configured in transmission mode 2 receives a DCI Format 0/0A/0B/0C uplink scheduling grant, it shall assume that the PUSCH transmission is associated with transport block 1 and that transport block 2 is disabled.

Table 8-3: PDCCH and PUSCH configured by C-RNTI

Transmission mode	DCI format	Search Space	Transmission scheme of PUSCH corresponding to PDCCH
Mode 1	DCI format 0	Common and UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
Mode 1	DCI format 0A or 0B or 0C or 7-0A	UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
Mode 2	DCI format 0	Common and UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
	DCI format 0A or 0B or 0C	UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
	DCI format 4 or 4A or 4B or 7-0B	UE specific by C-RNTI	Closed-loop spatial multiplexing (see Subclause 8.0.2)

Table 8-3A: EPDCCH and PUSCH configured by C-RNTI

Transmission mode	DCI format	Search Space	Transmission scheme of PUSCH corresponding to EPDCCH
Mode 1	DCI format 0 or 0A or 0B or 0C	UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
Mode 2	DCI format 0 or 0A or 0B or 0C	UE specific by C-RNTI	Single-antenna port, port 10 (see Subclause 8.0.1)
Mode 2	DCI format 4 or 4A or 4B	UE specific by C-RNTI	Closed-loop spatial multiplexing (see Subclause 8.0.2)

[36.213 Clause 13A]

If a UE is configured with a LAA SCell for UL transmissions, and the UE detects PDCCH with DCI CRC scrambled by CC-RNTI in subframe n, the UE may be configured with a ‘UL duration’ and ‘UL offset’ for subframe n according to the ‘UL duration and offset’ field in the detected DCI. The ‘UL duration and offset’ field indicates the ‘UL duration’ and ‘UL offset’ according to Table 13A-2.

If the ‘UL duration and offset’ field configures an ‘UL offset’ and an ‘UL duration’ for subframe n, the UE is not required to receive any downlink physical channels and/or physical signals in subframe(s) n+l+ i with i = 0, 1, …, d-1.

Table 13A-2: UL duration and offset.

Value of ‘UL duration and offset’ field	UL offset, (in subframes)	UL duration, (in subframes)
00000	Not configured	Not configured
00001	1	1
00010	1	2
00011	1	3
00100	1	4
00101	1	5
00110	1	6
00111	2	1
01000	2	2
01001	2	3
01010	2	4
01011	2	5
01100	2	6
01101	3	1
01110	3	2
01111	3	3
10000	3	4
10001	3	5
10010	3	6
10011	4	1
10100	4	2
10101	4	3
10110	4	4
10111	4	5
11000	4	6
11001	6	1
11010	6	2
11011	6	3
11100	6	4
11101	6	5
11110	6	6
11111	reserved	reserved

[TS 36.331 Clause 6.3.6]

twoStepSchedulingTimingInfo

Presence of this field indicates that the UE supports uplink scheduling using PUSCH trigger A and PUSCH trigger B (as defined in TS 36.213 [23]).

This field also indicates the timing between the PUSCH trigger B and the earliest time the UE supports performing the associated UL transmission. For reception of PUSCH trigger B in subframe N, value nPlus1 indicates that the UE supports performing the UL transmission in subframe N+1, value nPlus2 indicates that the UE supports performing the UL transmission in subframe N+2, and so on.

This field can be included only if uplinkLAA is included.

–

7.1.4.32.1 eLAA / SCell PUSCH / Correct handling of UL assignment / DCI0A/0B / One step scheduling

7.1.4.32.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and SS is sending an eLAA SCell scheduling grant DCI 0A on PDCCH with a valid C-RNTI indicating non-triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 0A in subframe n and UE has UL data available for transmission }

then { the UE transmits a PUSCH data frame in the indicated subframe and HARQ process }

(2)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and UE is configured to monitor DCI OB and SS is sending an eLAA SCell scheduling grant DCI 0B on PDCCH with a valid C-RNTI indicating non-triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 0B in subframe n and UE has UL data available for transmission }

then { the UE transmits multiple PUSCH data frame in the indicated multiple subframes and HARQ processes }

7.1.4.32.1.2 Conformance requirements

Reference to clause 7.1.4.32.0

7.1.4.32.1.3 Test description

7.1.4.32.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 (PCell) and Cell 10 (SCell)

– Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,0) is used for step 8 in 4.5.3A.3 according to [18].

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.32.1.3.2 Test procedure sequence

Table 7.1.4.32.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing one RLC PDUs	<–	MAC PDU (CC₁)	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS sends an UL grant suitable for transmitting one RLC PDU in subframe n on Cell 10.	<–	UL Grant (DCI Format 0A: HARQ PROCESS ID = X, New data indicator = 0)	–	–
7	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 4 in HARQ process X in subframe n+4 on Cell 10.	–>	MAC PDU (CC₂)	P	1
8	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing four RLC PDUs	<–	MAC PDU (CC₁)
9	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
10	The SS sends an UL grant suitable for transmitting one RLC PDU in subframe n on Cell 10.	<–	(UL Grant (DCI Formant 0B, Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = 1))	–	–
11	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 8 in HARQ process X in subframe n+4 on Cell 10?	–>	MAC PDU(CC₂)	P	2
12	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 8 in HARQ process mod(X+1, 16) in subframe n+5 on Cell 10?	–>	MAC PDU(CC₂)	P	2
13	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 8 in HARQ process mod(X+2, 16) in subframe n+6 on Cell 10?	–>	MAC PDU(CC₂)	P	2
14	Check: Does the UE transmit a MAC PDU containing one loop back PDU corresponding to step 8 in HARQ process mod(X+3, 16) in subframe n+7 on Cell 10?	–>	MAC PDU(CC₂)	P	2
Note 1: The default setting of DCI format 0A and 0B refers to TS 36.508 clause 4.3.6 with exception specified in the table 7.1.4.32.1.3.2-1.

7.1.4.32.1.3.3 Specific message contents

Table 7.1.4.32.1.3.3-1: RRCConnectionReconfiguration (step1, Table 7.1.4.32.1.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8 Condition SCell_AddMod

Table 7.1.4.32.1.3.3-2: RadioResourceConfigDedicated-SCell_AddMod (Table 7.1.4.32.1.3.3-1)

Derivation Path: 36.508 Table 4.6.3-19AAA
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE {
drb-ToAddModList::= SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {	1 Entry
drb-Identity[1]	1
logicalChannelIdentity[1]	3
logicalChannelConfig[1] ::= SEQUENCE {
laa-UL-Allowed-r14	True
}
}
}

Table 7.1.4.32.1.3.3-3: SCellToAddMod-r10 (Table 7.1.4.32.1.3.3-1)

Derivation Path: 36.508 Table 4.6.3-19D

Table 7.1.4.32.1.3.3-4: RadioResourceConfigDedicatedSCell-r10 (Table 7.1.4.32.1.3.3-3)

Derivation Path: 36.508 Table 4.6.3-19AA

Table 7.1.4.32.1.3.3-5: PhysicalConfigDedicatedSCell-r10 (Table 7.1.4.32.1.3.3-4)

Derivation Path:TS 36.508 Table 4.6.3-6A
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicatedSCell-r10 ::= SEQUENCE {
ul-Configuration-r10 SEQUENCE {
antennaInfoUL-r10 SEQUENCE {
transmissionModeUL-r10	tm1
}
}
laa-ScellConfiguration-r13 SEQUENCE {
subframeStartPosition	‘s0’
laa-SCellSubframeConfig	‘00000000’
}
laa-SCellConfiguration-v1430 SEQUENCE {
pdcch-ConfigLAA-r14 SEQUENCE {
maxNumberOfSchedSubframes-Format0B-r14	sf4	Enable DCI format 0B, and maximum number of schedulable subframes for DCI format 0B is 4 subframes
}
}
}

7.1.4.32.2 eLAA / SCell PUSCH / Correct handling of UL assignment / DCI4A/4B/One step scheduling

7.1.4.32.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and Uplink is configured with TM2 and SS is sending an eLAA SCell scheduling grant DCI 4A on PDCCH with a valid C-RNTI indicating non-triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 4A in subframe n and UE has UL data available for transmission }

then { the UE transmits a PUSCH data frame in the indicated subframe and HARQ process }

(2)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and uplink is configured with TM2 and Monitoring DCI 4B is enabled and SS is sending an eLAA SCell scheduling grant DCI 4B on PDCCH with a valid C-RNTI indicating non-triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 4B in subframe n and UE has UL data available for transmission }

then { the UE transmits multiple PUSCH data frames in the indicated multiple subframes and HARQ processes }

7.1.4.32.2.2 Conformance requirements

Refer to clause 7.1.4.32.0

7.1.4.32.2.3 Test description

7.1.4.32.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 (PCell) and Cell 10 (SCell)

– Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB (1, 0) is used for step 8 in 4.5.3A.3 according to [18].

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.32.2.3.2 Test procedure sequence

Table 7.1.4.32.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmit an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing two RLC PDUs	<–	MAC PDU (CC₁)	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS sends an UL grant suitable for transmitting two RLC PDUs in subframe n on Cell 10.	<–	(UL Grant (DCI Format 4A: HARQ PROCESS ID = X, New data indicator = 0, two identical transport blocks scheduled))	–	–
7	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 4 in HARQ process X in subframe n+4 on Cell 10.	–>	MAC PDU (CC₂)	P	1
8	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing eight RLC PDUs	<–	MAC PDU (CC₁)
9	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
10	The SS sends an UL grant suitable for transmitting two RLC PDUs on Cell 10.	<–	(UL Grant (DCI Formant 4B: Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = 1, two identical transport blocks scheduled)	–	–
11	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 8 in HARQ process X in subframe n+4 on Cell10?	–>	MAC PDU(CC₂)	P	2
12	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 8 in HARQ process mod(X+1, 16) in subframe n+5 on Cell10?	–>	MAC PDU(CC₂)	P	2
13	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 8 in HARQ process mod(X+2, 16) in subframe n+6 on Cell10?	–>	MAC PDU(CC₂)	P	2
14	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 8 in HARQ process mod(X+3, 16) in subframe n+7 on Cell10?	–>	MAC PDU(CC₂)	P	2
Note 1: The default setting of DCI format 4A and 4B refers to TS 36.508 clause 4.3.6 with exception specified in the table 7.1.4.32.2.3.2-1.

7.1.4.32.2.3.3 Specific message contents

Table 7.1.4.32.2.3.3-1: RRCConnectionReconfiguration (step1, Table 7.1.4.32.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8 Condition SCell_AddMod

Table 7.1.4.32.2.3.3-2: RadioResourceConfigDedicated-SCell_AddMod (Table 7.1.4.32.2.3.3-1)

Derivation Path: 36.508 Table 4.6.3-19AAA
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SCell_AddMod ::= SEQUENCE {
drb-ToAddModList::= SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {	1 Entry
drb-Identity[1]	1
logicalChannelIdentity[1]	3
logicalChannelConfig[1] ::= SEQUENCE {
laa-UL-Allowed-r14	True
}
}
}

Table 7.1.4.32.2.3.3-3: SCellToAddMod-r10 (Table 7.1.4.32.2.3.3-1)

Derivation Path: 36.508 Table 4.6.3-19D

Table 7.1.4.32.2.3.3-4: RadioResourceConfigDedicatedSCell-r10 (Table 7.1.4.32.2.3.3-3)

Derivation Path: 36.508 Table 4.6.3-19AA

Table 7.1.4.32.2.3.3-5: PhysicalConfigDedicatedSCell-r10 (Table 7.1.4.32.2.3.3-4)

Derivation Path:TS 36.508 Table 4.6.3-6A
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicatedSCell-r10-DEFAULT ::= SEQUENCE {
ul-Configuration-r10 SEQUENCE {
antennaInfoUL-r10 SEQUENCE {
transmissionModeUL-r10	tm2
}
}
laa-ScellConfiguration-r13 SEQUENCE {
subframeStartPosition	‘s0’
laa-SCellSubframeConfig	‘00000000’
}
laa-SCellConfiguration-v1430 SEQUENCE {
pdcch-ConfigLAA-r14 SEQUENCE {
maxNumberOfSchedSubframes-Format0B-r14	sf4	Enable DCI format 0B, and maximum number of schedulable subframes for DCI format 0B is 4 subframes
maxNumberOfSchedSubframes-Format4B-r14	sf4	Enable DCI format 0B, and maximum number of schedulable subframes for DCI format 0B is 4 subframes
}
}
}

7.1.4.32.3 eLAA / SCell PUSCH / Correct handling of UL assignment / DCI0A/0B / Two step scheduling

7.1.4.32.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and SS is sending an eLAA SC scellheduling grant DCI 0A on PDCCH with a valid C-RNTI indicating triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 0A in subframe n-p and SS transmits in PDCCH in eLAA Scell with DCI format 1C scrambled with CC-RNTI in subframe n and UE detects the DCI 1C and has UL data available for transmission }

then { the UE transmits a PUSCH data frame in the subframe and HARQ process indicated by DCI 0A and DCI 1C together}

(2)

with { UE in E-UTRA RRC_CONNECTED state with eLAA SCell configured and activated and SS is sending an eLAA SCell scheduling grant DCI 0B on PDCCH with a valid C-RNTI indicating triggered scheduling }

ensure that {

when { UE detects the valid UL grant DCI 0B in subframe n-p and SS transmits in PDCCH in eLAA Scell with DCI format 1C scrambled with CC-RNTI and UE detects the DCI 1C in subframe n and has UL data available for transmission }

then { the UE transmits multiple PUSCH data frames in the subframes and HARQ processes indicated by DCI 0B and DCI 1C together}

7.1.4.32.3.2 Conformance requirements

Reference to clause 7.1.4.32.0

7.1.4.32.3.3 Test description

7.1.4.32.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 (PCell) and Cell 10 (SCell)

– Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB(1,0) is used for step 8 in 4.5.3A.3 according to [18].

7.1.4.32.3.3.2 Test procedure sequence

Table 7.1.4.32.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmit an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits MAC PDU containing one RLC PDUs	<–	MAC PDU (CC₁)	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS sends an UL grant suitable for transmitting one RLC PDU on Cell 10.	<–	(UL Grant (DCI Format 0A: PUSCH trigger A = “1”, HARQ PROCESS ID = X, New data indicator = “0”, k = 0, v = 20))	–	–
7	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 4 in HARQ process X within 20 ms.	–>	MAC PDU (CC₂)	F	1
8	The SS sends, in subframe n-p, an UL grant suitable for transmitting one RLC PDU (Note 1).	<–	(UL Grant (DCI Format 0A: PUSCH trigger A = “1”, HARQ PROCESS ID = X, New data indicator = “0”, k = 0 , v = 20))	–	–
9	The SS sends PUSCH trigger B on Cell 10 in subframe n.	<–	(Trigger B (DCI Formant 1C: PUSCH Trigger B = “1”, l (Note 2), d = 1 )	–	–
10	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 4 in HARQ process X in subframe n+l?-	–>	MAC PDU (CC₂)	P	1
11	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing four RLC PDUs	<–	MAC PDU (CC₁)
12	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
13	The SS sends, in subframe n-p, an UL grant suitable for transmitting one RLC PDU on Cell 10 (Note 1).	<–	(UL Grant (DCI Format 0B: PUSCH trigger A = “1”, Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = “1”, k = 0 , v = 20))	–	–
14	Check: Does the UE transmit a MAC PDU containing one RLC PDU corresponding to step 11 in HARQ process X within 20 ms.	–>	MAC PDU (CC₂)	F	1
15	The SS sends, in subframe n-p, an UL grant suitable for transmitting one RLC PDU on Cell 10 (Note 1).	<–	(UL Grant (DCI Format 0B: PUSCH trigger A = “1”, Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = “1”, k = 0 , v = 20))	–	–
16	The SS sends PUSCH trigger B on Cell 10 in subframe n.		(Trigger B (DCI Formant 1C: PUSCH Trigger B = “1”, l (Note 2), d = 6 )
17	Check: Does the UE transmit a MAC PDU containing one loop back PDU corresponding to step 11 in HARQ process X in subframe n+l on Cell 10?	–>	MAC PDU(CC₂)	P	2
18	Check: Does the UE transmit a MAC PDU containing one loop back PDU corresponding to step 11 in HARQ process mod(X+1, 16) in subframe n+l+1 on Cell 10?	–>	MAC PDU(CC₂)	P	2
19	Check: Does the UE transmit a MAC PDU containing one loop back PDU corresponding to step 11 in HARQ process mod(X+2, 16) in subframe n+l+2 on Cell 10?	–>	MAC PDU(CC₂)	P	2
20	Check: Does the UE transmit a MAC PDU containing one loop back PDU corresponding to step 11 in HARQ process mod(X+3, 16) in subframe n+l+3 on Cell10?	–>	MAC PDU(CC₂)	P	2
Note1: The default setting of DCI format 0A and 0B refers to TS 36.508 clause 4.3 with exception in the table 7.1.4.32.3.3.2-1. Note 2: p and l are decided as per the twoStepSchedulingTimingInfo of UE capability and in a principle that p+l = 4. If twoStepSchedulingTimingInfo is indicated to be nPlus1, l = 1 and p = 3; if twoStepSchedulingTimingInfo is indicated to be nPlus2, l = 2 and p = 2; if twoStepSchedulingTimingInfo is indicated to be nPlus3, l = 3 and p = 1

7.1.4.32.3.3.3 Specific message contents

Refer to clause 7.1.4.32.1.3.3

7.1.4.32.4 eLAA / SCell PUSCH / Correct handling of UL assignment / DCI4A/4B / Two step scheduling

7.1.4.32.4.1 Test Purpose (TP)

(1)

ensure that {

when { UE detects the valid UL grant DCI 4A in subframe n-p and SS transmits in PDCCH in eLAA Scell with DCI format 1C scrambled with CC-RNTI in subframe n and UE detects the DCI 1C and has UL data available for transmission }

then { the UE transmits a PUSCH data frame in the subframe and HARQ process indicated by DCI 4A and DCI 1C together}

(2)

ensure that {

when { UE detects the valid UL grant DCI 4B in subframe n-p and SS transmits in PDCCH in eLAA Scell with DCI format 1C scrambled with CC-RNTI and UE detects the DCI 1C in subframe n and has UL data available for transmission }

then { the UE transmits multiple PUSCH data frames in the subframes and HARQ processes indicated by DCI 4B and DCI 1C together}

7.1.4.32.4.2 Conformance requirements

Reference to clause 7.1.4.32.0

7.1.4.32.4.3 Test description

7.1.4.32.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 (PCell) and Cell 10 (SCell)

– Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition SRB2-DRB (1, 0) is used for step 8 in 4.5.3A.3 according to [18].

– The loop back size is set in such a way that one RLC SDU in DL shall result in 1 RLC SDU’s in UL.

– No UL Grant is allocated; PUCCH is in synchronised state for sending Scheduling Requests.

7.1.4.32.4.3.2 Test procedure sequence

Table 7.1.4.32.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition.	<–	RRCConnectionReconfiguration	–	–
2	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3	The SS transmits Activation MAC control element to activate Scell (Cell 10).	<–	MAC PDU (Activation (C₁=1))	–	–
4	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing two RLC PDUs	<–	MAC PDU (CC₁)	–
5	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
6	The SS sends an UL grant suitable for transmitting two RLC PDUs on Cell 10.	<–	(UL Grant (DCI Format 4A: PUSCH trigger A = “1”,HARQ PROCESS ID = X, New data indicator = “0”, k = 0, v = 20, two identical transport blocks scheduled))	–	–
7	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 4 in HARQ process X within 20 ms.	–>	MAC PDU (CC₂)	F	1
8	The SS sends, in subframe n-p, an UL grant suitable for transmitting two RLC PDUs (Note 1) on Cell 10.	<–	(UL Grant (DCI Format 4A: PUSCH trigger A = “1”,HARQ PROCESS ID = X, New data indicator = “0”, k = 0, v = 20, two identical transport blocks scheduled))	–	–
9	The SS sends PUSCH trigger B in subframe n on Cell 10.	<–	(Trigger B (DCI Formant 1C: PUSCH Trigger B = “1”, l (Note 2), d = 1 )	–	–
10	Check: Does the UE transmit two MAC PDUs each containing a RLC PDU corresponding to step 4 in HARQ process X in subframe n+l on Cell 10?-	–>	MAC PDU (CC₂)	P	1
11	The SS indicates a new transmission on PDCCH of CC1 (Cell 1) and transmits a MAC PDU containing eight RLC PDUs	<–	MAC PDU (CC₁)
12	UE transmits a Scheduling Request on PUCCH.	–>	(SR)	–	–
13	The SS sends, in subframe n-p, an UL grant suitable for transmitting two RLC PDUs on Cell 10 (Note 1).	<–	(UL Grant (DCI Format 4B: PUSCH trigger A = “1”, Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = “1”, k = 0 , v = 20, two identical transport blocks scheduled))	–	–
14	Check: Does the UE transmit two MAC PDUs each containing one RLC PDU corresponding to step 11 in HARQ process X within 20 ms.	–>	MAC PDU (CC₂)	F	1
15	The SS sends, in subframe n-p, an UL grant suitable for transmitting two RLC PDUs (Note 1) on Cell 10.	<–	(UL Grant (DCI Format 4B: PUSCH trigger A = “1”, Number of scheduled subframes = 4, HARQ PROCESS ID = X, New data indicator = “1”, k = 0 , v = 20, , two identical transport blocks scheduled))	–	–
16	The SS sends PUSCH trigger B on Cell 10 in subframe n.	<–	(Trigger B (DCI Formant 1C: PUSCH Trigger B = “1”, l (Note 2), d = 6 )
17	Check: Does the UE transmit two MAC PDUs each containing one loop back PDU corresponding to step 11 in HARQ process X in subframe n+l on Cell 10?	–>	MAC PDU(CC₂)	P	2
18	Check: Does the UE transmit two MAC PDUs each containing one loop back PDU corresponding to step 11 in HARQ process mod(X+1, 16) in subframe n+l+1 on Cell 10?	–>	MAC PDU(CC₂)	P	2
19	Check: Does the UE transmit two MAC PDUs each containing one loop back PDU corresponding to step 11 in HARQ process mod(X+2, 16) in subframe n+l+2 on Cell 10?	–>	MAC PDU(CC₂)	P	2
20	Check: Does the UE transmit two MAC PDUs each containing one loop back PDU corresponding to step 11 in HARQ process mod(X+3, 16) in subframe n+l+3 on Cell10?	–>	MAC PDU(CC₂)	P	2
Note1: The default setting of DCI format 0A and 0B refers to TS 36.508 clause 4.3.6 with exception in the table 7.1.4.32.4.3.2-1. Note 2: p and l are decided as per the twoStepSchedulingTimingInfo of UE capability and in a principle that p+l = 4. If twoStepSchedulingTimingInfo is indicated to be nPlus1, l = 1 and p = 3; if twoStepSchedulingTimingInfo is indicated to be nPlus2, l = 2 and p = 2; if twoStepSchedulingTimingInfo is indicated to be nPlus3, l = 3 and p = 1.

7.1.4.32.4.3.3 Specific message contents

Refer to clause 7.1.4.32.2.3.3.

7.1.4.33 Void

7.1.4.34 Void

7.1.4.35 Void

7.1.4.36 Void

7.1.4.37 Short Processing Time / Correct handling of UL assignment

7.1.4.37.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an uplink grant on the PDCCH mapped onto the UE-specific search space in SF-NUM n }

then { UE performs the corresponding MAC PDU transmission in SF-NUM n+3 }

}

7.1.4.37.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 5.4.1 and TS 36.213 clause 7.7.

[TS 36.213, clause 5.4.1]

If the MAC entity has a C-RNTI, a Semi-Persistent Scheduling C-RNTI, a UL Semi-Persistent Scheduling V-RNTI, a AUL C-RNTI, or a Temporary C-RNTI, the MAC entity shall for each TTI and for each Serving Cell belonging to a TAG that has a running timeAlignmentTimer and for each grant received for this TTI and for each SPS configuration that is indicated by the PDCCH addressed to UL Semi-Persistent Scheduling V-RNTI:

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– else, if an uplink grant for this TTI has been received for this Serving Cell on the PDCCH for the MAC entity’s Semi-Persistent Scheduling C-RNTI or for the MAC entity’s UL Semi-Persistent Scheduling V-RNTI; or if an uplink grant for this TTI has been received for this Serving Cell on the PDCCH for the MAC entity’s AUL C-RNTI:

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

…

NOTE 1: The period of configured uplink grants is expressed in TTIs.

NOTE 2: If the MAC entity receives both a grant in a Random Access Response and a grant for its C-RNTI or Semi persistent scheduling C-RNTI requiring transmissions on the SpCell in the same UL subframe, the MAC entity may choose to continue with either the grant for its RA-RNTI or the grant for its C-RNTI or Semi persistent scheduling C-RNTI.

NOTE 3: When a configured uplink grant is indicated during a measurement gap and indicates an UL-SCH transmission during a measurement gap, the MAC entity processes the grant but does not transmit on UL-SCH. When a configured uplink grant is indicated during a Sidelink Discovery gap for reception and indicates an UL-SCH transmission during a Sidelink Discovery gap for transmission with a SL-DCH transmission, the MAC entity processes the grant but does not transmit on UL-SCH. When a configured uplink grant indicates an UL-SCH transmission during a V2X sidelink communication transmission and transmission of V2X sidelink communication is prioritized as described in clause 5.14.1.2.2, the MAC entity processes the grant but does not transmit on UL-SCH.

[TS 36.213, clause 7.7]

For each serving cell, in case of FDD configuration not configured with subframeAssignment-r15 and in case of Frame Structure Type 3 configuration on the serving cell which carries the HARQ feedback for this serving cell the HARQ RTT Timer is set to 8 subframes. For each serving cell, in case of TDD configuration or FDD with subframeAssignment-r15 configured on the serving cell which carries the HARQ feedback for this serving cell the HARQ RTT Timer is set to k + 4 subframes, where k is the interval between the downlink transmission and the transmission of associated HARQ feedback, as indicated in clauses 10.1 and 10.2 of TS 36.213 [2], and for an RN configured with rn-SubframeConfig, as specified in TS 36.331 [8] and not suspended, as indicated in Table 7.5.1-1 of TS 36.216 [11].

For HARQ processes scheduled using Short Processing Time (TS 36.331 [8]), the UL HARQ RTT Timer length is set to 3 subframes for FDD and for Frame Structure Type 3, and set to k_ULHARQRTT subframes for TDD, where k_ULHARQRTT equals the value indicated in Table 7.7-1 and Table 7.7-2.

Table 7.7-1: k_ULHARQRTT for TDD Short Processing Time when special subframe configurations 0~9 is configured

TDD UL/DL Configuration					subframe index n
	0	1	2	3		4	5	6	7	8	9
0			3	3		6			3	3	6
1			3	3					3	3
2			3						3
3			3	3		3
4			3	3
5			3
6			3	3		5			3	3

Table 7.7-2: k_ULHARQRTT for TDD Short Processing Time applied when special subframe configuration 10 is configured

TDD UL/DL Configuration	subframe index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9
0		4	3	3	6		4	3	3	6
1		3	3	3			3	3	3
2		3	3				3	3
3		4	3	3	3
4		3	3	3
5		3	3
6		4	3	3	5		3	3	3

7.1.4.37.3 Test description

7.1.4.37.3.1 Pre-test conditions

System Simulator:

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.37.3.3-1

UE:

– None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.37.3.2 Test procedure sequence

Table 7.1.4.37.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
3	Void	–	–	–	–
–	EXCEPTION: Step 4 runs in parallel with behaviour in table 7.1.4.37.3.2-2.	–	–	–	–
4	The SS transmits an UL Grant on PDCCH in UE-specific search space in SF-NUM ‘N’, allowing the UE to return the RLC SDU as received in step 2.	<–	UL Grant	–	–
5	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 4 in SF-NUM ‘N+3?	–>	MAC PDU	1	P

Table 7.1.4.37.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	UE transmits a Scheduling Request.	–>	(SR)	–	–

7.1.4.37.3.3 Specific Message Contents

Table 7.1.4.37.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.37.3.3-2: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 Table 4.8.2.1.6-1
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
PhysicalConfigDedicatedSTTI-r15 ::= SEQUENCE{
shortProcessingTime-r15	TRUE
}
}

7.1.4.38 Short TTI / Correct handling of UL assignment / Collision handling

7.1.4.38.1 sTTI combination {slot, slot} / Correct handling of UL assignment / Collision handling

7.1.4.38.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { UE receives an uplink grant on SPDCCH and has data available for slot-based PDSCH transmission in the associated slot 0 of SF-NUM n }

then { UE transmits a MAC PDU in slot 0 of SF-NUM n+2 }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives PDSCH transmission in SF-NUM x and receives an uplink grant on SPDCCH and has data available for slot-based PDSCH transmission in slot 0 of SF-NUM x+2 and configured spatial bundling for PUSCH }

then { UE performs slot-based PUSCH transmission and HARQ-ACK response associated with subframe-PUCCH in the slot 0 of SF-NUM x+4 }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an uplink grant on PDCCH for subframe-PUSCH transmission in SF-NUM x and receives an uplink grant on SPDCCH for slot-based PDSCH transmission in slot 0 of SF-NUM x+2 }

then { UE performs slot-based PUSCH transmission in the slot 0 of SF-NUM x+4 and drops subframe-PUSCH transmission }

}

7.1.4.38.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 5.4.1 and 3GPP TS 36.213 clause 7.7.

[TS 36.321, clause 5.4.1]

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

…

NOTE 1: The period of configured uplink grants is expressed in TTIs.

[TS 36.321, clause 7.7]

…

For each serving cell, for HARQ processes scheduled using short TTI (TS 36.331 [8]) the HARQ RTT is set to 8 TTIs if the TTI length is one slot or if proc-Timeline is set to n+4 set1, to 12 TTIs if proc-Timeline is set to n+6 set1 or n+6 set2 and to 16 TTIs if proc-Timeline is set to n+8 set2 for FDD and Frame Structure Type 3.

…

For HARQ processes scheduled using short TTI (TS 36.331 [8]), the UL HARQ RTT Timer length is set to 8 TTIs if the TTI length is one slot or if proc-Timeline is set to n+4 set1, to 12 TTIs if proc-Timeline is set to n+6 set1 or n+6 set2 and to 16 TTIs if proc-Timeline is set to n+8 set2 for FDD and Frame Structure Type 3. For TDD short TTI the UL HARQ RTT is set to k_ULHARQRTT TTIs, where k_ULHARQRTT equals the value indicated in Table 7.7-3, Table 7.7-4 and Table 7.7-5.

Table 7.7-3: k_ULHARQRTT for TDD short TTI applied when special subframe configurations 1, 2, 3, 4, 6, 7 and 8 are configured

TDD UL/DL Configuration	sTTI index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19
0					6	5	4	4	4	4					6	5	4	4	4	4
1					4	4	4	4							4	4	4	4
2					4	4									4	4
3					6	5	4	4	4	4
4					4	4	4	4
5					4	4
6					6	5	4	4	4	4					4	4	4	4

Table 7.7-4: k_ULHARQRTT for TDD short TTI applied when special subframe configurations 0, 5 and 9 are configured

TDD UL/DL Configuration	sTTI index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19
0					6	5	4	4	4	11					6	5	4	4	4	11
1					4	4	4	4							4	4	4	4
2					4	4									4	4
3					6	5	4	4	4	4
4					4	4	4	4
5					4	4
6					6	5	4	4	4	9					4	4	4	4

Table 7.7-5: k_ULHARQRTT for TDD short TTI applied when special subframe configuration 10 is configured

TDD UL/DL Configuration	sTTI index n
TDD UL/DL Configuration	0	1	2	3	4	5	6	7	8	9	10	11	12	13	14	15	16	17	18	19
0				7	6	5	4	4	4	11				7	6	5	4	4	4	11
1				5	4	4	4	4						5	4	4	4	4
2				4	4	4								4	4	4
3				7	6	5	4	4	4	4
4				5	4	4	4	4
5				4	4	4
6				7	6	5	4	4	4	9				5	4	4	4	4

7.1.4.38.1.3 Test description

7.1.4.38.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.38.1.3.3-1

UE:

– None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.38.1.3.2 Test procedure sequence

Table 7.1.4.38.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
2	The SS transmits an UL Grant on SPDCCH in the associated slot ‘0’ of SF-NUM ‘N’, allowing the UE to return the RLC SDU as received in step 1.	<–	UL Grant	–	–
3	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 4 in slot ‘0’ of SF-NUM ‘N+2’?	–>	MAC PDU	1	P
4	The SS transmits a MAC PDU containing a RLC PDU in SF-NUM ‘X’ with CRC is calculated in such a way that it will result in CRC pass on UE side.	<–	MAC PDU	–	–
5	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
6	The SS transmits an UL Grant on SPDCCH in the associated slot ‘0’ of SF-NUM ‘X+2’, allowing the UE to return the RLC SDU as received in step 5.	<–	UL Grant
7	Check: Does the UE transmit a MAC PDU in step 5 in slot ‘0’ of SF-NUM ‘X+4’?	–>	MAC PDU	2	P
8	Check: Does the UE transmit any HARQ ACK in slot ‘0’ of SF-NUM ‘X+4’?	–>	ACK	2	P
9	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
10	The SS transmits an UL Grant on PDCCH in SF-NUM ‘Y’, allowing the UE to return the RLC SDU as received in step 9.	<–	UL Grant	–	–
11	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
12	The SS transmits an UL Grant on SPDCCH in the associated slot ‘0’ of SF-NUM ‘Y+2’, allowing the UE to return the RLC SDU as received in step 11.	<–	UL Grant	–
13	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 12 in slot ‘0’ of SF-NUM ‘Y+4’?	–>	MAC PDU	3	P
14	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 10 in slot ‘0’ of SF-NUM ‘Y+4’?	–>	MAC PDU	3	F

NOTE 1: For TDD, the timing of ACK/NACK is not constant as FDD, see Table 10.1-1 of TS 36.213.

7.1.4.38.1.3.3 Specific Message Contents

Table 7.1.4.38.1.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig CHOICE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.38.1.3.3-2: PhysicalConfigDedicated-DEFAULT (preamble)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pucch-ConfigDedicated-r13	PUCCH-ConfigDedicated- r13-DEFAULT
}

Table 7.1.4.38.1.3.3-3: PUCCH-ConfigDedicated- r13-DEFAULT (Table 7.1.4.38.1.3.3-2)

Derivation Path: 36.508 Table 4.6.3-9AC
Information Element	Value/remark	Comment	Condition
PUCCH-ConfigDedicated- r13-DEFAULT ::= SEQUENCE {
ackNackRepetition-R13 CHOICE {
release	NULL
}
spatialBundlingPUCCH	TRUE
spatialBundlingPUSCH	TRUE
}

7.1.4.38.2 sTTI combination {subslot, subslot} / Correct handling of UL assignment / Collision handling

7.1.4.38.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and supporting sTTI length combination {subslot,subslot} }

ensure that {

when { UE receives an uplink grant on SPDCCH and has data available for subslot-based PDSCH transmission in the associated subslot i of SF-NUM n }

then { UE transmits a MAC PDU in the subslot j of SF-NUM n+x with j=mod{i+k,6} and x=floor{(i+k)/6, where k is dependent on UE capability and RRC configuration }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives PDSCH transmission in SF-NUM x and receives an uplink grant on SPDCCH and has data available for subslot-based PDSCH transmission in subslot 3 of SF-NUM x+3 }

then { UE performs subslot-based PUSCH transmission and HARQ-ACK response associated with subframe-PUCCH in the subslot j of SF-NUM x+4 where j=mod{3+k,6} and k is determined based on higher layer parameter min-proc-TimelineSubslot from {4,6,8} }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an uplink grant on PDCCH and has data available for subframe-PUSCH transmission in SF-NUM x and receives an uplink grant on SPDCCH and has data available for subslot-based PDSCH transmission in subslot 3 of SF-NUM x+3 }

then { UE performs subslot-based PUSCH transmission in the subslot j of SF-NUM x+4 and drops subframe-PUSCH transmission, where j=mod{3+k,6} and k is determined based on higher layer parameter min-proc-TimelineSubslot from {4,6,8} }

}

7.1.4.38.2.2 Conformance requirements

Same as sub-clause 7.1.4.38.1.2.

7.1.4.38.2.3 Test description

7.1.4.38.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.38.2.3.3-1

UE:

– None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.38.2.3.2 Test procedure sequence

Table 7.1.4.38.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
2	The SS transmits an UL Grant on SPDCCH in the associated subslot ‘i’ of SF-NUM ‘N’, allowing the UE to return the RLC SDU as received in step 1.	<–	UL Grant	–	–
3	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 9 in subslot ‘mod{i+k,6}’ of SF-NUM ‘N+floor{(i+k)/6}’?	–>	MAC PDU	1	P
4	The SS transmits a MAC PDU containing a RLC PDU in SF-NUM ‘X’ with CRC is calculated in such a way that it will result in CRC pass on UE side.	<–	MAC PDU	–	–
5	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
6	The SS transmits an UL Grant on SPDCCH in the associated subslot ‘3’ of SF-NUM ‘X+3’, allowing the UE to return the RLC SDU as received in step 5.	<–	UL Grant	–	–
7	Check: Does the UE transmit a MAC PDU corresponding to the grant in step 6 in subslot ‘mod{3+k,6}’ of SF-NUM ‘X+4’?	–>	MAC PDU	2	P
8	Check: Does the UE transmit a HARQ ACK in subslot ‘mod{3+k, 6}’ of SF-NUM ‘X+4’?	–>	ACK	2	P
9	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
10	The SS transmits an UL Grant on PDCCH in SF-NUM ‘Y’, allowing the UE to return the RLC SDU as received in step 9.	<–	UL Grant	–	–
11	The SS transmits a MAC PDU including a RLC SDU.	<–	MAC PDU	–	–
12	The SS transmits an UL Grant on SPDCCH in the associated subslot ‘3’ of SF-NUM ‘Y+3’, allowing the UE to return the RLC SDU as received in step 11.	<–	UL Grant	–
13	Check: Does the UE transmit a MAC PDU corresponding to grant in step 12 in subslot ‘mod{3+k, 6}’ of SF-NUM ‘Y+4’?	–>	MAC PDU	3	P
14	Check: Does the UE transmit a MAC PDU corresponding to grant in step 10 in subslot ‘mod{3+k, 6}’ of SF-NUM ‘Y+4’?	–>	MAC PDU	3	F
Note 1: The value k equals to 4 if proc-Timeline is set to n+4 set1, to 6 if proc-Timeline is set to n+6 set1 or n+6 set2 and to 8 if proc-Timeline is set to n+8 set2. If Set 1 or Set 2 is supported is a UE capability.

7.1.4.38.2.3.3 Specific Message Contents

Table 7.1.4.38.2.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig SEQUENCE{
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.38.2.3.3-2: PhysicalConfigDedicated-DEFAULT (preamble)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
PhysicalConfigDedicatedSTTI-r15 SEQUENCE {
shortTTI-r15 SEQUENCE {
dl-STTI-Length-r15	subslot
ul-STTI-Length-r15	subslot
}
}
}

7.1.4.39 Short TTI / Correct handling of UL assignment / DMRS sharing

7.1.4.39.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an uplink grant on SPDCCH for each subslot indicating DMRS sharing pattern among subslots and has data available for transmission }

then { UE transmits data in a subframe period according to the SPDCCH indication }

}

7.1.4.39.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 5.4.1 and 3GPP TS 36.211 clause 5.5.2.

[TS 36.213, clause 5.4.1]

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

…

NOTE 1: The period of configured uplink grants is expressed in TTIs.

[TS 36.211, clause 5.5.2]

In case of subslot-PUSCH, the mapping to resource elements , in the subframe shall be in increasing order of first for all values of , except if the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7, which indicates the use of Table 5.5.2.1.1-4. In this case the mapping to resource element shall be in increasing order of first only for values of satisfying . The value of depends on the uplink subslot number and the DMRS-pattern field in the most recent uplink-related DCI, according to Table 5.5.2.1.2-1, or according to Table 5.5.2.1.2-2 in case of semi-persistent scheduling of subslot-PUSCH (i.e. higher layer parameter sps-ConfigUL-sTTI-r15 is configured, se 3GPP TS 36.331 [9]) and with a configured periodicity of 1 subslot (i.e. semiPersistSchedIntervalUL-STTI-r15 set to sTTI1). In case of subslot-PUSCH and semi-persistent scheduling with a configured periodicity longer than 1 subslot, the mapping shall start at symbol according to the first row of Table 5.5.2.1.2-2 (i.e. equivalent to a signalling of DMRS-pattern field set to ’00’). In case no value of is defined for the uplink subslot number, and in case no valid starting symbol index (see table 5.3.4-1), no reference signal is transmitted associated with the uplink-related DCI format.

Table 5.5.2.1.2-1: The quantity for subslot-PUSCH

DMRS-pattern field in uplink-related DCI format [3]	Uplink subslot number
DMRS-pattern field in uplink-related DCI format [3]	#0	#1	#2	#3	#4	#5
00	0	3	5	0	2	4
01	2	4	–	1	3	–
10	–	–	–	2	–	–
11	–	5	–	–	4	–

Table 5.5.2.1.2-2: The quantity for subslot-PUSCH for semi-persistent scheduling

DMRS-pattern field in uplink-related DCI format [3]	Uplink subslot number
DMRS-pattern field in uplink-related DCI format [3]	#0	#1	#2	#3	#4	#5
00	0	3	5	0	2	4
10	0	5	5	2	2	4

7.1.4.39.3 Test description

7.1.4.39.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.39.3.2 Test procedure sequence

Table 7.1.4.39.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	SS transmits a MAC PDU containing a RLC SDU in each subslot from sTTI ‘0’ to sTTI ‘5’.	<–	MAC PDU	–	–
3	The SS transmits an UL Grant on SPDCCH in each subslot within a subframe using DCI format 7-0A with DMRS-pattern field given in Table 7.1.4.39.3.2-2, allowing the UE to return the RLC SDU as received in step 2.	<–	UL Grant	–	–
4	Check: Does the UE transmit uplink data and DMRS on each subslot-based PUSCH according to the DCI indication in step 3?	–>	MAC PDU	1	P

Table 7.1.4.39.3.2-2: DMRS pattern field

St	Uplink subslot number
St	#0	#1	#2	#3	#4	#5
DMRS-pattern field in uplink-related DCI format	00	10	01	00	10	00

7.1.4.39.3.3 Specific Message Contents

Table 7.1.4.39.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig SEQUENCE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.39.3.3-2: PhysicalConfigDedicated-DEFAULT (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
PhysicalConfigDedicatedSTTI-r15 SEQUENCE {
shortTTI-r15 SEQUENCE {
dl-STTI-Length-r15	subslot
ul-STTI-Length-r15	subslot
}
}
}

7.1.4.40 Short TTI / Correct handling of MAC control information / Scheduling requests and SPUCCH

7.1.4.40.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE has UL data available for transmission and UE has no UL-SCH resources available and SSR-COUNTER is less than dssr-TransMax }

then { UE transmits a SR on every available SPUCCH until UL-SCH resources are granted }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and has pending SR(s) }

ensure that {

when { UE receives an UL grant for a new transmission }

then { UE cancels all pending SR(s) }

}

7.1.4.40.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 5.4.4 and TS 36.213 clause 10.1.5.

[TS 36.213, clause 5.4.4]

The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.

When an SR is triggered, it shall be considered as pending until it is cancelled. All pending SR(s) shall be cancelled and sr-ProhibitTimer and ssr-ProhibitTimer shall be stopped when a MAC PDU is assembled and this PDU includes a BSR which contains buffer status up to (and including) the last event that triggered a BSR (see clause 5.4.5), or, if all pending SR(s) are triggered by Sidelink BSR, when a MAC PDU is assembled and this PDU includes a Sidelink BSR which contains buffer status up to (and including) the last event that triggered a Sidelink BSR (see clause 5.14.1.4), or, if all pending SR(s) are triggered by Sidelink BSR, when upper layers configure autonomous resource selection, or when the UL grant(s) can accommodate all pending data available for transmission.

If an SR is triggered and there is no other SR pending, the MAC entity shall set the SR_COUNTER and the SSR_COUNTER to 0.

As long as one SR is pending, the MAC entity shall for each TTI:

– if no UL-SCH resources are available for a transmission in this TTI:

– Except for NB-IoT:

– if the MAC entity has no valid PUCCH nor valid SPUCCH resource for SR configured in any TTI:

– if the MAC entity is a MCG MAC entity and rach-Skip is not configured; or

– if the MAC entity is a SCG MAC entity and rach-SkipSCG is not configured:

– initiate a Random Access procedure (see clause 5.1) on the corresponding SpCell and cancel all pending SRs;

– else if this TTI is not part of a measurement gap or Sidelink Discovery Gap for Transmission, and if transmission of V2X sidelink communication is not prioritized in this TTI as described in clause 5.14.1.2.2:

– if the MAC entity has at least one valid SPUCCH resource for SR configured for this TTI and if ssr-ProhibitTimer is not running:

– if SSR_COUNTER < dssr-TransMax:

– increment SSR_COUNTER by 1;

– instruct the physical layer to signal the SR on one valid SPUCCH resource for SR;

– start the ssr-ProhibitTimer.

– else:

– notify RRC to release SPUCCH for all serving cells;

– if the MAC entity has no valid PUCCH resource for SR configured in any TTI:

– notify RRC to release PUCCH for all serving cells;

– notify RRC to release SRS for all serving cells;

– clear any configured downlink assignments and uplink grants;

– initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

– if the MAC entity has at least one valid PUCCH resource for SR configured for this TTI and if sr-ProhibitTimer is not running:

– if SR_COUNTER < dsr-TransMax:

– increment SR_COUNTER by 1;

– instruct the physical layer to signal the SR on one valid PUCCH resource for SR;

– start the sr-ProhibitTimer.

– else:

– notify RRC to release PUCCH and SPUCCH for all serving cells;

– notify RRC to release SRS for all serving cells;

– clear any configured downlink assignments and uplink grants;

– initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs.

…

NOTE 1: The selection of which valid PUCCH/SPUCCH resource for SR to signal SR on when the MAC entity has more than one valid PUCCH/SPUCCH resource for SR in one TTI or overlapping TTIs is left to UE implementation.

NOTE 2: SR_COUNTER is incremented for each SR bundle. sr-ProhibitTimer is started in the first TTI of an SR bundle.

[TS 36.213, clause 10.1.5]

A non-BL/CE UE is configured by higher layers to transmit the SR on one antenna port or two antenna ports.
For a non-BL/CE UE, the scheduling request shall be transmitted on the PUCCH resource(s) for mapped to antenna port p as defined in [3], where is configured by higher layers unless the SR coincides in time with the transmission of HARQ-ACK using PUCCH Format 3/4/5 in which case the SR is multiplexed with HARQ-ACK according to Subclause 5.2.3.1 of [4]. The subframe-SR configuration for SR transmission periodicity and SR subframe offset is defined in Table 10.1.5-1 by the parameter sr-ConfigIndex given by higher layers.

Subframe-SR transmission instances are the uplink subframes satisfying .

The slot-SR configuration for SR transmission periodicity and SR slot offset is defined in Table 10.1.5-1A by the parameter sr-ConfigIndexSlot given by higher layers.

Slot-SR transmission instances are the uplink slots satisfying

The subslot-SR configuration for SR transmission periodicity and SR subslot offset is defined in Table 10.1.5-1B by the parameter sr-ConfigIndexSubslot given by higher layers.

Subslot-SR transmission instances are the uplink slots satisfying

, where is the subslot index within a subframe.

Table 10.1.5-1: UE-specific SR periodicity and subframe offset configuration for subframe-SR

SR configuration Index	SR periodicity (ms)	SR subframe offset
0 – 4	5
5 – 14	10
15 – 34	20
35 – 74	40
75 – 154	80
155 – 156	2
157	1

Table 10.1.5-1A: UE-specific SR periodicity and slot offset configuration for slot-SR

SR configuration Index	SR periodicity (number of slots)	SR slot offset
0	1
1 – 2	2
3 – 6	4
7 – 16	10
17 – 36	20

Table 10.1.5-1B: UE-specific SR periodicity and subslot offset configuration for subslot-SR

SR configuration Index	SR periodicity (number of subslots)	SR subslot offset
0	1
1 – 2	2
3 – 5	3
6 – 9	4
10 – 14	5
15 – 20	6
21 – 32	12
33 – 62	30
63 – 122	60

7.1.4.40.3 Test description

7.1.4.40.3.1 Pre-test conditions

System Simulator:

– Cell 1

– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.4.40.3.3-1

UE:

None

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.40.3.2 Test procedure sequence

Table 7.1.4.40.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	SS transmits a MAC PDU containing 10 MAC SDUs each containing a RLC SDU	<–	MAC PDU (containing 10 MAC SDUs)	–	–
–	EXCEPTION: Step 2 runs in parallel with behaviour in table 7.1.4.40.3.2-2	–	–	–	–
2	Check: Does the UE transmit 7 SR separately on 7 consecutively available SPUCCHs? Note 1	->	SR	1	P
3	The SS transmits an UL Grant to allocate UL-SCH resources that are enough to transmit MAC PDU containing 10 MAC SDUs	<–	UL Grant	–	–
4	Check: Does the UE transmit a MAC PDU containing 10 RLC PDUs?	–>	MAC PDU(containing 10 RLC PDUs)	1	P
5	Check: For 1 second, does the UE transmit any Scheduling Request?	->	SR	1,2	F
Note 1: The UE repeats the scheduling requests on every available SPUCCH as long as SSR_COUNTER < dssr-TransMax and there is UL data available for transmission and there are no resources available to transmit it. At the reception of first Scheduling Request from the UE, SS will be scheduled to transmit a grant after 60ms. Hence SS will receive 7 Scheduling Requests when SR periodicity is set as 10ms.

Table 7.1.4.40.3.2-2: Parallel behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	Check: Does the UE transmit a MAC PDU?	–>	MAC PDU	1	F

7.1.4.40.3.3 Specific Message Contents

Table 7.1.4.40.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.6.3-17
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated-DRB SEQUENCE {
drb-ToAddModList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {
logicalChannelConfig	LogicalChannelConfig-DRB
}
}
}
}
}
}

Table 7.1.4.40.3.3-2: LogicalChannelConfig-DRB (Table 7.1.4.40.3.3-1)

Derivation Path: 36.508 Table 4.8.2.1.4-1
Information Element	Value/remark	Comment	Condition
LogicalChannelConfig-DRB ::= SEQUENCE {
ul-SpecificParameters SEQUENCE {
priority	6		HI
	13		LO
prioritisedBitRate	kBps0	PBR is disabled.
bucketSizeDuration	ms100
logicalChannelGroup	1		HI
	2		LO
}
logicalChannelSR-Restriction-r15 CHOICE{
setup SEQUENCE {
logicalChannelSR-Restriction-r15	pucch
}
}
}

Table 7.1.4.40.3.3-3: PhysicalConfigDedicated (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated ::= SEQUENCE {
PhysicalConfigDedicatedSTTI-r15 SEQUENCE {
schedulingRequestConfig-v1530	SchedulingRequestConfig-v1530
shortTTI-r15 SEQUENCE {			FDD_subslot
dl-STTI-Length-r15	subslot
ul-STTI-Length-r15	subslot
}
}
}

Condition	Explanation
FDD_subslot	FDD cell environment and UEs supporting {subslot, subslot} combination

Table 7.1.4.40.3.3-4: SchedulingRequestConfig-v1530 to be used in RRCConnectionReconfiguration in preamble (Table 7.1.4.40.3.3-3)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
SchedulingRequestConfig-v1530::= CHOICE {
setup SEQUENCE {
sr-SlotSPUCCH-IndexFH-r15	See subclause 4.6.8 [18]	Channel-bandwidth-dependent parameter
sr-SlotSPUCCH-IndexNoFH-r15	See subclause 4.6.8 [18]	Channel-bandwidth-dependent parameter
sr-SubslotSPUCCH-ResourceList-r15 SEQUENCE (SIZE(1..4)) OF	1 entry		FDD_subslot
	See subclause 4.6.8 [18]
sr-ConfigIndexSlot-r15	21
sr-ConfigIndexSubslot-r15	76		FDD_subslot
dssr-TransMax-r15	n64
}
}

7.1.4.41 Short TTI / Correct handling of UL assignment / HARQ sharing between PUSCH and slot/subslot-PUSCH

7.1.4.41.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE receives an uplink grant on PDCCH with NDI not toggled, and the previous PUSCH transmission of the transport block is scheduled by the uplink grant on SPDCCH }

then { UE retransmits the PUSCH corresponding to the uplink grant on PDCCH }

}

7.1.4.41.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.213 clause 5.4.1 and 3GPP TS 36.211 clause 5.5.2.

[TS 36.213, clause 5.4.1]

– if an uplink grant for this TTI and this Serving Cell has been received on the PDCCH for the MAC entity’s C-RNTI or Temporary C-RNTI; or

– if an uplink grant for this TTI has been received in a Random Access Response:

– consider the NDI to have been toggled for the corresponding HARQ process regardless of the value of the NDI.

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

– if the NDI in the received HARQ information is 1:

– consider the NDI for the corresponding HARQ process not to have been toggled;

– deliver the uplink grant and the associated HARQ information to the HARQ entity for this TTI.

…

NOTE 1: The period of configured uplink grants is expressed in TTIs.

[TS 36.213, clause 8.0]

For a serving cell, and a UE configured with higher layer parameter shortTTI, the UE is not expected to transmit PUSCH corresponding to PDCCH/SPDCCH with CRC scrambled by the C-RNTI/SPS C-RNTI and with uplink DCI format 7-0A/7-0B

– in UpPTS of the special subframe in frame structure type 2 with special subframe configuration 0-9 or,

– for a transport block corresponding to a HARQ process with NDI not toggled if the previous PUSCH transmission of the transport block was signalled via PDCCH in UE specific search space with CRC scrambled by the C-RNTI/SPS C-RNTI with DCI format other than DCI format 7-0A/7-0B when the number of codewords for the previous PUSCH transmission is two or the transport block size is larger than the maximum transport block size supported for slot/subslot-PUSCH transmission.

7.1.4.41.3 Test description

7.1.4.41.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

7.1.4.41.3.2 Test procedure sequence

Table 7.1.4.41.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	SS transmits a MAC PDU containing a RLC SDU.	<–	MAC PDU	–	–
3	The SS transmits an UL Grant by using DCI 7-0A with NDI toggled on SPDCCH, allowing the UE to return the RLC SDU as received in step 2.	<–	UL Grant (SPDCCH)	–	–
4	Check: Does the UE transmit the MAC PDU according to the DCI indication in step 3?	–>	MAC PDU (initial transmission)	1	P
5	The SS transmits an UL Grant by using DCI 0 with NDI not toggled and the same assignment of MCS and PRBs as DCI format 7-0A in step 1, and the PDCCH is mapped on UE-specific search space.	<–	UL Grant (SPDCCH)	–	–
6	Check: Does the UE retransmit the MAC PDU according to the DCI indication in step 5?		MAC PDU (retransmission)	1	P

7.1.4.41.3.3 Specific Message Contents

Table 7.1.4.41.3.3-1: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1, step 8)

Derivation path: 36.508 table 4.8.2.1.5-1
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
RadioResourceConfigDedicated SEQUENCE {
mac-MainConfig SEQUENCE {
timeAlignmentTimerDedicated	Infinity
}
}
}
}
}
}

Table 7.1.4.41.3.3-2: PhysicalConfigDedicated (preamble: Table 4.5.3.3-1, step 8)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with condition Short-TTI
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated ::= SEQUENCE {
PhysicalConfigDedicatedSTTI-r15 SEQUENCE {
pucch-ConfigDedicated-v1530 SEQUENCE {
n1PUCCH-AN-SPT-r15	2
codebooksizeDeterminationSTTI-r15	Not present
}
shortProcessingTime-r15	TRUE
shortTTI-r15 SEQUENCE {			FDD_subslot
dl-STTI-Length-r15	subslot
ul-STTI-Length-r15	subslot
}
}
}

Condition	Explanation
FDD_subslot	FDD cell environment and UEs supporting {subslot, subslot} combination

7.1.4.42 Enhanced Coverage / UL Flexible starting PRB

7.1.4.42.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE has pending data for transmission and receives an uplink grant with RIV calculated by values of and }

then { UE transmits MAC PDU on PUSCH on the granted resources using DCI format 6-0A and the received resource allocation information }

}

7.1.4.42.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.213, clause 8.1.1.

[TS 36.213, clause 8.1.1]

The resource allocation information for uplink resource allocation type 0 indicates to a scheduled UE a set of contiguously allocated virtual resource block indices denoted by . A resource allocation field in the scheduling grant consists of a resource indication value (RIV) corresponding to a starting resource block () and a length in terms of contiguously allocated resource blocks (≥ 1).

For a BL/CE UE,

– uplink resource allocation type 0 is only applicable for UE configured with CEModeA, and

– , if the UE in TDD is configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig; otherwise and,

– if the UE is configured with higher layer parameters ce-PUSCH-FlexibleStartPRB-AllocConfig, shall not exceed with ={, where is the number of edge RB(s) not belonging to any narrowband in one side of system bandwidth , and is the number of narrowbands. PUSCH resource allocations shall not contain PRB(s) not belonging to any narrowband unless it is the centre PRB in the uplink system bandwidth, and,

– if the UE is not configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, is always set to 6 in this subclause regardless of the system bandwidth.

For PDCCH/SPDCCH DCI format 7-0A/7-0B and , VRB allocations for a UE vary from 4 VRB(s) up to VRBs with an increment step of 4 VRBs. A type 0 resource block assignment field consists of a resource indication value (RIV) corresponding to a starting resource block using and a length in terms of virtually contiguously allocated resource blocks , where is defined if configured by higher layer parameter resourceAllocationOffset; otherwise set to 0. The resource indication value is defined by:

if then

else

where , and , and where,

≥ 1 and shall not exceed .

Otherwise, the resource indication value is defined by

if then

if a BL/CE UE in TDD is configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, then

else

7.1.4.42.3 Test description

7.1.4.42.3.1 Pre-test conditions

System Simulator:

Cell 1

– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1.

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4-CE) according to [18].

7.1.4.42.3.2 Test procedure sequence

Table 7.1.4.42.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS ignores scheduling requests and does not allocate any uplink grant.	–	–	–	–
2	The SS transmits a MAC PDU.	<–	MAC PDU	–	–
3	The SS allocates an uplink grant indicating DCI Format 6-0A with a RIV calculated by values of and set according to clause 8.1.1 in TS 36.213, with the UE configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig.	<–	(UL Grant)	–	–
4	CHECK: Does UE return the same MAC PDU as received in step 1?	–>	MAC PDU	1	P

7.1.4.42.3.3 Specific message contents

Table 7.1.4.42.3.3-1: RadioResourceConfigCommon-DEFAULT (preamble)

Derivation Path : 36.508 table 4.6.3-13 with condition FullConfig and CEmodeA

Table 7.1.4.42.3.3-2: PhysicalConfigDedicated-DEFAULT (preamble)

Derivation Path: 36.508 Table 4.8.2.1.6-1 with CEmodeA
Information Element	Value/Remark	Comment	Condition
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {
pusch-ConfigDedicated-v1530 CHOICE {
ce-PUSCH-FlexibleStartPRB-AllocConfig-r15 CHOICE {
setup SEQUENCE{
offsetCE-ModeB-r15	1
}
}
}
}