Controlling resource set performing

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive signaling identifying a control resource set (CORESET) puncturing mode, the CORESET puncturing mode based at least in part on a number of resource blocks available before and after the CORESET puncturing procedure and a number of symbols of the CORESET. The UE may decode the downlink control information according to the CORESET puncturing mode. Numerous other aspects are described.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 518,042, filed August 7, 2023, entitled “CONTROL RESOURCE SETPUNCTURING,” and U.S. Non-Provisional Patent Application No. 18 / 542,463, filed December 15, 2023, entitled “CONTROL RESOURCE SET PUNCTURING,” assigned to the assignee of this application. The disclosures of these earlier applications are considered part of this patent application and are incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication and techniques and apparatus for controlling resource set censorship. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

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

[0005] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. New Radio (NR) (which may be referred to as 5G) is an enhancement set to the LTE mobile standard issued by 3GPP. NR is designed to better support mobile broadband internet access by: improving spectrum efficiency; reducing costs; improving service; utilizing new spectrum; and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink; and supporting beamforming, Multiple-Input Multiple-Output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0006] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to receive signaling for a CORESET pruning pattern, which is at least in part based on the number of resource blocks available before and after the CORESET pruning process and the number of symbols in the CORESET. The one or more processors may be individually or collectively configured to decode downlink control information according to the CORESET pruning pattern.

[0007] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to output signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. The one or more processors may be individually or collectively configured to configure a UE to decode downlink control information according to the CORESET truncation mode.

[0008] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include receiving signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. The method may include decoding downlink control information according to the CORESET truncation mode.

[0009] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include outputting signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. The method may include configuring a UE to decode downlink control information according to the CORESET truncation mode.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed individually or jointly by one or more processors of the UE, the set of instructions enables the UE to receive signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. When executed by one or more processors of the UE, the set of instructions enables the UE to decode downlink control information according to the CORESET truncation mode.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed individually or jointly by one or more processors of the network node, the set of instructions enables the network node to output signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. When executed individually or jointly by one or more processors of the network node, the set of instructions enables the network node to configure a UE to decode downlink control information according to the CORESET truncation mode.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving signaling identifying a CORESET pruning mode, the CORESET pruning mode being at least in part based on the number of resource blocks available before and after the CORESET pruning process and the number of symbols in the CORESET. The apparatus may include components for decoding downlink control information according to the CORESET pruning mode.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for outputting signaling identifying a CORESET truncation mode, the CORESET truncation mode being at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. The apparatus may also include components for configuring a UE to decode downlink control information according to the CORESET truncation mode.

[0014] The entirety of the terms includes methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the accompanying drawings and description and illustrated as illustrated in the drawings and description.

[0015] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, in both their organization and manner of operation, and the associated advantages, will be better understood by considering the following description in conjunction with the accompanying drawings. Each drawing provided in the drawings is for illustrative and descriptive purposes and not as a limitation of the definitions in the claims.

[0016] While aspects are described herein by way of example, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / shopping devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0017] To gain a full understanding of the foregoing features of this disclosure, a more specific description of the brief overview can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered as limiting its scope, as other equally valid aspects may be acknowledged in this description. The same reference numerals in different drawings may identify the same or similar elements.

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

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

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

[0021] Figure 4 This is a diagram illustrating an example resource structure for wireless communication according to the present disclosure.

[0022] Figure 5 This is a diagram illustrating an example of the control resource set (CORESET) pruning pattern associated with this disclosure.

[0023] Figures 6 to 11This is an illustration illustrating an example of the CORESET truncation mode associated with this disclosure.

[0024] Figure 12 This is a diagram illustrating an example of decoding downlink control information signals according to this disclosure.

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

[0026] 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 this disclosure.

[0027] Figure 15 This is a diagram of an example device for wireless communication according to the present disclosure.

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

[0029] The Control Resource Set (CORESET) addresses the challenges associated with managing and controlling data transmission across different frequency bands. A CORESET is a predefined set of Physical Resource Blocks (PRBs) in the frequency domain and time slots in the time domain reserved for control channel transmissions, including scheduling assignments, system control information, and other network commands. CORESET enables the network to deliver control signals to User Equipment (UE) in a consistent and structured manner, while also providing mechanisms for dynamically scheduling transmissions on a per-UE basis. Furthermore, the flexibility of CORESET configuration helps to utilize spectrum more effectively and improve capacity. Therefore, CORESET allows the network to maintain robust and reliable communication and optimize user experience, especially in high-demand wireless communication environments.

[0030] CORESET truncation is a technique in which control signals transmitted via CORESET are intentionally left blank or "truncated" in certain situations, particularly to limit transmission to a limited bandwidth, or in other situations, to allow the transmission of other potentially higher-priority data. CORESET truncation facilitates resource allocation in a dynamic and flexible manner, where specific network requirements or needs can be prioritized as required. For example, if the network has limited transmission bandwidth within the carrier bandwidth, CORESET can be designed to truncate a legacy CORESET with the minimum bandwidth to a CORESET with limited transmission bandwidth, such as truncating a legacy minimum of 24 resource blocks (RBs) CORESET to 15-RB CORESET within a 3MHz channel bandwidth, or truncating a legacy minimum of 24-RB CORESET to 20-RB CORESET within a 5MHz channel bandwidth. For example, if the network is facing high data traffic demands, CORESET truncation can be used to free up space for the transmission of additional data, thereby effectively improving network efficiency and capacity. However, excessive or inappropriate CORESET truncation can negatively impact network performance and quality of service because CORESET carries control information used for network operations. Therefore, CORESET truncation must be performed with caution.

[0031] Various aspects are involved in CORESET pruning as a whole. Some aspects more specifically involve CORESET pruning modes for certain bandwidths and / or PRB numbers. Some aspects more specifically involve CORESET pruning modes for certain RB offsets relative to the Synchronization Signal Block (SSB). Some aspects further involve at least partially based control channel element (CCE) to resource element group (REG) mapping based on CORESET pruning. In some examples, the UE receives signaling identifying the CORESET pruning mode, which is at least partially based on the number of resource blocks available before and after the CORESET pruning process and the number of symbols in the CORESET; and decodes downlink control information (DCI) according to the CORESET pruning mode. In some examples, the network node outputs signaling identifying the CORESET pruning mode, which is at least partially based on the number of resource blocks available before and after the CORESET pruning process and the number of symbols in the CORESET; and configures the UE to decode the DCI according to the CORESET pruning mode.

[0032] 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 examples, by receiving signaling identifying the CORESET truncation mode, the described techniques can be used to allow the UE to communicate according to a CORESET truncation mode from a legacy CORESET (e.g., legacy CORESET0) to a CORESET transmitted in a limited bandwidth (e.g., CORESET0). For a CORESET0 indicated by the Physical Broadcast Channel (PBCH) / Master Information Block (MIB) for UE detection of System Information Block (SIB) signaling, the legacy CORESET0 has a minimum of 24 RBs transmitted in a 5MHz channel bandwidth. To enable CORESET0 to be transmitted at frequencies less than 5 MHz within a 5 MHz channel bandwidth or even within a 3 MHz channel bandwidth, CORESET truncation can be instructed to truncate the legacy 24-RB CORESET0 to a CORESET0 with 3.6 MHz (e.g., 20-RB) within a 5 MHz channel bandwidth, or to truncate it to a CORESET0 with 2.7 MHz (e.g., 15-RB) within a 3 MHz channel bandwidth. In some examples, by receiving signaling identifying the CORESET truncation mode, the described techniques can be used to allow the UE to communicate according to the CORESET truncation mode, which improves network operation without significantly sacrificing quality of service. In some examples, by configuring the UE to decode downlink control information according to the CORESET truncation mode, the described techniques can be used to transmit control information even when high-priority data must be transmitted.

[0033] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatuses or methods practiced using structures, functions, or structures and functions other than those of the various aspects of this disclosure set forth herein or different from those of the disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0034] Various devices and techniques will now be used to illustrate several aspects of a telecommunications system. These devices 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 can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0035] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

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

[0037] In some examples, network node 110 is or includes network nodes such as RU that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes such as DU that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes such as CU that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. Network node 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 can interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks).

[0038] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 and / or the network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. Network nodes may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

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

[0040] Wireless network 100 may include one or more relay stations. A relay station is a network node that can receive data transmissions from upstream nodes (e.g., network node 110 or UE 120) and transmit data to downstream nodes (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. 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. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, repeater, etc.

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

[0042] Network controller 130 may be coupled to or communicate with network node set 110, and may provide coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul or midhaul link. Network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, network controller 130 may be a CU or core network device, or may include a CU or core network device.

[0043] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 may be 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, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, and / or any other suitable device configured to communicate via wireless or wired media.

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

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

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

[0047] Devices in Wireless Network 100 can communicate using the electromagnetic spectrum, which can be subdivided by frequency or wavelength into various categories, bands, channels, etc. For example, devices in Wireless Network 100 can communicate using one or more operating frequency bands. In 5G NR, two initial operating frequency bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is different from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0048] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as the frequency range designations 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). Each of these higher frequency bands falls within the EHF band.

[0049] Considering the examples above, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" is used herein, it can broadly refer to frequencies below 6 GHz, within FR1, or including intermediate frequency bands. Furthermore, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" is used herein, it can broadly refer to frequencies that can include intermediate frequency bands, within FR2, FR4, FR4-a, or FR4-1 and / or FR5, or within the EHF band. Modifications to frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) are contemplated, and the techniques described herein are applicable to those modified frequency ranges.

[0050] In some respects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET; and decode downlink control information according to the CORESET truncation mode. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0051] In some respects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may output signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET; and configure the UE to decode downlink control information according to the CORESET truncation mode. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

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

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

[0054] At network node 110, transmitting processor 220 may receive data from data source 212 intended for use by UE 120 (or UE set 120). Transmitting processor 220 may select one or more modulation and decoding schemes (MCS) for UE 120 based at least in part on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) the data for UE 120 based at least in part on the MCS selected for UE 120 and may provide data symbols for UE 120. Transmitting processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 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 stream sets (e.g., T Each output symbol stream is provided to the corresponding set of modems 232 (e.g., ...). T Each modem 232a to 232t (shown as modems 232a to 232t) may be used. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may also use a corresponding modulator component to process the output sample stream (e.g., convert to analog, amplify, filter, and / or up-convert) to obtain a downlink signal. Modems 232a to 232t may be used via a corresponding antenna set 234 (e.g., T Each antenna (shown as antennas 234a to 234t) is used to transmit a set of downlink signals (e.g., ...). T (One downlink signal).

[0055] At UE 120, antenna set 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 and / or other network nodes 110 and can transmit the received signal set (e.g., R The received signals are provided to the modem set 254 (e.g., REach modem 254 (shown as modems 254a to 254r) may receive a signal. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use a 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 a demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), Reference Signal Received Quality (RSRQ), and / or CQI. In some examples, one or more components of the UE 120 may be included in the housing 284.

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

[0057] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc., or may be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, and / or be coupled to one or more transmitting and / or receiving components (such as...). Figure 2 One or more antenna elements (one or more components in a )

[0058] On the uplink, at UE 120, the transmit processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 can generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 can be pre-decoded by the TX MIMO processor 266 where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, the modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, and / or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to execute this document (e.g., reference). Figures 4 to 16 ( ) any aspect of the methods described in the method.

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

[0060] The controller / processor 240 of network node 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component may perform one or more techniques associated with CORESET truncation, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component that can execute or direct, for example Figure 13 Process 1300 Figure 14 The operation of process 1400 and / or other processes as described herein. Memory 242 and memory 282 may store data and program code for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, these one or more instructions may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly, or after compilation, transformation and / or interpretation). Figure 13 Process 1300 Figure 14 The operation of process 1400 and / 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.

[0061] In some aspects, UE 120 includes components for receiving signaling identifying a CORESET truncation mode, which is at least partially based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET; and / or components for decoding downlink control information according to the CORESET truncation mode. Components for UE 120 to perform the operations described herein may include, for example, one or more of the following: 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.

[0062] In some aspects, network node 110 includes components for outputting signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET; and / or components for configuring the UE to decode downlink control information according to the CORESET truncation mode. Components for the network node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0063] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. Figure 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... Figure 2 The memory described. For example, a function 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.

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

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

[0066] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in either a converged or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as a converged base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A "network entity" or "network node" can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0067] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0068] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed individually. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0069] Figure 3This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. 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 indirectly with the core network 320 via one or more disaggregated control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0070] Each unit in the cells (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cell, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other cells via transmission media. In some examples, each unit in the cell may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other cells via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other cells via a wireless transmission media, or both.

[0071] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more 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 implemented to communicate with the DU 330 for network control and signaling purposes, as needed.

[0072] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

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

[0074] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support 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 305 can be configured to 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. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0075] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

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

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

[0078] Figure 4 This is a diagram illustrating an example resource structure 400 for wireless communication according to the present disclosure. Resource structure 400 shows examples of various resource groups described herein. As shown, resource structure 400 may include subframes 405. Subframes 405 may include multiple time slots 410. Although resource structure 400 is shown as including 2 time slots per subframe, different numbers of time slots may be included in a subframe (e.g., 4 time slots, 8 time slots, 16 time slots, 32 time slots, or another number of time slots). In some aspects, different types of transmission time intervals (TTIs) may be used in addition to subframes and / or time slots. Time slots 410 may include multiple symbols 415, such as 14 symbols per time slot.

[0079] The potential control area of ​​time slot 410 may be referred to as CORESET 420, and may be configured to support efficient use of resources, such as by flexibly configuring or reconfiguring the resources of CORESET 420 for one or more Physical Downlink Control Channels (PDCCH) and / or one or more Physical Downlink Shared Channels (PDSCH). In some aspects, CORESET 420 may occupy the first symbol 415 of time slot 410, the first two symbols 415 of time slot 410, or the first three symbols 415 of time slot 410. Thus, CORESET 420 may include multiple resource blocks (RBs) in the frequency domain and one, two, or three symbols 415 in the time domain. In 5G, the number of resources included in CORESET 420 can be flexibly configured (e.g., by indicating the frequency domain area (e.g., number of resource blocks) and / or time domain area (e.g., number of symbols) of CORESET 420 through the use of Radio Resource Control (RRC) signaling).

[0080] As illustrated, symbol 415, including CORESET 420, may include one or more CCEs 425, as exemplified by two CCEs 425 spanning a portion of the system bandwidth. CCEs 425 may include downlink control information (DCI) for providing control information for wireless communication. A base station may transmit DCI during multiple CCEs 425 (as shown), where the number of CCEs 425 used for transmitting DCI represents the aggregation level (AL) used by the BS for transmitting DCI. Figure 4 In the example shown, aggregation level two is represented, corresponding to two CCEs 425 in slot 410. In some respects, different aggregation levels may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

[0081] Each CCE 425 may include a fixed number of REGs 430 (shown as 6 REGs 430), or may include a variable number of REGs 430. In some aspects, the number of REGs 430 included in a CCE 425 may be specified by the REG bundle size. A REG 430 may include a resource block, which may include 12 resource elements (REs) 435 within a symbol 415. A resource element 435 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0082] The search space can include all possible locations where the PDCCH might be located (e.g., in time and / or frequency). CORESET 420 can include one or more search spaces, such as a UE-specific search space, a group common search space, and / or a common search space. A search space can indicate the set of CCE locations where the UE can find a PDCCH that can potentially be used to send control information to the UE. Possible locations of the PDCCH can depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE) or a group common PDCCH (e.g., for multiple UEs), and / or the aggregation level being used. Possible locations of the PDCCH (e.g., in time and / or frequency) can be referred to as PDCCH candidates, and the set of all possible PDCCH locations at an aggregation level can be referred to as the search space. For example, the set of all possible PDCCH locations for a specific UE can be referred to as the UE-specific search space. Similarly, the set of all possible PDCCH locations for all UEs can be referred to as the common search space. The set of all possible PDCCH locations for a specific group of UEs can be referred to as the group common search space. One or more search spaces across aggregation levels can be referred to as a search space (SS) set.

[0083] CORESET 420 can be interleaved or non-interleaved. An interleaved CORESET 420 may have a CCE-to-REG mapping such that adjacent CCEs are mapped to a scattered REG bundle in the frequency domain (e.g., adjacent CCEs are not mapped to a consecutive REG bundle of CORESET 420). A non-interleaved CORESET 420 may have a CCE-to-REG mapping such that all CCEs are mapped to a consecutive REG bundle of CORESET 420 (e.g., in the frequency domain).

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

[0085] Figure 5 This is an illustration of example 500 associated with the CORESET cut-off mode according to this disclosure.

[0086] like Figure 5As shown in Example 500, for a 3MHz channel bandwidth using a 15kHz subcarrier spacing and a maximum radio frequency transmission bandwidth of 15 resource blocks (RBs), the SSB truncation mode 505A-B for reducing the number of RBs from the legacy 20RB synchronization signal blocks (SSBs) to 12RB SSBs may include truncating the first four RBs (RBs 0-3) and the last four RBs (RBs 16-19) of each PBCH symbol. In some aspects, the first truncation mode 510A for CORESETs (e.g., CORESET0 indicated by the PBCH / MIB) for reducing the number of RBs from the legacy 24-RB CORESET to 15-RB CORESETs may include applying an offset of 0RB between the legacy 24-RB CORESET and the legacy 20-RB SSB without truncating. As shown in Example 500, the first three RBs (RBs 0-2) and the last six RBs (RBs 18-23) in the first truncation mode 510A are truncated in each CORESET symbol. With an offset of 0, the truncation mode can be predefined as truncating 3 RBs at a lower frequency and 6 RBs at a higher frequency. Therefore, with an offset of 0 RB between the lowest RB of the uncrunted legacy CORESET and the lowest RB of the uncrunted legacy SSB, both the truncated 12-RB SSB (RB 4-15) and the truncated 15-RB CORESET (RB 3-17) are transmitted within a 3MHz channel bandwidth. With an offset (such as 2 RB between the legacy 24-RB CORESET and the uncrunted legacy 20-RB SSB shown in Example 500), the first truncation mode 510B for CORESET can be predefined as truncating 6 RBs at a lower frequency and 3 RBs at a higher frequency in each CORESET symbol. Therefore, with an offset of 2 RB between the lowest RB of the untrunculated legacy CORESET and the lowest RB of the untrunculated legacy SSB, both the truncated 12-RB SSB (RB 4-15) and the truncated 15-RB CORESET (RB 6-20) are transmitted within a 3MHz channel bandwidth in each CORESET symbol. Regardless of the offset, in some respects, such as when the REG bundle size is 6, some CCEs can be truncated at higher or lower frequencies. For example, according to the first truncation mode 510A, the first 3 RBs (RB 0-2) and the last 6 RBs (RB 18-23) of the legacy 24-RB CORESET are truncated, resulting in 1.5 CCEs and 3 CCEs being truncated at lower and higher frequencies, respectively, for a 3-symbol CORESET, where each CCE has a total of 6 RBs, including 2 RBs in the frequency domain and 3 symbols in the time domain.Similarly, according to the first truncation mode 510B, the first 6 RBs (RB 0-5) and the last 3 RBs (RB 21-23) of the old 24-RB CORESET are truncated, resulting in 3 CCEs and 1.5 CCEs being truncated at lower and higher frequencies, respectively, for a 3-symbol CORESET. On the other hand, if the first 4 RBs (RB 0-3) and the last 5 RBs (RB 19-23) of the old 24-RB CORESET are truncated, then for a 3-symbol CORESET, 2 CCEs and 2.5 CCEs are truncated, but for a 2-symbol CORESET, 1.3 CCEs and 2.6 CCEs are truncated at lower and higher frequencies, respectively, where each CCE has 6 RBGs bundled together with 3 RBs in the frequency domain and 2 symbols in the time domain. To minimize the partial truncation of CCE, at least one of the number of RBs truncated at a lower or higher frequency should be a multiple of the RBG bundle size of 6.

[0087] In the second pruning mode 515A-B, the RB offset (if any) can be relative to the 12 RB SSB pruned using pruning mode 505A-B. For example, as shown in the second pruning mode 515A-B, no RBs are pruned at lower frequencies, which results in 9 RBs (RB 15-23) being pruned at higher frequencies. In the second pruning mode 515A-B, a portion of the CCE can be pruned at higher frequencies based on the number of RBs in the REG bundle and the number of RBs to be pruned. Furthermore, as shown in Example 500, the second pruning mode 515B can have an offset of 2 relative to the 12 RB SSB pruned using pruning mode 505B. Subsequently, with an offset of 0 or 2 RBs between the lowest RB of the un-truncated old CORESET and the lowest RB of the truncated SSB, both the truncated 12-RB SSB (RB 4-15) and the truncated 15-RB CORESET (RB 0-14) are transmitted within a 3MHz channel bandwidth in each CORESET symbol.

[0088] In some respects, for a 15RB core set truncated from a legacy 24RB core set, the offset of the truncation mode can be zero RBs (e.g., SSB truncation mode 505A or core set truncation mode 510A) or two RBs (e.g., SSB truncation mode 505B or core set truncation mode 510B). Other offsets are also possible as long as the core set and SSB are within the maximum bandwidth relative to the number of RBs and the channel bandwidth. For example, an offset of 4 might not be suitable for 15 RBs in a 3MHz channel bandwidth because the SSB and core set cannot be transmitted together within a 3MHz channel bandwidth.

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

[0090] Figures 6 to 11 These are illustrations of Examples 600 to 1100 associated with the CORESET truncation mode according to this disclosure.

[0091] Figure 6 Example 600 illustrates a two-symbol CORESET. Each REG bundle comprises six REGs bundled together with three RBs in the frequency domain and two symbols in the time domain, and Example 600 shows a total of eight REG bundles in a legacy 24-RB CORESET. A CCE shift is shown for each REG bundle (shown as...). n 移位 Furthermore, Example 600 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. In Example 600, the truncation mode can be defined as truncating 3 RBs at a lower frequency and 6 RBs at a higher frequency in each CORESET symbol. No CCEs are truncated at either the lower or higher frequency. Therefore, as shown, in the option illustrated in Example 600, RBs 0-2 and 18-23 are truncated.

[0092] Figure 7 Example 700 illustrates a three-symbol CORESET. Each REG bundle comprises six REGs bundled together with two RBs in the frequency domain and three symbols in the time domain, and Example 700 illustrates a total of 12 REG bundles in a legacy 24-RB CORESET. CCE shifting is shown for each REG bundle. Furthermore, Example 700 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. Similar to Example 600, in Example 700, the truncation mode can be defined as truncating three RBs at a lower frequency and six RBs at a higher frequency within each CORESET symbol. There is a truncated CCE at the lower frequency, but no truncated CCE at the higher frequency. Therefore, as shown in the figure, in the options shown in Example 700, RB 0-2 and 18-23 are truncated, which results in partial CCE truncation relative to REG bundle 2 (with interleaving) or REG bundle 1 (without interleaving), both of which include the truncated RB 2.

[0093] Figure 8Example 800 illustrates a two-symbol CORESET. Each REG bundle comprises six REGs bundled together with three RBs in the frequency domain and two symbols in the time domain, and Example 800 shows a total of eight REG bundles in a legacy 24-RB CORESET. CCE shifting is shown for each REG bundle. Furthermore, Example 800 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. In Example 800, the truncation mode can be defined as truncating six RBs at a lower frequency and three RBs at a higher frequency in each CORESET symbol. Partial CCEs may be truncated at the higher frequency. No partial CCEs are truncated at either the lower or higher frequency. Thus, as shown, in the option shown in Example 800, RBs 0-5 and 21-23 are truncated.

[0094] Figure 9 Example 900 illustrates a three-symbol CORESET. Each REG bundle comprises six REGs bundled together with two RBs in the frequency domain and three symbols in the time domain, and Example 900 shows a total of 12 REG bundles in a legacy 24-RB CORESET. CCE shifting is shown for each REG bundle. Furthermore, Example 900 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. Similar to Example 800, in Example 900, the truncation mode can be defined as truncating six RBs at a lower frequency and three RBs at a higher frequency. A portion of the CCE may be truncated at the higher frequency. There is one truncated portion of the CCE at the higher frequency, but no truncated portion of the CCE at the lower frequency. Therefore, as shown in the figure, in the options shown in Example 900, RBs 0-5 and 21-23 are truncated, which results in partial CCE truncation relative to REG bundle 9 (with interleaving) or REG bundle 10 (without interleaving), both of which include the truncated RB 21.

[0095] Figure 10Example 1000 illustrates a two-symbol CORESET. Each REG bundle comprises six REGs bundled together with three RBs in the frequency domain and two symbols in the time domain, and Example 1000 shows a total of eight REG bundles in a legacy 24-RB CORESET. CCE shifting is shown for each REG bundle. Furthermore, Example 1000 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. In Example 1000, the truncation mode can be defined as truncating nine RBs at higher frequencies. No CCEs are truncated at either the higher or lower frequencies. Therefore, as shown, in the option shown in Example 1000, RBs 15-23 are truncated.

[0096] Figure 11 Example 1100 illustrates a three-symbol CORESET. Each REG bundle comprises six REGs bundled together with two RBs in the frequency domain and three symbols in the time domain, and Example 1100 shows a total of 12 REG bundles in a legacy 24-RB CORESET. CCE shifting is shown for each REG bundle. Furthermore, Example 1100 illustrates an option with interleaving (e.g., an interleaver size of 2) and an option without interleaving. Similar to Example 1000, in Example 1100, the truncation mode can be defined as truncating nine RBs at higher frequencies. Only one portion of the CCE is truncated at the higher frequencies, while no portion of the CCE is truncated at the lower frequencies. Thus, as shown, in the option shown in Example 1100, RBs 15-23 are truncated, resulting in a partial CCE truncation relative to REG bundle 3 (with interleaving) or REG bundle 7 (without interleaving), both of which include the truncated RB 15.

[0097] For legacy cores, the CCE shift can be the cell identifier used for CCE-to-REG mapping. For cores truncated from, for example, a legacy 24-RB core to a 15-RB core, in some cases, a large aggregation level (AL) (such as AL 8) may not be supported for a core with 15 RBs. For example, if more than two CCEs are truncated, there is minimal performance gain compared to a smaller AL (e.g., AL 4) due to the truncation. For 2-symbol cores, more than two of the legacy 8 CCEs in a legacy 24-RB core are truncated with or without interleaving. For 3-symbol cores, more than two of the legacy 12 CCEs in a legacy 24-RB core can be truncated for aggregation level 8 if the truncation is with interleaving. Without interleaving, fewer than two CCEs are truncated for aggregation level 8 when the CCE shift is equal to 0, 1, or 2. Otherwise, if the aggregation level is 8, more than two CCEs will be truncated.

[0098] In some respects, to achieve the desired aggregation level, the CORESET CCE-to-REG mapping can be modified, at least in part, based on the CORESET truncation mode and configuration parameters for a specific channel bandwidth (such as a 3MHz channel bandwidth). For a CORESET with 15 RBs, 3 symbols, and no interleaving, the CCE shift can be equal to the variable... Y Add cell identifier mod X . X The value can be a constant, such as 3, and can be at least partially based on the number of truncated CCEs (e.g., 8) of cell randomization and desired clustering level. Variable Y This could be the number of CORESET CCEs (before pruning) minus the number of RBs to be pruned at lower frequencies. (Variable) Y Alternatively, it can be equal to the total number of RBs (e.g., 24 RBs) minus the number of RBs to be truncated at lower frequencies multiplied by the number of symbols in the CORESET and divided by the REG bundle size. L The results are shown below. Y Example equations.

[0099] In another example, such as for a 20-RB CORESET associated with a 5MHz channel bandwidth, if four RBs are to be removed from an older 24-RB CORESET, there can be at most two CCEs to be removed and the CCE shift can be equal to the cell identifier. In another example, such as for a CORESET associated with a 3MHz channel bandwidth, if there are no RBs to be removed (i.e., the CCE-to-REG mapping is directly based on the number of RBs indicated for each symbol of the CORESET), the CCE shift can be equal to the cell identifier.

[0100] As indicated above, Figures 6 to 11 This is provided as an example. Other examples are available relative to... Figures 6 to 11 The descriptions are different.

[0101] Figure 12 This is a diagram illustrating Example 1200 associated with decoding a DCI signal according to this disclosure. (See diagram for example.) Figure 12 As shown, network nodes (e.g., network nodes 110, CU, DU, and / or RU) can communicate with a UE (e.g., UE 120). In some aspects, the network nodes and the UE can be part of a wireless network (e.g., wireless network 100). The UE and the network nodes can... Figure 12 The operation shown has been performed with a wireless connection already established.

[0102] In some aspects, the configuration information may indicate one or more candidate configuration and / or communication parameters. In some aspects, these one or more candidate configuration and / or communication parameters may be selected, activated, and / or deactivated by subsequent indications. For example, a subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configuration and / or communication parameters. In some aspects, subsequent indications (e.g., the indications described herein) may include dynamic indications, such as one or more MAC CEs and / or one or more DCI messages, etc.

[0103] In some respects, configuration information may instruct the UE to receive signaling that identifies the CORESET truncation mode. As discussed above, the CORESET truncation mode may be based, at least in part, on the number of RBs available before and after the CORESET truncation process and the number of symbols in the CORESET.

[0104] The UE can configure itself, at least in part, based on configuration information. In some respects, the UE can be configured to perform one or more of the operations described herein, at least in part, based on configuration information.

[0105] As shown by reference numeral 1210 in the attached figure, the UE can send a capability report, and the network node can receive the capability report. The capability report can indicate whether the UE supports a feature and / or one or more parameters associated with that feature. For example, capability information can indicate the capabilities and / or parameters used for CORESET truncation. As another example, the capability report can indicate the capabilities and / or parameters used for decoding DCI signals based on CORESET truncation. One or more operations described herein can be based on the capability information in the capability report. For example, the UE can perform communication based on the capability information, or can receive configuration information based on the capability information. In some aspects, the capability report can indicate that the UE supports applying CORESET truncation mode, CCE-to-REG mapping, modifying CCE shift, and decoding DCI based on CORESET truncation mode, CCE-to-REG mapping, and modified CCE shift.

[0106] In some aspects, the configuration information and / or capability report described in conjunction with reference to reference numeral 1205 may include information transmitted via multiple communications. Additionally or alternatively, the network node may transmit the configuration information or communications including at least a portion of the configuration information before and / or after the UE transmits the capability report. For example, the network node may transmit a first portion of the configuration information before the capability report, the UE may transmit at least a portion of the capability report, and the network node may transmit a second portion of the configuration information after receiving the capability report.

[0107] As shown in Figure 1215, according to the CORESET truncation mode, the UE can receive downlink control information, and the network node can transmit downlink control information.

[0108] As indicated by reference numeral 1220 in the accompanying drawings, the UE may configure itself to decode DCI based at least in part on the indications described in conjunction with reference numeral 1215.

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

[0110] Figure 13 This is a diagram illustrating an example process 1300 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 1300 is an example in which the device or the UE (e.g., UE 120) performs an operation associated with CORESET truncation.

[0111] like Figure 13As shown, in some aspects, process 1300 may include receiving signaling identifying a CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET (box 1310). For example, the UE (e.g., using...) Figure 15 The communication manager 1506 shown can receive signaling identifying the CORESET pruning mode, which is at least in part based on the number of resource blocks available before and after the CORESET pruning process and the number of CORESET symbols, as described above.

[0112] like Figure 13 As further shown, in some aspects, process 1300 may include decoding downlink control information according to the CORESET truncation mode (box 1320). For example, the UE (e.g., using...) Figure 15 The Communication Manager 1506 shown can decode downlink control information according to the CORESET truncation mode, as described above.

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

[0114] In the first aspect, the CORESET pruning mode is still based, at least in part, on the resource block offset between the starting resource block of CORESET before the CORESET pruning process and the starting resource block of SSB communication after the CORESET pruning process.

[0115] In a second aspect, either alone or in combination with the first aspect, the CORESET truncation mode includes truncating a first number of resource blocks at a first frequency or truncating a second number of resource blocks at a second frequency.

[0116] In the third aspect, either alone or in combination with one or more of the first and second aspects, the CORESET truncation mode includes partial truncation of a single CCE.

[0117] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, a partial censoring of a single CCE occurs relative to a resource block associated with a first frequency or a resource block associated with a second frequency.

[0118] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the CORESET pruning mode is at least partially based on the REG bundle size.

[0119] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1300 includes determining, at least in part, a CCE-to-REG mapping associated with the CORESET truncation mode based on signaling that identifies the CORESET.

[0120] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the aggregation level is based at least in part on the CORESET pruning pattern and the CCE to REG mapping.

[0121] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the CCE to REG mapping is at least partially based on CCE shifts.

[0122] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the CCE shift for CCE-to-REG mapping is based at least in part on the cell identifier and the maximum number of CCEs to be truncated for the aggregation level.

[0123] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the CCE shift for CCE-to-REG mapping is based at least in part on the number of CCEs associated with CORESET before pruning and the number of CCEs to be pruned at the first frequency.

[0124] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the CCE shift is based at least in part on the number of resource blocks associated with the CORESET after truncation or the number of symbols associated with the CORESET.

[0125] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the CCE shift is based at least in part on whether the REG bundles used for CORESET are interleaved.

[0126] although Figure 13 An example box of process 1300 is shown, but in some respects, process 1300 may include... Figure 13 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the process 1300 may be executed in parallel.

[0127] 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 the present disclosure. Example process 1400 is an example in which the device or the network node (e.g., network node 110) performs an operation associated with CORESET truncation.

[0128] like Figure 14 As shown, in some aspects, process 1400 may include output signaling identifying a CORESET pruning mode, which is at least in part based on the number of resource blocks available before and after the CORESET pruning process and the number of CORESET symbols (box 1410). For example, network nodes (e.g., using...) Figure 16 The transmitting component 1604 and / or the communication manager 1606 shown can output signaling identifying the CORESET pruning mode, which is at least in part based on the number of resource blocks available before and after the CORESET pruning process and the number of CORESET symbols, as described above.

[0129] like Figure 14 As further shown, in some aspects, process 1400 may include configuring the UE to decode downlink control information according to the CORESET truncation mode (box 1420). For example, a network node (e.g., using...) Figure 16 The Communication Manager 1606 shown can configure the UE to decode downlink control information according to the CORESET truncation mode, as described above.

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

[0131] In the first aspect, the CORESET pruning mode is still based, at least in part, on the resource block offset between the starting resource block of CORESET before the CORESET pruning process and the starting resource block of SSB communication after the CORESET pruning process.

[0132] In a second aspect, either alone or in combination with the first aspect, the CORESET truncation mode includes truncating a first number of resource blocks at a first frequency or truncating a second number of resource blocks at a second frequency.

[0133] In the third aspect, either alone or in combination with one or more of the first and second aspects, the CORESET truncation mode includes partial truncation of a single CCE.

[0134] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, a partial censoring of a single CCE occurs relative to a resource block associated with a first frequency or a resource block associated with a second frequency.

[0135] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the CORESET pruning mode is at least partially based on the REG bundle size.

[0136] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, process 1400 includes configuring the UE to determine, at least in part, a CCE-to-REG mapping associated with the CORESET truncation mode based on signaling identifying the CORESET.

[0137] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the aggregation level is based at least in part on the CORESET pruning pattern and the CCE to REG mapping.

[0138] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the CCE to REG mapping is at least partially based on CCE shifts.

[0139] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the CCE shift for CCE-to-REG mapping is based at least in part on the cell identifier and the maximum number of CCEs to be truncated for the aggregation level.

[0140] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the CCE shift for CCE-to-REG mapping is based at least in part on the number of CCEs associated with CORESET before pruning and the number of CCEs to be pruned at the first frequency.

[0141] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the CCE shift is based at least in part on the number of resource blocks associated with the CORESET after truncation or the number of symbols associated with the CORESET.

[0142] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the CCE shift is based at least in part on whether the REG bundles used for CORESET are interleaved.

[0143] although Figure 14 An example box of process 1400 is shown, but in some respects, process 1400 may include... Figure 14 The boxes shown 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.

[0144] Figure 15This 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.

[0145] In some respects, device 1500 can be configured to perform the functions described herein. Figures 4 to 11 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.

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

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

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

[0149] The communication manager 1506 can receive signaling identifying the CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. The communication manager 1506 can decode downlink control information according to the CORESET truncation mode.

[0150] The communication manager 1506 can determine the CCE-to-REG mapping associated with the CORESET truncation mode based at least in part on the signaling that identifies the CORESET.

[0151] 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 15The set (one or more) components shown are executable descriptions by Figure 15 The other component shown performs one or more functions.

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

[0153] 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 device 1600 and / or one or more components shown may include a combination Figure 2 One 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.

[0154] 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 2The described network node may include 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 from device 1600 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0155] 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 2 The 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.

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

[0157] Transmitting component 1604 can output signaling identifying the CORESET truncation mode, which is at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols in the CORESET. Communication manager 1606 can configure the UE to decode downlink control information according to the CORESET truncation mode.

[0158] The communication manager 1606 can configure the UE to determine the CCE-to-REG mapping associated with the CORESET truncation mode based at least in part on signaling that identifies the CORESET.

[0159] 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 set (one or more) components shown are executable descriptions by Figure 16 The other component shown performs one or more functions.

[0160] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a UE, the method comprising: receiving signaling identifying a CORESET truncation mode, the CORESET truncation mode being at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols of the CORESET; and decoding downlink control information according to the CORESET truncation mode.

[0161] Aspect 2: According to the method of aspect 1, wherein the CORESET pruning mode is still at least in part based on the resource block offset between the starting resource block of the CORESET before the CORESET pruning process and the starting resource block of the SSB communication after the CORESET pruning process.

[0162] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the CORESET truncation mode includes truncating a first number of resource blocks at a first frequency or truncating a second number of resource blocks at a second frequency.

[0163] Aspect 4: According to the method described in aspect 3, wherein the CORESET truncation mode includes partial truncation of a single CCE.

[0164] Aspect 5: According to the method of aspect 4, wherein the partial truncation of the single CCE occurs relative to a resource block associated with the first frequency or a resource block associated with the second frequency.

[0165] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the CORESET pruning mode is at least partially based on the REG bundle size.

[0166] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising determining, at least in part, a CCE-to-REG mapping associated with the CORESET truncation mode based on signaling that identifies the CORESET.

[0167] Aspect 8: The method according to aspect 7, wherein the aggregation level is at least partially based on the CORESET truncation mode and the CCE to REG mapping.

[0168] Aspect 9: The method according to aspect 7, wherein the CCE to REG mapping is at least partially based on CCE shift.

[0169] Aspect 10: The method according to aspect 9, wherein the CCE shift for the CCE-to-REG mapping is based at least in part on the cell identifier and the maximum number of CCEs to be truncated for the aggregation level.

[0170] Aspect 11: According to the method of aspect 9, wherein the CCE shift for the CCE-to-REG mapping is based at least in part on the number of CCEs associated with the CORESET before pruning and the number of CCEs to be pruned at the first frequency.

[0171] Aspect 12: The method according to aspect 11, wherein the CCE shift is based at least in part on the number of resource blocks associated with the CORESET after truncation or the number of symbols associated with the CORESET.

[0172] Aspect 13: The method according to aspect 11, wherein the CCE shift is based at least in part on whether the REG bundles for the CORESET are interleaved.

[0173] Aspect 14: The method according to any one of aspects 1 to 14, wherein the CORESET is CORESET0.

[0174] Aspect 15: A method for wireless communication performed by a network node, the method comprising: outputting signaling identifying a CORESET truncation mode, the CORESET truncation mode being at least in part based on the number of resource blocks available before and after the CORESET truncation process and the number of symbols of the CORESET; and configuring a UE to decode downlink control information according to the CORESET truncation mode.

[0175] Aspect 16: According to the method of aspect 15, wherein the CORESET pruning mode is still at least in part based on the resource block offset between the starting resource block of the CORESET before the CORESET pruning process and the starting resource block of the SSB communication after the CORESET pruning process.

[0176] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the CORESET truncation mode includes truncating a first number of resource blocks at a first frequency or truncating a second number of resource blocks at a second frequency.

[0177] Aspect 18: The method according to aspect 17, wherein the CORESET truncation mode includes partial truncation of a single CCE.

[0178] Aspect 19: The method according to aspect 18, wherein the partial truncation of the single CCE occurs relative to a resource block associated with the first frequency or a resource block associated with the second frequency.

[0179] Aspect 20: The method according to any one of Aspects 15 to 19, wherein the CORESET pruning pattern is at least partially based on the REG bundle size.

[0180] Aspect 21: The method according to any one of Aspects 15 to 20, the method further comprising configuring the UE to determine, at least in part, a CCE-to-REG mapping associated with the CORESET truncation mode based on signaling identifying the CORESET.

[0181] Aspect 22: According to the method of aspect 21, wherein the aggregation level is based at least in part on the CORESET truncation mode and the CCE to REG mapping.

[0182] Aspect 23: The method according to aspect 21, wherein the CCE to REG mapping is at least partially based on CCE shifts.

[0183] Aspect 24: The method according to aspect 23, wherein the CCE shift for the CCE-to-REG mapping is based at least in part on the cell identifier and the maximum number of CCEs to be truncated for the aggregation level.

[0184] Aspect 25: The method according to aspect 23, wherein the CCE shift for the CCE-to-REG mapping is based at least in part on the number of CCEs associated with the CORESET before pruning and the number of CCEs to be pruned at the first frequency.

[0185] Aspect 26: The method according to aspect 25, wherein the CCE shift is based at least in part on the number of resource blocks associated with the CORESET after truncation or the number of symbols associated with the CORESET.

[0186] Aspect 27: The method according to aspect 25, wherein the CCE shift is based at least in part on whether the REG bundles for the CORESET are interleaved.

[0187] Aspect 28: The method according to any one of aspects 15 to 27, wherein the CORESET is CORESET0.

[0188] Aspect 29: 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 28.

[0189] Aspect 30: 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 28.

[0190] Aspect 31: 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 28.

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

[0192] Aspect 33: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, 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 28.

[0193] Aspect 34: 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 28.

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

[0195] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented through various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referred to in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0196] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using general-purpose single-chip or multi-chip processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some aspects, specific processes and methods can be performed by circuitry dedicated to a given function.

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

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

[0199] 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 interchangeable with “one or more.” Furthermore, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Additionally, as used herein, the terms “having” and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. A user equipment (UE) for wireless communication, the UE 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 UE to: receive signaling that identifies a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern based at least in part on a number of resource blocks available before and after a CORESET puncturing procedure and a number of symbols of the CORESET; and decode downlink control information in accordance with the CORESET puncturing pattern.

2. The UE of claim 1, wherein, the CORESET puncturing pattern is further based at least in part on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing procedure and a starting resource block of a synchronization signal block (SSB) communication after the CORESET puncturing procedure.

3. The UE of claim 1, wherein, the CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or puncturing a second number of resource blocks at a second frequency.

4. The UE of claim 3, wherein, the CORESET puncturing pattern includes partial puncturing of a single control channel element (CCE).

5. The UE of claim 4, wherein, the partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.

6. The UE of claim 1, wherein, the CORESET puncturing pattern is based at least in part on a resource element group (REG) bundling size.

7. The UE of claim 1, wherein, the one or more processors are individually or collectively further configured to cause the UE to determine a control channel element (CCE) to resource element group (REG) mapping associated with the CORESET puncturing pattern based at least in part on signaling that identifies the CORESET.

8. The UE of claim 7, wherein, an aggregation level is based at least in part on the CORESET puncturing pattern and the CCE to REG mapping.

9. The UE of claim 7, wherein, the CCE to REG mapping is based at least in part on a CCE shift.

10. The UE of claim 9, wherein, the CCE shift for the CCE to REG mapping is based at least in part on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.

11. The UE of claim 9, wherein, the CCE shift for the CCE to REG mapping is based at least in part on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured at a first frequency.

12. The UE of claim 11, wherein, the CCE shift is based at least in part on a number of resource blocks associated with the CORESET after puncturing or based at least in part on a number of symbols associated with the CORESET.

13. The UE of claim 11, wherein, the CCE shift is based at least in part on whether REG bundling for the CORESET is interleaved.

14. The UE of claim 1, wherein the CORESET is a CORESET0.

15. A network node for wireless communication, the network node 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 network node to: signaling that identifies a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern based at least in part on a number of resource blocks available before and after a CORESET puncturing procedure and a number of symbols of the CORESET; and configuring a user equipment (UE) to decode downlink control information according to the CORESET puncturing pattern.

16. The network node of claim 15, wherein, The CORESET puncturing pattern is further based at least in part on a resource block offset between a starting resource block of the CORESET before the CORESET puncturing procedure and a starting resource block of a synchronization signal block (SSB) communication after the CORESET puncturing procedure.

17. The network node of claim 15, wherein, The CORESET puncturing pattern includes puncturing a first number of resource blocks at a first frequency or puncturing a second number of resource blocks at a second frequency.

18. The network node of claim 17, wherein, The CORESET puncturing pattern includes partial puncturing of a single control channel element (CCE).

19. The network node of claim 18, wherein, The partial puncturing of the single CCE occurs with respect to resource blocks associated with the first frequency or resource blocks associated with the second frequency.

20. The network node of claim 15, wherein, The CORESET puncturing pattern is based at least in part on a resource element group (REG) bundling size.

21. The network node of claim 15, wherein, The one or more processors are further separately or collectively configured to cause the network node to configure the UE to determine a control channel element (CCE) to resource element group (REG) mapping associated with the CORESET puncturing pattern based at least in part on signaling that identifies the CORESET.

22. The network node of claim 21, wherein, An aggregation level is based at least in part on the CORESET puncturing pattern and the CCE to REG mapping.

23. The network node of claim 21, wherein, The CCE to REG mapping is based at least in part on a CCE shift.

24. The network node of claim 23, wherein, The CCE shift for the CCE to REG mapping is based at least in part on a cell identifier and a maximum number of CCEs to be punctured for an aggregation level.

25. The network node of claim 23, wherein, The CCE shift for the CCE to REG mapping is based at least in part on a number of CCEs associated with the CORESET before puncturing and a number of CCEs to be punctured at a first frequency.

26. The network node of claim 25, wherein, The CCE shift is based at least in part on a number of resource blocks associated with the CORESET after puncturing or based at least in part on a number of symbols associated with the CORESET.

27. The network node of claim 25, wherein, The CCE shift is based at least in part on whether REG bundling for the CORESET is interleaved.

28. The network node of claim 15, wherein, The CORESET is CORESET0.

29. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving signaling that identifies a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern based at least in part on a number of resource blocks available before and after a CORESET puncturing procedure and a number of symbols of the CORESET; and decoding downlink control information according to the CORESET puncturing pattern.

30. A method of wireless communication performed by a network node, the method comprising: output signaling that identifies a control resource set (CORESET) puncturing pattern, the CORESET puncturing pattern based at least in part on a number of resource blocks available before and after a CORESET puncturing procedure and a number of symbols of the CORESET; and configure a user equipment (UE) to decode downlink control information according to the CORESET puncturing pattern.

Images