Downlink receive assumption priority ordering based on downlink physical layer (PHY) priority.

Abstract

Various aspects of this disclosure relate to wireless communications, and more specifically, to techniques for determining reference assumption (e.g., quasi-co-location (QCL) assumption) priority ordering based on downlink physical layer (PHY) priority.

Description

[0001] Cross-references to related applications

[0002] This application hereby claims priority to U.S. Application No. 17 / 128,647, filed December 21, 2020, which in turn claims priority to Pending U.S. Provisional Patent Application No. 63 / 004,083, filed April 2, 2020, pursuant to 35 U.S.SC §119, the contents of which are incorporated herein by reference. Technical Field

[0003] In general, various aspects of this disclosure relate to wireless communications, and more specifically, to techniques for determining reference assumption (e.g., quasi-co-location (QCL) assumption) priority ordering based on downlink physical layer (PHY) priority. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can 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 systems include 3GPP Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name just a few.

[0005] In some examples, a radio multiple access communication system may include multiple base stations (BSs), each capable of simultaneously supporting communication for multiple communication devices (or user equipments (UEs)). In LTE or LTE-A networks, a group of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR) or 5G networks), a radio multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit / receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), where a group of one or more distributed units communicating with the central units may define access nodes (e.g., which may be referred to as base stations, 5G NBs, next-generation node Bs (gNBs or gNodeBs), TRPs, etc.). A base station or distributed unit can communicate with a group of UEs on downlink channels (e.g., for transmission from the base station or to the UE) and uplink channels (e.g., for transmission from the UE to the base station or distributed unit).

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, country, regional, and even global levels. New Radio (NR) (e.g., 5G) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard released 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 that use OFDMA with cyclic prefix (CP) on both the downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, with the continued increase in demand for mobile broadband access, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0008] The systems, methods, and apparatuses of this disclosure have several aspects, none of which individually assumes responsibility for their desired properties. Without limiting the scope of this disclosure as expressed by the following claims, features will now be briefly discussed. Upon consideration of this discussion, and particularly after reading the section entitled "Detailed Description," those skilled in the art will understand how the features of this disclosure provide advantages, including improved communication between access points and stations in a wireless network.

[0009] Certain aspects of this disclosure provide methods for wireless communication performed by a wireless node. The methods generally include: receiving signaling indicating a downlink priority level for downlink transmission and monitoring timing; determining, based on one or more rules, a reception assumption to be used when at least two downlink transmission and monitoring timings overlap in time; and processing, based on the reception assumption, at least two downlink transmission and monitoring timings that overlap in time.

[0010] Some aspects provide methods for wireless communication performed by network entities. The methods typically include: sending signaling to a wireless node indicating a downlink priority level for downlink transmission and monitoring timing; determining, based on one or more rules, a reception assumption to be used when at least two downlink transmission or monitoring timings overlap in time; and processing at least two downlink transmission and monitoring timings based on the reception assumption.

[0011] Certain aspects of this disclosure provide a wireless node. A wireless node typically includes: a unit for receiving signaling indicating a downlink priority level for downlink transmission and monitoring timing; a unit for determining, based on one or more rules, a reception assumption to be used when at least two downlink transmission and monitoring timings overlap in time; and a unit for processing, based on the reception assumption, at least two downlink transmission and monitoring timings that overlap in time.

[0012] Certain aspects of this disclosure provide network entities. Network entities typically include: units for sending signaling to radio nodes indicating downlink priority levels for downlink transmission and monitoring timing; units for determining, based on one or more rules, the reception assumptions to be used when at least two downlink transmission or monitoring timings overlap in time; and units for processing at least two downlink transmission and monitoring timings based on the reception assumptions.

[0013] Certain aspects of this disclosure provide a wireless node. A wireless node typically includes: a receiver configured to receive signaling indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine, based on one or more rules, a reception assumption to be used when at least two downlink transmission and monitoring timings overlap in time; and process, based on the reception assumption, at least two downlink transmission and monitoring timings that overlap in time.

[0014] Certain aspects of this disclosure provide a network entity. This network entity typically includes: a transmitter configured to: send signaling to a wireless node indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine, based on one or more rules, a reception assumption to be used when at least two downlink transmission or monitoring timings overlap in time; and process, based on the reception assumption, at least two downlink transmission and monitoring timings.

[0015] Certain aspects of this disclosure provide apparatus for wireless communication by a wireless node. The apparatus typically includes: an interface configured to: acquire signaling indicating a downlink priority level for downlink transmission and monitoring timings; and a processing system configured to: determine a reception assumption to be used based on one or more rules when at least two downlink transmission and monitoring timings overlap in time; and process the at least two overlapping downlink transmission and monitoring timings based on the reception assumption.

[0016] Certain aspects of this disclosure provide apparatus for wireless communication by a network entity. The apparatus typically includes: an interface configured to output signaling to a wireless node for transmission, the signaling indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine a reception assumption to be used based on one or more rules when at least two downlink transmission or monitoring timings overlap in time; and process at least two downlink transmission and monitoring timings based on the reception assumption.

[0017] Certain aspects of this disclosure provide a computer-readable medium for wireless communication. The computer-readable medium typically includes instructions executable to: obtain signaling indicating a downlink priority level for downlink transmission and monitoring timing; determine a reception assumption to be used based on one or more rules when at least two downlink transmission and monitoring timings overlap in time; and process the at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0018] Certain aspects of this disclosure provide a computer-readable medium for wireless communication. The computer-readable medium typically includes instructions executable to: output signaling to a wireless node for transmission, the signaling indicating a downlink priority level for downlink transmission and monitoring timing; when at least two downlink transmission or monitoring timings overlap in time, determine a reception assumption to be used based on one or more rules; and process at least two downlink transmission and monitoring timings based on the reception assumption.

[0019] Various aspects of this disclosure provide wireless nodes, UEs, units, devices, processors, and computer-readable media for performing the methods described herein.

[0020] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of one or more aspects are described in detail below and in the accompanying drawings. However, these features indicate only a few of the various methods that can employ the principles of these aspects. Attached Figure Description

[0021] To gain a detailed understanding of how the features of this disclosure are implemented, a more specific description of the content briefly outlined above can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and are therefore not intended to limit its scope, as the specification may acknowledge other equivalent aspects.

[0022] Figure 1 This is a block diagram conceptually illustrating certain aspects of an example telecommunications system based on this disclosure.

[0023] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to certain aspects of this disclosure.

[0024] Figure 3This is a block diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure.

[0025] Figure 4 This is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0026] Figure 5 This is a diagram illustrating an example of implementing a communication protocol stack according to certain aspects of this disclosure.

[0027] Figure 6 Examples of frame formats for new radio (NR) systems are shown, based on certain aspects of this disclosure.

[0028] Figure 7 This demonstrates how different beams can be used to transmit different synchronization signal blocks (SSBs) according to certain aspects of this disclosure.

[0029] Figure 8 An exemplary transport resource mapping is shown in accordance with certain aspects of this disclosure.

[0030] Figure 9 Examples of quasi-co-address (QCL) relationships are shown in accordance with certain aspects of this disclosure.

[0031] Figure 10 Example operations for wireless communication performed by a user equipment (UE) in accordance with certain aspects of this disclosure are shown.

[0032] Figure 11 Example operations for wireless communication performed by a network entity are shown, based on some aspects of this disclosure.

[0033] Figure 12-16 Example scenarios are shown in which various aspects of this disclosure can be utilized.

[0034] To facilitate understanding, the same reference numerals have been used wherever possible to indicate the same elements common to the figures. Elements disclosed in one aspect are intended to be beneficially applied to other aspects without specific description. Detailed Implementation

[0035] Various aspects of this disclosure provide apparatus, devices, methods, processing systems, and computer-readable media for determining downlink reception assumptions when downlink transmission or monitoring events overlap in time.

[0036] The following description provides examples, but is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as needed in the examples. For example, the described methods may be performed in a different order than described, and steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in other examples. For example, an apparatus or method may be implemented using any number of aspects set forth herein. Moreover, the scope of this disclosure is intended to cover apparatuses or methods that are practiced using structures, functions, or structures and functions other than or different from the aspects 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. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects.

[0037] The technologies described in this document can be used in various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), CDMA 2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. CDMA 2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

[0038] New Radio (NR) is an emerging wireless communication technology under development, developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and Improved LTE (LTE-A) are new releases of UMTS that adopt E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used with the wireless networks and radio technologies mentioned above, as well as other wireless networks and radio technologies. For clarity, although aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, aspects of this disclosure can also be applied to communication systems based on other generations, such as 5G and later (including NR technology).

[0039] New radio (NR) access (e.g., 5G technology) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or above), millimeter wave (mmW) targeting high carrier frequencies (e.g., 25 GHz or above), massive machine-type communication (mMTC) targeting non-backward compatible MTC technologies, and / or mission-critical services targeting ultra-reliable low-latency communication (URLLC). These services can include latency and reliability requirements. These services can also have different transmission time intervals (TTIs) to meet corresponding quality of service (QoS) requirements. Furthermore, these services can coexist in the same subframe.

[0040] Example wireless communication system

[0041] Figure 1 An example wireless communication network 100 (e.g., an NR / 5G network) is shown in which aspects of this disclosure can be implemented. For example, the wireless communication network 100 may include a UE 120 and / or a BS 110, the UE 120 being configured to implement... Figure 10 Operation 1000 determines the downlink receive assumed priority ordering based on downlink physical layer (PHY) priority, and BS110 is configured to perform this operation. Figure 11 Operation 1100 determines the downlink receive assumed priority ordering based on downlink physical layer (PHY) priority.

[0042] like Figure 1As shown, the wireless network 100 may include multiple base stations (BS) 110 and other network entities. A BS may be a station communicating with a user equipment (UE). Each BS 110 may provide communication coverage for a specific geographic area. In 3GPP, depending on the context in which the term "cell" is used, it may refer to the coverage area of ​​a Node B (NB) and / or the Node B subsystem serving that coverage area. In NR systems, the term "cell" and Next Generation Node B (gNB), New Radio Base Station (NR BS), 5G NB, Access Point (AP), or Transmitter Receiver Point (TRP) may be interchangeable. In some examples, the cell may not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some examples, base stations may interconnect with each other and / or with one or more other base stations or network nodes (not shown) in the wireless communication network 100 using any suitable transport network through various types of backhaul interfaces (e.g., direct physical connection, wireless connection, virtual network, etc.).

[0043] Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, subband, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0044] A base station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or other types of cells. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with a service subscription. A picocell can cover a relatively small geographic area and can allow unrestricted access by UEs with a service subscription. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UEs associated with that femtocell (e.g., UEs in a closed user group (CSG), UEs for users in a home, etc.). A BS used for macrocells can be called a macro BS. A BS used for picocells can be called a pico BS. A BS used for femtocells can be called a femto BS or a home BS. Figure 1In the example shown, BS 110a, BS 110b, and BS 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BS 110y and BS 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more (e.g., three) cells.

[0045] The wireless communication network 100 may also include relay stations. A relay station is a station that receives data transmissions and / or other information from an upstream station (e.g., a BS or a UE) and transmits data transmissions and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions to other UEs. Figure 1 In the example shown, relay station 110r can communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120r. A relay station can also be referred to as a relay BS, relay, etc.

[0046] Wireless network 100 can be a heterogeneous network comprising different types of BSs (e.g., macro BS, pico BS, femto BS, repeaters, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 20 watts), while pico BSs, femto BSs, and repeaters can have lower transmit power levels (e.g., 1 watt).

[0047] The wireless communication network 100 can support synchronous or asynchronous operation. For synchronous operation, the base stations (BSs) can have similar frame timing, and transmissions from different BSs can be approximately time-aligned. For asynchronous operation, the BSs can have different frame timing, and transmissions from different BSs can be time-disaligned. The techniques described herein can be used for both synchronous and asynchronous operations.

[0048] Network controller 130 can be coupled to a group of BSs and provide coordination and control for these BSs. Network controller 130 can communicate with BS 110 via backhaul. BS 110 can also communicate with each other (e.g., directly or indirectly) via wireless or wired backhaul.

[0049] UE 120 (e.g., UE 120x, UE 120y, etc.) can be distributed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as a mobile station, terminal, access terminal, user unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, home appliance, medical device or medical apparatus, biosensor / device, such as smartwatch, smart clothing, smart glasses, smart bracelet, smart jewelry (e.g., smart bracelet, smart bangle, etc.) wearable device, entertainment device (e.g., music device, video device, satellite radio unit, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, gaming device, augmented reality device (augmented reality (AR), extended reality (XR), or virtual reality (VR)), or any other suitable device configured to communicate via wireless or wired media.

[0050] Some UEs can be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc., that can communicate with a BS, another device (e.g., a remote device), or some other entity. Wireless nodes can provide connectivity to or from a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0051] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, frequency points, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size could be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands respectively.

[0052] While aspects of the examples described herein may be associated with LTE technology, aspects of this disclosure can be applied to other wireless communication systems (e.g., NR). NR can utilize OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission with precoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas with up to 8 streams and up to 2 streams per UE for multilayer DL transmission. Multilayer transmission with up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported.

[0053] In some scenarios, air interface access can be scheduled. For example, a scheduling entity (e.g., base station (BS), node B, eNB, gNB, etc.) can allocate resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. In other words, for scheduled communication, subordinate entities can utilize resources allocated by one or more scheduling entities.

[0054] A base station is not the only entity that can act as a scheduling entity. In some examples, a UE can act as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can use the resources scheduled by that UE for wireless communication. In some examples, a UE can act as a scheduling entity in a peer-to-peer (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0055] Return to Figure 1 This diagram illustrates various potential deployments for different deployment scenarios. For example, in Figure 1 In the diagram, a solid line with a double arrow indicates the desired transmission between the UE and the serving BS, which is designated to serve the UE on the downlink and / or uplink. A thin dashed line with a double arrow indicates interference transmission between the UE and the BS. Other lines indicate component-to-component (e.g., UE-to-UE) communication options.

[0056] Figure 2 Depicting can be done Figure 1 The illustration shows an example logical architecture of a distributed radio access network (RAN) 200 implemented in the wireless communication network 100. A 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be the central unit (CU) of the distributed RAN 200. Backhaul interfaces for the next-generation core network (NG-CN) 204 may terminate at the ANC 202. Backhaul interfaces for adjacent next-generation access nodes (NG-AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more transmit / receive points (TRPs) 208 (e.g., cells, BSs, gNBs, etc.).

[0057] TRP 208 can be a distributed unit (DU). TRP 208 can connect to a single ANC (e.g., ANC 202) or more ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, TRP 208 can connect to more than one ANC. Each TRP 208 may include one or more antenna ports. TRP 208 can be configured to serve services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0058] The logical architecture of the distributed RAN 200 can support a variety of backhaul and fronthauling solutions. This support can occur across and across different deployment types. For example, the logical architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or time base error).

[0059] The logical architecture of the distributed RAN 200 can share features and / or components with LTE. For example, the next-generation access node (NG-AN) 210 can support dual connectivity with NR and can share common fronthaul for LTE and NR.

[0060] The logical architecture of distributed RAN 200 enables collaboration between TRPs 208, for example, within a TRP and / or across TRPs via ANC 202. Inter-TRP interfaces may not be required.

[0061] Logical functions can be dynamically distributed within the logical architecture of the distributed RAN 200. (Refer to...) Figure 5 In more detail, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer can be adaptively arranged at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

[0062] Figure 3 An example physical architecture of a distributed radio access network (RAN) 300 according to various aspects of this disclosure is shown. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU 302 can be centrally deployed. C-CU 302 functions can be offloaded (e.g., offloaded to Advanced Wireless Services (AWS)) to handle peak capacity as best as possible.

[0063] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU 304 can host core network functions locally. The C-RU 304 can be deployed in a distributed manner. The C-RU 304 can be located close to the network edge.

[0064] The DU 306 can host one or more TRPs (Edge Node (EN), Edge Unit (EU), Radio Header Terminal (RH), Smart Radio Header Terminal (SRH), etc.). The DU can be located at the edge of a network with radio frequency (RF) capabilities.

[0065] Figure 4 Showing BS 110 and UE 120 (e.g.) Figure 1 The exemplary components (described herein) can be used to implement aspects of this disclosure. For example, antenna 452, processors 466, 458, 464 and / or controller / processor 480 of UE 120 can be used to perform... Figure 10Operation 1000, and the antenna 434, processors 420, 460, 438 and / or controller / processor 440 of BS 110 can be used to perform Figure 11 Operation 1100.

[0066] At BS 110, transmit processor 420 can receive data from data source 412 and control information from controller / processor 440. The control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. Data can be used for the Physical Downlink Shared Channel (PDSCH), etc. Processor 420 can process the data and control information separately (e.g., encoding and symbol mapping) to obtain data symbols and control symbols. Processor 420 can also generate reference symbols, such as for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). Transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 430 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols (if applicable) and provide an output symbol stream to modulators (MODs) 432a to 432t. Each modulator 432 can process the corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can also further process (e.g., convert to analog signal, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a to 432t can be transmitted via antennas 434a to 434t, respectively.

[0067] At UE 120, antennas 452a to 452r can receive downlink signals from base station 110 and provide the received signals to demodulators (DEMODs) 454a to 454r in the transceiver. Each demodulator 454 can adjust (e.g., filter, amplify, down-convert, and digitize) its respective received signal to obtain an input sample. Each demodulator can further process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 456 can obtain the received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols (if applicable), and provide the detected symbols. Receiver processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120 to data sink 460, and provide decoded control information to controller / processor 480.

[0068] On the uplink, at UE 120, transmit processor 464 can receive and process data from data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller / processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). Transmit processor 464 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signals (SRS)). Symbols from transmit processor 464 can be pre-coded (if applicable) by TX MIMO processor 466, further processed by demodulators 454a to 454r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to base station 110. At BS 110, uplink signals from UE 120 can be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 (if applicable), and further processed by receive processor 438 to obtain the data and control information transmitted by UE 120 to be decoded. The receiver processor 438 can provide decoded data to the data sink 439 and decoded control information to the controller / processor 440.

[0069] Controllers / processors 440 and 480 can respectively direct the operation of base station 110 and UE 120. Processor 440 and / or other processors and modules at BS 110 can execute or direct the execution of processes used in the techniques described herein. Memory 442 and 482 can respectively store data and program code for BS 110 and UE 120. Scheduler 444 can schedule the UE to perform data transmission on the downlink and / or uplink.

[0070] Figure 5 Figure 500 illustrates examples of implementing a communication protocol stack according to various aspects of this disclosure. The illustrated communication protocol stack can be implemented by a device operating in a wireless communication system such as a 5G system (e.g., a system supporting uplink-based mobility). Figure 500 illustrates a communication protocol stack including a Radio Resource Control (RRC) layer 510, a Packet Data Convergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer 520, a Media Access Control (MAC) layer 525, and a Physical (PHY) layer 530. In various examples, the layers of the protocol stack can be implemented as separate software modules, part of a processor or ASIC, part of a non-co-located device connected via a communication link, or various combinations thereof. For example, in a protocol stack for a network access device (e.g., AN, CU, and / or DU) or a UE, co-located and non-co-located implementations can be used.

[0071] Option 505-a illustrates a segmented implementation of the protocol stack, where the implementation of the protocol stack is segmented across a centralized network access device (e.g., Figure 2 ANC 202) and distributed network access devices (e.g., Figure 2 Between DU 208). In option 505-a, the RRC layer 510 and PDCP layer 515 can be implemented by the central unit, and the RLC layer 520, MAC layer 525, and PHY layer 530 can be implemented by the DU. In various examples, the CU and DU can be co-located or non-co-located. Option 505-a may be used in macrocell, microcell, or picocell deployments.

[0072] Option 505-b illustrates a unified implementation of the protocol stack, where the stack is implemented within a single network access device. In this option, the RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 can all be implemented by the AN. Option 505-b may be useful in deployments such as femtocells.

[0073] Regardless of whether the network access device implements part of the protocol stack or the entire protocol stack, the UE can implement the entire protocol stack, as shown in 505-c (e.g., RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525 and PHY layer 530).

[0074] The embodiments discussed herein can include a wide variety of interval and timing deployments. For example, in LTE, the basic transmission time interval (TTI), or packet duration, is a 1ms subframe. In NR, the subframe is still 1ms, but the basic TTI is called a slot. A subframe contains a variable number of slots depending on the subcarrier spacing (e.g., 1, 2, 4, 8, 16 slots). NR RBs are 12 consecutive frequency subcarriers. NR can support a basic subcarrier spacing of 15kHz and can define other subcarrier spacings relative to the basic subcarrier spacing (e.g., 30kHz, 60kHz, 120kHz, 240kHz, etc.). Symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

[0075] Figure 6This is a diagram illustrating an example of frame format 600 for NR. The transmission timeline for each of the downlink and uplink can be divided into units of radio frames. Each radio frame can have a predetermined duration (e.g., 10 ms) and can be divided into 10 subframes indexed from 0 to 9, each subframe being 1 ms long. Each subframe can include a variable number of time slots depending on the subcarrier spacing. Each time slot can include a variable number of symbol periods depending on the subcarrier spacing (e.g., 7 or 14 symbols). An index can be assigned to the symbol periods in each time slot. Micro-slots are sub-slot structures (e.g., 2, 3, or 4 symbols).

[0076] Each symbol in a time slot can indicate the link direction used for data transmission (e.g., DL, UL, or flexible), and the link direction used for each subframe can be dynamically switched. The link direction can be based on the time slot format. Each time slot can include DL / UL data and DL / UL control information.

[0077] In NR, a synchronization signal (SS) block (SSB) is transmitted. The SS block consists of the PSS, SSS, and a two-symbol PBCH. It can be transmitted at a fixed time slot location (e.g., such as...). Figure 6 Symbols 0-3 shown in the diagram transmit SS blocks. PSS and SSS can be used by the UE for cell search and acquisition. PSS can provide half-frame timing, and SS can provide CP length and frame timing. PSS and SSS can provide cell identification. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set period, system frame number, etc.

[0078] Other system information, such as Residual Minimum System Information (RMSI), System Information Block (SIB), and Other System Information (OSI), can be transmitted on the Physical Downlink Shared Channel (PDSCH) in certain subframes.

[0079] like Figure 7 As shown, SS blocks can be organized into SS burst sets to support beam scanning. As illustrated, different beams can be used to transmit each SSB in the burst set, which helps the UE quickly acquire both the transmit (Tx) and receive (Rx) beams (especially for mmW applications). The Physical Cell Identifier (PCI) can still be decoded from the PSS and SSS of the SSB.

[0080] Some deployment scenarios may include one or two NR deployment options. Some can be configured as non-standalone (NSA) and / or standalone (SA) options. Standalone cells may need to broadcast both SSBs and Residual Minimum System Information (RMSI) (e.g., using SIB1 and SIB2). Non-standalone cells may only need to broadcast SSBs without broadcasting RMSIs. In a single NR carrier, multiple SSBs can be transmitted on different frequencies and can include different types of SSBs.

[0081] Control Resource Set (CORESET)

[0082] A control resource set (CORESET) for an OFDMA system (e.g., a communication system that transmits PDCCH using OFDMA waveforms) may include one or more sets of control resources (e.g., time and frequency resources) configured to transmit PDCCH within the system bandwidth. Within each CORESET, one or more search spaces (e.g., common search space (CSS), UE-specific search space (USS), etc.) may be defined for a given UE. A search space is typically an area or portion in which a communication device (e.g., a UE) can search for control information.

[0083] According to various aspects of this disclosure, a CORESET is a set of time-domain and frequency-domain resources defined in units of Resource Element Groups (REGs). Each REG may include a fixed number (e.g., twelve) tones in a symbol period (e.g., a symbol period of a time slot), where one tone in a symbol period is called a Resource Element (RE). A fixed number of REGs may be included in Control Channel Elements (CCEs). The set of CCEs may be used to transmit a new radio PDCCH (NR-PDCCH), where different numbers of CCEs in the set are used to transmit the NR-PDCCH using different aggregation levels. Multiple sets of CCEs may be defined as a search space for the UE, and thus a NodeB or other base station may transmit an NR-PDCCH to the UE by transmitting an NR-PDCCH in the set of CCEs defined as decoding candidates within the search space for the UE, and the UE may receive the NR-PDCCH by searching within the search space for the UE and decoding the NR-PDCCH transmitted by the NodeB.

[0084] The operational characteristics of a Node B or other base station in an NR communication system can depend on the frequency range (FR) in which the system operates. A frequency range may include one or more operating bands (e.g., the “n1” band, “n2” band, “n7” band, and “n41” band), and the communication system (e.g., one or more NodeBs and UEs) may operate within one or more operating bands. Frequency ranges and operating bands are described in more detail in TS38.104 (Revision 15), “Base Station (BS) Radio Transmission and Reception,” which is available from the 3GPP website.

[0085] As described above, a CORESET is a set of time-domain and frequency-domain resources. A CORESET can be configured to transmit PDCCH within the system bandwidth. The UE can determine the CORESET and monitor it for control channels. During initial access, the UE can identify the initial CORESET (CORESET#0) configuration from fields in the Master Information Block (MIB) (e.g., pdcchConfigSIB1). This initial CORESET can then be used to configure the UE, for example, via dedicated (UE-specific) signaling to configure other CORESETs and / or bandwidth portions. When the UE detects a control channel in a CORESET, the UE attempts to decode the control channel and communicate with the sending base station (e.g., the sending cell) based on the control data provided in the control channel (e.g., transmitted via the CORESET).

[0086] According to various aspects of this disclosure, when a UE connects to a cell (or BS), the UE can receive a Master Information Block (MIB). The MIB can be located in a synchronization signal and a physical broadcast channel (SS / PBCH) block on a synchronization raster (e.g., in the PBCH of the SS / PBCH block). In some scenarios, the synchronization raster may correspond to an SSB. Based on the frequency of the synchronization raster, the UE can determine the operating frequency band of the cell. Based on the operating frequency band of the cell, the UE can determine the minimum channel bandwidth and subcarrier spacing (SCS) of the channel. The UE can then determine an index (e.g., four bits in the MIB that transmit an index in the range of 0-15) based on the MIB.

[0087] Given this index, the UE can look up or locate the CORESET configuration (the initial CORESET configured via the MIB is typically referred to as CORESET#0). This can be done based on one or more tables of CORESET configuration. These configurations (including single-table scenarios) can include various subsets of indexes that indicate valid CORESET configurations for various combinations of minimum channel bandwidth and SCS. In some arrangements, each combination of minimum channel bandwidth and SCS can be mapped to a subset of indexes in the tables.

[0088] Alternatively or additionally, the UE can select a search space CORESET configuration table from several tables of CORESET configurations. These configurations can be based on minimum channel bandwidth and SCS. The UE can then look up the CORESET configuration from the selected table based on that index (e.g., Type 0-PDCCH search space CORESET configuration). After determining the CORESET configuration (e.g., from a single table or from the selected table), the UE can then determine the CORESET to monitor (as described above) based on the location (in time and frequency) of the SS / PBCH block and the CORESET configuration.

[0089] Figure 8 An exemplary transport resource mapping 800 is shown according to various aspects of this disclosure. In the exemplary mapping, the BS (e.g., Figure 1 The BS 110a shown transmits SS / PBCH block 802. The SS / PBCH block includes a MIB, which transmits an index to the following table: this table correlates the time and frequency resources of CORESET 804 with the time and frequency resources of the SS / PBCH block.

[0090] The BS can also send control signaling. In some scenarios, the BS can also send control signaling to the UE (e.g., in CORESET (time / frequency resources)). Figure 1 The UE (120) shown in the diagram sends a PDCCH. The PDCCH can schedule PDSCH 806. The BS then sends the PDSCH to the UE. The UE can receive the MIB in the SS / PBCH block, determine the index, look up the CORESET configuration based on the index, and determine the CORESET according to the CORESET configuration and the SS / PBCH block. The UE can then monitor the CORESET, decode the PDCCH in the CORESET, and receive the PDSCH allocated by the PDCCH.

[0091] Different CORESET configurations can have different parameters used to define the corresponding CORESET. For example, each configuration can indicate the number of resource blocks (e.g., 24, 48, or 96), the number of symbols (e.g., 1-3), and the offset of the position in terms of frequency (e.g., 0-38 RBs).

[0092] QCL port and TCI status

[0093] In many cases, it is important for the UE to know what assumptions it can make on the channel corresponding to different transmissions. For example, the UE may need to know which reference signals it can use to estimate the channel in order to decode the transmitted signals (e.g., PDCCH or PDSCH). It may also be important for the UE to be able to report relevant Channel State Information (CSI) to the BS (gNB) for scheduling, link adaptation, and / or beam management purposes. In NR, the concepts of Quasi-Co-location (QCL) and Transport Configuration Indicator (TCI) states are used to convey information about these assumptions.

[0094] The QCL assumption is typically defined based on channel attributes. According to 3GPP TS 38.214, “If the attributes of the channel through which symbols are transmitted on one antenna port can be derived from the channel through which symbols are transmitted on another antenna port, then the two antenna ports are said to be quasi-co-located.” If a receiver (e.g., a UE) can apply the channel attributes determined by detecting a first reference signal to aid in the detection of a second reference signal, then these different reference signals can be considered quasi-co-located (“QCL'd”). TCI states typically include configurations such as QCL relationships (e.g., the QCL relationship between DL RS and PDSCH DMRS ports in a CSI-RS set).

[0095] In some cases, a UE can be configured with up to M TCI states. The configuration of these M TCI states can be achieved through higher-layer signaling, while the UE can be signaled to decode the PDSCH based on the detected PDCCH containing a DCI indicating one of the TCI states. Each configured TCI state can include an RS set TCI-RS-SetConfig, which indicates different QCL assumptions between certain source and target signals.

[0096] Figure 9 An example is shown of the association between the DL reference signal and the corresponding QCL type that can be indicated by TCI-RS-SetConfig.

[0097] exist Figure 9In the example, the source reference signal (RS) is indicated in the top block and associated with the target signal indicated in the bottom block. In this context, the target signal generally refers to a signal whose channel properties can be inferred by measuring those channel properties of the associated source signal. As described above, the UE can use the source RS to determine various channel parameters based on the associated QCL type and use these various channel properties (determined based on the source RS) to process the target signal. The target RS does not necessarily need to be the DMRS of the PDSCH; more precisely, it can be any other RS: PUSCH DMRS, CSIRS, TRS, and SRS.

[0098] As shown, each TCI-RS-SetConfig contains parameters. For example, these parameters can configure the quasi-co-address relationship between the RSs in the reference signal set and the DM-RS port group of the PDSCH. The RS set contains references to one or two DL RSs, and the associated quasi-co-address type (QCL-Type) for each RS configured by the higher-level parameter QCL-Type.

[0099] like Figure 9 As shown, the QCL type can be arranged in various ways for the case of two DL RSs. For example, the QCL types may be different regardless of whether the reference signal is for the same DL RS or different DL RSs. In the example shown, the SSB is associated with type C QCL for P-TRS, while the CSI-RS (CSIRS-BM) for beam management is associated with type D QCL.

[0100] In some scenarios, QCL information and / or type may depend on other information or be a function of other information. For example, the quasi-co-address (QCL) type indicated to the UE may be based on the higher-layer parameter QCL-Type and may take one or a combination of the following types:

[0101] QCL Type A: {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0102] QCL type B: {Doppler frequency shift, Doppler spread}

[0103] QCL type C: {Average delay, Doppler shift} and

[0104] QCL type D: {space Rx parameter},

[0105] Spatial QCL assumptions (QCL type D) can be used to help the UE select analog Rx beams (e.g., during beam management procedures). For example, an SSB resource indicator can indicate that the same beam for a previous reference signal should be used for subsequent transmissions.

[0106] During initial access, the initial CORESET (e.g., CORESET ID 0 or simply CORESET#0) in the NR can be identified (e.g., via a field in the MIB). The ControlResourceSet Information Element (CORESET IE), transmitted via Radio Resource Control (RRC) signaling, can convey information about the CORESET configured for the UE. The CORESET IE typically includes the CORESET ID, an indication of the frequency domain resources allocated to the CORESET (e.g., the number of RBs), the consecutive duration of the CORESET across multiple symbols, and the Transmission Configuration Indicator (TCI) status.

[0107] As described above, a subset of TCI states provides a quasi-co-address (QCL) relationship between DL RS and PDCCH demodulation RS (DMRS) ports in an RS set (e.g., TCI-Set). A specific TCI state (e.g., for unicast PDCCH) for a given UE can be transmitted to the UE via a Media Access Control (MAC) control element (MAC-CE). The specific TCI state is typically selected from a set of grouped TCI states transmitted via the CORESET IE, where the initial CORESET (CORESET#0) is typically configured via the MIB.

[0108] Search space information can also be provided via RRC signaling. For example, a search space IE is another RRC IE that defines how and where to search for PDCCH candidates for a given CORESET. Each search space is associated with a CORESET. The search space IE identifies the search space configured for a CORESET by a search space ID. In one aspect, the search space ID associated with CORESET#0 is search space ID#0. Search spaces are typically configured via PBCH (MIB).

[0109] Example downlink quasi-co-location (QCL) priority sorting based on downlink physical layer (PHY) priority.

[0110] As mentioned above, certain assumptions, such as the QCL assumption, can help the UE handle downlink transmissions. In some cases, overlapping downlink transmissions may have different QCL assumptions. Various aspects of this disclosure provide techniques that can help the UE prioritize one downlink transmission or another to handle overlapping downlink transmissions.

[0111] The UE can communicate on different operating frequency ranges, such as frequency range 1 (FR1) which includes a frequency band below 6 GHz, and frequency range 2 (FR2) which includes a frequency band from 24.25 GHz to 52.6 GHz.

[0112] In the current system, on FR2, the QCL priority ordering among overlapping PDSCHs can depend on the UE implementation, except in cases where System Information (SI) capture is triggered by Paging Radio Network Temporary Identifier (P-RNTI). In this case, the UE prioritizes PDSCHs scheduled via SI-RNTI over those scheduled via Cell RNTI (C-RNTI), Modulation and Coding Scheme C-RNTI (MCS-C-RNTI), and Configured Scheduling (CS-RNTI). In this situation, the UE may make unintended decisions for any other type of DL priority indication, such as abandoning such transmissions to support other transmissions (e.g., URLLC).

[0113] In some cases, priority levels can be assigned to different types of uplink and / or downlink physical layer (PHY) transmissions. For example, two levels of PHY priority (high and low) can be indicated for uplink transmissions. Example priorities may be shown below:

[0114] For SRs, configure priorities for each SR resource;

[0115] For P / SP CSI reports on PUCCH, the priority is low;

[0116] For AP / SP CSI reports on PUSCH, the priority is the same as that for PUSCH instructions;

[0117] For UL DG, the priority is indicated in DCI;

[0118] For UL CG, the priority is based on the RRC configuration configured for Type 1 and Type 2 CG;

[0119] (Re)activating DCI cannot override the priority of the RRC configuration;

[0120] For the A / N of DL DG, the priority is indicated in DCI;

[0121] For SPS A / N, the priority is based on the RRC configuration of SPS;

[0122] For PRACH, no priority is defined; and

[0123] For SRS, P / SP SRS and AP SRS triggered by DCI format 2_3 have lower priority.

[0124] The PHY priority level used for downlink reception can also have use cases at least in FR2. An example of a downlink transmission PHY priority level is shown below. For PDCCH transmission:

[0125] Option 1: DL PHY priority can be indicated for each CORESET or SS, for example, in the RRC IE of ControlResourceSet.

[0126] Option 2: If different pool indexes are configured, DL PHY optimization can be indicated for each CORESET pool index.

[0127] Priority

[0128] Option 3: The DL PHY priority can be indicated in the PDCCH itself.

[0129] For DL ​​channels / RS associated with UL feedback, such as CSI-RS+CSI reports on PDSCH or PUCCH / PUSCH with acknowledgments (+A / N):

[0130] DL PHY priority can be the same as UL PHY priority for UL feedback indication.

[0131] For DL ​​channels / RS scheduled via DCI (e.g., PDSCH, AP CSI-RS), with or without UL feedback:

[0132] Individual DL PHY priorities can be specified in the DCI.

[0133] For DL ​​channels / RS configured via RRC or activated via DCI / MAC-CE

[0134] (For example, SPS, P / SP CSI-RS):

[0135] Option 1: DL PHY priority can be configured in the corresponding RRC IE; or

[0136] Option 2: The DL PHY priority can be indicated when activating DCI / MAC-CE.

[0137] Various aspects of this disclosure provide a set of rules that can help a UE determine how to prioritize downlink reception assumptions (e.g., in FR2) in situations where multiple time-overlapping DL channels and / or reference signals (RS) have conflicting reception (e.g., QCL) assumptions. While some examples described herein may refer to prioritizing QCL assumptions, the techniques described herein can be applied more generally to any type of reception assumption.

[0138] For example, the UE can prioritize the QCL of the DL channel / RS with the highest PHY priority. As will be described in more detail below, if multiple DL channels / RS with the same high priority but different QCLs exist, existing rules (e.g., R15 / 16 rules) can be further applied to generate the final priority-ordered QCLs. This technique can be applied to processing various types of DL channels and RSs (e.g., including PDCCH, PDSCH, and CSI-RS).

[0139] Figure 10 Example operation 1000 for wireless communication performed by a wireless node (such as a UE) according to certain aspects of this disclosure is illustrated. For example, operation 1000 can be performed by... Figure 1 The UE 120 performs this to determine the reception assumptions for overlapping downlink transmissions.

[0140] At 1002, Operation 1000 begins by receiving signaling indicating the downlink physical layer priority level for downlink transmission and monitoring timing.

[0141] At point 1004, when at least two downlink transmission and monitoring opportunities overlap in time, the UE determines the reception assumption to be used based on one or more rules.

[0142] At 1006, the UE processes the at least two downlink transmission and monitoring opportunities that overlap in time, based on the reception assumption.

[0143] Figure 11 Example operation 1100 is shown. Example operation 1100 is used for wireless communication performed by a network entity and can be considered as... Figure 10 The complementary operation to operation 1000. For example, operation 1100 can be performed by the gNB that schedules the transmission to UE 120, where UE 120 performs... Figure 10 Operation 1000. In this way, the gNB and UE can agree on which QCL the UE prioritizes; for example, the gNB can then transmit more important information via the corresponding beam.

[0144] At 1102, operation 1100 begins by sending signaling to the user equipment (UE) indicating the downlink priority level for downlink transmission and monitoring timing.

[0145] At 1104, when at least two downlink transmission or monitoring events overlap in time, the reception assumption to be used is determined based on one or more rules.

[0146] At 1106, the network entity processes at least two downlink transmission and monitoring opportunities based on the reception assumption.

[0147] The techniques presented herein can be applied regardless of whether overlapping DL channels / RS (e.g., QCLs with conflicts) are in the same or different CCs, or in the same CC but from the same or different TRPs.

[0148] The aforementioned techniques may be useful because gNBs may not be able to completely avoid conflicting QCLs for various reasons. For example, a newly scheduled URLLC PDSCH may have to overlap with a previously scheduled eMBB PDSCH. As another example, two TRPs that are not closely coordinated may independently schedule overlapping PDSCHs with conflicting QCLs. Furthermore, URLLC SPSs may sometimes overlap with eMBB SPSs.

[0149] In some cases, more than two levels of DL PHY priority can be used, in which case the highest level among all overlapping levels can be prioritized. In some situations, scenarios where multiple overlapping DL channels / RS have conflicting QCLs and different DL PHY priority levels can be considered error conditions (e.g., the UE might not expect it to occur) and should not be handled using priority rules.

[0150] In some cases, QCL prioritization rules can depend on the number of repetitions of one of the overlapping DL channels / RS. According to one option, QCL priority can depend entirely on the number of repetitions (regardless of the DL PHY priority level). In other words, the QCL of the DL channel / RS with the most (or fewest) repetitions can be prioritized, regardless of its DL PHY priority. Alternatively, QCL prioritization can depend on the number of repetitions in addition to DL PHY priority. For example, among DL channels / RS with the same PHY priority, the QCL of the DL channel / RS with the most (or fewest) repetitions can be prioritized.

[0151] For example, depending on the type of overlapping downlink transmissions or monitoring timing, the techniques described in this paper can be applied to a variety of use cases.

[0152] For example, in a first use case, the technique can be applied to overlapping PDSCH transmissions. As described above, in current systems, the QCL priority allocation between overlapping PDSCHs can depend on the UE implementation, except in the case of P-RNTI-triggered SI capture, in which case the UE prioritizes PDSCHs scheduled via SI-RNTI compared to PDSCHs scheduled via C-RNTI, MCS-C-RNTI, and CS-RNTI within the same cell. Without any DL priority indication, the UE may discard one PDSCH transmission (e.g., eMBB) because of another PDSCH transmission (e.g., URLLC).

[0153] Based on the aspects presented in this paper, the UE can prioritize reception assumptions based on the DL PHY level. For example, the techniques presented in this paper can be applied to... Figure 12 In the example shown, two PDSCH transmissions with scheduling offsets greater than the PDSCH beam switching delay threshold (e.g., meaning they may not have time to apply the newly indicated beam) overlap, and they have different QCL types D (beams) and different DL PHY priorities. In this case, the UE can prioritize the QCL of the PDSCH with the higher DL PHY priority. If multiple PDSCHs have the same high DL PHY priority level, the UE can prioritize the QCL within the higher priority PDSCH based on existing rules (e.g., based on the UE implementation).

[0154] In some cases, if the UE successfully decodes a PDSCH transmission (e.g., PDSCH 1), but the gNB misses the corresponding ACK, it will retransmit PDSCH 1. Figure 13 As shown, the retransmitted PDSCH 1 with high DL priority overlaps with the newly transmitted PDSCH 2 with low DL priority. In this case, since the UE has successfully decoded PDSCH 1, the UE can prioritize the QCL of the previously undecoded PDSCH 2. In some cases, at least when the A / N of PDSCH 1 and PDSCH 2 share the same HARQ ACK information codebook, the UE can send an ACK (positive acknowledgment) for PDSCH 1 even if the retransmitted PDSCH 1 has not been decoded.

[0155] In the second use case, the technique can be applied to overlapping PDCCH transmissions. In current systems (e.g., R15 / 16), if a common search space (CSS) exists configured in multiple overlapping search spaces (SSs), the QCL with the lowest ID in the cell with the lowest ID is given priority. Without any PHY DL priority indication, the UE can discard the user-specific search space (USS) for scheduling URLLC, which may not allow scheduling on the preferred CSS (e.g., Type 0 / 0A / 1 / 2 CSS, or Type 3 CSS on the SCell). Type 0 / Type 0A CSS is for SI-RNTI, Type 1 CSS is for RA-RNTI or TC-RNTI, and Type 2 CSS is for P-RNTI. Type 3 CSS can be for C-RNTI, MCS-C-RNTI, or CS-RNTI, but is limited to the SCell. The RRC structure does not prohibit Type 3 CSS configured on the SCell.

[0156] Based on the aspects presented in this paper, the UE can prioritize the reception assumptions for overlapping PDCCH monitoring timing based on the DL PHY level. For example, the techniques presented in this paper can be applied to... Figure 14 The example shown illustrates two PDCCH monitoring events that overlap in time and have different QCL types (D) and different DL PHY priorities. In this case, the UE can prioritize the QCL of the monitoring event with the higher DL PHY priority. If multiple events have the same high DL PHY priority, the UE can prioritize the QCLs based on another rule (e.g., rule R15, within high-priority monitoring events).

[0157] In the third use case, the technique can be applied to overlapping PDCCH and PDSCH transmissions. In current systems (e.g., R15 / 16), the priority ordering between overlapping PDCCH and PDSCH may depend on the UE implementation.

[0158] Based on the aspects presented in this paper, when the PDCCH monitoring timing overlaps with the PDSCH transmission, the UE can prioritize the reception assumptions based on the DL PHY level. For example, the techniques presented in this paper can be applied to... Figure 15 In the example shown, at least one PDCCH monitoring timing overlaps in time with at least one PDSCH (with a scheduling offset greater than the PDSCH beam switching delay threshold) having different QCL type D and DL PHY priority. Figure 15 The example in the image shows two PDCCH monitoring times and two PDSCH transmissions.

[0159] In such cases, the UE can prioritize the QCL of the DL channel with the highest DL PHY priority. If multiple DL channels have high priorities, there are several options for prioritizing QCLs. For example, if there are multiple PDCCH monitoring opportunities instead of PDSCH, the UE can prioritize QCLs based on the R15 rule within the high-priority opportunities. If there are multiple PDSCHs but no PDCCH monitoring opportunities, the UE can prioritize QCLs based on the R15 rule within the high-priority PDSCHs.

[0160] If there is at least one PDCCH monitoring opportunity and at least one PDSCH, such as Figure 15 As shown, which PDCCH / PDSCH QCL is prioritized can depend on the UE implementation. If PDCCH QCL is prioritized, then during high-priority times, the previous rule (e.g., rule R15) is utilized.

[0161] In the fourth use case, the technique can be applied to situations where CSI-RS overlaps with PDCCH or PDSCH. In the current system, in this case, the UE can assume that the overlapping CORESET and the configured CSI-RS (except for repeated ON) are of type DQCL. However, the UE can assume that the configured CSI-RS with repeated ON does not overlap with the CORESET. Without any DL priority indication, the UE can discard CSI-RS with a QCL different from the overlapping CORESET and corresponding to a high-priority CSI report.

[0162] Based on the aspects presented in this paper, the UE can prioritize the reception of CSI-RS or overlapping PDCCH or PDSCH based on the DL PHY priority level. For example, the techniques presented in this paper can be applied to... Figure 16 The example scenario shown illustrates an overlap between CSI-RS (assuming repetition is not ON) and PDCCH monitoring timings. This example assumes that CSI-RS and PDCCH monitoring timings have different QCL types (D) and different DL PHY priorities. In this case, the UE can prioritize the QCL of the DL transmission with the higher DL PHY priority. When CSI-RS and PDCCH overlap with different QCL and DL PHY priorities, the same type of priority rule can be applied.

[0163] The techniques presented in this paper can also be extended to scenarios with multiple transmit / receive points (multiple TRPs) where different CORESET pool indices are configured (and each different CORESET pool index corresponds to a different TRP). In this case, the rules described above for prioritizing QCLs (e.g., based on DL PHY priority) can be applied to DL channels / RS scheduled by or associated with the same CORESET pool index. For example, assuming the UE can simultaneously receive any combination of DL channels / RS from different CORESET pool indices (with no QCL conflict between the two TRPs), priority rules can be applied for each CORESET pool index.

[0164] In addition to the aspects described above, aspects of specific combinations are also within the scope of this disclosure, some of which are described in detail below:

[0165] Aspect 1: A method for wireless communication by a wireless node, comprising: receiving signaling indicating a downlink priority level for downlink transmission and monitoring timing; determining a reception assumption to be used based on one or more rules when at least two downlink transmission and monitoring timings overlap in time; and processing at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0166] Aspect 2: According to the method of aspect 1, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0167] Aspect 3: The method according to any one of Aspects 1-2, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0168] Aspect 4: The method according to any one of Aspects 1-3, wherein the downlink transmission includes physical downlink shared channel (PDSCH) transmission having an offset associated with physical downlink control channel (PDCCH) that is equal to or greater than a beam switching delay threshold.

[0169] Aspect 5: The method according to any one of Aspects 1-4, wherein, according to at least a first rule in the rules, it is determined that the receiving assumption is that the receiving is performed using the one with the highest downlink priority level among at least two downlink transmission and monitoring opportunities that overlap in time during the receiving of downlink transmission and monitoring opportunities.

[0170] Aspect 6: The method according to any one of Aspects 1-5, wherein, according to at least the second rule in the rules: if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0171] Aspect 7: The method according to aspect 5, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0172] Aspect 8: The method according to any one of Aspects 1-7 further comprises, according to at least one of the rules, considering those downlink transmission and monitoring moments that overlap in time and have different assumptions and different downlink priorities as errors.

[0173] Aspect 9: The method according to any one of Aspects 1-8, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0174] Aspect 10: The method according to aspect 9, wherein, according to at least one of the rules, it is determined that the receiver assumption is the one with the most or least repetition among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0175] Aspect 11: According to the method of aspect 9, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least repetition among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0176] Aspect 12: The method according to any one of Aspects 1-11, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0177] Aspect 13: The method according to any one of Aspects 1-12, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0178] Aspect 14: The method according to any one of Aspects 1-13, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, using the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities.

[0179] Aspect 15: The method according to any one of Aspects 1-14, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0180] Aspect 16: The method according to any one of Aspects 1-15, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of either the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0181] Aspect 17: The method according to any one of Aspects 1-16, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; and the method further includes: applying one or more rules to determine a reception assumption for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0182] Aspect 18: The method according to any one of Aspects 1-17, wherein, if different control resource set (CORESET) pool indices are configured, the signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0183] Aspect 19: The method according to any one of Aspects 1-18, wherein, for downlink transmissions, monitoring timings, or downlink transmissions and monitoring timings associated with uplink feedback, the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication.

[0184] Aspect 20: The method according to any one of Aspects 1-19, wherein the downlink priority level for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI) is signaled in the DCI.

[0185] Aspect 21: The method according to any one of Aspects 1-20, wherein for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) Control Element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information Elements (IE) or via the DCI or MAC CE used for activation.

[0186] Aspect 22: A method for wireless communication by a network entity, comprising: sending signaling to a wireless node indicating a downlink priority level for downlink transmission and monitoring timing; determining a reception assumption to be used based on one or more rules when at least two downlink transmission or monitoring timings overlap in time; and processing at least two downlink transmission and monitoring timings based on the reception assumption.

[0187] Aspect 23: According to the method of aspect 22, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0188] Aspect 24: The method according to any one of Aspects 22-23, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0189] Aspect 25: The method according to any one of Aspects 22-24, wherein the downlink transmission includes physical downlink shared channel (PDSCH) transmission having an offset associated with physical downlink control channel (PDCCH) equal to or greater than a beam switching delay threshold.

[0190] Aspect 26: The method according to any one of Aspects 22-25, wherein, according to at least a first rule in the rules, it is determined that the receiving assumption is that the receiving is performed using the one with the highest downlink priority level among at least two downlink transmission and monitoring opportunities that overlap in time during the receiving of downlink transmission and monitoring opportunities.

[0191] Aspect 27: The method according to any one of Aspects 22-26, wherein, according to at least the second rule in the rules: if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0192] Aspect 28: The method according to aspect 26, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0193] Aspect 29: The method according to any one of Aspects 22-28, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0194] Aspect 30: The method according to aspect 29, wherein, according to at least one of the rules, it is determined that the receiver assumption is the one with the most or least repetition among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0195] Aspect 31: The method according to aspect 29, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least overlap among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0196] Aspect 32: The method according to any one of Aspects 22-31, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0197] Aspect 33: The method according to any one of Aspects 22-32, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0198] Aspect 34: The method according to any one of Aspects 22-33, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and the reception assumption of using the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities is determined according to at least one of the rules.

[0199] Aspect 35: The method according to any one of Aspects 22-34, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0200] Aspect 36: The method according to any one of Aspects 22-35, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of either the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0201] Aspect 37: The method according to any one of Aspects 22-36, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; and the method further includes: applying one or more rules to determine a reception assumption for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0202] Aspect 38: The method according to any one of Aspects 22-37, wherein, if different control resource set (CORESET) pool indices are configured, the signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0203] Aspect 39: The method according to any one of Aspects 22-38, wherein, for downlink transmissions, monitoring timings, or downlink transmissions and monitoring timings associated with uplink feedback, the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication.

[0204] Aspect 40: The method according to any one of Aspects 22-39, wherein the downlink priority level for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI) is signaled in the DCI.

[0205] Aspect 41: The method according to any one of Aspects 22-40, wherein for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) control element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information Elements (IE) or via the DCI or MAC CE used for activation.

[0206] Aspect 42: A wireless node comprising: a unit for receiving signaling indicating a downlink priority level for downlink transmission and monitoring timing; a unit for determining a reception assumption to be used based on one or more rules when at least two downlink transmission and monitoring timings overlap in time; and a unit for processing at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0207] Aspect 43: The wireless node according to aspect 42, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0208] Aspect 44: A wireless node according to any one of Aspects 42-43, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0209] Aspect 45: A wireless node according to any one of Aspects 42-44, wherein the downlink transmission includes physical downlink shared channel (PDSCH) transmission having an offset associated with physical downlink control channel (PDCCH) that is equal to or greater than a beam switching delay threshold.

[0210] Aspect 46: A wireless node according to any one of Aspects 42-45, wherein, according to at least a first rule in the rules, it is determined that the receiver uses the one with the highest downlink priority level among at least two downlink transmission and monitoring opportunities that overlap in time during the reception of downlink transmission and monitoring opportunities.

[0211] Aspect 47: A wireless node according to any one of Aspects 42-46, wherein, according to at least the second rule in the rules, if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0212] Aspect 48: The wireless node according to aspect 46, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0213] Aspect 49: The wireless node according to any one of Aspects 42-48 further includes, according to at least one of the rules, units that are deemed to be erroneous in at least two downlink transmission and monitoring moments that overlap in time during downlink transmission and monitoring.

[0214] Aspect 50: A wireless node according to any one of Aspects 42-49, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0215] Aspect 51: The wireless node according to aspect 50, wherein, according to at least one of the rules, it is determined that the receiver assumption is the one with the most or least repetition among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0216] Aspect 52: The wireless node according to aspect 50, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least overlap among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0217] Aspect 53: A wireless node according to any one of Aspects 42-52, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0218] Aspect 54: A wireless node according to any one of Aspects 42-53, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0219] Aspect 55: A wireless node according to any one of Aspects 42-54, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules to be the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities.

[0220] Aspect 56: A wireless node according to any one of Aspects 42-55, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0221] Aspect 57: A wireless node according to any one of Aspects 42-56, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0222] Aspect 58: A wireless node according to any one of aspects 42-57, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; and the wireless node further includes: a unit for applying one or more rules to determine reception assumptions for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0223] Aspect 59: A radio node according to any one of Aspects 42-58, wherein, if different control resource set (CORESET) pool indices are configured, signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0224] Aspect 60: A wireless node according to any one of Aspects 42-59, wherein the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication for the downlink transmission, monitoring timing, or downlink transmission and monitoring timing associated with uplink feedback.

[0225] Aspect 61: A wireless node according to any one of Aspects 42-60, wherein the downlink priority level for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI) is signaled in the DCI.

[0226] Aspect 62: A wireless node according to any one of Aspects 42-61, wherein, for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) Control Element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information Elements (IE) or via the DCI or MAC CE used for activation.

[0227] Aspect 63: A network entity comprising: a unit for sending signaling to a radio node indicating a downlink priority level for downlink transmission and monitoring timing; a unit for determining a reception assumption to be used based on one or more rules when at least two downlink transmission or monitoring timings overlap in time; and a unit for processing at least two downlink transmission and monitoring timings based on the reception assumption.

[0228] Aspect 64: The network entity according to aspect 63, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0229] Aspect 65: A network entity according to any one of Aspects 63-64, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0230] Aspect 66: A network entity according to any one of Aspects 63-65, wherein the downlink transmission includes physical downlink shared channel (PDSCH) transmission having an offset associated with physical downlink control channel (PDCCH) that is equal to or greater than a beam switching delay threshold.

[0231] Aspect 67: A network entity according to any one of Aspects 63-66, wherein, according to at least a first rule in the rules, it is determined that the receiving assumption is that the receiving is performed using the one with the highest downlink priority level among at least two time-overlapping downlink transmission and monitoring opportunities for receiving downlink transmission and monitoring opportunities.

[0232] Aspect 68: A network entity according to any one of Aspects 63-67, wherein, according to at least the second rule in the rules: if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0233] Aspect 69: The network entity according to aspect 67, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0234] Aspect 70: A network entity according to any one of Aspects 63-69, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0235] Aspect 71: The network entity according to aspect 70, wherein, according to at least one of the rules, it is determined that the receiver assumption is the one with the most or least overlap among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0236] Aspect 72: The network entity according to aspect 70, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least overlap among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0237] Aspect 73: A network entity according to any one of Aspects 63-72, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0238] Aspect 74: A network entity according to any one of Aspects 63-73, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0239] Aspect 75: A network entity according to any one of Aspects 63-74, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules to be the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities.

[0240] Aspect 76: A network entity according to any one of Aspects 63-75, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0241] Aspect 77: A network entity according to any one of Aspects 63-76, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of either the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0242] Aspect 78: A network entity according to any one of Aspects 63-77, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; and the network entity further includes: a unit for applying one or more rules to determine reception assumptions for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0243] Aspect 79: A network entity according to any one of Aspects 63-78, wherein, if different control resource set (CORESET) pool indices are configured, signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0244] Aspect 80: A network entity according to any one of Aspects 63-79, wherein the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication for the downlink transmission, monitoring timing, or downlink transmission and monitoring timing associated with the uplink feedback.

[0245] Aspect 81: A network entity according to any one of Aspects 63-80, wherein its downlink priority level is signaled in the DCI for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI).

[0246] Aspect 82: A network entity according to any one of Aspects 63-81, wherein, for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) Control Element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information Elements (IE) or via the DCI or MAC CE used for activation.

[0247] Aspect 83: A wireless node comprising: a receiver configured to: receive signaling indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: when at least two downlink transmission and monitoring timings overlap in time, determine a reception assumption to be used based on one or more rules, and process the at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0248] Aspect 84: The wireless node according to aspect 83, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0249] Aspect 85: A wireless node according to any one of Aspects 83-84, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0250] Aspect 86: A wireless node according to any one of aspects 83-85, wherein the downlink transmission includes physical downlink shared channel (PDSCH) transmission having an offset associated with a physical downlink control channel (PDCCH), the offset being equal to or greater than a beam switching delay threshold.

[0251] Aspect 87: A wireless node according to any one of aspects 83-86, wherein, according to at least a first rule in the rules, it is determined that the receiver uses the one with the highest downlink priority level among at least two time-overlapping downlink transmission and monitoring opportunities for receiving downlink transmission and monitoring opportunities.

[0252] Aspect 88: A wireless node according to any one of Aspects 83-87, wherein, according to at least the second rule in the rules: if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0253] Aspect 89: The wireless node according to aspect 87, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0254] Aspect 90: A wireless node according to any one of aspects 83-88 further includes, according to at least one of the rules, considering those downlink transmission and monitoring opportunities that overlap in time and have different assumptions and different downlink priorities as errors.

[0255] Aspect 91: A wireless node according to any one of Aspects 83-89, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0256] Aspect 92: The wireless node according to aspect 91, wherein, according to at least one of the rules, it is determined that the receiver assumption is the one with the most or least repetition among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0257] Aspect 93: The wireless node according to aspect 91, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least overlap among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0258] Aspect 94: A wireless node according to any one of Aspects 83-93, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0259] Aspect 95: A wireless node according to any one of Aspects 83-94, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0260] Aspect 96: A wireless node according to any one of Aspects 83-95, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules to be the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities.

[0261] Aspect 97: A wireless node according to any one of Aspects 83-96, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0262] Aspect 98: A wireless node according to any one of Aspects 83-97, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of either the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0263] Aspect 99: A wireless node according to any one of aspects 83-98, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; and the processing system is further configured to: apply one or more rules to determine reception assumptions for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0264] Aspect 100: A radio node according to any one of Aspects 83-99, wherein, if different control resource set (CORESET) pool indices are configured, signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0265] Aspect 101: A wireless node according to any one of aspects 83-100, wherein the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication for the downlink transmission, monitoring timing, or downlink transmission and monitoring timing associated with uplink feedback.

[0266] Aspect 102: A wireless node according to any one of aspects 83-101, wherein the downlink priority level for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI) is signaled in the DCI.

[0267] Aspect 103: A wireless node according to any one of aspects 83-102, wherein, for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) control element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information elements (IE) or via the DCI or MAC CE used for activation.

[0268] Aspect 104: A network entity includes: a transmitter configured to: send signaling to a wireless node indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine a reception assumption to be used based on one or more rules when at least two downlink transmission or monitoring timings overlap in time; and process at least two downlink transmission and monitoring timings based on the reception assumption.

[0269] Aspect 105: The network entity according to aspect 104, wherein the reception assumption includes a quasi-co-location (QCL) assumption, the QCL assumption being used to determine a spatial domain filter for receiving at least two temporally overlapping downlink transmission and monitoring opportunities.

[0270] Aspect 106: A network entity according to any one of Aspects 104-105, wherein at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

[0271] Aspect 107: A network entity according to any one of Aspects 104-106, wherein the downlink transmission includes a Physical Downlink Shared Channel (PDSCH) transmission having an offset associated with a Physical Downlink Control Channel (PDCCH) that is equal to or greater than a beam switching delay threshold.

[0272] Aspect 108: A network entity according to any one of Aspects 104-107, wherein, according to at least a first rule in the rules, it is determined that the receiving assumption is the one with the highest downlink priority level among at least two downlink transmission and monitoring opportunities that overlap in time during the receiving of downlink transmission and monitoring opportunities.

[0273] Aspect 109: A network entity according to any one of Aspects 104-108, wherein, according to at least the second rule in the rules: if there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, the second rule is used to determine which of the different reception assumptions should be used.

[0274] Aspect 110: The network entity according to aspect 108, wherein: signaling indicates at least three different downlink priority levels; and according to a first rule, a reception assumption is determined for the downlink transmission or monitoring timing with the highest downlink priority level among at least two downlink transmission and monitoring timings that overlap in time during downlink transmission and monitoring.

[0275] Aspect 111: A network entity according to any one of Aspects 104-110, wherein the number of repetitions of at least two downlink transmission and monitoring opportunities that overlap in time are determined according to at least one of the rules.

[0276] Aspect 112: The network entity according to aspect 111, wherein, according to at least one of the rules, it is determined that the reception assumption is the one with the most or least repetition among at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

[0277] Aspect 113: The network entity according to aspect 111, wherein, according to at least one of the rules, if at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, it is determined that the reception assumption is to use the one with the most or least overlap among the at least two downlink transmission and monitoring opportunities that overlap in time.

[0278] Aspect 114: A network entity according to any one of Aspects 104-113, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the use of one of the multiple PDSCH transmissions with the highest downlink priority level, according to at least one of the rules.

[0279] Aspect 115: A network entity according to any one of Aspects 104-114, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include physical downlink shared channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a first PDSCH that was previously successfully decoded and transmissions of a second PDSCH that was previously unsuccessfully decoded; and according to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, it is determined that the reception assumption of the second PDSCH is used.

[0280] Aspect 116: A network entity according to any one of Aspects 104-115, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and a reception assumption is determined to be the PDCCH monitoring opportunity with the highest downlink priority among the multiple PDCCH monitoring opportunities, according to at least one of the rules.

[0281] Aspect 117: A network entity according to any one of Aspects 104-116, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one physical downlink control channel (PDCCH) monitoring opportunity and at least one physical downlink shared channel (PDSCH) monitoring opportunity with different reception assumptions and different downlink priority levels; and a reception assumption is determined according to at least one of the rules, which is either the PDCCH monitoring opportunity or the PDSCH transmission with the highest downlink priority level.

[0282] Aspect 118: A network entity according to any one of Aspects 104-117, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and according to at least one rule in the rules, it is determined whether to use the reception assumption of either the CSI-RS or the PDCCH monitoring opportunity or PDSCH transmission with the highest downlink priority level.

[0283] Aspect 119: A network entity according to any one of Aspects 104-118, wherein: at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a first control resource set (CORESET) pool index, and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with a second CORESET pool index; the network entity further includes: applying one or more rules to determine reception assumptions for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

[0284] Aspect 120: A network entity according to any one of Aspects 104-119, wherein, if different control resource set (CORESET) pool indices are configured, signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

[0285] Aspect 121: A network entity according to any one of Aspects 104-120, wherein the signaling of the downlink priority level is the same as the uplink priority level for the uplink feedback indication for the downlink transmission, monitoring timing, or downlink transmission and monitoring timing associated with uplink feedback.

[0286] Aspect 122: A network entity according to any one of Aspects 104-121, wherein its downlink priority level is signaled in the DCI for downlink transmission and monitoring timing or downlink transmission and monitoring timing scheduled by downlink control information (DCI).

[0287] Aspect 123: A network entity according to any one of Aspects 104-122, wherein, for a downlink transmission, monitoring timing, or downlink transmission and monitoring timing activated via Radio Resource Control (RRC) configuration, via Downlink Control Information (DCI) activation, or via Medium Access Control (MAC) Control Element (CE), its downlink priority level is signaled via at least one of the Radio Resource Control (RRC) Information Elements (IE) or via the DCI or MAC CE used for activation.

[0288] Aspect 124: An apparatus for wireless communication by a wireless node, comprising: an interface configured to: acquire signaling indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine a reception assumption to be used based on one or more rules when at least two downlink transmission and monitoring timings overlap in time, and process the at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0289] Aspect 125: An apparatus for wireless communication by a network entity, comprising: an interface configured to: output signaling for transmission to a wireless node, the signaling indicating a downlink priority level for downlink transmission and monitoring timing; and a processing system configured to: determine a reception assumption to be used based on one or more rules when at least two downlink transmission or monitoring timings overlap in time, and process at least two downlink transmission and monitoring timings based on the reception assumption.

[0290] Aspect 126: A computer-readable medium for wireless communication, comprising instructions executable to: obtain signaling indicating a downlink priority level for downlink transmission and monitoring timing; when at least two downlink transmission and monitoring timings overlap in time, determine a reception assumption to be used based on one or more rules; and process the at least two downlink transmission and monitoring timings that overlap in time based on the reception assumption.

[0291] Aspect 127: A computer-readable medium for wireless communication, comprising instructions executable to: output signaling to a wireless node for transmission, the signaling indicating a downlink priority level for downlink transmission and monitoring timing; when at least two downlink transmission or monitoring timings overlap in time, determining a reception assumption to be used based on one or more rules; and processing at least two downlink transmission and monitoring timings based on the reception assumption.

[0292] The methods disclosed herein include one or more steps or actions for implementing these methods. These method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0293] As used herein, the phrase “at least one of” in a list of items refers to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination of multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbbc, cc, and ccc, or any other ordering of a, b, and c).

[0294] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, derivation, research, searching (e.g., searching in a table, database, or other data structure), assertion, and so on. Furthermore, "determine" can also include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), and so on. Additionally, "determine" can also include parsing, selecting, choosing, building, and so on.

[0295] The preceding description is provided to enable those skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to a singular element is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated, the term “some” refers to one or more. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, such structural and functional equivalents being known or to be known to those skilled in the art. Furthermore, the disclosure herein is not intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. No claim element is to be interpreted pursuant to the provisions of 35 U.S.SC §112(f) unless the element is expressly recited using the phrase “unit for…” or, in the case of a method claim, using the phrase “step for…”.

[0296] The various operations of the methods described above can be performed by any suitable unit capable of performing the corresponding functions. These units may include various hardware and / or software components and / or modules, including but not limited to: circuits, application-specific integrated circuits (ASICs), or processors. For example, Figure 4The processors 458, 464, 466 and / or controller / processor 480 of the UE 120 shown and / or the processors 420, 430, 438 and / or controller / processor 440 of the BS 110 can be configured to perform Figure 10 Operation 1000 or Figure 11 Operation 1100.

[0297] The unit for receiving may include Figure 4 The receiver shown is (e.g., one or more antennas or a receiver processor). The unit for transmitting may include... Figure 4 The transmitter shown is (e.g., one or more antennas or a transmitter processor). The units for determining, processing, disposing, and applying may include a processing system, which may include one or more processors, for example, Figure 4 The processors 458, 464, 466 and / or controller / processor 480 of the UE 120 shown, and / or processors 420, 430, 438 and / or controller / processor 440 of the BS 110.

[0298] In some cases, a device may have an interface (output unit) for outputting frames for transmission, rather than actually sending frames. For example, a processor may output frames to a radio frequency (RF) front end for transmission via a bus interface. Similarly, instead of actually receiving frames, a device may have an interface (acquisition unit) for acquiring frames received from another device. For example, a processor may acquire (or receive) frames from an RF front end for receiving via a bus interface.

[0299] The various exemplary logic blocks, modules, and circuits described in connection with this disclosure can be implemented or executed using general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices (PLDs), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may 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 architecture.

[0300] When implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may utilize a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnected buses and bridges. The bus can link together various circuits, including a processor, machine-readable media, and a bus interface. The bus interface can be used to connect network adapters, etc., to the processing system via the bus. The network adapter can be used to implement signal processing functions at the PHY layer. In user terminal 120 (see...) Figure 1 In this case, a user interface (e.g., keyboard, monitor, mouse, joystick, etc.) can also be connected to the bus. The bus also links various other circuits, such as clock sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and therefore will not be described further. The processor can be implemented using one or more general-purpose processors and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how best to implement the functions of the described processing system, depending on the specific application and the overall design constraints imposed on the system as a whole.

[0301] When implemented in software, the functionality may be stored as one or more instructions or code on or transmitted through a computer-readable medium. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, data, or any combination thereof. Computer-readable media includes both computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general-purpose processing, including executing software stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be part of the processor. For example, the machine-readable medium may include transmission lines, carrier waveforms modulated by data, and / or a separate computer-readable storage medium containing instructions, all accessible to the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, for example, in the case of a cache and / or a general-purpose register file. By way of example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. Machine-readable media may be embodied in a computer program product.

[0302] Software modules can include a single instruction or many instructions, and can be distributed across several different code segments, different programs, and across multiple storage media. Computer-readable media can include multiple software modules. Software modules include instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. Software modules can include transfer modules and receive modules. Each software module can reside in a single storage device or be distributed across multiple storage devices. By way of example, when a triggering event occurs, a software module can be loaded from the hard disk into RAM. During the execution of the software module, the processor can load some of the instructions into the cache to increase access speed. Subsequently, one or more cache lines can be loaded into the general-purpose register file for execution by the processor. When referring to the functionality of a software module, it should be understood that such functionality is implemented by the processor when executing the instructions from that software module.

[0303] Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, then those coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and optical discs include compressed optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and... Optical discs, where magnetic disks typically copy data magnetically, use lasers to optically copy data. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0304] Therefore, certain aspects may include computer program products for performing the operations set forth herein. For example, such computer program products may include computer-readable media having instructions stored thereon (and / or encoded thereon) that can be executed by one or more processors to perform the operations described herein. Figure 9-10 The instructions for the operation shown are as follows.

[0305] Furthermore, it should be understood that modules and / or other suitable units for performing the methods and techniques described herein can be downloaded and / or otherwise obtained by the user terminal and / or base station on demand. For example, such a device can be coupled to a server to facilitate the delivery of units for performing the methods described herein. Alternatively, the various methods described herein can be provided via storage units (e.g., RAM, ROM, physical storage media such as CDs or floppy disks), so that the user terminal and / or base station can obtain the various methods after the storage units are coupled to or provided to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device can also be utilized.

[0306] It should be understood that the claims are not limited to the precise configurations and components shown above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the methods and apparatus described above without departing from the scope of the claims.

Claims

1. A method for wireless communication performed by a wireless node, comprising: Receive signaling indicating the downlink priority level for downlink transmission and monitoring timing; When at least two downlink transmission and monitoring opportunities overlap in time, a reception assumption to be used is determined based on one or more rules, wherein the one or more rules are at least partially based on the downlink priority level indicated by the received signaling, or at least one of the number of repetitions of the at least two overlapping downlink transmission and monitoring opportunities in time; as well as Based on the reception assumption, the at least two downlink transmission and monitoring opportunities that overlap in time are processed during the downlink transmission and monitoring opportunities.

2. The method according to claim 1, wherein, The reception assumption includes a quasi-co-location (QCL) assumption, which is used to determine a spatial domain filter for receiving the at least two temporally overlapping downlink transmission and monitoring opportunities.

3. The method according to claim 1, wherein, The at least two downlink transmission and monitoring opportunities that overlap in time are associated with the same cell or different cells.

4. The method according to claim 1, wherein, The downlink transmission includes physical downlink shared channel (PDSCH) transmission with an offset associated with physical downlink control channel (PDCCH) that is equal to or greater than a beam switching delay threshold.

5. The method according to claim 1, wherein, According to at least the first rule in the rules, the determination is based on the reception assumption that one of the at least two downlink transmission and monitoring opportunities that overlap in time during the downlink transmission and monitoring is the one with the highest downlink priority level.

6. The method according to claim 1, wherein, According to at least the second rule in the aforementioned rules: If there are multiple overlapping downlink transmission and monitoring opportunities with the same highest downlink priority level, and if the multiple overlapping downlink transmission and monitoring opportunities have different reception assumptions, then a second rule is used to determine which of the different reception assumptions should be used.

7. The method according to claim 5, wherein: The signaling indicates at least three different downlink priority levels; and According to the first rule, the determination is based on the reception assumption of the downlink transmission or monitoring timing with the highest downlink priority level among the at least two downlink transmission and monitoring timings that overlap in time.

8. The method of claim 1, further comprising: according to at least one of the rules: Those downlink transmission and monitoring opportunities that overlap in time and have different assumptions and different downlink priorities are considered errors.

9. The method according to claim 1, wherein, According to at least one of the rules, the determination depends at least in part on the number of repetitions of one of the at least two downlink transmission and monitoring opportunities that overlap in time during the downlink transmission and monitoring.

10. The method according to claim 9, wherein, According to at least one of the rules, the determination is based on the reception assumption of the one with the most or least repetition among the at least two downlink transmission and monitoring times that overlap in time, regardless of the downlink priority level of the at least two downlink transmission and monitoring times that overlap in time.

11. The method according to claim 9, wherein, According to at least one of the rules, if the at least two downlink transmission and monitoring opportunities that overlap in time have the same downlink priority level, the determination is based on the reception assumption of the one with the most or least repetition among the at least two downlink transmission and monitoring opportunities that overlap in time.

12. The method according to claim 1, wherein: The at least two overlapping downlink transmission and monitoring opportunities in the downlink transmission and monitoring opportunities include: multiple Physical Downlink Shared Channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels; and According to at least one of the rules, the determination is a reception assumption using the PDSCH transmission with the highest downlink priority level among the plurality of PDSCH transmissions.

13. The method according to claim 1, wherein: The at least two overlapping downlink transmission and monitoring opportunities in the downlink transmission and monitoring opportunities include Physical Downlink Shared Channel (PDSCH) transmissions with different reception assumptions and different downlink priority levels, including retransmissions of a previously successfully decoded first PDSCH and transmissions of a previously unsuccessfully decoded second PDSCH; and According to at least one of the rules, even if the downlink priority level of the first PDSCH is higher than the downlink priority level of the second PDSCH, the determination is also based on the reception assumption of the second PDSCH.

14. The method according to claim 1, wherein: The at least two overlapping downlink transmission and monitoring opportunities in the downlink transmission and monitoring opportunities include: multiple physical downlink control channel (PDCCH) monitoring opportunities with different reception assumptions and different downlink priority levels; and According to at least one of the rules, the determination is a reception assumption using the PDCCH monitoring timing with the highest downlink priority level among the plurality of PDCCH monitoring timings.

15. The method according to claim 1, wherein: The at least two overlapping downlink transmission and monitoring opportunities in the downlink transmission and monitoring opportunities include: at least one physical downlink control channel (PDCCH) monitoring opportunity with different reception assumptions and different downlink priority levels, and at least one physical downlink shared channel (PDSCH); and According to at least one of the rules, the determination is a reception assumption using either the PDCCH monitoring timing or the PDSCH transmission with the highest downlink priority level.

16. The method according to claim 1, wherein: The at least two downlink transmission and monitoring opportunities that overlap in time include: at least one non-repeating Channel State Information Reference Signal (CSI-RS) overlapping with at least one Physical Downlink Control Channel (PDCCH) monitoring opportunity or Physical Downlink Shared Channel (PDSCH) transmission, wherein the CSI-RS and the PDCCH monitoring opportunity or PDSCH transmission have different reception assumptions and different downlink priority levels; and According to at least one of the rules, the determination is a reception assumption that uses the CSI-RS, or the PDCCH monitoring timing, or the PDSCH transmission with the highest downlink priority level.

17. The method according to claim 1, wherein: The at least two downlink transmission and monitoring opportunities that overlap in time include: two or more downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with the first control resource set (CORESET) pool index; and two or more other downlink transmission and monitoring opportunities that overlap in time and are scheduled by or associated with the second CORESET pool index. The method further includes: applying the one or more rules to determine a reception assumption for processing at least two downlink transmission and monitoring opportunities that are scheduled by or associated with the same CORESET pool index.

18. The method according to claim 1, wherein, If different control resource set (CORESET) pool indices are configured, the signaling indicates the downlink priority level for physical downlink control channel (PDCCH) transmission for each CORESET pool index.

19. The method according to claim 1, wherein, For downlink transmissions, monitoring events, or downlink transmissions and monitoring events associated with uplink feedback, the signaling for the downlink priority level is the same as the uplink priority level for the uplink feedback indication.

20. The method according to claim 1, wherein, For downlink transmission and monitoring opportunities, or downlink transmission and monitoring opportunities scheduled by downlink control information (DCI), the downlink priority level is signaled in the DCI.

21. The method according to claim 1, wherein, For downlink transmissions, monitoring events, or downlink transmissions and monitoring events that are configured via Radio Resource Control (RRC), activated via Downlink Control Information (DCI), or activated via Medium Access Control (MAC) Control Element (CE), their downlink priority level is signaled via at least one RRC IE in the Radio Resource Control (RRC) Information Element (IE) or via the DCI or MAC CE used for activation.

22. A wireless node, comprising: The receiver is configured to receive signaling indicating a downlink priority level for downlink transmission and monitoring timing. as well as The processing system is configured as follows: When at least two downlink transmission and monitoring opportunities overlap in time, a reception assumption to be used is determined based on one or more rules, wherein the one or more rules are at least partially based on the downlink priority level indicated by the received signaling, or at least one of the number of repetitions of the at least two overlapping downlink transmission and monitoring opportunities in time; as well as Based on the reception assumption, the at least two downlink transmission and monitoring opportunities that overlap in time are processed during the downlink transmission and monitoring opportunities.

23. The wireless node according to claim 22, wherein, The wireless node includes user equipment.

24. An apparatus for wireless communication performed by a wireless node, comprising: The interface is configured to: obtain signaling indicating the downlink priority level for downlink transmission and monitoring timing; as well as The processing system is configured as follows: When at least two downlink transmission and monitoring opportunities overlap in time, a reception assumption to be used is determined based on one or more rules, wherein the one or more rules are at least partially based on the downlink priority level indicated by the received signaling, or at least one of the number of repetitions of the at least two overlapping downlink transmission and monitoring opportunities in time; as well as Based on the reception assumption, the at least two downlink transmission and monitoring opportunities that overlap in time are processed during the downlink transmission and monitoring opportunities.

25. A wireless node, comprising One or more processors; and One or more memories coupled to one or more processors and storing processor-executable code thereon, which, when executed by one or more processors, causes the one or more processors to perform the method of any one of claims 1-21.

Images