Content for TS 38.321 Word version: 18.0.0

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.9 Activation/Deactivation of SCells 5.10 Activation/Deactivation of PDCP duplication 5.11 MAC reconfiguration 5.12 MAC Reset 5.13 Handling of unknown, unforeseen and erroneous protocol data 5.14 Handling of measurement gaps 5.15 Bandwidth Part (BWP) operation 5.15.1 Downlink and Uplink 5.15.2 Sidelink 5.16 SUL operation 5.17 Beam Failure Detection and Recovery procedure
...

5.9 Activation/Deactivation of SCells p. 107

If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured SCells. Upon configuration of an SCell, the SCell is deactivated unless the parameter sCellState is set to activated for the SCell by upper layers.

The configured SCell(s) is activated and deactivated by:

receiving the SCell Activation/Deactivation MAC CE described in clause 6.1.3.10;
receiving the Enhanced SCell Activation/Deactivation MAC CE described in clause 6.1.3.55;
configuring sCellDeactivationTimer timer per configured SCell (except the SCell configured with PUCCH, if any): the associated SCell is deactivated upon its expiry;
configuring sCellState per configured SCell: if configured, the associated SCell is activated upon SCell configuration;
receiving scg-State: the SCells of SCG are deactivated.

The MAC entity shall for each configured SCell:

1 >

if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received activating the SCell:

2 >

if the SCell was deactivated prior to receiving this Enhanced SCell Activation/Deactivation MAC CE and a TRS is indicated for this SCell:

3 >

indicate to lower layers the information regarding the TRS.

2 >

if the SCell was deactivated prior to receiving this SCell Activation/Deactivation MAC CE or this Enhanced SCell Activation/Deactivation MAC CE; or

2 >

if the SCell is configured with sCellState set to activated upon SCell configuration:

3 >

if firstActiveDownlinkBWP-Id is not set to dormant BWP:

4 >

activate the SCell according to the timing defined in TS 38.213 for MAC CE activation and according to the timing defined in TS 38.133 for direct SCell activation; i.e. apply normal SCell operation including:

5 >

SRS transmissions on the SCell;

5 >

CSI reporting for the SCell;

5 >

PDCCH monitoring on the SCell;

5 >

PDCCH monitoring for the SCell;

5 >

PUCCH transmissions on the SCell, if configured.

3 >

else (i.e. firstActiveDownlinkBWP-Id is set to dormant BWP):

4 >

stop the bwp-InactivityTimer of this Serving Cell, if running.

3 >

activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

2 >

start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213 for MAC CE activation and according to the timing defined in TS 38.133 for direct SCell activation;

2 >

if the active DL BWP is not the dormant BWP:

3 >

(re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2;

3 >

trigger PHR according to clause 5.4.6.

1 >

else if an SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received deactivating the SCell; or

1 >

if the sCellDeactivationTimer associated with the activated SCell expires; or

1 >

if the SCG associated with the activated SCell is deactivated:

2 >

deactivate the SCell according to the timing defined in TS 38.213;

2 >

stop the sCellDeactivationTimer associated with the SCell;

2 >

stop the bwp-InactivityTimer associated with the SCell;

2 >

deactivate any active BWP associated with the SCell;

2 >

clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

2 >

clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;

2 >

suspend any configured uplink grant Type 1 associated with the SCell;

2 >

flush all HARQ buffers associated with the SCell;

2 >

cancel, if any, triggered consistent LBT failure for the SCell.

1 >

if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or

1 >

if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

1 >

if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

1 >

if a MAC PDU is received in a configured downlink assignment:

2 >

restart the sCellDeactivationTimer associated with the SCell.

1 >

if the SCell is deactivated:

2 >

not transmit SRS on the SCell;

2 >

not report CSI for the SCell;

2 >

not transmit on UL-SCH on the SCell;

2 >

not transmit on RACH on the SCell;

2 >

not monitor the PDCCH on the SCell;

2 >

not monitor the PDCCH for the SCell;

2 >

not transmit PUCCH on the SCell.

When the measurement reporting for fast unknown SCell activation is configured by RRC, the MAC entity shall:

1 >

if SCell Activation/Deactivation MAC CE or an Enhanced SCell Activation/Deactivation MAC CE is received activating the SCell(s):

2 >

if SCell(s) was deactivated prior to receiving this SCell Activation/Deactivation MAC CE or this Enhanced SCell Activation/Deactivation MAC CE:

3 >

indicate to upper layers SCell(s) activation indication.

HARQ feedback for the MAC PDU containing SCell Activation/Deactivation MAC CE or Enhanced SCell Activation/Deactivation MAC CE shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation in TS 38.133.

When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted.

5.10 Activation/Deactivation of PDCP duplication p. 109

If one or more DRBs are configured with PDCP duplication, the network may activate and deactivate the PDCP duplication for all or a subset of associated RLC entities for the configured DRB(s).

The PDCP duplication for the configured DRB(s) is activated and deactivated by:

receiving the Duplication Activation/Deactivation MAC CE described in clause 6.1.3.11;
receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32;
indication by RRC.

The PDCP duplication for all or a subset of associated RLC entities for the configured DRB(s) is activated and deactivated by:

receiving the Duplication RLC Activation/Deactivation MAC CE described in clause 6.1.3.32;
indication by RRC.

The PDCP duplication for all associated RLC entities for the configured DRB(s) is activated by:

receiving an uplink grant addressed to CS-RNTI with NDI=1 for a logical channel associated with the DRB configured with survivalTimeStateSupport, described in clause 5.4.1.

The MAC entity shall for each DRB configured with PDCP duplication:

1 >

if a Duplication Activation/Deactivation MAC CE is received activating the PDCP duplication of the DRB:

2 >

indicate the activation of PDCP duplication of the DRB to upper layers.

1 >

if a Duplication Activation/Deactivation MAC CE is received deactivating the PDCP duplication of the DRB:

2 >

indicate the deactivation of PDCP duplication of the DRB to upper layers.

1 >

if a Duplication RLC Activation/Deactivation MAC CE is received activating PDCP duplication for associated RLC entities of a DRB configured with PDCP duplication:

2 >

indicate the activation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to upper layers.

1 >

if a Duplication RLC Activation/Deactivation MAC CE is received deactivating PDCP duplication for associated RLC entities of a DRB configured with PDCP duplication:

2 >

indicate the deactivation of PDCP duplication for the indicated secondary RLC entity(ies) of the DRB to upper layers.

1 >

if activation of a PDCP duplication for all configured RLC entities is triggered for the DRB as specified in clause 5.4.1:

2 >

indicate the activation of PDCP duplication for all configured RLC entities of the DRB to upper layers.

5.11 MAC reconfiguration p. 110

When a reconfiguration of the MAC entity is requested by upper layers, the MAC entity shall:

1 >

initialize the corresponding HARQ entity upon addition of an SCell;

1 >

remove the corresponding HARQ entity upon removal of an SCell;

1 >

apply the new value for timers when the timer is (re)started;

1 >

apply the new maximum parameter value when counters are initialized;

1 >

apply immediately the configurations received from upper layers for other parameters.

5.12 MAC Reset p. 110

If a reset of the MAC entity is requested by upper layers or the reset of the MAC entity is triggered due to SCG deactivation as defined in clause 5.29, the MAC entity shall:

1 >

if the MAC reset is not due to SCG deactivation:

2 >

initialize Bj for each logical channel to zero;

1 >

initialize SBj for each logical channel to zero if Sidelink resource allocation mode 1 is configured by RRC;

1 >

if upper layers indicate SCG deactivation and bfd-and-RLM with value true is configured for the deactivated SCG:

2 >

stop (if running) all timers except beamFailureDetectionTimer associated with PSCell and timeAlignmentTimers.

1 >

else:

2 >

stop (if running) all timers, except MBS broadcast DRX timers;

2 >

consider all timeAlignmentTimers, inactivePosSRS-TimeAlignmentTimer, and cg-SDT-TimeAlignmentTimer, if configured, as expired and perform the corresponding actions in clause 5.2;

1 >

set the NDIs for all uplink HARQ processes to the value 0;

1 >

sets the NDIs for all HARQ process IDs to the value 0 for monitoring PDCCH in Sidelink resource allocation mode 1;

1 >

stop, if any, ongoing Random Access procedure;

1 >

discard explicitly signalled contention-free Random Access Resources for 4-step RA type and 2-step RA type, if any;

1 >

flush Msg3 buffer;

1 >

flush MSGA buffer;

1 >

cancel, if any, triggered Scheduling Request procedure;

1 >

cancel, if any, triggered Buffer Status Reporting procedure;

1 >

cancel, if any, triggered Delay Status Reporting procedure;

1 >

cancel, if any, triggered Power Headroom Reporting procedure;

1 >

cancel, if any, triggered consistent LBT failure;

1 >

cancel, if any, triggered Sidelink consistent LBT failure;

1 >

cancel, if any, triggered BFR;

1 >

cancel, if any, triggered Sidelink Buffer Status Reporting procedure;

1 >

cancel, if any, triggered Pre-emptive Buffer Status Reporting procedure;

1 >

cancel, if any, triggered Timing Advance Reporting procedure;

1 >

cancel, if any, triggered Recommended bit rate query procedure;

1 >

cancel, if any, triggered Configured uplink grant confirmation;

1 >

cancel, if any, triggered configured sidelink grant confirmation;

1 >

clear, if any, configured sidelink grants;

1 >

cancel, if any, triggered Desired Guard Symbol query;

1 >

cancel, if any, triggered Positioning Measurement Gap Activation/Deactivation Request procedure;

1 >

cancel, if any, triggered SDT procedure;

1 >

cancel, if any, triggered IAB-MT Recommended Beam Indication query;

1 >

cancel, if any, triggered Desired DL TX Power Adjustment query;

1 >

cancel, if any, triggered Desired IAB-MT PSD range query;

1 >

cancel, if any, triggered Case-6 Timing Request query;

1 >

flush the soft buffers for all DL HARQ processes, except for the DL HARQ process being used for MBS broadcast;

1 >

for each DL HARQ process, except for the DL HARQ process being used for MBS broadcast, consider the next received transmission for a TB as the very first transmission;

1 >

release, if any, Temporary C-RNTI;

1 >

clear, if any, Differential Koffset;

1 >

if upper layers indicate SCG deactivation and bfd-and-RLM with value true is not configured; or

1 >

if the MAC reset is not due to SCG deactivation:

2 >

reset all BFI_COUNTERs;

1 >

reset all LBT_COUNTERs.

If a Sidelink specific reset of the MAC entity is requested for a PC5-RRC connection by upper layers, the MAC entity shall:

1 >

flush the soft buffers for all Sidelink processes for all TB(s) associated to the PC5-RRC connection;

1 >

consider all Sidelink processes for all TB(s) associated to the PC5-RRC connection as unoccupied;

1 >

cancel, if any, triggered Scheduling Request procedure only associated to the PC5-RRC connection;

1 >

cancel, if any, triggered Sidelink Buffer Status Reporting procedure only associated to the PC5-RRC connection;

1 >

cancel, if any, triggered Sidelink CSI Reporting procedure associated to the PC5-RRC connection;

1 >

cancel, if any, triggered Sidelink DRX Command MAC CE associated to the PC5-RRC connection;

1 >

cancel, if any, triggered Sidelink IUC-Request transmission procedure associated to the PC5-RRC connection;

1 >

cancel, if any, triggered Sidelink IUC-Information Reporting procedure associated to the PC5-RRC connection;

1 >

stop (if running) all timers associated to the PC5-RRC connection;

1 >

reset the numConsecutiveDTX associated to the PC5-RRC connection;

1 >

initialize SBj for each logical channel associated to the PC5-RRC connection to zero.

5.12a Void

5.13 Handling of unknown, unforeseen and erroneous protocol data p. 112

When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI, CS-RNTI, G-RNTI, G-CS-RNTI or by the configured downlink assignment, containing a Reserved LCID or eLCID value, or an LCID or eLCID value the MAC Entity does not support, the MAC entity shall at least:

1 >

discard the received subPDU and any remaining subPDUs in the MAC PDU.

When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI or CS-RNTI, or by the configured downlink assignment, containing an LCID or eLCID value which is not configured, or an LCID or eLCID value associated with a suspended RB as specified in TS 38.331, the MAC entity shall at least:

1 >

discard the received subPDU.

When a MAC entity receives a MAC PDU on SL-SCH containing a Reserved LCID value for broadcast or groupcast, or an LCID value which is not configured, the MAC entity shall:

1 >

discard the received subPDU.

When a MAC entity receives a MAC PDU on SL-SCH containing a Reserved LCID value for unicast, the MAC entity shall:

1 >

discard the received subPDU and any remaining subPDUs in the MAC PDU.

5.14 Handling of measurement gaps p. 112

During an activated measurement gap, the MAC entity shall, on the Serving Cell(s) in the corresponding frequency range of the measurement gap configured by measGapConfig as specified in TS 38.331:

1 >

not perform the transmission of HARQ feedback, SR, and CSI;

1 >

not report SRS;

1 >

not transmit on UL-SCH except for Msg3 or the MSGA payload as specified in clause 5.4.2.2;

1 >

if the ra-ResponseWindow or the ra-ContentionResolutionTimer or the msgB-ResponseWindow is running, or if there is an ongoing RACH-less LTM cell switch, or if there is an ongoing RACH-less handover in a terrestrial network:

2 >

monitor the PDCCH as specified in clauses 5.1.4 and 5.1.5.

1 >

else:

2 >

not monitor the PDCCH;

2 >

not receive on DL-SCH.

5.15 Bandwidth Part (BWP) operation p. 112

5.15.1 Downlink and Uplink |R16| p. 112

In addition to clause 12 of TS 38.213, this clause specifies requirements on BWP operation.

A Serving Cell may be configured with one or multiple BWPs, and the maximum number of BWP per Serving Cell is specified in TS 38.213.

The BWP switching for a Serving Cell is used to activate an inactive BWP and deactivate an active BWP at a time. The BWP switching is controlled by the PDCCH indicating a downlink assignment or an uplink grant, by the bwp-InactivityTimer, by RRC signalling, or by the MAC entity itself upon initiation of Random Access procedure or upon detection of consistent LBT failure on SpCell. Upon RRC (re-)configuration of firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id for SpCell except for PSCell when SCG is deactivated (see clause 5.29) or activation of an SCell, the DL BWP and/or UL BWP indicated by firstActiveDownlinkBWP-Id and/or firstActiveUplinkBWP-Id respectively (as specified in TS 38.331) is active without receiving PDCCH indicating a downlink assignment or an uplink grant. Upon RRC (re-)configuration of firstActiveDownlinkBWP-Id for PSCell when SCG is deactivated, the DL BWP is switched to the firstActiveDownlinkBWP-Id as specified in TS 38.331. The active BWP for a Serving Cell is indicated by either RRC or PDCCH (as specified in TS 38.213). For unpaired spectrum, a DL BWP is paired with a UL BWP, and BWP switching is common for both UL and DL.

For each SCell a dormant BWP may be configured with dormantBWP-Id by RRC signalling as described in TS 38.331. Entering or leaving dormant BWP for SCells is done by BWP switching per SCell or per dormancy SCell group based on instruction from PDCCH (as specified in TS 38.213). The dormancy SCell group configurations are configured by RRC signalling as described in TS 38.331. Upon reception of the PDCCH indicating leaving dormant BWP, the DL BWP indicated by firstOutsideActiveTimeBWP-Id or by firstWithinActiveTimeBWP-Id (as specified in TS 38.331 and TS 38.213) is activated. Upon reception of the PDCCH indicating entering dormant BWP, the DL BWP indicated by dormantBWP-Id (as specified in TS 38.331) is activated. The dormant BWP configuration for SpCell or PUCCH SCell is not supported.

BWP for SRS for positioning Tx frequency hopping can be configured for a Serving Cell in TS 38.331. BWP for SRS Tx frequency hopping is considered as activated when it is configured. BWP switching is not applicable for BWP for SRS Tx frequency hopping.

For each activated Serving Cell configured with a BWP, the MAC entity shall:

1 >

if a BWP is activated and the active DL BWP for the Serving Cell is not the dormant BWP and the Serving Cell is not the PSCell of deactivated SCG:

2 >

transmit on UL-SCH on the BWP;

2 >

transmit on RACH on the BWP, if PRACH occasions are configured;

2 >

monitor the PDCCH on the BWP;

2 >

transmit PUCCH on the BWP, if configured;

2 >

report CSI for the BWP;

2 >

transmit SRS on the BWP, if configured;

2 >

receive DL-SCH on the BWP;

2 >

(re-)initialize any suspended configured uplink grants of configured grant Type 1 on the active BWP according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2;

2 >

if lbt-FailureRecoveryConfig is configured:

3 >

stop the lbt-FailureDetectionTimer, if running;

3 >

set LBT_COUNTER to 0;

3 >

monitor LBT failure indications from lower layers as specified in clause 5.21.2.

1 >

if a BWP is activated and the active DL BWP for the Serving Cell is dormant BWP:

2 >

stop the bwp-InactivityTimer of this Serving Cell, if running.

2 >

not monitor the PDCCH on the BWP;

2 >

not monitor the PDCCH for the BWP;

2 >

not receive DL-SCH on the BWP;

2 >

not report CSI on the BWP, report CSI except aperiodic CSI for the BWP;

2 >

not transmit SRS on the BWP;

2 >

not transmit on UL-SCH on the BWP;

2 >

not transmit on RACH on the BWP;

2 >

not transmit PUCCH on the BWP;

2 >

clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

2 >

suspend any configured uplink grant Type 1 associated with the SCell;

2 >

if configured, perform beam failure detection and beam failure recovery for the SCell if beam failure is detected.

1 >

if a BWP is deactivated or the Serving Cell is PSCell of deactivated SCG:

2 >

not transmit on UL-SCH on the BWP;

2 >

not transmit on RACH on the BWP;

2 >

not monitor the PDCCH on the BWP;

2 >

not transmit PUCCH on the BWP;

2 >

not report CSI for the BWP;

2 >

not transmit SRS on the BWP;

2 >

not receive DL-SCH on the BWP;

2 >

clear any configured downlink assignment and configured uplink grant of configured grant Type 2 on the BWP;

2 >

suspend any configured uplink grant of configured grant Type 1 on the inactive BWP.

Upon initiation of the Random Access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure as specified in clause 5.1.1, the MAC entity shall for the selected carrier of this Serving Cell:

1 >

if PRACH occasions are not configured for the active UL BWP:

2 >

if the UE is an (e)RedCap UE; and

2 >

if initialUplinkBWP-RedCap is configured:

3 >

switch the active UL BWP to BWP indicated by initialUplinkBWP-RedCap.

2 >

else:

3 >

switch the active UL BWP to BWP indicated by initialUplinkBWP.

2 >

if the Serving Cell is an SpCell:

3 >

if the UE is an (e)RedCap UE; and

3 >

if initialDownlinkBWP-RedCap is configured:

4 >

switch the active DL BWP to BWP indicated by initialDownlinkBWP-RedCap.

3 >

else:

4 >

switch the active DL BWP to BWP indicated by initialDownlinkBWP.

1 >

else:

2 >

if the Serving Cell is an SpCell:

3 >

if the active DL BWP does not have the same bwp-Id as the active UL BWP:

4 >

switch the active DL BWP to the DL BWP with the same bwp-Id as the active UL BWP.

1 >

stop the bwp-InactivityTimer associated with the active DL BWP of this Serving Cell, if running.

1 >

if the Serving Cell is SCell:

2 >

stop the bwp-InactivityTimer associated with the active DL BWP of SpCell, if running.

1 >

perform the Random Access procedure on the active DL BWP of SpCell and active UL BWP of this Serving Cell.

If the MAC entity receives a PDCCH for BWP switching of a Serving Cell, the MAC entity shall:

1 >

if there is no ongoing Random Access procedure associated with this Serving Cell; or

1 >

if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (as specified in clauses 5.1.4, 5.1.4a, and 5.1.5):

2 >

cancel, if any, triggered consistent LBT failure for this Serving Cell;

2 >

perform BWP switching to a BWP indicated by the PDCCH.

If the MAC entity receives a PDCCH for BWP switching for a Serving Cell(s) or a dormancy SCell group(s) while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, it is up to UE implementation whether to switch BWP or ignore the PDCCH for BWP switching, except for the PDCCH reception for BWP switching addressed to the C-RNTI for successful Random Access procedure completion (as specified in clauses 5.1.4, 5.1.4a, and 5.1.5) in which case the UE shall perform BWP switching to a BWP indicated by the PDCCH. Upon reception of the PDCCH for BWP switching other than successful contention resolution, if the MAC entity decides to perform BWP switching, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the BWP switching; if the MAC decides to ignore the PDCCH for BWP switching, the MAC entity shall continue with the ongoing Random Access procedure on the Serving Cell.

Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell while a Random Access procedure associated with that Serving Cell is ongoing in the MAC entity, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure after performing the BWP switching.

Upon reception of RRC (re-)configuration for BWP switching for a Serving Cell, cancel any triggered consistent LBT failure in this Serving Cell.

The MAC entity shall for each activated Serving Cell configured with bwp-InactivityTimer:

1 >

if the defaultDownlinkBWP-Id is configured, and the active DL BWP is not the BWP indicated by the defaultDownlinkBWP-Id, and the active DL BWP is not the BWP indicated by the dormantBWP-Id if configured; or

1 >

if the UE is neither a RedCap nor an eRedCap UE, and if the defaultDownlinkBWP-Id is not configured, and the active DL BWP is not the initialDownlinkBWP, and the active DL BWP is not the BWP indicated by the dormantBWP-Id if configured; or

1 >

if the UE is an (e)RedCap UE, and if the defaultDownlinkBWP-Id is not configured, and initialDownlinkBWP-RedCap is not configured, and the active DL BWP is not the initialDownlinkBWP; or

1 >

if the UE is an (e)RedCap UE, and if the defaultDownlinkBWP-Id is not configured, and initialDownlinkBWP-RedCap is configured, and the active DL BWP is not the initialDownlinkBWP-RedCap:

2 >

if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received on the active BWP; or

2 >

if a PDCCH addressed to G-RNTI or G-CS-RNTI configured for multicast indicating downlink assignment is received on the active BWP; or

2 >

if a PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment or uplink grant is received for the active BWP; or

2 >

if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

2 >

if a MAC PDU is received in a configured downlink assignment for unicast or MBS multicast:

3 >

if there is no ongoing Random Access procedure associated with this Serving Cell; or

3 >

if the ongoing Random Access procedure associated with this Serving Cell is successfully completed upon reception of this PDCCH addressed to C-RNTI (as specified in clauses 5.1.4, 5.1.4a and 5.1.5):

step 4. start or restart the bwp-InactivityTimer associated with the active DL BWP.

2 >

if the bwp-InactivityTimer associated with the active DL BWP expires:

3 >

if the defaultDownlinkBWP-Id is configured:

4 >

perform BWP switching to a BWP indicated by the defaultDownlinkBWP-Id.

3 >

else:

4 >

if the UE is a (e)RedCap UE; and

4 >

if initialDownlinkBWP-RedCap is configured:

5 >

perform BWP switching to the initialDownlinkBWP-RedCap.

4 >

else:

5 >

perform BWP switching to the initialDownlinkBWP.

1 >

if a PDCCH for BWP switching is received, and the MAC entity switches the active DL BWP:

2 >

if the defaultDownlinkBWP-Id is configured, and the MAC entity switches to the DL BWP which is not indicated by the defaultDownlinkBWP-Id and is not indicated by the dormantBWP-Id if configured; or

2 >

if the UE is neither a RedCap nor an eRedCap UE, and if the defaultDownlinkBWP-Id is not configured, and the MAC entity switches to the DL BWP which is not the initialDownlinkBWP and is not indicated by the dormantBWP-Id if configured; or

2 >

if the UE is an (e)RedCap UE, and if the defaultDownlinkBWP-Id is not configured, and initialDownlinkBWP-RedCap is not configured, and the MAC entity switches to the DL BWP which is not the initialDownlinkBWP; or

2 >

if the UE is an (e)RedCap UE, and if the defaultDownlinkBWP-Id is not configured, and initialDownlinkBWP-RedCap is configured, and the MAC entity switches to the DL BWP which is not the initialDownlinkBWP-RedCap:

3 >

start or restart the bwp-InactivityTimer associated with the active DL BWP.

Upon initiation of the Random Access procedure, after selection of the carrier for performing Random Access procedure as specified in clause 5.1.1, if the UE is an (e)RedCap UE in RRC_IDLE or RRC_INACTIVE mode, the MAC entity shall:

1 >

if initialUplinkBWP-RedCap is configured for the selected carrier:

2 >

perform the Random Access procedure as specified in clause 5.1 by using the BWP configured by initialUplinkBWP-RedCap.

1 >

else:

2 >

perform the Random Access procedure as specified in clause 5.1 by using the BWP configured by initialUplinkBWP.

1 >

if initialDownlinkBWP-RedCap is configured:

2 >

if the Random Access procedure was initiated for SI request (as specified in TS 38.331) and the Random Access Resources for SI request have been explicitly provided by RRC, and if the selected carrier is SUL carrier:

3 >

monitor the PDCCH on the BWP configured by initialDownlinkBWP.

2 >

else:

3 >

monitor the PDCCH on the BWP configured by initialDownlinkBWP-RedCap.

1 >

else:

2 >

monitor the PDCCH on the BWP configured by initialDownlinkBWP.

5.15.2 Sidelink |R16| p. 117

In addition to clause 16 of TS 38.213, this clause specifies requirements on BWP operation for sidelink.

The MAC entity is configured with at most a single SL BWP per sidelink carrier where sidelink transmission and reception are performed.

For a BWP, the MAC entity shall:

1 >

if the BWP is activated:

2 >

transmit SL-BCH on the BWP, if configured;

2 >

transmit S-PSS and S-SSS on the BWP, if configured;

2 >

transmit PSCCH on the BWP;

2 >

transmit SL-PRS on the BWP;

2 >

transmit SL-SCH on the BWP;

2 >

receive PSFCH on the BWP, if configured;

2 >

receive S-PSS and S-SSS on the BWP, if configured;

2 >

receive SL-BCH on the BWP, if configured;

2 >

receive PSCCH on the BWP;

2 >

receive SL-PRS on the BWP;

2 >

receive SL-SCH on the BWP;

2 >

transmit PSFCH on the BWP, if configured;

2 >

(re-)initialize any suspended configured sidelink grant of configured grant Type 1.

2 >

if sl-lbt-FailureRecoveryConfig is configured:

3 >

set SL_LBT_COUNTER to 0 for all RB sets in the SL BWP;

3 >

monitors SL LBT failure indications from lower layers as specified in clause 5.31.2.

1 >

if the BWP is deactivated:

2 >

not transmit SL-BCH on the BWP, if configured;

2 >

not transmit S-PSS and S-SSS on the BWP, if configured;

2 >

not transmit PSCCH on the BWP;

2 >

not transmit SL-PRS on the BWP;

2 >

not transmit SL-SCH on the BWP;

2 >

not receive PSFCH on the BWP, if configured;

2 >

not receive SL-BCH on the BWP, if configured;

2 >

not receive S-PSS and S-SSS on the BWP, if configured;

2 >

not receive PSCCH on the BWP;

2 >

not receive SL-PRS on the BWP;

2 >

not receive SL-SCH on the BWP;

2 >

not transmit PSFCH on the BWP, if configured;

2 >

suspend any configured sidelink grant of configured grant Type 1;

2 >

clear any configured sidelink grant of configured grant Type 2;

2 >

cancel, if any, triggered Scheduling Request procedure for sidelink;

2 >

cancel, if any, triggered Sidelink Buffer Status Reporting procedure;

2 >

cancel, if any, triggered Sidelink CSI Reporting procedure;

2 >

cancel, if any, triggered Sidelink DRX Command MAC CE;

2 >

cancel, if any, triggered Sidelink IUC-Request transmission procedure;

2 >

cancel, if any, triggered Sidelink IUC-Information Reporting procedure;

2 >

if sl-lbt-FailureDetectionTimer is configured:

3 >

stop the sl-lbt-FailureDetectionTimer for all RB sets in the SL BWP, if running.

5.16 SUL operation p. 118

The Supplementary UL (SUL) carrier can be configured as a complement to the normal UL (NUL) carrier. Switching between the NUL carrier and the SUL carrier means that the UL transmissions move from one carrier to the other carrier, which is done by:

an indication in DCI;
the Random Access procedure as specified in clause 5.1.1;
the SDT procedure as specified in clause 5.27.

If the MAC entity receives a UL grant indicating an SUL switch while a Random Access procedure is ongoing, the MAC entity shall ignore the UL grant.

The Serving Cell configured with supplementaryUplink belongs to a single TAG.

5.17 Beam Failure Detection and Recovery procedure p. 118

The MAC entity may be configured by RRC per Serving Cell or per BFD-RS set with a beam failure recovery procedure which is used for indicating to the serving gNB of a new SSB or CSI-RS when beam failure is detected on the serving SSB(s)/CSI-RS(s). Beam failure is detected by counting beam failure instance indication from the lower layers to the MAC entity. If beamFailureRecoveryConfig is reconfigured by upper layers during an ongoing Random Access procedure for beam failure recovery for SpCell, the MAC entity shall stop the ongoing Random Access procedure and initiate a Random Access procedure using the new configuration. The Serving Cell is configured with two BFD-RS sets if and only if failureDetectionSet1 and failureDetectionSet2 are configured for the active DL BWP of the Serving Cell. When the SCG is deactivated, the UE performs beam failure detection on the PSCell if bfd-and-RLM is set to true.

RRC configures the following parameters in the beamFailureRecoveryConfig, beamFailureRecoverySpCellConfig, beamFailureRecoverySCellConfig and the radioLinkMonitoringConfig for the Beam Failure Detection and Recovery procedure:

beamFailureInstanceMaxCount for the beam failure detection (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets);
beamFailureDetectionTimer for the beam failure detection (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets);
beamFailureRecoveryTimer for the beam failure recovery procedure for SpCell;
rsrp-ThresholdSSB: an RSRP threshold for the SpCell beam failure recovery;
rsrp-ThresholdBFR: an RSRP threshold for the SCell beam failure recovery or for the beam failure recovery of BFD-RS set of Serving Cell;
powerRampingStep: powerRampingStep for the SpCell beam failure recovery;
powerRampingStepHighPriority: powerRampingStepHighPriority for the SpCell beam failure recovery;
preambleReceivedTargetPower: preambleReceivedTargetPower for the SpCell beam failure recovery;
preambleTransMax: preambleTransMax for the SpCell beam failure recovery;
scalingFactorBI: scalingFactorBI for the SpCell beam failure recovery;
ssb-perRACH-Occasion: ssb-perRACH-Occasion for the SpCell beam failure recovery using contention-free Random Access Resources;
ra-ResponseWindow: the time window to monitor response(s) for the SpCell beam failure recovery using contention-free Random Access Resources;
prach-ConfigurationIndex: prach-ConfigurationIndex for the SpCell beam failure recovery using contention-free Random Access Resources;
ra-ssb-OccasionMaskIndex: ra-ssb-OccasionMaskIndex for the SpCell beam failure recovery using contention-free Random Access Resources;
ra-OccasionList: ra-OccasionList for the SpCell beam failure recovery using contention-free Random Access Resources;
candidateBeamRSList: list of candidate beams for SpCell beam failure recovery;
candidateBeamRS-List-r16: list of candidate beams for SCell beam failure recovery or list of candidate beams for beam failure recovery of a Serving Cell for BFD-RS set one;
candidateBeamRS-List2-r17: list of candidate beams for beam failure recovery of a Serving Cell for BFD-RS set two.

The following UE variables are used for the beam failure detection procedure:

BFI_COUNTER (per Serving Cell or per BFD-RS set of Serving Cell configured with two BFD-RS sets): counter for beam failure instance indication which is initially set to 0.

The MAC entity shall for each Serving Cell configured for beam failure detection:

1 >

if the Serving Cell is configured with two BFD-RS sets:

2 >

if beam failure instance indication for a BFD-RS set has been received from lower layers:

3 >

start or restart the beamFailureDetectionTimer of the BFD-RS set;

3 >

increment BFI_COUNTER of the BFD-RS set by 1;

3 >

if BFI_COUNTER of the BFD-RS set >= beamFailureInstanceMaxCount:

4 >

trigger a BFR for this BFD-RS set of the Serving Cell;

2 >

if BFR is triggered for both BFD-RS sets of the SpCell and the Beam Failure Recovery procedure is not successfully completed for any of the BFD-RS sets:

3 >

initiate a Random Access procedure (see clause 5.1) on the SpCell;

2 >

if the Serving Cell is SpCell and the Random Access procedure initiated for beam failure recovery of both BFD-RS sets of SpCell is successfully completed (see clause 5.1):

3 >

set BFI_COUNTER of each BFD-RS set of SpCell to 0.

3 >

consider the Beam Failure Recovery procedure successfully completed.

2 >

if the beamFailureDetectionTimer of this BFD-RS set expires; or

2 >

if beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any of the reference signals used for beam failure detection is reconfigured by upper layers or by the BFD-RS Indication MAC CE associated with a BFD-RS set of the Serving Cell; or

2 >

if the reference signal(s) associated with a BFD-RS set of the Serving Cell used for beam failure detection is changed:

3 >

set BFI_COUNTER of the BFD-RS set to 0.

2 >

if a PDCCH addressed to C-RNTI indicating uplink grant for a new transmission is received for the HARQ process used for the transmission of the Enhanced BFR MAC CE or Truncated Enhanced BFR MAC CE which contains beam failure recovery information of this BFD-RS set of the Serving Cell:

3 >

set BFI_COUNTER of the BFD-RS set to 0;

3 >

consider the Beam Failure Recovery procedure successfully completed for this BFD-RS set and cancel all the triggered BFRs of this BFD-RS set of the Serving Cell.

2 >

if the Serving Cell is SCell and the SCell is deactivated as specified in clause 5.9:

3 >

set BFI_COUNTER of each BFD-RS set of SCell to 0;

3 >

consider the Beam Failure Recovery procedure successfully completed and cancel all the triggered BFRs of all BFD-RS sets of the Serving Cell.

1 >

else:

2 >

if beam failure instance indication has been received from lower layers:

3 >

start or restart the beamFailureDetectionTimer;

3 >

increment BFI_COUNTER by 1;

3 >

if BFI_COUNTER >= beamFailureInstanceMaxCount:

4 >

if the Serving Cell is SCell:

5 >

trigger a BFR for this Serving Cell;

4 >

else if the Serving Cell is PSCell and, the SCG is deactivated:

5 >

if beam failure of the PSCell has not been indicated to upper layers since the SCG was deactivated or since the deactivated SCG was last reconfigured with BFD-RS:

6 >

indicate beam failure of the PSCell to upper layers.

4 >

else:

5 >

initiate a Random Access procedure (see clause 5.1) on the SpCell;

5 >

if beam failure is detected for an NCR-MT:

6 >

indicate to NCR-Fwd to cease forwarding.

2 >

if the beamFailureDetectionTimer expires; or

2 >

if beamFailureDetectionTimer, beamFailureInstanceMaxCount, or any of the reference signals used for beam failure detection is reconfigured by upper layers associated with this Serving Cell; or

2 >

if the reference signal(s) associated with this Serving Cell used for beam failure detection is changed:

3 >

set BFI_COUNTER to 0.

2 >

if the Serving Cell is SpCell and the Random Access procedure initiated for SpCell beam failure recovery is successfully completed (see clause 5.1):

3 >

set BFI_COUNTER to 0;

3 >

stop the beamFailureRecoveryTimer, if configured;

3 >

if the Random Access procedure was triggered by beam failure recovery for NCR-MT:

4 >

indicate to NCR-Fwd to resume forwarding using the last forwarding configuration received by NCR-MT as part of side control information before beam failure detection;

3 >

consider the Beam Failure Recovery procedure successfully completed.

2 >

else if the Serving Cell is SCell, and a PDCCH addressed to C-RNTI indicating uplink grant for a new transmission is received for the HARQ process used for the transmission of the MAC CE for BFR which contains beam failure recovery information of this Serving Cell; or

2 >

if the SCell is deactivated as specified in clause 5.9:

3 >

set BFI_COUNTER to 0;

3 >

consider the Beam Failure Recovery procedure successfully completed and cancel all the triggered BFRs for this Serving Cell.

The MAC entity shall:

1 >

if the Beam Failure Recovery procedure determines that at least one BFR has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed and if none of the Serving Cell(s) of this MAC entity are configured with two BFD-RS sets:

2 >

if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the BFR MAC CE plus its subheader as a result of LCP:

3 >

instruct the Multiplexing and Assembly procedure to generate the BFR MAC CE.

2 >

else if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Truncated BFR MAC CE plus its subheader as a result of LCP:

3 >

instruct the Multiplexing and Assembly procedure to generate the Truncated BFR MAC CE.

2 >

else:

3 >

trigger the SR for SCell beam failure recovery for each SCell for which BFR has been triggered, not cancelled, and for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed.

1 >

if the Beam Failure Recovery procedure determines that at least one BFR for any BFD-RS set has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed; or

1 >

if the Beam Failure Recovery procedure determines that at least one BFR for only one BFD-RS set has been triggered and not cancelled for an SpCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed; or

1 >

if the Beam Failure Recovery procedure determines that at least one BFR has been triggered and not cancelled for an SCell for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed and if at least one Serving Cell of this MAC entity is configured with two BFD-RS sets:

2 >

if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Enhanced BFR MAC CE plus its subheader as a result of LCP:

3 >

instruct the Multiplexing and Assembly procedure to generate the Enhanced BFR MAC CE.

2 >

else if UL-SCH resources are available for a new transmission and if the UL-SCH resources can accommodate the Truncated Enhanced BFR MAC CE plus its subheader as a result of LCP:

3 >

instruct the Multiplexing and Assembly procedure to generate the Truncated Enhanced BFR MAC CE.

2 >

else:

3 >

trigger the SR for beam failure recovery of each BFD-RS set for which BFR has been triggered, not cancelled, and for which evaluation of the candidate beams according to the requirements as specified in TS 38.133 has been completed;

3 >

All BFRs triggered for an SCell shall be cancelled when a MAC PDU is transmitted and this PDU includes a MAC CE for BFR which contains beam failure information of that SCell. All BFRs triggered for a BFD-RS set of a Serving Cell shall be cancelled when a MAC PDU is transmitted and this PDU includes an Enhanced BFR MAC CE or Truncated Enhanced BFR MAC CE which contains beam failure recovery information of that BFD-RS set of the Serving Cell.