Carrier indicator field mapping

By mapping the carrier indicator field (CIF) values ​​in the wireless communication system, the problem of inaccurate resource mapping in multi-cell scheduling is solved, and communication efficiency and performance are improved.

CN118947082APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380034063.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-12-29
Filing Date
2023-02-24
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The existing wireless communication system is difficult to effectively utilize the carrier indicator field (CIF) value in multi-cell scheduling, resulting in inaccurate resource mapping and affecting communication efficiency.

Method used

By mapping carrier indicator field (CIF) values ​​between user equipment (UE) and network nodes, resource scheduling and communication of multiple cells are realized, and the CIF value is used to identify the cell on which to communicate, and in the downlink The link control information contains CIF values ​​to schedule resources.

Benefits of technology

The communication efficiency of multi-cell scheduling is improved, the accurate mapping and utilization of resources is ensured, and the overall performance of wireless communication is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947082A_ABST
    Figure CN118947082A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive downlink control information including a carrier indicator field (CIF) value, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information configured to schedule resources on the one or more cells. The UE may communicate on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 363,367, filed on April 21, 2022, entitled “CARRIER INDICATOR FIELD MAPPING” and U.S. Non-Provisional Patent Application No. 18 / 148,241, filed on December 29, 2022, entitled “CARRIER INDICATOR FIELD MAPPING” and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for carrier indicator field mapping. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards by using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR, and other radio access technologies remain useful. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0008] FIG. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0009] FIG. 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0010] FIG. 3 is a diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.

[0011] FIG. 4 is a diagram illustrating an example of downlink control information (DCI) scheduling a plurality of cells according to the present disclosure.

[0012] 5A to 5K are diagrams illustrating examples associated with carrier indicator field (CIF) mapping according to the present disclosure.

[0013] 6 to 7 are diagrams illustrating example processes associated with CIF mapping according to the present disclosure.

[0014] 8-9 are diagrams of example apparatuses for wireless communications according to the present disclosure. Summary of the invention

[0015] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving downlink control information including a carrier indicator field (CIF) value, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The method may include communicating on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0016] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The method may include communicating with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, can cause the UE to: receive downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The instruction set, when executed by one or more processors of the UE, can cause the UE to: communicate on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to: send downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The instruction set, when executed by one or more processors of the network node, may cause the network node to: communicate with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The apparatus may include means for communicating on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The apparatus may include means for communicating with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0021] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0022] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0023] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. The devices incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes, and configurations. DETAILED DESCRIPTION

[0024] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of the claims.

[0025] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0026] Although various aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0027] FIG. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0028] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0029] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a micro cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A micro cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a micro cell may be referred to as a micro network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. In the example shown in FIG. 1 , the network node 110a may be a macro network node for a macro cell 102a, the network node 110b may be a pico network node for a pico cell 102b, and the network node 110c may be a femto network node for a femto cell 102c. The network node may support one or more (e.g., three) cells. In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move according to the location of the mobile network node 110 (e.g., a mobile network node).

[0030] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC) or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0031] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. In the example shown in FIG. 1 , a network node 110 d (e.g., a relay network node) may communicate with a network node 110 a (e.g., a macro network node) and a UE 120 d to facilitate communication between the network node 110 a and the UE 120 d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0032] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0033] The network controller 130 may be coupled to or in communication with a collection of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network device.

[0034] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0035] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0036] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0037] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0038] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as a "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as a "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunication Union (ITU).

[0039] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz), and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0040] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be below 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0041] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive downlink control information including a carrier indicator field (CIF) value that identifies one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and communicate on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0042] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and communicate with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0043] As indicated above, Figure 1 is provided as an example. Other examples may differ from what is described with respect to Figure 1 .

[0044] 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0045] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0046] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from the network node 110 and / or other network nodes 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from the modem 254, can perform MIMO detection on the received symbols where applicable, and can provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0047] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0048] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmit and / or receive components (such as one or more of FIG. 2 ).

[0049] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, where applicable, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280 ) and memory 282 to perform aspects of any of the methods described herein (eg, with reference to FIGS. 5A-9 ).

[0050] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 5A-9 ).

[0051] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform one or more techniques associated with CIF mapping, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or any other component of FIG. 2 may perform or direct the operation of, for example, process 600 of FIG. 6, process 700 of FIG. 7, and / or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after being compiled, converted, and / or interpreted) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct operations such as process 600 of FIG. 6 , process 700 of FIG. 7 , and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, among others.

[0052] In some aspects, the UE 120 includes a component for receiving downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and / or a component for communicating on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. The components for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0053] In some aspects, the network node 110 includes a component for sending downlink control information including a CIF value to the UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and / or a component for communicating with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. In some aspects, the components for the network node 110 to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0054] Although the blocks in FIG2 are illustrated as distinct components, the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0055] As indicated above, Figure 2 is provided as an example. Other examples may differ from what is described with respect to Figure 2.

[0056] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0057] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), etc.

[0058] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Various units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0059] 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as through an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via corresponding radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.

[0060] Each of these units (including CU 310, DU 330, RU 340) and near-RT RIC 325, non-RTRIC 315 and SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces, which are configured to receive or send signals, data or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, and the wireless interface may include a receiver, a transmitter or a transceiver (such as an RF transceiver), which is configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0061] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0062] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may implement 4g using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0063] Each RU 340 may implement lower layer functionality. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on a functional split (e.g., a functional split defined by 3GPP) such as a lower layer functional split, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, and other examples. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0064] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0065] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0066] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0067] As indicated above, Figure 3 is provided as an example. Other examples may differ from what is described with respect to Figure 3.

[0068] FIG4 is a diagram illustrating an example 400 of scheduling downlink control information (DCI) for multiple cells according to the present disclosure. As shown in FIG4, a network node 110 and a UE 120 may communicate with each other.

[0069] The network node 110 may send a DCI 405 to the UE 120, which is configured to schedule one or more communications for the UE 120. The multiple communications may be scheduled for at least two different cells. In some cases, a cell may be referred to as a "component carrier", "CC" or "carrier". In some cases, a DCI that schedules communications for a cell via which the DCI is sent may be referred to as a self-carrier (or self-cell) scheduled DCI. In some cases, a DCI that schedules communications for a cell via which the DCI is sent may be referred to as a cross-carrier (or cross-cell) scheduled DCI. In some aspects, the DCI 405 may be a cross-carrier scheduled DCI, and may or may not be a self-carrier scheduled DCI. In some aspects, the DCI 405 carrying communications in at least two cells may be referred to as a combined DCI.

[0070] In example 400, DCI 405 schedules communications for a first cell 410 (shown as CC0) that carries DCI 405, schedules communications for a second cell 415 (shown as CC1) that does not carry DCI 405, and schedules communications for a third cell 420 (shown as CC2) that does not carry DCI 405. In some aspects, DCI 405 may schedule communications on a different number of cells than shown in FIG4 (e.g., two cells, four cells, five cells, etc.). The number of cells may be greater than or equal to two.

[0071] Communications scheduled by DCI 405 may include data communications, such as physical downlink shared channel (PDSCH) communications, physical uplink shared channel (PUSCH) communications. For data communications, DCI 405 may schedule a single transport block (TB) across multiple cells, or may schedule multiple TBs separately in multiple cells. Additionally or alternatively, communications scheduled by DCI 405 may include reference signals, such as channel state information (CSI) reference signals (RS) (CSI-RS) or sounding reference signals (SRS). For reference signals, DCI 405 may trigger a single resource for reference signal transmission across multiple cells, or may schedule multiple resources separately for reference signal transmission in multiple cells. In some cases, scheduling information in DCI 405 may be indicated once and reused for multiple communications (e.g., on different cells), such as MCS, resources to be used for hybrid automatic repeat request (HARQ) acknowledgement (ACK) or negative acknowledgement (NACK) (ACK / NACK) of communications scheduled by DCI 405, and / or resource allocations for the scheduled communications to save signaling overhead.

[0072] As indicated above, Figure 4 is provided as an example. Other examples may differ from what is described with respect to Figure 4.

[0073] For the cross-carrier scheduling (CCS) scenario, the network node may set a cross-carrier scheduling configuration (crossCarrierSchedulingConfig) for each scheduled cell. The cross-carrier scheduling configuration may include one or more parameters, such as a parameter indicating which serving cell is the scheduling cell or a parameter indicating which CIF value corresponds to the scheduled cell, etc. The CIF value may indicate the mapping between the scheduled cell on which the DCI is sent and the scheduled cell on which the PDSCH may be scheduled by the DCI. For example, a CIF value of "0" may indicate a first cell of a first carrier (e.g., self-scheduling), a CIF value of "1" may indicate a second cell of a second carrier, or a CIF value of "2" may indicate a third cell of a third carrier, and so on.

[0074] A set of control channel elements (CCEs) for physical downlink control channel (PDCCH) candidates with a configured aggregation level may be based at least in part on a parameter n CI , where n CIThe value of is indicated by or is equivalent to the CIF value. Therefore, DCI formats with different CIF values ​​may correspond to different CCE sets for blind decoding. However, in multi-cell scheduling, the UE may lack information that identifies the associated mapping of DCI formats and CIF values ​​to cells or carriers. Some aspects described herein enable CIF mapping, such as in multi-cell scheduling scenarios. For example, some aspects described herein provide CIF-based multi-cell scheduling mapping, which may enable the UE and / or network node to determine a set of resources on which to communicate and / or monitor communications.

[0075] 5A to 5K are diagrams illustrating an example 500 associated with CIF mapping according to the present disclosure. As shown in FIG5A , the example 500 includes communications between a UE 120 and a network node 110.

[0076] 5A and further illustrated by reference numeral 510, UE 120 may receive DCI from network node 110. For example, UE 120 may receive DCI in which the value of the CIF field is set to "0" to "3" to indicate one or more scheduled cells. Additionally or alternatively, the value of the CIF field may be set to a range of "0" to "7" or another range for indicating a cell set or a carrier set.

[0077] In some aspects, the UE 120 may map a CIF value to a carrier or cell to determine a resource in which to communicate with the network node 110. For example, the UE 120 may map a CIF value to a set of carriers using a configured mapping (such as a mapping table or a codebook). In some aspects, the size (e.g., payload) and content (e.g., field set) of a DCI format of a DCI is determined on a per-CIF basis. For example, as described herein, a DCI having a CIF value associated with multiple cells may include one or more dedicated or extended DCI fields for multi-cell scheduling. In some aspects, the network node 110 may align the size of the DCI format. For example, when a cell may be mapped from multiple CIF values, the network node 110 may align the size between two DCI formats having different CIF values ​​associated with the same cell or carrier, as described herein. In other words, if two DCI formats are associated with different CIF values ​​and may schedule the same cell, the network node 110 may add padding bits to the smaller of the two DCIs to align the respective sizes of the DCIs. Similarly, the network node 110 may align sizes between DCIs having different downlink cells and uplink cells identified therein, as described in more detail herein.Alternatively, the network node 110 may send DCIs having different sizes.

[0078] As shown in FIG5B , for multi-cell scheduling, a CIF value may be mapped to one or more scheduled cells. For example, a first CIF value (e.g., “0”) in the DCI may be mapped to a first carrier (e.g., carrier “CC#0” for self-scheduling), and a second CIF value (e.g., “1”) in the DCI may be mapped to a second carrier set (e.g., carriers “CC#2”, “CC#4”, and “CC#5”). In this case, the UE 120 may determine the CIF mapping (e.g., one-to-one CIF mapping or one-to-many CIF mapping) based at least in part on the received radio resource configuration (RRC) signaling indicating the CIF mapping. As further shown in FIG5B , each carrier may be associated with a parameter set, such as a scheduling cell information (schedulingCellInfo) parameter, a scheduling cell identifier (schedulingCellId) parameter, or a CIF in a scheduling cell parameter (cifInSchedulingCell), and the like. In this case, for multiple cells configured with cross-carrier scheduling from the same scheduled cell, the value of the cifInSchedulingCell parameter is the same value. In other words, based at least in part on the fact that CC#2, CC#4, and CC#5 can be scheduled from the same carrier CC#0, each of CC#2, CC#4, and CC#5 has the same cifInSchedulingCell parameter in cross-carrier scheduling.

[0079] As shown in Figures 5C and 5D, for multi-cell scheduling, the CIF value can be mapped to both the self-scheduled carrier and the cross-carrier scheduled carrier. For example, UE 120 can receive DCI on CC#0 including a CIF value indicating that the DCI can schedule PDSCH on CC#0 and on CC#2 and CC#4. In some aspects, to indicate that CC#2 and CC#4 are scheduled from CC#0, which is also self-scheduled, the range of values ​​of cifInSchedulingCell can be extended to 0, as shown in Figure 5C. Additionally or alternatively, the parameter schedulingCellInfo can be configured to a value other than "self" (e.g., which indicates self-scheduling as shown in Figure 5B), such as a value of "1", as shown in Figure 5D, instead of extending the range of values ​​of cifInSchedulingCell to 0. In this case, CC#0 is associated with a value of "1" for cifInSchedulingCell, thereby grouping CC#0 with CC#2 and CC#4 for multi-cell scheduling.

[0080] In some aspects, UE 120 may determine a search space for monitoring DCI for multi-cell scheduling. For example, UE 120 may determine CCEs for PDCCH candidates based at least in part on a CIF value. In this case, when there are one or more PDCCH candidates associated with the same CIF value, the same n CI The value corresponds to a CCE for one or more PDCCH candidates. In some aspects, UE 120 may monitor the CCE corresponding to n CI The number of search space sets for one or more serving cells of the value.

[0081] In some aspects, the scheduled cell may be mapped to only a single CIF value. In this case, the UE 120 may monitor the CIF value corresponding to the single cell. CI The maximum number of blind decoded or non-overlapping CCEs for one scheduled cell may be the PDCCH blind decoding CCE budget for a case where multi-cell scheduling is not configured, and may be applicable to a search space set for PDCCH and associated DCI with a CIF value for one or more cells. Alternatively, the maximum number of blind decoded or non-overlapping CCEs for one scheduled cell multiplied by an integer M may be the PDCCH blind decoding CCE budget, and may be applicable to a search space set for PDCCH and associated DCI with a CIF value if the CIF value is associated with M cells. The network node 110 may configure the number of PDCCH candidates so that for a PDCCH and with each CIF or n cells, CI The number of blind decodings or CCEs to be processed by UE 120 for the associated DCI reception of the value does not exceed the PDCCH blind decoding CCE budget of each scheduled cell that UE 120 can process in the scheduling cell. Alternatively, if the scheduled cell exceeds the PDCCH blind decoding CCE budget, UE 120 may determine not to monitor one or more search space sets in the scheduling cell to avoid exceeding the blind decoding CCE budget (e.g., this situation may be referred to as a "PDCCH oversubscription" situation). Figure 5E shows an example set of CIF mappings when a single scheduled cell can be mapped to only a single CIF value. For example, Table 550-1 shows an example of CIF mapping to more than one scheduled cell (from one scheduling cell). Alternatively, Table 550-2 and Table 550-3 show examples of CIF mapping to more than one scheduled cell (from one scheduling cell) using self-scheduling (e.g., as described above, respectively using an extended cifInSchedulingCell range or using schedulingCellInfo configured to another value).

[0082] In some aspects, the scheduled cells may be mapped to one or more CIF values. In this case, the UE 120 may monitor the PDCCH candidates of each scheduled cell, rather than being limited to a single n CI In some aspects, in the case of mapping to one or more CIF values, the PDCCH blind decoding CCE budget applies to one or more cells for PDCCH and has n CI Alternatively, when a cell can be scheduled by DCI, the PDCCH blind decoding CCE budget can be applied to the search space set for DCI with multiple CIF values. In this case, the network node 110 can configure one or more n associated with the cell. CI The number of PDCCH candidates of value such that for one or more n CI value, the number of blind decodings or CCEs to be processed by UE 120 does not exceed the PDCCH blind decoding CCE budget of each scheduled cell that UE 120 can process in the scheduling cell. Alternatively, as described above, UE 120 may abandon monitoring one or more search space sets that exceed the blind decoding CCE budget (e.g., in a PDCCH oversubscription scenario). Figure 5F shows an example set of CIF mappings when a single scheduled cell can be mapped to one or more CIF values. For example, Table 555-1 shows an example of CIF mapping to more than one scheduled cell (from one scheduling cell). Alternatively, Table 555-2 and Table 555-3 show examples of CIF mapping to more than one scheduled cell (from one scheduling cell) using self-scheduling (e.g., as described above, using an extended cifInSchedulingCell range or using schedulingCellInfo configured to another value, respectively). As shown in each of the tables of FIG. 5F , the scheduled cells may be mapped from multiple different CIF values, such as CC#1 and CC#2 mapping from both CIF value 1 and value 2 in table 555 - 1 .

[0083] In some aspects, the UE 120 may monitor multiple types of DCI formats to receive DCI with a CIF value. For example, for a scheduling cell, the UE 120 may monitor a first DCI format for multi-cell scheduling and a second DCI format for single-cell scheduling. In the first case, the DCI format for multi-cell scheduling may be a format in which the DCI can be scheduled on multiple cells (but may not necessarily be scheduled on multiple cells). In this first case, when the DCI can be scheduled on multiple cells but is only scheduled on a single cell, the DCI is a multi-cell scheduling DCI. In the second case, the DCI format for multi-cell scheduling may be a format in which the DCI is indeed scheduled on multiple cells. In other words, in this second case, when the DCI can be scheduled on multiple cells but is only scheduled on a single cell, the DCI is a single-cell scheduling DCI. In some aspects, on a scheduling cell (e.g., associated with a CIF value of 0), the UE 120 may monitor a multi-cell scheduling DCI format and a single-cell scheduling DCI format. When UE 120 receives DCI having a format that does not include a CIF field, UE 120 may, based at least in part on a DCI having a default CIF value (eg, n CI The default value of 0 is used to determine the PDCCH candidate for DCI by using a hash function equation. FIG. 5G shows an example of CIF mapping when UE 120 is configured to monitor multiple DCI formats. In this case, as shown in the figure, the mapping of CIF values ​​to scheduled cells is based at least in part on which DCI format the CIF value is received.

[0084] In some aspects, the number of downlink cells or carriers is not the same as the number of uplink cells or carriers. For example, UE 120 may be configured to monitor a first number of downlink cells having a first downlink traffic pattern and a second number of uplink cells having a second uplink traffic pattern, wherein the second uplink traffic pattern may be independent of the first downlink traffic pattern. Therefore, UE 120 may have a separate configuration for multi-cell scheduling for PDSCH reception on the downlink and PUSCH transmission on the uplink. For example, UE 120 may enable multi-cell PDSCH scheduling on the downlink, but UE 120 may not enable multi-cell PUSCH scheduling on the uplink, or vice versa. Similarly, the DCI format may be configured for scheduling PDSCH on a number N cells and for scheduling PUSCH on a number M cells. In cross-carrier scheduling, the same DCI format may be used for PDSCH scheduling and PUSCH scheduling (eg, a 1-bit format identifier is included in the DCI to distinguish between PDSCH scheduling and PUSCH scheduling), and the CIF value may point to the same scheduled cell for PDSCH scheduling and PUSCH scheduling.

[0085] 5H shows an example of CIF mapping, where DCI on CC#0 is scheduled to CC#0, CC#2, CC#4, and CC#5 according to the CIF mapping. As shown in the CIF mapping, for some CIF values ​​(e.g., value 0 and value 1), the PDSCH mapping and PUSCH mapping can be the same, but for other values, as shown, only the PDSCH mapping (e.g., CIF values ​​2 and 3) can be configured based at least in part on the downlink (but not the uplink) configured on the carrier corresponding to the other values. Alternatively, as shown in FIG. 5I, the CIF values ​​can be mapped independently to the downlink and uplink. In other words, as shown, the UE 120 can have a first mapping of CIF values ​​to downlink cells and a second mapping of CIF values ​​to uplink cells. In this case, in Table 560-1, the uplink cells pointed to by the CIF value may be restricted to a subset of the downlink cells pointed to by the same CIF value, or in Table 560-2, the uplink cells may be any uplink cell set independent of the downlink cell set pointed to by the same CIF value. In some aspects, the corresponding CIF value mapping may be configured for the UE 120 by RRC signaling received from the network node 110 and indicated using a bit indicator (e.g., indicating whether the received CIF value mapping is for uplink or downlink). Figures 5J and 5K show additional examples of independent uplink and downlink CIF mappings. For example, Figure 5J shows an example of CIF mapping with downlink carrier aggregation of 11 carriers and no uplink carrier aggregation. In contrast, Figure 5K shows an example of downlink carrier aggregation with 11 carriers and uplink carrier aggregation with 3 carriers.

[0086] 5A, UE 120 may communicate with network node 110 according to the DCI, as indicated by reference numeral 520. For example, UE 120 may receive one or more PDSCHs on one or more carriers indicated by the DCI in conjunction with CIF values ​​and mapping of CIF values ​​to carriers or cells.

[0087] As indicated above, Figures 5A to 5K are provided as examples. Other examples may differ from what is described with respect to Figures 5A to 5K.

[0088] 6 is a diagram illustrating an example process 600, performed, for example, by a UE, in accordance with the present disclosure. Example process 600 is an example of a UE (eg, UE 120) performing operations associated with carrier indicator field mapping.

[0089] As shown in FIG. 6 , in some aspects, process 600 may include receiving downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells (block 610). For example, a UE (e.g., using the communication manager 140 and / or receiving component 802 depicted in FIG. 8 ) may receive downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells, as described above in conjunction with FIGS. 5A to 5K . In some aspects, the downlink control information may include a field allocated for conveying the CIF value. Additionally or alternatively, the downlink control information may include a field that is not allocated for conveying the CIF value but that the network node and the UE may use to communicate the CIF value. Additionally or alternatively, the UE may infer the CIF value based at least in part on some other value in the downlink control information.

[0090] As further shown in FIG. 6, in some aspects, process 600 may include communicating on one or more cells based at least in part on a mapping between a CIF value and one or more cells (block 620). For example, a UE (e.g., using the communication manager 140 and / or receiving component 802 or transmitting component 804 depicted in FIG. 8) may communicate on the one or more cells based at least in part on a mapping between a CIF value and one or more cells, as described above in conjunction with FIGS. 5A to 5K. In some aspects, the UE may identify a cell on which to communicate based at least in part on a CIF value. For example, the UE may have a mapping between a CIF value and a cell on which the UE is to communicate. In this case, downlink control information including a CIF value may be scheduled to a cell corresponding to a CIF value included in the downlink control information. The UE may store the mapping as a table or other data structure.

[0091] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0092] In a first aspect, the CIF value is mapped from a common scheduling cell to a plurality of cells configured with cross-carrier scheduling for at least one of the plurality of cells.

[0093] In a second aspect, alone or in combination with the first aspect, the downlink control information schedules data on the same cell that conveys the downlink control information.

[0094] In a third aspect, alone or in combination with one or more of the first and second aspects, the CIF value ranges from 0 to at least 3.

[0095] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the scheduling cell information parameter has an "other" value, and the scheduling cell is mapped to a non-zero CIF value.

[0096] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, process 600 comprises monitoring a search space set for the downlink control information, wherein a control channel element for a physical downlink control channel candidate associated with the downlink control information is based at least in part on the CIF value.

[0097] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

[0098] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

[0099] In the eighth aspect, either alone or in combination with one or more of aspects one to seven, process 600 includes monitoring a plurality of different downlink control information formats for a scheduling cell associated with the CIF value, wherein the plurality of different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

[0100] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the first set of scheduled downlink cells is different from the second set of scheduled uplink cells.

[0101] In the tenth aspect, alone or in combination with one or more aspects from the first to the ninth aspects, the CIF value is mapped to a first scheduled downlink cell set and a second scheduled uplink cell set, wherein the second scheduled uplink cell set is a subset of the first scheduled uplink cell set.

[0102] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the size and content of the downlink control information are associated with the CIF value.

[0103] In a twelfth aspect, either alone or in combination with one or more of aspects 1 to eleven, the CIF value is mapped to a cell, and the downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

[0104] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell is different from the first downlink cell or is a subset of the first downlink cell, and the downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align the size with another downlink control information that schedules the other of the first downlink cell or the second uplink cell.

[0105] Although Figure 6 shows example blocks of process 600, in some aspects, process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in Figure 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0106] 7 is a diagram illustrating an example process 700, performed, for example, by a network node, in accordance with the present disclosure. Example process 700 is an example of a network node (eg, network node 110) performing operations associated with CIF mapping.

[0107] As shown in FIG. 7 , in some aspects, process 700 may include sending downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells (block 710). For example, a network node (e.g., using the communication manager 150 and / or the transmitting component 904 depicted in FIG. 9 ) may send downlink control information including a CIF value to a UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells, as described above in conjunction with FIGS. 5A to 5K . In some aspects, the downlink control information may include a field allocated for conveying the CIF value. Additionally or alternatively, the downlink control information may include a field that is not allocated for conveying the CIF value but that the network node and the UE may use to communicate the CIF value. Additionally or alternatively, the network node may include some other values ​​in the downlink control information, and the UE may infer the CIF value based at least in part on these values.

[0108] As further shown in FIG. 7, in some aspects, the process 700 may include communicating with the UE on the one or more cells based at least in part on a mapping between a CIF value and one or more cells (block 720). For example, the network node (e.g., using the communication manager 150 and / or the receiving component 902 or the transmitting component 904 depicted in FIG. 9) may communicate with the UE on the one or more cells based at least in part on a mapping between a CIF value and one or more cells, as described above in conjunction with FIGS. 5A to 5K. In some aspects, the UE may identify the cell on which to communicate based at least in part on the CIF value. For example, the UE may have a mapping between a CIF value and a cell on which the UE is to communicate. In this case, downlink control information including the CIF value may be scheduled to a cell corresponding to the CIF value included in the downlink control information. The UE may store the mapping as a table or other data structure. Based at least in part on the UE identifying the cells on which to communicate, the UE may tune to these cells and transmit or receive, and the network node may monitor these cells and / or transmit on these cells.

[0109] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0110] In a first aspect, the CIF value is mapped from a common scheduling cell to a plurality of cells configured with cross-carrier scheduling for at least one of the plurality of cells.

[0111] In a second aspect, alone or in combination with the first aspect, the downlink control information schedules data on the same cell that conveys the downlink control information.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, the CIF value ranges from 0 to at least 3.

[0113] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the scheduling cell information parameter has an "other" value, and the scheduling cell is mapped to a non-zero CIF value.

[0114] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, sending the downlink control information comprises: sending the downlink control information in a search space set for the downlink control information, wherein a control channel element for a physical downlink control channel candidate associated with the downlink control information is at least partially based on the CIF value.

[0115] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

[0117] In the eighth aspect, alone or in combination with one or more aspects from the first to the seventh aspects, sending the downlink control information includes: for the scheduled cell associated with the CIF value, sending the downlink control information using multiple different downlink control information formats, wherein the multiple different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

[0118] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the first set of scheduled downlink cells is different from the second set of scheduled uplink cells.

[0119] In the tenth aspect, alone or in combination with one or more aspects from the first to the ninth aspects, the CIF value is mapped to a first scheduled downlink cell set and a second scheduled uplink cell set, wherein the second scheduled uplink cell set is a subset of the first scheduled uplink cell set.

[0120] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the size and content of the downlink control information are associated with the CIF value.

[0121] In a twelfth aspect, either alone or in combination with one or more of aspects 1 to eleven, the CIF value is mapped to a cell, and the downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

[0122] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell is different from the first downlink cell or is a subset of the first downlink cell, and the downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align the size with another downlink control information that schedules the other of the first downlink cell or the second uplink cell.

[0123] Although Figure 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged differently than those depicted in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0124] 8 is a diagram of an example apparatus 800 for wireless communication. Apparatus 800 may be a UE, or a UE may include apparatus 800. In some aspects, apparatus 800 includes a receiving component 802 and a sending component 804 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using receiving component 802 and sending component 804. As further shown, apparatus 800 may include a communication manager 140. Communication manager 140 may include monitoring component 808, etc.

[0125] In some aspects, the device 800 may be configured to perform one or more operations described herein in conjunction with Figures 5A to 5K. Additionally or alternatively, the device 800 may be configured to perform one or more processes described herein, such as process 600 of Figure 6. In some aspects, the device 800 and / or one or more components shown in Figure 8 may include one or more components of the UE described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 8 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in the set of components may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0126] The receiving component 802 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 806. The receiving component 802 may provide the received communications to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 800. In some aspects, the receiving component 802 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the UE described in conjunction with FIG. 2.

[0127] The transmitting component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, one or more other components of the device 800 may generate communications, and the generated communications may be provided to the transmitting component 804 for transmission to the device 806. In some aspects, the transmitting component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and may transmit the processed signals to the device 806. In some aspects, the transmitting component 804 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof, of the UE described in conjunction with FIG. 2. In some aspects, the transmitting component 804 may be co-located in a transceiver with the receiving component 802.

[0128] The receiving component 802 may receive downlink control information including a CIF value, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The receiving component 802 and / or the transmitting component 804 may communicate on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0129] Monitoring component 808 can monitor a set of search spaces for downlink control information, wherein a control channel element for a physical downlink control channel candidate associated with the downlink control information is based at least in part on a CIF value. Monitoring component 808 can monitor a plurality of different downlink control information formats for a scheduling cell associated with the CIF value, wherein the plurality of different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

[0130] The number and arrangement of components shown in FIG8 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG8. In addition, two or more components shown in FIG8 may be implemented within a single component, or a single component shown in FIG8 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG8 may perform one or more functions described as being performed by another set of components shown in FIG8.

[0131] 9 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a network node, or a network node may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a sending component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using receiving component 902 and sending component 904. As further shown, apparatus 900 may include a communication manager 150. Communication manager 150 may include configuration component 908, etc.

[0132] In some aspects, the device 900 may be configured to perform one or more operations described herein in conjunction with Figures 5A to 5K. Additionally or alternatively, the device 900 may be configured to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the device 900 and / or one or more components shown in Figure 9 may include one or more components of the network node described in conjunction with Figure 2. Additionally or alternatively, one or more components shown in Figure 9 may be implemented within one or more components described in conjunction with Figure 2. Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0133] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 906. The receiving component 902 may provide the received communications to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the network nodes described in conjunction with FIG. 2.

[0134] The transmitting component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate communications, and the generated communications may be provided to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications, and may transmit the processed signals to the device 906. In some aspects, the transmitting component 904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network nodes described in conjunction with FIG. 2. In some aspects, the transmitting component 904 may be co-located in a transceiver with the receiving component 902.

[0135] The transmitting component 904 may transmit downlink control information including a CIF value to the UE, the CIF value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells. The receiving component 902 or the transmitting component 904 may communicate with the UE on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells. The configuring component 908 may configure the CIF value for the downlink control information transmitted to schedule resources.

[0136] The number and arrangement of the components shown in Figure 9 are provided as examples. In practice, there may be additional components, fewer components, different components, or components arranged in a different manner than those shown in Figure 9. In addition, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.

[0137] The following provides an overview of some aspects of the disclosure:

[0138] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving downlink control information including a carrier indicator field (CIF) value, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and communicating on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0139] Aspect 2: The method according to aspect 1, wherein the CIF value is mapped from a common scheduling cell to a plurality of cells, the plurality of cells being configured with cross-carrier scheduling for at least one of the plurality of cells.

[0140] Aspect 3: The method according to any one of aspects 1 to 2, wherein the downlink control information schedules data on the same cell that transmits the downlink control information.

[0141] Aspect 4: The method according to any one of aspects 1 to 3, wherein the CIF value ranges from 0 to at least 3.

[0142] Aspect 5: The method according to any one of aspects 1 to 4, wherein the scheduling cell information parameter has an "other" value, and the scheduling cell is mapped to a non-zero CIF value.

[0143] Aspect 6: According to the method described in any one of Aspects 1 to 5, the method further includes: monitoring a search space set for the downlink control information, wherein the control channel elements for the physical downlink control channel candidates associated with the downlink control information are at least partially based on the CIF value.

[0144] Aspect 7: The method according to any one of aspects 1 to 6, wherein there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

[0145] Aspect 8: The method according to any one of aspects 1 to 7, wherein there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

[0146] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: monitoring multiple different downlink control information formats for the scheduling cell associated with the CIF value, wherein the multiple different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

[0147] Aspect 10: A method according to any one of Aspects 1 to 9, wherein the CIF value is mapped to a first scheduled downlink cell set and a second scheduled uplink cell set, wherein the first scheduled downlink cell set is different from the second scheduled uplink cell set.

[0148] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the CIF value is mapped to a first scheduled downlink cell set and a second scheduled uplink cell set, wherein the second scheduled uplink cell set is a subset of the first scheduled uplink cell set.

[0149] Aspect 12: The method according to any one of aspects 1 to 11, wherein the size and content of the downlink control information are associated with the CIF value.

[0150] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the CIF value is mapped to a cell, and wherein the downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

[0151] Aspect 14: A method according to any one of Aspects 1 to 13, wherein the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell is different from the first downlink cell or is a subset of the first downlink cell, and wherein the downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align the size with another downlink control information that schedules the other of the first downlink cell or the second uplink cell.

[0152] Aspect 15: A method of wireless communication performed by a network node, the method comprising: sending downlink control information including a carrier indicator field (CIF) value to a user equipment, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; and communicating with the user equipment on the one or more cells based at least in part on a mapping between the CIF value and the one or more cells.

[0153] Aspect 16: The method according to aspect 15, wherein the CIF value is mapped from a common scheduling cell to a plurality of cells, the plurality of cells being configured with cross-carrier scheduling for at least one of the plurality of cells.

[0154] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the downlink control information schedules data on the same cell that transmits the downlink control information.

[0155] Aspect 18: A method according to any one of aspects 15 to 17, wherein the CIF value ranges from 0 to at least 3.

[0156] Aspect 19: The method according to any one of aspects 15 to 18, wherein the scheduling cell information parameter has an "other" value, and the scheduling cell is mapped to a non-zero CIF value.

[0157] Aspect 20: A method according to any one of Aspects 15 to 19, wherein sending the downlink control information includes: sending the downlink control information in a search space set for the downlink control information, wherein the control channel element for the physical downlink control channel candidate associated with the downlink control information is at least partially based on the CIF value.

[0158] Aspect 21: The method according to any one of aspects 15 to 20, wherein there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

[0159] Aspect 22: The method according to any one of aspects 15 to 21, wherein there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

[0160] Aspect 23: A method according to any one of Aspects 15 to 22, wherein sending the downlink control information includes: for a scheduling cell associated with the CIF value, sending the downlink control information using multiple different downlink control information formats, wherein the multiple different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

[0161] Aspect 24: A method according to any one of Aspects 15 to 23, wherein the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the first set of scheduled downlink cells is different from the second set of scheduled uplink cells.

[0162] Aspect 25: A method according to any one of Aspects 15 to 24, wherein the CIF value is mapped to a first scheduled downlink cell set and a second scheduled uplink cell set, wherein the second scheduled uplink cell set is a subset of the first scheduled uplink cell set.

[0163] Aspect 26: A method according to any one of aspects 15 to 25, wherein the size and content of the downlink control information are associated with the CIF value.

[0164] Aspect 27: A method according to any one of Aspects 15 to 26, wherein the CIF value is mapped to a cell, and wherein the downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

[0165] Aspect 28: A method according to any one of Aspects 15 to 27, wherein the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell is different from the first downlink cell or is a subset of the first downlink cell, and wherein the downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align the size with another downlink control information that schedules the other of the first downlink cell or the second uplink cell.

[0166] Aspect 29: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 1 to 14.

[0167] Aspect 30: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of aspects 1 to 14.

[0168] Aspect 31: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 14.

[0169] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 14.

[0170] Aspect 33: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform a method according to one or more of aspects 1 to 14.

[0171] Aspect 34: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to one or more of Aspects 15 to 28.

[0172] Aspect 35: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more aspects of Aspects 15 to 28.

[0173] Aspect 36: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 15 to 28.

[0174] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 15 to 28.

[0175] Aspect 38: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method according to one or more of aspects 15 to 28.

[0176] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.

[0177] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0178] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0179] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. Many of these features can be combined in ways that are not specifically listed in the claims and / or disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of these items (including a single member). As an example, "at least one of a, b, or c" is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0180] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more entries and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: receiving downlink control information including a carrier indicator field (CIF) value, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; as well as Communicating over the one or more cells is performed based at least in part on the mapping between the CIF values ​​and the one or more cells. 2 . The UE of claim 1 , wherein the CIF value is mapped from a common scheduling cell to a plurality of cells, the plurality of cells being configured with cross-carrier scheduling for at least one of the plurality of cells. 3 . The UE of claim 1 , wherein the downlink control information schedules data on the same cell that transmits the downlink control information. The UE according to claim 1 , wherein the CIF value has a value range of 0 to at least 3.

5. The UE of claim 1 , wherein a scheduling cell information parameter has an “other” value, and the scheduling cell is mapped to a non-zero CIF value.

6. The UE of claim 1, wherein the one or more processors are further configured to: A set of search spaces for the downlink control information is monitored, wherein a control channel element for a physical downlink control channel candidate associated with the downlink control information is based at least in part on the CIF value.

7. The UE of claim 1, wherein there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

8. The UE of claim 1, wherein there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

9. The UE of claim 1, wherein the one or more processors are further configured to: A plurality of different downlink control information formats are monitored for a scheduled cell associated with the CIF value, wherein the plurality of different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

10. The UE of claim 1, wherein the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the first set of scheduled downlink cells is different from the second set of scheduled uplink cells.

11. The UE of claim 1, wherein the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the second set of scheduled uplink cells is a subset of the first set of scheduled uplink cells.

12. The UE according to claim 1, wherein the size and content of the downlink control information are associated with the CIF value.

13. The UE according to claim 1, wherein the CIF value is mapped to a cell, and The downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

14. The UE of claim 1, wherein the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell being different from the first downlink cell or being a subset of the first downlink cell, and The downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align a size with another downlink control information scheduling the other of the first downlink cell or the second uplink cell.

15. A network node for wireless communication, the network node comprising: Memory; and one or more processors coupled to the memory and configured to: sending downlink control information including a carrier indicator field (CIF) value to a user equipment, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; as well as Communicating with the user equipment on the one or more cells is performed based at least in part on the mapping between the CIF value and the one or more cells.

16. The network node of claim 15, wherein the CIF value is mapped from a common scheduling cell to a plurality of cells configured with cross-carrier scheduling for at least one of the plurality of cells.

17. The network node of claim 15, wherein the downlink control information schedules data on the same cell that conveys the downlink control information.

18. The network node of claim 15, wherein the CIF value has a value range of 0 to at least 3.

19. The network node of claim 15, wherein a scheduled cell information parameter has an "other" value, and the scheduled cell is mapped to a non-zero CIF value.

20. The network node of claim 15, wherein to send the downlink control information, the one or more processors are configured to: The downlink control information is sent in a search space set for the downlink control information, wherein a control channel element for a physical downlink control channel candidate associated with the downlink control information is based at least in part on the CIF value.

21. The network node of claim 15, wherein there is a one-to-one mapping or a many-to-one mapping of scheduled cells to CIF values.

22. The network node of claim 15, wherein there is a one-to-one mapping, a many-to-one mapping, a one-to-many mapping, or a many-to-many mapping of scheduled cells to CIF values.

23. The network node of claim 15, wherein to send the downlink control information, the one or more processors are configured to: For a scheduled cell associated with the CIF value, the downlink control information is sent using a plurality of different downlink control information formats, wherein the plurality of different downlink control information formats include at least one of a multi-cell scheduling format or a single-cell scheduling format.

24. The network node of claim 15, wherein the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the first set of scheduled downlink cells is different from the second set of scheduled uplink cells.

25. The network node of claim 15, wherein the CIF value is mapped to a first set of scheduled downlink cells and a second set of scheduled uplink cells, wherein the second set of scheduled uplink cells is a subset of the first set of scheduled uplink cells.

26. The network node of claim 15, wherein the size and content of the downlink control information are associated with the CIF value.

27. The network node of claim 15, wherein the CIF value is mapped to a cell, and The downlink control information includes one or more padding bits to align the size with another downlink control information having another CIF value mapped to the cell.

28. The network node of claim 15, wherein the CIF value is mapped to a first downlink cell and a second uplink cell, the second uplink cell being different from the first downlink cell or being a subset of the first downlink cell, and The downlink control information schedules one of the first downlink cell or the second uplink cell and includes one or more padding bits to align a size with another downlink control information scheduling the other of the first downlink cell or the second uplink cell.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving downlink control information including a carrier indicator field (CIF) value, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; as well as Communicating over the one or more cells is performed based at least in part on the mapping between the CIF values ​​and the one or more cells.

30. A method of wireless communication performed by a network node, the method comprising: sending downlink control information including a carrier indicator field (CIF) value to a user equipment, the carrier indicator field (CIF) value identifying one or more cells, the downlink control information being configured to schedule resources on the one or more cells; as well as Communicating with the user equipment on the one or more cells is performed based at least in part on the mapping between the CIF value and the one or more cells.