Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 38.321  Word version:  18.3.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.1.2…   5.2…   5.4…   5.4.4…   5.5…   5.9…   5.18…   5.18.18…   5.19…   5.22…   5.22.1.4…   5.22.2…   5.23…   6…   6.1.3…   6.1.3.8…   6.1.3.11…   6.1.3.17…   6.1.3.21…   6.1.3.26…   6.1.3.31…   6.1.3.37…   6.1.3.42…   6.1.3.49…   6.1.3.53…   6.1.3.59…   6.1.3.64…   6.1.3.70…   6.1.3.74…   6.1.3.79…   6.1.4…   6.2…   7… 
5.5 PCH reception  5.6 BCH reception  5.7 Discontinuous Reception (DRX)  5.7a Discontinuous Reception (DRX) for MBS Broadcast  5.7b Discontinuous Reception (DRX) for MBS Multicast  5.8 Transmission and reception without dynamic scheduling  5.8.1 Downlink  5.8.1a Downlink for Multicast  5.8.2 Uplink  5.8.3 Sidelink 
...

 

5.5  PCH reception  p. 94

When the MAC entity needs to receive PCH, the MAC entity shall:
1 >
if a PCH assignment has been received on the PDCCH for the P-RNTI:
2 >
attempt to decode the TB on the PCH as indicated by the PDCCH information;
2 >
if the TB on the PCH has been successfully decoded:
3 >
deliver the decoded MAC PDU to upper layers.

5.6  BCH reception  p. 94

When the MAC entity needs to receive BCH, the MAC entity shall:
1 >
receive and attempt to decode the BCH;
1 >
if a TB on the BCH has been successfully decoded:
2 >
deliver the decoded MAC PDU to upper layers.

5.7  Discontinuous Reception (DRX)  p. 94

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, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SL-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI and cellDTRX-RNTI. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other clauses of this specification. When in RRC_CONNECTED, if DRX is configured, for all the activated Serving Cells, the MAC entity may monitor the PDCCH discontinuously using the DRX operation specified in this clause; otherwise the MAC entity shall monitor the PDCCH as specified in TS 38.213.
RRC controls DRX operation by configuring the following parameters:
  • drx-onDurationTimer: the duration at the beginning of a DRX cycle;
  • drx-SlotOffset: the delay before starting the drx-onDurationTimer;
  • drx-InactivityTimer: the duration after the PDCCH occasion in which a PDCCH indicates a new UL, DL or SL transmission for the MAC entity;
  • drx-RetransmissionTimerDL (per DL HARQ process except for the broadcast process): the maximum duration until a DL retransmission is received;
  • drx-RetransmissionTimerUL (per UL HARQ process): the maximum duration until a grant for UL retransmission is received;
  • drx-LongCycleStartOffset: the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX cycle starts;
  • drx-NonIntegerLongCycleStartOffset (optional): the Long DRX cycle and drx-StartOffset which defines the subframe where the Long and Short DRX cycle start, when the length of the Long DRX cycle and/or the short DRX cycle is not an integer;
  • drx-ShortCycle (optional): the Short DRX cycle;
  • drx-NonIntegerShortCycle (optional): the Short DRX cycle whose length is not an integer;
  • drx-ShortCycleTimer (optional): the duration the UE shall follow the Short DRX cycle;
  • drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity;
  • drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity;
  • drx-RetransmissionTimerSL (per sidelink process): the maximum duration until a grant for SL retransmission is received;
  • drx-HARQ-RTT-TimerSL (per sidelink process): the minimum duration before an SL retransmission grant is expected by the MAC entity;
  • drx-LastTransmissionUL (optional): the configuration to start drx-HARQ-RTT-TimerUL after the last transmission within a bundle;
  • ps-Wakeup (optional): the configuration to start associated drx-onDurationTimer in case DCP is monitored but not detected;
  • ps-TransmitOtherPeriodicCSI (optional): the configuration to report periodic CSI that is not L1-RSRP on PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started;
  • ps-TransmitPeriodicL1-RSRP (optional): the configuration to transmit periodic CSI that is L1-RSRP on PUCCH during the time duration indicated by drx-onDurationTimer in case DCP is configured but associated drx-onDurationTimer is not started;
  • downlinkHARQ-FeedbackDisabled (optional): the configuration to disable HARQ feedback per DL HARQ process;
  • uplinkHARQ-Mode (optional): the configuration to set HARQmodeA or HARQmodeB per UL HARQ process;
  • disableCG-RetransmissionMonitoring (optional): the configuration to disable starting drx-HARQ-RTT-TimerUL for UL transmission over a configured uplink grant;
  • drx-TimeReferenceSFN (optional): the configuration to indicate how UE initializes of DRX_SFN_COUNTER.
The following UE variable is used for the DRX operation if drx-NonIntegerLongCycleStartOffset is configured:
  • DRX_SFN_COUNTER: the counter that increments when SFN changes to 0. The maximum value of this counter is at least 65535.
Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all Serving Cells belong to that one DRX group. When two DRX groups are configured, each Serving Cell is uniquely assigned to either of the two groups. The DRX parameters that are separately configured for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters that are common to the DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-NonIntegerLongCycleStartOffset, drx-ShortCycle (optional), drx-NonIntegerShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.
When DRX is configured, the Active Time for Serving Cells in a DRX group includes the time while:
  • drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or
  • drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL is running on any Serving Cell in the DRX group; or
  • ra-ContentionResolutionTimer (as described in clause 5.1.5) or msgB-ResponseWindow (as described in clause 5.1.4a) is running; or
  • a Scheduling Request is sent on PUCCH and is pending (as described in clause 5.4.4 or 5.22.1.5). If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for all the SR configurations with pending SR(s) plus the UE-gNB RTT; 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 Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble (as described in clauses 5.1.4 and 5.1.4a); or
  • there is an ongoing RACH-less LTM cell switch; or
  • there is an ongoing RACH-less handover in a terrestrial network.
The following MAC timers are used for DRX operation in a non-terrestrial network:
  • HARQ-RTT-TimerDL-NTN (per DL HARQ process configured with HARQ feedback enabled): the minimum duration before a DL assignment for HARQ retransmission is expected by the MAC entity;
  • HARQ-RTT-TimerUL-NTN (per UL HARQ process configured with HARQModeA): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity.
When DRX is not configured and multicast DRX is configured for a G-RNTI or G-CS-RNTI, the MAC entity shall:
1 >
monitor the PDCCH as specified in TS 38.213;
1 >
if a MAC PDU is received in a configured downlink assignment for unicast; or
1 >
if the PDCCH indicates a DL unicast transmission:
2 >
stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process.
When DRX is configured, the MAC entity shall:
1 >
if a MAC PDU is received in a configured downlink assignment for unicast:
2 >
if this Serving Cell is configured with downlinkHARQ-FeedbackDisabled:
3 >
if the corresponding HARQ process is configured with HARQ feedback enabled:
4 >
set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;
4 >
start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
2 >
else:
3 >
start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
2 >
stop the drx-RetransmissionTimerDL for the corresponding HARQ process;
2 >
stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process.
1 >
if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers:
2 >
if this Serving Cell is configured with uplinkHARQ-Mode:
3 >
if the corresponding HARQ process is configured as HARQModeA:
4 >
set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value;
4 >
if drx-LastTransmissionUL is configured:
5 >
start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission.
4 >
else:
5 >
start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission.
2 >
else:
3 >
if disableCG-RetransmissionMonitoring is not configured for the configured uplink grant:
4 >
if drx-LastTransmissionUL is configured:
5 >
start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission.
4 >
else:
5 >
start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission.
2 >
stop the drx-RetransmissionTimerUL for the corresponding HARQ process at the first transmission (within a bundle) of the corresponding PUSCH transmission.
1 >
if a MAC PDU is transmitted in a configured sidelink grant:
2 >
if the PUCCH resource is configured:
3 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or
3 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted;
3 >
stop the drx-RetransmissionTimerSL for the corresponding HARQ process.
2 >
else:
3 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the end of the corresponding PSSCH transmission;
3 >
stop the drx-RetransmissionTimerSL for the corresponding HARQ process.
1 >
if a drx-HARQ-RTT-TimerDL expires:
2 >
if the data of the corresponding HARQ process was not successfully decoded:
3 >
start the drx-RetransmissionTimerDL for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerDL.
1 >
if a HARQ-RTT-TimerDL-NTN expires:
2 >
if the data of the corresponding HARQ process was not successfully decoded:
3 >
start the drx-RetransmissionTimerDL for the corresponding HARQ process in the first symbol after the expiry of HARQ-RTT-TimerDL-NTN.
1 >
if a drx-HARQ-RTT-TimerUL expires:
2 >
start the drx-RetransmissionTimerUL for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerUL.
1 >
if a HARQ-RTT-TimerUL-NTN expires:
2 >
start the drx-RetransmissionTimerUL for the corresponding HARQ process in the first symbol after the expiry of HARQ-RTT-TimerUL-NTN.
1 >
if a drx-HARQ-RTT-TimerSL expires:
2 >
if a HARQ NACK feedback for the corresponding HARQ process is transmitted on PUCCH; or
2 >
if a HARQ NACK feedback for the corresponding HARQ process is generated but not transmitted on PUCCH; or
2 >
if the PUCCH resource is not configured for the SL grant:
3 >
start the drx-RetransmissionTimerSL for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerSL.
1 >
if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission or a Long DRX Command MAC CE is received:
2 >
stop drx-onDurationTimer for each DRX group;
2 >
stop drx-InactivityTimer for each DRX group.
1 >
if drx-InactivityTimer for a DRX group expires:
2 >
if the Short DRX cycle is configured:
3 >
start or restart drx-ShortCycleTimer for this DRX group in the first symbol after the expiry of drx-InactivityTimer;
3 >
use the Short DRX cycle for this DRX group.
2 >
else:
3 >
use the Long DRX cycle for this DRX group.
1 >
if a DRX Command MAC CE indicated by PDCCH addressed to C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission is received:
2 >
if the Short DRX cycle is configured:
3 >
start or restart drx-ShortCycleTimer for each DRX group in the first symbol after the end of DRX Command MAC CE reception;
3 >
use the Short DRX cycle for each DRX group.
2 >
else:
3 >
use the Long DRX cycle for each DRX group.
1 >
if drx-ShortCycleTimer for a DRX group expires:
2 >
use the Long DRX cycle for this DRX group.
1 >
if a Long DRX Command MAC CE is received:
2 >
stop drx-ShortCycleTimer for each DRX group;
2 >
use the Long DRX cycle for each DRX group.
1 >
if the drx-NonIntegerLongCycleStartOffset is configured:
2 >
increment DRX_SFN_COUNTER by 1 in the first symbol of a slot in which SFN changes to 0;
2 >
if DRX is (re-)configured by RRC:
3 >
if drx-TimeReferenceSFN is included in the RRC (re-)configuration which is received during the first half of a hyper frame (i.e., SFN is between 0 and 511):
4 >
set DRX_SFN_COUNTER to 1.
3 >
else:
4 >
set DRX_SFN_COUNTER to 0.
1 >
if the Short DRX cycle is used for a DRX group and the drx-NonIntegerShortCycle is not configured, and [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle); or
1 >
if the Short DRX cycle is used for a DRX group and the drx-NonIntegerShortCycle is configured, and floor([(DRX_SFN_COUNTER × 10240) + (SFN × 10) + subframe number - drx-StartOffset] modulo (drx-NonIntegerShortCycle)) = 0:
2 >
start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.
1 >
if the Long DRX cycle is used for a DRX group and the drx-NonIntegerLongCycleStartOffset is not configured, and [(SFN × 10) + subframe number] modulo (drx-LongCycle) = drx-StartOffset; or
1 >
if the Long DRX cycle is used for a DRX group and the drx-NonIntegerLongCycleStartOffset is configured, and floor([(DRX_SFN_COUNTER × 10240) + (SFN × 10) + subframe number] modulo (drx-NonIntegerLongCycle)) = drx-StartOffset:
2 >
if DCP monitoring is configured for the active DL BWP as specified in clause 10.3 of TS 38.213:
3 >
if DCP indication associated with the current DRX cycle received from lower layer indicated to start drx-onDurationTimer, as specified in TS 38.213; or
3 >
if all DCP occasion(s) in time domain, as specified in TS 38.213, associated with the current DRX cycle occurred in Active Time considering grants/assignments/DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to start of the last DCP occasion, or during a measurement gap, or when the MAC entity monitors for a PDCCH transmission on the search space indicated by recoverySearchSpaceId of the SpCell identified by the C-RNTI while the ra-ResponseWindow is running (as specified in clause 5.1.4); or
3 >
if ps-Wakeup is configured with value true and DCP indication associated with the current DRX cycle has not been received from lower layers:
4 >
start drx-onDurationTimer after drx-SlotOffset from the beginning of the subframe.
2 >
else:
3 >
start drx-onDurationTimer for this DRX group after drx-SlotOffset from the beginning of the subframe.
1 >
if a DRX group is in Active Time:
2 >
monitor the PDCCH on the Serving Cells in this DRX group as specified in TS 38.213;
2 >
if the PDCCH indicates a DL transmission; or
2 >
if the PDCCH indicates a one-shot HARQ feedback as specified in clause 9.1.4 of TS 38.213; or
2 >
if the PDCCH indicates a retransmission of HARQ feedback as specified in clause 9.1.5 of TS 38.213:
3 >
if this Serving Cell is configured with downlinkHARQ-FeedbackDisabled:
4 >
if the corresponding HARQ process is configured with HARQ feedback enabled:
5 >
set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;
5 >
start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
3 >
else:
4 >
start or restart the drx-HARQ-RTT-TimerDL for the corresponding HARQ process(es) whose HARQ feedback is reported in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
3 >
stop the drx-RetransmissionTimerDL for the corresponding HARQ process(es) whose HARQ feedback is reported;
3 >
stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process;
3 >
if the PDSCH-to-HARQ_feedback timing indicate an inapplicable k1 value as specified in TS 38.213:
4 >
start the drx-RetransmissionTimerDL in the first symbol after the (end of the last) PDSCH transmission (within a bundle) for the corresponding HARQ process.
2 >
if the PDCCH indicates a UL transmission:
3 >
if this Serving Cell is configured with uplinkHARQ-Mode:
4 >
if the corresponding HARQ process is configured as HARQModeA:
5 >
set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value;
5 >
if drx-LastTransmissionUL is configured:
6 >
start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission.
5 >
else:
6 >
start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission.
3 >
else:
4 >
if drx-LastTransmissionUL is configured:
5 >
start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the last transmission (within a bundle) of the corresponding PUSCH transmission.
4 >
else:
5 >
start the drx-HARQ-RTT-TimerUL for the corresponding HARQ process in the first symbol after the end of the first transmission (within a bundle) of the corresponding PUSCH transmission.
3 >
stop the drx-RetransmissionTimerUL for the corresponding HARQ process.
2 >
if the PDCCH indicates an SL transmission:
3 >
if the PUCCH resource is configured:
4 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH transmission carrying the SL HARQ feedback; or
4 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the corresponding PUCCH resource for the SL HARQ feedback when the PUCCH is not transmitted;
4 >
stop the drx-RetransmissionTimerSL for the corresponding HARQ process.
3 >
else:
4 >
start the drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after end of PDCCH occasion;
4 >
stop the drx-RetransmissionTimerSL for the corresponding HARQ process.
2 >
if the PDCCH indicates a new transmission (DL, UL or SL) on a Serving Cell in this DRX group:
3 >
start or restart drx-InactivityTimer for this DRX group in the first symbol after the end of the PDCCH reception.
2 >
if a HARQ process receives downlink feedback information and acknowledgement is indicated:
3 >
stop the drx-RetransmissionTimerUL for the corresponding HARQ process.
1 >
if DCP monitoring is configured for the active DL BWP as specified in clause 10.3 of TS 38.213; and
1 >
if the current symbol n occurs within drx-onDurationTimer duration; and
1 >
if drx-onDurationTimer associated with the current DRX cycle is not started as specified in this clause:
2 >
if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and
2 >
if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or if all multicast DRXes would not be in Active Time considering multicast assignments/DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions are configured with multicast DRX:
3 >
not transmit periodic SRS and semi-persistent SRS defined in TS 38.214;
3 >
not report semi-persistent CSI configured on PUSCH;
3 >
not report semi-persistent CSI on PUCCH;
3 >
if ps-TransmitPeriodicL1-RSRP is not configured with value true:
4 >
not report periodic CSI that is L1-RSRP on PUCCH.
3 >
if ps-TransmitOtherPeriodicCSI is not configured with value true:
4 >
not report periodic CSI that is not L1-RSRP on PUCCH.
1 >
else:
2 >
in current symbol n, if a DRX group would not be in Active Time considering grants/assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE/Long DRX Command MAC CE received and Scheduling Request sent until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and
2 >
if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol n, if all multicast DRXes corresponding to the DRX group would not be in Active Time considering multicast assignments/DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX:
3 >
not transmit periodic SRS and semi-persistent SRS defined in TS 38.214 in this DRX group;
3 >
not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group.
2 >
if CSI masking (csi-Mask) is setup by upper layers:
3 >
in current symbol n, if drx-onDurationTimer of a DRX group would not be running considering grants/assignments scheduled on Serving Cell(s) in this DRX group and DRX Command MAC CE/Long DRX Command MAC CE received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in this clause; and
3 >
if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any of the active BWP(s) of the Serving Cell(s), or, in current symbol n, if drx-onDurationTimerPTM(s) of all multicast DRXes corresponding to the DRX group would not be running considering DRX Command MAC CE for MBS multicast received until 4 ms prior to symbol n when evaluating all DRX Active Time conditions as specified in Clause 5.7b and all multicast sessions corresponding to the DRX group are configured with multicast DRX:
4 >
not report CSI on PUCCH in this DRX group.
The MAC entity shall ensure no rounding error is generated when performing the modulus operation with drx-NonIntegerShortCycle or drx-NonIntegerLongCycle as the divisor.
Regardless of whether the MAC entity is monitoring PDCCH or not on the Serving Cells in a DRX group, the MAC entity transmits HARQ feedback, aperiodic CSI on PUSCH, and aperiodic SRS defined in TS 38.214 on the Serving Cells in the DRX group when such is expected.
The MAC entity needs not to monitor the PDCCH if it is not a complete PDCCH occasion (e.g. the Active Time starts or ends in the middle of a PDCCH occasion).
When drx-LastTransmissionUL is configured, drx-HARQ-RTT-TimerUL or HARQ-RTT-TimerUL-NTN is started after the last PUSCH transmission occasion of a bundle regardless of whether that last PUSCH transmission occasion is used for a PUSCH transmission for that bundle or not.
Up

5.7a  Discontinuous Reception (DRX) for MBS Broadcast |R17|  p. 102

For MBS broadcast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s) as specified in TS 38.331. When in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED, if broadcast DRX is configured for a G-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI discontinuously using the broadcast DRX operation specified in this clause; otherwise the MAC entity monitors each PDCCH for this G-RNTI as specified in TS 38.213. The broadcast DRX operation specified in this clause is performed independently for each G-RNTI and independently from the DRX operation specified in clauses 5.7 and 5.7b.
RRC controls broadcast DRX operation by configuring the following parameters:
  • drx-onDurationTimerPTM: the duration at the beginning of a DRX cycle;
  • drx-SlotOffsetPTM: the delay before starting the drx-onDurationTimerPTM;
  • drx-InactivityTimerPTM: the duration after the PDCCH occasion in which a PDCCH indicates a new DL broadcast transmission for the MAC entity;
  • drx-LongCycleStartOffsetPTM: the long DRX cycle drx-LongCycle-PTM and drx-StartOffset-PTM which defines the subframe where the DRX cycle starts.
When broadcast DRX is configured for a G-RNTI, the Active Time includes the time while:
  • drx-onDurationTimerPTM or drx-InactivityTimerPTM for this G-RNTI is running.
When broadcast DRX is configured for a G-RNTI, the MAC entity shall for this G-RNTI:
1 >
if [(SFN × 10) + subframe number] modulo (drx-LongCycle-PTM) = drx-StartOffset-PTM:
2 >
start drx-onDurationTimerPTM after drx-SlotOffsetPTM from the beginning of the subframe.
1 >
if the MAC entity is in Active Time for this G-RNTI:
2 >
monitor the PDCCH for this G-RNTI as specified in TS 38.213;
2 >
if the PDCCH indicates a DL transmission for MBS broadcast:
3 >
start or restart drx-InactivityTimerPTM in the first symbol after the end of the PDCCH reception.
Up

5.7b  Discontinuous Reception (DRX) for MBS Multicast |R17|  p. 103

For MBS multicast, the MAC entity may be configured by RRC with a DRX functionality per G-RNTI or per G-CS-RNTI that controls the UE's PDCCH monitoring activity for the MAC entity's G-RNTI(s) and G-CS-RNTI(s) as specified in TS 38.331. When in RRC_CONNECTED, if multicast DRX is configured for a G-RNTI or G-CS-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI or G-CS-RNTI discontinuously using the multicast DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH for this G-RNTI or G-CS-RNTI as specified in TS 38.213. When in RRC_INACTIVE, if the UE is configured to receive multicast in RRC_INACTIVE and multicast DRX is configured for a G-RNTI, the MAC entity is allowed to monitor the PDCCH for this G-RNTI discontinuously using the multicast DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH for this G-RNTI as specified in TS 38.213. The multicast DRX operation specified in this clause is performed independently for each G-RNTI or G-CS-RNTI and independently from the DRX operation specified in clauses 5.7 and 5.7a.
RRC controls multicast DRX operation per G-RNTI or per G-CS-RNTI by configuring the following parameters:
  • drx-onDurationTimerPTM: the duration at the beginning of a DRX cycle;
  • drx-SlotOffsetPTM: the delay before starting the drx-onDurationTimerPTM;
  • drx-InactivityTimerPTM: the duration after the PDCCH occasion in which a PDCCH indicates a new DL multicast transmission for the MAC entity;
  • drx-LongCycleStartOffsetPTM: the long DRX cycle drx-LongCycle-PTM and drx-StartOffset-PTM which defines the subframe where the long DRX cycle starts;
  • drx-RetransmissionTimerDL-PTM (per DL HARQ process for MBS multicast): the maximum duration until a DL multicast retransmission is received;
  • drx-HARQ-RTT-TimerDL-PTM (per DL HARQ process for MBS multicast): the minimum duration before a DL multicast assignment for HARQ retransmission is expected by the MAC entity.
The following MAC timer is used for DRX operation in a non-terrestrial network:
  • HARQ-RTT-TimerDL-PTM-NTN (per DL HARQ process for MBS multicast): the minimum duration before a DL multicast assignment for HARQ retransmission is expected by the MAC entity.
When multicast DRX is configured for a G-RNTI or G-CS-RNTI, the Active Time includes the time while:
  • drx-onDurationTimerPTM or drx-InactivityTimerPTM or drx-RetransmissionTimerDL-PTM for this G-RNTI or G-CS-RNTI is running.
When multicast DRX is not configured for a G-RNTI or G-CS-RNTI, and the cfr-ConfigMulticast is configured for at least one of the active BWP(s) of the Serving Cell(s), and unicast DRX is configured, the MAC entity shall for this G-RNTI or G-CS-RNTI:
1 >
monitor the PDCCH as specified in TS 38.213;
1 >
if the PDCCH indicates a DL multicast transmission; or
1 >
if a MAC PDU is received in a configured downlink multicast assignment:
2 >
stop the drx-RetransmissionTimerDL for the corresponding HARQ process.
1 >
if the PDCCH addressed to G-RNTI indicates a DL multicast transmission; or
1 >
if the PDCCH addressed to G-CS-RNTI indicates a DL multicast transmission and CS-RNTI is configured; or
1 >
if a MAC PDU is received in a configured downlink multicast assignment and CS-RNTI is configured:
2 >
if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213; and
2 >
if HARQ feedback for MBS multicast is enabled:
3 >
if the MAC PDU is received on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
4 >
set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;
4 >
start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
3 >
else:
4 >
start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
When multicast DRX is configured for a G-RNTI or G-CS-RNTI, and the cfr-ConfigMulticast is configured for at least one of the active BWP(s) of the Serving Cell(s), or when multicast DRX is configured for a G-RNTI for multicast in RRC_INACTVE, the MAC entity shall for this G-RNTI or G-CS-RNTI:
1 >
if a MAC PDU is received in a configured downlink multicast assignment:
2 >
if HARQ feedback for MBS multicast is enabled:
3 >
if the MAC PDU is received on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
4 >
set HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL-PTM plus the latest available UE-gNB RTT value;
4 >
start the HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
3 >
else:
4 >
start the drx-HARQ-RTT-TimerDL-PTM for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback;
3 >
if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213; and
3 >
if CS-RNTI is configured:
4 >
if the MAC PDU is received on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
5 >
set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;
5 >
start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
4 >
else:
5 >
start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
2 >
else if drx-HARQ-RTT-TimerDL-PTM is configured:
3 >
if the MAC PDU is received on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
4 >
set HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL-PTM plus the latest available UE-gNB RTT value;
4 >
start the HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled.
3 >
else:
4 >
start the drx-HARQ-RTT-TimerDL-PTM for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled.
2 >
stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process;
2 >
stop the drx-RetransmissionTimerDL for the corresponding HARQ process.
1 >
if a drx-HARQ-RTT-TimerDL-PTM expires:
2 >
if the data of the corresponding HARQ process was not successfully decoded:
3 >
start the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process in the first symbol after the expiry of drx-HARQ-RTT-TimerDL-PTM.
1 >
if a HARQ-RTT-TimerDL-PTM-NTN expires:
2 >
if the data of the corresponding HARQ process was not successfully decoded:
3 >
start the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process in the first symbol after the expiry of HARQ-RTT-TimerDL-PTM-NTN.
1 >
if a DRX Command MAC CE indicated by PDCCH addressed to a G-RNTI or G-CS-RNTI, or by a configured downlink multicast assignment is received:
2 >
stop drx-onDurationTimerPTM of the DRX for this G-RNTI or G-CS-RNTI, or the corresponding G-CS-RNTI;
2 >
stop drx-InactivityTimerPTM of the DRX for this G-RNTI or G-CS-RNTI, or the corresponding G-CS-RNTI.
1 >
if [(SFN × 10) + subframe number] modulo (drx-LongCycle-PTM) = drx-StartOffset-PTM:
2 >
start drx-onDurationTimerPTM after drx-SlotOffsetPTM from the beginning of the subframe.
1 >
if the MAC entity is in Active Time for this G-RNTI or G-CS-RNTI:
2 >
monitor the PDCCH for this G-RNTI or G-CS-RNTI as specified in TS 38.213;
2 >
if the PDCCH indicates a DL multicast transmission:
3 >
if HARQ feedback for MBS multicast is enabled:
4 >
if the PDCCH is indicated on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
5 >
set HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL-PTM plus the latest available UE-gNB RTT value;
5 >
start the HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
4 >
else:
5 >
start the drx-HARQ-RTT-TimerDL-PTM for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback;
4 >
if the first HARQ-ACK reporting mode (i.e. ack-nack) is used as specified in TS 38.213:
5 >
if the PDCCH addressed to G-RNTI indicates a DL multicast transmission; or
5 >
if the PDCCH addressed to G-CS-RNTI indicates a DL multicast transmission and CS-RNTI is configured:
6 >
if the PDCCH is indicated on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
7 >
set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;
7 >
start the HARQ-RTT-TimerDL-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
6 >
else:
7 >
start the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.
3 >
else if drx-HARQ-RTT-TimerDL-PTM is configured for multicast in RRC_INACTIVE:
4 >
if the PDCCH is indicated on a non-terrestrial network and the UE supports ptm-RetransmissionInactive:
5 >
set HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL-PTM plus the latest available UE-gNB RTT value;
5 >
start the HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding multicast transmission.
4 >
else if the UE supports ptm-RetransmissionInactive:
5 >
start the drx-HARQ-RTT-TimerDL-PTM for the corresponding HARQ process in the first symbol after the end of the corresponding multicast transmission.
3 >
else if drx-HARQ-RTT-TimerDL-PTM is configured:
4 >
if the PDCCH is indicated on a non-terrestrial network and the UE supports harq-RTT-TimerDL-ForNTN-MulticastMBS-r17:
5 >
set HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process equal to drx-HARQ-RTT-TimerDL-PTM plus the latest available UE-gNB RTT value;
5 >
start the HARQ-RTT-TimerDL-PTM-NTN for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled.
4 >
else:
5 >
start the drx-HARQ-RTT-TimerDL-PTM for the corresponding HARQ process in the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback that would be performed if HARQ feedback were enabled.
3 >
stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ process;
3 >
stop the drx-RetransmissionTimerDL for the corresponding HARQ process.
2 >
if the PDCCH indicates a new multicast transmission for this G-RNTI or G-CS-RNTI:
3 >
start or restart drx-InactivityTimerPTM in the first symbol after the end of the PDCCH reception.
The MAC entity needs not to monitor the PDCCH for a G-RNTI or a G-CS-RNTI if it is not a complete PDCCH occasion (e.g. the Active Time for a G-RNTI or a G-CS-RNTI starts or ends in the middle of a PDCCH occasion).
Up

5.8  Transmission and reception without dynamic scheduling  p. 107

5.8.1  Downlink  p. 107

Semi-Persistent Scheduling (SPS) is configured by RRC for a Serving Cell per BWP. Multiple assignments can be active simultaneously in the same BWP. Activation and deactivation of the DL SPS are independent among the Serving Cells.
For the DL SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS activation or deactivation.
RRC configures the following parameters when the SPS is configured:
  • cs-RNTI: CS-RNTI for activation, deactivation, and retransmission;
  • nrofHARQ-Processes: the number of configured HARQ processes for SPS;
  • harq-ProcID-Offset: Offset of HARQ process for SPS;
  • periodicity: periodicity of configured downlink assignment for SPS.
When the SPS is released by upper layers, all the corresponding configurations shall be released.
After a downlink assignment is configured for SPS, the MAC entity shall consider sequentially that the Nth downlink assignment occurs in the slot for which:
(numberOfSlotsPerFrame × SFN + slot number in the frame) =
[(numberOfSlotsPerFrame × SFNstart time + slotstart time) + N × periodicity × numberOfSlotsPerFrame / 10]
modulo (1024 × numberOfSlotsPerFrame)
where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was (re-)initialised.
Up

5.8.1a  Downlink for Multicast |R17|  p. 108

MBS Semi-Persistent Scheduling (SPS) is only applicable for UEs in RRC_CONNECTED and is configured by RRC on one Serving Cell per BWP. Multiple assignments can be active simultaneously in the same BWP.
For the DL MBS SPS, a DL assignment is provided by PDCCH, and stored or cleared based on L1 signalling indicating SPS activation or deactivation.
RRC configures the following parameters when the MBS SPS is configured:
  • cs-RNTI: CS-RNTI for MBS SPS deactivation, PTP for PTM retransmission if configured;
  • g-cs-RNTI: G-CS-RNTI for activation, deactivation, and retransmission;
  • nrofHARQ-Processes: the number of configured HARQ processes for MBS SPS;
  • harq-ProcID-Offset: Offset of HARQ process for MBS SPS;
  • periodicity: periodicity of configured downlink assignment for MBS SPS.
When the MBS SPS is released by upper layers, all the corresponding configurations shall be released.
After a downlink assignment is configured for MBS SPS, the MAC entity shall consider sequentially that the Nth downlink assignment occurs in the slot for which:
(numberOfSlotsPerFrame × SFN + slot number in the frame) =
[(numberOfSlotsPerFrame × SFNstart time + slotstart time) + N × periodicity × numberOfSlotsPerFrame / 10]
modulo (1024 × numberOfSlotsPerFrame)
where SFNstart time and slotstart time are the SFN and slot, respectively, of the first transmission of PDSCH where the configured downlink assignment was (re-)initialised.
Up

5.8.2  Uplink  p. 108

There are two types of transmission without dynamic grant:
  • configured grant Type 1 where an uplink grant is provided by RRC, and stored as configured uplink grant;
  • configured grant Type 2 where an uplink grant is provided by PDCCH, and stored or cleared as configured uplink grant based on L1 signalling indicating configured uplink grant activation or deactivation.
Type 1 and Type 2 are configured by RRC for a Serving Cell per BWP. Multiple configurations can be active simultaneously in the same BWP. For Type 2, activation and deactivation are independent among the Serving Cells. For the same BWP, the MAC entity can be configured with both Type 1 and Type 2.
A multi-PUSCH configured grant has multiple consecutive configured uplink grants within a periodicity. Both Type 1 and Type 2 can be configured for a multi-PUSCH configured grant by RRC.
Only configured grant Type 1 can be configured for CG-SDT or for RACH-less LTM cell switch or for RACH-less handover. CG-SDT can only be configured on initial BWP.
RRC configures the following parameters when the configured grant Type 1 is configured:
  • cs-RNTI: CS-RNTI for retransmission;
  • cg-SDT-CS-RNTI: CS-RNTI for CG-SDT retransmission;
  • cg-SDT-RSRP-ThresholdSSB: an RSRP threshold configured for SSB selection for CG-SDT;
  • cg-RRC-RSRP-ThresholdSSB: an RSRP threshold configured for SSB selection for RACH-less handover;
  • periodicity: periodicity of the configured grant Type 1;
  • timeDomainOffset: Offset of a resource with respect to SFN = timeReferenceSFN in time domain;
  • timeDomainAllocation: Allocation of configured uplink grant in time domain which contains startSymbolAndLength (i.e. SLIV in TS 38.214) or startSymbol (i.e. S in TS 38.214);
  • nrofHARQ-Processes: the number of HARQ processes for configured grant;
  • harq-ProcID-Offset: offset of HARQ process for configured grant configured with cg-RetransmissionTimer for operation with shared spectrum channel access;
  • harq-ProcID-Offset2: offset of HARQ process for configured grant not configured with cg-RetransmissionTimer;
  • timeReferenceSFN: SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration;
  • timeReferenceH-SFN: H-SFN used for determination of the offset of a resource in time domain. The UE uses the closest H-SFN with the indicated number preceding the reception of the configured grant configuration.
RRC configures the following parameters when the configured grant Type 2 is configured:
  • cs-RNTI: CS-RNTI for activation, deactivation, and retransmission;
  • periodicity: periodicity of the configured grant Type 2;
  • nrofHARQ-Processes: the number of HARQ processes for configured grant;
  • harq-ProcID-Offset: offset of HARQ process for configured grant configured with cg-RetransmissionTimer for operation with shared spectrum channel access;
  • harq-ProcID-Offset2: offset of HARQ process for configured grant not configured with cg-RetransmissionTimer.
RRC configures the following parameter when retransmissions on configured uplink grant is configured:
  • cg-RetransmissionTimer: the duration after a configured grant (re)transmission of a HARQ process when the UE shall not autonomously retransmit that HARQ process;
  • cg-SDT-RetransmissionTimer: the duration after a configured grant (re)transmission of a HARQ process of the initial CG-SDT transmission with CCCH message when the UE shall not autonomously retransmit the HARQ process;
  • cg-RRC-RetransmissionTimer: the duration after a configured grant (re)transmission of a HARQ process of the initial transmission of RACH-less handover and RACH-less LTM cell switch when the UE shall not autonomously retransmit the HARQ process.
RRC configures the following parameter when a multi-PUSCH configured grant is configured:
  • nrofSlotsInCG-Period: the number of configured uplink grants in a periodicity of a multi-PUSCH configured grant.
RRC configures the following parameter when UTO-UCI (as specified in clause 9.3 in TS 38.213) is configured for a configured grant:
  • nrofBitsInUTO-UCI: number of bits in a UTO-UCI bitmap.
For a configured uplink grant, the MAC entity shall:
1 >
if its associated configured grant is configured with UTO-UCI and it has not been indicated to the lower layers as unused for PUSCH transmission; or
1 >
if its associated configured grant is not configured with UTO-UCI:
2 >
if it is associated with a multi-PUSCH configured grant and meets the validity conditions specified in the clause 6.1 in TS 38.214; or
2 >
if it is not associated with a multi-PUSCH configured grant:
3 >
consider it available for use.
The MAC entity shall not include the UL-SCH resource of a configured uplink grant not available for use in its procedures (e.g. in clause 5.4.4).
For a configured grant configured with UTO-UCI, the MAC entity determines if a configured uplink grant which is within the subsequent nrofBitsInUTO-UCI valid occasions of its associated configured grant configuration is going to be used for PUSCH transmission by considering at least the amount of buffered data that can be transmitted on the available occasions of the associated configured grant and other available UL-SCH resources. Upon this determination, the MAC entity sends an indication to lower layers, for use in the procedure for reporting UTO-UCI.
Upon configuration of a configured grant Type 1 for a BWP of a Serving Cell by upper layers, the MAC entity shall:
1 >
store the uplink grant provided by upper layers as a configured uplink grant for the indicated BWP of the Serving Cell;
1 >
initialise or re-initialise the configured uplink grant to start in the symbol according to timeDomainOffset, timeReferenceSFN, and S (derived from SLIV or provided by startSymbol as specified in TS 38.214), and to reoccur with periodicity.
If cg-SDT-PeriodicityExt (as defined in TS 38.331) is not configured, after an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the configured uplink grant, or the first configured uplink grant in a multi-PUSCH configured grant, in the Nth (N ≥ 0) periodicity occurs in the symbol for which:
[(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)
+ (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =
(timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot
+ timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity)
modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)
If cg-SDT-PeriodicityExt (as defined in TS 38.331) is configured, after an uplink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the configured uplink grant, or the first configured uplink grant in a multi-PUSCH configured grant, in the Nth (N ≥ 0) periodicity occurs in the symbol for which:
[(H-SFN × numberOfSFNperH-SFN + SFN) × numberOfSlotsPerFrame × numberOfSymbolsPerSlot
+ (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =
((timeReferenceH-SFN × numberOfSFNperH-SFN + timeReferenceSFN)
× numberOfSlotsPerFrame × numberOfSymbolsPerSlot
+ timeDomainOffset × numberOfSymbolsPerSlot + S + N × periodicity)
modulo (1024 × 1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)
For a multi-PUSCH configured grant Type 1, the Mth (1 < M ≤ nrofSlotsInCG-Period) configured uplink grant within a periodicity occurs (M-1) × numberOfSymbolsPerSlot symbols after the symbol in which the first configured uplink grant in that periodicity occurs.
For an uplink grant configured for configured grant Type 1 for CG-SDT on the selected uplink carrier as in clause 5.27, when CG-SDT is triggered and not terminated, for each configured uplink grant valid according to TS 38.214 for which the above formula is satisfied, the MAC entity shall:
1 >
if, after initial transmission for CG-SDT with CCCH message has been performed according to clause 5.4.1, PDCCH addressed to the MAC entity's C-RNTI has not been received:
2 >
if the SSB corresponding to the configured UL grant has the same SSB index as the SSB selected for initial transmission for CG-SDT with CCCH message (i.e., retransmission of initial transmission of CG-SDT):
3 >
select this SSB;
3 >
indicate the SSB index corresponding to the configured uplink grant to the lower layer;
3 >
consider this configured uplink grant as valid.
1 >
else if at least one SSB configured for CG-SDT with SS-RSRP above cg-SDT-RSRP-ThresholdSSB is available:
2 >
if at least one SSB corresponding to the configured uplink grant with SS-RSRP above the cg-SDT-RSRP-ThresholdSSB is available:
3 >
if this is the initial transmission of CG-SDT with CCCH message after the CG-SDT procedure is initiated as in clause 5.27 (i.e., initial transmission for CG-SDT):
4 >
select an SSB with SS-RSRP above cg-SDT-RSRP-ThresholdSSB amongst the SSB(s) associated with the configured uplink grant.
3 >
else if PDCCH addressed to C-RNTI has been received after the initial transmission of CG-SDT with CCCH message (i.e., subsequent new transmission for CG-SDT):
4 >
if SS-RSRP of the SSB selected for the previous transmission for CG-SDT is above cg-SDT-RSRP-ThresholdSSB and this SSB is associated with this configured uplink grant:
5 >
select this SSB.
4 >
else if SS-RSRP of the SSB selected for the previous transmission for CG-SDT is not above cg-SDT-RSRP-ThresholdSSB:
5 >
select an SSB with SS-RSRP above cg-SDT-RSRP-ThresholdSSB amongst the SSB(s) associated with the configured uplink grant.
3 >
if SSB is selected above:
4 >
indicate the SSB index to the lower layer;
4 >
consider this configured uplink grant as valid.
1 >
else:
2 >
consider this configured uplink grant as not valid.
2 >
if PDCCH addressed to C-RNTI after the initial transmission of the CG-SDT with CCCH message has been received:
3 >
if there is data available for transmission for at least one RB configured for SDT:
4 >
initiate Random Access procedure in clause 5.1.
For an uplink grant configured for configured grant Type 1 for RACH-less LTM cell switch, when there is an ongoing RACH-less LTM cell switch procedure, for each configured uplink grant valid according to TS 38.214 for which the above formula is satisfied, the MAC entity shall:
1 >
if an SSB corresponding to the configured UL grant has the same SSB index as the SSB associated with the TCI state indicated by the TCI state ID field in LTM Cell Switch Command MAC CE, as specified in clause 5.18.35:
2 >
select the SSB associated with the TCI state indicated by LTM Cell Switch Command MAC CE.
2 >
indicate the SSB index to the lower layer;
2 >
consider this configured uplink grant as valid.
1 >
else:
2 >
consider this configured uplink grant as not valid.
For the uplink grant configured for configured grant Type 1 for RACH-less handover, if the configured uplink grant is valid according to TS 38.214 for which the above formula is satisfied, the MAC entity shall:
1 >
if, after the initial transmission of RACH-less handover has been performed according to clause 5.4.1 and 5.33, RACH-less handover is not successfully completed:
2 >
if the SSB corresponding to the configured UL grant has the same SSB index as the SSB selected for the initial transmission of RACH-less handover (i.e., retransmission of initial transmission of RACH-less handover):
3 >
select this SSB;
3 >
indicate the SSB index corresponding to the configured uplink grant to the lower layer;
3 >
consider this configured uplink grant as valid.
1 >
else if at least one SSB corresponding to the configured uplink grant with SS-RSRP above cg-RRC-RSRP-ThresholdSSB is available:
2 >
select an SSB with SS-RSRP above cg-RRC-RSRP-ThresholdSSB amongst the SSB(s) associated with the configured uplink grant;
2 >
indicate the selected SSB index to the lower layer;
2 >
consider this configured uplink grant as valid.
1 >
else:
2 >
consider this configured uplink grant as not valid;
2 >
initiate Random Access procedure in clause 5.1.
After an uplink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the configured uplink grant, or the first configured uplink grant in a multi-PUSCH configured grant, in the Nth (N ≥ 0) periodicity occurs in the symbol for which:
[(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)
+ (slot number in the frame × numberOfSymbolsPerSlot) + symbol number in the slot] =
[(SFNstart time × numberOfSlotsPerFrame × numberOfSymbolsPerSlot
+ slotstart time × numberOfSymbolsPerSlot + symbolstart time) + N × periodicity]
modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)
where SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, of the first transmission opportunity of PUSCH where the configured uplink grant was (re-)initialised.
For a multi-PUSCH configured grant Type 2, the Mth (1 < M ≤ nrofSlotsInCG-Period) configured uplink grant within the same periodicity occurs (M-1) × numberOfSymbolsPerSlot symbols after the symbol in which the first configured uplink grant in that periodicity occurs.
If cg-nrofPUSCH-InSlot or cg-nrofSlots is configured for a configured grant Type 1 or Type 2, the MAC entity shall consider the uplink grants occur in those additional PUSCH allocations as specified in clause 6.1.2.3 of TS 38.214.
When the configured uplink grant is released by upper layers, all the corresponding configurations shall be released and all corresponding uplink grants shall be cleared.
The MAC entity shall:
1 >
if at least one configured uplink grant confirmation has been triggered and not cancelled; and
1 >
if the MAC entity has UL resources allocated for new transmission:
2 >
if, in this MAC entity, at least one configured uplink grant is configured by configuredGrantConfigToAddModList:
3 >
instruct the Multiplexing and Assembly procedure to generate a Multiple Entry Configured Grant Confirmation MAC CE as defined in clause 6.1.3.31.
2 >
else:
3 >
instruct the Multiplexing and Assembly procedure to generate a Configured Grant Confirmation MAC CE as defined in clause 6.1.3.7.
2 >
cancel all triggered configured uplink grant confirmation(s).
For a configured grant Type 2, the MAC entity shall clear the configured uplink grant(s) immediately after first transmission of Configured Grant Confirmation MAC CE or Multiple Entry Configured Grant Confirmation MAC CE which confirms the configured uplink grant deactivation.
Retransmissions use:
  • repetition of configured uplink grants; or
  • received uplink grants addressed to CS-RNTI; or
  • configured uplink grants with cg-RetransmissionTimer, cg-RRC-RetransmissionTimer or cg-SDT-RetransmissionTimer configured.
Up

5.8.3  Sidelink |R16|  p. 113

There are two types of transmission without dynamic sidelink grant:
  • configured grant Type 1 where an sidelink grant is provided by RRC, and stored as configured sidelink grant;
  • configured grant Type 2 where an sidelink grant is provided by PDCCH, and stored or cleared as configured sidelink grant based on L1 signalling indicating configured sidelink grant activation or deactivation.
Type 1 and/or Type 2 are configured with a single BWP. Multiple configurations of up to 8 configured grants (including both Type 1 and Type 2, if configured) can be active simultaneously on the BWP.
RRC configures the following parameters when the configured grant Type 1 is configured, as specified in TS 38.331 or TS 36.331:
  • sl-ConfigIndexCG: the identifier of a configured grant for sidelink;
  • sl-CS-RNTI: SL-CS-RNTI for retransmission;
  • sl-NrOfHARQ-Processes: the number of HARQ processes for configured grant;
  • sl-PeriodCG: periodicity of the configured grant Type 1;
  • sl-TimeOffsetCG-Type1: Offset of a resource with respect to reference logical slot defined by sl-TimeReferenceSFN-Type1 in time domain, referring to the number of logical slots in a resource pool;
  • sl-TimeResourceCG-Type1: time resource location of the configured grant Type 1;
  • sl-CG-MaxTransNumList: the maximum number of times that a TB can be transmitted using the configured grant;
  • sl-HARQ-ProcID-offset: offset of HARQ process for configured grant Type 1;
  • sl-PRS-ResourceID: SL-PRS configuration index for configured grant Type 1;
  • sl-TimeReferenceSFN-Type1: SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the first logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration Type 1 as reference logical slot. If it is absent, the indicated reference SFN is zero.
RRC configures the following parameters when the configured grant Type 2 is configured, as specified in TS 38.331:
  • sl-ConfigIndexCG: the identifier of a configured grant for sidelink;
  • sl-CS-RNTI: SL-CS-RNTI for activation, deactivation, and retransmission;
  • sl-PRS-CS-RNTI: SL-PRS-CS-RNTI for activation, and deactivation;
  • sl-NrOfHARQ-Processes: the number of HARQ processes for configured grant;
  • sl-PeriodCG: periodicity of the configured grant Type 2;
  • sl-CG-MaxTransNumList: the maximum number of times that a TB can be transmitted using the configured grant;
  • sl-HARQ-ProcID-offset: offset of HARQ process for configured grant Type 2.
Upon configuration of a configured grant Type 1, the MAC entity shall for each configured sidelink grant:
1 >
store the sidelink grant provided by RRC as a configured sidelink grant;
1 >
initialise or re-initialise the configured sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) and SL-PRS transmission occasion(s) according to sl-TimeOffsetCG-Type1 and sl-TimeResourceCG-Type1, and to reoccur with sl-periodCG for transmissions of multiple MAC PDUs and SL-PRS(s) according to clause 8.1.2 of TS 38.214.
After a sidelink grant is configured for a configured grant Type 1, the MAC entity shall consider sequentially that the first slot of the Sth sidelink grant occurs in the logical slot for which:
CURRENT_slot = (sl-ReferenceSlotCG-Type1 + sl-TimeOffsetCG-Type1 + S × PeriodicitySL) modulo T'max
where CURRENT_slot refers to current logical slot in the associated resource pool, PeriodicitySL=formula#1 in §5.8.3 and T'max is the number of slots that belongs to the associated resource pool as defined in clause 8 of TS 38.214. sl-ReferenceSlotCG-Type1 refers to reference logical slot defined by sl-TimeReferenceSFN-Type1.
After a sidelink grant is configured for a configured grant Type 2, the MAC entity shall consider sequentially that the first slot of Sth sidelink grant occurs in the logical slot for which:
CURRENT_slot = (sl-StartSlotCG-Type2 + S × PeriodicitySL) modulo T'max
where sl-StartSlotCG-Type2 refers to the logical slot of the first transmission opportunity of PSSCH or SL-PRS where the configured sidelink grant was (re)initialised.
When a configured sidelink grant is released by RRC, all the corresponding configurations shall be released and all corresponding sidelink grants shall be cleared.
The MAC entity shall:
1 >
if the configured sidelink grant confirmation has been triggered and not cancelled; and
1 >
if the MAC entity has UL resources allocated for new transmission:
2 >
instruct the Multiplexing and Assembly procedure to generate a Sidelink Configured Grant Confirmation MAC CE as defined in clause 6.1.3.34;
2 >
cancel the triggered configured sidelink grant confirmation.
For a configured grant Type 2, the MAC entity shall clear the corresponding configured sidelink grant immediately after first transmission of Sidelink Configured Grant Confirmation MAC CE triggered by the configured sidelink grant deactivation.
Up

Up   Top   ToC