7.1.4a DL-SCH and 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
7.1.4a.1 Correct downlink reception and uplink transmission when specific valid subframes are signalled for BL UE
7.1.4a.1 Test Purpose (TP)
(1)
with { BL UE in E-UTRA RRC_CONNECTED state with DRB established }
ensure that {
when { valid subframes for FDD downlink or TDD transmissions are signalled in SIB1-BR in IE fdd-DownlinkOrTddSubframeBitmapBR-r13 as 10 bit subframe pattern and }
then { UE performs reception in the valid subframes }
}
(2)
with { BL UE in E-UTRA RRC_CONNECTED state with DRB established }
ensure that {
when { valid subframes for FDD downlink or TDD transmissions are signalled in SIB1-BR in IE fdd-DownlinkOrTddSubframeBitmapBR-r13 as 40 bit subframe pattern and }
then { UE performs reception in the valid subframes }
}
(3)
with { BL UE in E-UTRA RRC_CONNECTED state with DRB established in a FDD cell}
ensure that {
when { valid subframes for FDD uplink transmissions are signalled in SIB1-BR in IE fdd-UplinkSubframeBitmapBR-r13}
then { UE transmits in valid uplink subframes }
}
7.1.4a.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.3a, TS 36.213, clause 7.1, 7.1.11, 8.0, 10.1.3.1, 10.2.
[TS 36.331, clause 5.2.3a]
When acquiring an SI message, the BL UE or UE in CE or NB-IoT UE shall:
1> determine the start of the SI-window for the concerned SI message as follows:
2> for the concerned SI message, determine the number n which corresponds to the order of entry in the list of SI messages configured by schedulingInfoList in SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT);
2> determine the integer value x = (n – 1)*w, where w is the si-WindowLength-BR (or si-WindowLength in NB-IoT);
2> if the UE is a NB-IoT UE:
3> the SI-window starts at the subframe #0 in the radio frame for which (H-SFN * 1024 + SFN) mod T = FLOOR(x/10) + Offset, where T is the si-Periodicity of the concerned SI message and, Offset is the offset of the start of the SI-Window (si-RadioFrameOffset);
2> else:
3> the SI-window starts at the subframe #0 in the radio frame for which SFN mod T = FLOOR(x/10), where T is the si-Periodicity of the concerned SI message;
1> if the UE is a NB-IoT UE:
2> receive and accumulate SI message transmissions on DL-SCH from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is given by si-WindowLength, starting from the radio frames as provided in si-RepetitionPattern and in subframes as provided in downlinkBitmap, or until successful decoding of the accumulated SI message transmissions excluding the subframes used for transmission of NPSS, NSSS, MasterInformationBlock-NB and SystemInformationBlockType1-NB. If there are not enough subframes for one SI message transmission in the radio frames as provided in si-RepetitionPattern, the UE shall continue to receive the SI message transmission in the radio frames following the radio frame indicated in si-RepetitionPattern;
1> else:
2> receive and accumulate SI message transmissions on DL-SCH on narrowband provided by si-Narrowband, from the start of the SI-window and continue until the end of the SI-window whose absolute length in time is given by si-WindowLength-BR, only in radio frames as provided in si-RepetitionPattern and subframes as provided in fdd-DownlinkOrTddSubframeBitmapBR in bandwidthReducedAccessRelatedInfo, or until successful decoding of the accumulated SI message transmissions;
1> if the SI message was not possible to decode from the accumulated SI message transmissions by the end of the SI-window, continue reception and accumulation of SI message transmissions on DL-SCH in the next SI-window occasion for the concerned SI message;
[TS 36.213, clause 7.1]
Except the subframes indicated by the higher layer parameter mbsfn-SubframeConfigList or by mbsfn-SubframeConfigList-v12x0 or by laa-SCellSubframeConfig of serving cell 
, a UE shall:
– upon detection of a PDCCH of the serving cell with DCI format 1, 1A, 1B, 1C, 1D, 2, 2A, 2B, 2C, or 2D intended for the UE in a subframe, or
– upon detection of an EPDCCH of the serving cell with DCI format 1, 1A, 1B, 1D, 2, 2A, 2B, 2C, or 2D intended for the UE in a subframe
decode the corresponding PDSCH in the same subframe with the restriction of the number of transport blocks defined in the higher layers.
For BL/CE UEs , the higher layers indicate the set of BL/CE DL subframes according to fdd-DownlinkOrTddSubframeBitmapBR [11].
A BL/CE UE shall upon detection of a MPDCCH with DCI format 6-1A, 6-1B, 6-2 intended for the UE, decode the corresponding PDSCH in one more BL/CE DL subframes as described in subclause 7.1.11, with the restriction of the number of transport blocks defined in the higher layers.
[TS 36.213, clause 7.1.11]
A BL/CE UE shall upon detection of a MPDCCH with DCI format 6-1A/6-1B/6-2 intended for the UE, decode the corresponding PDSCH in subframe(s) n+ki with i = 0, 1, …, N-1 according to the MPDCCH, where
– subframe n is the last subframe in which the MPDCCH is transmitted and is determined from the starting subframe of MPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; and
– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE DL subframe(s) where, x=k0<k1<…,kN-1 and the value of 
is determined by the repetition number field in the corresponding DCI, where 
are given in Table 7.1.11-1, Table 7.1.11-2 and Table 7.1.11-3, respectively and subframe n+x is the second BL/CE DL subframe after subframe n.
If PDSCH carrying SystemInformationBlockType1-BR is transmitted in one narrowband in subframe n+ki, a BL/CE UE shall assume any other PDSCH in the same narrowband in the subframe n+ki is dropped. If PDSCH carrying SI message is transmitted in one narrowband in subframe n+ki, a BL/CE UE shall assume any other PDSCH not carrying SystemInformationBlockType1-BR in the same narrowband in the subframe n+ki is dropped.
For single antenna port (port 0), transmit diversity and closed-loop spatial multiplexing transmission schemes, if a PDSCH is transmitted in BL/CE DL subframe n+ki and BL/CE DL subframe n+ki is configured as an MBSFN subframe, a BL/CE UE shall assume that the PDSCH in subframe n+ki is dropped.
Table 7.1.11-1: PDSCH repetition levels (DCI Format 6-1A)
|
Higher layer parameter ‘pdsch-maxNumRepetitionCEmodeA’ |
|
|
Not configured |
{1,2,4,8} |
|
16 |
{1,4,8,16} |
|
32 |
{1,4,16,32} |
Table 7.1.11-2: PDSCH repetition levels (DCI Format 6-1B)
|
Higher layer parameter ‘pdsch-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} |
Table 7.1.11-3: PDSCH repetition levels (DCI Format 6-2)
|
2-bit “DCI subframe repetition number” field in DCI Format 6-2 |
|
|
00 |
{1,2,4,8,16,32,64,128} |
|
01 |
{4,8,16,32,64,128,192,256} |
|
10 |
{32,64,128,192,256,384,512,768} |
|
11 |
{192,256,384,512,768,1024,1536,2048} |
[TS 36.213, clause 8.0]
For BL/CE UEs, the higher layers indicate the set of BL/CE UL subframes according to fdd-DownlinkOrTddSubframeBitmapBR and fdd-UplinkSubframeBitmapBR [11].
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+ki 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≤k0<k1<…,kN-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+ki with i=0,1,…,N-1 are N consecutive BL/CE UL subframe(s) starting with subframe n+x, and in case N=1, k0=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 in that subframe.
– For a BL/CE UE in half-duplex FDD operation, in case a PUSCH transmission including half-duplex guard subframe without a corresponding MPDCCH collides partially or fully with a PDSCH transmission with a corresponding MPDCCH, the PUSCH transmission without a corresponding MPDCCH 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 } |
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 10.1.3.1]
HARQ-ACK transmission on two antenna ports is supported for PUCCH format 1a/1b with TDD HARQ-ACK bundling feedback mode and for PUCCH format 3.
A UE that supports aggregating more than one serving cell with frame structure type 2 can be configured by higher layers for HARQ-ACK transmission on two antenna ports for PUCCH format 1b with channel selection.
The TDD HARQ-ACK procedure for a UE configured with PUCCH format 3 is as described in subclause 10.1.3.2.2 when the UE receives PDSCH and/or SPS release PDCCH/EPDCCH only on the primary cell.
If the UE is not configured with the higher layer parameter EIMTA-MainConfigServCell-r12, for TDD HARQ-ACK bundling or TDD HARQ-ACK multiplexing for one configured serving cell and a subframe n with where is the number of elements in the set defined in Table 10.1.3.1-1, the UE shall use PUCCH resource for transmission of HARQ-ACK in subframe for mapped to antenna port p for PUCCH format 1a/1b, where
- If there is PDSCH transmission indicated by the detection of corresponding PDCCH/EPDCCH or there is PDCCH/EPDCCH indicating downlink SPS release within subframe(s) , where and (defined in Table 10.1.3.1-1) is a set of M elements depending on the subframe n and the UL/DL configuration (defined in Table 4.2-2 in [3]), and if PDCCH indicating PDSCH transmission or downlink SPS release is detected in subframe , where is the smallest value in set such that UE detects a PDCCH/EPDCCH indicating PDSCH transmission or downlink SPS release within subframe(s) and , the UE first selects a value out of {0, 1, 2, 3} which makes and shall use for antenna port , where is configured by higher layers, , and is the number of the first CCE used for transmission of the corresponding PDCCH in subframe and the corresponding m. When two antenna port transmission is configured for PUCCH format 1a/1b, the PUCCH resource for HARQ-ACK bundling for antenna port is given by .
- For a non-BL/CE UE and if there is only a PDSCH transmission where there is not a corresponding PDCCH/EPDCCH detected within subframe(s) , where and is defined in Table 10.1.3.1-1, the UE shall use PUCCH format 1a/1b and PUCCH resource with the value of is determined according to higher layer configuration and Table 9.2-2. For a UE configured for two antenna port transmission for PUCCH format 1a/1b and HARQ-ACK bundling, a PUCCH resource value in Table 9.2-2 maps to two PUCCH resources with the first PUCCH resource for antenna port and the second PUCCH resource for antenna port , otherwise, the PUCCH resource value maps to a single PUCCH resource for antenna port .
- If there is PDSCH transmission indicated by the detection of corresponding PDCCH/EPDCCH or there is PDCCH/EPDCCH indicating downlink SPS release within subframe(s) , where and (defined in Table 10.1.3.1-1) is a set of M elements depending on the subframe n and the UL/DL configuration (defined in Table 4.2-2 in [3]), and if EPDCCH indicating PDSCH transmission or downlink SPS release is detected in subframe , where is the smallest value in set such that UE detects a PDCCH/EPDCCH indicating PDSCH transmission or downlink SPS release within subframe(s) and , the UE shall use
– if EPDCCH-PRB-set is configured for distributed transmission
– if EPDCCH-PRB-set is configured for localized transmission
for antenna port , where is the number of the first ECCE (i.e. lowest ECCE index used to construct the EPDCCH) used for transmission of the corresponding DCI assignment in EPDCCH-PRB-set in subframe and the corresponding m, for EPDCCH-PRB-set is configured by the higher layer parameter pucch-ResourceStartOffset-r11 , for EPDCCH-PRB-set in subframe is given in subclause 6.8A.1 in [3], is determined from the antenna port used for EPDCCH transmission in subframe which is described in subclause 6.8A.5 in [3]. If , is determined from the HARQ-ACK resource offset field in the DCI format of the corresponding EPDCCH as given in Table 10.1.2.1-1. If , is determined from the HARQ-ACK resource offset field in the DCI format of the corresponding EPDCCH as given in Table 10.1.3.1-2. If the UE is configured to monitor EPDCCH in subframe , is equal to the number of ECCEs in EPDCCH-PRB-set configured for that UE in subframe. If the UE is not configured to monitor EPDCCH in subframe , is equal to the number of ECCEs computed assuming EPDCCH-PRB-set is configured for that UE in subframe . For normal downlink CP, if subframe is a special subframe with special subframe configuration 0 or 5, is equal to 0. For extended downlink CP, if subframe is a special subframe with special subframe configuration 0 or 4 or 7, is equal to 0. When two antenna port transmission is configured for PUCCH format 1a/1b, the PUCCH resource for HARQ-ACK bundling for antenna port is given by
– if EPDCCH-PRB-set is configured for distributed transmission
– if EPDCCH-PRB-set is configured for localized transmission
- For a BL/CE UE, if there is only a PDSCH transmission within one or more consecutive BL/CE downlink subframe(s) where subframe , is the last subframe in which the PDSCH is transmitted where and is defined in Table 10.1.3.1-1 and there is not a corresponding MPDCCH, the UE shall use PUCCH format 1a and PUCCH resource
where the value of 
is determined according to higher layer configuration and Table 9.2-2.
- If there is PDSCH transmission indicated by the detection of corresponding MPDCCH or there is MPDCCH indicating downlink SPS release within subframe(s) , where and (defined in Table 10.1.3.1-1) is a set of M elements depending on the subframe n and the UL/DL configuration (defined in Table 4.2-2 in [3]) and subframe is the last subframe in which the PDSCH or MPDCCH indicating downlink SPS release is transmitted and there is no
where 
and subframe 
is the last subframe in which a PDSCH indicated by the detection of corresponding MPDCCH or MPDCCH indicating downlink SPS release is transmitted, the UE shall use
– if MPDCCH-PRB-set is configured for distributed transmission
– if MPDCCH-PRB-set is configured for localized transmission
for antenna port , where is the number of the first ECCE (i.e. lowest ECCE index used to construct the MPDCCH) used for transmission of the corresponding DCI assignment in MPDCCH-PRB-set , 
for MPDCCH-PRB-set is configured
- by the higher layer parameter n1PUCCH-AN-r13, if configured; otherwise:
- by the higher layer parameter n1PUCCH-AN-InfoList-r13 for the corresponding CE level,
for MPDCCH-PRB-set is given in subclause 6.8A.1 in [3], is determined from the antenna port used for the MPDCCH transmission which is described in subclause 6.8A.5 in [3]. If , is determined from the HARQ-ACK resource offset field in the DCI format of the corresponding MPDCCH as given in Table 10.1.2.1-1. If , is determined from the HARQ-ACK resource offset field in the DCI format of the corresponding MPDCCH as given in Table 10.1.3.1-2. If subframe is a BL/CE downlink subframe, is equal to the number of ECCEs in MPDCCH-PRB-set configured for that UE in subframe. If subframe is not a BL/CE downlink subframe, is equal to 0. For normal downlink CP, if subframe is a special subframe with special subframe configuration 0 or 5, is equal to 0. For extended downlink CP, if subframe is a special subframe with special subframe configuration 0 or 4 or 7, is equal to 0. When an MPDCCH-PRB-set is 2+4, following procedures is applied.
– if the detected MPDCCH is located within 2 PRB set, 
is obtained by above procedure.
– if the detected MPDCCH is located within 4 PRB set, 
is the sum between 
and the value obtained by above procedure.
– if the detected MPDCCH is MPDCCH format 5, 
is obtained by the above procedure with 
= 0.
Table 10.1.3.1-1: Downlink association set : for TDD
|
UL/DL Configuration |
Subframe n |
|||||||||
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
|
|
0 |
– |
– |
6 |
– |
4 |
– |
– |
6 |
– |
4 |
|
1 |
– |
– |
7, 6 |
4 |
– |
– |
– |
7, 6 |
4 |
– |
|
2 |
– |
– |
8, 7, 4, 6 |
– |
– |
– |
– |
8, 7, 4, 6 |
– |
– |
|
3 |
– |
– |
7, 6, 11 |
6, 5 |
5, 4 |
– |
– |
– |
– |
– |
|
4 |
– |
– |
12, 8, 7, 11 |
6, 5, 4, 7 |
– |
– |
– |
– |
– |
– |
|
5 |
– |
– |
13, 12, 9, 8, 7, 5, 4, 11, 6 |
– |
– |
– |
– |
– |
– |
– |
|
6 |
– |
– |
7 |
7 |
5 |
– |
– |
7 |
7 |
– |
[TS 36.213, clause 10.2]
For FDD, a BL/CE UE shall upon detection of a PDSCH intended for the UE and for which an HARQ-ACK shall be provided, transmit the HARQ-ACK response using the same 
derived according to section 10.1.2.1 in subframe(s) n+ki with i =0,1, …, N-1, where
– subframe n-4 is the last subframe in which the PDSCH is transmitted; and
– 0≤k0<k1<…,kN-1 and the value of
and 
is provided by higher layer parameter pucch-NumRepetitionCE-format1 if the PDSCH does not contain a contention resolution, otherwise it is provided by higher layer parameter pucch-NumRepetitionCE Msg4-Level0-r13, pucch-NumRepetitionCE-Msg4-Level1-r13, pucch-NumRepetitionCE-Msg4-Level2-r13 or pucch-NumRepetitionCE-Msg4-Level3-r13 depending on whether the most recent PRACH coverage enhancement level for the UE is 0, 1, 2 or 3, respectively; and
if N>1
– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE UL subframe(s) immediately after subframe n-1, and the set of BL/CE UL subframes are configured by higher layers;
otherwise
– k0 =0
For TDD, a BL/CE UE shall upon detection of a PDSCH within subframe(s) , where and is defined in Table 10.1.3.1-1 intended for the UE and for which HARQ-ACK response shall be provided, transmit the HARQ-ACK response using the same 
derived according to section 10.1.3.1 in subframe(s) n+ki with i =0,1, …, N-1, where
– subframe n-k is the last subframe in which the PDSCH is transmitted; and
– 0≤k0<k1<…,kN-1 and the value of
and 
is provided by higher layers parameter pucch-NumRepetitionCE-format1 if the PDSCH does not contain a contention resolution, otherwise it is provided by higher layer parameter pucch-NumRepetitionCE Msg4-Level0-r13, pucch-NumRepetitionCE-Msg4-Level1-r13, pucch-NumRepetitionCE-Msg4-Level2-r13 or pucch-NumRepetitionCE-Msg4-Level3-r13 depending on whether the most recent PRACH coverage enhancement level for the UE is 0, 1, 2 or 3, respectively; and
if N>1
– subframe(s) n+ki with i=0,1,…,N-1 are N consecutive BL/CE UL subframe(s) immediately after subframe n-1, and the set of BL/CE UL subframes are configured by higher layers;
otherwise
– k0 =0
The uplink timing for the ACK corresponding to a detected PDCCH/EPDCCH indicating downlink SPS release shall be the same as the uplink timing for the HARQ-ACK corresponding to a detected PDSCH, as defined above.
For a BL/CE UE, the uplink timing for the ACK corresponding to a detected MPDCCH indicating downlink SPS release shall be the same as the uplink timing for the HARQ-ACK corresponding to a detected PDSCH, as defined above.
7.1.4a.1.3 Test description
7.1.4a.1.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 Registered, Idle mode (state 2A-CE) according to [18].
7.1.4a.1.3.2 Test procedure sequence
Table 7.1.4a.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS sends the SystemInformationBlockType1-BR using test parameter values as given in Table 7.1.4a.1.3.3-1 |
<– |
– |
– |
– |
|
2 |
The SS indicates new system information by Direct Indication information with bit 1 transmitted on MPDCCH using P-RNTI |
<– |
– |
– |
– |
|
3 |
Wait 2.1* modification period for the UE to receive updated system information |
– |
– |
– |
– |
|
4 |
Generic test procedure in TS 36.508 subclause 4.5.3AB.3 and 4.5.4A.3 is performed on Cell 1. |
– |
– |
– |
– |
|
– |
EXCEPTION: Step 5 is repeated 1(CE Mode A)/4 (CE Mode B) (Repetition number) times, in consecutive frames |
– |
– |
– |
– |
|
5 |
The SS transmits a valid MAC PDU containing RLC PDU with DL Grant DCI format 6-1A(CE Mode A) / 6-1B(CE Mode B), Repetition number is set as ‘00’B/’000’B, in configured DL subframe |
<– |
MAC PDU |
– |
– |
|
6 |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
7 |
The SS allocates an UL Grant suitable to send the looped back PDU |
<– |
Uplink Grant |
– |
– |
|
8 |
Check: Does the UE retransmit the MAC PDU for the DL MAC PDU in Step 5? |
–> |
MAC PDU |
1 |
P |
|
– |
EXCEPTION: Step 9 is repeated 2(CE Mode A)/8(CE Mode B) (Repetition number) times, in consecutive frames |
– |
– |
– |
– |
|
9 |
The SS transmits a valid MAC PDU containing RLC PDU with DL Grant DCI format 6-1A(CE Mode A) / 6-1B(CE Mode B), Repetition number is set as ‘01’B/’001’B, in configured DL subframe |
<– |
MAC PDU |
– |
– |
|
10 |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
11 |
The SS allocates an UL Grant suitable to send the looped back PDU |
<– |
Uplink Grant |
– |
– |
|
12 |
Check: Does the UE retransmit the MAC PDU for the DL MAC PDU in Step 9? |
–> |
MAC PDU |
1 |
P |
|
– |
EXCEPTION: Step 13 is repeated 4 (CE Mode A) / 16 (CE Mode B) (Repetition number) times in consecutive frames |
– |
– |
– |
– |
|
13 |
The SS transmits a valid MAC PDU containing RLC PDU with DL Grant DCI format 6-1A, Repetition number is set as ‘10’B/’010’B, in configured DL subframe |
<– |
MAC PDU |
– |
– |
|
14 |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
15 |
The SS allocates an UL Grant suitable to send the looped back PDU |
<– |
Uplink Grant |
– |
– |
|
16 |
Check: Does the UE retransmit the MAC PDU for the DL MAC PDU in Step 13? |
–> |
MAC PDU |
1 |
P |
|
– |
EXCEPTION: Step 17 is repeated 8(CE Mode A) / 32 (CE Mode B) (Repetition number) times in consecutive frames |
– |
– |
– |
|
|
17 |
The SS transmits a valid MAC PDU containing RLC PDU with DL Grant DCI format 6-1A(CE Mode A) / 6-1B(CE Mode B), Repetition number is set as ‘11’B/’011’B, in configured DL subframe |
<– |
MAC PDU |
– |
– |
|
18 |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
19 |
The SS allocates an UL Grant suitable to send the looped back PDU |
<– |
Uplink Grant |
– |
– |
|
20 |
Check: Does the UE retransmit the MAC PDU for the DL MAC PDU in Step 17? |
–> |
MAC PDU |
1 |
P |
|
21 |
The SS transmits an RRCConnectionRelease message. |
<– |
RRCConnectionRelease |
– |
– |
|
22 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state |
– |
– |
– |
– |
|
23 |
The SS changes the SystemInformationBlockType1-BR to using test parameter values as given in Table 7.1.4a.1.3.3-2 |
– |
– |
– |
– |
|
24 |
The SS indicates new system information by Direct Indication information with bit 1 transmitted on MPDCCH using P-RNTI |
<– |
– |
– |
– |
|
25 |
Wait 2.1* modification period for the UE to receive updated system information |
– |
– |
– |
– |
|
26 |
Generic test procedure in TS 36.508 subclause 4.5.3AB.3 and 4.5.4A.3 is performed on Cell 1. |
– |
– |
– |
– |
|
27-42 |
Same as step 5 to 20 above. |
– |
– |
2 |
– |
|
– |
EXCEPTION: Steps 43 to 60 are executed only for FDD |
– |
– |
– |
– |
|
43 |
The SS transmits an RRCConnectionRelease message |
<– |
RRCConnectionRelease |
– |
– |
|
44 |
Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state. |
– |
– |
– |
– |
|
45 |
The SS changes the SystemInformationBlockType1-BR to use test parameter values as given in Table 7.1.4a.1.3.3-3 |
– |
– |
– |
– |
|
46 |
The SS indicates new system information by Direct Indication information with bit 1 transmitted on MPDCCH using P-RNTI |
<– |
– |
– |
– |
|
47 |
Wait 2.1* modification period for the UE to receive updated system information. |
– |
– |
– |
– |
|
48 |
Generic test procedure in TS 36.508 subclause 4.5.3AB.3 and 4.5.4A.3 is performed on Cell 1. |
– |
– |
– |
– |
|
49 |
The SS transmits a valid MAC PDU containing RLC PDU |
<– |
MAC PDU |
– |
– |
|
49A |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
50 |
60 ms after Step 49, the SS allocates an UL Grant DCI format 6-0A(CE Mode A) / 6-0B(CE Mode B), sufficient for one RLC SDU to be looped back in one TTI, Repetition number is set as ‘00’B / ’000’B |
<– |
Uplink Grant |
– |
– |
|
– |
EXCEPTION: Step 51 is repeated 1(CE Mode A) / 4 (CE Mode B) (Repetition number) times |
– |
– |
– |
– |
|
51 |
Check: Does the UE retransmit the MAC PDU in configured UL subframe? |
–> |
MAC PDU |
3 |
P |
|
52 |
The SS transmits a valid MAC PDU containing RLC PDU |
🡨 |
MAC PDU |
– |
– |
|
52A |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
53 |
60 ms after Step 52 the SS allocates an UL Grant DCI format 6-0A(CE Mode A) / 6-0B(CE Mode B), sufficient for one RLC SDU to be looped back in one TTI, Repetition number is set as ‘01’B / ’001’B |
<– |
Uplink Grant |
– |
– |
|
– |
EXCEPTION: Step 54 is repeated 2(CE Mode A) / 8 (CE Mode B) (Repetition number) times |
– |
– |
– |
– |
|
54 |
Check: Does the UE retransmit the MAC PDU in configured UL subframe? |
–> |
MAC PDU |
3 |
P |
|
55 |
The SS transmits a valid MAC PDU containing RLC PDU |
<– |
MAC PDU |
– |
– |
|
55A |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
56 |
60 ms after Step 55 the SS allocates an UL Grant DCI format 6-0A(CE Mode A) / 6-0B(CE Mode B), sufficient for one RLC SDU to be looped back in one TTI, Repetition number is set as ‘10’B / ’010’B |
<– |
Uplink Grant |
– |
– |
|
– |
EXCEPTION: Step 56 is repeated 4(CE Mode A) / 16 (CE Mode B) (Repetition number) times |
– |
– |
– |
– |
|
57 |
Check: Does the UE retransmit the MAC PDU in configured UL subframe? |
–> |
MAC PDU |
3 |
P |
|
58 |
The SS transmits a valid MAC PDU containing RLC PDU |
<– |
MAC PDU |
– |
– |
|
58A |
UE transmits a Scheduling Request on PUCCH. |
–> |
(SR) |
– |
– |
|
59 |
60 ms after Step 58 the SS allocates an UL Grant DCI format 6-0A(CE Mode A) / 6-0B(CE Mode B), sufficient for one RLC SDU to be looped back in one TTI, Repetition number is set as ‘11’B/’011’B |
<– |
Uplink Grant |
– |
– |
|
– |
EXCEPTION: Step 60 is repeated 8(CE Mode A) / 32 (CE Mode B) (Repetition number) times |
– |
– |
– |
– |
|
60 |
Check: Does the UE retransmit the MAC PDU in configured UL subframe? |
–> |
MAC PDU |
3 |
P |
7.1.4a.1.3.3 Specific message contents
Table 7.1.4a.1.3.3-1: SystemInformationBlockType1-BR-r13 (step 1, Table 7.1.4a.1.3.2-1)
|
Derivation path: 36.508 table 4.4.3.2-3A |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType1-BR-r13 ::= SEQUENCE { |
|||
|
systemInfoValueTag |
1 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE { |
|||
|
fdd-DownlinkOrTddSubframeBitmapBR-r13 CHIOCE { |
|||
|
subframePattern10-r13 |
‘1000000001’ B |
Subframe 0 and 9 allowed |
FDD |
|
subframePattern10-r13 |
‘1001000001’ B |
Subframe 0 and 9 allowed for DL and Subframe 3 allowed for UL |
TDD |
|
subframePattern10-r13 |
‘1100000011’ B |
Subframe 0, 1, 8 and 9 allowed |
FDD Half Duplex |
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 7.1.4a.1.3.3-2: SystemInformationBlockType1-BR-r13 (step 23, Table 7.1.4a.1.3.2-1)
|
Derivation path: 36.508 table 4.4.3.2-3A |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType1-BR-r13 ::= SEQUENCE { |
|||
|
systemInfoValueTag |
2 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE { |
|||
|
fdd-DownlinkOrTddSubframeBitmapBR-r13 CHIOCE { |
|||
|
subframePattern40-r13 |
‘1000000001100000000110000000011000000001’ B |
Subframe 0 and 9 allowed |
FDD |
|
subframePattern40-r13 |
‘1001000001100100000110010000011001000001’ B |
Subframe 0 and 9 allowed for DL and Subframe 3 allowed for UL |
TDD |
|
subframePattern40-r13 |
‘1100000011110000001111000000111100000011’B |
Subframe 0, 1, 8 and 9 allowed |
FDD Half Duplex |
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 7.1.4a.1.3.3-3: SystemInformationBlockType1-BR-r13 (step 45, Table 7.1.4a.1.3.2-1)
|
Derivation path: 36.508 table 4.4.3.2-3A |
|||
|
Information Element |
Value/Remark |
Comment |
Condition |
|
SystemInformationBlockType1-BR-r13 ::= SEQUENCE { |
|||
|
systemInfoValueTag |
3 |
||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
nonCriticalExtension SEQUENCE { |
|||
|
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE { |
|||
|
fdd-UplinkSubframeBitmapBR-r13 |
‘0011000000’B |
Subframe 2 and 3 allowed (UL subframe for FDD and Half Duplex FDD) |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
Table 7.1.4a.1.3.3-4: Void
Table 7.1.4a.1.3.3-5: Void