7.1.5 PUSCH Hopping
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.5.1 Inter-TTI PUSCH hopping by uplink grant
7.1.5.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state and ‘Hopping-mode’ is set to ‘InterSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits indicating Type 1 PUSCH Hopping }
then { UE transmits UL data on resource blocks as per type 1 PUSCH hopping}
}
7.1.5.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.212 clause 5.3.3.1.1 and 36.213 clauses 8.4, 8.4.1 & 8.4,2.
[TS 36.212, clause 5.3.3.1.1]
DCI format 0 is used for the scheduling of PUSCH.
The following information is transmitted by means of the DCI format 0:
– Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
– Hopping flag – 1 bit as defined in section 8.4 of [3]
– Resource block assignment and hopping resource allocation – 
bits
– For PUSCH hopping:
– NUL_hop MSB bits are used to obtain the value of 
as indicated in subclause [8.4] of [3]
– 
bits provide the resource allocation of the first slot in the UL subframe
– For non-hopping PUSCH:
– 
bits provide the resource allocation in the UL subframe as defined in section 8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a subframe (S1) including the lowest index PRB (
) in subframe n from the resource allocation field in the latest PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE shall determine its hopping type based on
– the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport block is semi-persistently scheduled or
– the random access response grant for the same transport block, when the PUSCH is initiated by the random access response grant.
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by Table 8.4-1 below where the number of PUSCH resource blocks is defined as
For type 1 and type 2 PUSCH hopping, 
if 
is an odd number where 
defined in [3]. 
in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits shall be 
, where NUL_hop = 1 or 2 bits. The number of contiguous RBs that can be assigned to a type-1 hopping user is limited to 
. The number of contiguous RBs that can be assigned to a type-2 hopping user is limited to min(,
),where the number of sub-bands 
is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits NUL_hop vs. System Bandwidth
|
System BW |
#Hopping bits for 2nd slot RA (NUL_hop) |
|
6-49 |
1 |
|
50-110 |
2 |
The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is “inter-subframe” or “intra and inter-subframe”.
[TS 36.213, clause 8.4.1]
For PUSCH hopping type 1 the hopping bit or bits indicated in Table 8.4-1 determine
as defined in Table 8.4-2. The lowest index PRB (
) of the 1st slot RA in subframe i is defined as 
, where 
, and 
is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
The lowest index PRB (
) of the 2nd slot RA in subframe i is defined as 
.
The set of physical resource blocks to be used for PUSCH transmission are 
contiguously allocated resource blocks from PRB index 
for the 1st slot, and from PRB index 
for the 2nd slot, respectively, where 
is obtained from the uplink scheduling grant as in Section 8.4 and Section 8.1.
If the Hopping-mode is "inter-subframe", the 1st slot RA is applied to even CURRENT_TX_NB, and the 2nd slot RA is applied to odd CURRENT_TX_NB, where CURRENT_TX_NB is defined in [8].
[TS 36.213, clause 8.4.2]
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
|
System BW |
Number of Hopping bits |
Information in hopping bits |
|
|
6 – 49 |
1 |
0 |
|
|
1 |
Type 2 PUSCH Hopping |
||
|
50 – 110 |
2 |
00 |
|
|
01 |
|
||
|
10 |
|
||
|
11 |
Type 2 PUSCH Hopping |
,
7.1.5.1.3 Test description
7.1.5.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.5.1.3.2 Test procedure sequence
Table 7.1.5.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. |
– |
– |
– |
– |
|
Exception: Steps 2 to 5 are executed as per table 7.1.5.1.3.2-2 |
|||||
|
2 |
SS transmits a MAC PDU including 8 (FDD)/4(TDD) RLC SDU’s |
<– |
MAC PDU |
– |
– |
|
3 |
The SS waits for 60 ms |
– |
– |
– |
– |
|
Exception: Steps 4 and 5 are repeated such that UE sends data in 8 ([FDD)/4(TDD) consecutive UL TTI’s. |
|||||
|
4 |
The SS is configured for Uplink Grant Allocation Type 2. SS transmits an UL Grant, allowing the UE to return 1 RLC SDU as received in step 2. Hopping flag’ set as 1, all bits in ‘NUL_hop’ are set as per table 7.1.5.3.2-2 for various execution runs |
<– |
(UL Grant (C-RNTI)) |
– |
– |
|
5 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4? |
– |
– |
1 |
P |
|
Note 1: Steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD configuration 1. Note 2: The grant allocated in step 4 is such that the loop back PDU’s are received in 8 (FDD)/4(TDD) UL TTI’s |
|||||
Table 7.1.5.1.3.2-2: Bandwidth dependent parameters
|
System BW |
Number of Hopping bits |
Execution Counter K |
Information in hopping bits |
|
5 MHz |
1 |
1 |
0 |
|
10/20 MHz |
2 |
1 |
00 |
|
2 |
01 |
||
|
3 |
10 |
7.1.5.1.3.3 Specific message contents.
None
7.1.5.2 Predefined intra-TTI PUSCH hopping (N_sb=1)
7.1.5.2.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 1 and ‘Hopping-mode’ is set to ‘intraAndInterSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop‘ bits all set to 1(Type 2 predefined hopping) }
then { UE transmits data with predefined, intra-TTI PUSCH hopping}
}
7.1.5.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.211 clause 5.3.4 , 36.212 clause 5.3.3.1.1 and 36.213 clause 8.4, 8.4.2.
[TS 36.211, clause 5.3.4]
If uplink frequency-hopping with predefined hopping pattern is enabled, the set of physical resource blocks to be used for transmission in slot 
is given by the scheduling grant together with a predefined pattern according to
where 
is obtained from the scheduling grant as described in Section 8.1 in [4]. The parameter pusch-HoppingOffset,
, is provided by higher layers. The size 
of each sub-band is given by
where the number of sub-bands 
is given by higher layers. The function 
determines whether mirroring is used or not. The parameter Hopping-mode provided by higher layers determines if hopping is “inter-subframe” or “intra and inter-subframe”.
The hopping function 
and the function
are given by
where 
=0 and the pseudo-random sequence 
is given by section 7.2 and CURRENT_TX_NB indicates the transmission number for the transport block transmitted in slot 
as defined in [8]. The pseudo-random sequence generator shall be initialised with 
for FDD and 
for TDD at the start of each frame.
[TS 36.212, clause 5.3.3.1.1]
DCI format 0 is used for the scheduling of PUSCH.
The following information is transmitted by means of the DCI format 0:
– Flag for format0/format1A differentiation – 1 bit, where value 0 indicates format 0 and value 1 indicates format 1A
– Hopping flag – 1 bit as defined in section 8.4 of [3]
– Resource block assignment and hopping resource allocation – 
bits
– For PUSCH hopping:
– NUL_hop MSB bits are used to obtain the value of 
as indicated in subclause [8.4] of [3]
– 
bits provide the resource allocation of the first slot in the UL subframe
– For non-hopping PUSCH:
– 
bits provide the resource allocation in the UL subframe as defined in section 8.1 of [3]
[TS 36.213, clause 8.4]
The UE shall perform PUSCH frequency hopping if the single bit frequency hopping (FH) field in a corresponding PDCCH with DCI format 0 is set to 1 otherwise no PUSCH frequency hopping is performed.
A UE performing PUSCH frequency hopping shall determine its PUSCH resource allocation (RA) for the first slot of a subframe (S1) including the lowest index PRB (
) in subframe n from the resource allocation field in the latest PDCCH with DCI format 0 for the same transport block. If there is no PDCCH for the same transport block, the UE shall determine its hopping type based on
– the hopping information in the most recent semi-persistent scheduling assignment PDCCH, when the initial PUSCH for the same transport block is semi-persistently scheduled or
– the random access response grant for the same transport block, when the PUSCH is initiated by the random access response grant.
The resource allocation field in DCI format 0 excludes either 1 or 2 bits used for hopping information as indicated by Table 8.4-1 below where the number of PUSCH resource blocks is defined as
For type 1 and type 2 PUSCH hopping, 
if 
is an odd number where 
defined in [3]. 
in other cases. The size of the resource allocation field in DCI format 0 after excluding either 1 or 2 bits shall be 
, where NUL_hop = 1 or 2 bits. The number of contiguous RBs that can be assigned to a type-1 hopping user is limited to 
. The number of contiguous RBs that can be assigned to a type-2 hopping user is limited to min(
,
),where the number of sub-bands 
is given by higher layers.
A UE performing PUSCH frequency hopping shall use one of two possible PUSCH frequency hopping types based on the hopping information. PUSCH hopping type 1 is described in section 8.4.1 and type 2 is described in section 8.4.2.
Table 8.4-1: Number of Hopping Bits NUL_hop vs. System Bandwidth
|
System BW |
#Hopping bits for 2nd slot RA (NUL_hop) |
|
6-49 |
1 |
|
50-110 |
2 |
The parameter Hopping-mode provided by higher layers determines if PUSCH frequency hopping is “inter-subframe” or “intra and inter-subframe”.
[TS 36.213, clause 8.4.2]
In PUSCH hopping type 2 the set of physical resource blocks to be used for transmission in slot 
is given by the scheduling grant together with a predefined pattern according to [3] section 5.3.4. If the system frame number is not acquired by the UE yet, the UE shall not transmit PUSCH with type-2 hopping and Nsb>1 for TDD, where Nsb is defined in [3].
Table 8.4-2: PDCCH DCI Format 0 Hopping Bit Definition
|
System BW |
Number of Hopping bits |
Information in hopping bits |
|
|
6 – 49 |
1 |
0 |
|
|
1 |
Type 2 PUSCH Hopping |
||
|
50 – 110 |
2 |
00 |
|
|
01 |
|
||
|
10 |
|
||
|
11 |
Type 2 PUSCH Hopping |
,
7.1.5.2.3 Test description
7.1.5.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].
7.1.5.2.3.2 Test procedure sequence
Table 7.1.5.2.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 8 (FDD)/4(TDD) RLC SDU’s |
<– |
MAC PDU |
– |
– |
|
3 |
The SS waits for 60 ms |
– |
– |
– |
– |
|
Exception: Steps 4 and 5 are repeated such that UE sends data in 8 ([FDD)/4(TDD) consecutive UL TTI’s. |
|||||
|
4 |
The SS is configured for Uplink Grant Allocation Type 2. SS transmits an UL Grant, allowing the UE to return 1 RLC SDU as received in step 2. Hopping flag’ set as 1, all bits in ‘NUL_hop’ are set to 1. |
<– |
(UL Grant (C-RNTI)) |
– |
– |
|
5 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4? |
–> |
MAC PDU |
1 |
P |
|
Note 1: steps 4 and 5 are repeated for 8 times corresponding to 8 sub frames for FDD and 4 for default TDD configuration 1. Note 2: The grant allocated in step 4 is such that the loop back PDU’s are received in 8 (FDD)/4(TDD) UL TTI’s |
|||||
7.1.5.2.3.3 Specific message contents.
Table 7.1.5.2.3.3-1: SystemInformationBlockType2(preamble)
|
Derivation Path: 36.508 Table 4.4.3.3-1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType2 ::= SEQUENCE { |
|||
|
radioResourceConfigCommon SEQUENCE {} |
RadioResourceConfigCommonSIB-DEFAULT-7152 |
||
|
} |
|||
Table 7.1.5.2.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7152(Table 7.1.5.2.3.3-1)
|
Derivation Path: 36.508 Table 4.6.3-14 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigCommonSIB-DEFAULT-7152 ::= SEQUENCE { |
|||
|
pusch-Config |
PUSCH-ConfigCommon-DEFAULT-7152 |
||
|
} |
|||
Table 7.1.5.2.3.3-3: PUSCH-ConfigCommon-DEFAULT-7152(Table 7.1.5.2.3.3-2)
|
Derivation Path: 36.508 table 4.6.3-10 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PUSCH-ConfigCommon-DEFAULT-7152 ::= SEQUENCE { |
|||
|
pusch-ConfigBasic SEQUENCE { |
|||
|
n-SB |
1 |
Default value |
|
|
hoppingMode |
intraAndInterSubFrame |
||
|
pusch-HoppingOffset |
See subclause 4.6.8[36.508] |
Default value |
|
|
} |
|||
|
} |
|||
7.1.5.3 Predefined intra-TTI PUSCH hopping (N_sb=2/3/4)
7.1.5.3.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 2/3/4 and ‘Hopping-mode’ is set to ‘intraAndInterSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits all set to 1(Type 2 predefined hopping) }
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}
7.1.5.3.2 Conformance requirements
Same Conformance requirements as in clause 7.1.5.2.2
7.1.5.3.3 Test description
7.1.5.3.3.1 Pre-test conditions
System Simulator
– Cell 1
UE:
None.
Preamble:
– The UE is in state Registered, Idle mode, Test Mode Activated (State 2A) according to [18].
7.1.5.3.3.2 Test procedure sequence
Table 7.1.5.3.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
EXCEPTION: Step 0 to 7 are repeated for execution counter k=1 to 3 |
|||||
|
0 |
The SS transmits a Paging message in a paging occasion including a systemInfoModification. |
<– |
Paging |
– |
– |
|
0a |
From the beginning of the next modification period the SS transmits a modified SystemInformationBlockType2 as specified. |
– |
– |
– |
– |
|
1 |
The UE is brought to state Loopback Activated (state 4) according to [18] |
– |
– |
– |
– |
|
2 |
The SS ignores scheduling requests and does not allocate any uplink grant. |
– |
– |
– |
– |
|
3 |
SS transmits a MAC PDU including a RLC SDU |
<– |
MAC PDU |
1 |
– |
|
4 |
The SS waits for 60 ms |
– |
– |
– |
|
|
5 |
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. Hopping flag’ set as 1, ‘NUL_hop’ is set to 1. |
<– |
(UL Grant (C-RNTI)) |
– |
– |
|
6 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4? |
– |
– |
1 |
P |
|
7 |
The SS releases the RRC connection |
– |
– |
– |
– |
7.1.5.3.3.3 Specific message contents.
Table 7.1.5.3.3.3-1: SystemInformationBlockType2 (Step 0 of Table 7.1.5.3.3.2-1)
|
Derivation Path: 36.331 clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType2 ::= SEQUENCE { |
|||
|
ac-BarringInfo SEQUENCE {} |
Not present |
||
|
radioResourceConfigCommon SEQUENCE {} |
RadioResourceConfigCommonSIB-DEFAULT-7153 |
||
|
} |
|||
Table 7.1.5.3.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7153
|
Derivation Path: 36.508 Table 4.6.3-14 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigCommonSIB-DEFAULT-7153 ::= SEQUENCE { |
|||
|
pusch-Config |
PUSCH-ConfigCommon-DEFAULT-7153 |
||
|
} |
|||
Table 7.1.5.3.3.3-3: PUSCH-ConfigCommon-DEFAULT-7153
|
Derivation Path: 36.508 table 4.6.3-10 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PUSCH-ConfigCommon-DEFAULT-7153 ::= SEQUENCE { |
|||
|
pusch-ConfigBasic SEQUENCE { |
|||
|
n-SB |
2 |
Execution counter k =1 |
|
|
n-SB |
3 |
Execution counter k =2 |
|
|
n-SB |
4 |
Execution counter k =3 |
|
|
hoppingMode |
intraAndInterSubFrame |
||
|
pusch-HoppingOffset |
See subclause 4.6.8 |
Default value |
|
|
enable64QAM |
FALSE |
Default value |
|
|
} |
|||
|
} |
|||
7.1.5.4 Predefined inter-TTI PUSCH hopping (N_sb=1)
7.1.5.4.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 1 and ‘Hopping-mode‘ is set to ‘interSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop‘ bits all set to 1(Type 2 predefined hopping) }
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 1, ‘Hopping-mode‘ is set to ‘interSubFrame’ has transmitted a transport block with predefined, inter-TTI PUSCH hopping }
ensure that {
when { UE has to make a non adaptive retransmission) }
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}
7.1.5.4.2 Conformance requirements
Same Conformance requirements as in clause 7.1.5.2.2
7.1.5.4.3 Test description
7.1.5.4.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.5.2.3.1
Test procedure sequence
Table 7.1.5.4.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 |
The SS waits for 60 ms. |
– |
– |
– |
– |
|
4 |
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. Hopping flag’ set as 1, all bits in ‘NUL_hop’ are set to 1. |
<– |
(UL Grant (C-RNTI)) |
– |
– |
|
5 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4? |
– |
MAC PDU |
1 |
P |
|
6 |
The SS transmits a HARQ NACK |
<– |
HARQ NACK |
– |
– |
|
7 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4, for same HARQ process as in step 5? |
–> |
MAC PDU |
2 |
P |
|
8 |
The SS transmits a HARQ NACK |
<– |
HARQ NACK |
– |
– |
|
9 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4, for same HARQ process as in step 7? |
–> |
MAC PDU |
2 |
P |
|
10 |
The SS transmits a HARQ NACK |
<– |
HARQ NACK |
– |
– |
|
11 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4, for same HARQ process as in step 9? |
–> |
MAC PDU |
2 |
P |
|
12 |
The SS transmits an HARQ ACK |
<– |
HARQ ACK |
– |
– |
|
Note: 4 HARQ transmissions is selected to be less than MaxHARQ-Tx (=5) |
|||||
7.1.5.4.3.3 Specific message contents.
None
7.1.5.5 Predefined inter-TTI PUSCH hopping (N_sb=2/3/4)
7.1.5.5.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state, number of sub bands ‘N-sb’ is set to 2/3/4 and ‘Hopping-mode’ is set to ‘interSubFrame’}
ensure that {
when { UE receives for a TTI an uplink grant with ‘Hopping flag’ set as 1, ‘NUL_hop’ bits are all set to 1(Type 2 predefined hopping) }
then { UE transmits data with predefined, inter-TTI PUSCH hopping}
}
7.1.5.5.2 Conformance requirements
Same Conformance requirements as in clause 7.1.5.2.2
7.1.5.5.3 Test description
7.1.5.5.3.1 Pre-test conditions
Same Pre-test conditions as in clause 7.1.5.3.3.1
Test procedure sequence
Same Test procedure sequence as in table 7.1.5.3.3.2-1
7.1.5.5.3.3 Specific message contents.
Table 7.1.5.5.3.3-1: SystemInformationBlockType2 (Step 0 of Table 7.1.5.3.3.2-1)
|
Derivation Path: 36.331 clause 6.3.1 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SystemInformationBlockType2 ::= SEQUENCE { |
|||
|
ac-BarringInfo SEQUENCE {} |
Not present |
||
|
radioResourceConfigCommon SEQUENCE {} |
RadioResourceConfigCommonSIB-DEFAULT-7155 |
||
|
} |
|||
Table 7.1.5.5.3.3-2: RadioResourceConfigCommonSIB-DEFAULT-7155
|
Derivation Path: 36.508 Table 4.6.3-14 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigCommonSIB-DEFAULT-7155 ::= SEQUENCE { |
|||
|
pusch-Config |
PUSCH-ConfigCommon-DEFAULT-7155 |
||
|
} |
|||
Table 7.1.5.5.3.3-3: PUSCH-ConfigCommon-DEFAULT-7155
|
Derivation Path: 36.508 table 4.6.3-10 |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
PUSCH-ConfigCommon-DEFAULT-7155 ::= SEQUENCE { |
|||
|
pusch-ConfigBasic SEQUENCE { |
|||
|
n-SB |
2 |
Execution counter k =1 |
|
|
n-SB |
3 |
Execution counter k =2 |
|
|
n-SB |
4 |
Execution counter k =3 |
|
|
hoppingMode |
interSubFrame |
Default value |
|
|
pusch-HoppingOffset |
See subclause 4.6.8 |
Default value |
|
|
enable64QAM |
FALSE |
Default value |
|
|
} |
|||
|
} |
|||
7.1.5.6 PUSCH Hopping / multi-subframe repetitions
7.1.5.6.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state with DRB established }
ensure that {
when { UE receives UL Grant DCI format 0C with ‘Frequency hopping flag’ set as 1}
then { UE transmits UL data repetition in consecutive uplink subframes using the PRB resources with PUSCH hopping}
}
7.1.5.6.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.212 clause 5.3.3.1.1C and 36.211 clauses 5.3.4.
[TS 36.212, clause 5.3.3.1.1C]
DCI format 0C is used for the scheduling of PUSCH in one UL cell.
The following information is transmitted by means of the DCI format 0C:
– Flag for format 0C/format1A differentiation – 1 bit, where value 0 indicates format 0C and value 1 indicates format 1A
– Resource allocation type – 1 bit. This field is only present if 
. The interpretation of this field is provided in section 8.1 of [3]
– Frequency hopping flag – 1 bit as defined in section 5.3.4 of [2]. This field is used as the MSB of the corresponding resource allocation field for resource allocation type 1.
– Resource block assignment – 
bits
– For PUSCH with resource allocation type 0:
– 
bits provide the resource allocation in the UL subframe as defined in section 8.1.1 of [3]
– For non-hopping PUSCH with resource allocation type 1:
– The concatenation of the frequency hopping flag field and the resource block assignment field provides the resource allocation field in the UL subframe as defined in section 8.1.2 of [3]
– Modulation and coding scheme – 5 bits as defined in section 8.6 of [3]
– Repetition number – 3 bits as defined in section 8.0 of [3]
– HARQ process number – 3 bits
– New data indicator – 1 bit
– Redundancy version – 2 bits
– 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 the following cases: 1) TDD primary cell and either TDD operation with uplink-downlink configurations 1-6 or FDD operation; or 2) EN-DC with FDD primary cell and higher layer parameter subframeAssignment-r15 configured)
– CSI request – 1, 2 or 3 bits as defined in section 7.2.1 of [3]. The 2-bit field applies to UEs configured with no more than five DL cells and to
– UEs that are configured with more than one DL cell and when the corresponding DCI format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
– UEs that are configured by higher layers with more than one CSI process and when the corresponding DCI format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
– UEs that are configured with two CSI measurement sets by higher layers with the parameter csi-MeasSubframeSet, and when the corresponding DCI format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
the 3-bit field applies to UEs that are configured with more than five DL cells and when the corresponding DCI format is mapped onto the UE specific search space given by the C-RNTI as defined in [3];
otherwise the 1-bit field applies
– SRS request –1 bit. The interpretation of this field is provided in section 8.2 of [3]
– Modulation order override – 1 bit as defined in section 8.6.1 of [3]
– Precoding information: number of bits as specified in Table 5.3.3.1.8-1. This field is present only if the higher layer parameter transmissionModeUL is configured to be transmission mode 2. Bit field as shown in Table 5.3.3.1.8-2 and Table 5.3.3.1.8-3, where only codeword 0 is enabled and the indexes corresponding to 1 layer are used. 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]. The transport block is mapped to codeword 0.
If the number of information bits in format 0C mapped onto a given search space is less than the payload size of format 1A for scheduling the same serving cell and mapped onto the same search space (including any padding bits appended to format 1A), zeros shall be appended to format 0C until the payload size equals that of format 1A.
[TS 36.211, clause 5.3.4]
For UEs configured with PUSCHEnh-Configuration, the number of PUSCH subframe repetitions 
and the PRB resources for PUSCH transmission in the first subframe are obtained from the DCI as described in clause 5.3.3.1.1C in [3]. PUSCH frequency hopping is enabled when the higher-layer parameters pusch-HoppingOffsetPUSCHEnh and interval-ULHoppingPUSCHEnh are set and the frequency hopping flag in DCI format 0C indicates frequency hopping, otherwise frequency hopping is disabled. If frequency hopping is not enabled for PUSCH, the PUSCH repetitions are located at the same PRB resources as in the first subframe. If frequency hopping is enabled for PUSCH, PUSCH is transmitted in subframe 
within the 
consecutive uplink subframes using the PRB resources starting at PRB index 
where 
is the absolute subframe number of the first UL subframe carrying the PUSCH and 
is given by the higher-layer parameter pusch-HoppingOffsetPUSCHEnh and 
is given by the higher-layer parameter interval-ULHoppingPUSCHEnh.
7.1.5.6.3 Test description
7.1.5.6.3.1 Pre-test conditions
System Simulator
– 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.5.6.3.2 Test procedure sequence
Table 7.1.5.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 |
SS transmits a MAC PDU including 8 (FDD)/4(TDD) RLC SDU’s |
<– |
MAC PDU |
– |
– |
|
3 |
The UE transmits a Scheduling Request |
–> |
Scheduling Request |
– |
– |
|
Exception: Steps 4 to 5 are repeated 8 ([FDD)/4(TDD) times |
|||||
|
4 |
The SS allocates an UL Grant DCI format 0C. allowing the UE to return 1 RLC SDU as received in step 2. ‘Frequency hopping flag’ set as 1, ‘Repetition number’ set as 011 |
<– |
(UL Grant (C-RNTI)) |
– |
– |
|
Exception: Steps 5 are repeated such that UE sends data in 8 consecutive UL subframes. |
|||||
|
5 |
Check: Does the UE transmit a MAC PDU corresponding to grant in step 4? |
–> |
MAC PDU |
1 |
P |
7.1.5.6.3.3 Specific message contents
Table 7.1.5.6.3.3-1: RRCConnectionReconfiguration (Preamble)
|
Derivation Path: 36.508 clause 4.6.1-8, condition SRB2-DRB(1, 1) |
|||
|
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 |
1 |
||
|
interval-ULHoppingPUSCH-Enh-r14 CHOICE { |
|||
|
interval-FDD-PUSCH-Enh-r14 |
int1 |
FDD |
|
|
interval-TDD-PUSCH-Enh-r14 |
int1 |
TDD |
|
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||
|
} |
|||