Scheduled cell identification for multi-cell scheduling

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive multi-cell downlink control information (MC-DCI), which may be scheduled for communications for more than one scheduled cell via a scheduling cell. The overhead of DCI (e.g., MC-DCI) may be reduced by compressing or removing a carrier indication field (CIF). For example, radio resource control signaling may indicate to the UE a DCI payload size, a control channel element (CCE), and / or a physical downlink control channel (PDCCH) candidate for each scheduled cell or each group of scheduled cells. If the DCI payload size, CCE, and / or PDCCH candidate are different for scheduled cells indicated in the radio resource control message, the UE may determine to which scheduled cell (s) the DCI received in the PDCCH monitoring occasion applies based on the payload size and / or CCE of the PDCCH monitoring occasion without using CIF.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 883,560, filed by Takeda et al. on August 8, 2022, entitled “SCHEDULED CELLIDENTIFICATION FOR MULTI-CELL SCHEDULING,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Background Art

[0003] The following relates to wireless communications related to scheduled cell identities for multi-cell scheduling. 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 communications 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 communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for supporting scheduled cell identification for multi-cell scheduling. For example, the described technology provides multi-cell downlink control information (MC-DCI) with reduced overhead. A user equipment (UE) may receive MC-DCI via a scheduling cell, which may schedule communications for more than one scheduled cell. Since MC-DCI conveys more information than a single-cell DCI in order to schedule communications on multiple cells, the overhead of MC-DCI may increase compared to a single-cell DCI. The overhead of DCI can be reduced by compressing or removing a carrier indication field (CIF). For example, radio resource control (RRC) signaling may indicate to the UE the DCI payload size, control channel element (CCE) and / or physical downlink control channel (PDCCH) candidates for each scheduled cell or each scheduled cell group. If the DCI payload size, CCE and / or PDCCH candidate are different for the scheduled cells indicated in the RRC message, the UE can determine which (which) scheduled cells the DCI received in the PDCCH monitoring opportunity applies to based on the payload size and / or CCE of the PDCCH monitoring opportunity without using the CIF field. In some aspects, if the DCI payload size, CCE and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE can determine the scheduled cell for the PDCCH monitoring opportunity based on one or more configured rules without using the CIF. In some aspects, if the DCI payload size, CCE and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE can determine the corresponding scheduled cell or scheduled cell group based on determining the radio network temporary identifier (RNTI) for scrambling the cyclic redundancy check (CRC) for the PDCCH monitoring opportunity without using the CIF and matching the RNTI with the scheduled cell or scheduled cell group.

[0005] A method for wireless communication at a first network node is described. The method may include: receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and receiving DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0006] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to: receive control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; determine a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and receive DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0007] Another apparatus for wireless communication at a first network node is described. The apparatus may include: a component for receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; a component for determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and a component for receiving DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0008] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network node, causes the network node to receive control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, determine a DCI format for a downlink control channel monitoring opportunity in the scheduling cell, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and receive DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0009] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on the third comparison information.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on a payload size of the downlink control channel monitoring opportunity that matches a corresponding DCI payload size of the scheduled cell subset.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on a CCE set for the downlink control channel monitoring opportunity that matches a corresponding CCE set for the scheduled cell subset.

[0012] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0013] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that the corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the rule-based indication includes information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or a number of cells associated with the scheduled cell subset.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a cyclic redundancy check for the downlink control channel monitoring opportunity.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling also includes an indication of an association between a respective radio network identifier and each of the scheduled cell subsets.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI includes scheduling information for communicating with one or more of the scheduled cell subset.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling also includes an indication of a corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells and the determination of the scheduling information can be based on the indication of the corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for comparing the respective DCI payload sizes and generating the first comparison information based on the comparison of the respective DCI payload sizes.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for comparing the respective sets of CCEs and generating the second comparison information based on the comparison of the respective CCEs.

[0021] A method for wireless communication at a first network node is described. The method may include: sending control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the downlink control channel format includes the absence or presence of an indication of the scheduled cell subset; and sending DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0022] A first network node for wireless communication is described. The first network node may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to cause the device to send control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, determine a DCI format for a downlink control channel monitoring opportunity in the scheduling cell, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the downlink control channel format includes the absence or presence of an indication of the scheduled cell subset; and send DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0023] Another apparatus for wireless communication at a first network node is described. The apparatus may include: means for sending control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; means for determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and means for sending DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0024] A non-transitory computer-readable medium having stored thereon code for wireless communication is described. The code, when executed by a first network node, causes the network node to send control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, determine a DCI format for a downlink control channel monitoring opportunity in the scheduling cell, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the downlink control channel format includes the absence or presence of an indication of the scheduled cell subset; and send DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0025] In some examples of methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on the third comparison information.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on a payload size of the downlink control channel monitoring opportunity that matches a corresponding DCI payload size of the scheduled cell subset.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, determining the DCI format may include operations, features, components, or instructions for determining the DCI format based on a CCE set for the downlink control channel monitoring opportunity that matches a corresponding CCE set for the scheduled cell subset.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0029] Some examples of the methods, devices, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that the corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the rule-based indication includes information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or a number of cells associated with the scheduled cell subset.

[0031] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the DCI includes the presence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets may be equal and also based on the second comparison information indicating that corresponding CCE sets for the at least two scheduled cell subsets may be equal, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a cyclic redundancy check for the downlink control channel monitoring opportunity.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling also includes an indication of an association between a respective radio network identifier and each of the scheduled cell subsets.

[0033] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the DCI includes scheduling information for communicating with one or more of the scheduled cell subset.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the control signaling also includes an indication of a corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells and the determination of the scheduling information can be based on the indication of the corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells.

[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for comparing the respective DCI payload sizes and generating the first comparison information based on the comparison of the respective DCI payload sizes.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for comparing the respective sets of CCEs and generating the second comparison information based on the comparison of the respective CCEs. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 2 An example of a scheduling map supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0039] Figure 3 An example of a scheduling map supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0040] Figure 4 An example of a wireless communication system supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 5 An example of a resource map supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated.

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

[0043] Figure 7 and Figure 8 A block diagram of a device supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is shown.

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

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

[0046] Fig.11 and Fig.12 A block diagram of a device supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is shown.

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

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

[0049] Figure 15 to Figure 16 A flow chart illustrating a method of supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0050] Some wireless communications may implement cross-carrier scheduling, where downlink control information (DCI) received via a physical downlink control channel (PDCCH) opportunity on a scheduling cell schedules communications for different cells (scheduled cells). Cross-carrier DCI may include an indication of the scheduled cell in a carrier indication field (CIF). Some wireless communication systems may support multi-cell DCI (MC-DCI), which means that a single DCI received via a scheduling cell may schedule communications for more than one scheduled cell. Since MC-DCI conveys more information than single-cell DCI in order to schedule communications on multiple cells, the overhead of MC-DCI may increase compared to single-cell DCI.

[0051] The overhead of DCI can be reduced by compressing or removing CIF. For example, radio resource control (RRC) signaling may indicate to the user equipment (UE) the DCI payload size, control channel element (CCE) and / or PDCCH candidate for each scheduled cell or each scheduled cell group. If the DCI payload size, CCE and / or PDCCH candidate are different for the scheduled cells indicated in the RRC, the UE can determine which (which) scheduled cells the DCI received in the PDCCH monitoring opportunity applies to based on the payload size and / or CCE of the PDCCH monitoring opportunity without using the CIF field. Therefore, the size of the DCI can be reduced by removing the CIF field.

[0052] In some aspects, if the DCI payload size, CCE, and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE may determine the scheduled cell for the PDCCH monitoring opportunity based on one or more configured rules without using the CIF. For example, if the DCI payload size, CCE, and PDCCH monitoring opportunity match two or more scheduled cells or scheduled cell groups, the UE may determine that the PDCCH monitoring opportunity corresponds to a scheduled cell with a lower / higher component carrier index, a lower / higher subcarrier spacing (SCS), a scheduled cell group including a primary cell, a scheduled cell group including a scheduling cell, or a cell group including the largest / least number of cells.

[0053] In some aspects, if the DCI payload size, CCE, and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE can determine the corresponding scheduled cell or scheduled cell group based on determining a radio network temporary identifier (RNTI) used to scramble a cyclic redundancy check (CRC) for a PDCCH monitoring opportunity and matching the RNTI with the scheduled cell or scheduled cell group without using a CIF.

[0054] 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 scheduling diagrams, resource 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 involving scheduled cell identities for multi-cell scheduling.

[0055] Figure 1 An example of a wireless communication system 100 supporting scheduled cell identification 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 aspects, 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).

[0056] 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 aspects, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, etc. In some aspects, 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) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0057] 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 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 capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0058] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, apparatus, device, computing system, etc. may include disclosure of UE, base station, apparatus, device, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first apparatus, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0059] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0060] 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 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.

[0061] In some aspects, the network entities 105 may communicate with the core network 130, or 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 aspects, the network entities 105 may communicate with each other via the backhaul communication links 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 aspects, the network entities 105 may communicate with each other via the midhaul communication links 162 (e.g., according to the midhaul interface protocol) or the fronthaul communication links 168 (e.g., according to the fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, the midhaul communication links 162, or the fronthaul communication links 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), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0062] 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 terminology). In some aspects, 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).

[0063] In some aspects, 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, an intelligent 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 aspects, 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)).

[0064] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions, 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, or RU 170. For example, a functional split of a protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of a protocol stack and DU 165 can support one or more different layers of a protocol stack. In some aspects, CU 160 can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., 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 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., open fronthaul (FH) interface). In some aspects, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to an interface (eg, a channel) between layers of a protocol stack supported by respective network entities 105 communicating via such communication links.

[0065] In some wireless communication systems (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 the 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 host entities or IAB hosts. 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 host network entity 105 (e.g., a host base station 140). One or more host network entities 105 (e.g., IAB hosts) may communicate with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the DU 165 of the coupled IAB host. 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 aspects, 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 cases, 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.

[0066] For example, an access network (AN) or RAN may include an access node (e.g., an IAB host), communications between an IAB node 104, and one or more UEs 115. The IAB host may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB host may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB host may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB host and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1 AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CU 160 associated with an alternative IAB host) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0067] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). The DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB host may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB host may relay for UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

[0068] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child node associated with the IAB host, or both. The IAB host may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB host may relay the transmission to the UE 115 via the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB host may signal the establishment of a communication link to the IAB node 104 via the F1 interface, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB host to the UE 115) via the DU 165. That is, data may be relayed to and from the IAB node 104 via signaling via the NR Uu interface of the MT to the IAB node 104. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB host, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

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

[0070] 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 aspects, UE 115 may include or 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 appliances or vehicles, meters, etc.

[0071] 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, relay base stations, etc. Figure 1as shown in .

[0072] 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) using resources associated with one or more carriers. The term "carrier" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting 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 bandwidth portion (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) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices 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 a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0073] In some aspects, 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 identified according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by a 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).

[0074] 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, among other transmission configurations. A carrier may carry either downlink communications or uplink communications (e.g., in an FDD mode), or may be configured to carry both downlink communications and uplink communications (e.g., in a TDD mode).

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

[0076] The signal waveform transmitted via 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 using MCM technology, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high rate of communication. Wireless communication resources may refer to a combination of RF spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0077] One or more parameter sets for a carrier may be supported, and 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 aspects, a UE 115 may be configured with multiple BWPs. In some aspects, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to one or more active BWPs.

[0078] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, for which Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each 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).

[0079] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some aspects, a 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 appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0080] A subframe, slot, mini-slot, or 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 aspects, 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)).

[0081] According to various techniques, physical channels may be multiplexed using carriers for communication. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, 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 of a carrier or a subset of that system bandwidth. 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 for a control channel candidate may refer to the number of control channel resources (e.g., CCEs) associated with the 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 .

[0082] 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., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other cell identifier) ​​used to distinguish adjacent cells. In some aspects, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which a 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 may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0083] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to a UE 115 that has a service subscription 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) than a macro cell, and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that has a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user 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 via one or more cells.

[0084] In some aspects, 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.

[0085] In some aspects, 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 aspects, 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.

[0086] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timings, and in some aspects, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0087] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a network entity 105 (e.g., base station 140) without human intervention. In some aspects, M2M communication or MTC may include communication from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, health care monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0088] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some aspects, half-duplex communication may be performed at a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

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

[0090] In some aspects, a UE 115 may be configured to support communication directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some aspects, 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 (e.g., scheduled) by the network entity 105. In some aspects, one or more UEs 115 in such a group may be outside of the coverage area 110 of the network entity 105, or may otherwise be unable or not configured to receive transmissions from the network entity 105. In some aspects, 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 other UE 115 in the group. In some aspects, network entity 105 may facilitate scheduling of resources for D2D communications. In some other examples, D2D communications may be performed between UEs 115 without involving network entity 105.

[0091] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some aspects, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these items. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some aspects, the vehicles in the V2X system can communicate with roadside infrastructure such as roadside units, or communicate with the network using vehicle-to-network (V2N) communication via one or more network nodes (e.g., network entity 105, base station 140, RU 170), or communicate with both.

[0092] 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 transferred via a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of 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.

[0093] 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). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about one decimeter to one meter in length. 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. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using lower frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0094] The wireless communication system 100 may also operate using a super high frequency (SHF) region (also known as a centimeter band) that may be in the range of 3 GHz to 30 GHz or an extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as a millimeter band) using a spectrum. In some aspects, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and network entity 105 (e.g., base station 140, RU170), and the EHF antenna of the corresponding device may be smaller and more closely spaced than the UHF antenna. In some aspects, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and shorter range than SHF or UHF transmissions. The technology disclosed herein may be adopted across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may differ by country or regulatory agency.

[0095] The wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 may employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 may employ carrier sensing for conflict detection and avoidance. In some aspects, operations performed using unlicensed bands may be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0096] The network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, 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 assembly, such as an antenna tower. In some aspects, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include 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.

[0097] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such technology may be referred to as spatial multiplexing. Multiple signals may be, for example, sent by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include single-user MIMO (SU-MIMO), in which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), in which multiple spatial layers are sent to multiple devices.

[0098] 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 along 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 orientation (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other orientation).

[0099] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0100] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as a receiving network entity 105 or a receiving UE 115)). In some aspects, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted along one or more beam directions. For example, UE 115 may receive one or more of the signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0101] In some aspects, transmission by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from the network entity 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may be precoded or non-precoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0102] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some aspects, a receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0103] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0104] UE 115 and network entity 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using CRC), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some aspects, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0105] The wireless communication system 100 can implement cross-carrier scheduling and / or multi-cell scheduling by a single DCI (e.g., MC-DCI). The overhead of DCI can be reduced by compressing or removing CIF. For example, RRC can indicate the DCI payload size, CCE and / or PDCCH candidates for each scheduled cell or each scheduled cell group to UE 115. If the DCI payload size, CCE and / or PDCCH candidates are different for the scheduled cells indicated in the RRC signaling, UE 115 can determine which (which) scheduled cells the DCI received in the PDCCH monitoring opportunity is applied to based on the payload size and / or CCE of the PDCCH monitoring opportunity without using the CIF field. Therefore, the size of DCI can be reduced by removing the CIF field.

[0106] In some aspects, if the DCI payload size, CCE, and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE 115 may determine the scheduled cell for the PDCCH monitoring opportunity based on one or more configured rules without using the CIF. For example, if the DCI payload size, CCE, and PDCCH monitoring opportunity match two or more scheduled cells or scheduled cell groups, the UE 115 may determine that the PDCCH monitoring opportunity corresponds to a scheduled cell with a lower / higher component carrier index, a lower / higher SCS, a scheduled cell group including a primary cell, a scheduled cell group including a scheduling cell, or a cell group including the largest / least number of cells.

[0107] In some aspects, if the DCI payload size, CCE, and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE 115 can determine the corresponding scheduled cell or scheduled cell group based on determining the RNTI used to scramble the CRC for the PDCCH monitoring opportunity and matching the RNTI with the scheduled cell or scheduled cell group without using the CIF.

[0108] Figure 2 An example of a scheduling diagram 200 supporting scheduled cell identification for multi-cell scheduling in accordance with one or more aspects of the present disclosure is illustrated. In some aspects, the scheduling diagram 200 can implement aspects of the wireless communication system 100.

[0109] In self-scheduling mode, the DCI received in the PDCCH opportunity via a carrier includes scheduling information for data communication of the carrier. The RRC message may indicate the number of blind decoding (BD) capabilities and the number of CCEs that the UE can process per PDCCH opportunity. The RRC may indicate up to 6 different DCI formats (e.g., 4 of 0_0, 1_0, 1_1, 0_2, and 1_2) for a given PDCCH opportunity and the UE may process up to 3 DCI formats of payload size for a cell-RNTI (C-RNTI) and 1 DCI payload size for other RNTIs of the cell.

[0110] In the cross-carrier scheduling mode, as shown in the scheduling diagram 200, carriers are used to schedule data communications on different carriers. For example, in the PDCCH opportunity 205, the first DCI 210-a can schedule data communication 215-a on the first carrier (e.g., cell), the second DCI 210-b can schedule data communication 215-b on the second carrier, and the third DCI 210-c can schedule data communication 215-c on the third carrier. The RRC message can indicate the number of BD capabilities and the number of CCEs that the UE can process per PDCCH opportunity. The RRC can indicate up to 6 different DCI formats (e.g., 4 of 0_0, 1_0, 1_1, 0_2, and 1_2) for a given PDCCH opportunity and the UE can process up to 3 DCI formats of payload sizes for the C-RNTI and 1 DCI payload size for other RNTIs of the scheduled cell. Parameter n ci Distinguish the DCI for the scheduled cell (eg, the first DCI 210-a, the second DCI 210-b, or the third DCI 210-c). ci Used to distinguish which DCI is associated with which scheduled cell.

[0111] Cross-carrier scheduling can be configured by the RRC field CrossCarrierSchedulingConfig, which can be configured for each scheduled cell. If CrossCarrierSchedulingConfig is configured with the parameter "other", it indicates to the UE that the scheduled cell is configured for cross-carrier scheduling. The CrossCarrierSchedulingConfig field can provide which cell is the scheduling cell and the CIF / n associated with the scheduled cell. ci For example, the field schedulingCellID may indicate a serving cell index to indicate a scheduling cell and the field cif-InSchedulingCell may indicate a CIF / n associated with a scheduled cell. ci .

[0112] A given PDCCH opportunity may include the number of CCEs, and n ci It can indicate which CCEs to monitor for a given scheduled cell. For example, for a search space set s associated with a control resource set (CORESET) p, in the search space set s for the carrier indicator field value n CI The time slot of the corresponding serving cell's active DL BWP PDCCH candidates for the search space set The corresponding CCE index of aggregation level L is given by Formula 1, where for any common search space (CSS), For UE-specific search space (USS), Y p,-1 =n RNTI ≠0, pmod3=0, A p =39827, pmod3 = 1, A p =39829, pmod3 = 2, A p =39839, and D = 65537; i = 0, ..., L-1; N CCE,p is the number of CCEs in CORESETp, numbered from 0 to N CCE,p -1 and, if available, for each resource block (RB) set; if the UE is configured with the carrier indicator field via the CrossCarrierSchedulingConfig of the serving cell on which it monitors the PDCCH, then n CI is the Carrier Indicator field value; otherwise, including for any CSS, n CI =0; in The UE is configured for use with n CIThe number of PDCCH candidates monitored for the aggregation level L of the search space set s of the corresponding serving cell; for any CSS, For USS, are all configurations n of CCE aggregation level L for search space set s CI Worth The maximum value of .

[0113]

[0114] For cross-carrier scheduling, although the UE monitors the PDCCH on the same scheduling cell for multiple scheduled cells, the CCEs of PDCCH candidates for different scheduled cells may not overlap (as long as there are sufficient number of CCEs in the CORESET). For example, Table 1 below shows the CCEs of PDCCH candidates for a CORESET with n ci = 0, 1 and 2, respectively, with 96 CCEs, L = 4 and M = 4, and where Y p =0.

[0115] Table 1

[0116]

[0117] Figure 3 An example of a scheduling diagram 300 supporting scheduled cell identification for multi-cell scheduling in accordance with one or more aspects of the present disclosure is illustrated. In some aspects, the scheduling diagram 300 can implement aspects of the wireless communication system 100.

[0118] The MC-DCI 310 received in the PDCCH opportunity 305 may schedule communications on more than one cell (e.g., transmitted via a physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH)) via the same MC-DCI 310. For example, the MC-DCI 310 may schedule a first communication 315-a on a first cell, a second communication 315-b on a second cell, and a third communication 315-c on a third cell. The RRC message may indicate the number of BD capabilities and the number of CCEs that the UE can process per PDCCH opportunity. The MC-DCI may be implemented in intra-band or inter-band carrier aggregation operations. The MC-DCI may be implemented in frequency range 1 (FR1) or frequency range 2 (FR2). In some aspects, a single MC-DCI may be used for 3 or more cells for multi-cell PUSCH and / or PDSCH scheduling.

[0119] Before the UE decodes a PDCCH candidate, the UE can determine whether the PDCCH candidate is for MC-DCI or single-cell DCI. ciThe framework can be used to indicate whether the PDCCH candidate is being used for MC-DCI or single-cell DCI. For example, RRC can configure CIF / n ci The association between the value and the set of cells that can be scheduled by MC-DCI. For example, in Table 2 below, CIF / n ci The value 2 is configured to be associated with cells 2, 3, and 4 (eg, indicating MC-DCI for cells 2, 3, and 4), CIF / n ci The value 1 is configured to be associated with cell 1 (eg, indicating a single-cell DCI for cell 1), and CIF / n ci The value 0 is configured to be associated with cell 0 (e.g., indicating a single-cell DCI for cell 0). Therefore, in the scenario shown in Table 2, when the MC-DCI has cells 2, 3, and 4 as co-scheduled cells, the MC-DCI has a CIF field indicating a value of 2. For example, Table 2 shows that for a cell with n ci = 0, 1 and 2 (where the value 2 is associated with cells 2, 3 and 4) with 96 CCEs, L = 4 and M = 4, and where Y p =0.

[0120] Table 2

[0121]

[0122] Figure 4 An example of a wireless communication system 400 that supports scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. The wireless communication system 400 may implement aspects of the wireless communication system 100. The wireless communication system 400 may include a UE 115-a, which may be an example of a UE 115 as described herein. The wireless communication system 400 may include a network entity 105-a, which may be an example of a network entity 105 as described herein.

[0123] UE 115-a may communicate with network entity 105-a using communication link 125-a, which may be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a may include a bidirectional link that enables both uplink and downlink communications. For example, UE 115-a may use communication link 125-a to send uplink transmissions 405, such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a may use communication link 125-a to send downlink transmissions 410, such as downlink control signals or downlink data signals, to UE 115-a.

[0124] As described herein, the wireless communication system 400 may implement multi-cell scheduling using a single DCI 430. For example, the DCI 430 received via the scheduling cell 415 may schedule communications (e.g., downlink communications 435-a or uplink communications 435-b) with one or more of the scheduling cell 415, the first cell 420-a, the second cell 420-b, the third cell 420-c, the fourth cell 420-d, the fifth cell 420-e, the sixth cell 420-f, the seventh cell 420-g, or the eighth cell 420-h.

[0125] Since MC-DCI conveys more information than single-cell DCI in order to schedule communications on multiple cells, the overhead of MC-DCI may be higher than that of single-cell DCI. In order to compress the overhead of MC-DCI, the CIF field may be compressed or removed. However, in some example wireless communication systems, CIF is configured to always be included in the scheduling DCI 430 so that UE115-a can determine which (which) scheduled cells the DCI 430 corresponds to. However, other means may be used to distinguish whether the DCI 430 decoded on the CCE set is for a specific scheduled cell without using CIF, and therefore, in some aspects, the CIF field may not be used (e.g., may be removed from DCI 430).

[0126] For example, the RRC signaling 425 may indicate the payload size, CCE, and / or PDCCH timing associated with different DCI formats for different cells or subsets of scheduled cells (e.g., one or more of the scheduling cell 415, the first cell 420-a, the second cell 420-b, the third cell 420-c, the fourth cell 420-d, the fifth cell 420-e, the sixth cell 420-f, the seventh cell 420-g, or the eighth cell 420-h). For example, if the payload sizes of the DCI formats for different sets of scheduled cells are different, the UE 115-a may identify which scheduled cell(s) the decoded DCI 430 is for based on a CRC check of multiple assumptions of the DCI size. As another example, if the CCE sets of PDCCH candidates for different scheduled cells are different, the UE 115-a may identify which scheduled cell(s) the decoded DCI 430 is for based on the CCE to which each PDCCH candidate is mapped. In other words, in some aspects, the CIF field may be used to identify scheduled cells when: (1) the payloads of the DCI formats for different scheduled cells are the same; and (2) the CCE sets of PDCCH candidates for different scheduled cells are the same.

[0127] Thus, in some aspects, the CIF field may be used to identify a scheduled cell in the following situations: (1) the UE is configured to monitor two or more DCI formats on the same scheduling cell, which DCI formats are configured to schedule PDSCH or PUSCH on different scheduled cells (sets) and the payload / size of the two or more DCI formats of the different scheduled cells (sets) is the same; and (2) the UE is configured to decode a PDCCH candidate for one of the two or more DCI formats on a CCE set and decode another PDCCH candidate for another of the two or more DCI formats on the same CCE set on the same scheduling cell. Conditions (1) and (2) may be controlled via configuration in RRC signaling 425, and whether these conditions are met may be identified by UE 115-a (and in some aspects by network entity 105-a) through these configurations. For example, the DCI payload size may depend on various parameters in fields PDSCH-Config, PUCCH-Config, or PUSCH-Config in RRC signaling 425. The set of CCEs used for the PDCCH candidate may depend on parameters in field PDCCH-Config in RRC signaling 425. In some aspects, UE 115-a (and in some aspects, network entity 105-a) may compare DCI payload sizes associated with different scheduled cells to generate payload size comparison information to determine whether condition (1) is met. In some aspects, UE 115-a (and in some aspects, network entity 105-a) may compare CCEs associated with PDCCH candidates for different DCI formats to generate CCE comparison information to determine whether condition (2) is met.

[0128] In some aspects, the CIF field may be used to identify a scheduled cell in the following situations: (1) the UE is configured to monitor two or more DCI formats on the same scheduling cell, the DCI formats being configured to schedule PDSCH or PUSCH on different scheduled cells (sets) and the payload / size of the two or more DCI formats of the different scheduled cells (sets) being the same; (2) the UE is configured to decode a PDCCH candidate for one of the two or more DCI formats on a CCE set and another PDCCH candidate for another of the two or more DCI formats on the same CCE set on the same scheduling cell; and (3) the PDCCH candidates for the two or more DCI formats are monitored at the same PDCCH monitoring opportunity. Conditions (1), (2), and (3) may be controlled via configuration in RRC signaling 425, and whether these conditions are met may be identified by UE 115-a (and in some aspects by network entity 105-a) through these configurations. The PDCCH monitoring opportunity can be configured in the field PDCCH-Config in the RRC signaling 425. Figure 5 As illustrated, due to condition (3), if PDCCH candidates are monitored with different periodicities for different DCI formats, when condition (3) is met, the CIF field may be included in DCI 430 at the PDCCH monitoring opportunity, but when condition (3) is not met, the CIF field may not be included in another DCI 430.

[0129] In some aspects, the CIF may not be included in the DCI 430 even when (e.g., at least for MC-DCI) conditions (1) and (2) are satisfied (and in some aspects, condition (3) is satisfied). For example, the UE 115-a (and the network entity 105-a) may apply one or more rules to determine which scheduled cell(s) the DCI 430 in the PDCCH monitoring opportunity applies to. For example, if the DCI payload size, CCE, and PDCCH monitoring opportunity match two or more scheduled cells or scheduled cell groups, the UE 115 (and the network entity 105-a) may determine that the PDCCH monitoring opportunity corresponds to a scheduled cell with a lower / higher component carrier index, a lower / higher SCS, a scheduled cell group including a primary cell, a scheduled cell group including the scheduling cell 415, or a cell group including the largest / least number of cells.

[0130] In some aspects, if the DCI payload size, CCE, and PDCCH candidates for two or more scheduled cells or scheduled cell groups are the same, the UE 115-a (and the network entity 105-a) can determine the corresponding scheduled cell or scheduled cell group based on determining the RNTI for scrambling the CRC parity bits for the PDCCH monitoring opportunity and matching the RNTI with the scheduled cell or scheduled cell group without using the CIF. For example, the UE 115-a can be configured with a UE-specific (virtual) RNTI value for scrambling the CRC of the PDCCH (e.g., via RRC signaling 425). If conditions (1) and (2) (or conditions (1), (2), and (3)) are met, the UE 115-a can check both the legacy RNTI (e.g., C-RNTI, configured scheduling RNTI (CS-RNTI), modulation and coding scheme cell RNTI (MCS-C-RNTI)) and the additional UE-specific (virtual) RNTI. Depending on which RNTI is used to scramble the CRC, the UE 115 - a may identify which DCI format is used in the PDCCH monitoring occasion (and accordingly, which scheduled cell(s) the DCI 430 applies to). The RRC signaling 425 may configure the association between the DCI format and the additional UE-specific virtual RNTI.

[0131] In some aspects, the n used in Equation 1 to determine which CCEs correspond to which DCI formats (and therefore which scheduled cells) ci The value may be independent of the CIF field in the DCI 430, for example, because the DCI 430 may not include a CIF field. The n value of each scheduled cell or scheduled cell group may be indicated in the RRC signaling 425. ci If a CIF field is present in DCI 430, the CIF field is consistent with n for the scheduled cell or scheduled cell group. ci The values ​​match.

[0132] In some aspects, the term DCI format 0_X may be used to schedule MC-DCI for multiple PUSCHs on multiple cells (one PUSCH per cell). In some aspects, the term DCI format 1_X may be used to schedule MC-DCI for multiple PDSCHs on multiple cells (one PDSCH per cell). Different transport blocks (TBs) may be scheduled on different cells by DCI with DCI format 0_X or DCI format 1_X. In some aspects, fallback DCI (e.g., DCI formats 0_0 and 1_0) may not support multi-cell scheduling. In some aspects, DCI from multi-cell scheduling may be monitored only in a USS set. In some aspects, PDSCH may not be scheduled by DCI with DCI format 0_X. In some aspects, PUSCH may not be scheduled by DCI with DCI format 1_X. In some aspects, all cells and scheduling cells in a cell co-scheduled by DCI with DCI format 1_X may be included in the same physical uplink control channel (PUCCH) group. In some aspects, all cells in a cell co-scheduled by a DCI with DCI format 0_X and the scheduling cell may be included in the same cell or PUCCH group. In some aspects, a DCI with DCI format 0-X or 1-X on a scheduling cell may be used to schedule PUSCH or PDSCH on multiple cells including the scheduling cell. In some aspects, a DCI with DCI format 0-X or 1-X on a scheduling cell may be used to schedule PUSCH or PDSCH on multiple cells not including the scheduling cell. In some aspects, for UE 115-a, the maximum number of cells scheduled by a DCI with DCI format 0_X may be the same as or different from the maximum number of cells scheduled by a DCI with DCI format 1_X.

[0133] In some aspects, a value for the maximum number of co-scheduled cells scheduled by DCI with DCI format 0_X may be selected from {3, 4, 8}. In some aspects, a value for the maximum number of co-scheduled cells scheduled by DCI with DCI format 0_X may be less than or equal to {3, 4, 8}. In some aspects, a value for the maximum number of co-scheduled cells scheduled by DCI with DCI format 1_X may be selected from {3, 4, 8}. In some aspects, a value for the maximum number of co-scheduled cells scheduled by DCI with DCI format 1_X may be less than or equal to {3, 4, 8}.

[0134] In some aspects, DCI format 0_X may be used for single cell PUSCH scheduling. In some aspects, DCI format 1_X may be used for single cell PDSCH scheduling. UE 115-a may monitor one or both of multi-cell scheduling DCI and single cell scheduling DCI for scheduled cells. In some aspects, DCI with DCI format 0_X or 1_X is sent via the primary cell. In some aspects, at least when DCI with DCI format 0_X or 1_X does not schedule PUSCH or PDSCH on the primary cell, DCI with DCI format 0_X or 1_X is sent via the secondary cell.

[0135] Figure 5 An example of a resource map 500 supporting scheduled cell identification for multi-cell scheduling in accordance with one or more aspects of the present disclosure is illustrated. In some aspects, the resource map 500 can implement aspects of the wireless communication system 100 or 400.

[0136] A first PDCCH candidate of DCI format X scheduling PDSCH or PUSCH on cell set A may be monitored on each time slot (e.g., in PDCCH monitoring opportunity 505-a in time slot 0, in PDCCH monitoring opportunity 505-b in time slot 1, in PDCCH monitoring opportunity 505-c in time slot 2, and in PDCCH monitoring opportunity 505-d in time slot 3). A second PDCCH candidate of DCI format Y scheduling PDSCH on cell set B may be monitored on every other time slot (e.g., in PDCCH monitoring opportunity 505-a in time slot 0 and in PDCCH monitoring opportunity 505-c in time slot 2). If both DCI formats X and Y are associated with CCE 4, CCE 5, CCE 6, and CCE 7, and both have the same DCI payload size, UE 115 may determine that the DCI received in PDCCH monitoring opportunity 505-b and the DCI received in PDCCH monitoring opportunity 505-d schedule PDSCH or PUSCH on cell set A without using CIF, because PDCCH monitoring opportunity 505-b and PDCCH monitoring opportunity 505-d are not configured for DCI format Y. However, for PDCCH monitoring opportunity 505-a and PDCCH monitoring opportunity 505-c, CIF may be used to indicate whether the DCI in PDCCH monitoring opportunity 505-a and PDCCH monitoring opportunity 505-c schedules PDSCH or PUSCH on cell set A or cell set B (e.g., whether the DCI has DCI format X or DCI format Y).

[0137] Figure 6An example of a process flow 600 for supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is illustrated. The process flow 600 may include a UE 115-b, which may be an example of a UE 115 as described herein. The process flow 600 may include a network entity 105-b, which may be an example of a network entity 105 as described herein. In the following description of the process flow 600, operations between the network entity 105-b and the UE 115-b may be sent in an order different from the example order shown, or operations performed by the network entity 105-b and the UE 115-b may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 600, and other operations may be added to the process flow 600.

[0138] At 605, UE 115-b may receive control signaling from network entity 105-b, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with the scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset.

[0139] At 610, the UE 115-b (and in some aspects, the network entity 105-b) may determine a DCI format for scheduling downlink control channel monitoring opportunities in the cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set. The DCI format is associated with a scheduled cell subset of the scheduled cell set, and the DCI format includes the absence or presence of an indication of the scheduled cell subset.

[0140] At 615 , the UE 115 - b may receive DCI from the network entity 105 - b via a DCI monitoring opportunity according to the determined DCI format.

[0141] In some aspects, the control signaling also includes an indication of a corresponding set of downlink control channels for each scheduled cell subset, and the third comparison information corresponds to the corresponding set of downlink control channels. The UE 115-b (and in some aspects, the network entity 105-b) may determine the DCI format based on the third comparison information.

[0142] In some aspects, the first comparison information indicates that each respective DCI payload size of each scheduled cell subset is different.Determining the DCI format may include determining the DCI format based on a payload size of a downlink control channel monitoring occasion that matches a respective DCI payload size of the scheduled cell subset.

[0143] In some aspects, the second comparison information indicates that each respective set of CCEs for each scheduled cell subset is different.Determining the DCI format may include determining the DCI format based on a set of CCEs for downlink control channel monitoring opportunities that matches a respective set of CCEs for the scheduled cell subset.

[0144] In some aspects, the first comparison information indicates that at least two corresponding DCI payload sizes of the at least two scheduled cell subsets are equal, wherein the second comparison information indicates that corresponding CCE sets for the at least two scheduled cell subsets are equal. The UE 115-b (and in some aspects, the network entity 105-b) may determine that the DCI includes the presence of an indication of the scheduled cell subsets based on the first comparison information indicating that the at least two corresponding DCI payload sizes are equal and the second comparison information indicating that the corresponding CCE sets are equal. The indication of the scheduled cell subsets may include an explicit indication of the scheduled cell subsets.

[0145] In some aspects, the first comparison information indicates that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that the corresponding CCE sets for at least two scheduled cell subsets are equal. The UE 115-b (and in some aspects, the network entity 105-b) may determine the presence of the DCI including an indication of the scheduled cell subset based on the first comparison information indicating that the at least two corresponding DCI payload sizes are equal and the second comparison information indicating that the corresponding CCE sets are equal. The indication of the scheduled cell subset may include a rule-based indication of the scheduled cell subset. In some aspects, the rule-based indication includes information indicating a rule for selecting a scheduled cell subset of the scheduled cell set based on one of the following: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, a scheduled cell subset including a primary cell for the first network node, a scheduled cell subset including a scheduling cell, or a number of cells associated with the scheduled cell subset.

[0146] In some aspects, the first comparison information indicates that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that the corresponding CCE sets for at least two scheduled cell subsets are equal. UE 115-b (and in some aspects, network entity 105-b) may determine that the DCI includes the presence of an indication of the scheduled cell subsets based on the first comparison information indicating that the at least two corresponding DCI payload sizes are equal and the second comparison information indicating that the corresponding CCE sets are equal. The indication of the scheduled cell subset may include a radio network identifier for scrambling a CRC of a downlink control channel monitoring opportunity. In some aspects, the control signaling also includes an indication of an association between the corresponding radio network identifier and each scheduled cell subset.

[0147] In some aspects, the DCI includes scheduling information for one or more communications with the scheduled cell subset. At 620, the UE 115-b may communicate the one or more communications with the scheduled cell subset. In some aspects, the control signaling also includes an indication of a corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells, and the determination of the scheduling information is based on the indication of the corresponding carrier indicator associated with each scheduled cell in the set of scheduled cells.

[0148] In some aspects, UE 115-b (and in some aspects, network entity 105-b) may compare respective DCI payload sizes and generate first comparison information based on the comparison of respective DCI payload sizes. In some aspects, UE 115-b (and in some aspects, network entity 105-b) may compare respective CCE sets; and generate second comparison information based on the comparison of respective CCE sets.

[0149] Figure 7 A block diagram 700 of a device 705 supporting scheduled cell identification 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).

[0150] 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 associated with scheduled cell identities for multi-cell scheduling). The information may be delivered to other components of the device 705. The receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0151] 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 associated with various information channels (e.g., control channels, data channels, information channels associated with scheduled cell identities for multi-cell scheduling), such as packets, user data, control information, or any combination thereof. In some aspects, 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.

[0152] 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 the identification of scheduled cells 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.

[0153] In some aspects, 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 that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some aspects, 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).

[0154] Additionally or alternatively, in some aspects, 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 (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0155] In some aspects, the communication manager 720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the receiver 710, the transmitter 715, or both. For example, the communication manager 720 may 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.

[0156] According to an example as disclosed herein, the communication manager 720 may support wireless communication at a first network node. For example, the communication manager 720 may be configured to or otherwise support a component for receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The communication manager 720 may be configured to or otherwise support a component for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The communication manager 720 may be configured to or otherwise support a component for receiving DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0157] By including or configuring a communication manager 720 according to examples as described herein, a device 705 (e.g., a processor controlling or otherwise coupled to a receiver 710, a transmitter 715, a communication manager 720, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0158] Figure 8 A block diagram 800 of a device 805 supporting scheduled cell identification 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).

[0159] 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 associated with scheduled cell identities for multi-cell scheduling). The information may be delivered to other components of the device 805. The receiver 810 may utilize a single antenna or a collection of multiple antennas.

[0160] 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 associated with various information channels (e.g., control channels, data channels, information channels associated with scheduled cell identities for multi-cell scheduling), such as packets, user data, control information, or any combination thereof. In some aspects, 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.

[0161] The device 805 or its various components may be examples of components for performing various aspects of the identification of scheduled cells for multi-cell scheduling as described herein. For example, the communication manager 820 may include a scheduled cell manager 825, a DCI format manager 830, a DCI manager 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 aspects, the communication manager 820 or its various components may be configured to use or otherwise cooperate with the receiver 810, the transmitter 815, or both 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.

[0162] According to examples as disclosed herein, the communication manager 820 may support wireless communication at the first network node. The scheduled cell manager 825 may be configured to or otherwise support components for receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The DCI format manager 830 may be configured to or otherwise support components for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduled cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The DCI manager 835 may be configured to or otherwise support components for receiving DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0163] Fig. 9 A block diagram 900 of a communication manager 920 supporting scheduled cell identification for multi-cell scheduling according to one or more aspects of the present disclosure is shown. The communication manager 920 may 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 may be examples of components for performing various aspects of scheduled cell identification for multi-cell scheduling as described herein. For example, the communication manager 920 may include a scheduled cell manager 925, a DCI format manager 930, a DCI manager 935, a downlink control channel manager 940, a DCI payload size manager 945, a DCI CCE manager 950, a scheduled cell indication manager 955, a rule-based scheduled cell manager 960, a network identifier manager 965, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0164] According to examples as disclosed herein, the communication manager 920 may support wireless communication at a first network node. The scheduled cell manager 925 may be configured to or otherwise support components for receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The DCI format manager 930 may be configured to or otherwise support components for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduled cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The DCI manager 935 may be configured to or otherwise support components for receiving DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0165] In some aspects, to support determining the DCI format, the downlink control channel manager 940 may be configured or otherwise support means for determining the DCI format based on the third comparison information.

[0166] In some aspects, to support determining a DCI format, the DCI payload size manager 945 may be configured or otherwise support components for determining a DCI format based on a payload size of a downlink control channel monitoring opportunity that matches a corresponding DCI payload size for a subset of scheduled cells.

[0167] In some aspects, to support determining DCI formats, DCI CCE manager 950 may be configured or otherwise support components for determining DCI formats based on a set of CCEs for downlink control channel monitoring opportunities that matches a corresponding set of CCEs for a scheduled cell subset.

[0168] In some aspects, the scheduled cell indication manager 955 may be configured to or otherwise support components for: determining that the DCI includes the presence of an indication of a scheduled cell subset based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0169] In some aspects, the rule-based scheduled cell manager 960 may be configured to or otherwise support components for determining, based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, the presence of an indication that the DCI includes a scheduled cell subset, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0170] In some aspects, the rule-based indication includes information indicating a rule for selecting a scheduled cell subset of a set of scheduled cells based on one of: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, a scheduled cell subset including a primary cell for a first network node, a scheduled cell subset including a scheduling cell, or a number of cells associated with the scheduled cell subset.

[0171] In some aspects, the network identifier manager 965 may be configured to or otherwise support components for determining, based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, the presence of an indication that the DCI includes a scheduled cell subset, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a CRC for a downlink control channel monitoring opportunity.

[0172] In some aspects, the control signaling also includes an indication of an association between a respective radio network identifier and each scheduled cell subset.

[0173] In some aspects, the DCI includes scheduling information for communications with one or more of the scheduled subset of cells.

[0174] In some aspects, the control signaling further includes an indication of a respective carrier indicator associated with each scheduled cell in the set of scheduled cells. In some aspects, the determination of the scheduling information is based on the indication of the respective carrier indicator associated with each scheduled cell in the set of scheduled cells.

[0175] In some aspects, DCI payload size manager 945 may be configured or otherwise support components for comparing respective DCI payload sizes. In some aspects, DCI payload size manager 945 may be configured or otherwise support components for generating first comparison information based on a comparison of respective DCI payload sizes.

[0176] In some aspects, the DCI CCE manager 950 may be configured or otherwise support components for comparing respective CCE sets. In some aspects, the DCI CCE manager 950 may be configured or otherwise support components for generating second comparison information based on the comparison of respective CCE sets.

[0177] Fig.10 A diagram of a system 1000 including a device 1005 supporting a scheduled cell identification 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 components thereof. 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).

[0178] I / O controller 1010 can manage input signals and output signals of 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.

[0179] 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. The transceiver 1015 may communicate bidirectionally via one or more antennas 1025, a wired or wireless link, as described herein. 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.

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

[0181] 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 that support the identification of scheduled cells 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.

[0182] According to examples as disclosed herein, the communication manager 1020 may support wireless communication at a first network node. For example, the communication manager 1020 may be configured to or otherwise support a component for receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The communication manager 1020 may be configured to or otherwise support a component for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The communication manager 1020 may be configured to or otherwise support a component for receiving DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0183] By including or configuring a communications manager 1020 according to examples as described herein, the device 1005 can support techniques for more efficiently utilizing communications resources.

[0184] In some aspects, 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 aspects, 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 scheduled cell identification 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.

[0185] Fig.11 A block diagram 1100 of a device 1105 supporting scheduled cell identification 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).

[0186] 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 passed to other components of the device 1105. In some aspects, 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.

[0187] The transmitter 1115 may provide a means for outputting (e.g., sending, providing, conveying, 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 aspects, 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 aspects, 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.

[0188] 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 the identification of scheduled cells 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.

[0189] In some aspects, 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 that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some aspects, a processor and a memory coupled to the processor may be configured (e.g., by the processor executing instructions stored in the memory) to perform one or more of the functions described herein.

[0190] Additionally or alternatively, in some aspects, 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 functionality 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 (e.g., configured as or otherwise supporting means for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

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

[0192] According to an example as disclosed herein, the communication manager 1120 may support wireless communication at a first network node. For example, the communication manager 1120 may be configured to or otherwise support a component for sending control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The communication manager 1120 may be configured to or otherwise support a component for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The communication manager 1120 may be configured to or otherwise support a component for sending DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0193] By including or configuring a communications 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 communications manager 1120, or a combination thereof) may support techniques for more efficiently utilizing communications resources.

[0194] Fig.12 A block diagram 1200 of a device 1205 supporting scheduled cell identification 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).

[0195] 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 passed to other components of the device 1205. In some aspects, 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.

[0196] The transmitter 1215 may provide a means for outputting (e.g., sending, providing, conveying, 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 aspects, 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 aspects, 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.

[0197] The device 1205 or its various components may be examples of components for performing various aspects of the identification of scheduled cells for multi-cell scheduling as described herein. For example, the communication manager 1220 may include a scheduled cell manager 1225, a DCI format manager 1230, a DCI manager 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 aspects, 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 with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0198] According to examples as disclosed herein, the communication manager 1220 may support wireless communication at the first network node. The scheduled cell manager 1225 may be configured to or otherwise support means for sending control signaling to the second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of the scheduled cell set, wherein the scheduled cell set is associated with the scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The DCI format manager 1230 may be configured to or otherwise support means for determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The DCI manager 1235 may be configured to or otherwise support means for sending DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0199] Fig.13 A block diagram 1300 of a communication manager 1320 supporting scheduled cell identification 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 aspects of the communication manager 1120, the communication manager 1220, or both as described herein. The communication manager 1320 or its various components may be examples of components for performing various aspects of scheduled cell identification for multi-cell scheduling as described herein. For example, the communication manager 1320 may include a scheduled cell manager 1325, a DCI format manager 1330, a DCI manager 1335, a downlink control channel manager 1340, a DCI payload size manager 1345, a DCI CCE manager 1350, a scheduled cell indication manager 1355, a rule-based scheduled cell manager 1360, a network identifier manager 1365, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication 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.

[0200] According to examples as disclosed herein, the communication manager 1320 may support wireless communication at the first network node. The scheduled cell manager 1325 may be configured to or otherwise support means for sending control signaling to the second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of the scheduled cell set, wherein the scheduled cell set is associated with the scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The DCI format manager 1330 may be configured to or otherwise support means for determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The DCI manager 1335 may be configured to or otherwise support means for sending DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0201] In some aspects, to support determining the DCI format, the downlink control channel manager 1340 may be configured or otherwise support means for determining the DCI format based on the third comparison information.

[0202] In some aspects, to support determining a DCI format, the DCI payload size manager 1345 may be configured or otherwise support components for determining a DCI format based on a payload size of a downlink control channel monitoring opportunity that matches a corresponding DCI payload size for a subset of scheduled cells.

[0203] In some aspects, to support determining DCI formats, DCI CCE manager 1350 may be configured or otherwise support components for determining DCI formats based on a set of CCEs for downlink control channel monitoring opportunities that matches a corresponding set of CCEs for a scheduled cell subset.

[0204] In some aspects, the scheduled cell indication manager 1355 may be configured to or otherwise support components for: determining that the DCI includes the presence of an indication of a scheduled cell subset based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0205] In some aspects, the rule-based scheduled cell manager 1360 may be configured to or otherwise support components for: determining the presence of a DCI including an indication of a scheduled cell subset based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0206] In some aspects, the rule-based indication includes information indicating a rule for selecting a scheduled cell subset of a set of scheduled cells based on one of: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, a scheduled cell subset including a primary cell for a first network node, a scheduled cell subset including a scheduling cell, or a number of cells associated with the scheduled cell subset.

[0207] In some aspects, the network identifier manager 1365 may be configured to or otherwise support components for determining, based on first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on second comparison information indicating that corresponding CCE sets for at least two scheduled cell subsets are equal, the presence of an indication that the DCI includes a scheduled cell subset, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a CRC for a downlink control channel monitoring opportunity.

[0208] In some aspects, the control signaling also includes an indication of an association between a respective radio network identifier and each scheduled cell subset.

[0209] In some aspects, the DCI includes scheduling information for communications with one or more of the scheduled subset of cells.

[0210] In some aspects, the control signaling further includes an indication of a respective carrier indicator associated with each scheduled cell in the set of scheduled cells. In some aspects, the determination of the scheduling information is based on the indication of the respective carrier indicator associated with each scheduled cell in the set of scheduled cells.

[0211] In some aspects, DCI payload size manager 1345 may be configured or otherwise support components for comparing respective DCI payload sizes. In some aspects, DCI payload size manager 1345 may be configured or otherwise support components for generating first comparison information based on the comparison of respective DCI payload sizes.

[0212] In some aspects, the DCI CCE manager 1350 may be configured or otherwise support components for comparing respective CCE sets. In some aspects, the DCI CCE manager 1350 may be configured or otherwise support components for generating second comparison information based on the comparison of respective CCE sets.

[0213] Fig.14 A diagram of a system 1400 including a device 1405 supporting a scheduled cell identification 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 receive 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).

[0214] As described herein, the transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both. In some aspects, the transceiver 1410 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some aspects, the transceiver 1410 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some aspects, the device 1405 may include one or more antennas 1415 that may be able to (e.g., concurrently) send or receive wireless transmissions. The transceiver 1410 may also include a modem for modulating a signal, for providing a modulated signal for transmission (e.g., through one or more antennas 1415, through a wired transmitter), for receiving a modulated signal (e.g., from one or more antennas 1415, from a wired receiver), and for demodulating the signal. In some implementations, the transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1410 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform the following operations: perform or support operations based on received or obtained information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1410 or the transceiver 1410 and one or more antennas 1415 or the transceiver 1410 and one or more antennas 1415 and one or more processors or memory components (e.g., processor 1435 or memory 1425 or both) may be included in a chip or chip assembly installed in the device 1405. In some aspects, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0215] 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 (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1425 may include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0216] The processor 1435 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the 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 the processor 1435. The processor 1435 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 1425) to enable the device 1405 to perform various functions (e.g., functions or tasks supporting the identification of scheduled cells for multi-cell scheduling). For example, the device 1405 or a component of the device 1405 may include a processor 1435 and a memory 1425 coupled to the processor 1435, and the processor 1435 and the memory 1425 are configured to perform various functions described herein. The 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 (e.g., by executing code 1430) to perform functions of the device 1405. The processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1405 (such as in the memory 1425). In some specific implementations, the processor 1435 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1405). For example, the processing system of the device 1405 may refer to a system including various other components or subcomponents of the device 1405, such as the processor 1435, or the transceiver 1410, or the communication manager 1420, or other components or combinations of components of the device 1405. The processing system of the device 1405 may interface with other components of the device 1405, and may process information (such as inputs or signals) received from other components or output information to other components. For example, a chip or modem of the device 1405 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that the device 1405 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1405 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0217] In some aspects, bus 1440 may support communications of protocol layers (e.g., within protocol layers) of a protocol stack. In some aspects, bus 1440 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1405, or between different components of device 1405 that may be co-located or located at 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).

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

[0219] According to an example as disclosed herein, the communication manager 1420 may support wireless communication at a first network node. For example, the communication manager 1420 may be configured to or otherwise support a component for sending control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The communication manager 1420 may be configured to or otherwise support a component for: determining a DCI format for a downlink control channel monitoring opportunity in a scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset. The communication manager 1420 may be configured to or otherwise support a component for sending DCI via a downlink control channel monitoring opportunity according to the determined DCI format.

[0220] 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.

[0221] In some aspects, 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 aspects, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, the processor 1435, the memory 1425, the code 1430, or any combination thereof. For example, the code 1430 may include instructions executable by the processor 1435 to cause the device 1405 to perform various aspects of the scheduled cell identification 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.

[0222] Fig.15 A flowchart illustrating a method 1500 for supporting a scheduled cell identification 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 10The described functions may be performed by the UE 115. In some aspects, 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.

[0223] At 1505, the method may include receiving control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a set of scheduled cells, wherein the set of scheduled cells is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The operations of 1505 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1505 may be performed as described in reference to Fig. 9 The description is performed by the scheduled cell manager 925.

[0224] At 1510, the method may include determining a DCI format for scheduling a downlink control channel monitoring opportunity in a cell based on first comparison information corresponding to a corresponding DCI payload size and second comparison information corresponding to a corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in a set of scheduled cells, wherein the DCI format includes an absence or presence of an indication of the scheduled cell subset. The operations of 1510 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1510 may be performed as described in reference to Fig. 9 The DCI format manager 930 is used to execute.

[0225] At 1515, the method may include receiving DCI via a downlink control channel monitoring opportunity according to the determined DCI format. The operations of 1515 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1515 may be performed as described in reference to Fig. 9 The DCI manager 935 is used to execute.

[0226] Fig.16 A flowchart illustrating a method 1600 for supporting scheduled cell identification 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 network entity or a component thereof as described herein. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 6 as well as Figures 11 to 14 In some aspects, 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.

[0227] At 1605, the method may include sending control signaling to a second network node, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset of a set of scheduled cells, wherein the set of scheduled cells is associated with the scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset. The operations of 1605 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1605 may be performed as described with reference to Fig.13 The description is performed by the scheduled cell manager 1325.

[0228] At 1610, the method may include determining a DCI format for scheduling a downlink control channel monitoring opportunity in a cell based on first comparison information corresponding to a corresponding DCI payload size and second comparison information corresponding to a corresponding CCE, wherein the DCI format is associated with a scheduled cell subset in a set of scheduled cells, wherein the DCI format includes an absence or presence of an indication of the scheduled cell subset. The operations of 1610 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1610 may be performed as described in reference to Fig.13 The DCI format manager 1330 is used to execute.

[0229] At 1615, the method may include sending the DCI via a downlink control channel monitoring opportunity according to the determined DCI format. The operations of 1615 may be performed according to examples as disclosed herein. In some aspects, aspects of the operations of 1615 may be performed as described in reference to Fig.13 The DCI manager 1335 is used to perform the above operations. The following provides an overview of various aspects of the present disclosure:

[0230] Aspect 1: A method for performing wireless communications at a first network node, the method comprising: receiving control signaling, the control signaling including an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also includes an indication of a corresponding CCE set for each scheduled cell subset; determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the DCI format includes the absence or presence of an indication of the scheduled cell subset; and receiving DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0231] Aspect 2: A method according to Aspect 1, wherein the control signaling also includes an indication of a corresponding downlink control channel set for each scheduled cell subset, wherein third comparison information corresponds to the corresponding downlink control channel set, and wherein determining the DCI format includes: determining the DCI format based on the third comparison information.

[0232] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the first comparison information indicates that each corresponding DCI payload size of each scheduled cell subset is different, and determining the DCI format includes: determining the DCI format based on the payload size of the downlink control channel monitoring opportunity that matches the corresponding DCI payload size of the scheduled cell subset.

[0233] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the second comparison information indicates that each corresponding CCE set used for each scheduled cell subset is different, and wherein determining the DCI format includes: determining the DCI format based on a CCE set used for the downlink control channel monitoring opportunity that matches the corresponding CCE set used for the scheduled cell subset.

[0234] Aspect 5: According to the method described in any one of Aspects 1 to 2, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0235] Aspect 6: According to the method described in any one of Aspects 1 to 2, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0236] Aspect 7: A method according to Aspect 6, wherein the rule-based indication includes information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of the following: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or the number of cells associated with the scheduled cell subset.

[0237] Aspect 8: According to the method described in any one of Aspects 1 to 2, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling the cyclic redundancy check of the downlink control channel monitoring opportunity.

[0238] Aspect 9: The method according to aspect 8, wherein the control signaling further comprises an indication of an association between a corresponding radio network identifier and each scheduled cell subset.

[0239] Aspect 10: The method according to any one of aspects 1 to 9, wherein the DCI includes scheduling information for communicating with one or more of the scheduled cell subsets.

[0240] Aspect 11: A method according to Aspect 10, wherein the control signaling also includes an indication of a corresponding carrier indicator associated with each scheduled cell in the scheduled cell set, and the determination of the scheduling information is based on the indication of the corresponding carrier indicator associated with each scheduled cell in the scheduled cell set.

[0241] Aspect 12: According to the method according to any one of Aspects 1 to 11, the method also includes: comparing the corresponding DCI payload sizes; and generating the first comparison information based on the comparison of the corresponding DCI payload sizes.

[0242] Aspect 13: According to the method according to any one of aspects 1 to 12, the method further includes: comparing the corresponding CCE sets; and generating the second comparison information based on the comparison of the corresponding CCE sets.

[0243] Aspect 14: A method for performing wireless communications at a first network node, the method comprising: sending control signaling to a second network node, the control signaling comprising an indication of a corresponding DCI payload size for each scheduled cell subset in a scheduled cell set, wherein the scheduled cell set is associated with a scheduling cell, and wherein the control signaling also comprises an indication of a corresponding CCE set for each scheduled cell subset; determining a DCI format for a downlink control channel monitoring opportunity in the scheduling cell based on first comparison information corresponding to the corresponding DCI payload size and second comparison information corresponding to the corresponding CCE set, wherein the DCI format is associated with a scheduled cell subset in the scheduled cell set, wherein the downlink control channel format comprises the absence or presence of an indication of the scheduled cell subset; and sending DCI via the downlink control channel monitoring opportunity according to the determined DCI format.

[0244] Aspect 15: A method according to Aspect 14, wherein the control signaling also includes an indication of a corresponding downlink control channel set for each scheduled cell subset, wherein third comparison information corresponds to the corresponding downlink control channel set, and wherein determining the DCI format includes: determining the DCI format based on the third comparison information.

[0245] Aspect 16: A method according to any one of Aspects 14 to 15, wherein the first comparison information indicates that each corresponding DCI payload size of each scheduled cell subset is different, and wherein determining the DCI format includes: determining the DCI format based on the payload size of the downlink control channel monitoring opportunity that matches the corresponding DCI payload size of the scheduled cell subset.

[0246] Aspect 17: A method according to any one of Aspects 14 to 16, wherein the second comparison information indicates that each corresponding CCE set used for each scheduled cell subset is different, and wherein determining the DCI format includes: determining the DCI format based on a CCE set used for the downlink control channel monitoring opportunity that matches the corresponding CCE set used for the scheduled cell subset.

[0247] Aspect 18: According to the method described in any one of Aspects 14 to 15, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

[0248] Aspect 19: According to the method described in any one of Aspects 14 to 15, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

[0249] Aspect 20: A method according to Aspect 19, wherein the rule-based indication includes information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of the following: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or the number of cells associated with the scheduled cell subset.

[0250] Aspect 21: According to the method described in any one of Aspects 14 to 15, the method further includes: determining that the DCI includes the existence of the indication of the scheduled cell subset based on the first comparison information indicating that at least two corresponding DCI payload sizes of at least two scheduled cell subsets are equal and also based on the second comparison information indicating that the corresponding CCE sets used for the at least two scheduled cell subsets are equal, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling the cyclic redundancy check of the downlink control channel monitoring opportunity.

[0251] Aspect 22: The method according to aspect 21, wherein the control signaling further comprises an indication of an association between a corresponding radio network identifier and each scheduled cell subset.

[0252] Aspect 23: The method according to any one of aspects 14 to 22, wherein the DCI includes scheduling information for communicating with one or more of the scheduled cell subsets.

[0253] Aspect 24: A method according to Aspect 23, wherein the control signaling also includes an indication of a corresponding carrier indicator associated with each scheduled cell in the scheduled cell set, and the determination of the scheduling information is based on the indication of the corresponding carrier indicator associated with each scheduled cell in the scheduled cell set.

[0254] Aspect 25: According to the method according to any one of Aspects 14 to 24, the method also includes: comparing the corresponding DCI payload sizes; and generating the first comparison information based on the comparison of the corresponding DCI payload sizes.

[0255] Aspect 26: According to the method according to any one of Aspects 14 to 25, the method further includes: comparing the corresponding CCE sets; and generating the second comparison information based on the comparison of the corresponding CCE sets.

[0256] Aspect 27: A first network node for wireless communication, the first network node comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform the method according to any one of aspects 1 to 13.

[0257] Aspect 28: An apparatus for wireless communication at a first network node, the apparatus comprising at least one component for performing a method according to any one of aspects 1 to 13.

[0258] Aspect 29: A non-transitory computer readable medium having stored thereon code for wireless communication, the code, when executed by a network node, causes the network node to perform the method according to any one of aspects 1 to 13.

[0259] Aspect 30: A first network node for wireless communication, the first network node comprising: a memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to perform the method according to any one of aspects 14 to 26.

[0260] Aspect 31: An apparatus for wireless communication at a first network node, the apparatus comprising at least one component for performing a method according to any one of aspects 14 to 26.

[0261] Aspect 32: A non-transitory computer readable medium having stored thereon code for wireless communication, the code, when executed by a network node, causes the network node to perform a method according to any one of aspects 14 to 26.

[0262] The above methods describe possible implementations, operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0263] 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 described 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.

[0264] The information and signals described herein may be represented using any of a variety of different technologies 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.

[0265] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

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

[0267] Computer-readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates computer program to be transferred from one position to another position.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 device or other magnetic storage device or can be used for carrying or storing desired program code parts 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, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer-readable medium. Disks and optical disks used herein include CDs, laser optical disks, optical optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, while optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0268] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to the listed alternatives. For example, references to "X is based on A or B" should be interpreted as including within its scope X based on A, X based on B, and X based on A and B. In this regard, references to "X is based on A or B" refer to "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, references to "X is based on A, B, or C" should be interpreted as including within its scope X based on A, X based on B, X based on C, X based on A and B, X based on A and C, X based on B and C, and X based on A, B, and C. In this regard, references to "X is based on A, B, or C" refer to "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based on only one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based on at least A" unless specifically stated differently. Likewise, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same manner as "one or more" or "at least one."

[0269] The term "determining" encompasses a 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 the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Additionally, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

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

[0271] 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 terms "aspect" or "example" used herein mean "used as an aspect, example, instance, or illustration," rather than "preferred" or "advantageous over other aspects." The specific embodiments include specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0272] 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 first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving control signaling, the control signaling comprising an indication of a respective downlink control information payload size for each subset of scheduled cells in a set of scheduled cells, wherein the set of scheduled cells is associated with a scheduling cell, and wherein the control signaling further comprises an indication of a respective set of control channel elements for each subset of scheduled cells; determining, based on first comparison information corresponding to the corresponding downlink control information payload size and second comparison information corresponding to the corresponding set of control channel elements, a downlink control information format for a downlink control channel monitoring opportunity in the scheduled cell, wherein the downlink control information format is associated with a subset of scheduled cells in the set of scheduled cells, wherein the downlink control information format includes the absence or presence of an indication of the subset of scheduled cells; as well as According to the determined downlink control information format, downlink control information is received via the downlink control channel monitoring opportunity.

2. The first network node of claim 27, wherein the control signaling further comprises an indication of a corresponding set of downlink control channels for each scheduled cell subset, wherein the third comparison information corresponds to the corresponding set of downlink control channels, and wherein to determine the downlink control information format, the at least one processor is configured to: The downlink control information format is determined based on the third comparison information.

3. The first network node of claim 27, wherein the first comparison information indicates that each corresponding downlink control information payload size of each scheduled cell subset is different, wherein to determine the downlink control information format, the at least one processor is configured to: The downlink control information format is determined based on a payload size of the downlink control channel monitoring occasion that matches a corresponding downlink control information payload size of the scheduled cell subset.

4. The first network node of claim 27, wherein the second comparison information indicates that each corresponding set of control channel elements for each scheduled cell subset is different, wherein to determine the downlink control information format, the at least one processor is configured to: The downlink control information format is determined based on a set of control channel elements for the downlink control channel monitoring occasions that matches a corresponding set of control channel elements for the scheduled cell subset.

5. The first network node according to claim 27, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that the corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

6. The first network node according to claim 27, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that the corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

7. The first network node according to claim 6, wherein the rule-based indication includes information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of the following: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or a number of cells associated with the scheduled cell subset.

8. The first network node according to claim 27, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that the corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a cyclic redundancy check of the downlink control channel monitoring opportunity.

9. The first network node according to claim 8, wherein the control signalling further comprises an indication of an association between a respective radio network identifier and each scheduled cell subset.

10. The first network node of claim 27, wherein downlink control information comprises scheduling information for communicating with one or more of the scheduled subset of cells.

11. The first network node according to claim 10, wherein the control signaling further comprises an indication of a respective carrier indicator associated with each scheduled cell in the set of scheduled cells, and wherein the determination of the scheduling information is based on the indication of the respective carrier indicator associated with each scheduled cell in the set of scheduled cells.

12. The first network node of claim 27, wherein the at least one processor is configured to: comparing the respective downlink control information payload sizes; and The first comparison information is generated based on the comparison of the respective downlink control information payload sizes.

13. The first network node of claim 27, wherein the at least one processor is configured to: comparing the corresponding sets of control channel elements; and The second comparison information is generated based on the comparison of the respective sets of control channel elements.

14. A first network node for wireless communication, the first network node comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: sending control signaling to a second network node, the control signaling comprising an indication of a respective downlink control information payload size for each subset of scheduled cells in a set of scheduled cells, wherein the set of scheduled cells is associated with a scheduling cell, and wherein the control signaling further comprises an indication of a respective set of control channel elements for each subset of scheduled cells; determining, based on first comparison information corresponding to the corresponding downlink control information payload size and second comparison information corresponding to the corresponding set of control channel elements, a downlink control information format for a downlink control channel monitoring opportunity in the scheduled cell, wherein the downlink control information format is associated with a subset of scheduled cells in the set of scheduled cells, wherein the downlink control information format includes the absence or presence of an indication of the subset of scheduled cells; as well as According to the determined downlink control information format, downlink control information is sent via the downlink control channel monitoring opportunity.

15. The first network node of claim 14, wherein the control signaling further comprises an indication of a corresponding set of downlink control channels for each scheduled cell subset, wherein the third comparison information corresponds to the corresponding set of downlink control channels, and wherein to determine the downlink control information format, the at least one processor is configured to: The downlink control information format is determined based on the third comparison information.

16. The first network node of claim 14, wherein the first comparison information indicates that each corresponding downlink control information payload size of each scheduled cell subset is different, wherein to determine the downlink control information format, the at least one processor is configured to: The downlink control information format is determined based on a payload size of the downlink control channel monitoring occasion that matches a corresponding downlink control information payload size of the scheduled cell subset.

17. The first network node of claim 14, wherein the second comparison information indicates that each corresponding set of control channel elements for each scheduled cell subset is different, wherein to determine the downlink control information format, the at least one processor is configured to: The determination is based on a set of control channel elements for the downlink control channel monitoring occasions that matches a corresponding set of control channel elements for the scheduled cell subset.

18. The first network node according to claim 14, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes an explicit indication of the scheduled cell subset.

19. The first network node according to claim 14, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes a rule-based indication of the scheduled cell subset.

20. The first network node of claim 19, wherein the rule-based indication comprises information indicating a rule for selecting the scheduled cell subset of the scheduled cell set based on one of: a component carrier index associated with one or more scheduled cells within the scheduled cell subset, a subcarrier spacing associated with one or more scheduled cells within the scheduled cell subset, the scheduled cell subset including a primary cell for the first network node, the scheduled cell subset including the scheduling cell, or a number of cells associated with the scheduled cell subset.

21. The first network node according to claim 14, wherein the first comparison information indicates that at least two corresponding downlink control information payload sizes of at least two scheduled cell subsets are equal, wherein the second comparison information indicates that corresponding control channel element sets for the at least two scheduled cell subsets are equal, and wherein the at least one processor is configured to: Based on the first comparison information indicating that the at least two corresponding downlink control information payload sizes are equal and the second comparison information indicating that the corresponding control channel element sets are equal, it is determined that the downlink control information includes the presence of the indication of the scheduled cell subset, wherein the indication of the scheduled cell subset includes a radio network identifier for scrambling a cyclic redundancy check of the downlink control channel monitoring opportunity.

22. The first network node according to claim 21, wherein the control signalling further comprises an indication of an association between a respective radio network identifier and each scheduled cell subset.

23. The first network node of claim 14, wherein the downlink control information comprises scheduling information for one or more communications between the second network node and the subset of scheduled cells.

24. The first network node according to claim 23, wherein the control signaling further comprises an indication of a respective carrier indicator associated with each scheduled cell in the set of scheduled cells, and wherein the determination of the scheduling information is based on the indication of the respective carrier indicator associated with each scheduled cell in the set of scheduled cells.

25. The first network node of claim 14, wherein the at least one processor is configured to: comparing the respective downlink control information payload sizes; and The first comparison information is generated based on the comparison of the respective downlink control information payload sizes.

26. The first network node of claim 14, wherein the at least one processor is configured to: comparing the corresponding sets of control channel elements; and The second comparison information is generated based on the comparison of the respective sets of control channel elements.

27. A method for wireless communication at a first network node, the method comprising: receiving control signaling, the control signaling comprising an indication of a respective downlink control information payload size for each subset of scheduled cells in a set of scheduled cells, wherein the set of scheduled cells is associated with a scheduling cell, and wherein the control signaling further comprises an indication of a respective set of control channel elements for each subset of scheduled cells; determining, based on first comparison information corresponding to the corresponding downlink control information payload size and second comparison information corresponding to the corresponding set of control channel elements, a downlink control information format for a downlink control channel monitoring opportunity in the scheduled cell, wherein the downlink control information format is associated with a subset of scheduled cells in the set of scheduled cells, wherein the downlink control channel format includes the absence or presence of an indication of the subset of scheduled cells; as well as According to the determined downlink control information format, downlink control information is received via the downlink control channel monitoring opportunity.

28. The method of claim 27, wherein the control signaling further comprises an indication of a corresponding set of downlink control channels for each scheduled cell subset, wherein the third comparison information corresponds to the corresponding set of downlink control channels, and wherein determining the downlink control information format comprises: The downlink control information format is determined based on the third comparison information.

29. The method of claim 27, wherein the first comparison information indicates that each corresponding downlink control information payload size of each scheduled cell subset is different, wherein determining the downlink control information format comprises: The downlink control information format is determined based on a payload size of the downlink control channel monitoring occasion that matches a corresponding downlink control information payload size of the scheduled cell subset.

30. A method for wireless communication at a first network node, the method comprising: sending control signaling to a second network node, the control signaling comprising an indication of a respective downlink control information payload size for each subset of scheduled cells in a set of scheduled cells, wherein the set of scheduled cells is associated with a scheduling cell, and wherein the control signaling further comprises an indication of a respective set of control channel elements for each subset of scheduled cells; determining, based on first comparison information corresponding to the corresponding downlink control information payload size and second comparison information corresponding to the corresponding set of control channel elements, a downlink control information format for a downlink control channel monitoring opportunity in the scheduled cell, wherein the downlink control information format is associated with a subset of scheduled cells in the set of scheduled cells, wherein the downlink control channel format includes the absence or presence of an indication of the subset of scheduled cells; as well as According to the determined downlink control information format, downlink control information is sent via the downlink control channel monitoring opportunity.

Images