Patent Description:
Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for joint release for multiple semi-persistent scheduling configurations.

The publication "<NPL> relates to SPS enhancements including support of multiple simultaneous active SPS configurations, shorter and finer SPS periodicities, and conflicts among different multiple SPS configurations.

The publication "<NPL>, relates to configuration and activation/release of multiple active configured grant (CG) configurations correspondent to different service types. A joint activation/release is achieved through a single DCI indicating multiple indices correspondent to each configuration via bitmap or joint coding.

The publication "<NPL>, relates to CG confirmation mechanisms for multiple Type <NUM> CGs. A CG confirmation MAC CE is extended with the information to identify the CG configurations and allow a joint feedback.

Aspects generally include a method, apparatus, and computer-readable medium as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

A cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile BS.

Two or more UEs <NUM> (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using a base station <NUM> as an intermediary to communicate with one another).

Controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform one or more techniques associated with joint activation and/or release for multiple configured grant and/or semi-persistent scheduling configurations, as described in more detail elsewhere herein. For example, controller/processor <NUM> of base station <NUM>, controller/processor <NUM> of UE <NUM>, and/or any other component(s) of <FIG> may perform or direct operations of, for example, process <NUM> of <FIG> and/or other processes as described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. In some aspects, memory <NUM> and/or memory <NUM> may comprise a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station <NUM> and/or the UE <NUM>, may perform or direction operations of, for example, process <NUM> of <FIG> and/or other processes as described herein.

UE <NUM> includes means for receiving a single downlink control information (DCI) message, means for mapping a bit sequence in the single DCI message to a configuration set that includes multiple downlink semi-persistent scheduling configurations or multiple uplink configured grant configurations to be jointly activated or released, and/or the like. In some aspects, such means may include one or more components of UE <NUM> described in connection with <FIG>, such as controller/processor <NUM>, transmit processor <NUM>, TX MIMO processor <NUM>, MOD <NUM>, antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, and/or the like.

Semi-persistent scheduling (SPS) enables radio resources to be semi-statically configured and allocated to a UE for a longer time period than one subframe, which may avoid the need for specific downlink assignment messages and/or uplink grant messages over a physical downlink control channel (PDCCH) for each subframe. To configure SPS, radio resource control (RRC) signaling may indicate an interval at which the radio resources are periodically assigned. PDCCH signaling may indicate specific transmission resource allocations in the time/frequency domain and transmission attributes (e.g., periodicity, modulation and control scheme (MCS), time offset, transmit power, and/or the like). For SPS in LTE UL, non-adaptive synchronous hybrid automatic repeat request (HARQ) is performed. For example, non-adaptive retransmissions may be performed on a same resource and with a same MCS as was used for a last (e.g., previous) transmission. For SPS in LTE DL, adaptive asynchronous HARQ is performed. For example, adaptive retransmissions may be performed on a resource and, if provided, with the MCS indicated on the PDCCH.

Furthermore, in order to support certain service types (e.g., ultra reliable low latency communication (URLLC), enhanced mobile broadband (eMBB), massive machine-type communications (MMTC), and/or the like) that may have different requirements with respect to reliability, latency, data rates, communication range, and/or the like, NR UL defines two types of UL data transmissions that may be performed without a grant, generally referred to as a configured grant (CG). More particularly, in a Type <NUM> CG configuration, a UE can perform UL data transmission without a grant based at least in part on RRC (re)configuration without any L1 signaling, and in a Type <NUM> CG configuration, the UE can perform UL data transmission without a grant based at least in part on RRC (re)configuration in combination with L1 signaling to activate and/or release the Type <NUM> CG configuration.

In some instances, a UE can be provided with multiple downlink SPS configurations for a given bandwidth part (BWP) of a serving cell and/or multiple Type <NUM> uplink configurations. For example, in some cases, a given UE may be associated with up to sixteen (<NUM>) different downlink SPS configurations and up to twelve (<NUM>) different Type <NUM> uplink CG configurations. However, one challenge that arises when a UE is associated with multiple downlink SPS configurations and/or multiple Type <NUM> uplink configurations relates to activating and/or releasing the configurations. For example, as mentioned above, a Type <NUM> uplink CG configuration is initially indicated to the UE in an RRC configuration, and subsequent L1 signaling via downlink control information (DCI) is used to activate and/or release the Type <NUM> CG configuration. Accordingly, before the UE can perform uplink transmissions according to a Type <NUM> CG configuration, the UE has to receive a DCI message activating the Type <NUM> CG configuration. Furthermore, a similar approach is typically used for a downlink SPS configuration, which is initially indicated in an RRC configuration and a subsequent DCI message activates and/or releases the downlink SPS configuration.

In current approaches, different downlink SPS configurations and different Type <NUM> uplink CG configurations are activated and released individually. In other words, a base station needs to send N DCI messages to a UE in order to activate N downlink SPS configurations, and the same applies when separately releasing the downlink SPS configurations, separately activating and/or releasing different Type <NUM> uplink CG configurations, and/or the like. Accordingly, the current approach of having separate activations and separate releases for different SPS configurations, different Type <NUM> uplink CG configurations, and/or the like increases network overhead and consumes substantial resources at the base station and the UE because the base station has to prepare and transmit multiple DCIs, the network has to transport the multiple DCIs, the UE has to receive and process the multiple DCIs, and/or the like.

Some aspects described herein provide techniques and apparatuses for using a single DCI message to jointly activate and/or release multiple downlink SPS configurations, multiple Type <NUM> uplink CG configurations, and/or the like. For example, in some aspects, different SPS and/or CG configurations associated with a UE may be divided or otherwise grouped into different sets, and a bit sequence in a single DCI message can be used to indicate multiple SPS and/or CG configurations that are to be jointly activated and/or released. For example, the bit sequence may include a codepoint that indicates an index associated with a particular SPS and/or CG configuration to be activated or released, and all SPS and/or CG configurations that are members of the set that includes the particular SPS and/or CG configuration may be jointly activated and/or released. Additionally, or alternatively, the bit sequence may include a bitmap in which each individual bit corresponds to a particular set, which can be used to indicate multiple sets that are to be jointly activated and/or released. In another example, different configurations may be associated with different sets, and an individual configuration may be activated and/or released based at least in part on whether the bitmap indicates that all sets including the individual configuration are to be activated or released. In addition, as described in further detail elsewhere herein, some aspects may provide for techniques and apparatuses to jointly acknowledge multiple SPS and/or CG configurations that have been activated or released.

In this way, by jointly activating and/or releasing multiple downlink SPS configurations, multiple uplink CG configurations, and/or the like using a single DCI message, aspects described herein may conserve network resources, base station resources, UE resources, and/or the like relative to current approaches that use multiple DCIs to separately activate and/or release the multiple downlink SPS configurations, the multiple uplink CG configurations, and/or the like. Furthermore, some aspects described herein may constrain a length of the bit sequence in the single DCI message to be less than or equal to a length of a DCI field used for separate activation and/or release, which avoids incurring additional overhead by ensuring that the joint activation and/or joint release technique(s) do not impact a size of the DCI message. In a similar respect, an existing DCI field (e.g., a HARQ process number) may be used to indicate which configuration(s) are to be activated and/or released, thus avoiding a need to introduce a new DCI field to indicate which configuration(s) are to be activated and/or released, which would otherwise require that the new DCI field be padded in a Cell Radio Network Temporary Identifier (C-RNTI) to avoid increasing the DCI size.

Embodiments described in the following correspond to the claimed invention only for the aspects of joint release of multiple downlink SPS configurations and subsequent joint acknowledgement.

<FIG> is a diagram illustrating an example <NUM> of joint activation and/or scheduling for multiple uplink CG configurations and/or multiple downlink SPS configurations, in accordance with various aspects of the present disclosure. As shown, example <NUM> includes a UE <NUM> (hereinafter referred to as a UE) and a base station <NUM> (hereinafter referred to as a BS). In general, the UE may be associated with multiple Type <NUM> uplink CG configurations that are indicated in an RRC configuration and subsequently activated and/or released, and the Type <NUM> uplink CG configurations are hereinafter referred to as "CG configurations" for simplicity. Additionally, or alternatively, the UE may be associated with multiple downlink SPS configurations, which are hereinafter referred to as "SPS configurations" for simplicity.

As shown in <FIG>, and by reference number <NUM>, the BS may transmit, and the UE may receive, a single DCI message that includes a bit sequence to indicate CG and/or SPS configurations to be jointly activated and/or released. In particular, as mentioned above, the CG and/or SPS configurations may be indicated to the UE in an RRC configuration, and a subsequent DCI message may be communicated to the UE in order to activate and/or release the CG and/or SPS configurations. For example, after the UE receives a DCI message to activate a particular CG configuration, the UE may perform uplink transmissions according to the activated CG configuration, and the UE may subsequently cease to perform uplink transmissions according to the CG configuration after receiving another DCI message to release the CG configuration. In a similar respect, after the UE receives a DCI message to activate a particular SPS configuration, the UE may receive scheduled downlink transmissions according to the activated SPS configuration, and the UE may cease to receive downlink transmissions according to the SPS configuration after receiving another DCI message to release the SPS configuration. Accordingly, in <FIG>, the single DCI message received by the UE may be communicated to jointly activate one or more CG configurations, to jointly release one or more CG configurations, to jointly activate one or more SPS configurations, to jointly release one or more SPS configurations, and/or the like.

As further shown in <FIG>, and by reference number <NUM>, the UE may map the bit sequence in the single DCI message to one or more CG and/or SPS configurations to be activated and/or released. In some aspects, various different techniques can be used to determine the mapping between the bit sequence and the CG/SPS configurations to be activated and/or released.

In a first technique, as shown by reference number <NUM>, the bit sequence may be a codepoint that indicates a particular configuration index (e.g., an index associated with a particular CG configuration or a particular SPS configuration), and the particular configuration index may be used as a proxy to jointly activate or release all members of a configuration set that includes the particular configuration index as a member. For example, as mentioned above, the UE may be permitted to have up to <NUM> uplink CG configurations and up to <NUM> downlink SPS configurations. Accordingly, in some aspects, a bit sequence with <NUM> bits may be sufficient to define a configuration index for each uplink CG configuration and/or downlink SPS configuration associated with the UE (e.g., four bits may yield up to <NUM> codepoints that can correspond to up to <NUM> different configuration indices, and more generally, N bits may yield up to <NUM>N codepoints that can correspond to up to <NUM>N different configuration indices).

Furthermore, as mentioned above, multiple uplink CG configurations and/or multiple downlink SPS configurations that are associated with the UE may be divided into different sets in the first technique. For example, because different service types (e.g., URLLC, eMBB, MMTC, and/or the like) may generally share various parameters (e.g., with respect to latency, data rate, and/or the like), configurations that belong to the same service type may grouped within the same configuration set. In some aspects, a mapping between the configurations and the configuration sets may be indicated to the UE in an RRC configuration. Accordingly, in the first technique, the UE may identify a codepoint from the bit sequence in the single DCI message, and the codepoint may generally correspond to a configuration index associated with a particular CG configuration or a particular SPS configuration that is to be activated or released. The UE may then jointly activate or release each CG or SPS configuration that is a member of the same set as the particular CG or SPS configuration corresponding to the codepoint indicated in the bit sequence of the single DCI message.

For example, in <FIG>, the codepoint indicates that a configuration with index '<NUM>' is to be activated or released. The UE may therefore identify the CG or SPS configuration with the index '<NUM>' and jointly activate or release all members of the configuration set that includes the CG or SPS configuration with the index '<NUM>' as a member. For example, in a case where the UE has <NUM> downlink SPS configurations, the UE may be configured with <NUM> configuration sets that have <NUM> members each, <NUM> configuration sets that include a first set with <NUM> members and a second set with <NUM> members (e.g., the first set may be for a URLLC service type and the second set may be for an eMBB service type), and/or the like. In the former case, all <NUM> members of the set that includes the configuration with the index '<NUM>' may be jointly activated or released based at least in part on the single DCI message. In the latter case, if the configuration with the index '<NUM>' is a member of the first set, all <NUM> members of the first set may be jointly activated or released based on the single DCI message; otherwise, all <NUM> members of the first set may be jointly activated or released based on the configuration with the index '<NUM>' being a member of the second set. In other words, all members of a configuration set may be jointly activated or released when the codepoint indicates that an individual configuration index within that configuration set is to be activated or released, whereby individual configuration indices are used as proxies to represent all members of the corresponding configuration sets.

In some aspects, the first technique described above can generally be used to indicate, within a single DCI message, a codepoint associated with an individual CG and/or SPS configuration in order to jointly activate and/or release all CG and/or SPS configurations that are grouped with the individual CG and/or SPS configuration within an individual configuration set based on having a common service type. Thus, in the first technique, one configuration set (which may have one or multiple members) can be activated and/or released within a single DCI message. Accordingly, in some aspects, efficiency may be increased by using a single DCI message to jointly activate and/or release multiple configuration sets, each of which may include one or multiple members. For example, as mentioned above, configurations that have a particular service type may be grouped together within the configuration sets. Additionally, or alternatively, configurations with a common service type may be distributed among different configuration sets, with members of the respective configuration sets sharing one or more parameters (e.g., a configuration set may include a first CG configuration for URLLC and a second CG configuration for eMBB based on the first and second CG configurations having a common periodicity, modulation coding scheme (MCS), time offset, and/or the like).

Accordingly, in a second technique, as shown by reference number <NUM>, the bit sequence may be a bitmap to individually indicate one or more configuration sets to be activated and/or released, and all members of the indicated configuration sets may be jointly activated and/or released. In some aspects, in the second technique, a length of the bit sequence may generally correspond to a quantity of different configuration sets, whereby each bit in the bit sequence may correspond to an individual configuration set. For example, if the bit sequence has a length of <NUM> bits as illustrated in <FIG>, the UE may be configured with up to <NUM> configuration sets that may have an equal or unequal number of members (e.g., the UE may have <NUM> configuration sets that each have up to <NUM> members, <NUM> configuration sets that have <NUM> members and <NUM> set that has <NUM> member, and/or the like). Accordingly, in the second technique, the bit sequence in the single DCI message may indicate one or more configuration sets that are to be jointly activated or released, and all CG and/or SPS configurations that are members of a configuration set that is indicated to be activated or released may be activated or released together.

For example, in <FIG>, the bitmap includes <NUM> bits to represent four individual configuration sets, each of which may have one or more members. In <FIG>, the bitmap includes the bit sequence '<NUM>' to indicate that the second and fourth configuration sets are to be activated or released (e.g., based on the second and fourth bits being set to '<NUM>'). The UE may therefore identify all of the CG and/or SPS configurations that are members of the second configuration set and all of the CG and/or SPS configurations that are members of the fourth configuration set, and the identified configurations may be jointly activated or released based on the bitmap in the single DCI message.

According to various aspects, in the first technique and/or the second technique described above, a single Configured Scheduling Radio Network Temporary Identifier (CS-RNTI) may be associated with multiple uplink CG configurations, multiple downlink SPS configurations, and/or the like. In particular, the CS-RNTI generally corresponds to a unique identification for the UE that is used to manage resources associated with uplink CG configurations, downlink SPS configurations, and/or the like. For example, with respect to Type <NUM> uplink CG configurations, RRC may define a periodicity of the uplink CG configuration while a PDCCH addressed to a CS-RNTI can be used as a signal to either activate or release the uplink CG configuration (e.g., a PDCCH addressed to the CS-RNTI may indicate that the uplink CG configuration can be implicitly reused according to the periodicity defined by RRC until released). In addition, with a downlink SPS configuration, RRC may define a periodicity of the configured downlink assignments while a PDCCH addressed to the CS-RNTI can activate and/or release the configured downlink assignment (e.g., a PDCCH addressed to the CS-RNTI may indicate that the downlink assignment can be implicitly reused according to the periodicity defined by RRC until released).

Accordingly, in the first technique and/or the second technique described above, different configuration sets can be associated with different CS-RNTIs, and the CS and/or SPS configurations that are jointly activated or released may be constrained to those configurations that are associated with the same CS-RNTI. For example, in some aspects, the UE may be associated with multiple CS-RNTIs, and each CS-RNTI may correspond to a particular configuration set that contains one or more multiple configurations that can be jointly activated or released. In this way, with multiple different CS-RNTIs, the bit sequence in the DCI that is used to jointly activate or release uplink CG configurations, downlink SPS configurations, and/or the like may be reduced, thus achieving greater reliability.

As described above, in the first technique and the second technique, all the members of a configuration set are jointly activated or jointly released based on the codepoint and/or bitmap indicated in the single DCI message. In a third technique, as shown by reference number <NUM>, the bit sequence is a bitmap to indicate one or more configuration sets to be activated or released (e.g., in a similar manner as in the second technique). However, in the third technique, one or more CG and/or SPS configurations may be associated with multiple configuration sets, and an individual configuration may be activated or released only if all of the configuration sets that include the individual configuration as a member are activated or released. For example, a mapping between configurations and one or more associated configuration sets may be RRC configured (e.g., based on service type, periodicity, MCS, time offset, and/or the like), and each configuration set may be associated with an index. Accordingly, the bitmap in the single DCI message may indicate one or more configuration set indices that are to be activated or released, and a particular configuration may be activated or released if all the configuration set indices associated with the configuration set are activated or released. In this way, by associating individual configurations with one or more configuration sets, a single DCI message can be used to jointly activate or release multiple configurations individually rather than having to activate or release every member of a configuration set together.

For example, in <FIG>, the bitmap in the single DCI message includes a bit sequence '<NUM>' that may correspond to {set4, set3, set2, set1}. Accordingly, in an example where a first configuration is associated with set1 and set2, a second configuration is associated with set1, and a third configuration is associated with set3 and set4, the bitmap '<NUM>' activates or releases the first configuration and the second configuration but not the third configuration. In particular, the bitmap '<NUM>' activates or releases set1, set2, and set3, whereby the first configuration and the second configuration are activated or released because all the configuration sets associated with the first configuration are activated or released and all the configuration sets associated with the second configuration are activated or released. However, because the first bit in the bitmap (corresponding to set4) has a value of '<NUM>', set4 is not activated or released by the single DCI message. Accordingly, because the third configuration is associated with set4, the third configuration is not activated or released by the single DCI message.

In some aspects, the bit sequence in the single DCI message may be based on a PDCCH validation procedure used to validate scheduling activation and/or release where multiple Type <NUM> uplink CG configurations, multiple downlink SPS configurations, and/or the like are supported per bandwidth part. For example, a new field may be defined to indicate within the single DCI message the configuration(s) and/or configuration set(s) to be activated or released, and the new field may be padded in a Cell RNTI (C-RNTI) to adhere to the above-mentioned constraint to maintain the DCI size. Additionally, or alternatively, one or more existing DCI fields may be reinterpreted or repurposed to indicate the configuration(s) and/or configuration set(s) to be activated or released. For example, an existing DCI field that may be reinterpreted or repurposed may be a HARQ process number, which is a <NUM>-bit field. In this way, by reinterpreting or repurposing an existing field, a need to pad a new field in the C-RNTI may be avoided. Furthermore, in cases where HARQ indices are divided among different CG and/or SPS configurations, the HARQ index that belongs to a CG and/or SPS configuration can be used to activate or release the corresponding configuration (e.g., the codepoint in the first technique described above may indicate the HARQ index that corresponds to a particular CG and/or SPS configuration). For example, the above-mentioned field for the HARQ process number has <NUM> bits because there can be up to <NUM> HARQ indices, and these HARQ indices can be divided among different CG and/or SPS configurations. For example, if the UE has four CG configurations, the <NUM> HARQ indices can be divided among the four CG configurations (e.g., <NUM> HARQ indices per CG configuration). Accordingly, in any of the first through third techniques, the bit sequence in the single DCI message may indicate one of the HARQ indices associated with a particular CG configuration, a particular SPS configuration, and/or the like to be activated or released. In other words, the HARQ indices can be used as proxies for the CG and/or SPS configurations to be activated or released.

As further shown in <FIG>, and by reference number <NUM>, the UE may transmit, to the BS, a message to jointly acknowledge all CG and/or SPS configurations that were activated and/or released by the single DCI message. For example, in the case of an SPS configuration that is activated or released, the UE may acknowledge the activation or release by transmitting the acknowledgement in a codebook through a physical uplink control channel (PUCCH) resource, and in the case of a CG configuration that is activated or released, the UE may acknowledge the activation or release by transmitting the acknowledgement through a medium access control (MAC) control element (MAC-CE).

In some aspects, based on the single DCI message activating or releasing one or more SPS configurations, the UE may use different techniques to determine the PUCCH resource to be used to transmit the acknowledgement and/or a location of an acknowledgement bit in the codebook (e.g., an individual bit used to acknowledge all of the SPS configurations that were activated or released). In general, when SPS configurations are individually activated or released, a location of the acknowledgement bit in the codebook is associated with the physical downlink shared channel (PDSCH) corresponding to the individually activated or released SPS configuration (e.g., based on a time domain resource allocation (TDRA) table). Accordingly, as described herein, different techniques may be applied to determine the PUCCH resource to be used to transmit the acknowledgement and/or the location of the acknowledgement bit in the codebook for cases where multiple SPS configurations are jointly activated or released.

More particularly, in some aspects, the UE may receive multiple PDSCHs, including an SPS PDSCH, a dynamic PDSCH, and/or the like. If the multiple PDSCHs have the same PUCCH for acknowledgement (ACK) and negative acknowledgement (NACK), the UE may multiplex the ACK-NACKs for the multiple PDSCHs and determine a location in the codebook for the ACK-NACK corresponding to each PDSCH. For example, in some aspects, the PUCCH resource to be used to transmit the acknowledgement bit may be defined by the single DCI message indicating the SPS configuration(s) to be activated or released (e.g., when there is only SPS traffic and there is no multiplexing of a HARQ-ACK with a dynamic PDSCH). In this example, the codebook size is only one bit because there is only SPS traffic, so the UE does not need to further determine the location in the codebook for the acknowledgement bit.

In another example, for dynamic (e.g., Type <NUM>) codebook construction where a HARQ-ACK for SPS PDSCH release and a HARQ-ACK for a dynamic PDSCH release are multiplexed, the PUCCH resource may be indicated by a PUCCH resource indicator (PRI) of a last (e.g., preceding or most recent) DCI message and the location of the acknowledgement bit in the codebook may be given by the single DCI message that was used to activate or release the one or more SPS configurations.

In another example, for semi-static (e.g., Type <NUM>) codebook construction where a HARQ-ACK for both an SPS release and a dynamic PDSCH release are multiplexed (e.g., there is SPS and non-SPS traffic), a location in the semi-static HARQ-ACK codebook for HARQ-ACK information that corresponds to an SPS PDSCH release is generally the same as for a corresponding SPS PDSCH reception. Accordingly, when a semi-static codebook is used to acknowledge the SPS configuration(s) activated or released by the single DCI message, the location of the acknowledgement bit in the codebook may correspond to a PDSCH reception occasion of the SPS configuration given in the codepoint for the codepoint-based activation and/or release techniques described above. Alternatively, for the bitmap-based activation and/or release techniques described above, the location of the acknowledgement bit in the codebook may correspond to a PDSCH reception occasion of a first (e.g., initial) SPS configuration given in a first set of activated or released configurations. With respect to the other PDSCH occasions that correspond to the activated or released SPS configurations, the UE may provide a NACK in the codebook. Alternatively, the UE may provide only the individual acknowledgement bit in the codebook and no bits for the other PDSCH occasions that correspond to the activated or released SPS configurations, which may save codebook size.

In some aspects, whereas the techniques described above relate to techniques that the UE employs to acknowledge a single DCI message activating or releasing one or more SPS configurations, the UE may use different techniques to transmit the acknowledgement through a MAC-CE when the single DCI message is used to activate or release one or more CG configurations. For example, in some aspects, the UE may transmit one or more MAC-CEs to acknowledge the one or more CG configurations that were activated or released, and each MAC-CE may indicate the index corresponding to the CG configuration being acknowledged. Furthermore, each MAC-CE may also indicate whether the acknowledgement is to confirm that the CG configuration was activated or released. Additionally, or alternatively, a bitmap may be used in the confirmation MAC-CE to jointly acknowledge multiple CG configurations that were activated or released, which reduces overhead of the MAC-CE because fewer (e.g., only one) MAC-CEs can be transmitted to acknowledge all of the CG configurations that were activated or released in the single DCI. For example, in some aspects, a size of the bitmap may correspond to a maximum quantity of uplink CG configurations that are supported per bandwidth part of a serving cell (e.g., if the UE can have up to <NUM> uplink CG configurations, the confirmation MAC-CE may have up to <NUM> bits, which may be arranged as two octets with <NUM> reserved bits). Additionally, or alternatively, a bit length of the MAC-CE can be reduced based on a technique used to jointly activate or release multiple CG configurations. For example, if a single DCI includes a codepoint or a bitmap to release multiple CG configurations grouped together in a configuration set, the confirmation MAC-CE can be sent with an indicator that identifies only a single index among the indices associated with the multiple CG configurations.

<FIG> is a diagram illustrating an example process <NUM> performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process <NUM> is an example where a UE (e.g., UE <NUM> and/or the like) performs operations associated with joint activation and/or release for multiple CG configurations, multiple SPS configurations, and/or the like using a single DCI message.

As shown in <FIG>, in some aspects, process <NUM> may include receiving a single DCI message (block <NUM>). For example, the UE (e.g., using antenna <NUM>, DEMOD <NUM>, MIMO detector <NUM>, receive processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may receive a DCI message, as described above.

As further shown in <FIG>, in some aspects, process <NUM> may include mapping a bit sequence in the single DCI message to a configuration set that includes multiple downlink SPS configurations or multiple uplink CG configurations to be jointly activated or released (block <NUM>). For example, the UE (e.g., using receive processor <NUM>, transmit processor <NUM>, controller/processor <NUM>, memory <NUM>, and/or the like) may map a bit sequence in the single DCI message to a configuration set that includes multiple downlink SPS configurations or multiple uplink CG configurations to be jointly activated or released, as described above.

In a first aspect, when mapping the bit sequence in the single DCI message to the configuration set, the UE may identify a codepoint that indicates an index associated with an individual configuration to be activated or released based at least in part on the bit sequence, and the UE may jointly activate or release each configuration in the configuration set based at least in part on determining that the individual configuration to be activated or released is a member of the configuration set.

In a second aspect, alone or in combination with the first aspect, the index is a hybrid automatic repeat request (HARQ) index associated with the individual configuration to be activated or released.

In a third aspect, alone or in combination with one or more of the first and second aspects, each configuration in the configuration set is associated with a particular service type.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, when mapping the bit sequence in the single DCI message to the configuration set, the UE may identify an individual bit that corresponds to the configuration set based at least in part on the bit sequence, and the UE may jointly activate or release each configuration in the configuration set based at least in part on the individual bit that corresponds to the configuration set indicating that the configuration set is to be activated or released.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the configuration set is a first configuration set, the individual bit is a first individual bit, the UE may identify a second individual bit that corresponds to a second configuration set based at least in part on the bit sequence in the single DCI message, and the UE may jointly activate or release each configuration in the second configuration set based at least in part on the second individual bit indicating that the second configuration set is to be activated or released.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, each configuration in the configuration set is associated with one or more of a particular service type or a particular parameter.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a length of the bit sequence corresponds to a quantity of different configuration sets associated with the UE.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, at least one configuration in the configuration set is a member of one or more additional configuration sets, and the at least one configuration is activated or released based at least in part on the bit sequence in the single DCI message indicating that the configuration set and the one or more additional configuration sets are all to be activated or released.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the UE is associated with multiple Configured Scheduling Radio Network Temporary Identifiers (CS-RNTIs) that respectively correspond to multiple configuration sets with one or more downlink SPS configurations or uplink CG configurations that can be jointly activated or released.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the bit sequence is provided in a HARQ process number field of the DCI message.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the multiple downlink SPS configurations or multiple uplink CG configurations are grouped within the configuration set based at least in part on an indicator in a radio resource control configuration message.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, a length of the bit sequence is less than or equal to a length of a field in the DCI message used to separately activate or release an individual downlink SPS configuration or an individual uplink CG configuration.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the UE may transmit, through a physical uplink control channel (PUCCH) resource, a codebook that includes an individual acknowledgement bit based at least in part on the bit sequence indicating that the multiple downlink SPS configurations are to be jointly released.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the PUCCH resource used to transmit the codebook is determined based at least in part on the single DCI message.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the PUCCH resource used to transmit the codebook is indicated by a PUCCH resource indicator in a most recent DCI message, and a location of the individual acknowledgement bit in the codebook is determined based at least in part on the single DCI message.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, a location of the individual acknowledgement bit in the codebook corresponds to a physical downlink shared channel (PDSCH) reception occasion associated with an individual downlink SPS configuration that corresponds to a codepoint indicated in the bit sequence.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, a location of the individual acknowledgement bit in the codebook corresponds to a PDSCH reception occasion associated with an initial downlink SPS configuration in a first set of downlink SPS configurations that the bit sequence indicates is to be jointly released.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the codebook further includes a negative acknowledgement for one or more PDSCH reception occasions that correspond to one or more of the multiple downlink SPS configurations to be jointly released.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the UE may transmit, through a medium access control (MAC) control element, an acknowledgement of the single DCI message based at least in part on the bit sequence indicating that the multiple uplink CG configurations are to be jointly activated or released, and the MAC control element may further indicate an index corresponding to an acknowledged uplink CG configuration and indicate whether the acknowledgement is for a joint activation or a joint release.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the acknowledgement includes a bitmap with a set of bits to jointly acknowledge all of the multiple uplink CG configurations that are to be jointly activated or released.

Claim 1:
A method of wireless communication performed by a user equipment, UE, comprising:
receiving a single downlink control information, DCI, message (<NUM>);
mapping a bit sequence in the single DCI message to a configuration set that includes multiple downlink semi-persistent scheduling, SPS, configurations to be jointly released (<NUM>); and
transmitting, through a physical uplink control channel, PUCCH, resource, a codebook that includes an acknowledgement bit based at least in part on the bit sequence indicating that one or more of the multiple downlink SPS configurations are to be jointly released, wherein the acknowledgement bit is an individual acknowledgement bit used to acknowledge all of the downlink SPS configurations that were released.