7.1.6 DRX operation
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.6.1 DRX operation / Short cycle not configured / Parameters configured by RRC
7.1.6.1.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) = drxStartOffset }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-subframes }
}
(2)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and a new DL transmission is indicated on the PDCCH during Active Time }
then { UE starts or restarts the Drx-InactivityTimer and monitors the PDCCH for Drx-InactivityTimer PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where the DL new transmission was indicated }
}
(3)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded }
then { UE starts the drx-RetransmissionTimer for the corresponding HARQ process and monitors the PDCCH for drx-RetransmissionTimer consecutive PDCCH-subframes }
}
(4)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and an uplink grant for a pending HARQ retransmission can occur in this subframe }
then { UE monitors the PDCCH in this subframe }
}
7.1.6.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.
…
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
…
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission is expected by the UE.
…
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.
[TS 36.321, clause 5.7]
The UE may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for the UE’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and Semi-Persistent Scheduling C-RNTI (if configured). When in RRC_CONNECTED, if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously using the DRX operation specified in this subclause; otherwise the UE monitors the PDCCH continuously. When using DRX operation, the UE shall also monitor PDCCH according to requirements found in other subclauses of this specification. RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (one per DL HARQ process except for the broadcast process), the longDRX-Cycle, the value of the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ process (except for the broadcast process) is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
– onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-ContentionResolutionTimer (as described in subclause 5.1.5) is running; or
– a Scheduling Request sent on PUCCH is pending (as described in subclause 5.4.4); or
– an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer; or
– a PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been received after successful reception of a Random Access Response for the explicitly signalled preamble (as described in subclause 5.1.4).
When DRX is configured, the UE shall for each subframe:
– If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle); or
– if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) = drxStartOffset:
– start onDurationTimer.
– if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded:
– start the drx-RetransmissionTimer for the corresponding HARQ process.
– if a DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx–InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the long DRX cycle.
– during the Active Time, for a PDCCH-subframe if the subframe is not required for uplink transmission for half-duplex FDD UE operation and if the subframe is not part of a configured measurement gap:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL or UL):
– start or restart drx-InactivityTimer.
– when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such is expected.
NOTE: A UE may optionally choose to not send CQI/PMI/RI reports on PUCCH and/or SRS transmissions for up to 4 subframes following a PDCCH indicating a new transmission (UL or DL) received in the last subframe of active time. The choice not to send CQI/PMI/RI reports on PUCCH and/or SRS transmissions is not applicable for subframes where onDurationTimer is running.
7.1.6.1.3 Test description
7.1.6.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] configured to return no data in UL.
7.1.6.1.3.2 Test procedure sequence
For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until next PDCCH-subframe available, starting from current subframe number on current SFN. For example at step 1, drxStartOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If drxStartOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.
For example at step 13, assuming drxStartOffset points to subframe number 0 at frame number A, NormalSF(A, 0, onDurationTimer-2) is first added, which counts 18 PDCCH-subframes/30 normal subframes in this case. The current subframe becomes subframe number 0 at frame number A+3. Secondly, HARQ RTT timer is added, which is 11 normal subframes. The current subframe becomes subframe number 1 at frame number A+4. To further add in NormalSF(A+4, 1, drx-RetransmissionTimer-1), which is to counts 5 PDCCH-subframes/9 normal subframes, the current subframe is subframe number 0 at frame number A+5.
Table 7.1.6.1.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0A |
SS Transmits RRCConnectionReconfiguration to configure specific DRX parameters |
<– |
– |
– |
– |
|
0B |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
|
1 |
In the first PDCCH sub frame when the OnDurationTimer is running, the SS indicates the transmission of a DL MAC PDU on the PDCCH. i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(SFN1 * 10) + csfn1] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
MAC PDU |
– |
– |
|
2 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 1? |
–> |
HARQ ACK |
1 |
P |
|
3 |
At least drx-InactivityTimer PDCCH-sub frames after the transmission of the MAC PDU in Step 1 has been indicated(This means the next DRX cycle or later after Step 1) in the last PDCCH sub frame while the onDurationTimer is still running, the SS indicates the transmission a DL MAC PDU on the PDDCH. (Note 4). i.e., on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)]/10); where [(SFN2 * 10) + csfn2] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
MAC PDU |
– |
– |
|
4 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 3? |
–> |
HARQ ACK |
1 |
P |
|
5 |
drx-InactivityTimer PDCCH-subframes after the transmission of the MAC PDU transmitted in step 3 was indicated on the PDCCH, the SS indicates the transmission of a DL MAC PDU on the PDCCH. (Note 4) i.e. on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer + drx-InactivityTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer+ drx-InactivityTimer-1)]/10) |
<– |
MAC PDU |
– |
– |
|
6 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 5? |
–> |
HARQ ACK |
2 |
P |
|
7 |
At least drx-InactivityTimer PDCCH sub frames after the transmission of the MAC PDU in Step 5 has been indicated (This means the next DRX cycle or later after Step 3) and 1 PDCCH sub-frame before the OnDurationTimer expires, the SS indicates the transmission of a DL MAC PDU on the PDDCH. The DL MAC PDU transmitted is invalid. (Note 1, Note 4) i.e., on the subframe with the subframe number = [csfn3 + NormalSF(SFN3, csfn3, onDurationTimer-2)] mod 10, and system frame number = SFN3 + floor([csfn3 + NormalSF(SFN3, csfn3, onDurationTimer-2)]/10); where [(SFN3 * 10) + csfn3] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
Invalid MAC PDU |
– |
– |
|
8 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 7? |
–> |
HARQ NACK |
1 |
P |
|
9 |
In the first PDCCH sub frame when the Drx-RetransmissionTimer for the MAC PDU in Step 7 is started, the SS indicates the transmission of a DL MAC PDU on the PDCCH. i.e., on the subframe with the subframe number = [csfn4 + NormalSF(SFN4, csfn4, 0)] modulo 10, and system frame number = SFN4 + floor([csfn4 + NormalSF(SFN4, csfn4, 0)]/10); where csfn4 = [csfn3 + NormalSF(SFN3, csfn3, onDurationTimer-2)+HARQ RTT timer] modulo 10 and SFN4=SFN3+floor([csfn3 + NormalSF(SFN3, csfn3, onDurationTimer-2)+HARQ RTT timer]/10) For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 7. |
<– |
MAC PDU |
– |
– |
|
10 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 9? |
–> |
HARQ ACK |
3 |
P |
|
11 |
At least drx-InactivityTimer PDCCH sub frames after the transmission of the DL MAC PDU in Step 9 has been indicated (This means the next DRX cycle or later after Step 9) and 1 PDCCH sub-frame before the OnDurationTimer expires, the SS indicates the transmission of DL MAC PDU on the PDCCH. The DL MAC PDU transmitted is invalid(Note 1, Note 4) i.e., on the subframe with the subframe number = [csfn5 + NormalSF(SFN5, csfn5, onDurationTimer-2)] modulo 10 and system frame number=SFN5+floor([csfn5 + NormalSF(SFN5, csfn5, onDurationTimer-2)]/10) ; where [(SFN5 * 10) + csfn5] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
Invalid MAC PDU |
– |
– |
|
12 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 11? |
–> |
HARQ NACK |
1 |
P |
|
13 |
In the last PDCCH sub frame when the drx-RetransmissionTimer for MAC PDU in Step 11 is still running, the SS indicates the transmission of a DL MAC PDU on the PDCCH. i.e. on the subframe with subframe number = [csfn6 + NormalSF(SFN6,csfn6,drx-RetransmissionTimer -1)] modulo 10 and the system frame number=SFN6+floor([csfn6 + NormalSF(SFN6,csfn6,drx-RetransmissionTimer -1)]/10); where the csfn6 = [csfn5 + NormalSF(SFN5, csfn5, onDurationTimer-2)+HARQ RTT timer] modulo 10 and SFN6=SFN5+floor([csfn5 + NormalSF(SFN5, csfn5, onDurationTimer-2)+HARQ RTT timer]/10); For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 11. |
<– |
MAC PDU |
– |
– |
|
14 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 13? |
–> |
HARQ ACK |
3 |
P |
|
15 |
The SS is configured for Uplink Grant Allocation Type 2. At least drx-InactivityTimer PDCCH sub frames after the transmission of the DL MAC PDU in Step 13 has been indicated in the last sub-frame when the onDuratiopnTimer is still running (This means the next DRX cycle or later after Step 7), the SS indicates an UL grant to the UE on the PDCCH. (Note 4) i.e., on the subframe with the subframe number = [csfn7 + NormalSF(SFN7, csfn7, onDurationTimer-1)] modulo 10 and system frame number=SFN7 + floor([csfn7 + NormalSF(SFN7, csfn7, onDurationTimer-1)]/10); where [(SFN7 * 10) + csfn7] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
UL grant on PDCCH |
– |
– |
|
16 |
Check: Does the UE transmit a Buffer Status Report on the UL indicating an empty buffer? |
–> |
Buffer Status Report MAC control element |
1 |
P |
|
17 |
X sub frames after the sub frame in which the UL grant was indicated on the PDCCH for the UL MAC PDU sent in the previous step the SS indicates the transmission of a DL MAC PDU on the PDCCH. X is the number of sub frames required to do a retransmission of the UL MAC PDU transmitted in the previous Step maxHARQ-Tx -1 times (for FDD this is 8x maxHARQ-Tx sub frames, for TDD this is 10x maxHARQ-Tx sub frames considering the default configuration 1.). |
<– |
MAC PDU |
– |
– |
|
18 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 17? |
–> |
HARQ ACK |
4 |
P |
|
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check. Note 2: All the DL MAC PDU are transmitted with the NDI set on the PDCCH. Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer. Note 4: The drx-InactivityTimer is started in the next PDCCH sub-frame of the PDCCH sub-frame where DL new transmission is indicated. |
|||||
7.1.6.1.3.3 Specific message contents
Table 7.1.6.1.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table 7.1.6.1.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf640 |
4 |
|||
|
} |
||||
|
shortDRX |
Not present |
|||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
7.1.6.1a DRX operation / Short cycle not configured / Parameters configured by RRC / Enhanced Coverage / CE Mode A
7.1.6.1a.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { Long DRX cycle is configured and if a UL HARQ RTT Timer expires in this subframe }
then { UE starts the drx-ULRetransmissionTimer for the corresponding HARQ process and monitors the PDCCH for drx-ULRetransmissionTimer consecutive MPDCCH-subframes }
}
7.1.6.1a.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1, 5.7 and 7.7.
[TS 36.321, clause 3.1]
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after the subframe in which a PDCCH indicates an initial UL, DL or SL user data transmission for this MAC entity. For NB-IoT it specifies the number of consecutive PDCCH-subframe(s) after the subframe containing an UL-SCH or after the subframe containing the HARQ feedback for a DL data transmission for this MAC entity.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) until a DL retransmission is received.
drxShortCycleTimer: Specifies the number of consecutive subframe(s) the MAC entity shall follow the Short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
drx-ULRetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) until a grant for UL retransmission is received.
…
UL HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a UL HARQ retransmission grant is expected by the MAC entity.
NOTE: A timer is running once it is started, until it is stopped or until it expires; otherwise it is not running. A timer can be started if it is not running or restarted if it is running. A Timer is always started or restarted from its initial value.
[TS 36.321, clause 5.7]
The MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for the MAC entity’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, Semi-Persistent Scheduling C-RNTI (if configured), eIMTA-RNTI (if configured) and SL-RNTI (if configured). When in RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH discontinuously using the DRX operation specified in this subclause; otherwise the MAC entity monitors the PDCCH continuously. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other subclauses of this specification. RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (one per DL HARQ process except for the broadcast process), drx-ULRetransmissionTimer (one per asynchronous UL HARQ process), the longDRX-Cycle, the value of the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ process (except for the broadcast process) and UL HARQ RTT Timer per asynchronous UL HARQ process is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
– onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or drx-ULRetransmissionTimer or mac-ContentionResolutionTimer (as described in subclause 5.1.5) is running; or
– a Scheduling Request is sent on PUCCH and is pending (as described in subclause 5.4.4); or
– an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer for synchronous HARQ process; or
– a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the preamble not selected by the MAC entity (as described in subclause 5.1.4).
When DRX is configured, the MAC entity shall for each subframe:
…
– if an UL HARQ RTT Timer expires in this subframe:
– start the drx-ULRetransmissionTimer for the corresponding HARQ process.
– if NB-IoT, start or restart the drx-InactivityTimer.
– if a DRX Command MAC control element or a Long DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx-InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the Short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the Long DRX cycle.
– if a Long DRX Command MAC control element is received:
– stop drxShortCycleTimer;
use the Long DRX cycle.
– If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle); or
– if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (longDRX-Cycle) = drxStartOffset:
– start onDurationTimer.
– during the Active Time, for a PDCCH-subframe, if the subframe is not required for uplink transmission for half-duplex FDD UE operation, and if the subframe is not a half-duplex guard subframe [7] and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception, and for NB-IoT if the subframe is not required for uplink transmission or downlink reception other than on PDCCH; or
– during the Active Time, for a subframe other than a PDCCH-subframe and for a UE capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for at least one serving cell not configured with schedulingCellId [8] and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception; or
– during the Active Time, for a subframe other than a PDCCH-subframe and for a UE not capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for the SpCell and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:
– start the HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PDSCH reception;
– else:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates an UL transmission for an asynchronous HARQ process:
– start the UL HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PUSCH transmission;
– stop the drx-ULRetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL, UL or SL):
– except for NB-IoT, start or restart drx-InactivityTimer.
– if the PDCCH indicates a transmission (DL, UL) for a NB-IoT UE:
– stop drx-InactivityTimer, drx-ULRetransmissionTimer and onDurationTimer.
– in current subframe n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, type-0-triggered SRS [2] shall not be reported.
– if CQI masking (cqi-Mask) is setup by upper layers:
– in current subframe n, if onDurationTimer would not be running considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported.
– else:
– in current subframe n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported.
Regardless of whether the MAC entity is monitoring PDCCH or not, the MAC entity receives and transmits HARQ feedback and transmits type-1-triggered SRS [2] when such is expected.
NOTE: The same Active Time applies to all activated serving cell(s).
NOTE: In case of downlink spatial multiplexing, if a TB is received while the HARQ RTT Timer is running and the previous transmission of the same TB was received at least N subframes before the current subframe (where N corresponds to the HARQ RTT Timer), the MAC entity should process it and restart the HARQ RTT Timer.
NOTE: The BL UE and the UE in enhanced coverage waits until the last subframe of the configured MPDCCH search space before executing the next specified action.
[TS 36.321, clause 7.7]
Except for NB-IoT, UL HARQ RTT Timer length is set to 4 subframes for FDD, and set to kULHARQRTT subframes for TDD, where kULHARQRTT equals to the kPHICH value indicated in Table 9.1.2-1 of [2].
7.1.6.1a.3 Test description
7.1.6.1a.3.1 Pre-test conditions
System Simulator:
– Cell 1
UE:
None.
Preamble:
– The UE is in state Loopback Activated (state 4-CE) according to [18].
7.1.6.1a.3.2 Test procedure sequence
For FDD, NormalSF(current SFN,current subframe number,y)=y; For TDD, NormalSF(current SFN,current subframe number,y) counts the minimum number of normal subframes needed to cover y number of PDCCH-subframes until next PDCCH-subframe available, starting from current subframe number on current SFN. For example at step 1, drxStartOffset can point to UL or DL subframe for TDD. If it points to a UL subframe, NormalSF(current SFN,current subframe number,0) counts the number of normal subframes until reach the first DL/special subframe available. If drxStartOffset points to a DL subframe, NormalSF(current SFN,current subframe number,0)=0.
Table 7.1.6.1a.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0A |
SS Transmits RRCConnectionReconfiguration to configure specific DRX parameters |
<– |
– |
– |
– |
|
0B |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
|
1 |
In the first PDCCH sub frame when the OnDurationTimer is running, the SS indicates the transmission of a DL MAC PDU on the MPDCCH. i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(SFN1 * 10) + csfn1] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
MAC PDU |
– |
– |
|
2 |
The SS allocates an UL Grant DCI format 6 0A, sufficient for one RLC SDU to be loop backed in a TTI |
<– |
Uplink Grant |
– |
– |
|
3 |
The UE transmit a MAC PDU including one RLC SDU. |
–> |
MAC PDU |
– |
– |
|
4 |
In the MPDCCH sub frame when the drx-uLRetransmissionTimer for MAC PDU in Step 3 is still running, the SS indicates the transmission of a DL MAC PDU on the MPDCCH. i.e. UL HARQ RTT + drx-uLRetransmissionTimer – x subframes after step 3 (x is between 0 and 20 the difference between On duration and UL Retransmission timer) |
<– |
MAC PDU |
– |
– |
|
5 |
The SS allocates an UL Grant DCI format 6 0A, sufficient for one RLC SDU to be loop backed in a TTI |
<– |
Uplink Grant |
– |
– |
|
6 |
Check: Does the UE transmit a MAC PDU including one RLC SDU? |
–> |
MAC PDU |
1 |
P |
7.1.6.1a.3.3 Specific message contents
Table 7.1.6.1a.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table 7.1.6.1a.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf640 |
4 |
|||
|
} |
||||
|
shortDRX |
Not present |
|||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
drx-Config-r13 CHOICE{ |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer-v1310 |
psf300 |
|||
|
drx-RetransmissionTimer-v1310 |
psf40 |
|||
|
drx-ULRetransmissionTimer-r13 |
Psf320 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
7.1.6.2 DRX operation / Short cycle not configured / DRX command MAC control element reception
7.1.6.2.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { long DRX cycle is configured and a DRX Command MAC control element is received }
then { UE successfully decodes the MAC control PDU }
}
(2)
with { UE in CONNECTED mode }
ensure that {
when { long DRX cycle is configured and the HARQ RTT Timer is running and a DRX Command MAC control element is received }
then { UE continues running the HARQ RTT timer }
}
(3)
with { UE in CONNECTED mode }
ensure that {
when { long DRX cycle is configured and the drx-RetransmissionTimer is running and a DRX Command MAC control element is received }
then { UE continues running the drx-RetransmissionTimer and monitors the PDCCH }
}
7.1.6.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.
…
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
…
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission is expected by the UE.
…
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.
[TS 36.321, clause 5.7]
– if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded:
– start the drx-RetransmissionTimer for the corresponding HARQ process.
– if a DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx-InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the long DRX cycle.
– during the Active Time, for a PDCCH-subframe except if the subframe is required for uplink transmission for half-duplex FDD UE operation and except if the subframe is part of a configured measurement gap:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL or UL):
– start or restart drx-InactivityTimer.
– when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such is expected.
7.1.6.2.3 Test description
7.1.6.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] configured to return no data in UL.
7.1.6.2.3.2 Test procedure sequence
The definition of NormalSF(current SFN,current subframe number,y) can be found in clause 7.1.6.1.3.2.
Table 7.1.6.2.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
0A |
SS Transmits RRCConnectionReconfiguration to configure specific DRX parameters |
<– |
– |
– |
– |
|
0B |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
|
1 |
In a PDCCH sub frame which is X PDCCH sub frames before the PDCCH sub-frame in which the onDurationTimer expires, i.e., on the subframe with the subframe number csfn2 = [csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X)] modulo 10, and the system frame number SFN2 = SFN1+floor([csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X)]/10); and [(SFN1 * 10) + csfn1] modulo (Long DRX Cycle) = drxStartOffset. |
<– |
MAC PDU |
– |
– |
|
2 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 1? |
–> |
HARQ NACK |
1 |
P |
|
3 |
In a PDCCH sub frames before the onDurationTimer expires, the SS indicates the transmission of a DL MAC PDU on the PDCCH. The SS transmits a DL MAC PDU with DRX MAC Control element. UE successfully decodes the MAC PDU. i.e., on the subframe with the subframe number csfn3 = [csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X+Y)] modulo 10, and the system frame number SFN3 = SFN1+floor([csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X+Y)]/10); and 0<Y<X) |
<– |
MAC PDU(DRX MAC Control element) |
– |
– |
|
4 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 3? |
–> |
HARQ ACK |
1 |
P |
|
5 |
In the PDCCH sub frame when the drx-RetransmissionTimer for the MAC PDU indicated in Step 1 on the PDCCH is started the SS indicates the transmission of a DL MAC PDU. The SS transmits an invalid MAC PDU.(Note 1) i.e., on the subframe with the subframe number csfn5 = [csfn4+NormalSF(SFN4, csfn4, 0)] modulo 10, and the system frame number SFN5 = SFN4+floor([csfn4+NormalSF(SFN4, csfn4, 0)]/10); where csfn4 = [csfn2+HARQ RTT Timer] modulo 10, and the SFN4 = SFN2+floor([csfn2+HARQ RTT Timer]/10); For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 1 |
<– |
MAC PDU |
– |
– |
|
6 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 5? |
–> |
HARQ NACK |
2,3 |
P |
|
7 |
Z PDCCH sub frames, i.e., on the subframe with the subframe number = [csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –Z)] modulo 10, and the system frame number = SFN6+floor([csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –Z)]/10); where csfn6 = [csfn5+HARQ RTT Timer] modulo 10, and the SFN6 = SFN5+floor([csfn5+HARQ RTT Timer]/10); For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 5. |
<– |
MAC PDU(DRX MAC Control element) |
– |
– |
|
8 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 7? |
–> |
HARQ ACK |
2,3,1 |
P |
|
9 |
In the last sub frame when the Drx-RetransmissionTimer for the DL MAC PDU indicated on the PDCCH in Step 5 is still running, the SS indicates the transmission of a DL MAC PDU. i.e., on the subframe with the subframe number = [csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –1)] modulo 10, and the system frame number = SFN6+floor([csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –1)]/10); |
<– |
MAC PDU |
– |
– |
|
10 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 9? |
–> |
HARQ ACK |
2,3 |
P |
|
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check. Note 2: All DL MAC PDUs are transmitted with the NDI set on the PDCCH. Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer. |
|||||
7.1.6.2.3.3 Specific message contents
Table 7.1.6.2.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table 7.1.6.2.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf640 |
4 |
|||
|
} |
||||
|
shortDRX |
Not present |
|||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
7.1.6.3 DRX operation / Short cycle configured / Parameters configured by RRC
7.1.6.3.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { Short DRX cycle is configured and [(SFN * 10) + subframe number] modulo (ShortDRX-Cycle) = drxStartOffset modulo (ShortDRX-Cycle) }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-subframes }
}
(2)
with { UE in CONNECTED mode }
ensure that {
when { drxShortCycleTimer is expired and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) = drxStartOffset}
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-subframes }
}
7.1.6.3.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.
…
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
…
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission is expected by the UE.
…
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.
[TS 36.321, clause 5.7]
The UE may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for the UE’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI and Semi-Persistent Scheduling C-RNTI (if configured). When in RRC_CONNECTED, if DRX is configured, the UE is allowed to monitor the PDCCH discontinuously using the DRX operation specified in this subclause; otherwise the UE monitors the PDCCH continuously. When using DRX operation, the UE shall also monitor PDCCH according to requirements found in other subclauses of this specification. RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (one per DL HARQ process except for the broadcast process), the longDRX-Cycle, the value of the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ process (except for the broadcast process) is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
– onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or mac-ContentionResolutionTimer (as described in subclause 5.1.5) is running; or
– a Scheduling Request sent on PUCCH is pending (as described in subclause 5.4.4); or
– an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer; or
– a PDCCH indicating a new transmission addressed to the C-RNTI of the UE has not been received after successful reception of a Random Access Response for the explicitly signalled preamble (as described in subclause 5.1.4).
When DRX is configured, the UE shall for each subframe:
– If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle); or
– if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) = drxStartOffset:
– start onDurationTimer.
– if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded:
– start the drx-RetransmissionTimer for the corresponding HARQ process.
– if a DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx–InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the long DRX cycle.
– during the Active Time, for a PDCCH-subframe if the subframe is not required for uplink transmission for half-duplex FDD UE operation and if the subframe is not part of a configured measurement gap:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL or UL):
– start or restart drx-InactivityTimer.
– when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such is expected.
NOTE: A UE may optionally choose to not send CQI/PMI/RI reports on PUCCH and/or SRS transmissions for up to 4 subframes following a PDCCH indicating a new transmission (UL or DL) received in the last subframe of active time. The choice not to send CQI/PMI/RI reports on PUCCH and/or SRS transmissions is not applicable for subframes where onDurationTimer is running.
7.1.6.3.3 Test description
7.1.6.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] configured to return no data in UL.
7.1.6.3.3.2 Test procedure sequence
The definition of NormalSF (current SFN,current subframe number,y) can be found in clause 7.1.6.1.3.2.
Table 7.1.6.3.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS Transmits RRCConnectionReconfiguration to configure specific DRX parameters |
<– |
– |
– |
– |
|
2 |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
|
3 |
In the first PDCCH sub frame when the OnDurationTimer is running, the SS indicates the transmission of a DL MAC PDU on the PDCCH. i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(SFN1 * 10) + csfn1] modulo (ShortDRX-Cycle) = drxStartOffset modulo (ShortDRX-Cycle) |
<– |
MAC PDU |
– |
– |
|
4 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 3? |
–> |
HARQ ACK |
1 |
P |
|
5 |
At least drx-InactivityTimer PDCCH-sub frames after the transmission of the MAC PDU in Step 3 has been indicated(This means the next DRX cycle or later after Step 3) in the last PDCCH sub frame while the onDurationTimer is still running, the SS indicates the transmission a DL MAC PDU on the PDDCH. (Note). i.e., on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)]/10); where [(SFN2 * 10) + csfn2] modulo (ShortDRX-Cycle) = drxStartOffset modulo (ShortDRX-Cycle) |
<– |
MAC PDU |
– |
– |
|
6 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 5? |
–> |
HARQ ACK |
1 |
P |
|
7 |
UE waits for drxShortCycleTimer expire. |
– |
– |
– |
– |
|
8 |
In the first PDCCH sub frame when the OnDurationTimer of Long DRX cycle is running, the SS indicates the transmission of a DL MAC PDU on the PDCCH. i.e., on the subframe with the subframe number = [csfn1 + NormalSF(SFN1, csfn1, 0)] modulo 10, and system frame number = SFN1 + floor([csfn1 + NormalSF(SFN1, csfn1, 0)]/10); where [(SFN1 * 10) + csfn1] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
MAC PDU |
– |
– |
|
9 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 8? |
–> |
HARQ ACK |
2 |
P |
|
10 |
At least drx-InactivityTimer PDCCH-sub frames after the transmission of the MAC PDU in Step 1 has been indicated(This means the next DRX cycle or later after Step 1) in the last PDCCH sub frame while the onDurationTimer is still running, the SS indicates the transmission a DL MAC PDU on the PDDCH. (Note). i.e., on the subframe with the subframe number = [csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)] modulo 10, and system frame number = SFN2 + floor([csfn2 + NormalSF(SFN2,csfn2,onDurationTimer-1)]/10); where [(SFN2 * 10) + csfn2] modulo (LongDRX-Cycle) = drxStartOffset |
<– |
MAC PDU |
– |
– |
|
11 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 10? |
–> |
HARQ ACK |
2 |
P |
|
Note: The drx-InactivityTimer is started in the next PDCCH sub-frame of the PDCCH sub-frame where DL new transmission is indicated. |
|||||
7.1.6.3.3.3 Specific message contents
Table 7.1.6.3.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 1 of table 7.1.6.3.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf640 |
4 |
|||
|
} |
||||
|
shortDRX { |
||||
|
shortDRX-Cycle |
sf64 |
|||
|
drxShortCycleTimer |
4 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
7.1.6.4 DRX operation / Short cycle configured / DRX command MAC control element reception
7.1.6.4.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { Short DRX cycle is configured and a DRX Command MAC control element is received }
then { UE successfully decodes the MAC control PDU }
}
(2)
with { UE in CONNECTED mode }
ensure that {
when { Short DRX cycle is configured and the HARQ RTT Timer is running and a DRX Command MAC control element is received }
then { UE continues running the HARQ RTT timer }
}
(3)
with { UE in CONNECTED mode }
ensure that {
when { Short DRX cycle is configured and the drx-RetransmissionTimer is running and a DRX Command MAC control element is received }
then { UE continues running the drx-RetransmissionTimer and monitors the PDCCH }
}
7.1.6.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.
…
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
…
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission is expected by the UE.
…
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.
[TS 36.321, clause 5.7]
– if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded:
– start the drx-RetransmissionTimer for the corresponding HARQ process.
– if a DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx-InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the long DRX cycle.
– during the Active Time, for a PDCCH-subframe except if the subframe is required for uplink transmission for half-duplex FDD UE operation and except if the subframe is part of a configured measurement gap:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL or UL):
– start or restart drx-InactivityTimer.
– when not in Active Time, CQI/PMI/RI on PUCCH and SRS shall not be reported.
Regardless of whether the UE is monitoring PDCCH or not the UE receives and transmits HARQ feedback when such is expected.
7.1.6.4.3 Test description
7.1.6.4.3.1 Pre-test conditions
System Simulator:
– Cell 1
UE:
None.
Preamble:
– The UE is in state Loopback Activated (state 4) according to [18] configured to return no data in UL.
7.1.6.4.3.2 Test procedure sequence
The definition of NormalSF(current SFN,current subframe number,y) can be found in clause 7.1.6.1.3.2.
Table 7.1.6.4.3.2-1: Main Behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
SS Transmits RRCConnectionReconfiguration to configure specific DRX parameters |
<– |
– |
– |
– |
|
2 |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
|
– |
The following messages are sent before drxShortCycleTimer expires. |
– |
– |
– |
– |
|
3 |
In a PDCCH sub frame which is X PDCCH sub frames before the PDCCH sub-frame in which the onDurationTimer expires, with drx-InactivityTimer< X < the number of PDCCH subframes encapsulated by HARQ RTT timer, the SS indicates the transmission of a DL MAC PDU on the PDCCH. The SS transmits an invalid MAC PDU.(Note 1) i.e., on the subframe with the subframe number csfn2 = [csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X)] modulo 10, and the system frame number SFN2 = SFN1+floor([csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X)]/10); and [(SFN1 * 10) + csfn1] modulo (Short DRX Cycle) = drxStartOffset modulo (Short DRX Cycle). |
<– |
MAC PDU |
– |
– |
|
4 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 3? |
–> |
HARQ NACK |
1 |
P |
|
5 |
In a PDCCH sub frames before the onDurationTimer expires, the SS indicates the transmission of a DL MAC PDU on the PDCCH. The SS transmits a DL MAC PDU with DRX MAC Control element. UE successfully decodes the MAC PDU. i.e., on the subframe with the subframe number csfn3 = [csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X+Y)] modulo 10, and the system frame number SFN3 = SFN1+floor([csfn1+NormalSF(SFN1, csfn1, onDurationTimer-1-X+Y)]/10); and 0<Y<X) |
<– |
MAC PDU(DRX MAC Control element) |
– |
– |
|
6 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 5? |
–> |
HARQ ACK |
1 |
P |
|
7 |
In the PDCCH sub frame when the drx-RetransmissionTimer for the MAC PDU indicated in Step 3 on the PDCCH is started the SS indicates the transmission of a DL MAC PDU. The SS transmits an invalid MAC PDU.(Note 1) i.e., on the subframe with the subframe number csfn5 = [csfn4+NormalSF(SFN4, csfn4, 0)] modulo 10, and the system frame number SFN5 = SFN4+floor([csfn4+NormalSF(SFN4, csfn4, 0)]/10); where csfn4 = [csfn2+HARQ RTT Timer] modulo 10, and the SFN4 = SFN2+floor([csfn2+HARQ RTT Timer]/10); For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 1 |
<– |
MAC PDU |
– |
– |
|
8 |
Check: Does the UE transmit a HARQ NACK for the DL MAC PDU in Step 7? |
–> |
HARQ NACK |
2,3 |
P |
|
9 |
Z PDCCH sub frames, where Z>drx-InactivityTimer, before the PDCCH sub-frame in which the drx-RetransmissionTimer for the DL MAC PDU in Step 7 expires, the SS indicates the transmission of a DL MAC PDU. The SS transmits a DL MAC PDU with DRX MAC Control element. i.e., on the subframe with the subframe number = [csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –Z)] modulo 10, and the system frame number = SFN6+floor([csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –Z)]/10); where csfn6 = [csfn5+HARQ RTT Timer] modulo 10, and the SFN6 = SFN5+floor([csfn5+HARQ RTT Timer]/10); For TDD the HARQ RTT timer is the HARQ RTT timer for the DL transmission in Step 7. |
<– |
MAC PDU(DRX MAC Control element) |
– |
– |
|
10 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 9? |
–> |
HARQ ACK |
2,3,1 |
P |
|
11 |
In the last sub frame when the Drx-RetransmissionTimer for the DL MAC PDU indicated on the PDCCH in Step 7 is still running, the SS indicates the transmission of a DL MAC PDU. i.e., on the subframe with the subframe number = [csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –1)] modulo 10, and the system frame number = SFN6+floor([csfn6+NormalSF(SFN6, csfn6, drx-RetransmissionTimer –1)]/10); |
<– |
MAC PDU |
– |
– |
|
12 |
Check: Does the UE transmit a HARQ ACK for the DL MAC PDU in Step 11? |
–> |
HARQ ACK |
2,3 |
P |
|
Note 1: Invalid MAC PDU is a MAC PDU that fails the CRC check. Note 2: All DL MAC PDUs are transmitted with the NDI set on the PDCCH. Note 3: Timer tolerances for the MAC DRX related timers measured in subframes or PDCCH subframes is 0. These timers are: drx-InactivityTimer, drx-RetransmissionTimer, HARQ RTT Timer. |
|||||
7.1.6.4.3.3 Specific message contents
Table 7.1.6.4.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 1 of table 7.1.6.4.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf640 |
4 |
|||
|
} |
||||
|
shortDRX { |
||||
|
shortDRX-Cycle |
sf64 |
|||
|
drxShortCycleTimer |
10 |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
7.1.6.5 eDRX operation / Long cycle configured / Parameters configured by RRC
7.1.6.5.1 Test Purpose (TP)
(1)
with { UE in CONNECTED mode }
ensure that {
when { UE determines that Long eDRX cycle is configured and [(SFN * 10) + subframe number] modulo (LongDRX-Cycle) = drxStartOffset }
then { UE starts the OnDurationTimer and monitors the PDCCH for OnDurationTimer PDCCH-subframes }
}
(2)
with { UE in CONNECTED mode }
ensure that {
when { Long eDRX cycle is configured and a new DL transmission is indicated on the PDCCH during Active Time }
then { UE starts or restarts the Drx-InactivityTimer and monitors the PDCCH for Drx-InactivityTimer PDCCH sub-frames starting from the next PDCCH sub-frame of the PDCCH sub-frame where the DL new transmission was indicated }
}
(3)
with { UE in CONNECTED mode }
ensure that {
when { Long eDRX cycle is configured and if a HARQ RTT Timer expires in this subframe and the data in the soft buffer of the corresponding HARQ process was not successfully decoded }
then { UE starts the drx-RetransmissionTimer for the corresponding HARQ process and monitors the PDCCH for drx-RetransmissionTimer consecutive PDCCH-subframes }
}
(4)
with { UE in CONNECTED mode }
ensure that {
when { Long eDRX cycle is configured and an uplink grant for a pending HARQ retransmission can occur in this subframe }
then { UE monitors the PDCCH in this subframe }
}
7.1.6.5.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clauses 3.1 and 5.7.
[TS 36.321, clause 3.1]
Active Time: Time related to DRX operation, as defined in subclause 5.7, during which the UE monitors the PDCCH in PDCCH-subframes.
…
DRX Cycle: Specifies the periodic repetition of the On Duration followed by a possible period of inactivity (see figure 3.1-1 below).
Figure 3.1-1: DRX Cycle
drx-InactivityTimer: Specifies the number of consecutive PDCCH-subframe(s) after successfully decoding a PDCCH indicating an initial UL or DL user data transmission for this UE.
drx-RetransmissionTimer: Specifies the maximum number of consecutive PDCCH-subframe(s) for as soon as a DL retransmission is expected by the UE.
drxShortCycleTimer: Specifies the number of consecutive subframe(s)the UE shall follow the short DRX cycle.
drxStartOffset: Specifies the subframe where the DRX Cycle starts.
…
HARQ RTT Timer: This parameter specifies the minimum amount of subframe(s) before a DL HARQ retransmission is expected by the UE.
…
onDurationTimer: Specifies the number of consecutive PDCCH-subframe(s) at the beginning of a DRX Cycle.
PDCCH-subframe: For FDD UE operation, this represents any subframe; for TDD, only downlink subframes and subframes including DwPTS.
[TS 36.321, clause 5.7]
The MAC entity may be configured by RRC with a DRX functionality that controls the UE’s PDCCH monitoring activity for the MAC entity’s C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, Semi-Persistent Scheduling C-RNTI (if configured), eIMTA-RNTI (if configured) and SL-RNTI (if configured). When in RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH discontinuously using the DRX operation specified in this subclause; otherwise the MAC entity monitors the PDCCH continuously. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other subclauses of this specification. RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (one per DL HARQ process except for the broadcast process), drx-ULRetransmissionTimer (one per asynchronous UL HARQ process), the longDRX-Cycle, the value of the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ process (except for the broadcast process) and UL HARQ RTT Timer per asynchronous UL HARQ process is also defined (see subclause 7.7).
When a DRX cycle is configured, the Active Time includes the time while:
– onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or drx-ULRetransmissionTimer or mac-ContentionResolutionTimer (as described in subclause 5.1.5) is running; or
– a Scheduling Request is sent on PUCCH and is pending (as described in subclause 5.4.4); or
– an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer for synchronous HARQ process; or
– a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the preamble not selected by the MAC entity (as described in subclause 5.1.4).
When DRX is configured, the MAC entity shall for each subframe:
– if a HARQ RTT Timer expires in this subframe:
– if the data of the corresponding HARQ process was not successfully decoded:
– start the drx-RetransmissionTimer for the corresponding HARQ process;
– if NB-IoT, start or restart the drx-InactivityTimer.
– if an UL HARQ RTT Timer expires in this subframe:
– start the drx-ULRetransmissionTimer for the corresponding HARQ process.
– if NB-IoT, start or restart the drx-InactivityTimer.
– if a DRX Command MAC control element or a Long DRX Command MAC control element is received:
– stop onDurationTimer;
– stop drx-InactivityTimer.
– if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe:
– if the Short DRX cycle is configured:
– start or restart drxShortCycleTimer;
– use the Short DRX Cycle.
– else:
– use the Long DRX cycle.
– if drxShortCycleTimer expires in this subframe:
– use the Long DRX cycle.
– if a Long DRX Command MAC control element is received:
– stop drxShortCycleTimer;
use the Long DRX cycle.
– If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle); or
– if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (longDRX-Cycle) = drxStartOffset:
– start onDurationTimer.
– during the Active Time, for a PDCCH-subframe, if the subframe is not required for uplink transmission for half-duplex FDD UE operation, and if the subframe is not a half-duplex guard subframe [7] and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception, and for NB-IoT if the subframe is not required for uplink transmission or downlink reception other than on PDCCH; or
– during the Active Time, for a subframe other than a PDCCH-subframe and for a UE capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for at least one serving cell not configured with schedulingCellId [8] and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception; or
– during the Active Time, for a subframe other than a PDCCH-subframe and for a UE not capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for the SpCell and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception:
– monitor the PDCCH;
– if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe:
– if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage:
– start the HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PDSCH reception;
– else:
– start the HARQ RTT Timer for the corresponding HARQ process;
– stop the drx-RetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates an UL transmission for an asynchronous HARQ process:
– start the UL HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PUSCH transmission;
– stop the drx-ULRetransmissionTimer for the corresponding HARQ process.
– if the PDCCH indicates a new transmission (DL, UL or SL):
– except for NB-IoT, start or restart drx-InactivityTimer.
– if the PDCCH indicates a transmission (DL, UL) for a NB-IoT UE:
– stop drx-InactivityTimer, drx-ULRetransmissionTimer and onDurationTimer.
– in current subframe n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, type-0-triggered SRS [2] shall not be reported.
– if CQI masking (cqi-Mask) is setup by upper layers:
– in current subframe n, if onDurationTimer would not be running considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported.
– else:
– in current subframe n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this subclause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported.
Regardless of whether the MAC entity is monitoring PDCCH or not, the MAC entity receives and transmits HARQ feedback and transmits type-1-triggered SRS [2] when such is expected.
NOTE 1: The same Active Time applies to all activated serving cell(s).
NOTE 2: In case of downlink spatial multiplexing, if a TB is received while the HARQ RTT Timer is running and the previous transmission of the same TB was received at least N subframes before the current subframe (where N corresponds to the HARQ RTT Timer), the MAC entity should process it and restart the HARQ RTT Timer.
NOTE 3: The BL UE and the UE in enhanced coverage waits until the last subframe of the configured MPDCCH search space before executing the next specified action.
7.1.6.5.3 Test description
7.1.6.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] configured to return no data in UL.
7.1.6.5.3.2 Test procedure sequence
Same test procedure sequence as in clause 7.1.6.1.3.2
7.1.6.5.3.3 Specific message contents
Table 7.1.6.5.3.3-1: specific Parameters in RRCConnectionReconfiguration (step 0A of table 7.1.6.1.3.2-1)
|
Derivation Path: 36.508 Table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
measConfig |
Not present |
|||
|
mobilityControlInfo |
Not present |
|||
|
dedicatedInfoNASList |
Not present |
|||
|
radioResourceConfigDedicated::= SEQUENCE { |
||||
|
srb-ToAddModList |
Not present |
|||
|
drb-ToAddModList |
Not present |
|||
|
drb-ToReleaseList |
Not present |
|||
|
mac-MainConfig CHOICE { |
||||
|
explicitValue::= SEQUENCE { |
||||
|
ul-SCH-Config SEQUENCE { |
||||
|
maxHARQ-Tx |
n5 |
|||
|
retxBSR-Timer |
sf10240 |
|||
|
ttiBundling |
FALSE |
|||
|
} |
||||
|
drx-Config CHOICE { |
||||
|
setup SEQUENCE { |
||||
|
onDurationTimer |
psf20 |
|||
|
drx-InactivityTimer |
psf6 |
|||
|
drx-RetransmissionTimer |
psf6 |
|||
|
longDRX-CycleStartOffset CHOICE { |
||||
|
sf2560 |
4 |
|||
|
} |
||||
|
shortDRX |
Not present |
|||
|
} |
||||
|
} |
||||
|
timeAlignmentTimerDedicated |
infinity |
|||
|
phr-Config CHOICE { |
||||
|
release |
NULL |
|||
|
} |
||||
|
} |
||||
|
eDRX-Config-CycleStartOffset-r13 CHOICE { |
||||
|
setup CHOICE { |
||||
|
sf5120 |
0 |
longDRX-Cycle =5120 and drxStartOffset, = 2560*0+4 |
||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||