17.2 MBMS Data Reception

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

17.2.1 UE Acquire the MBMS data based on the SIB13 and MCCH message /MCCH and MTCH are on the same MCH

17.2.1.1 Test Purpose (TP)

(1)

with { UE receiving an MBMS service }

ensure that {

when { UE receives a MAC PDU on MCH, multiplexing both MCCH and MTCH RLC PDU’s }

then { UE successfully de-multiplexes the MCCH and MTCH data}

}

17.2.1.2 Conformance requirements

References:

The conformance requirements covered in the present TC are specified in: TS 36.321, clause 5, 12, 6.1.2, 6.1.3.7 and 6.2.1.

[TS 36.321, clause 5.12]

MCH transmission may occur in subframes configured by upper layer for MCCH or MTCH transmission. For each such subframe, upper layer indicates if signallingMCS or dataMCS applies. The transmission of an MCH occurs in a set of subframes known as the MCH subframe allocation (MSA), defined by PMCH-Config. An MCH Scheduling Information MAC control element is included at the beginning of the MCH scheduling period in the first subframe of each MSA to indicate the position of each MTCH and unused subframes on the MCH. The UE shall assume that the first scheduled MTCH starts immediately after the MCCH or the MCH Scheduling Information MAC control element if the MCCH is not present, and the other scheduled MTCH(s) start at the earliest in the subframe where the previous MTCH stops. When the UE needs to receive MCH, the UE shall:

– attempt to decode the TB on the MCH;

– if a TB on the MCH has been successfully decoded:

– demultiplex the MAC PDU and deliver the MAC SDU(s) to upper layers.

[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 subheaders; each subheader corresponds to either a MAC SDU, a MAC control element or padding.

A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU and for fixed sized MAC control elements. The last subheader in the MAC PDU and subheaders 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 subheader

Figure 6.1.2-2: R/R/E/LCID MAC subheader

MAC PDU subheaders have the same order as the corresponding MAC SDUs, MAC control elements and padding.

MAC control elements are always placed before any MAC SDU.

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. A maximum of one MCH MAC PDU can be transmitted per TTI.

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.1.3.7]

The MCH Scheduling Information MAC Control Element illustrated in Figure 6.1.3.7-1 is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-4. This control element has a variable size. For each MTCH the fields below are included:

– LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits;

– Stop MTCH: this field indicates the ordinal number of the subframe within the MCH scheduling period where the corresponding MTCH stops. The length of the field is 11 bits. The special Stop MTCH value 2047 indicates that the corresponding MTCH is not scheduled. The value range 2043 to 2046 is reserved.

Figure 6.1.3.7-1: MCH Scheduling Information MAC control element

[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. 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;

– 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;

– 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 bit, set to "0".

The MAC header and subheaders are octet aligned.

…

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
11111	Padding
NOTE: If there is no MCCH on MCH, an MTCH could use this value.

17.2.1.3 Test description

17.2.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 15 as defined in TS 36.508[18] clause 4.4.3.1 is used

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH in Cell 1.

UE:

– none

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18], with the UE TEST LOOP MODE C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

17.2.1.3.2 Test procedure sequence

Table 17.2.1.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	In the current MCCH modification period SS transmits MCCH Modification notification for notification indicator 0	–	MCCH Modification notification	–	–
2	In frame number SFN Mod 512 =1(FDD)/0(TDD) ; i.e. start of next MCCH modification period, the SS transmits a valid MAC PDU including ‘MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘11111111111’ andMCCH RLC PDU(carrying MBSFNAreaConfiguration)	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘11111111111’, MCCH RLC PDU)	–	–
–	Exception; Step 3 is repeated 15 times	–	–	–	–
3	In frame with SFN Mod 32 =1(FDD)/0(TDD), the SS transmits MCH MAC PDU containing MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000000’,MCCH RLC PDU (carrying MBSFNAreaConfiguration) and MTCH RLC PDU carrying 1 MBMS packet.	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘00000000000’,MCCH RLC PDU and MTCH RLC PDU)	–	–
4	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
5	Check: Does the UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE with number of reported MBMS Packets received on the MTCH is greater than zero?	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	1	P
Note 1: The Imcs used in steps 2 and 3 is signallingMCS-r9. Note 2: The subframe number for steps 2 and 3 is determined by subframeAllocation which is 1 (FDD)/ 8 (TDD).

17.2.1.3.3 Specific message contents

Table 17.2.1.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS.

Table 17.2.1.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C

Table 17.2.1.3.3-1b: CLOSE UE TEST LOOP (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C

Table 17.2.1.3.3-3: MBSFNAreaConfiguration (steps 2 and 3, Table 17.2.1.3.2-1)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf32
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
sf-AllocEnd-r9	7
dataMCS-r9	0
mch-SchedulingPeriod-r9	rf32	E-UTRAN configures mch-SchedulingPeriod of the (P)MCH listed first in PMCH-InfoList to be smaller than or equal to mcch-RepetitionPeriod.
}
}
}
}

17.2.2 UE Acquire the MBMS data based on the SIB13 and MCCH message /MCCH and MTCH are on different MCHs

17.2.2.1 Test Purpose (TP)

(1)

with { UE receiving an MBMS service }

ensure that {

when { UE receives a MAC PDU on MCH, containing MCCH PDU’s }

then { UE succesfully de-multiplexes the MCCH data}

when { UE receives a MAC PDU on MCH, containing MTCH PDU’s }

then { UE succesfully de-multiplexes the MTCH data}

}

17.2.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.321, clause 5.12, 6.1.2, 6.1.3.7 and 6.2.1.

[TS 36.321, clause 5.12]

– attempt to decode the TB on the MCH;

– if a TB on the MCH has been successfully decoded:

– demultiplex the MAC PDU and deliver the MAC SDU(s) to upper layers.

[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 subheaders; each subheader corresponds to either a MAC SDU, a MAC control element or padding.

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

Figure 6.1.2-2: R/R/E/LCID MAC subheader

MAC PDU subheaders 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. A maximum of one MCH MAC PDU can be transmitted per TTI.

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.1.3.7]

– LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits;

Figure 6.1.3.7-1: MCH Scheduling Information MAC control element

[TS 36.321, clause 6.2.1]

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

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

The MAC header and subheaders are octet aligned.

…

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
11111	Padding
NOTE: If there is no MCCH on MCH, an MTCH could use this value.

17.2.2.3 Test description

17.2.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 15 as defined in TS 36.508[18] clause 4.4.3.1 is used

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH in Cell 1.

UE:

– none

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18], with the UE TEST LOOP MODE C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

17.2.2.3.2 Test procedure sequence

Table 17.2.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	In the current MCCH modification period SS transmits MCCH Modification notification for notification indicator 0	–	MCCH Modification notification	–	–
2	In frame number SFN Mod 512 =1(FDD)/0(TDD) ; i.e. start of next MCCH modification period, the SS transmits a valid MAC PDU including ‘MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘11111111111’ and MCCH RLC PDU(carrying MBSFNAreaConfiguration)	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘11111111111’, MCCH RLC PDU)	–	–
–	Exception; Steps 3 and 4 are repeated 15 times	–	–	–	–
3	In frame with SFN MOD 32 =1(FDD)/0(TDD ), the SS transmits MCH MAC PDU containing MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘00000000001’, and MCCH RLC PDU(carrying MBSFNAreaConfiguration)	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘00000000001’, MCCH RLC PDU)	–	–
4	In frame with SFN MOD 32 =5 (FDD)/4 (TDD) the SS transmits MCH MCCH PDU containing MTCH RLC PDUcarrying 1 MBMS packet	<–	MAC PDU (MTCH RLC PDU)	–	–
5	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
6	Check: Does the UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE with number of reported MBMS Packets received on the MTCH is greater than zero?	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	1	P
Note 1: The Imcs used in steps 2 and 3 is signallingMCS-r9 and that in step 4 is dataMCS-r9. Note 2: The subframe number for steps 2,3 and 4 is determined by subframeAllocation which is 1 (FDD)/ 9 (TDD).

17.2.2.3.3 Specific message contents

Table 17.2.2.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS

Table 17.2.2.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C.

Table 17.2.2.3.3-1b: CLOSE UE TEST LOOP (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C

Table 17.2.2.3.3-3: MBSFNAreaConfiguration (steps 2 and 3, Table 17.2.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf16
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
sf-AllocEnd-r9	3
dataMCS-r9	0
mch-SchedulingPeriod-r9	rf32	E-UTRAN configures mch-SchedulingPeriod of the (P)MCH listed first in PMCH-InfoList to be smaller than or equal to mcch-RepetitionPeriod.
}
}
}
}

17.2.3 UE receives the MBMS data when this data is in the beginning of the MSP

17.2.3.1 Test Purpose (TP)

(1)

with { UE receiving an MBMS service }

ensure that {

when { UE receives a MAC PDU on MCH, containing MTCH PDU’s at the start of MCH scheduling period}

then { UE successfully de-multiplexes the MTCH data}

}

17.2.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.321, clause 5.12, 6.1.2, 6.1.3.7 and 6.2.1.

[TS 36.321, clause 5.12]

– attempt to decode the TB on the MCH;

– if a TB on the MCH has been successfully decoded:

– demultiplex the MAC PDU and deliver the MAC SDU(s) to upper layers.

[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 subheaders; each subheader corresponds to either a MAC SDU, a MAC control element or padding.

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

Figure 6.1.2-2: R/R/E/LCID MAC subheader

MAC PDU subheaders 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. A maximum of one MCH MAC PDU can be transmitted per TTI.

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.1.3.7]

– LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits;

Figure 6.1.3.7-1: MCH Scheduling Information MAC control element

[TS 36.321, clause 6.2.1]

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

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

The MAC header and subheaders are octet aligned.

…

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
11111	Padding
NOTE: If there is no MCCH on MCH, an MTCH could use this value.

17.2.3.3 Test description

17.2.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 15 as defined in TS 36.508[18] clause 4.4.3.1 is used.

– MBSFNAreaConfiguration as defined in TS 36.508[18] table 4.6.1-4A is transmitted on MCCH in Cell 1.

UE:

– none

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18], with the UE TEST LOOP MODE C.

– The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

17.2.3.3.2 Test procedure sequence

Table 17.2.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	In the current MCCH modification period SS transmits MCCH Modification notification for notification indicator 0	–	MCCH Modification notification	–	–
2	In frame number SFN Mod 512 =1(FDD)/0(TDD) ; i.e. start of next MCCH modification period, the SS transmits a valid MAC PDU including ‘MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘11111111111’ , MCCH RLC PDU(carrying MBSFNAreaConfiguration)	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘11111111111’, MCCH RLC PDU)	–	–
–	Exception; Steps 3 and 4 are repeated 8 times	–	–	–	–
3	In frame with SFN MOD 32 is not =1(FDD)/0(TDD) and SFN MOD 16 =1(FDD)/0(TDD), the SS transmits MCH MAC PDU containing ‘MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000000’ and MTCH RLC PDU carrying 1 MBMS packet	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘00000000000’, MTCH RLC PDU)	–	–
4	In frame with SFN MOD 32 =1(FDD)/0(TDD) the SS transmits MCH MCCH PDU containing ‘MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000000’, MCCH RLC PDU(carrying MBSFNAreaConfiguration) and MTCH RLC PDU carrying 1 MBMS packet	<–	MAC PDU (MCH Scheduling Information MAC Control Element: LCID=’00001’, Stop MTCH= ‘00000000000’, MCCH RLC PDU, MTCH RLC PDU)	–	–
5	The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.	<–	UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST	–	–
6	Check: Does the UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE with number of reported MBMS Packets received on the MTCH is greater than zero?	–>	UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE	1	P
Note 1: The Imcs used in steps 2 ,3 and 4 is signallingMCS-r9. Note 2: The subframe number for steps 2,3 and 4 is determined by subframeAllocation which is 1 (FDD)/ 8 (TDD).

17.2.3.3.3 Specific message contents

Table 17.2.3.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS

Table 17.2.3.3.3-1a: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE C

Table 17.2.3.3.3-1b: CLOSE UE TEST LOOP (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE C

Table 17.2.3.3.3-3: MBSFNAreaConfiguration (steps 2 and 4, Table 17.2.3.3.2-1)

Derivation Path: 36.508 table 4.6.1-4A
Information Element	Value/remark	Comment	Condition
MBSFNAreaConfiguration-r9 ::= SEQUENCE {
commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {
commonSF-AllocPeriod-r9	rf16
pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {
pmch-Config-r9 SEQUENCE {
sf-AllocEnd-r9	3
dataMCS-r9	0
mch-SchedulingPeriod-r9	rf16
}
}
}
}

17.2.4 Reception of PDCCH DCI format 0 and PHICH in MBSFN subframes

17.2.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC_CONNECTED state and in a subframe configured as MBSFN subframe }

ensure that {

when { UE receives a PDCCH DCI format 0 }

then { UE performs uplink data transmission as per DCI format 0 received }

}

(2)

with { UE in E-UTRAN RRC_CONNECTED state and in a subframe configured as MBSFN subframe }

ensure that {

when { UE receives a PHICH for an uplink data transmission made }

then { UE acts upon the PHICH information }

}

17.2.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.211 clause 6.1.1, 6.7, TS 36.331 clause 5.2.2.9 and TS 36.213 clause 8.3.

[TS 36.211, clause 6.1.1]

A subset of the downlink subframes in a radio frame on a carrier supporting PDSCH transmission can be configured as MBSFN subframes by higher layers. Each MBSFN subframe is divided into a non-MBSFN region and an MBSFN region.

– The non-MBSFN region spans the first one or two OFDM symbols in an MBSFN subframe where the length of the non-MBSFN region is given by Table 6.7-1. Transmission in the non-MBSFN region shall use the same cyclic prefix length as used for subframe 0.

– The MBSFN region in an MBSFN subframe is defined as the OFDM symbols not used for the non-MBSFN region.

[TS 36.211, clause 6.7]

The physical control format indicator channel carries information about the number of OFDM symbols used for transmission of PDCCHs in a subframe. The set of OFDM symbols possible to use for PDCCH in a subframe is given by Table 6.7-1.

Table 6.7-1: Number of OFDM symbols used for PDCCH

Subframe	Number of OFDM symbols for PDCCH when	Number of OFDM symbols for PDCCH when
Subframe 1 and 6 for frame structure type 2	1, 2	2
MBSFN subframes on a carrier supporting PDSCH, configured with 1 or 2 cell-specific antenna ports	1, 2	2
MBSFN subframes on a carrier supporting PDSCH, configured with 4 cell-specific antenna ports	2	2
Subframes on a carrier not supporting PDSCH	0	0
Non-MBSFN subframes (except subframe 6 for frame structure type 2) configured with positioning reference signals	1, 2, 3	2, 3
All other cases	1, 2, 3	2, 3, 4

The PCFICH shall be transmitted when the number of OFDM symbols for PDCCH is greater than zero.

[TS 36.331, clause 5.2.2.9]

Upon receiving SystemInformationBlockType2, the UE shall:

…

1> if the mbsfn-SubframeConfigList is included:

2> consider that no other DL assignments occur in the MBSFN subframes indicated in the mbsfn-SubframeConfigList:

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

For Frame Structure type 2 UL/DL configuration 0, an ACK/NACK received on the PHICH in the resource corresponding to , as defined in Section 9.1.2, 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. If, for Frame Structure type 2 UL/DL configuration 0, an ACK/NACK received on the PHICH in the resource corresponding to , as defined in Section 9.1.2, assigned to a UE in subframe i is associated with the PUSCH transmission in the subframe i-6.

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

The physical layer in the UE shall deliver indications to the higher layers as follows:

For downlink subframe i, if a transport block was transmitted in the associated PUSCH subframe then:

– if ACK is decoded on the PHICH in subframe i, ACK shall be delivered to the higher layers;

– else NACK shall be delivered to the higher layers.

17.2.4.3 Test description

17.2.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 15 as defined in TS 36.508[18] clause 4.4.3.1 is used.

UE:

None.

Preamble:

– The generic procedure to get the UE in state Loopback Activated (state 4) according to [18] with UE TEST LOOP MODE A, is executed with parameters as specified in the generic procedure except that BSR and PHR sending is disabled.

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

17.2.4.3.2 Test procedure sequence

Table 17.2.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message in a paging occasion including a systemInfoModification.	<–	Paging	–	–
2	From the beginning of the next modification period the SS transmits a modified SystemInformationBlockType2 and SystemInformationBlockType13 as specified.	–	–	–	–
2A	Wait 13 s for UE to receive the modified system information (Note).	–	–	–	–
3	The SS Transmits a valid MAC PDU containing RLC PDU	<–	MAC PDU	–	–
4	The SS is configured for Uplink Grant Allocation Type 3. The SS allocates an UL Grant (DCI format 0) in SFN x, sub frame 8 (FDD)/9(TDD).	<–	Uplink Grant	–	–
5	Check: Does the UE transmit a MAC PDU including one RLC SDU, as per grant in step 4?	–>	MAC PDU	1	P
6	The SS transmits a NACK corresponding to MAC PDU in step 5 in SFN x+1, sub frame 6 (FDD)/9(TDD).	<–	HARQ NACK	–	–
7	Check: Does the UE retransmit the MAC PDU?	–>	MAC PDU	2	P
8	The SS transmits a NACK corresponding to MAC PDU in step 7 in SFN x+2, sub frame 4 (FDD)/ SFN x+2, sub frame 9(TDD).	<–	HARQ NACK	–	–
9	The UE retransmit the MAC PDU.	–>	MAC PDU	–	–
10	The SS transmits an ACK corresponding to MAC PDU in step 9 in SFN x+3, sub frame 2 (FDD)/ SFN x+3, sub frame 9(TDD).	<–	HARQ ACK	–	–
11	Check: Does the UE retransmit the MAC PDU ?	–>	MAC PDU	2	F
12	The SS transmits a Paging message in a paging occasion including a systemInfoModification.	<–	Paging	–	–
13	From the beginning of the next modification period the SS transmits a defaultSystemInformationBlockType2 and SystemInformationBlockType13 as in TS 36.508, table 4.4.3.3-1 and table 4.4.3.3-13 respectively.	–	–	–	–
14	Wait 13 s for UE to receive the modified system information (Note)	–	–	–	–
Note: Minimum delay 12,8 sec. = 2.5 * BCCH modification period (512 rf) to ensure UE detected modified SIB2.

17.2.4.3.3 Specific message contents

Table 17.2.4.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1, condition MBMS

Table 17.2.4.3.3-2: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE A.

Table 17.2.4.3.3-3: CLOSE UE TEST LOOP (preamble)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE A

Table 17.2.4.3.3-4: SystemInformationBlockType2 for Cell 1 (step 2, Table 17.2.4.3.2-3)

Derivation Path: 36.508 table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
mbsfn-SubframeConfiguration SEQUENCE {
radioframeAllocationPeriod	n1
radioframeAllocationOffset	0
subframeAllocation CHOICE{
oneFrame	‘010101’	corresponds to subframes 2, 6 and 8	FDD
oneFrame	‘000010’	corresponds to subframe 9	TDD
}
}
}

Table 17.2.4.3.3-5: SystemInformationBlockType13 for Cell 1 (step 2)

Derivation Path: 36.331 clause 6.3.1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType13 ::= SEQUENCE {
mbsfn-AreaInfoList-r9 SEQUENCE (SIZE(1..maxMBSFN-Area)) OF SEQUENCE {
mcch-Config-r9 SEQUENCE {
sf-AllocInfo-r9	‘010101’B		FDD
	‘000010’B		TDD
}
}
}