Physical downlink shared channel resources carrying downlink control information for multiple user equipments

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first user equipment (UE) can receive, from a network node via a physical downlink control channel (PDCCH), first downlink control information (DCI) that includes control information for multiple UEs and indicates resources of a physical downlink shared channel (PDSCH) that carries second DCI without carrying a downlink shared channel, and then can receive the second DCI that includes control information for one or more of the multiple UEs. The first UE can receive an indication of the one or more UEs that have control information in the second DCI, and can determine whether to attempt to decode the second DCI based on whether the one or more UEs that have control information in the second DCI include the first UE. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 635,420, filed April 15, 2024, entitled “PHYSICAL DOWNLINK SHAREDCHANNEL RESOURCES THAT CARRY DOWNLINK CONTROL INFORMATION FOR MULTIPLE USEREQUIPMENTS”, which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for carrying physical downlink shared channel resources for carrying downlink control information for multiple user equipment. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0006] In some aspects, a method of wireless communication performed by a first user equipment (UE) includes: receiving first downlink control information (DCI) from a network node via a physical downlink control channel (PDCCH), the first DCI including control information for a plurality of UEs and indicating resources of a physical downlink shared channel (PDSCH) carrying a second DCI but not a downlink shared channel; receiving the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; receiving from the network node an indication of the one or more UEs having control information in the second DCI; and determining, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI includes the first UE.

[0007] In some aspects, a method of wireless communication performed by a network node includes: transmitting a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources of a PDSCH carrying a second DCI but not a downlink shared channel; transmitting the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and transmitting an indication to the plurality of UEs of the one or more UEs having control information in the second DCI.

[0008] In some aspects, an apparatus for performing wireless communication at a first UE includes: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the first UE to: receive a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; receive the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; receive from the network node an indication of the one or more UEs having control information in the second DCI; and determine, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI includes the first UE.

[0009] In some aspects, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories and configured to cause the network node to: transmit a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; transmit the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and transmit an indication to the plurality of UEs of the one or more UEs having control information in the second DCI.

[0010] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a first UE, cause the first UE to: receive a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; receive the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; receive from the network node an indication to the one or more UEs having control information in the second DCI; and determine, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI includes the first UE.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; transmit the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and transmit an instruction to the plurality of UEs for the one or more UEs having control information in the second DCI.

[0012] In some aspects, an apparatus for wireless communication includes: components for receiving a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; components for receiving the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; components for receiving from the network node an indication of the one or more UEs having control information in the second DCI; and components for determining, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI include the first UE.

[0013] In some aspects, an apparatus for wireless communication includes: means for transmitting a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources of a PDSCH carrying a second DCI but not a downlink shared channel; means for transmitting the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and means for transmitting to the plurality of UEs an indication to the one or more UEs having control information in the second DCI.

[0014] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0015] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

[0019] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0020] Figure 4 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0021] Figures 5 to 11 This is a diagram illustrating an example of a process according to the present disclosure that supports a Physical Downlink Shared Channel (PDSCH) resource carrying downlink control information (DCI) for multiple UEs.

[0022] Figure 12 This is a diagram illustrating an example of signaling exchanged between a network node and a UE according to this disclosure.

[0023] Figure 13 This is a diagram illustrating an example process performed, for example, at the UE or at a device of the UE, according to this disclosure.

[0024] Figure 14 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0025] Figure 15 and Figure 16 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0026] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0027] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0028] Some wireless communication devices (e.g., network nodes, user equipment (UEs)) may rely on downlink control information (DCI) to coordinate communication between devices. For example, a network node may send a DCI to a UE for downlink grant, uplink grant, or some other reason. In some wireless communication networks, a network node may send a DCI on the physical downlink control channel (PDCCH). In this example, the DCI may be delivered via a control resource set (CORESET), and the UE may perform blind decoding on multiple decoding candidates within the CORESET to identify the DCI that includes control information for the UE. In some instances, blind decoding candidates may be organized in a search space set, and one or more search space sets may be associated with a CORESET. Blind decoding that relies on the delivery of DCI via the PDCCH can reduce congestion between UEs by randomly hashing the locations of the PDCCHs from different UEs in different ways within the CORESET. However, blind decoding increases the processing burden at the UE, thereby increasing the complexity at the UE for receiving and decoding the DCI (e.g., compared to DCI communication that does not rely on blind decoding).

[0029] Therefore, some network nodes can offload at least a portion of the control information (e.g., DCI) for the UE from the PDCCH resource, instead transmitting the control information via the PDSCH resource. That is, network nodes can transmit at least a portion of the control information for the UE via the PDSCH resource. In some cases, this technique may be referred to as "DCI on PDSCH". To offload control from the PDCCH resource, network nodes may attempt to reduce the size of the DCI transmitted via the PDCCH resource and may use the PDCCH resource for other UEs (e.g., such as UEs without downlink permission). In some cases, network nodes may transmit variable-length control information via the PDSCH resource, which allows network nodes to align the size of the control information partially transmitted via the PDCCH resource across multiple formats, thereby reducing the blind decoding complexity at the UE.

[0030] Transmitting at least a portion of the DCI via PDSCH resources can reduce the amount of blind decoding (e.g., for PDCCH) that the UE performs to decode the DCI. Additionally, control information (e.g., the DCI) can be communicated more efficiently via PDSCH resources compared to PDCCH resources. That is, the overhead associated with communication via PDSCH resources can be reduced. For example, there may be less Cyclic Redundancy Check (CRC) overhead associated with communication transmitted via PDSCH resources (e.g., due to the reduced CRC length in PDSCH transmission). In some instances, the reduction in CRC length can additionally reduce the amount of pruning performed by the UE to decode the DCI. In another example, PDSCH transmission may rely on a shared demodulation reference signal (DMRS) (e.g., for data DMRS), while PDCCH transmission may rely on a non-shared DMRS.

[0031] Additionally, PDSCH transmission is associated with greater beamforming and rank efficiency compared to PDCCH transmission. Therefore, if a network node transmits control information via PDSCH resources and uses a data rate similar to that used for data transmission via PDSCH, control information can be transmitted more efficiently than via PDCCH resources. Furthermore, network nodes can reduce the transmission rate of control information via PDSCH resources (e.g., compared to the data transmission rate via PDSCH resources) to improve the reliability of control information transmission, while still transmitting control information at a higher transmission rate than via PDCCH resources.

[0032] In some cases where at least a portion of the control information is offloaded to the PDSCH resource, a network node may determine to transmit DCI via the PDSCH resource without transmitting any downlink shared channel transmission (e.g., PDSCH data) via the PDSCH resource. For example, if the size of the control information to be transmitted via the PDSCH resource results in insufficient space for PDSCH data also transmitted via the PDSCH resource, the network node may transmit only DCI via the PDSCH resource (e.g., and may not transmit any downlink shared channel transmission via the PDSCH resource). Additionally or alternatively, the PDSCH payload size may not take into account the DCI payload size, and the impact on PDSCH decoding may be unnecessarily high. Therefore, a network node may choose to transmit DCI via the PDSCH resource without including any downlink shared channel transmission in the PDSCH resource. That is, a network node may transmit only DCI via the PDSCH resource.

[0033] If a network node transmits DCI-only via PDSCH resources in unicast mode (e.g., for a UE), the DCI-only transmission in the PDSCH resources may include UE-specific control information for that UE. The UE may perform blind decoding on unicast DCI received via PDCCH resources based on the UE's identifier (e.g., the UE's Cell Radio Network Temporary Identifier (C-RNTI)), and the unicast DCI received via PDSCH resources may not include the UE identifier.

[0034] In some other examples, network nodes may transmit DCI-only via PDSCH resources in multicast or multicast mode (e.g., for multiple UEs). Here, the DCI transmitted via PDSCH resources may include control information for a group of UEs (e.g., group-specific control information), and thus the network node can address that group of UEs in the control information transmitted via PDSCH resources. Subsequently, the DCI transmitted via PDSCH resources may include UE-specific control information for one or more UEs in that group. That is, the network node may transmit multiple grants (e.g., downlink grants, uplink grants) to one or more UEs in the DCI transmitted via PDSCH resources.

[0035] The various aspects generally involve network nodes transmitting control information via resources associated with the PDSCH in broadcast or multicast modes, but not via resources associated with the PDSCH (e.g., data, downlink shared channel transport blocks). Some aspects more specifically involve encoding and decoding operations associated with control information transmitted via PDCCH resources and control information transmitted via PDSCH resources. For example, a network node can encode control information transmitted via PDCCH resources using identifiers associated with a group of UEs. Therefore, the group of UEs receiving the control information via PDCCH resources can decode the control information. Additionally, the network node can configure the group of UEs such that each UE in the group can identify and decode the portion of the DCI carried via the PDSCH resources that includes control information for that UE. Thus, via PDSCH resources carrying DCI but not the downlink shared channel, the network node can transmit and the group of UEs can receive the DCI.

[0036] Various other aspects more specifically relate to instances where one or more UEs receiving a DCI via PDCCH resources do not receive any control information via PDSCH resources. For example, a network node may transmit a DCI via PDCCH resources that includes group-specific control information for a group of UEs, and may transmit a DCI via PDSCH resources that includes UE-specific control information for one or more first UEs in that group but not UE-specific control information for one or more second UEs in that group. In this example, the network node may transmit, and the UEs may receive, signaling indicating that one or more first UEs have control information in the DCI carried by the PDSCH resources. Subsequently, each UE in the group may determine whether to attempt to decode at least a portion of the DCI received via PDSCH resources based on whether the UE is indicated to have control information in the DCI received via PDSCH resources (e.g., based on whether the UE is one of one or more first UEs).

[0037] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some cases, by enabling each UE in a group of UEs to identify and decode a portion of the DCI carried via PDSCH resources that includes control information for that UE, the network node and UEs can utilize resources for transmitting control information more efficiently (e.g., compared to a case where the network node transmits all control information via PDCCH). Additionally, by indicating to the group of UEs that one or more UEs have control information in the DCI transmitted via PDSCH resources, each UE can avoid attempting to decode DCI transmissions that do not include control information for that UE, thereby reducing power consumption at the UE.

[0038] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0039] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0040] Figure 1This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0041] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NRRATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0042] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency 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.

[0043] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0044] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0045] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0046] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0047] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0048] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0049] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Various types of network nodes 110 can typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100 compared to other types of network nodes 110. For example, macro network nodes can have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0050] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit DCI (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more PDCCHs (PDCCHs), and downlink data channels may include one or more physical downlink shared channels (PDSCHs). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0051] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0052] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0053] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0054] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0055] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.

[0056] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0057] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0058] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR-Lite UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0059] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can send and receive sidelink communication using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0060] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0061] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0062] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; receive the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; receive from the network node an indication to the one or more UEs having control information in the second DCI; and determine, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI includes the first UE. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0063] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may transmit a first DCI to a plurality of UEs via PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; transmit the second DCI, including control information for the one or more of the plurality of UEs, via the resources of the PDSCH; and transmit to the plurality of UEs an indication to the one or more UEs having control information in the second DCI. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0064] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0065] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0066] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0067] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “processor,” “controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0068] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0069] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0070] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., TA set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).

[0071] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0072] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0073] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0074] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0075] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0076] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0077] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, may perform MIMO detection on the received symbols where applicable, and may provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, may provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and may provide the decoded control information and system information to controller / processor 280.

[0078] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0079] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or cyclic prefix OFDM (CP-OFDM)). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output symbol streams (e.g., U A set of output symbol streams is provided to a set of modems 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0080] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or UUplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmissions made directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0081] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0082] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0083] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0084] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0085] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0086] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in one or more network nodes. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0087] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0088] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0089] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0090] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0091] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may perform corrective actions using AI / ML models via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0092] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0093] Network node 110, network node 110's controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340 or Figure 1 , Figure 2 or Figure 3 Any other component may implement one or more technologies or perform one or more operations associated with PDSCH resources carrying DCI for multiple UEs, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 13 Process 1300 Figure 14The operation of process 1400 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 13 Process 1300 Figure 14 The process 1400 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0094] In some aspects, the first UE (e.g., UE 120) includes: components for receiving a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; components for receiving the second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; components for receiving from the network node an indication to the one or more UEs having control information in the second DCI; and / or components for determining, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI include the first UE. Components for enabling the first UE to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0095] In some aspects, a network node (e.g., network node 110) includes: components for transmitting a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; components for transmitting the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and / or components for transmitting an indication to the plurality of UEs of the one or more UEs having control information in the second DCI. Components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TX MIMO processor 216, 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.

[0096] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0097] Figure 4 This is a diagram illustrating example 400 of a wireless communication network according to this disclosure. For example... Figure 4 As shown, network node 110 and UEs 120-a, 120-b, 120-c and 120-n can communicate with each other.

[0098] In Example 400, network node 110 may send DCI 410-a to UE 120 via PDCCH resource 405. Additionally, network node 110 may send an additional DCI 410-b to UE 120 via PDSCH resource 415. In some cases, when network node 110 sends DCI 410 to UE 120 via two parts (e.g., a first part delivered to UE 120 via PDCCH resource 405 in DCI 410-a, and a second part delivered to UE 120 via PDSCH resource 415 in DCI 410-b), the first part of DCI 410-a delivered via PDCCH resource 405 may be referred to as DCI1, and the second part of DCI 410-b delivered via PDSCH resource 415 may be referred to as DCI2. Network node 110 may send a first subset of control information for UE 120 (e.g., DCI1, DCI 410-a) via PDCCH resource 405, and may send a second subset of control information for UE 120 (e.g., DCI2, DCI 410-b) via PDSCH resource 415.

[0099] In DCI 410-a, network node 110 can send control information to a group of UEs 120 (e.g., multiple UEs 120), which may include, for example, UE 120-a, UE 120-b, UE 120-c, and UE 120-n (and one or more additional UEs 120). For example, DCI 410-a can be sent via broadcast, multicast, or multicast through PDCCH resource 405. That is, network node 110 can operate in broadcast, multicast, or multicast mode when sending DCI 410-a. Therefore, DCI 410-a can include control information for all UEs 120 in the group of UEs 120.

[0100] DCI 410-a may be associated with a search space set and CORESET decoded by each UE 120 in the group of UEs 120 (e.g., UE 120-a, UE 120-b, UE 120-c, UE 120-n, and one or more additional UEs 120). In some instances, to ensure that each UE 120 in the group of UEs 120 can decode DCI 410, the identifier associated with DCI 410 may be shared by the group of UEs 120. For example, DCI 410-a may include a shared Radio Network Temporary Identifier (RNTI), such as a System Information RNTI (SI-RNTI) or a Paging RNTI (P-RNTI). Additionally, the format of DCI 410-a and the search space of DCI 410-a may be shared by each UE in the group of UEs 120. Specifically, network node 110 can be configured with a group common search space associated with DCI410-a, shared by each UE in the group of UEs 120.

[0101] DCI 410-a may include basic information about PDSCH resource 415, including the resource allocation associated with PDSCH resource 415, the rank associated with PDSCH resource 415, and the modulation order associated with PDSCH resource 415. In some cases, the information about PDSCH resource 415 included in DCI 410-a may enable UE 120 to perform DMRS-based channel estimation and to perform demodulation of transmissions received via PDSCH resource 415.

[0102] Network node 110 may additionally include in DCI 410-a a field containing information about DCI 410-b transmitted via PDSCH resource 415. For example, DCI 410-a may include a size field containing information related to the size of DCI 410-b (e.g., the number of resource elements). Additionally or alternatively, the size field may include information about the code rate of DCI 410-b (e.g., payload size). DCI 410-a may additionally include the time-domain resource allocation (TDRA) and / or frequency-domain resource allocation (FDRA) of DCI 410-b to be transmitted via PDSCH resource 415, the rank of DCI 410-b, or other information related to DCI 410-b. In some instances, the information related to DCI 410-b included in DCI 410-a may indicate rate control information associated with DCI 410-b.

[0103] In DCI 410-b, network node 110 may transmit the remainder of the DCI for UE 120. In some cases, DCI 410-b may include UE-specific control information for a subset of UE 120 in the group of UE 120 (e.g., one or more of the plurality of UE 120s receiving DCI 410-a). For example, DCI 410-b may include multiple sets of control information including UE-specific control information. In example 400, DCI 410-b may include a first set of control information for UE 120-a (e.g., DCI 420-a for UE1), a second set of control information for UE 120-b (e.g., DCI 420-b for UE2), and a third set of control information for UE 120-n (e.g., DCI 420-c for UEn).

[0104] DCI 410-b may include a set of control information that is jointly encoded or separately encoded. For example, DCI 410-b may include a shared CRC, and network node 110 may use, for example, polar codes with a shared CRC and / or low-density parity check (LDPC) to jointly encode the set of control information (e.g., DCI 420-a for UE1, DCI 420-b for UE2, and DCI 420-c for UEn). In another example, DCI 410-b may include a CRC for each UE 120 that has control information in DCI 410-b. For example, DCI 410-b may include a first CRC associated with UE 120-a, a second CRC associated with UE 120-b, and a third CRC associated with UE 120-n. Here, network node 110 may use, for example, polar codes and / or LDPC with CRC associated with each UE 120 to encode the set of control information (e.g., DCI 420-a for UE1, DCI 420-b for UE2 and DCI 420-c for UEn).

[0105] For example, network node 110 may include information related to downlink granting for UE 120 in DCI 410-b, such as Hybrid Automatic Repeat Request (HARQ) process identifier, Redundancy Version (RV) identifier, and / or New Data Indicator. DCI 410 may additionally include other non-time-critical information, such as Transmit Power Control (TPC) information, CSI triggering information, SRS triggering information, Downlink Assignment Index (DAI), uplink granting (e.g., including FDD uplink granting or TDD with uplink granting for later time slots), or other downlink granting (e.g., downlink granting for later time slots, downlink granting for multiple transmission time intervals (multiple TTIs), or multi-time slot granting).

[0106] In Example 400, network node 110 may transmit DCI 410-b via each PDSCH resource in PDSCH resource 415, and may not include any downlink shared channel in PDSCH resource 415. That is, all PDSCH resources in PDSCH resource 415 may carry DCI 410-b, and there may be no remaining PDSCH resources 415 for carrying downlink shared channels. Therefore, in Example 400, PDSCH resource 415 may carry DCI 410-b without carrying downlink shared channels.

[0107] To ensure that each UE 120 containing control information in DCI 410-b can decode at least a portion of the DCI 410-b including control information for that respective UE 120, network node 110 can configure UE 120 such that each UE 120 containing control information in DCI 410-b can identify and decode a portion of the DCI 410-b carried via PDSCH resource 415, including control information for that UE 120. Therefore, network node 110 can transmit and the group of UEs 120 can receive DCI 410-b via PDSCH resource 415 carrying DCI 410-b but not the downlink shared channel.

[0108] Additionally, network node 110 may send, and UE 120 may receive, signaling indicating that one or more UEs 120 have control information in DCI 410-b carried by PDSCH resource 415. Subsequently, each UE 120 in the group may determine whether to attempt to decode at least a portion of DCI 410-b based on whether that UE 120 is indicated to have control information in DCI 410-b. In Example 400, network node 110 may send signaling indicating that UEs 120-a, 120-b, and 120-n have control information in at least a portion of DCI 410-b. Therefore, UEs 120-a, 120-b, and 120-n may attempt to decode at least a portion of DCI 410-b (e.g., DCI 420-a for UE1, DCI 420-b for UE2, and DCI 420-c for UEn) that includes control information for UE 120, based on signaling instructing DCI 410-b to include control information for UE 120, 120-b, and 120-n, respectively. Additionally, UE 120-c may avoid attempting to decode at least a portion of DCI 410-b based on signaling instructing DCI 410-b to include control information for UE 120, 120-b, and 120-n but not instructing DCI 410-b to include control information for UE 120-c.

[0109] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0110] Figure 5 This is a diagram illustrating Example 500 of a process that supports carrying PDSCH resources for DCIs of multiple UEs according to this disclosure. In some cases, Example 500 may include information regarding... Figure 4The described aspects of Example 400. For example, DCI 510 may include aspects of DCI 410-b. That is, a network node may send DCI 510 to a group of UEs via a set of PDSCH resources (e.g., without carrying a downlink shared channel).

[0111] DCI 510 may correspond to DCI2 and may include one or more sets of UE-specific control information. For example, DCI 510 may include a first set of control information for UE1 (e.g., DCI 520-a for UE1), a second set of control information for UE2 (e.g., DCI 520-b for UE2), and a third set of control information for UEn (e.g., DCI 520-c for UEn). Network nodes may encode DCI 510 to ensure that each UE having control information in DCI 510 is able to decode at least a portion of DCI 510 including control information for that UE.

[0112] In Example 500, a network node may encode DCI 510 (e.g., the entire contents of DCI 510) into a codeword and append a single CRC 515. For example, the network node may encode DCI 510 using polar codes or LDPC. Network node 110 may scramble the CRC 515 using identifiers common to the group of UEs (e.g., including UE1, UE2, and UEn). For example, network node 110 may scramble the CRC 515 using broadcast or multicast RNTIs (e.g., SI-RNTI, P-RNTI).

[0113] Network nodes may include a UE-specific identifier (e.g., UE ID 530) in the payload of the DCI for each UE 520. For example, DCI 520-a for UE1 may include UE ID 530-a in its payload; DCI 520-b for UE2 may include UE ID 530-b in its payload; and DCI 520-c for UEn may include UE ID 530-c in its payload. UE ID 530 may be a UE-specific identifier, such as a C-RNTI. Additionally or alternatively, UE ID 530 may be a shorter (e.g., fewer bits) UE-specific identifier than a C-RNTI that may include up to 16 bits. For example, UE ID 530 may alternatively include a portion of the C-RNTI corresponding to each UE. Here, the first part of the C-RNTI may be included in the UE ID 530 (e.g., 8 bits of the C-RNTI), and the second part of the C-RNTI may be included in the MAC Protocol Data Unit (PDU) (e.g., when permitted to be transmitted with the associated PDSCH). In another example, the network node may configure a UE ID 530 for each UE in the group (e.g., multiple UEs receiving multicast / multicast / broadcast DCI via PDCCH resources), where the configured UE ID 530 is shorter than the UE-specific C-RNTI. Here, each UE ID 530 may indicate one UE in the group.

[0114] As indicated by reference numeral 505, the UE can decode DCI 510. For example, the UE can decode the entire DCI 510 carried by the PDSCH resource to obtain a DCI for decoding UE 525. That is, after decoding the entire DCI 510, each UE can obtain DCI 525-a for decoding UE1, DCI 525-b for decoding UE2, and DCI 525-c for decoding UEn. Subsequently, each UE can identify a portion of the DCI 510 containing control information for that UE based on the UE ID 530 included in each set of decoded control information (e.g., in the DCI for decoding UE 525). For example, UE1 can identify the control information for UE1 as DCI 525-a for decoding UE1 based on the UE ID 530-a corresponding to UE1 included in the DCI 525-a for decoding UE1.

[0115] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0116] Figure 6This is a diagram illustrating Example 600 of a process that supports carrying PDSCH resources for DCIs of multiple UEs according to this disclosure. In some cases, Example 600 may include information regarding... Figure 4 The aspects of Example 400 described. For example, DCI 610 may include aspects of DCI 410-b. That is, a network node may send DCI 610 to a group of UEs via a set of PDSCH resources (e.g., without carrying a downlink shared channel).

[0117] DCI 610 may correspond to DCI2 and may include one or more sets of UE-specific control information. For example, DCI 610 may include a first set of control information for UE1 (e.g., DCI 620-a for UE1), a second set of control information for UE2 (e.g., DCI 620-b for UE2), and a third set of control information for UEn (e.g., DCI 620-c for UEn). Network nodes may encode DCI 610 to ensure that each UE having control information in DCI 610 is able to decode at least a portion of DCI 610 including control information for that UE.

[0118] In Example 600, a network node may encode each set of control information in DCI 610 (e.g., for each DCI of UE 620). For example, DCI 610 may additionally include a CRC for each UE having control information in DCI 610. That is, DCI 610 may include CRC 615-a for UE1, CRC 615-b for UE2, and CRC 615-c for UEn. To encode DCI 610, a network node may encode the DCI for each UE 615 separately and append its own corresponding CRC.

[0119] Network nodes can also scramble each CRC using the UE-specific identifier corresponding to the UE. For example, a network node can encode DCI 620-a for UE1 and append CRC 615-a for UE1, and scramble the CRC 615-a for UE1 using the UE-specific identifier for UE1. The UE-specific identifier may include a C-RNTI. Additionally or alternatively, the UE-specific identifier may be a shorter (e.g., including fewer bits) UE-specific identifier than a C-RNTI that may include up to 16 bits. For example, the UE-specific identifier may alternatively include a portion of the C-RNTI corresponding to each UE. Here, the first portion of the C-RNTI can be used to scramble the CRC for each UE. In another example, a network node may configure a UE-specific identifier for each UE in the group of UEs (e.g., multiple UEs receiving multicast / multicast / broadcast DCI via PDCCH resources), wherein the configured UE-specific identifier is shorter than the UE-specific C-RNTI.

[0120] As shown by reference numeral 605 in the accompanying drawings, the UE can decode DCI 610 (e.g., to obtain a decoded DCI for UE 625) and identify a portion of DCI 610 including control information for that UE based on a CRC check. That is, the UE can perform a CRC check on each CRC for UE 615 and identify the decoded DCI for UE 625 including control information for that UE in response to a passing CRC check (e.g., in response to successful descrambling of the CRC using a UE-specific identifier corresponding to that UE). For example, in response to successful descrambling of CRC 615-b for UE2 using a UE-specific identifier for UE2, UE2 can identify that portion of DCI 610 including control information for UE2 is DCI 625-b for UE2. In some cases, because the UE can use a CRC check to identify that portion of the DCI including control information for that UE (e.g., regardless of control information including a UE-specific identifier), the DCI for each UE (e.g., 620 and 625) may not include the UE-specific identifier for the corresponding UE.

[0121] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0122] Figure 7 This is a diagram illustrating Example 700 of a process that supports carrying PDSCH resources for DCI of multiple UEs according to this disclosure. In some cases, Example 700 may include information regarding... Figure 4The aspects of Example 400 described. For example, DCI 710 may include aspects of DCI 410-b. That is, a network node may send DCI 710 to a group of UEs via a set of PDSCH resources (e.g., without carrying a downlink shared channel).

[0123] DCI 710 may correspond to DCI2 and may include one or more sets of UE-specific control information. For example, DCI 710 may include a first set of control information for UE1 (e.g., DCI 720-a for UE1), a second set of control information for UE2 (e.g., DCI 720-b for UE2), and a third set of control information for UEn (e.g., DCI 720-c for UEn). Network nodes may encode DCI 710 to ensure that each UE having control information in DCI 710 is able to decode at least a portion of DCI 710 including control information for that UE.

[0124] In Example 700, the network node may encode the header 715 of DCI 710 via polar coding or LDPC. The network node may include in the header 715 an indication of the UE associated with each set of control information in DCI 710. For example, header 715 may indicate that DCI 720-a for UE1 is associated with UE1, DCI 720-b for UE2 is associated with UE2, and DCI 720-c for UEn is associated with UEn. In some cases, header 715 may use a UE-specific identifier to associate each set of control information in DCI 710 with a UE. The UE-specific identifier may include a C-RNTI. Additionally or alternatively, the UE-specific identifier may be a shorter (e.g., including fewer bits) UE-specific identifier than a C-RNTI that may include up to 16 bits. For example, the UE-specific identifier may alternatively include a portion of the C-RNTI corresponding to each UE. Here, the first portion of the C-RNTI may be used to scramble the CRC for each UE. In another example, the network node may configure a UE-specific identifier for each UE in the group (e.g., multiple UEs receiving multicast / multicast / broadcast DCI via PDCCH resources), wherein the configured UE-specific identifier is shorter than the UE-specific C-RNTI.

[0125] As indicated by reference numeral 705, the UE may decode DCI 710. For example, the UE may decode the header 715 of DCI 710 to identify one or more portions of DCI 710 that include control information for the UE. In some cases, the UE may then decode the identified portions of DCI 710 to obtain a decoded DCI for the UE 725. For example, header 715 may indicate that DCI 720-a for UE1 includes control information for UE1, and UE1 may then decode DCI 720-a for UE1 to obtain a decoded DCI 725-a for UE1. Additionally or alternatively, the UE may decode the entire DCI 710 to obtain each decoded DCI in the decoded DCI for UE 725. Subsequently, each UE may determine, based on the information included in header 715, which (if any) decoded DCIs include control information for the UE.

[0126] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0127] Figure 8 This is a diagram illustrating example 800 of a process that supports carrying PDSCH resources for DCIs of multiple UEs according to this disclosure. In some cases, example 800 may include information regarding... Figure 4 The described aspects of Example 400. For example, the DCI carried via PDCCH 815 may include aspects of DCI 410-a, while the DCI carried via PDSCH 810 may include aspects of DCI 410-b. That is, a network node may send control information for a group of UEs via DCI carried via PDCCH 815, and may send UE-specific control information for one or more UEs in that group via DCI carried via PDSCH 810.

[0128] The DCI carried via PDSCH 810 may correspond to DCI2 and may include one or more sets of UE-specific control information. For example, the DCI carried via PDSCH 810 may include a first set of control information for UE1 (e.g., DCI820-a for UE1), a second set of control information for UE2 (e.g., DCI820-b for UE2), and a third set of control information for UEn (e.g., DCI820-c for UEn). The network node may configure the UEs such that each UE having control information in the DCI carried via PDSCH 810 is capable of decoding at least a portion of the DCI carried via PDSCH 810, including control information for that UE.

[0129] In Example 800, the DCI carried via PDCCH 815 may have control information 835 (e.g., control information for the group of UEs) and may also include an association field 840. A network node may send indications of the UEs associated with each set of control information in the DCI carried via PDSCH 810 via the association field 840 in the DCI carried via PDCCH 815. For example, the association field 840 may indicate that DCI 820-a for UE1 is associated with UE1, DCI 820-b for UE2 is associated with UE2, and DCI 820-c for UEn is associated with UEn. In some cases, the association field 840 may use the UE's UE-specific identifier to associate each set of control information in the DCI carried via PDSCH 810 with the UE. The UE-specific identifier may include a C-RNTI. Additionally or alternatively, the UE-specific identifier may be a shorter (e.g., fewer bits) UE-specific identifier than a C-RNTI that may include up to 16 bits. For example, a UE-specific identifier may alternatively include a portion of the C-RNTI corresponding to each UE. Here, the first portion of the C-RNTI can be used to scramble the CRC for each UE. In another example, the network node may configure a UE-specific identifier for each UE in the group of UEs (e.g., multiple UEs receiving multicast / multicast / broadcast DCI via PDCCH resources), wherein the configured UE-specific identifier is shorter than the UE-specific C-RNTI.

[0130] As indicated by reference numeral 805, the UE can decode the DCI carried by PDSCH 810. For example, the UE can decode the associated field 840 in the DCI carried by PDCCH 815. Based on the decoding of the associated field 840, the UE can identify one or more portions of the DCI carried by PDSCH 810 that include control information for the UE. In some cases, the UE can then decode the identified portion of the DCI carried by PDSCH 810 to obtain the decoded DCI for the UE 825. For example, the associated field 840 may indicate that DCI 820-a for UE1 includes control information for UE1, and UE1 can then decode DCI 820-a for UE1 to obtain DCI 825-a for UE1. Additionally or alternatively, the UE can decode the entire DCI carried by PDSCH 810 to obtain the decoded DCI 825 for the UE. Subsequently, each UE can determine, based on the information included in the associated field 840, which (if any) decoded DCIs include control information for that UE.

[0131] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0132] Figure 9 This is a diagram illustrating Example 900 of a process that supports carrying PDSCH resources for DCIs of multiple UEs according to this disclosure. In some cases, Example 900 may include information regarding... Figure 4 The described aspects of Example 400. For example, the DCI carried via PDCCH 915 may include aspects of DCI 410-a, while the DCI carried via PDSCH 910 may include aspects of DCI 410-b. That is, a network node may send control information for a group of UEs via the DCI carried via PDCCH 915, and may send UE-specific control information for one or more UEs in that group via the DCI carried via PDSCH 910.

[0133] In Example 900, the DCI carried via PDSCH 910 may include one or more sets of UE-specific control information. For example, the DCI carried via PDSCH 910 may include a first set of control information for UE2 (e.g., DCI 920-a for UE2) and a second set of control information for UEn (e.g., DCI 920-b for UEn). Additionally, the DCI carried via PDSCH 910 may not include UE-specific control information for one or more UEs in the group of UEs that receive the DCI carried via PDCCH 915. For example, the DCI carried via PDSCH 910 may not include UE-specific control information for UE1. The network node may configure the UEs such that each UE having control information in the DCI carried via PDSCH 910 is capable of decoding at least a portion of the DCI carried via PDSCH 910, including control information for that UE.

[0134] A network node can send, and the group of UEs can receive, signaling indicating that one or more UEs have control information in the DCI carried via PDSCH 910. For example, a network node can send signaling indicating that UE2 and UEn have control information in the DCI. In Example 900, a network node can send signaling via the DCI carried via PDCCH 915. For example, the DCI carried via PDCCH 915 may include an indication to a UE with a DCI carried via PDSCH 940.

[0135] In one example, an indication to a UE carrying a DCI via PDSCH 940 may be carried by one or more unused fields in the DCI carried via PDCCH 915. Specifically, in cases where PDSCH resources carry the DCI without carrying any downlink shared channel, the HARQ field within the DCI carried via PDSCH 940 may be unused because the information within the DCI carried via PDSCH 910 may be time-critical and may not require retransmission (e.g., via a HARQ acknowledgment (HARQ-ACK) procedure). Therefore, an indication to a UE carrying a DCI via PDSCH 940 may be carried by unused HARQ fields in the DCI carried via PDCCH 915. Unused HARQ fields may include, for example, a HARQ identifier field, an RV identifier field, and / or a New Data Indicator (NDI) field.

[0136] In a first instance, where the indication to a UE with DCI carried via PDSCH 940 is carried by one or more unused HARQ fields of the DCI carried via PDCCH 915, the UE may reinterpret the one or more unused HARQ fields as a hash function (e.g., a function with many inputs to a few outputs). In another instance, where the indication to a UE with DCI carried via PDSCH 940 is carried by one or more unused HARQ fields of the DCI carried via PDCCH 915, a new field in PDCCH 915 (e.g., having the same number of bits as the one or more unused HARQ fields) may carry the indication to the UE with DCI carried via PDSCH 940.

[0137] In any instance, the indication of a UE carrying a DCI via PDSCH 940 can use a hash function to indicate one or more UEs that have control information in the DCI carried via PDSCH 910. For example, a network node can configure a small number (e.g., one or two) of indicator bits in the DCI carried via PDCCH 915 to carry an indication of a UE carrying a DCI via PDSCH 940. These bits can indicate which UEs have control information (e.g., are assigned a DCI component) in the DCI carried via PDSCH 910. For example, the location of the indicator bits in the DCI carried via PDSCH 915 can be determined via a hash algorithm that maps the UE-specific identifier of the UE that has control information in the DCI carried via PDSCH 910 to a single output. Subsequently, each UE in this group of UEs can determine, based on the location of the indicator bits and the hash algorithm, whether the DCI carried via PDSCH 910 includes control information for that UE.

[0138] In another example, the indication of a UE with a DCI carried via PDSCH 940 may be carried by a field in a DCI carried via PDCCH 915, and may include a list of UE-specific identifiers of the UE that have control information in a DCI carried via PDSCH 910.

[0139] As indicated by reference numeral 905 in the accompanying drawings, upon receiving an instruction to one or more UEs that have control information in the DCI carried via PDSCH 910, each UE in that group of UEs may determine whether to attempt to decode the DCI carried via PDSCH 910. For example, if a UE determines that the instruction to one or more UEs that have control information in the DCI carried via PDSCH 910 is directed to it, then the UE may attempt to decode the DCI carried via PDSCH 910. Additionally, if a UE determines that the instruction to one or more UEs that have control information in the DCI carried via PDSCH 910 is not directed to it (e.g., the UE is not included in one or more UEs that have control information in the DCI carried via PDSCH 910), then the UE may avoid decoding the DCI carried via PDSCH 910.

[0140] In Example 900, UE2 and UEn may determine that one or more UEs indicated as having control information in the DCI carried via PDSCH 910 include UE2 and UEn, and therefore may attempt to decode the DCI carried via PDSCH 910 to obtain DCI 925-b for decoding of UE2 and DCI 925-c for decoding of UEn. Additionally, UE1 may determine that one or more UEs indicated as having control information in the DCI carried via PDSCH 910 do not include UE1, and therefore may avoid attempting to decode the DCI carried via PDSCH 910.

[0141] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0142] Figure 10 This is a diagram illustrating Example 1000 of a process that supports carrying PDSCH resources for DCIs of multiple UEs according to this disclosure. In some cases, Example 1000 may include information regarding... Figure 4 The aspects of Example 400 described. For example, DCI 1010 may include aspects of DCI 410-b. That is, a network node may send control information for a group of UEs via a DCI (e.g., DCI1) carried by PDCCH resources, and may send UE-specific control information for one or more UEs in that group of UEs via DCI 1010, wherein DCI 1010 is carried by PDSCH resources carrying DCI 1010 but not carrying the downlink shared channel.

[0143] In Example 1000, DCI 1010 may include one or more sets of UE-specific control information. For example, DCI 1010 may include a first set of control information for UE1 (e.g., DCI 1020-a for UE1) and a second set of control information for UEn (e.g., DCI 1020-b for UEn). Additionally, DCI 1010 may not include UE-specific control information for one or more UEs in the group of UEs. For example, DCI 1010 may not include UE-specific control information for UE2. The network node may configure the UEs such that each UE having control information in DCI 1010 is able to decode at least a portion of DCI 1010, including control information for that UE.

[0144] A network node can send, and the group of UEs can receive, signaling indicating that one or more UEs have control information in DCI 1010. For example, a network node can send signaling indicating that UE1 and UEn have control information in DCI 1010. In Example 1000, the network node can send this signaling via header 1015 in DCI 1010. In Example 1000, DCI 1010 can be configured according to a two-stage structure, wherein the first stage may include header 1015, and the second stage includes UE-specific control information (e.g., DCI 1020-a for UE1 and DCI 1020-b for UEn). Here, as indicated by reference numeral 1005, each of the UEs in the group can decode header 1015, and as indicated by reference numeral 1035, one or more UEs (e.g., indicated by header 1015) that are indicated as having control information in DCI 1010 can decode at least a portion of DCI 1010 having UE-specific control information are indicated as indicated by reference numeral 1035.

[0145] In some cases, the DCI (e.g., DCI1) transmitted via PDCCH may indicate the size of header 1015 (e.g., via TDRA, FDRA, and / or bit length). To enable each UE in the group of UEs to decode header 1015 (as indicated by reference numeral 1005), header 1015 may include its own DMRS with a specific pattern. For example, the network node may indicate the pattern of the DMRS used in header 1015 via a DCI carried through PDCCH resources. Additionally, the network node may encode header 1015 so that the UEs can decode header 1015 using CRC-based polar codes. In some cases, header 1015 may have a smaller size (e.g., the TDRA, FDRA, and / or bit length associated with header 1015 may be smaller), enabling the group of UEs to decode header 1015 quickly (e.g., compared to larger headers). In some instances, the DMRS and resource elements in header 1015 can be frequency-division multiplexed (FDM), which can further reduce the size of header 1015. Here, the FDRA DMRS pattern of header 1015 can include aspects of the frequency-domain DMRS pattern. For example, the DMRS and header resource elements of header 1015 can be FDMed at a frequency-domain density of 25% or 33%. Additionally or alternatively, the TDRA DMRS pattern of the DMRS in header 1015 can be based on the TDRA of header 1015.

[0146] To indicate one or more UEs having control information in DCI 1010, header 1015 may include a list of UE-specific identifiers. Here, header 1015 may additionally indicate the association between the UE-specific identifiers and a set of control information in DCI 1010 (e.g., DCI 1020-a for UE1 and DCI 1020-b for UEn). If the header indicates the association between the UE-specific identifiers and a set of control information in DCI 1010, then the set of control information in DCI 1010 (e.g., DCI payload, DCI components for the UE, DCI 1020 for the UE) may not include the UE-specific identifiers.

[0147] Upon receiving an instruction to one or more UEs that have control information in DCI 1010, each UE in that group of UEs may determine whether to attempt to decode the remainder of DCI 1010 (e.g., the portion including UE-specific control information) (as indicated by reference numeral 1035). For example, if a UE determines that the instruction to one or more UEs that have control information in DCI 1010 is directed to it, then the UE may attempt to decode DCI 1010. Additionally, if a UE determines that the instruction to one or more UEs that have control information in DCI 1010 is not directed to it (e.g., the UE is not included in one or more UEs that have control information in DCI 1010), then the UE may avoid decoding DCI 1010.

[0148] In Example 1000, UE1 and UEn may be determined to be one or more UEs indicated as having control information in DCI 1010, including UE1 and UEn, and therefore may attempt to decode DCI 1010 (as indicated by reference numeral 1035) to obtain DCI 1025-a for decoding of UE1 and DCI 1025-c for decoding of UEn. Additionally, UE2 may be determined to be one or more UEs indicated as having control information in DCI 1010, excluding UE2, and therefore may avoid attempting to decode DCI 1010.

[0149] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0150] Figure 11 This is an illustration of Example 1100, which demonstrates a process for supporting PDSCH resources carrying DCI for multiple UEs according to this disclosure. In some cases, Example 1100 may include information regarding... Figure 4 The aspects of Example 400 described. For example, DCI 1110 may include aspects of DCI 410-b. That is, a network node may transmit control information for a group of UEs via a DCI (e.g., DCI1) carried by PDCCH resources, and may transmit UE-specific control information for one or more UEs in that group of UEs via DCI 1110, wherein DCI 1110 is carried by PDSCH resources carrying DCI 1110 but not the downlink shared channel. Example 1100 may additionally include references Figure 10 The described aspects of Example 1000. For example, DCI1110 may include aspects of DCI 1010, such as configuration according to a two-stage structure.

[0151] In Example 1100, DCI 1110 may include one or more sets of UE-specific control information. For example, DCI 1110 may include a first set of control information for UE1 (e.g., DCI 1120-a for UE1), a third set of control information for UE1 (e.g., DCI 1120-b for UE1), and a second set of control information for UEn (e.g., DCI 1120-b for UEn). Additionally, DCI 1110 may not include UE-specific control information for one or more UEs in the group of UEs. For example, DCI 1110 may not include UE-specific control information for UE2. The network node may configure the UEs such that each UE having control information in DCI 1110 is able to decode at least a portion of DCI 1110, including control information for that UE.

[0152] A network node can send, and the group of UEs can receive, signaling indicating that one or more UEs have control information in DCI 1110. For example, a network node can send signaling indicating that UE1 and UEn have control information in DCI 1110. In Example 1100, the network node can send this signaling via header 1115 in DCI 1110. In Example 1100, DCI 1110 can be configured according to a two-stage structure, wherein the first stage may include header 1115, and the second stage includes UE-specific control information (e.g., DCI 1120-a for UE1 and DCI 1120-b for UEn). Here, as indicated by reference numeral 1105, each of the UEs in the group can decode header 1115, and as indicated by reference numeral 1135, one or more UEs (e.g., indicated by header 1115) that are indicated as having control information in DCI 1110 can decode at least a portion of DCI 1110 having UE-specific control information are indicated as indicated by reference numeral 1135.

[0153] Header 1115 may indicate one or more UEs having control information in DCI 1110 via a hash algorithm. Here, header 1115 may be based on a hash algorithm associated with a UE-specific identifier of the UE having control information in DCI 1110. To determine whether the UE has UE-specific control information in DCI 1110, each UE may apply a hash check algorithm to header 1115. In this example, the set of control information in DCI 1110 (e.g., the DCI payload, DCI components for the UE, DCI 1120 for the UE) may include UE-specific identifier 1130.

[0154] Upon receiving an instruction for one or more UEs that have control information in DCI 1110, each UE in that group of UEs may determine whether to attempt to decode the remainder of DCI 1110 (e.g., the portion including UE-specific control information). For example, if a UE determines that the instruction for one or more UEs that have control information in DCI 1110 is directed to it, then the UE may attempt to decode DCI 1110. Additionally, if a UE determines that the instruction for one or more UEs that have control information in DCI 1110 is not directed to it (e.g., the UE is not included in one or more UEs that have control information in DCI 1110), then the UE may avoid decoding DCI 1110.

[0155] In Example 1100, UE1 and UEn may determine that one or more UEs indicated as having control information in DCI 1110 include UE1 and UEn, and therefore may attempt to decode DCI 1110 to obtain DCI 1125-a for UE1, DCI 1125-b for UE1, and DCI 1125-c for UEn. Additionally, UE2 may determine that one or more UEs indicated as having control information in DCI 1110 do not include UE2, and therefore may avoid attempting to decode DCI 1110. The UE may determine, based on the UE-specific identifier 1130 included in DCI 1110, which determines which set of decoded control information includes control information for that UE. For example, UE1 may determine, based on UE IDs 1130-a and 1130-b being UE-specific identifiers for UE1, that DCI 1125-a and 1125-b for UE1 include control information for UE1. Additionally, UEn may identify the DCI used for decoding UEn 1125-c based on UE ID 1130-c being a UE-specific identifier for UEn, including control information for UEn.

[0156] As indicated above, Figure 11 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 11 The examples described are different.

[0157] Figure 12 This is a diagram illustrating example 1200 of signaling exchanged between network node 110 and UE 120 according to this disclosure. In some cases, network node 110 and UE 120 described with reference to wireless communication network 400 may implement aspects of example 1200.

[0158] As shown by reference numeral 1205 in the accompanying drawings, via the PDCCH, network node 110 can send and UE 120 can receive a first DCI (e.g., DCI1), which includes control information for multiple UEs and indicates resources for carrying a second DCI without carrying the downlink shared channel PDSCH. In some cases, the first DCI may include a DCI shared among multiple UEs (e.g., non-UE-specific control information).

[0159] As shown by reference numeral 1210 in the accompanying drawings, network node 110 may encode a second DCI (e.g., DCI2) for transmission via PDSCH resources. In some cases, the second DCI may include a UE-specific DCI for one or more of a plurality of UEs.

[0160] As shown by reference numeral 1215 in the attached figure, network node 110 can send and UE 115 can receive a second DCI that includes control information for one or more of a plurality of UEs.

[0161] As shown by reference numeral 1220 in the attached figure, network node 110 can send instructions to UE 120, which can receive instructions to one or more UEs that have control information in the second DCI.

[0162] As shown by reference numeral 1225 in the accompanying drawings, UE 120 may optionally attempt to decode at least a portion of the second DCI, at least in part, based on whether one or more UEs having control information in the second DCI include UE 120. For example, if one or more UEs having control information in the second DCI include the first UE, then UE 120 may attempt to decode at least that portion of the second DCI to obtain control information for UE 120. Additionally, if one or more UEs having control information in the second DCI do not include UE 120, then UE 120 may avoid decoding at least that portion of the second DCI.

[0163] As indicated above, Figure 12 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 12 The examples described are different.

[0164] Figure 13 This is a diagram illustrating an example process 1300 performed, for example, at a first UE or a device of a UE, according to this disclosure. Example process 1300 is an example in which a device or UE (e.g., UE 120) performs operations associated with PDSCH resources carrying DCIs for multiple UEs.

[0165] like Figure 13As shown, in some aspects, process 1300 may include: receiving a first DCI from a network node via PDCCH, the first DCI including control information for multiple UEs and indicating resources for carrying a second DCI but not a downlink shared channel PDSCH (box 1310). For example, the first UE (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described herein may receive a first DCI from a network node via PDCCH as described above. The first DCI includes control information for multiple UEs and indicates resources for carrying a second DCI but not a downlink shared channel PDSCH.

[0166] like Figure 13 Further shown, in some aspects, process 1300 may include: receiving the second DCI from the network node via the resource of the PDSCH, the second DCI including control information for one or more of the plurality of UEs (box 1320). For example, the first UE (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described herein may receive the second DCI from the network node via the resource of the PDSCH as described above, the second DCI including control information for one or more of the plurality of UEs.

[0167] like Figure 13 Further shown, in some aspects, process 1300 may include: receiving from the network node an indication to one or more UEs that have control information in the second DCI (block 1330). For example, a first UE (e.g., using...) Figure 15 The receiving component 1502 and / or communication manager 1506 described herein can receive instructions from the network node to the one or more UEs having control information in the second DCI, as described above.

[0168] like Figure 13 Further shown, in some aspects, process 1300 may include: determining, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having the control information in the second DCI include the first UE (block 1340). For example, the first UE (e.g., using...) Figure 15 The communication manager 1506 described above may determine whether to attempt to decode at least a portion of the second DCI based at least in part on whether the one or more UEs having the control information in the second DCI include the first UE.

[0169] Process 1300 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 in this document.

[0170] In a first aspect, process 1300 includes: attempting to decode at least a portion of the second DCI based at least in part on the one or more UEs, including the first UE, that have the control information in the second DCI to obtain control information for the first UE.

[0171] In a second aspect, process 1300 includes: attempting to decode at least a portion of the second DCI based at least in part on an identifier associated with the first UE, the second DCI including multiple sets of control information, each including control information for one of the one or more UEs.

[0172] In a third aspect, attempting to decode at least a portion of the second DCI includes descrambling the cyclic redundancy check in the second DCI using an identifier associated with the first UE, wherein the identifier is associated with the plurality of UEs, and process 1300 includes: identifying the one or more sets of control information from the plurality of sets of control information based at least in part on one or more sets of control information including control information for the first UE, including a UE-specific identifier of the first UE.

[0173] In the fourth aspect, attempting to decode at least a portion of the second DCI includes attempting to descramble multiple cyclic redundancy checks in the second DCI, each associated with one of the plurality of sets of control information, using the identifier associated with the first UE, wherein the identifier includes a UE-specific identifier of the first UE; and process 1300 includes: identifying the one or more sets of control information from the plurality of sets of control information in response to successfully descrambling one or more cyclic redundancy checks associated with one or more sets of control information including control information for the first UE using the UE-specific identifier of the first UE.

[0174] In a fifth aspect, attempting to decode at least a portion of the second DCI includes decoding the header of the second DCI, the header indicating a UE associated with each subset of the plurality of sets of control information among the one or more UEs; and process 1300 includes: identifying the one or more sets of control information from the plurality of sets of control information based at least in part on the header of the second DCI indicating that one or more sets of control information including control information for the first UE are associated with the first UE.

[0175] In a sixth aspect, process 1300 includes: decoding a field in the first DCI that indicates a UE associated with each subset of the plurality of sets of control information in the one or more UEs; and identifying the one or more sets of control information from the plurality of sets of control information based at least in part on the field in the first DCI indicating that the one or more sets of control information in the second DCI, including control information for the first UE, are associated with the first UE.

[0176] In the seventh aspect, the identifier includes at least a portion of a UE-specific RNTI, broadcast RNTI, multicast RNTI, or group RNTI configured by the network node.

[0177] In the eighth aspect, process 1300 includes: avoiding attempts to decode at least a portion of the second DCI to obtain control information for the first UE, based at least in part on the fact that the one or more UEs having the control information in the second DCI do not include the first UE.

[0178] In the ninth aspect, receiving the instruction includes receiving the instruction via the PDCCH.

[0179] In the tenth aspect, the indication includes a plurality of bits that indicate, via a hash algorithm, the one or more UEs having the control information in the second DCI.

[0180] In the eleventh aspect, the first DCI includes one or more UE identifiers corresponding to the one or more UEs.

[0181] In a twelfth aspect, process 1300 includes: decoding the header of the second DCI, the header including the indication of the one or more UEs having the control information in the second DCI, wherein determining whether to attempt to decode at least the portion of the second DCI is based at least in part on whether the one or more UEs indicated in the header of the second DCI include the first UE.

[0182] In a thirteenth aspect, process 1300 includes: the header of the second DCI includes one or more UE identifiers corresponding to the one or more UEs; the header of the second DCI indicates, for each of the one or more UEs, a PDSCH resource carrying control information for a corresponding UE among the one or more UEs; and process 1300 includes: attempting to decode at least a portion of the second DCI carried by the PDSCH resource carrying the control information for the first UE, based at least in part on the fact that the one or more UE identifiers in the header of the second DCI include a first UE identifier corresponding to the first UE.

[0183] In a fourteenth aspect, process 1300 includes: the header of the second DCI includes a plurality of bits indicating, via a hash algorithm, the one or more UEs having the control information in the second DCI; the second DCI includes a plurality of sets of control information, each for one of the one or more UEs; and the second DCI includes a plurality of UE identifiers, each corresponding to a corresponding set of the plurality of sets of control information, the one or more UE identifiers indicating, for the corresponding set of the plurality of sets of control information, a UE associated with the corresponding set of the plurality of sets of control information among the one or more UEs.

[0184] although Figure 13 An example box of process 1300 is shown, but in some respects, process 1300 may include... Figure 13 The boxes depicted in the text are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1300 may be executed in parallel.

[0185] Figure 14 This is a diagram illustrating an example process 1400 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1400 is an example in which a device or network node (e.g., network node 110) performs operations associated with PDSCH resources carrying DCIs for multiple UEs.

[0186] like Figure 14 As shown, in some aspects, process 1400 may include: transmitting a first DCI to a plurality of UEs via PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel (box 1410). For example, a network node (e.g., using...) Figure 16 The transmitting component 1604 and / or communication manager 1606 described herein may transmit a first DCI to a plurality of UEs via PDCCH as described above. The first DCI includes control information for the plurality of UEs and indicates resources for a PDSCH carrying a second DCI but not a downlink shared channel.

[0187] like Figure 14 Further shown, in some aspects, process 1400 may include: sending the second DCI, which includes control information for the one or more UEs among the plurality of UEs, via the resource of the PDSCH (box 1420). For example, a network node (e.g., using...) Figure 16The transmitting component 1604 and / or communication manager 1606 described herein may transmit the second DCI to one or more of the plurality of UEs via the resource of the PDSCH as described above, the second DCI including control information for the one or more of the plurality of UEs.

[0188] like Figure 14 Further shown, in some aspects, process 1400 may include: sending an instruction to the plurality of UEs to the one or more UEs that have control information in the second DCI (block 1430). For example, a network node (e.g., using...) Figure 16 The transmitting component 1604 and / or the communication manager 1606 described herein can transmit instructions to the plurality of UEs, as described above, to the one or more UEs that have control information in the second DCI.

[0189] Process 1400 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 in this document.

[0190] although Figure 14 An example box of process 1400 is shown, but in some respects, process 1400 may include... Figure 14 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1400 may be executed in parallel.

[0191] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a UE, or a UE may include device 1500. In some aspects, device 1500 includes a receiving component 1502, a transmitting component 1504, and / or a communication manager 1506 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1506 is combined with... Figure 1 The described communication manager 140. As shown, device 1500 can communicate with another device 1508 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1502 and transmitting component 1504.

[0192] In some respects, device 1500 can be configured to perform the functions described herein. Figures 4 to 12 One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 13 The process is 1300. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0193] Receiver 1502 may receive communications from device 1508, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 1500. In some aspects, receiver 1502 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0194] Transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1508. In some aspects, one or more other components of device 1500 may generate communications and provide the generated communications to transmitting component 1504 for transmission to device 1508. In some aspects, transmitting component 1504 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 device 1508. In some aspects, transmitting component 1504 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1504 may co-located with the receive component 1502 in one or more transceivers.

[0195] The communication manager 1506 may support the operation of the receiving component 1502 and / or the transmitting component 1504. For example, the communication manager 1506 may receive information associated with configuring the reception of communications by the receiving component 1502 and / or the transmission of communications by the transmitting component 1504. Additionally or alternatively, the communication manager 1506 may generate control information and / or provide control information to the receiving component 1502 and / or the transmitting component 1504 to control the reception and / or transmission of communications.

[0196] The receiving component 1502 can receive a first DCI from the network node via the PDCCH. The first DCI includes control information for multiple UEs and indicates resources for a PDSCH carrying a second DCI but not a downlink shared channel. The receiving component 1502 can receive the second DCI from the network node via the resources of the PDSCH. The second DCI includes control information for one or more of the multiple UEs. The receiving component 1502 can receive from the network node an indication for the one or more UEs that have control information in the second DCI. The communication manager 1506 can determine, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs that have control information in the second DCI include the first UE.

[0197] The communication manager 1506 may attempt to decode at least a portion of the second DCI to obtain control information for the first UE, based at least in part on the one or more UEs, including the first UE, that have the control information in the second DCI.

[0198] The communication manager 1506 may attempt to decode at least a portion of the second DCI based at least in part on an identifier associated with the first UE, the second DCI comprising multiple sets of control information, each including control information for one of the one or more UEs.

[0199] The communication manager 1506 can decode the field in the first DCI that indicates a UE associated with each subset of the plurality of sets of control information in the one or more UEs.

[0200] The communication manager 1506 may identify the one or more sets of control information from the plurality of sets of control information by at least partially based on the field in the first DCI indicating that one or more sets of control information, including control information for the first UE, are associated with the first UE in the second DCI.

[0201] The communication manager 1506 may avoid attempting to decode at least a portion of the second DCI to obtain control information for the first UE, based at least in part on the fact that the one or more UEs having the control information in the second DCI do not include the first UE.

[0202] The communication manager 1506 can decode the header of the second DCI, which includes the indication to the one or more UEs having the control information in the second DCI, wherein determining whether to attempt to decode at least the portion of the second DCI is based at least in part on whether the one or more UEs indicated in the header of the second DCI include the first UE.

[0203] Figure 15 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 15 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The collection of (one or more) components shown is executable and described as being composed of Figure 15 Another set of components shown performs one or more functions.

[0204] Figure 16 This is a diagram of an example device 1600 for wireless communication according to the present disclosure. Device 1600 may be a network node, or a network node may include device 1600. In some aspects, device 1600 includes a receiving component 1602, a transmitting component 1604, and / or a communication manager 1606 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 1606 is combined with... Figure 1 The described communication manager 150. As shown, device 1600 can communicate with another device 1608 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1602 and transmitting component 1604.

[0205] In some respects, device 1600 can be configured to perform the functions described herein. Figures 4 to 11 One or more operations described herein. Additionally or alternatively, the apparatus 1600 may be configured to perform one or more processes described herein, such as Figure 14 The process is 1400. In some respects, Figure 16 The illustrated device 1600 and / or one or more components may include a combination Figure 2One or more components of the described network node. Additionally or alternatively, Figure 16 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0206] Receiver 1602 may receive communications from device 1608, such as reference signals, control information, data communications, or combinations thereof. Receiver 1602 may provide the received communications to one or more other components of device 1600. In some aspects, receiver 1602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1600. In some aspects, receiver 1602 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1602 and / or transmitter component 1604 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1600 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0207] Transmitting component 1604 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1608. In some aspects, one or more other components of device 1600 may generate communications and provide the generated communications to transmitting component 1604 for transmission to device 1608. In some aspects, transmitting component 1604 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 device 1608. In some aspects, transmitting component 1604 may include combinations of... Figure 2The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1604 may co-located with the receive component 1602 in one or more transceivers.

[0208] The communication manager 1606 may support the operation of the receiving component 1602 and / or the transmitting component 1604. For example, the communication manager 1606 may receive information associated with configuring the reception of communications by the receiving component 1602 and / or the transmission of communications by the transmitting component 1604. Additionally or alternatively, the communication manager 1606 may generate control information and / or provide control information to the receiving component 1602 and / or the transmitting component 1604 to control the reception and / or transmission of communications.

[0209] Transmitting component 1604 can transmit a first DCI to multiple UEs via PDCCH. The first DCI includes control information for the multiple UEs and indicates resources for a PDSCH carrying a second DCI but not a downlink shared channel. Transmitting component 1604 can transmit the second DCI, which includes control information for the one or more UEs, via the resources of the PDSCH. Transmitting component 1604 can also transmit an indication to the one or more UEs that have control information in the second DCI.

[0210] Figure 16 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 16 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 16 The two or more components shown can be implemented within a single component, or Figure 16 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 16 The collection of (one or more) components shown is executable and described as being composed of Figure 16 Another set of components shown performs one or more functions.

[0211] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a first UE, the method comprising: receiving a first DCI from a network node via a PDCCH, the first DCI including control information for a plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; receiving a second DCI from the network node via the resources of the PDSCH, the second DCI including control information for one or more of the plurality of UEs; receiving from the network node an indication of the one or more UEs having control information in the second DCI; and determining, at least in part, whether to attempt to decode at least a portion of the second DCI based on whether the one or more UEs having control information in the second DCI includes the first UE.

[0212] Aspect 2: According to the method of aspect 1, the method further includes: attempting to decode at least a portion of the second DCI based at least in part on the one or more UEs having the control information in the second DCI, including the first UE, to obtain control information for the first UE.

[0213] Aspect 3: According to the method of aspect 2, the method further includes: attempting to decode at least a portion of the second DCI based at least in part on an identifier associated with the first UE, the second DCI comprising a plurality of sets of control information each including control information for one of the one or more UEs.

[0214] Aspect 4: The method according to aspect 3, wherein: attempting to decode at least a portion of the second DCI includes descrambling the cyclic redundancy check in the second DCI using the identifier associated with the first UE, wherein the identifier is associated with the plurality of UEs; and the method further includes identifying the one or more sets of control information from the plurality of sets of control information based at least in part on a UE-specific identifier of the first UE, which includes one or more sets of control information including control information for the first UE.

[0215] Aspect 5: The method according to aspect 3, wherein: attempting to decode at least a portion of the second DCI includes attempting to descramble multiple cyclic redundancy checks in the second DCI, each associated with one of the plurality of sets of control information, using the identifier associated with the first UE, wherein the identifier includes a UE-specific identifier of the first UE; and the method further includes identifying the one or more sets of control information from the plurality of sets of control information in response to successfully descrambling one or more cyclic redundancy checks associated with one or more sets of control information including control information for the first UE using the UE-specific identifier of the first UE.

[0216] Aspect 6: The method according to aspect 3, wherein: attempting to decode at least a portion of the second DCI includes decoding the header of the second DCI, the header indicating a UE associated with each subset of the plurality of sets of control information among the one or more UEs; and the method further includes identifying the one or more sets of control information from the plurality of sets of control information by at least partially based on the header of the second DCI indicating that one or more sets of control information including control information for the first UE are associated with the first UE.

[0217] Aspect 7: The method according to aspect 3, the method further comprising: decoding a field in the first DCI indicating a UE associated with each subset of the plurality of sets of control information in the one or more UEs; and identifying the one or more sets of control information from the plurality of sets of control information by at least partially based on the field in the first DCI indicating that one or more sets of control information in the second DCI, including control information for the first UE, are associated with the first UE.

[0218] Aspect 8: The method according to aspect 3, wherein the identifier includes at least a portion of a UE-specific RNTI, broadcast RNTI, multicast RNTI, or group RNTI configured by the network node.

[0219] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: avoiding attempts to decode at least said portion of the second DCI to obtain control information for the first UE based at least in part on the fact that the one or more UEs having the control information in the second DCI do not include the first UE.

[0220] Aspect 10: The method according to any one of aspects 1 to 9, wherein receiving the instruction includes receiving the instruction via the PDCCH.

[0221] Aspect 11: According to the method of aspect 10, the indication includes a plurality of bits, the plurality of bits indicating the one or more UEs having the control information in the second DCI via a hash algorithm.

[0222] Aspect 12: According to the method of aspect 10, wherein the first DCI includes one or more UE identifiers corresponding to the one or more UEs.

[0223] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: decoding the header of the second DCI, the header including the indication to the one or more UEs having the control information in the second DCI, wherein determining whether to attempt to decode at least the portion of the second DCI is based at least in part on whether the one or more UEs indicated in the header of the second DCI include the first UE.

[0224] Aspect 14: The method according to aspect 13, wherein: the header of the second DCI includes one or more UE identifiers corresponding to the one or more UEs; the header of the second DCI indicates, for each of the one or more UEs, a PDSCH resource carrying control information for a corresponding UE among the one or more UEs; and the method further includes, at least in part, attempting to decode, based on the fact that the one or more UE identifiers in the header of the second DCI include a first UE identifier corresponding to the first UE, by means of at least said portion of the second DCI carried as the PDSCH resource carrying the control information for the first UE.

[0225] Aspect 15: The method according to aspect 13, wherein: the header of the second DCI includes a plurality of bits, the plurality of bits indicating, via a hash algorithm, the one or more UEs having the control information in the second DCI; the second DCI includes a plurality of sets of control information, each for one of the one or more UEs; and the second DCI includes a plurality of UE identifiers, each corresponding to a corresponding set of the plurality of sets of control information, the one or more UE identifiers indicating, for the corresponding set of the plurality of sets of control information, a UE associated with the corresponding set of the plurality of sets of control information among the one or more UEs.

[0226] Aspect 16: A method for wireless communication performed by a network node, the method comprising: transmitting a first DCI to a plurality of UEs via a PDCCH, the first DCI including control information for the plurality of UEs and indicating resources for a PDSCH carrying a second DCI but not a downlink shared channel; transmitting the second DCI to one or more of the plurality of UEs via the resources of the PDSCH, the second DCI including control information for the one or more of the plurality of UEs; and transmitting an indication to the plurality of UEs of the one or more UEs having control information in the second DCI.

[0227] Aspect 17: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 16.

[0228] Aspect 18: An apparatus for wireless communication at a device, the apparatus comprising one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 16.

[0229] Aspect 19: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 16.

[0230] Aspect 20: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 16.

[0231] Aspect 21: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 16.

[0232] Aspect 22: A device for wireless communication, the device including a processing system comprising one or more processors; and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 16.

[0233] Aspect 23: An apparatus for wireless communication at a device, the apparatus comprising one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 16.

[0234] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0235] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0236] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0237] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: 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 of the same element (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).

[0238] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0239] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for performing wireless communication at a first user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the first UE to: The network node receives first downlink control information (DCI) via the physical downlink control channel (PDCCH). The first DCI includes control information for multiple UEs and indicates resources of the physical downlink shared channel (PDSCH) that carry a second DCI but not a downlink shared channel. The second DCI is received from the network node via the resources of the PDSCH, and the second DCI includes control information for one or more of the plurality of UEs; Receive instructions from the network node to the one or more UEs that have control information in the second DCI; as well as Whether to attempt to decode at least a portion of the second DCI is determined at least in part based on whether the one or more UEs having the control information in the second DCI include the first UE.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the first UE to: At least in part, based on the fact that one or more UEs, including the first UE, have the control information in the second DCI, they attempt to decode at least a portion of the second DCI to obtain control information for the first UE.

3. The apparatus of claim 2, wherein the one or more processors are further configured to cause the first UE to: At least a portion of the second DCI is attempted to be decoded based at least in part on an identifier associated with the first UE, the second DCI comprising multiple sets of control information, each including control information for one of the one or more UEs.

4. The apparatus according to claim 3, wherein: In order to attempt to decode at least a portion of the second DCI, the one or more processors are configured to cause the first UE to descramble the cyclic redundancy check in the second DCI using the identifier associated with the first UE, wherein the identifier is associated with the plurality of UEs; and The one or more processors are further configured to cause the first UE to identify the one or more sets of control information from the plurality of sets of control information, at least in part, based on one or more sets of control information including a UE-specific identifier of the first UE.

5. The apparatus according to claim 3, wherein: In order to attempt to decode at least a portion of the second DCI, the one or more processors are configured to cause the first UE to attempt to descramble multiple cyclic redundancy checks in the second DCI, each associated with one of a plurality of sets of control information, using the identifier associated with the first UE, wherein the identifier includes a UE-specific identifier of the first UE; and The one or more processors are further configured to cause the first UE to identify the one or more sets of control information from the plurality of sets of control information in response to successfully descrambling one or more cyclic redundancy checks associated with one or more sets of control information including control information for the first UE using the UE-specific identifier of the first UE.

6. The apparatus according to claim 3, wherein: In order to attempt to decode at least a portion of the second DCI, the one or more processors are configured to cause the first UE to decode the header of the second DCI, the header indicating one of the one or more UEs associated with each subset of the plurality of sets of control information; and The one or more processors are further configured to cause the first UE to associate one or more sets of control information, including control information for the first UE, with the header indication of the second DCI at least in part, to identify the one or more sets of control information from the plurality of sets of control information.

7. The apparatus of claim 3, wherein the one or more processors are further configured to cause the first UE to: Decoding the field in the first DCI that indicates a UE associated with each subset of the plurality of sets of control information in the one or more UEs; and The control information is identified from the plurality of sets of control information by at least partly based on the fields in the first DCI indicating that one or more sets of control information, including control information for the first UE, are associated with the first UE.

8. The apparatus of claim 3, wherein the identifier includes at least a portion of a UE-specific radio network temporary identifier (RNTI), broadcast RNTI, multicast RNTI, or group RNTI configured by the network node.

9. The apparatus of claim 1, wherein the one or more processors are further configured to cause the first UE to: At least in part, based on the fact that the one or more UEs having the control information in the second DCI do not include the first UE, attempts are avoided to decode at least the portion of the second DCI to obtain control information for the first UE.

10. The apparatus of claim 1, wherein, in order for the first UE to receive the indication, the one or more processors are configured to cause the first UE to receive the indication via the PDCCH.

11. The apparatus of claim 10, wherein the indication comprises a plurality of bits, the plurality of bits indicating, via a hash algorithm, the one or more UEs having the control information in the second DCI.

12. The apparatus of claim 10, wherein the first DCI includes one or more UE identifiers corresponding to the one or more UEs.

13. The apparatus of claim 1, wherein the one or more processors are further configured to cause the first UE to: The header of the second DCI is decoded, the header including the indication to the one or more UEs that have the control information in the second DCI. The determination of whether to attempt to decode at least a portion of the second DCI is based at least in part on whether the one or more UEs indicated in the header of the second DCI include the first UE.

14. The apparatus according to claim 13, wherein: The header of the second DCI includes one or more UE identifiers corresponding to the one or more UEs; The header of the second DCI indicates, for each of the one or more UEs, a PDSCH resource carrying control information for the corresponding UE among the one or more UEs; and The one or more processors are further configured to cause the first UE to attempt to decode, at least in part, a portion of the second DCI carried as a PDSCH resource containing control information for the first UE, based on the one or more UE identifiers in the header of the second DCI, including a first UE identifier corresponding to the first UE.

15. The apparatus according to claim 13, wherein: The header of the second DCI includes a plurality of bits, which are hashed to indicate the one or more UEs that have the control information in the second DCI; The second DCI includes multiple sets, each for control information used by one of the one or more UEs; and The second DCI includes a plurality of UE identifiers, each corresponding to a corresponding set among the plurality of sets of control information, the one or more UE identifiers indicating, for the corresponding set among the plurality of sets of control information, a UE among the one or more UEs associated with the corresponding set among the plurality of sets of control information.

16. A method for wireless communication performed by a first user equipment (UE), the method comprising: The network node receives first downlink control information (DCI) via the physical downlink control channel (PDCCH). The first DCI includes control information for multiple UEs and indicates resources of the physical downlink shared channel (PDSCH) that carry a second DCI but not a downlink shared channel. The second DCI is received from the network node via the resources of the PDSCH, and the second DCI includes control information for one or more of the plurality of UEs; Receive instructions from the network node to the one or more UEs that have control information in the second DCI; as well as Whether to attempt to decode at least a portion of the second DCI is determined at least in part based on whether the one or more UEs having the control information in the second DCI include the first UE.

17. The method according to claim 16, further comprising: At least in part, based on the fact that one or more UEs, including the first UE, have the control information in the second DCI, they attempt to decode at least a portion of the second DCI to obtain control information for the first UE.

18. The method according to claim 17, further comprising: At least a portion of the second DCI is attempted to be decoded based at least in part on an identifier associated with the first UE, the second DCI comprising multiple sets of control information, each including control information for one of the one or more UEs.

19. The method of claim 18, wherein: Attempting to decode at least a portion of the second DCI includes descrambling the cyclic redundancy check (CRC) in the second DCI using the identifier associated with the first UE, wherein the identifier is associated with the plurality of UEs; and The method further includes identifying the one or more sets of control information from the plurality of sets of control information based at least in part on one or more sets of control information including a UE-specific identifier of the first UE.

20. 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 first user equipment (UE), cause the first UE to: The network node receives first downlink control information (DCI) via the physical downlink control channel (PDCCH). The first DCI includes control information for multiple UEs and indicates resources of the physical downlink shared channel (PDSCH) that carry a second DCI but not a downlink shared channel. The second DCI is received from the network node via the resources of the PDSCH, and the second DCI includes control information for one or more of the plurality of UEs; Receive instructions from the network node to the one or more UEs that have control information in the second DCI; as well as Whether to attempt to decode at least a portion of the second DCI is determined at least in part based on whether the one or more UEs having the control information in the second DCI include the first UE.

Images