Joint indication for multi-cell scheduling

By determining bit field sizes based on carrier parameters and applying default or reuse strategies, the UE efficiently handles multi-cell scheduling across carriers with varying parameter sets, addressing complexity in parameter determination.

CN119096652APending Publication Date: 2024-12-06QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380032349.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-12
Filing Date
2023-04-04
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In wireless communication systems, user equipment (UE) faces increased complexity in determining appropriate parameters for carriers with varying parameter set sizes due to inconsistent bit field sizes across carriers, leading to difficulties in interpreting joint indications for multi-cell scheduling.

Method used

The UE determines the bit field size based on the maximum or minimum number of parameters supported by a given carrier, decodes the bit field, and applies default parameters or parameter reuse strategies for carriers with blank entries, enabling efficient communication across carriers with different parameter sets.

Benefits of technology

This approach simplifies parameter determination for UE, allowing seamless communication across carriers with varying parameter sets, reducing complexity and ensuring effective multi-cell scheduling.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096652A_ABST
    Figure CN119096652A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive, from a network entity, a message indicating one or more parameter sets for a set of carriers supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the set of carriers. The UE may monitor a domain of a control message based on the message. A domain size of the domain may be based on the parameter set, and a respective value of the domain may indicate a respective one of the parameter sets for one or more carriers of the carrier set. Based on receiving the control message and decoding the associated domain, the UE may communicate via at least one carrier of the set of carriers using the respective set of parameters for the at least one carrier.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 17 / 719,305, entitled “JOINT INDICATION FOR MULTI-CELL SCHEDULING,” filed by Takeda et al. on April 12, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including joint indication for multi-cell scheduling. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communication of communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support joint indication for multi-cell scheduling. For example, the described techniques enable a user equipment (UE) to determine which parameters will be used in wireless communication for a carrier set with a varying parameter set size. In some cases, the UE may decode a bit field of a control message that indicates a set of bits associated with one or more parameters for one or more carriers in the carrier set and a blank entry (e.g., the decoded bit field is not configured with a parameter) for one or more other carriers in the carrier set. In some examples, the UE may assume that the carrier with the blank entry may not be used for wireless communication (e.g., within a given duration). In some examples, the UE may configure default parameters for each carrier, which may be used when a given carrier does not have a parameter for the indicated bit field value. In some examples, the UE may reuse parameters for a given carrier for other bit field values ​​in a given order (e.g., recursively, cyclically, etc.). In some examples, the UE may reuse parameters for the first bit field value for a given carrier for other bit field values ​​that share the same bit value.

[0006] In some cases, the network entity may instruct the UE to perform bandwidth part (BWP) switching for multiple carriers, where the active BWP for each carrier may be switched to a second BWP. In an example where the second BWP supports a different number of parameters, the UE may determine the adjusted bit field size based on the techniques described herein.

[0007] A method for wireless communication is described. The method may include: receiving a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; monitoring a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0008] An apparatus for wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; monitor a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicate one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0009] Another apparatus for wireless communication is described. The apparatus may include: means for receiving a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; means for monitoring a domain of a control message based on the message, wherein a domain size of the domain is based on the one or more parameter sets, and wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and means for communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; monitor a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicate one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, monitoring the field of the control message may include operations, features, components, or instructions for performing the following operations: decoding one or more bits of the field of the control message based on the field size, where the field size may be based on the number of parameters associated with a parameter set of the one or more parameter sets.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining the domain size based on a carrier of the carrier set, the carrier being associated with the parameter set, wherein the number of parameters may be greater than the number of corresponding parameters for each remaining carrier of the carrier set.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: determining the domain size based on a carrier of the carrier set, the carrier being associated with the parameter set, wherein the number of parameters may be less than the number of corresponding parameters for each remaining carrier of the carrier set.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each value of the field for a first subset of carriers of the set of carriers indicates at least one corresponding parameter for each carrier of the first subset of carriers, the first subset of carriers including the one or more carriers, and each value of the field for a second subset of carriers is associated with a blank value for each carrier of the second subset of the set of carriers, the second subset of carriers not including the first subset of carriers.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: based on the value of the field of the carrier in the second subset of carriers corresponding to the blank value, refraining from using the carrier to communicate the one or more messages.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: based on the value of the field of each carrier of the second subset of carriers corresponding to the blank value, communicating using corresponding default parameters for each carrier of the second subset of carriers.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each respective default parameter corresponds to a zero code point domain parameter for the respective carrier.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: filling blank values ​​for the second carrier subset for a given value of the domain by reusing parameters for the second carrier subset associated with other values ​​of the domain.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, filling blank values ​​for a given carrier of the second subset of carriers includes recursively filling the blank values ​​for the given carrier by reusing parameters for the given carrier associated with other values ​​of the field.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, filling blank values ​​for a given carrier of the second subset of carriers may include operations, features, components, or instructions for performing the following operations: based on the first value of the field for the given carrier sharing one or more common bits with the second value of the field for the given carrier, filling a first blank value associated with the first value of the field using a parameter associated with the second value of the field.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: monitoring a subset of values ​​of the domain in a set of available values ​​for the domain, wherein each value of the subset of values ​​includes a corresponding parameter for each carrier of the set of carriers; and communicating the one or more messages based on the domain of the control message being a value in the subset of values.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving a radio resource control message indicating a number of bits associated with the domain for decoding, wherein the domain size may be based on the number of bits.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: receiving a second control message indicating a change from the one or more parameter sets to a second one or more parameter sets available to the carrier set for the UE.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of bits associated with the field of the second one or more parameter sets may be less than the number of bits associated with the field of the one or more parameter sets.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: zeroing the value of the field that may be associated with the one or more parameter sets and not associated with the second one or more parameter sets.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of bits associated with the field of the second one or more parameter sets may be greater than the number of bits associated with the field of the one or more parameter sets.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for interpreting entries of the field of the second one or more parameter sets using the number of least significant bits associated with the one or more parameter sets.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each parameter of the one or more parameter sets includes a BWP or a time domain resource allocation (TDRA).

[0029] A method for wireless communication is described. The method may include: sending a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; sending a control message via a carrier of the carrier set based on the message, wherein a field size associated with a field of the control message is based on the one or more parameter sets, wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0030] An apparatus for wireless communication is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; send a control message via a carrier of the carrier set based on the message, wherein a domain size associated with a domain of the control message is based on the one or more parameter sets, wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicate one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0031] Another apparatus for wireless communication is described. The apparatus may include: means for sending a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; means for sending a control message via a carrier of the carrier set based on the message, wherein a field size associated with a field of the control message is based on the one or more parameter sets, wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and means for communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0032] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: send a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; send a control message via a carrier of the carrier set based on the message, wherein a field size associated with a field of the control message is based on the one or more parameter sets, wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicate one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a radio resource control message indicating a number of bits associated with the domain, wherein the domain size may be based on the number of bits.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for performing the following operations: sending a second control message indicating a change from the one or more parameter sets for the carrier set available to the UE to a second one or more parameter sets for the carrier set available to the UE.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of bits associated with the field of the second one or more parameter sets may be less than the number of bits associated with the field of the one or more parameter sets.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the number of bits associated with the field of the second one or more parameter sets may be greater than the number of bits associated with the field of the one or more parameter sets.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each parameter of the one or more parameter sets includes a BWP or a TDRA. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 An example of a wireless communication system supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0039] Figure 2 An example of a wireless communication system supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 3A – Figure 3C An example of parameter configuration supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 4 An example of a bandwidth part (BWP) configuration timing diagram to support joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 5 An example of a BWP configuration timing diagram supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 6 An example of a process flow supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 7 and Figure 8 A block diagram of an apparatus supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown.

[0045] Fig. 9 A block diagram of a communication manager supporting joint indication for multi-cell scheduling is shown in accordance with one or more aspects of the present disclosure.

[0046] Fig.10 A diagram of a system including a device supporting joint indication for multi-cell scheduling is shown in accordance with one or more aspects of the present disclosure.

[0047] Fig.11 and Fig.12 A block diagram of an apparatus supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown.

[0048] Fig.13 A block diagram of a communication manager supporting joint indication for multi-cell scheduling is shown in accordance with one or more aspects of the present disclosure.

[0049] Fig.14 A diagram of a system including a device supporting joint indication for multi-cell scheduling is shown in accordance with one or more aspects of the present disclosure.

[0050] Figures 15 to 18 A flow chart illustrating a method of supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0051] In some examples or wireless communications, a user equipment (UE) and a network entity may communicate via multiple carriers across respective sets of frequency resources. In this manner, the network entity may send an indication of a set of parameters for each of the multiple carriers to use for wireless communications. Based on the respective set of parameters configured for each carrier for the UE, the network entity may send an indication of which parameters of each carrier may be used by the UE for a given communication. For example, the network entity may send a control message with a joint carrier indication, wherein a single bit field within the control message may indicate respective parameters for all carriers (e.g., using a lookup table, the UE interprets the same bit field differently for each carrier to obtain communication parameters for each carrier).

[0052] However, in scenarios where carriers are configured with different numbers of parameters (or different numbers of parameter sets), the UE may experience increased complexity in determining the appropriate parameters to be used for each carrier. For example, a first carrier may support four different parameters (e.g., indicated by the following bit fields: 00, 01, 10, 11), while a second carrier may support two different parameters (e.g., indicated by the following bit fields: 0, 1). When the network uses a joint indication, a two-bit field may be used for the first carrier and a one-bit field may be used for the second carrier. As such, the UE may not be able to interpret the bit fields or determine the size of the bit fields for all carriers supported by the UE (e.g., when a two-bit field is used, the UE may not be able to determine the appropriate parameter set for the second carrier because the UE expects a one-bit field).

[0053] The UE may determine which parameters to use for a carrier set with a varying parameter set size based on the techniques described herein. For example, the UE may determine the size of the bit field based on the maximum number of parameters or the minimum number of parameters supported by a given carrier. Based on determining the size of the bit field, the UE may decode the bit field. In some cases, the decoded bit field may indicate a set of bits associated with a blank entry for one or more carriers (e.g., the decoded bit field is not configured with a parameter). In some examples, the UE may assume that a carrier with a blank entry cannot be used. In some examples, the UE may configure default parameters for each carrier, which may be used when a given carrier does not have a parameter for the indicated bit field value. In some examples, the UE may reuse parameters for a given carrier for other bit field values ​​in a given order (e.g., recursively, cyclically, etc.). In some examples, the UE may reuse parameters for a first bit field value for a given carrier for other bit field values ​​that share the same bit value.

[0054] In some cases, the network entity may instruct the UE to perform bandwidth part (BWP) switching for multiple carriers, where the active BWP for each carrier may be switched to a second BWP. In an example where the second BWP supports a different number of parameters, the UE may determine the adjusted bit field size based on the techniques described herein.

[0055] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated by and described with reference to parameter configurations, BWP configuration timing diagrams, and process flows. Aspects of the present disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flow diagrams relating to joint indication for multi-cell scheduling.

[0056] Figure 1 An example of a wireless communication system 100 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, a new radio (NR) network, or a network operating according to other systems and radio technologies (including future systems and radio technologies not explicitly mentioned herein).

[0057] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area), and the UE 115 and the network entity 105 may establish one or more communication links 125 over the coverage area. The coverage area 110 may be an example of a geographic area over which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0058] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1 . The UEs 115 described herein may be able to communicate with various types of devices such as Figure 1 105 or other UEs 115 or network entities 105 shown in FIG.

[0059] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0060] In some examples, the network entities 105 may communicate with the core network 130, or communicate with each other, or both. For example, the network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, the network entities 105 may communicate with each other on the backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols) directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130). In some examples, the network entities 105 may communicate with each other via the midhaul communication link 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication link 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, the midhaul communication link 162, or the fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), and other examples or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0061] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home Evolved Node B, or other suitable terms). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140).

[0062] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0063] The functional split between CU 160, DU 165, and RU 175 is flexible and may support different functionalities, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, and RU 175. For example, a functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within the protocol layer (e.g., some functions of the protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating over those communication links.

[0064] In a wireless communication system (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140). One or more donor network entities 105 (e.g., an IAB donor) may communicate with one or more additional network entities 105 (e.g., an IAB node 104) via supported access and backhaul links (e.g., a backhaul communication link 120). The IAB node 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such a case, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0065] In the case where the techniques described herein are applied to the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support joint indication for multi-cell scheduling as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0066] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where a "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects such as electrical appliances or vehicles, meters, etc.

[0067] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, such as Figure 1 shown.

[0068] The UE 115 and the network entity 105 may wirelessly communicate with each other via one or more communication links 125 (e.g., access links) on one or more carriers. The term "carrier" may refer to a set of RF spectrum resources having a defined physical layer structure to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a BWP) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between a device and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate," when referring to the network entity 105, may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN that communicates with another device (e.g., directly or via one or more other network entities 105).

[0069] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be located based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0070] The communication link 125 shown in the wireless communication system 100 may include downlink transmissions (e.g., forward link transmissions) from the network entity 105 to the UE 115, uplink transmissions (e.g., return link transmissions) from the UE 115 to the network entity 105, or both, as well as other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in TDD mode).

[0071] A carrier may be associated with a particular bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths of carriers of a particular radio access technology (e.g., 1.4 megahertz (MHz), 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). A device of the wireless communication system 100 (e.g., a network entity 105, a UE 115, or both) may have a hardware configuration that supports communication over a particular carrier bandwidth, or may be configurable to support communication over one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a UE 115 that supports concurrent communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0072] The signal waveform sent on the carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that adopts MCM technology, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and the subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), so that the more resource elements a device receives and the higher the order of the modulation scheme, the higher the data rate of the device can be. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers, beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE115.

[0073] One or more parameter sets for a carrier may be supported, where the parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be constrained to one or more active BWPs.

[0074] The time interval of the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames, each radio frame having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0075] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a certain number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, the time slot may also be divided into multiple mini-time slots including one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0076] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0077] Physical channels may be multiplexed on a carrier according to various techniques. For example, physical control channels and physical data channels may be multiplexed on a downlink carrier using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth or a subset of a system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to a plurality of UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0078] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0079] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have service subscriptions with a network provider, or may provide restricted access to UEs 115 associated with a small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications on one or more cells.

[0080] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0081] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.

[0082] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC). UE 115 can be designed to support ultra-reliable, low-latency or critical functions. Ultra-reliable communication can include private communication or group communication, and can be supported by one or more services (such as push-to-talk, video or data). Support for ultra-reliable, low-latency functions can include prioritization of services, and such services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency and ultra-reliable low-latency can be used interchangeably in this article.

[0083] In some examples, a UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group that are performing D2D communication may be within a coverage area 110 of a network entity 105 (e.g., a base station 140, a RU 170), which may support aspects of such D2D communication configured or scheduled by the network entity 105. In some examples, one or more UEs 115 in the group may be outside of the coverage area 110 of the network entity 105, or otherwise not able or configured to receive transmissions from the network entity 105. In some examples, a group of UEs 115 communicating via D2D communication may support a one-to-many (1:M) system, in which each UE 115 transmits to each UE 115 in the group. In some examples, the network entity 105 may facilitate scheduling resources for D2D communication. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105 .

[0084] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0085] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength range is about one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but these waves may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0086] The wireless communication system 100 can utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can adopt license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed RF spectrum band, devices such as network entities 105 and UEs 115 can use carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration combined with component carriers operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0087] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas, which can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna component, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may have an antenna array having antenna ports of a plurality of rows and columns of a collection that the network entity 105 can use to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0088] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0089] In some examples or wireless communication systems 100, the UE 115 and the network entity 105 may communicate via multiple carriers spanning a corresponding set of frequency ranges. In this way, the network entity 105 may send an indication of a parameter set for each of the multiple carriers to use for wireless communication. Based on the corresponding parameter set configured for each carrier for the UE 115, the network entity 105 may send an indication of which parameters for each carrier the UE 115 may use for a given communication. For example, the network entity 105 may send a control message with a joint carrier indication, where a single bit field within the control message may indicate the corresponding parameters for all carriers. However, in the case where the carriers are configured with different numbers of parameters, the UE 115 may experience an increase in complexity in determining the appropriate parameters to be used for each carrier.

[0090] In this way, the UE 115 can determine which parameters will be used for a carrier set with a varying parameter set size according to the techniques described herein. For example, the UE 115 can determine the bit field size based on the maximum number of parameters or the minimum number of parameters supported by a given carrier. Based on determining the size of the bit field, the UE 115 can decode the bit field. In some cases, the decoded bit field can indicate a set of bits associated with a blank entry for one or more carriers (e.g., the decoded bit field is not configured with parameters). In some examples, the UE 115 can assume that a carrier with a blank entry cannot be used. In some examples, the UE 115 can configure default parameters for each carrier, which can be used when a given carrier does not have a parameter for the indicated bit field value. In some examples, the UE 115 can recursively reuse parameters for a given carrier for other bit field values ​​in a given order. In some examples, the UE 115 can reuse parameters for the first bit field value for a given carrier for other bit field values ​​that share the same bit value. In some cases, the network entity 105 may instruct the UE 115 to perform BWP switching for multiple carriers, where the active BWP for each carrier may be switched to a second BWP. In examples where the second BWP supports a different number of parameters, the UE 115 may determine the adjusted bit field size based on the techniques described herein.

[0091] Figure 2 An example of a wireless communication system 200 that supports joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may implement one or more aspects of the wireless communication system 100. For example, the UE 115-a and the network entity 105-a may be as described herein. Figure 1 Corresponding examples of UE 115-a 115 and network entity 105-a are described.

[0092] In some examples, the UE 115-a and the network entity 105-a may communicate via multiple carriers 210 across corresponding sets of frequency resources. In this way, the network entity 105-a may send a parameter configuration message 205 to the UE 115-a, which may indicate a set of parameters 215 for each of the multiple carriers 210 to use for wireless communication. When communicating via a given carrier 210, the UE 115-a may use the parameters 215 for uplink communication, downlink communication, or both. For example, the parameters 215 of the parameter configuration message 205 may include a BWP indicator, a frequency domain resource allocation (FDRA), a time domain resource allocation (TDRA), a modulation coding scheme (MCS), a redundancy version, a hybrid automatic repeat request (HARQ) process number, a rate matching number, or any combination thereof.

[0093] Based on configuring the UE 115-a with the respective parameter sets 215 for each carrier 210, the network entity 105-a may send a control message 220 (e.g., a downlink control information (DCI) message) that may indicate which of the parameters 215 for each carrier 210 the UE 115-a may use for a given communication. In some examples, the network entity 105-a may send the control message 220 with a per-carrier 210 indication, wherein multiple fields of the control message 220 or multiple control messages 220 are used to separately indicate the parameters 215 for each of the multiple carriers 210. In some examples, the network entity 105-a may send the control message 220 with a joint carrier 210 indication, wherein a single bit field within the control message 220 may indicate the respective parameters 215 for all carriers 210 (e.g., using a lookup table, the UE 115-a interprets the same bit field differently for each carrier 210 to obtain the communication parameters 215 for each carrier 210).

[0094] In some examples, per-carrier 210 indication may increase flexibility in parameter 215 configuration, but may also increase overhead for the wireless communication system 200. Thus, the network entity 105-a may operate in accordance with the joint carrier 210 indication technique to reduce network overhead. However, in situations where the carriers 210 are configured with different numbers of parameters 215 (e.g., different numbers of entries in parameter 215, lists, or information elements (IEs)), the UE 115-a may experience increased complexity in determining the appropriate parameters 215 to use for each carrier 210. For example, if Figure 2As illustrated, carrier 210-a may be configured with four parameters 215 (e.g., parameter 215-a, parameter 215-b, parameter 215-c, and parameter 215-d), carrier 210-b may be configured with two parameters 215 (e.g., parameter 215-e and parameter 215-f), carrier 210-c may be configured with one parameter 215 (e.g., parameter 215-g), and carrier 210-a may be configured with four parameters 215 (e.g., parameter 215-h, parameter 215-i, parameter 215-j, and parameter 215-k). Thus, carrier 210-a may support four different parameters 215, which may be indicated by bit fields 00, 01, 10, and 11, while carrier 210-b may support two different parameters 215, which may be indicated by bit fields 0 and 1. Parameters 215 based on different carriers 210 are associated with different bit field sizes (e.g., as Figure 2 2-bit field or 1-bit field as illustrated), UE 115-a may not be able to interpret a single bit field to determine parameters 215 for each carrier 210.

[0095] UE 115-a may determine which parameters 215 to use for a given carrier 210 with varying parameter 215 set sizes in accordance with the techniques described herein. For example, UE 115-a may perform control message field size determination 225 based on the number of parameters 215 configured for each carrier 210. In some examples, UE 115-a may determine the control message field size based on the maximum number of parameters 215 supported by a given carrier 210 (e.g., N max ) determines the field size within control message 220. For example, UE 115-a may determine the field size (F) according to Formula 1:

[0096] F = log2(N max ) (1)

[0097] In some examples, the domain size is rounded up to the nearest integer. For example, if the maximum number of parameters 215 configured for a carrier 210 of a set of carriers 210 is seven parameters 215, then the associated domain size would be three bits. In some examples, UE 115-a may select a domain size based on the minimum number of parameters 215 supported by a given carrier 210 (e.g., N min ) determines the field size within control message 220. For example, UE 115-a may determine the field size (F) according to Formula 2:

[0098] F = log2(N min ) (2)

[0099] In some cases, the domain size is rounded up to the nearest integer.For example, if the minimum number of parameters 215 configured for a carrier 210 of a set of carriers 210 is one parameter 215, then the associated domain size will be one bit.

[0100] Based on performing control message field size determination 225, UE 115-a may perform field decoding 230 procedure to decode the field of control message 220. However, in some cases, the decoded bit field may indicate a set of bits associated with a blank entry (e.g., blank, empty, N / A, no entry, unconfigured, or an entry with no associated value) for one or more carriers 210. For example, referring to Figure 2 , if the bit field indicates a value of 01, this may indicate that the UE 115-a is to use parameters 215-b for carrier 210-a, parameters 215-f for carrier 210-b, parameters 215-i for carrier 210-d, and that no parameters 215 are available for carrier 210-c. In some examples, the UE 115-a 115 may parse blank entries for a given carrier 210 according to the techniques of the carrier parameter configuration 235. In some examples, the UE 115-a may assume that a carrier 210 with a blank entry cannot be used. In some examples, the UE 115-a may configure default parameters 215 for each carrier 210, which may be configured when the given carrier 210 does not have parameters 215 for the indicated bit field value. In some examples, the UE 115-a may reuse parameters 215 for a given carrier 210 for other bit field values ​​in a given order (e.g., recursively, cyclically, etc.). In some examples, the UE 115-a may reuse the parameter 215 of the first bit field value for a given carrier 210 for other bit field values ​​that share the same bit value (same least significant bit (LSB) or same most significant bit (MSB)). In some examples, the network entity 105-a may configure the additional parameter 215 via RRC for the carrier 210 with a blank entry for the given bit field value. FIG. 3A to FIG. 3B ) describes further discussion of carrier parameter configuration 235 technology.

[0101] In some cases, the network entity 105-a may instruct the UE 115-a to perform a BWP switch for multiple carriers 210, where the active BWP for each carrier 210 may be switched to a second BWP. In an example where the second BWP supports a different number of parameters 215 (i.e., the carrier 210-a of the active BWP supports four parameters 215, while the carrier 210-a of the second BWP supports two parameters 215), the UE 115-a may determine the adjusted domain size of the control message 220 based on the techniques described herein. Figure 4 and Figure 5) describes further discussion of BWP switching of multiple carriers 210.

[0102] Figure 3A An example of a parameter configuration 300-a supporting a joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the parameter configuration 300-a can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, or a combination thereof. For example, carrier 310-a, carrier 310-b, carrier 310-c, and carrier 310-d can be reference Figure 2 Additionally or alternatively, parameters 315-a to 315-k may be reference Figure 2 Example of parameter 215.

[0103] like Figure 3A As illustrated, UE 115 may be configured with a parameter set 315 for each carrier 310. For example, carrier 310-a may be configured with four parameters 315 (e.g., parameter 315-a, parameter 315-b, parameter 315-c, and parameter 315-d), carrier 310-b may be configured with two parameters 315 (e.g., parameter 315-e and parameter 315-f), carrier 310-c may be configured with one parameter 315 (e.g., parameter 315-g), and carrier 310-a may be configured with four parameters 315 (e.g., parameter 315-h, parameter 315-i, parameter 315-j, and parameter 315-k). Figure 3A In the example of Figure 2 The bit field size is determined by formula 1 described above (e.g., the bit field size is based on the maximum number of parameters 315 configured for a given carrier 310). In some other specific implementations, the UE 115 can determine the bit field size based on the reference Figure 2 The described formula 2 determines the bit field size (eg, the bit field size is based on the minimum number of parameters 315 configured for a given carrier 310). In some other implementations, the UE 115 may determine the bit field size based on receiving an RRC message from the network entity 105 configuring the bit field size.

[0104] Based on UE 115 determining that the bit field size is 2, one or more carriers 310 may have blank entries for one or more field values ​​305-a of the bit field. For example, carrier 310-b may have blank entries for field value 305-a values ​​10 and 11, and carrier 310-c may have blank entries for field value 305-a values ​​01, 10, and 11. In some examples, the blank entries may be examples of blank parameters 315, empty parameters 315, N / A, no entry, unconfigured parameters 315, or no associated values.

[0105] In this way, UE 115 can process the blank entry for carrier 310 according to the techniques described herein. In some examples, if UE 115 receives a DCI message with a field value 305-a indicating a blank entry for carrier 310 (or cell), UE 115 can determine that the DCI message may not schedule data on the carrier 310 (or cell). For example, if UE 115 receives a value of 10 for field value 305-a, UE 115 can determine that the DCI message may not schedule data for carrier 310-b or carrier 310-c.

[0106] Additionally or alternatively, if UE 115 receives a DCI message with a field value 305-a indicating a blank entry for a carrier 310 (or cell), UE 115 may determine that the DCI message schedules data for the carrier 310 via a default configuration (e.g., default parameters 315). For example, if UE 115 receives a field value 305-a value of 10, UE 115 may use default parameters 315 for carrier 310-b and default parameters 315 for carrier 310-c. In some examples, the default parameters 315 for a given carrier may be parameters 315 associated with an all-zero bit field or code point (e.g., a field value 305-a value of 00). For example, referring to Figure 3A , the default parameters 315 for carrier 310-b may be parameters 315-e, and the default parameters 315 for carrier 310-c may be parameters 315-g. In some other examples, the default parameters 315 for a given carrier 310 may be the parameters 315 currently configured for the given carrier 310. For example, carrier 310-b may be currently configured with parameters 315-f. Thus, if UE 115 receives a value of 10 for domain value 305-a, UE 115 may determine to continue using parameters 315-f for carrier 310-b.

[0107] Additionally or alternatively, UE 115 may not expect to receive a DCI field having a field value 305-a that has a blank entry for at least one of configured carriers 310. Figure 3A , UE 115 may refrain from monitoring value 01, value 10, and value 11 of domain value 305-a based on carrier 310-b, carrier 310-c, or both having blank entries for these values. Additionally or alternatively, network entity 105 may refrain from sending DCI with value 01, value 10, and value 11 of domain value 305-a based on carrier 310-b, carrier 310-c, or both having blank entries for these values.

[0108] Figure 3BAn example of a parameter configuration 300-b and a parameter configuration 300-c supporting a joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the parameter configuration 300-b and the parameter configuration 300-c can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, the parameter configuration 300-a, or a combination thereof. For example, the carrier 310-a, the carrier 310-b, the carrier 310-c, and the carrier 310-d can be reference Figure 2 Additionally or alternatively, BWP 320-a to BWP 320-k and TDRA 325-a to TDRA 325-j may be reference Figure 2 Examples or references for parameter 215 Figure 3A Example of parameters 315.

[0109] Referring to parameter configuration 300-b, each field value 305-b may indicate a BWP 320 configuration in one or more BWP 320 configurations for each carrier 310. Referring to parameter configuration 300-c, each field value 305-c may indicate a TDRA 325 configuration in one or more TDRA 325 configurations for each carrier 310. In some examples, TDRA 325 may be an example of a start and length indication value (SLIV) or a time slot offset value (e.g., a k0 or k2 time domain allocation). As shown in FIG. Figure 3A As discussed, UE 115 may also determine the bit field size of parameter configuration 300-b and parameter configuration 300-c according to Formula 1. In some other implementations, UE 115 may determine the bit field size according to Formula 2. In some other implementations, UE 115 may determine the bit field size based on receiving an RRC message configuring the bit field size from network entity 105.

[0110] like Figure 3BAs illustrated, the UE 115 may be configured with a set of BWPs 320 for each carrier 310. For example, the carrier 310-a may be configured with four BWPs 320 (e.g., BWP 320-a, BWP 320-b, BWP 320-c, and BWP 320-d), the carrier 310-b may be configured with two BWPs 320 (e.g., BWP 320-e and BWP 320-f), the carrier 310-c may be configured with one BWP 320 (e.g., BWP 320-g), and the carrier 310-a may be configured with four BWPs 320 (e.g., BWP 320-h, BWP 320-i, BWP 320-j, and BWP 320-k). Additionally or alternatively, the UE 115 may be configured with a set of TDRAs 325 for the carriers 310. For example, carrier 310-a may be configured with seven TDRAs 325 (e.g., TDRA 325-a, TDRA 325-b, TDRA 325-c, TDRA 325-d, TDRA 325-e, TDRA 325-f, and TDRA 325-g), and carrier 310-b may be configured with three TDRAs 325 (e.g., TDRA 325-h, TDRA 325-i, and TDRA 325-j).

[0111] In some examples, parameter configuration 300-b and parameter configuration 300-c may be related. For example, a set of corresponding TDRAs 325 of carrier 310-a and carrier 310-b may be configured for a given BWP 320 of carrier 310-a and carrier 310-b. For example, TDRAs 325-a through TDRAs 325-g may be associated with BWP 320-a of carrier 310-a, and TDRAs 325-h through TDRAs 325-j may be associated with BWP 320-e of carrier 310-b.

[0112] In some examples, carrier 310 may be configured with various numbers of BWPs 320 and TDRAs 325, and therefore, one or more of domain values ​​305-b and domain values ​​305-c may have empty entries for one or more of carriers 310. In some examples, UE 115 may determine to recursively or cyclically fill empty entries with values ​​of existing entries. For example, UE 115 may fill domain value 305-b with a value of 10 with BWP 320-e and fill with a value of 11 with BWP 320-f. In an example where more domain values ​​305-b are to be filled for carrier 310-a, UE 115 will recursively fill BWP 320-e and BWP 320-f until each domain value 305-b of carrier 310-b is filled. Similarly, for carrier 310-c, UE 115 may recursively populate value 01, value 10, and value 11 of field value 305-b with BWP 320-g. In some examples, UE 115 may populate parameter configuration 300-c using the same technique as populating parameter configuration 300-b. For example, with reference to carrier 310-b, UE 115 may recursively populate field value 305-c with TDRA 325-h, TDRA 325-i, and TDRA 325-j until each value of field value 305-c is populated.

[0113] Figure 3C An example of a parameter configuration 300-d and a parameter configuration 300-e supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the parameter configuration 300-d and the parameter configuration 300-e may be reference Figure 3B Parameter configuration 300-b and parameter configuration 300-c are corresponding examples. Thus, Figure 3C Reference Figure 3B Filling techniques additional or alternative to those described.

[0114] As reference Figure 3C As illustrated, UE 115 may determine to fill blank entries with values ​​of existing entries that share similar bit values. For example, UE 115 may fill field value 305-d and field value 305-e with existing entries that share the same LSB value. For example, referring to carrier 310-b, UE 115 may fill field value 305-d with value 10 using BWP 320-e based on value 10 sharing an LSB with value 00, and may fill field value 305-d with value 11 using BWP 320-f based on value 11 sharing an LSB with value 01. In the example, in the event that the existing entry is a blank entry, UE 115 may refrain from filling the entry that shares the LSB value. For example, referring to carrier 310-c, UE 115 may refrain from filling field value 305-d with value 11 based on value 01 being a blank entry for carrier 310-c. Figure 3C As illustrated, UE 115 may populate parameter configuration 300-e using the same techniques as used to populate parameter configuration 300-d. Figure 3C An LSB-based padding technique is illustrated, but in some other implementations, the UE 115 may employ an MSB-based padding technique, where the UE 115 fills empty entries with existing entries that share the same MSB.

[0115] Figure 4 An example of a BWP configuration timing diagram 400 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the BWP configuration timing diagram 400 can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, the parameter configuration 300-a to the parameter configuration 300-e, or a combination thereof. For example, carrier 410-a, carrier 410-b, carrier 410-c, and carrier 410-d can be reference Figure 2 An example or reference of carrier wave 210 FIG. 3A to FIG. 3C Additionally or alternatively, parameter 415 may be a reference Figure 2 An example of parameter 215 of or an example of parameter 315 of reference FIG. 3 .

[0116] like Figure 4 As illustrated, UE 115 may be configured with a carrier set 410 for uplink and downlink communications with the network. In some examples, network entity 105 may configure a first BWP (e.g., BWP configuration 425-a) for UE 115, where UE 115 uses a first corresponding BWP for each carrier 410. In some examples, network entity 105 may configure UE 115 to use the first corresponding BWP for a duration 420 (e.g., a plurality of timing resources or a plurality of timing time slots). For example, referring to Figure 4 , the network entity 105 may configure the use of the first corresponding BWP in the first time slot. In some examples, each carrier 410 using the first corresponding BWP may also be associated with one or more parameters 415, which are associated with the first corresponding BWP. For example, when configured with BWP configuration 425-a, carrier 410-a may be configured with parameter 415-a and parameter 415-b, carrier 410-b may be configured with parameter 415-c and parameter 415-d, carrier 410-c may be configured with parameter 415-e and parameter 415-f, and carrier 410-d may be configured with parameter 415-g and parameter 415-h. Thus, according to Formula 1 or Formula 2, UE 115 may determine that the bit field size of domain value 405-a is 2. In some other examples, UE 115 may determine the bit field size based on receiving an RRC configuration message configuring the bit field size from network entity 105.

[0117] In some cases, the UE 115 may receive a DCI 430-a from the network entity 105 that may indicate a field value 405-a (e.g., 0 or 1) for the UE 115 to use when determining which parameters 415 to use. However, in some cases, the UE 115 may receive a DCI-based BWP switch in which the size of the bit field associated with the parameters 415 may change. For example, the UE 115 may receive a DCI 430-b that may instruct the UE 115 to switch from a first corresponding BWP for each carrier 410 (e.g., BWP configuration 425-a) to a second corresponding BWP for each carrier 410 (e.g., BWP configuration 425-b). Figure 4 As illustrated, when associated with BWP configuration 425-b, each carrier 410 may have a varying number of parameters 415. For example, with reference to BWP configuration 425-b, carrier 410-a may be associated with four parameters 415 (e.g., parameter 415-k, parameter 415-l, parameter 415-m, and parameter 415-n), carrier 410-b may be associated with two parameters 415 (e.g., parameter 415-o and parameter 415-p), carrier 410-c may be associated with one parameter 415 (e.g., parameter 415-q), and carrier 410-d may be associated with four parameters 415 (e.g., parameter 415-r, parameter 415-s, parameter 415-t, and parameter 415-u). Thus, the bit field of field value 405-b may have a larger number of bits (e.g., two bits) than the bit field of field value 405-a (e.g., one bit). In an example where the bit field increases from a first BWP configuration to a second BWP configuration, the UE 115 may interpret the bit field using a number of LSBs of the DCI format that is equal to the bit field for the uplink BWP and the downlink BWP before interpreting the DCI format information field. For example, referring to BWP configuration 425-b, the UE 115 may interpret the bit field size using two LSBs of the DCI 430-b bit field based on a maximum number of parameters 415 configured for the carrier 410 being four. Based on switching to BWP configuration 425-b, the UE 115 may periodically receive DCI 430 (e.g., DCI 430-c and DCI 430-d) that may indicate a field value 405-b of the bit field to be used when determining which parameters 415 to use for the corresponding carrier 410.

[0118] In some cases, UE 115 may refer to FIG. 3A to FIG. 3CIn some examples, if UE 115 receives DCI 430 with a field value 405-b indicating a blank entry for a carrier 410 (or cell), UE 115 may determine that DCI 430 may not schedule data on the carrier 410 (or cell). In some examples, if UE 115 receives DCI 430 with a field value 405-b indicating a blank entry for a carrier 410 (or cell), UE 115 may determine that DCI 430 schedules data for the carrier 410 via a default configuration (e.g., default parameters 415), as described in reference to FIG. Figure 3A Additionally or alternatively, UE 115 may refrain from monitoring a DCI bit field having a field value 405-b that has a blank entry for at least one of configured carriers 410. In some examples, UE 115 may recursively fill in the blank entries, as described in reference to Figure 3B In some examples, the UE 115 can fill the blank entry (e.g., LSB-based filling or MSB-based filling) based on the first domain value 405-b sharing the same bit value with the second domain value 405-b, as described in reference Figure 3C as described.

[0119] In some examples, UE 115 may receive DCI 430 indicating that UE 115 is transitioning from a BWP configuration 425 configured with more parameters 415 to a BWP configuration 425 configured with fewer parameters 415. For example, DCI 430 may indicate that UE 115 is switching from BWP configuration 425-b to BWP configuration 425-a. In such examples, UE 115 may determine the size of the bit field by adding zeros in front of the value of the bit field until the size of the bit field reaches the size for interpreting the BWP configuration 425 with fewer parameters 415. For example, referring to Figure 4 If the UE switches from BWP configuration 425-b to BWP configuration 425-a, the UE 115 adds zeros in front of the bit field until the bit field is a one-bit field (e.g., to account for the size of the carrier 410 associated with BWP configuration 425-a).

[0120] Figure 5 An example of a BWP configuration timing diagram 500 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the BWP configuration timing diagram 500 can implement one or more aspects of the wireless communication system 100, the wireless communication system 200, the parameter configuration 300-a to the parameter configuration 300-e, or a combination thereof. For example, carrier 510-a, carrier 510-b, carrier 510-c, and carrier 510-d can be reference Figure 2Examples of carrier 210, reference FIG. 3A to FIG. 3C An example or reference of carrier wave 310 Figure 4 Additionally or alternatively, parameter 515 may be a reference Figure 2 3 or the example of parameter 215 of reference figure 315. Figure 4 Example of parameters 415.

[0121] like Figure 5 As illustrated, UE 115 may be configured with a set of carriers 510 for uplink or downlink communication with the network. In some examples, network entity 105 may configure a first BWP (e.g., BWP configuration 525-a) for UE 115, where UE 115 uses a first corresponding BWP for each carrier 510. In some examples, network entity 105 may configure UE 115 to use the first corresponding BWP for a duration 520 (e.g., a plurality of timing resources or a plurality of timing time slots). For example, referring to Figure 5 , the network entity 105 may configure the use of the first corresponding BWP in the first time slot. In some examples, each carrier 510 using the first corresponding BWP may also be associated with one or more parameters 515, which are associated with the first corresponding BWP. For example, when configuring the BWP configuration 525-a, the carrier 510-a may be configured with parameters 515-a and 515-b, the carrier 510-b may be configured with parameters 515-c and 515-d, the carrier 510-c may be configured with parameters 515-e and 515-f, and the carrier 510-d may be configured with parameters 515-g and 515-h. In this way, according to Formula 1 or Formula 2, the UE 115 may determine that the bit field size of the domain value 505-a is 2. In some other examples, the UE 115 may determine the bit field size based on receiving an RRC configuration message configuring the bit field size from the network entity 105.

[0122] In some cases, the UE 115 may receive a DCI 530-a from the network entity 105 that may indicate a field value 505-a (e.g., 0 or 1) for the UE 115 to use when determining which parameters 515 to use. However, in some cases, the UE 115 may receive a DCI-based BWP switch in which the size of the bit field associated with the parameter 515 may vary. For example, the UE 115 may receive a DCI 530-b that may indicate that the UE 115 is switching from a first corresponding BWP (e.g., BWP configuration 525-a) of one or more carriers 510 to a second corresponding BWP (e.g., BWP configuration 525-b) of the one or more carriers 510. Figure 5As illustrated, DCI 530-b may instruct carrier 510-b and carrier 510-c to switch to BWP configuration 525-b, and instruct carrier 510-a and carrier 510-d to remain in BWP configuration 525-a. Based on carrier 510-b and carrier 510-c switching to BWP configuration 525-b, each carrier 510 may have a varying number of parameters 515. For example, carrier 510-a may remain associated with the previous two parameters 515 (e.g., parameter 515-a and parameter 515-b), carrier 510-b may be associated with four parameters 515 (e.g., parameter 515-k, parameter 515-l, parameter 515-m, and parameter 515-n), carrier 510-c may be associated with four parameters 515 (e.g., parameter 515-o, parameter 515-p, parameter 515-q, and parameter 515-r), and carrier 510-d may remain associated with the previous two parameters 515 (e.g., parameter 515-g and parameter 515-h). Thus, the bit field of domain value 505-b may have a larger number of bits (e.g., two bits) than the bit field of domain value 505-a (e.g., one bit). In an example where the bit field increases from a first BWP configuration to a second BWP configuration, the UE 115 may interpret the bit field using a number of LSBs of the DCI format equal to the bit field for the uplink BWP and the downlink BWP before interpreting the DCI format information field. For example, with reference to DCI 530-b that switches carrier 510-b and carrier 510-c to BWP configuration 525-b, the UE 115 may interpret the bit field size using two LSBs of the DCI 530-b bit field based on a maximum number of parameters 515 configured for carrier 510 being 4. In some cases, the UE 115 may periodically receive DCI 530 (e.g., DCI 530-c and DCI 530-d) that may indicate a field value 505-b of the bit field to be used when determining which parameters 515 to use for the corresponding carrier 510.

[0123] In some cases, UE 115 may refer to FIG. 3A to FIG. 3C In some examples, if UE 115 receives DCI 530 with a field value 505-b indicating a blank entry for a carrier 510 (or cell), UE 115 may determine that DCI 530 may not schedule data on the carrier 510 (or cell). In some examples, if UE 115 receives DCI 530 with a field value 505-b indicating a blank entry for a carrier 510 (or cell), UE 115 may determine that DCI 530 schedules data for the carrier 510 via a default configuration (e.g., default parameters 515), as described in reference to FIG. Figure 3AAdditionally or alternatively, UE 115 may refrain from monitoring a DCI bit field having a field value 505-b that has a blank entry for at least one of configured carriers 510. In some examples, UE 115 may recursively fill in the blank entries, as described in reference to Figure 3B In some examples, the UE 115 can fill the blank entry (e.g., LSB-based filling or MSB-based filling) based on the first domain value 505-b sharing the same bit value with the second domain value 505-b, as described in reference Figure 3C as described.

[0124] In some examples, UE 115 may receive DCI 530 that instructs UE 115 to transition from a BWP configuration 525 configured with more parameters 515 to a BWP configuration 525 configured with fewer parameters 515. For example, DCI 530 may instruct UE 115 to switch carrier 510-b and carrier 510-c from BWP configuration 525-b back to BWP configuration 525-a. In such examples, UE 115 may determine the size of the bit field by adding zeros in front of the value of the bit field until the size of the bit field reaches a size for interpreting the BWP configuration 525 with fewer parameters 515. For example, referring to Figure 5 If each carrier 510 switches back to BWP configuration 525-a, the UE 115 adds zeros in front of the bit field until the bit field is a one-bit field (e.g., to account for the size of the carrier associated with BWP configuration 525-a).

[0125] Figure 6 An example of a process flow 600 for supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 600 can implement aspects of the wireless communication system 100, the wireless communication system 200, the parameter configuration 300-a to the parameter configuration 300-e, the BWP configuration timing diagram 400, the BWP configuration timing diagram 500, or a combination thereof. The process flow 600 includes the UE 115-b and the network entity 105-b, which can be reference Figure 2 105 and corresponding examples of UE 115 and network entity 105. The following alternative examples may be implemented in which some of the steps are performed in a different order than described or are not performed at all. In some cases, the steps may include additional features not mentioned below, or other steps may be added. In addition, although process flow 600 shows the process between UE 115 and network entity 105, it should be understood that these processes may occur between any number of network devices.

[0126] At 605, UE 115-b may receive a parameter configuration message. In some examples, the parameter configuration message may indicate one or more parameter sets for a set of carriers supported by UE 115-b, the one or more parameter sets indicating communication parameters for communicating via the set of carriers. In some examples, each parameter in the one or more parameter sets may be BWP or TDRA.

[0127] At 610, UE 115-b may monitor a field of a control message based on the parameter configuration message. In some examples, a field size of the field may be based on the one or more parameter sets, and a corresponding value of the field may indicate a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. Based on monitoring the field of the control message, at 615, UE 115-b may receive a control message indicating the corresponding parameter set.

[0128] In some examples, at 620, UE 115-b may receive an RRC message indicating a number of bits associated with the domain for decoding, wherein the domain size is based on the number of bits.

[0129] At 625, the UE 115-b may decode the field of the control message. For example, the UE 115-b may decode one or more bits of the field of the control message based on the field size, where the field size may be based on a number of parameters associated with a parameter set of the one or more parameter sets. In some cases, the UE 115-b may determine the field size based on a carrier of the carrier set that is associated with the parameter set, where the number of parameters may be greater than a number of corresponding parameters for each remaining carrier of the carrier set. In some cases, the UE 115-b may determine the field size based on a carrier of the carrier set that is associated with the parameter set, where the number of parameters may be less than a number of corresponding parameters for each remaining carrier of the carrier set.

[0130] At 630, UE 115-b may perform carrier parameter configuration based on the decoded values ​​of the field. In some examples, each value of the field for a first subset of carriers of the set of carriers may indicate at least one corresponding parameter for each carrier of the first subset of carriers, and each value of the field for a second subset of carriers is associated with a blank value for each carrier of the second subset of the set of carriers, the second subset of carriers not including the first subset of carriers.

[0131] In some examples, UE 115-b may refrain from using the carrier to communicate one or more messages based on the value of the field for a carrier in the second subset of carriers corresponding to the blank value.

[0132] In some examples, UE 115-b can communicate using corresponding default parameters for each carrier of the second subset of carriers based on the value of the field for each carrier of the second subset of carriers corresponding to the blank value. In such examples, the default parameter can correspond to a zero code point field parameter for the corresponding carrier.

[0133] In some examples, UE 115-b may fill blank values ​​for a given value of the domain for the second subset of carriers by reusing parameters for the second subset of carriers associated with other values ​​of the domain. For example, UE 115-b may recursively fill the blank values ​​for the given carrier by reusing parameters for the given carrier associated with other values ​​of the domain. Additionally or alternatively, UE 115-b may fill a first blank value associated with the first value of the domain using parameters associated with the second value of the domain based on the first value of the domain for the given carrier sharing one or more common bits with the second value of the domain for the given carrier.

[0134] In some examples, UE 115-b may monitor a subset of values ​​for the domain in a set of available values ​​for the domain, wherein each value of the subset of values ​​includes a corresponding parameter for each carrier of the set of carriers. In such examples, UE 115-b may communicate one or more messages based on the domain of the control message being a value in the subset of values.

[0135] At 635, UE 115-b may communicate one or more messages via at least one carrier of the set of carriers using the corresponding set of parameters for the at least one carrier.

[0136] In some examples, at 640, UE 115-b may receive a second control message indicating a change from the one or more parameter sets to a second one or more parameter sets for the set of carriers available to UE 115-b.

[0137] In such an example, at 645, UE 115-b may perform carrier parameter reconfiguration. For example, the number of bits associated with the field of the second one or more parameter sets may be less than the number of bits associated with the field of the one or more parameter sets. In such an instance, UE 115-b may zero the value of the field that may be associated with the one or more parameter sets and not associated with the second one or more parameter sets. Additionally or alternatively, the number of bits associated with the field of the second one or more parameter sets may be greater than the number of bits associated with the field of the one or more parameter sets. In such an instance, UE 115-b may interpret the entries of the field of the second one or more parameter sets using the number of LSBs associated with the one or more parameter sets.

[0138] Figure 7A block diagram 700 of a device 705 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 705 may be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0139] The receiver 710 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to joint indications for multi-cell scheduling). The information may be communicated to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0140] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to joint indications for multi-cell scheduling). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0141] The communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of joint indication for multi-cell scheduling as described herein. For example, the communication manager 720, the receiver 710, the transmitter 715, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0142] In some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is configured to or otherwise supports means for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0143] Additionally or alternatively, in some examples, the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 720, the receiver 710, the transmitter 715, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functionality described in the present disclosure).

[0144] In some examples, the communication manager 720 can be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 can receive information from the receiver 710, transmit information to the transmitter 715, or be integrated in conjunction with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0145] According to examples as disclosed herein, the communication manager 720 may support wireless communications. For example, the communication manager 720 may be configured as or otherwise support a component for performing the following operations: receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The communication manager 720 may be configured as or otherwise support a component for performing the following operations: monitoring a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The communication manager 720 may be configured as or otherwise support a component for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0146] By including or configuring a communication manager 720 according to examples as described herein, the device 705 (e.g., a processor controlling or otherwise coupled to the receiver 710, the transmitter 715, the communication manager 720, or a combination thereof) can support techniques for more efficiently utilizing communication resources, reducing signaling overhead, and improving domain decoding reliability.

[0147] Figure 8A block diagram 800 of a device 805 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 805 may be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The receiver 810 may provide means for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to joint indications for multi-cell scheduling). The information may be communicated to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0149] The transmitter 815 may provide means for transmitting signals generated by other components of the device 805. For example, the transmitter 815 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to joint indications for multi-cell scheduling). In some examples, the transmitter 815 may be co-located with the receiver 810 in a transceiver module. The transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0150] The device 805 or its various components may be examples of components for performing various aspects of the joint indication for multi-cell scheduling as described herein. For example, the communication manager 820 may include a parameter receiving component 825, a control domain monitoring component 830, a carrier communication component 835, or any combination thereof. The communication manager 820 may be an example of various aspects of the communication manager 720 as described herein. In some examples, the communication manager 820 or its various components may be configured to use the receiver 810, the transmitter 815, or both or otherwise cooperate with them to perform various operations (e.g., receive, obtain, monitor, output, send). For example, the communication manager 820 may receive information from the receiver 810, transmit information to the transmitter 815, or be integrated with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0151] According to examples as disclosed herein, the communication manager 820 may support wireless communications. The parameter receiving component 825 may be configured as or otherwise support a means for performing the following operations: receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The control domain monitoring component 830 may be configured as or otherwise support a means for performing the following operations: monitoring a domain of a control message based on the message, wherein a domain size of the domain is based on the one or more parameter sets, and wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The carrier communication component 835 may be configured as or otherwise support a means for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0152] Fig. 9 A block diagram 900 of a communication manager 920 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The communication manager 920 can be an example of aspects of the communication manager 720, the communication manager 820, or both as described herein. The communication manager 920 or its various components can be examples of means for performing various aspects of the joint indication for multi-cell scheduling as described herein. For example, the communication manager 920 may include a parameter receiving component 925, a control domain monitoring component 930, a carrier communication component 935, a decoding component 940, a carrier parameter determination component 945, an RRC message receiving component 950, a domain size determination component 955, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0153] According to examples as disclosed herein, the communication manager 920 may support wireless communications. The parameter receiving component 925 may be configured as or otherwise support a means for performing the following operations: receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The control domain monitoring component 930 may be configured as or otherwise support a means for performing the following operations: monitoring a domain of a control message based on the message, wherein a domain size of the domain is based on the one or more parameter sets, and wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The carrier communication component 935 may be configured as or otherwise support a means for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0154] In some examples, to support monitoring of the field of the control message, the decoding component 940 may be configured as or otherwise support a means for decoding one or more bits of the field of the control message based on the field size, where the field size may be based on the number of parameters associated with a parameter set of the one or more parameter sets.

[0155] In some examples, domain size determining component 955 may be configured as or otherwise support means for determining the domain size based on a carrier of the carrier set, the carrier being associated with the parameter set, wherein the number of parameters is greater than the number of corresponding parameters for each remaining carrier of the carrier set.

[0156] In some examples, domain size determining component 955 may be configured as or otherwise support means for determining the domain size based on a carrier of the carrier set, the carrier being associated with the parameter set, wherein the number of parameters is less than the number of corresponding parameters for each remaining carrier of the carrier set.

[0157] In some examples, each value of the field for a first subset of carriers of the set of carriers indicates at least one corresponding parameter for each carrier of the first subset of carriers, the first subset of carriers including the one or more carriers. In some examples, each value of the field for a second subset of carriers is associated with a blank value for each carrier of the second subset of the set of carriers, the second subset of carriers not including the first subset of carriers.

[0158] In some examples, carrier parameter determination component 945 can be configured as or otherwise support means for performing the following operations: based on the value of the field of a carrier in the second subset of carriers corresponding to the blank value, refraining from using the carrier to communicate the one or more messages.

[0159] In some examples, carrier parameter determination component 945 can be configured as or otherwise support means for performing the following operations: based on the value of the field for each carrier of the second subset of carriers corresponding to the blank value, communicating using corresponding default parameters for each carrier of the second subset of carriers.

[0160] In some examples, each respective default parameter corresponds to a zero code point domain parameter for the respective carrier.

[0161] In some examples, carrier parameter determination component 945 can be configured as or otherwise support means for filling blank values ​​for the second carrier subset for a given value of the domain by reusing parameters for the second carrier subset associated with other values ​​of the domain.

[0162] In some examples, to support filling blank values ​​for a given carrier of the second subset of carriers, the carrier parameter determination component 945 may be configured as or otherwise support means for recursively filling the blank values ​​for the given carrier by reusing parameters for the given carrier associated with other values ​​of the domain.

[0163] In some examples, to support filling blank values ​​for a given carrier of the second subset of carriers, the carrier parameter determination component 945 may be configured as or otherwise support a means for performing the following operations: based on the first value of the domain of the given carrier sharing one or more common bits with the second value of the domain of the given carrier, fill a first blank value associated with the first value of the domain using a parameter associated with the second value of the domain.

[0164] In some examples, control domain monitoring component 930 can be configured as or otherwise support means for monitoring a subset of values ​​of the domain in a set of available values ​​for the domain, wherein each value of the subset of values ​​comprises a corresponding parameter for each carrier of the set of carriers. In some examples, carrier communication component 935 can be configured as or otherwise support means for communicating the one or more messages based on the domain of the control message being a value in the subset of values.

[0165] In some examples, RRC message receiving component 950 can be configured as or otherwise support means for receiving a radio resource control message indicating a number of bits associated with the domain for decoding, wherein the domain size is based on the number of bits.

[0166] In some examples, parameter receiving component 925 may be configured as or otherwise support means for receiving a second control message indicating a change from the one or more parameter sets to a second one or more parameter sets available to the carrier set for the UE.

[0167] In some examples, the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the one or more parameter sets.

[0168] In some examples, domain size determination component 955 can be configured as or otherwise support means for zeroing the value of the domain associated with the one or more parameter sets and not associated with the second one or more parameter sets.

[0169] In some examples, the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the one or more parameter sets.

[0170] In some examples, domain size determination component 955 can be configured as or otherwise support means for interpreting entries of the domain of the second one or more parameter sets using the number of LSBs associated with the one or more parameter sets.

[0171] In some examples, each parameter in the one or more parameter sets includes a BWP or a TDRA.

[0172] Fig.10 A diagram of a system 1000 including a device 1005 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of a device 705, a device 805, or a UE 115 as described herein or include a component of these devices. The device 1005 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1005 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, a memory 1030, a code 1035, and a processor 1040. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1045).

[0173] I / O controller 1010 can manage input and output signals for device 1005. I / O controller 1010 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1010 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1010 may be implemented as part of a processor such as processor 1040. In some cases, a user may interact with device 1005 via I / O controller 1010 or via hardware components controlled by I / O controller 1010.

[0174] In some cases, the device 1005 may include a single antenna 1025. However, in some other cases, the device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. As described herein, the transceiver 1015 may communicate bidirectionally via one or more antennas 1025, wired or wireless links. For example, the transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1015 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 1025 for transmission, and demodulating packets received from one or more antennas 1025. The transceiver 1015, or the transceiver 1015 and one or more antennas 1025 may be examples of transmitters 715, transmitters 815, receivers 710, receivers 810, or any combination thereof or components thereof as described herein.

[0175] The memory 1030 may include random access memory (RAM) and read-only memory (ROM). The memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed by the processor 1040, cause the device 1005 to perform various functions described herein. The code 1035 may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, the code 1035 may not be directly executable by the processor 1040, but may cause the computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, the memory 1030 may include a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0176] The processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to enable the device 1005 to perform various functions (e.g., functions or tasks supporting joint indication for multi-cell scheduling). For example, the device 1005 or a component of the device 1005 may include a processor 1040 and a memory 1030 coupled to or coupled to the processor 1040, and the processor 1040 and the memory 1030 are configured to perform the various functions described herein.

[0177] According to examples as disclosed herein, the communication manager 1020 may support wireless communications. For example, the communication manager 1020 may be configured as or otherwise support a component for performing the following operations: receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The communication manager 1020 may be configured as or otherwise support a component for performing the following operations: monitoring a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The communication manager 1020 may be configured as or otherwise support a component for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0178] By including or configuring a communication manager 1020 according to examples as described herein, the device 1005 can support techniques for more efficiently utilizing communication resources, reducing signaling overhead, improving communication reliability, improving coordination between devices, reducing latency, and improving domain decoding reliability.

[0179] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1015, one or more antennas 1025, or any combination thereof. Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported or performed by the processor 1040, the memory 1030, the code 1035, or any combination thereof. For example, the code 1035 may include instructions that are executable by the processor 1040 to cause the device 1005 to perform various aspects of the joint indication for multi-cell scheduling as described herein, or the processor 1040 and the memory 1030 may be otherwise configured to perform or support such operations.

[0180] Fig.11 A block diagram 1100 of a device 1105 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0181] The receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1105. In some examples, the receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0182] The transmitter 1115 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1105. For example, the transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1115 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1115 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1115 and the receiver 1110 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0183] The communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or various components thereof may be examples of means for performing various aspects of joint indication for multi-cell scheduling as described herein. For example, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

[0184] In some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0185] Additionally or alternatively, in some examples, the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functions of the communication manager 1120, the receiver 1110, the transmitter 1115, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure).

[0186] In some examples, communication manager 1120 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in conjunction with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0187] According to examples as disclosed herein, the communication manager 1120 may support wireless communications. For example, the communication manager 1120 may be configured as or otherwise support a component for performing the following operations: sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The communication manager 1120 may be configured as or otherwise support a component for performing the following operations: sending a control message via a carrier of the carrier set based on the message, wherein a domain size associated with a domain of the control message is based on the one or more parameter sets, wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The communication manager 1120 may be configured as or otherwise support a component for performing the following operations: communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0188] By including or configuring a communication manager 1120 according to examples as described herein, a device 1105 (e.g., a processor controlling or otherwise coupled to a receiver 1110, a transmitter 1115, a communication manager 1120, or a combination thereof) may support techniques for more efficiently utilizing communication resources, reducing signaling overhead, and improving domain decoding reliability.

[0189] Fig.12 A block diagram 1200 of a device 1205 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 1205 may be an example of aspects of the device 1105 or network entity 105 as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communication manager 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0190] The receiver 1210 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be communicated to other components of the device 1205. In some examples, the receiver 1210 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0191] The transmitter 1215 may provide means for outputting (e.g., sending, providing, communicating, transmitting) information generated by other components of the device 1205. For example, the transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, the transmitter 1215 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1215 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0192] The device 1205 or its various components may be examples of means for performing various aspects of the joint indication for multi-cell scheduling as described herein. For example, the communication manager 1220 may include a parameter sending component 1225, a control message sending component 1230, a carrier communication component 1235, or any combination thereof. The communication manager 1220 may be an example of various aspects of the communication manager 1120 as described herein. In some examples, the communication manager 1220 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with the receiver 1210, the transmitter 1215, or both. For example, the communication manager 1220 may receive information from the receiver 1210, transmit information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to receive information, output information, or perform various other operations as described herein.

[0193] According to examples as disclosed herein, the communication manager 1220 may support wireless communications. The parameter sending component 1225 may be configured as or otherwise support a means for performing the following operations: sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The control message sending component 1230 may be configured as or otherwise support a means for performing the following operations: sending a control message via a carrier of the carrier set based on the message, wherein a domain size associated with a domain of the control message is based on the one or more parameter sets, wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The carrier communication component 1235 may be configured as or otherwise support a means for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0194] Fig.13 A block diagram 1300 of a communication manager 1320 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The communication manager 1320 may be an example of the communication manager 1120, the communication manager 1220, or aspects of both as described herein. The communication manager 1320 or its various components may be examples of means for performing various aspects of joint indication for multi-cell scheduling as described herein. For example, the communication manager 1320 may include a parameter sending component 1325, a control message sending component 1330, a carrier communication component 1335, an RRC message sending component 1340, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses), which may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0195] According to examples as disclosed herein, the communication manager 1320 may support wireless communications. The parameter sending component 1325 may be configured as or otherwise support a means for performing the following operations: sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The control message sending component 1330 may be configured as or otherwise support a means for performing the following operations: sending a control message via a carrier of the carrier set based on the message, wherein a domain size associated with a domain of the control message is based on the one or more parameter sets, wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The carrier communication component 1335 may be configured as or otherwise support a means for performing the following operations: communicating one or more messages using the corresponding parameter set for the at least one carrier via at least one carrier of the carrier set.

[0196] In some examples, RRC message sending component 1340 can be configured as or otherwise support means for sending a radio resource control message indicating a number of bits associated with the domain, wherein the domain size is based on the number of bits.

[0197] In some examples, the control message sending component 1330 may be configured as or otherwise support a component for performing the following operations: sending a second control message indicating a change from the one or more parameter sets for the carrier set available to the UE to a second one or more parameter sets for the carrier set available to the UE.

[0198] In some examples, the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the one or more parameter sets.

[0199] In some examples, the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the one or more parameter sets.

[0200] In some examples, each parameter in one or more parameter sets includes a bandwidth portion or a TDRA.

[0201] Fig.14A diagram of a system 1400 including a device 1405 supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of a device 1105, a device 1205, or a network entity 105 as described herein, or include components thereof. The device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1405 may include components that support output and acquisition of communications, such as a communication manager 1420, a transceiver 1410, an antenna 1415, a memory 1425, a code 1430, and a processor 1435. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1440).

[0202] The transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. For example, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1405 may include one or more antennas 1415, which may be capable of sending or receiving wireless transmissions (e.g., concurrently). The transceiver 1410 may also include a modem to modulate a signal, provide a modulated signal for transmission (e.g., through one or more antennas 1415, through a wired transmitter), receive a modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and demodulate a signal. The transceiver 1410, or the transceiver 1410 and one or more antennas 1415 or wired interfaces (where applicable) may be examples of transmitter 1115, transmitter 1215, receiver 1110, receiver 1210, or any combination thereof or components thereof as described herein. In some examples, the transceiver may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0203] Memory 1425 may include RAM and ROM. Memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by processor 1435, cause device 1405 to perform various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, memory 1425 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0204] Processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, ASIC, CPU, FPGA, microcontroller, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1435. Processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1425) to enable device 1405 to perform various functions (e.g., functions or tasks supporting joint indications for multi-cell scheduling). For example, device 1405 or a component of device 1405 may include processor 1435 and memory 1425 coupled to processor 1435, and processor 1435 and memory 1425 are configured to perform various functions described herein. Processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance), which may host functions for performing functions of device 1405 (e.g., by executing code 1430).

[0205] In some examples, bus 1440 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1440 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1405, or communications performed between different components of device 1405 that may be co-located or located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, memory 1425, code 1430, and processor 1435 may be located in one of the different components or divided between the different components).

[0206] In some examples, communication manager 1420 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1420 may manage delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1420 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in collaboration with other network entities 105. In some examples, communication manager 1420 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0207] According to examples as disclosed herein, the communication manager 1420 may support wireless communications. For example, the communication manager 1420 may be configured as or otherwise support a means for performing the following operations: sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The communication manager 1420 may be configured as or otherwise support a means for performing the following operations: sending a control message via a carrier of the carrier set based on the message, wherein a domain size associated with a domain of the control message is based on the one or more parameter sets, wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The communication manager 1420 may be configured as or otherwise support a means for performing the following operations: communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0208] By including or configuring a communication manager 1420 according to examples as described herein, the device 1405 can support techniques for more efficiently utilizing communication resources, reducing signaling overhead, improving communication reliability, improving coordination between devices, reducing latency, and improving domain decoding reliability.

[0209] In some examples, the communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof. Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the processor 1435, the memory 1425, the code 1430, the transceiver 1410, or any combination thereof. For example, the code 1430 may include instructions that are executable by the processor 1435 to cause the device 1405 to perform various aspects of the joint indication for multi-cell scheduling as described herein, or the processor 1435 and the memory 1425 may be otherwise configured to perform or support such operations.

[0210] Fig.15 A flowchart illustrating a method 1500 for supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0211] At 1505, the method may include receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Fig. 9 The described parameters are received by component 925 for execution.

[0212] At 1510, the method may include monitoring a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The described control domain monitoring component 930 is executed.

[0213] At 1515, the method may include communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The carrier communication component 935 described is executed.

[0214] Fig.16 A flowchart illustrating a method 1600 for supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 10 The described UE 115 may be performed. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0215] At 1605, the method may include receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The operations of 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Fig. 9 The described parameters are received by component 925 for execution.

[0216] At 1610, the method may include monitoring a field of a control message based on the message, wherein a field size of the field is based on the one or more parameter sets, and wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The operations of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Fig. 9 The described control domain monitoring component 930 is executed.

[0217] At 1615, the method may include decoding one or more bits of the field of the control message based on the field size, wherein the field size is based on the number of parameters associated with the parameter set of the one or more parameter sets. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Fig. 9 The decoding component 940 is used to perform.

[0218] At 1620, the method may include communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier. The operations of 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Fig. 9 The carrier communication component 935 described is executed.

[0219] Fig.17 A flowchart illustrating a method 1700 for supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0220] At 1705, the method may include sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Fig.13 The described parameter sending component 1325 is executed.

[0221] At 1710, the method may include sending a control message via a carrier of the carrier set based on the message, wherein a field size associated with a field of the control message is based on the one or more parameter sets, wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The operations of 1710 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Fig.13 The described control message sending component 1330 is executed.

[0222] At 1715, the method may include communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier. The operations of 1715 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Fig.13 The carrier communication component 1335 described is executed.

[0223] Fig.18A flowchart illustrating a method 1800 for supporting joint indication for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 6 as well as Figures 11 to 14 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0224] At 1805, the method may include sending a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.13 The described parameter sending component 1325 is executed.

[0225] At 1810, the method may include sending a control message via a carrier of the carrier set based on the message, wherein a field size associated with a field of the control message is based on the one or more parameter sets, wherein a corresponding value of the field indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.13 The described control message sending component 1330 is executed.

[0226] At 1815, the method may include communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier. The operations of 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Fig.13 The carrier communication component 1335 described is executed.

[0227] At 1820, the method may include sending a second control message indicating a change from the one or more parameter sets for the carrier set available to the UE to a second one or more parameter sets for the carrier set available to the UE. The operations of 1820 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described in reference to Fig.13 The described control message sending component 1330 is executed.

[0228] The following provides an overview of various aspects of the disclosure:

[0229] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a message indicating one or more parameter sets for a carrier set supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; monitoring a domain of a control message based at least in part on the message, wherein a domain size of the domain is based at least in part on the one or more parameter sets, and wherein a corresponding value of the domain indicates a corresponding parameter set of the one or more parameter sets for one or more carriers of the carrier set; and communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0230] Aspect 2: A method according to Aspect 1, wherein monitoring the domain of the control message includes: decoding one or more bits of the domain of the control message based at least in part on the domain size, wherein the domain size is based at least in part on the number of parameters associated with a parameter set of the one or more parameter sets.

[0231] Aspect 3: According to the method according to Aspect 2, the method also includes: determining the domain size at least in part based on a carrier of the carrier set, the carrier being associated with the parameter set, wherein the number of parameters is greater than the number of corresponding parameters for each remaining carrier of the carrier set.

[0232] Aspect 4: According to the method described in any one of Aspects 2 to 3, the method also includes: determining the domain size at least in part based on the carriers of the carrier set, the carriers being associated with the parameter set, wherein the number of parameters is less than the number of corresponding parameters for each remaining carrier of the carrier set.

[0233] Aspect 5: A method according to any one of Aspects 1 to 4, wherein each value of the domain of a first carrier subset of the carrier set indicates at least one corresponding parameter for each carrier of the first carrier subset, and the first carrier subset includes the one or more carriers; and each value of the domain of a second carrier subset is associated with a blank value for each carrier of the second subset of the carrier set, and the second carrier subset does not include the first carrier subset.

[0234] Aspect 6: The method according to aspect 5, further comprising: refraining from using the carrier to communicate the one or more messages based at least in part on the value of the field of the carrier in the second subset of carriers corresponding to the blank value.

[0235] Aspect 7: According to any one of Aspects 5 to 6, the method also includes: communicating using corresponding default parameters for each carrier of the second carrier subset based at least in part on the value of the domain of each carrier of the second carrier subset corresponding to the blank value.

[0236] Aspect 8: The method according to aspect 7, wherein each corresponding default parameter corresponds to a zero code point domain parameter of the corresponding carrier.

[0237] Aspect 9: According to the method of any one of Aspects 5 to 8, the method also includes: filling blank values ​​for the second carrier subset for a given value of the domain by reusing parameters of the second carrier subset associated with other values ​​of the domain.

[0238] Aspect 10: The method according to aspect 9, wherein filling blank values ​​for a given carrier of the second subset of carriers comprises: recursively filling the blank values ​​of the given carrier by reusing parameters for the given carrier associated with other values ​​of the domain.

[0239] Aspect 11: A method according to any one of Aspects 9 to 10, wherein filling blank values ​​for a given carrier of the second carrier subset includes: at least partially based on the first value of the domain of the given carrier sharing one or more common bits with the second value of the domain of the given carrier, using parameters associated with the second value of the domain to fill a first blank value associated with the first value of the domain.

[0240] Aspect 12: According to the method described in any one of Aspects 5 to 11, the method further includes: monitoring a subset of values ​​of the domain in a set of available values ​​of the domain, wherein each value of the subset of values ​​includes a corresponding parameter for each carrier of the carrier set; and conveying the one or more messages based at least in part on the domain of the control message being a value in the subset of values.

[0241] Aspect 13: According to any one of aspects 1 to 12, the method also includes: receiving a radio resource control message, the radio resource control message indicating a number of bits associated with the domain for decoding, wherein the domain size is at least partially based on the number of bits.

[0242] Aspect 14: According to the method described in any one of Aspects 1 to 13, the method further includes: receiving a second control message indicating a change from the one or more parameter sets to a second one or more parameter sets of the carrier set available to the UE.

[0243] Aspect 15: The method according to aspect 14, wherein the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the one or more parameter sets.

[0244] Aspect 16: The method according to aspect 15, further comprising: setting the value of the field associated with the one or more parameter sets and not associated with the second one or more parameter sets to zero.

[0245] Aspect 17: The method according to any one of aspects 14 to 16, wherein the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the one or more parameter sets.

[0246] Aspect 18: The method according to aspect 17, the method further comprising: interpreting entries of the field of the second one or more parameter sets using the number of least significant bits associated with the one or more parameter sets.

[0247] Aspect 19: The method according to any one of aspects 1 to 18, wherein each parameter of the one or more parameter sets comprises BWP or TDRA.

[0248] Aspect 20: A method for wireless communication at a network entity, the method comprising: sending a message indicating one or more parameter sets for a carrier set supported by a UE, the one or more parameter sets indicating communication parameters for communicating via the carrier set; sending a control message via a carrier of the carrier set based at least in part on the message, wherein a domain size associated with a domain of the control message is based at least in part on the one or more parameter sets, wherein corresponding values ​​of the domain indicate corresponding parameter sets of the one or more parameter sets for one or more carriers of the carrier set; and communicating one or more messages via at least one carrier of the carrier set using the corresponding parameter set for the at least one carrier.

[0249] Aspect 21: The method according to aspect 20, the method further comprising: sending a radio resource control message, the radio resource control message indicating a number of bits associated with the domain, wherein the domain size is based at least in part on the number of bits.

[0250] Aspect 22: According to the method described in any one of Aspects 20 to 21, the method also includes: sending a second control message, wherein the second control message indicates a change from the one or more parameter sets of the carrier set available to the UE to a second one or more parameter sets of the carrier set available to the UE.

[0251] Aspect 23: The method according to aspect 22, wherein the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the one or more parameter sets.

[0252] Aspect 24: A method according to any one of aspects 22 to 23, wherein the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the one or more parameter sets.

[0253] Aspect 25: The method according to any one of aspects 20 to 24, wherein each parameter of the one or more parameter sets comprises BWP or TDRA.

[0254] Aspect 26: An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 19.

[0255] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to any one of aspects 1 to 19.

[0256] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 19.

[0257] Aspect 29: An apparatus for wireless communication, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 20 to 25.

[0258] Aspect 30: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to any one of aspects 20 to 25.

[0259] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to any one of aspects 20 to 25.

[0260] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0261] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0262] The information and signals described herein may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0263] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0264] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the functions are implemented at different physical locations.

[0265] Computer-readable medium includes both non-transient computer storage medium and communication medium, including any medium that promotes computer program to be transmitted from one place to another.Non-transient storage medium can be any available medium that can be accessed by general or special-purpose computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage or other magnetic storage device or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by general or special-purpose computer or general or special-purpose processor in the form of instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0266] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items accompanied by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0267] The term "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, and similar actions. Additionally, "determining" may include receiving (such as receiving information), accessing (such as accessing data in a memory), and similar actions. Additionally, "determining" may include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0268] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between the similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label regardless of the second reference label or other subsequent reference labels.

[0269] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples". The specific implementation includes specific details to provide an understanding of the technology. However, the technologies may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0270] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), the method comprising: receiving a message indicating one or more parameter sets for a set of carriers supported by the UE, the one or more parameter sets indicating communication parameters for communicating via the set of carriers; monitoring a field of a control message based at least in part on the message, wherein a field size of the field is based at least in part on the one or more parameter sets, and wherein a respective value of the field indicates a respective one of the one or more parameter sets for one or more carriers of the set of carriers; as well as One or more messages are communicated via at least one carrier of the set of carriers using the respective set of parameters for the at least one carrier.

2. The method of claim 1 , wherein monitoring the domain of the control message comprises: One or more bits of the field of the control message are decoded based at least in part on the field size, wherein the field size is based at least in part on a number of parameters associated with a parameter set of the one or more parameter sets.

3. The method according to claim 2, further comprising: The domain size is determined based at least in part on a carrier of the set of carriers, the carrier being associated with the set of parameters, wherein a number of the parameters is greater than a corresponding number of parameters for each remaining carrier of the set of carriers.

4. The method according to claim 2, further comprising: The domain size is determined based at least in part on a carrier of the set of carriers, the carrier being associated with the set of parameters, wherein the number of parameters is less than a corresponding number of parameters for each remaining carrier of the set of carriers.

5. The method according to claim 1, wherein: each value of the field for a first subset of carriers of the set of carriers indicates at least one corresponding parameter for each carrier of the first subset of carriers, the first subset of carriers comprising the one or more carriers; and Each value of the field for a second subset of carriers is associated with a blank value for each carrier of the second subset of the set of carriers, the second subset of carriers not including the first subset of carriers.

6. The method according to claim 5, further comprising: Based at least in part on the value of the field for a carrier in the second subset of carriers corresponding to the null value, refraining from using the carrier to communicate the one or more messages.

7. The method according to claim 5, further comprising: Based at least in part on the value of the field for each carrier of the second subset of carriers corresponding to the null value, communicating using respective default parameters for each carrier of the second subset of carriers.

8. The method of claim 7, wherein each respective default parameter corresponds to a zero code point domain parameter of the respective carrier.

9. The method according to claim 5, further comprising: The second carrier subset is populated with blank values ​​for a given value of the domain by reusing parameters for the second carrier subset associated with other values ​​of the domain.

10. The method of claim 9, wherein filling blank values ​​for a given carrier of the second subset of carriers comprises: The blank value for the given carrier is recursively filled by reusing parameters for the given carrier associated with other values ​​of the field.

11. The method of claim 9, wherein filling blank values ​​for a given carrier of the second subset of carriers comprises: Based at least in part on the first value of the domain for the given carrier sharing one or more common bits with a second value of the domain for the given carrier, a first blank value associated with the first value of the domain is filled with a parameter associated with the second value of the domain.

12. The method according to claim 5, further comprising: monitoring a subset of values ​​of the domain from a set of available values ​​of the domain, wherein each value of the subset of values ​​comprises a respective parameter for each carrier of the set of carriers; as well as The one or more messages are communicated based at least in part on the field of the control message being a value within the subset of values.

13. The method according to claim 1, further comprising: A radio resource control message is received, the radio resource control message indicating a number of bits associated with the domain for decoding, wherein the domain size is based at least in part on the number of bits.

14. The method according to claim 1, further comprising: A second control message is received, the second control message indicating a change from the one or more sets of parameters to a second one or more sets of parameters available to the set of carriers available to the UE.

15. The method of claim 14, wherein the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the first one or more parameter sets.

16. The method according to claim 15, further comprising: Values ​​of the fields associated with the one or more parameter sets and not associated with the second one or more parameter sets are reset to zero.

17. The method of claim 14, wherein the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the first one or more parameter sets.

18. The method according to claim 17, further comprising: The entries of the field of the second one or more parameter sets are interpreted using the number of least significant bits associated with the one or more parameter sets.

19. The method of claim 1, wherein each parameter of the one or more parameter sets comprises a bandwidth portion or a time domain resource allocation.

20. A method for wireless communication at a network entity, the method comprising: sending a message indicating one or more parameter sets for a set of carriers supported by a user equipment (UE), the one or more parameter sets indicating communication parameters for communicating via the set of carriers; transmitting a control message via a carrier of the set of carriers based at least in part on the message, wherein a field size associated with a field of the control message is based at least in part on the one or more parameter sets, wherein respective values ​​of the fields indicate respective ones of the one or more parameter sets for one or more carriers of the set of carriers; and One or more messages are communicated via at least one carrier of the set of carriers using the respective set of parameters for the at least one carrier.

21. The method according to claim 20, further comprising: A radio resource control message is sent, the radio resource control message indicating a number of bits associated with the domain, wherein the domain size is based at least in part on the number of bits.

22. The method according to claim 20, further comprising: A second control message is sent, the second control message indicating a change from the one or more sets of parameters for the set of carriers available to the UE to a second set of one or more parameters for the set of carriers available to the UE.

23. The method of claim 22, wherein the number of bits associated with the field of the second one or more parameter sets is less than the number of bits associated with the field of the first one or more parameter sets.

24. The method of claim 22, wherein the number of bits associated with the field of the second one or more parameter sets is greater than the number of bits associated with the field of the first one or more parameter sets.

25. The method of claim 20, wherein each parameter of the one or more parameter sets comprises a bandwidth portion or a time domain resource allocation.

26. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a message indicating one or more parameter sets for a set of carriers supported by a user equipment (UE), the one or more parameter sets indicating communication parameters for communicating via the set of carriers; monitoring a field of a control message based at least in part on the message, wherein a field size of the field is based at least in part on the one or more parameter sets, and wherein a respective value of the field indicates a respective one of the one or more parameter sets for one or more carriers of the set of carriers; as well as One or more messages are communicated via at least one carrier of the set of carriers using the respective set of parameters for the at least one carrier.

27. The apparatus of claim 26, wherein the instructions for monitoring the field of the control message are executable by the processor to cause the apparatus to: One or more bits of the field of the control message are decoded based at least in part on the field size, wherein the field size is based at least in part on a number of parameters associated with a parameter set of the one or more parameter sets.

28. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: The domain size is determined based at least in part on a carrier of the set of carriers, the carrier being associated with the set of parameters, wherein a number of the parameters is greater than a corresponding number of parameters for each remaining carrier of the set of carriers.

29. The apparatus of claim 27, wherein the instructions are further executable by the processor to cause the apparatus to: The domain size is determined based at least in part on a carrier of the set of carriers, the carrier being associated with the set of parameters, wherein the number of parameters is less than a corresponding number of parameters for each remaining carrier of the set of carriers.

30. An apparatus for wireless communication, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending a message indicating one or more parameter sets for a set of carriers supported by a user equipment (UE), the one or more parameter sets indicating communication parameters for communicating via the set of carriers; transmitting a control message via a carrier of the set of carriers based at least in part on the message, wherein a field size associated with a field of the control message is based at least in part on the one or more parameter sets, wherein respective values ​​of the fields indicate respective ones of the one or more parameter sets for one or more carriers of the set of carriers; and One or more messages are communicated via at least one carrier of the set of carriers using the respective set of parameters for the at least one carrier.