CN118160261A

CN118160261A - Processing of physical downlink shared channels overlapping semi-static symbols

Info

Publication number: CN118160261A
Application number: CN202280071369.4A
Authority: CN
Inventors: A·A·I·A·泽韦尔; M·霍什内维桑; J·孙; 张晓霞; 田庆江
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-11-03
Filing date: 2022-09-23
Publication date: 2024-06-07

Abstract

Aspects of the present disclosure relate generally to wireless communications. In some aspects, a network node may receive downlink control information that schedules multiple physical downlink shared channels and repetition within an associated slot for a symbol set of the slot. The network node may communicate over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the associated time slot are repeated without collision with one or more semi-static uplink symbols of the set of symbols. Numerous other aspects are described.

Description

Processing of physical downlink shared channels overlapping semi-static symbols

Cross Reference to Related Applications

This patent application claims priority from U.S. provisional patent application No. 63/263,486 entitled "processing of physical DOWNLINK shared channel overlapping semi-STATIC SYMBOLs" (HANDLING OF A PHYSICAL DOWNLINK SHARED CHANNEL OVERLAPPING WITH A SEMI-STATIC SYMBOL) filed on day 11 and U.S. non-provisional patent application No. 17/823,834 entitled "processing of physical DOWNLINK shared channel overlapping semi-STATIC SYMBOLs" (HANDLING OF APHYSICAL DOWNLINK SHARED CHANNEL OVERLAPPING WITH A SEMI-STATIC SYMBOL) filed on day 8 and day 31 of 2022, which are assigned to the assignee of the present application. The disclosures of these prior applications are considered to be part of the present patent application and are incorporated by reference into the present patent application.

Technical Field

Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatuses for processing of physical downlink shared channels overlapping semi-static symbols.

Background

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple-access techniques capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple-access techniques include Code Division Multiple Access (CDMA) systems, time Division Multiple Access (TDMA) systems, frequency Division Multiple Access (FDMA) systems, orthogonal Frequency Division Multiple Access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/advanced LTE is an enhanced set of Universal Mobile Telecommunications System (UMTS) mobile standards promulgated by the third generation partnership project (3 GPP).

A wireless network may include one or more base stations that support communication for a User Equipment (UE) or multiple UEs. The UE may communicate with the base station via downlink and uplink communications. "downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

The multiple access techniques described above have been employed in various telecommunications standards to provide a common protocol that enables different UEs to communicate at a city, country, region, and/or global level. The New Radio (NR), which may be referred to as 5G, is an enhanced set of LTE mobile standards promulgated by 3 GPP. NR is designed to better integrate with other open standards by improving spectral efficiency, reducing costs, improving services, utilizing new spectrum, and using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) on the downlink (CP-OFDM), using CP-OFDM and/or single carrier frequency division multiplexing (SC-FDM) on the uplink (also known as discrete fourier transform spread OFDM (DFT-s-OFDM)), and supporting beamforming, multiple Input Multiple Output (MIMO) antenna technology, and carrier aggregation, thereby better supporting mobile broadband internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.

Disclosure of Invention

Some aspects described herein relate to a wireless communication method performed by a network node. The method may include receiving downlink control information that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot. The method may include communicating over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the associated time slot repeat without collision with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to a method of wireless communication performed by a base station. The method may include transmitting downlink control information to a network node that schedules a plurality of physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot. The method may include communicating with the network node and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive downlink control information that schedules a plurality of physical downlink shared channels and repetition within an associated slot for a set of symbols of the slot. The one or more processors may be configured to communicate over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to a base station for wireless communications. The base station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit downlink control information to the network node that schedules multiple physical downlink shared channels and repetition within an associated slot for a symbol set of the slot. The one or more processors may be configured to communicate with the network node and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to a non-transitory computer readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive downlink control information that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot. The set of instructions, when executed by the one or more processors of the network node, may cause the network node to communicate over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to a non-transitory computer readable medium storing a set of instructions for wireless communication by a base station. The set of instructions, when executed by the one or more processors of the base station, may cause the base station to transmit downlink control information to a network node that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot. The set of instructions, when executed by the one or more processors of the base station, may cause the network node to communicate with the base station and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving downlink control information that schedules multiple physical downlink shared channels for a symbol set of a time slot and repetition within an associated time slot. The apparatus may include means for communicating over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting downlink control information to a network node that schedules a plurality of physical downlink shared channels and repetition within an associated time slot for a symbol set of the time slot. The apparatus may include means for communicating with the network node and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Aspects generally include a method, apparatus, system, computer program product, non-transitory computer readable medium, user equipment, base station, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and description.

The foregoing has outlined rather broadly the features and technical advantages of examples in accordance with the present disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The features of the concepts disclosed herein, both as to their organization and method of operation, together with the associated advantages will be better understood when the following description is considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description, and is not intended as a definition of the limits of the claims.

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

Drawings

So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to aspects, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects. The same reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

Fig. 2 is a diagram illustrating an example of a base station communicating with a User Equipment (UE) in a wireless network according to the present disclosure.

Fig. 3 is a diagram illustrating an example of a logical architecture of a distributed radio access network according to the present disclosure.

Fig. 4 is a diagram illustrating an example of multiple Transmission Reception Point (TRP) communications according to the present disclosure.

Fig. 5 is a diagram illustrating an example of a multi-TRP multi-Physical Downlink Shared Channel (PDSCH) transmission with intra-slot repetition in accordance with the present disclosure.

Fig. 6 is a diagram illustrating an example of processing associated with PDSCH overlapping semi-static uplink symbols according to the present disclosure.

Fig. 7 to 8 are diagrams illustrating example procedures of processing associated with PDSCH overlapping with semi-static uplink symbols according to the present disclosure.

Fig. 9-10 are diagrams of example apparatuses for wireless communication according to the present disclosure.

Fig. 11 is a diagram of an open radio access network (O-RAN) architecture according to the present disclosure.

Detailed Description

Various aspects of the disclosure are described more fully hereinafter with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art will appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method practiced using any number of the aspects set forth herein. Furthermore, the scope of the present disclosure is intended to cover such an apparatus or method that is implemented with other structures, functionality, or both in addition to or other than the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more components of the present invention.

Several aspects of the telecommunications system will now be presented with reference to various apparatus and techniques. These devices and techniques will be described in the following detailed description and illustrated in the figures by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

Although aspects may be described herein using terms generally associated with 5G or New Radio (NR) Radio Access Technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and/or 5G later RATs (e.g., 6G).

Fig. 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., long Term Evolution (LTE)) network, and so on. Wireless network 100 may include one or more base stations 110 (shown as BS110 a, BS110b, BS110c, and BS110 d), user Equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120 e), and/or other network entities. Base station 110 is the entity in communication with UE 120. Base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, nodes B, eNB (e.g., in 4G), gnbs (e.g., in 5G), access points, and/or transmission-reception points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the third generation partnership project (3 GPP), the term "cell" can refer to a coverage area of a base station 110 and/or a base station subsystem serving the coverage area, depending on the context in which the term is used.

The base station 110 may provide communication coverage for a macrocell, a picocell, a femtocell, and/or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscription. The pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having an association with the femto cell (e.g., UEs 120 in a Closed Subscriber Group (CSG)). The base station 110 for a macro cell may be referred to as a macro base station. The base station 110 for a pico cell may be referred to as a pico base station. The base station 110 for a femto cell may be referred to as a femto base station or a home base station. In the example shown in fig. 1, BS110a may be a macro base station for macro cell 102a, BS110b may be a pico base station for pico cell 102b, and BS110c may be a femto base station for femto cell 102 c. A base station may support one or more (e.g., three) cells.

In some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of the moving base station 110 (e.g., a mobile base station). In some examples, base stations 110 may be interconnected in wireless network 100 to each other and/or to one or more other base stations 110 or network nodes (not shown) through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive a transmission of data from an upstream station (e.g., base station 110 or UE 120) and send a transmission of data to a downstream station (e.g., UE 120 or base station 110). The relay station may be a UE 120 capable of relaying transmissions for other UEs 120. In the example shown in fig. 1, BS110d (e.g., a relay base station) may communicate with BS110a (e.g., a macro base station) and UE 120d to facilitate communications between BS110a and UE 120 d. The base station 110 relaying communications may be referred to as a relay station, a relay base station, a relay, and so on.

The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, and so on. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impact on interference in the wireless network 100. For example, macro base stations may have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

The network controller 130 may be coupled to, or in communication with, a set of base stations 110 and may provide coordination and control for these base stations. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link.

UEs 120 may be distributed throughout wireless network 100 and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a mobile station, and/or a subscriber unit. UE 120 may be a cellular telephone (e.g., a smart phone), a Personal Digital Assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a Wireless Local Loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, a super book, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smartwristband, smart jewelry (e.g., a smartring or smart bracelet)), an entertainment device (e.g., a music device, a video device, and/or a satellite radio), a vehicle component or sensor, a smart meter/sensor, industrial manufacturing equipment, a global positioning system device, and/or any other suitable device configured to communicate via a wireless medium.

Some UEs 120 may be considered Machine Type Communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and/or eMTC UEs may include, for example, robots, drones, remote devices, sensors, gauges, monitors, and/or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered internet of things (IoT) devices and/or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered customer premise equipment. UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.

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

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

Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., according to frequency or wavelength. For example, devices of wireless network 100 may communicate using one or more operating frequency bands. In 5G NR, two initial operating bands have been identified as frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be appreciated that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. With respect to FR2, a similar naming problem sometimes occurs, which is commonly (interchangeably) referred to in documents and articles as the "millimeter wave" band, although it differs from the Extremely High Frequency (EHF) band (30 GHz-300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band.

The frequency between FR1 and FR2 is commonly referred to as the mid-band frequency. Recent 5G NR studies have identified the operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). The frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend the characteristics of FR1 and/or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz) and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF frequency band.

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

Deployment of a communication system, such as a 5G NR system, may be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of a network, radio Access Network (RAN) nodes, core network nodes, network elements, base stations, or network equipment may be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR Base Station (BS), 5G NB, next generation node B (gNB), access Point (AP), TRP, or cell) or one or more units (or one or more components) performing base station functionality may be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a decomposed base station. A "network entity" or "network node" may refer to an exploded base station, a UE in communication therewith, or one or more units of an exploded base station, such as one or more central units or Control Units (CUs), one or more Distributed Units (DUs), one or more remote units or Radio Units (RUs), or a combination thereof.

The aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). The decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed among one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as virtual units (e.g., virtual Central Units (VCUs), virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs)).

Base station type operation or network design may take into account the aggregate nature of the base station functionality. For example, the split base station may be used in an Integrated Access Backhaul (IAB) network, an open radio access network (O-RAN, such as network configuration advocated by the O-RAN alliance), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating base station functionality into one or more units that may be deployed separately. The decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Each unit of the base station may be configured for wired or wireless communication with at least one other unit of the base station.

In some aspects, UE 120 (e.g., a network node) may include a communication manager 140. As described in more detail elsewhere herein, communication manager 140 can receive downlink control information that schedules multiple physical downlink shared channels for a symbol set of a time slot and repetition within an associated time slot; and communicating over a set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols. Additionally or alternatively, communication manager 140 may perform one or more other operations described herein.

In some aspects, the base station 110 (e.g., another network node or network entity) may include a communication manager 150. As described in more detail elsewhere herein, communication manager 150 may transmit downlink control information to a network node (e.g., UE 120) that schedules multiple physical downlink shared channels for symbol sets of a time slot and repetition within an associated time slot; and communicating with the network node and over a symbol set of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the symbol set. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

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

Fig. 2 is a diagram illustrating an example 200 of a base station 110 in a wireless network 100 in communication with a UE 120 in accordance with the present disclosure. Base station 110 may be equipped with a set of antennas 234a through 234T, such as T antennas (T.gtoreq.1). UE 120 may be equipped with a set of antennas 252a through 252R, such as R antennas (r≡1).

At base station 110, transmit processor 220 may receive data intended for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more Modulation and Coding Schemes (MCSs) for UE 120 based at least in part on one or more Channel Quality Indicators (CQIs) received from UE 120. Base station 110 may process (e.g., encode and modulate) data for UE 120 based at least in part on the MCS selected for UE 120 and provide data symbols for UE 120. Transmit processor 220 may process system information (e.g., for semi-Static Resource Partitioning Information (SRPI)) and control information (e.g., CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary Synchronization Signals (PSS) or Secondary Synchronization Signals (SSS)). A Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, control symbols, overhead symbols, and/or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modulators) (shown as modems 232a through 232T). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and/or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. Modems 232 a-232T may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234 a-234T).

At UE 120, a set of antennas 252 (shown as antennas 252a through 252R) may receive downlink signals from base station 110 and/or other base stations 110 and a set of received signals (e.g., R received signals) may be provided to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254R). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal using a corresponding demodulator component to obtain input samples. Each modem 254 may use a demodulator assembly to further process the input samples (e.g., for OFDM) to obtain received symbols. MIMO detector 256 may obtain the received symbols from modem 254, may perform MIMO detection on the received symbols, if applicable, and may provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280. The term "controller/processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, and/or a CQI parameter, among others. In some examples, one or more components of UE 120 may be included in housing 284.

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

The one or more antennas (e.g., antennas 234a through 234t and/or antennas 252a through 252 r) may include or be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and/or one or more antenna arrays, etc. The antenna panel, antenna group, set of antenna elements, and/or antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and/or one or more antenna elements coupled to one or more transmission and/or reception components (such as one or more components in fig. 2).

On the uplink, at UE 120, transmit processor 264 may receive and process data from data source 262 as well as control information from controller/processor 280 (e.g., for reports including RSRP, RSSI, RSRQ and/or CQI). Transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from transmit processor 264 may be pre-decoded, if applicable, by a TX MIMO processor 266, further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some examples, modem 254 of UE 120 may include a modulator and a demodulator. In some examples, UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modems 254, MIMO detector 256, receive processor 258, transmit processor 264, and/or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller/processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., with reference to fig. 6-10).

At base station 110, uplink signals from UE 120 and/or other UEs may be received by antennas 234, processed by modems 232 (e.g., demodulator components, shown as DEMODs, of modems 232), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller/processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. Base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and/or uplink communications. In some examples, modem 232 of base station 110 may include a modulator and a demodulator. In some examples, base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modems 232, MIMO detector 236, receive processor 238, transmit processor 220, and/or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller/processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., with reference to fig. 6-10).

The controller/processor 240 of the base station 110, the controller/processor 280 of the UE 120, and/or any other component of fig. 2 may perform one or more techniques associated with processing of a Physical Downlink Shared Channel (PDSCH) that overlaps with semi-static uplink symbols, as described in more detail elsewhere herein. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of fig. 2 may perform or direct operations such as process 700 of fig. 7, process 800 of fig. 8, and/or other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and/or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and/or UE 120 (e.g., directly, or after compilation, conversion, and/or interpretation), may cause the one or more processors, UE 120, and/or base station 110 to perform or direct operations such as process 700 of fig. 7, process 800 of fig. 8, and/or other processes described herein. In some examples, the execution instructions may include execution instructions, conversion instructions, compilation instructions, and/or interpretation instructions, among others.

In some aspects, a network node (e.g., UE 120) includes: means for receiving downlink control information that schedules a plurality of physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot; and/or means for communicating over a symbol set of a time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the symbol set. In some aspects, means for a network node to perform the operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, base station 110 (e.g., another network node) includes means for transmitting downlink control information to a network node (e.g., UE 120) that schedules multiple physical downlink shared channels for a symbol set of a time slot and repetition within an associated time slot; and/or means for communicating with the network node and over a set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols. Means for base station 110 to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

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

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

Fig. 3 illustrates an example logical architecture of a distributed RAN 300 according to this disclosure.

The 5G access node 305 may include an access node controller 310. The access node controller 310 may be a CU of the distributed RAN 300. The backhaul interface to the 5G core network 315 may terminate at the access node controller 310. The 5G core network 315 may include a 5G control plane component 320 and a 5G user plane component 325 (e.g., a 5G gateway), and a backhaul interface for one or both of the 5G control plane and the 5G user plane may terminate at the access node controller 310. Additionally or alternatively, a backhaul interface to one or more neighbor access nodes 330 (e.g., another 5G access node 305 and/or an LTE access node) may terminate at the access node controller 310.

Access node controller 310 may include and/or may communicate with one or more TRPs 335 (e.g., via an F1 control (F1-C) interface and/or an F1 user (F1-U) interface). TRP 335 may be a DU of distributed RAN 300. TRP 335 may correspond to base station 110 described above in connection with fig. 1. For example, different TRPs 335 may be included in different base stations 110. Additionally or alternatively, multiple TRPs 335 may be included in a single base station 110. Base station 110 may include a CU (e.g., access node controller 310) and/or one or more DUs (e.g., one or more TRPs 335). In some cases, TRP 335 may be referred to as a cell, panel, antenna array, or array. A deployment with multiple TRPs 335 may be referred to as a "multi TRP" or "mTRP" deployment.

TRP 335 may be connected to a single access node controller 310 or multiple access node controllers 310. Dynamic configuration of split logic functions may exist within the architecture of the distributed RAN 300. For example, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and/or a Medium Access Control (MAC) layer may be configured to terminate at the access node controller 310 or TRP 335.

Multiple TRPs 335 may transmit communications (e.g., same communications or different communications) in the same Transmission Time Interval (TTI) (e.g., time slot, micro-slot, subframe, or symbol) or different TTIs using different quasi-co-located (QCL) relationships (e.g., different spatial parameters, different Transmission Configuration Indicator (TCI) states, different precoding parameters, and/or different beamforming parameters). The TCI state may be used to indicate one or more QCL relationships. TRP 335 may be configured to provide services to UE 120 alone (e.g., using dynamic selection) or jointly (e.g., using joint transmission with one or more other TRPs 335).

As indicated above, fig. 3 is provided as an example. Other examples may differ from the example described with respect to fig. 3.

Fig. 4 is a diagram illustrating an example 400 of multi-TRP communication (sometimes referred to as multi-panel communication) in accordance with the present disclosure. As shown in fig. 4, multiple TRPs 405 may be in communication with the same UE 120. TRP 405 may correspond to TRP 335 described above in connection with fig. 3.

Multiple TRPs 405 (shown as TRP a and TRP B) may communicate with the same UE 120 in a coordinated manner (e.g., using coordinated multipoint transmission) to improve reliability and/or increase throughput. TRP 405 may coordinate such communications via interfaces between TRP 405 (e.g., backhaul interfaces and/or access node controllers 310). The interface may have less delay and/or higher capacity when TRP 405 is co-located at the same base station 110 (e.g., when TRP 405 is a different antenna array or panel of the same base station 110), and may have greater delay and/or lower capacity (compared to co-location) when TRP 405 is located at a different base station 110. Different TRP 405 may communicate with UE 120 using different QCL relationships (e.g., different TCI states), different DMRS ports, and/or different layers (e.g., different layers in a multi-layer communication).

In a first multi-TRP transmission mode (e.g., mode 1), downlink data communications for a single PDSCH may be scheduled using a single Physical Downlink Control Channel (PDCCH). In this case, multiple TRPs 405 (e.g., TRP a and TRP B) may transmit communications to UE 120 on the same PDSCH. For example, the communication may be transmitted using a single codeword with different spatial layers for different TRPs 405 (e.g., where one codeword maps to a first set of layers transmitted by a first TRP 405 and to a second set of layers transmitted by a second TRP 405). As another example, a communication may be transmitted using multiple codewords, where different codewords are transmitted by different TRPs 405 (e.g., using different sets of layers). In either case, different TRP 405 may use different QCL relationships (e.g., different TCI states) for different DMRS ports corresponding to different layers. For example, the first TRP 405 may use a first QCL relationship or a first TCI state for a first set of DMRS ports corresponding to a first layer set, and the second TRP 405 may use a second (different) QCL relationship or a second (different) TCI state for a second (different) set of DMRS ports corresponding to a second (different) layer set. The TCI state (e.g., transmitted on the PDCCH, such as DCI format 1_0 or DCI format 1_1) in the Downlink Control Information (DCI) may indicate a first QCL relationship (e.g., by indicating a first TCI state) and a second QCL relationship (e.g., by indicating a second TCI state). The first and second TCI states may be indicated using a TCI field in the DCI. In general, in this multi-TRP transmission mode (e.g., mode 1), the TCI field may indicate a single TCI state (for single TRP transmission) or multiple TCI states (for multi-TRP transmission as discussed herein).

In a second multi-TRP transmission mode (e.g., mode 2), multiple PDCCHs may be used to schedule downlink data communications for multiple corresponding PDSCH (e.g., one PDCCH for each PDSCH). In this case, the first PDCCH may schedule a first codeword to be transmitted by the first TRP 405, and the second PDCCH may schedule a second codeword to be transmitted by the second TRP 405. Further, a first DCI (e.g., transmitted by a first TRP 405) may schedule a first PDSCH communication associated with a first set of DMRS ports having a first QCL relationship (e.g., indicated by a first TCI state) for the first TRP 405, and a second DCI (e.g., transmitted by a second TRP 405) may schedule a second PDSCH communication associated with a second set of DMRS ports having a second QCL relationship (e.g., indicated by a second TCI state) for the second TRP 405. In this case, the DCI (e.g., with DCI format 1_0 or DCI format 1_1) may indicate a corresponding TCI state for TRP 405 corresponding to the DCI. The TCI field of the DCI indicates a corresponding TCI state (e.g., the TCI field of the first DCI indicates a first TCI state and the TCI field of the second DCI indicates a second TCI state).

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

As described above, the DCI may include information associated with scheduling communications in a multi-TRP deployment, such as PDSCH communications or Physical Uplink Shared Channel (PUSCH) communications, among other examples. For example, in a multi-TRP deployment, a single DCI may schedule multiple PDSCH transmissions to a single UE. Although the DCI may not schedule each PDSCH communication that will collide with an uplink symbol, the DCI may schedule one or more PDSCH communications that collide with an uplink symbol. When PDSCH is scheduled for transmission during symbols defined for a UE as uplink symbols for the UE to transmit, collisions between the scheduled PDSCH and uplink symbols may occur. When PDSCH scheduled by DCI collides with uplink symbols, the UE may not receive PDSCH. The uplink symbols may be specified by a configuration message, such as a tdd-UL-DL-ConfigurationCommon configuration message or a tdd-UL-DL-ConfigurationDedicated configuration message.

In another example, a UE may receive DCI scheduling multiple PUSCH communications for the UE. Although the DCI may not schedule each PUSCH communication to collide with a downlink symbol, the DCI may schedule one or more PUSCH communications to collide with a downlink symbol. When PUSCH is scheduled for transmission during symbols defined for a UE as downlink symbols for the UE to receive from TRPs, collisions between the scheduled PUSCH and the downlink symbols may occur. When the PUSCH scheduled by the DCI collides with a downlink symbol, the UE may not transmit the PUSCH. The downlink symbols may be specified by a configuration message, such as a tdd-UL-DL-ConfigurationCommon configuration message or a tdd-UL-DL-ConfigurationDedicated configuration message.

For example, PDSCH or PUSCH, the UE may have an associated hybrid automatic repeat request (HARQ) process number that may be used by the UE and base station for reliability and retransmission signaling. When the UE discards PDSCH (e.g., the UE does not receive PDSCH) or PUSCH (e.g., the UE does not transmit PUSCH) due to collision with uplink symbols or downlink symbols, respectively, the UE may skip incrementing the HARQ process number. In other words, the UE may apply only the HARQ process number to the valid PDSCH or PUSCH that is not skipped due to collision.

Fig. 5 is a diagram illustrating an example 500 of multi-TRP multi-PDSCH transmission with intra-slot repetition in accordance with the present disclosure.

As shown in fig. 5, a group of transmissions may occur across symbol sets of a slot. For example, when intra-slot Time Division Multiplexing (TDM) is enabled, TRP may transmit multiple repetitions of PDSCH within a single slot. In this case, a first instance of transmission of the PDSCH is referred to as "first repetition", and a second instance of transmission of the PDSCH is referred to as "second repetition".

The first network node (e.g., TRP) may transmit two repetitions of PDSCH to the second network node (e.g., UE) based at least in part on control information (e.g., DCI) including a TCI field indicating two TCI states. For example, a network node (e.g., a first network node or a second network node) may receive TCI fields indicating a first TCI state "1" and a second TCI state "2". In this case, the network node may interpret the Time Domain Resource Allocation (TDRA) field of the control information as a Start and Length Indicator Value (SLIV) identifying a first repetition of PDSCH using the first TCI state. For example, as shown, the network node may identify a starting symbol (S) of a first repetition of the PDSCH as symbol 3 (e.g., where the sequential first symbol is indexed as symbol 0) and a length (L) of the first repetition of the PDSCH as 4 symbols. In this case, the network node may identify the second repetition as having the same length as the first repetition (e.g., 4 symbols, as shown). The gap between the first repetition and the second repetition may be configured via signaling separate from control information that schedules PDSCH repetition. For example, as shown, the network node may receive Radio Resource Control (RRC) signaling indicating a gap (G) of 2 symbols between the end of the first repetition and the beginning of the second repetition.

The TDRA field of SLIV used by the network node to identify repetitions of PDSCH may be interpreted using a TDRA table. For single PDSCH grants, a scheduling entity (e.g., a CU of a base station) may configure TDRA tables for one or more network nodes to ensure that there is no overlap between the repetition of the scheduled PDSCH and uplink symbols (e.g., which may be semi-statically configured and referred to as "semi-static uplink symbols"). The collision between dynamic PDSCH and semi-static uplink symbols may be considered an error condition to be avoided by the scheduling entity. However, when the scheduling entity is to provide multiple PDSCH grants, TDRA rows of the TDRA table may schedule up to 8 PDSCH with TDM repetitions. Thus, the scheduling entity may have up to 16 SLIV that do not overlap with the semi-static uplink symbol. Implementing such requirements may unduly limit network scheduling flexibility, thereby resulting in reduced throughput and poor network performance.

As indicated above, fig. 5 is provided as an example. Other examples may differ from what is described with respect to fig. 5.

Fig. 6 is a diagram illustrating an example 600 of processing associated with PDSCH overlapping semi-static uplink symbols according to the present disclosure. As shown in fig. 6, example 600 includes communications between network nodes 602-a and 602-B (e.g., which may be TRP or DUs of a base station and associated with an Access Node Controller (ANC) or CU of the base station) and network node 610 (e.g., which may be UE 120). In some aspects, the network node 602 may correspond to one or more base stations 110. In some aspects, network nodes 602-A and 602-B and network node 610 are included in a wireless network, such as wireless network 100.

As shown in fig. 6 and further by reference numeral 620, the network node 610 may receive control information for scheduling PDSCH. For example, the network node 610 may receive DCI scheduling multiple PDSCH and an associated intra-slot repetition of the multiple PDSCH. In other words, the network node 610 may receive DCI scheduling first and second repetitions of a first PDSCH and first and second repetitions of a second PDSCH. Additionally or alternatively, the network node 610 may receive DCI scheduling an additional number of repetitions or an additional number of PDSCH, as well as other examples. In some aspects, the network node 610 may receive DCI including a TDRA field, the TDRA field indicating a PDSCH mapping type for PDSCH of PDSCH grants (e.g., multiple PDSCH grants) in the DCI. For example, the network node 610 may receive information identifying a mapping type for each PDSCH corresponding to a PDSCH grant. In this case, PDSCH of PDSCH grant may have different mapping types, the same mapping type, or a combination of different mapping types and the same mapping type.

In some aspects, network node 610 may receive control information associated with semi-statically configuring communications with network nodes 602-A and 602-B. For example, the network node 610 may receive RRC signaling (e.g., which is signaled via DCI) that configures gaps between repetitions of PDSCH. Additionally or alternatively, the network node 610 may receive repeated first control information configuring PDSCH and repeated second control information activating PDSCH. Additionally or alternatively, the network node 610 may receive control information that configures directionality of symbols within a slot. For example, network node 610 may receive semi-static signaling (e.g., via RRC) indicating whether the symbol is an uplink symbol, a downlink symbol, or a flexible symbol (e.g., a symbol that may be flexibly used for downlink or uplink).

In some aspects, the network node 610 may determine a PDSCH mapping type for PDSCH grants (e.g., multiple PDSCH grants) in the DCI. For example, the network node 610 may determine a PDSCH mapping type for the first repetition of the PDSCH and the second repetition of the PDSCH based at least in part on the TDRA table. In some aspects, the network node 610 may apply PDSCH mapping type B to each repetition of PDSCH based at least in part on PDSCH mapping type B defined for each SLIV of the indicated TDRA rows of the TDRA table. Additionally or alternatively, the network node 610 may apply PDSCH mapping type B to each repetition of PDSCH even when SLIV of indicated TDRA rows of the TDRA table are associated with a different PDSCH mapping type. In this way, for a scenario in which PDSCH mapping type B is to be used, instead of having to use network resources to receive multiple TDRA tables for multiple PDSCH mapping types and using storage resources to store the multiple TDRA tables, the network node 610 may reuse the TDRA tables defined for PDSCH mapping type a. Additionally or alternatively, the network node 610 may apply different PDSCH mapping types to different repetitions of PDSCH. For example, the network node 610 may apply the indicated mapping type (e.g., PDSCH mapping type a) of SLIV of TDRA rows of the TDRA table to the first PDSCH repetition and the statically defined PDSCH mapping type (e.g., PDSCH mapping type B). In this way, the network node 610 may reuse TDRA the table in part by statically applying PDSCH mapping type B to some PDSCH repetitions, even when TDRA rows of the TDRA table are associated with different PDSCH mapping types.

As in fig. 6 and further illustrated by reference numerals 630 and 640, the network node 610 may receive the transmitted PDSCH according to control information. For example, the network node 610 may receive a repeated subset of one or more PDSCH (e.g., a repeated subset of the first PDSCH and/or a repeated subset of the second PDSCH) based at least in part on whether the repeated subset collides with semi-static uplink symbols.

In some aspects, the network node 610 may determine whether any PDSCH repetition collides with semi-static uplink symbols. For example, the network node 610 may determine that a single repetition (or multiple repetitions) of the multiple repetitions of the PDSCH collides with a semi-static uplink symbol. In this case, the single repetition (or multiple repetitions) may be a first repetition of the PDSCH and/or a subsequent repetition of the PDSCH. Additionally or alternatively, the network node 610 may determine that multiple repetitions of the PDSCH collide with semi-static uplink symbols.

In some aspects, network node 610 and network nodes 602-a and 602-B may consider repetitions of PDSCH that collide with semi-static uplink symbols as error conditions (e.g., such scenarios may be considered invalid and may not be schedulable and/or may result in changes to scheduling to avoid such scenarios). For example, a collision between any repetition of PDSCH in a multiple PDSCH grant with an intra-slot repetition scenario and any semi-static uplink symbol may be defined as an error condition. In this case, the network node 602-a or 602-B may discard transmissions of the collided PDSCH repetition (e.g., may discard any transmissions or may transmit or receive another communication other than the collided PDSCH repetition), and the network node 610 may discard transmissions of the collided PDSCH repetition (e.g., may discard any receptions or may transmit or receive another communication other than the collided PDSCH repetition). Additionally or alternatively, the network node 602-a or 602-B and the network node 610 may determine that DCI scheduling PDSCH is invalid. For example, when the network node 610 is configured to treat repetitions of PDSCH that collide with semi-static uplink symbols as an error condition, the network node 610 may discard all grants of DCI and/or its PDSCH resources.

In some aspects, the network node 610 may determine that the PDSCH is invalid when any repetition of the PDSCH collides with semi-static uplink symbols. For example, the network node 610 may determine to discard all repetitions of receiving PDSCH including at least one repetition that collides with semi-static uplink symbols, but the network node 610 may determine the repetition of other PDSCH of the multiple PDSCH grant receiving DCI. In this way, network node 610 and network nodes 602-a and 602-B increase network flexibility by allowing the DCI to include grants of conflicting PDSCH repetitions (e.g., of a first PDSCH) and remain valid relative to at least one other PDSCH repetition (e.g., of a second PDSCH). In some aspects, the network node 610 may discard HARQ feedback for any invalid PDSCH. For example, for HARQ Acknowledgement (ACK) (HARQ-ACK) codebook type 1, the network node 610 may forgo transmitting Negative Acknowledgements (NACKs) for any PDSCH determined to be invalid (e.g., based at least in part on having repetitions in conflict with semi-static uplink symbols).

In some aspects, the network node 610 may determine whether the PDSCH is invalid based at least in part on which repetition of the PDSCH collides with semi-static uplink symbols. For example, when the first repetition of the PDSCH collides with a semi-static uplink symbol, the network node 610 may determine that the PDSCH is invalid and may forego receiving any repetition of the PDSCH and/or transmitting HARQ feedback for the PDSCH. Additionally or alternatively, when the second or other subsequent repetition of the PDSCH collides with the semi-static uplink symbol, the network node 610 may determine only that the second or other subsequent repetition of the PDSCH is invalid. In other words, the network node 610 may receive the first repetition of the PDSCH and transmit HARQ feedback for the first repetition of the PDSCH, but may relinquish reception of the second repetition of the PDSCH. In this way, network node 610 and network nodes 602-a and 602-B further increase flexibility by enabling multiple PDSCH scheduling with respect to PDSCH with some repetitions that collide with semi-static uplink symbols to still have efficient PDSCH repetition.

As indicated above, fig. 6 is provided as an example. Other examples may differ from what is described with respect to fig. 6.

Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a network node, in accordance with the present disclosure. Example procedure 700 is an example of operations in which a network node (e.g., network node 610 or UE 120) performs processing associated with a physical downlink shared channel that overlaps with semi-static symbols.

As shown in fig. 7, in some aspects, process 700 may include receiving downlink control information that schedules multiple physical downlink shared channels for a symbol set of a slot and repetition within an associated slot (block 710). For example, a network node (e.g., using communication manager 140 and/or receiving component 902, depicted in fig. 9) may receive downlink control information that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot, as described above.

As further shown in fig. 7, in some aspects, process 700 may include communicating over a symbol set of a time slot, wherein a plurality of physical downlink shared channels and one or more semi-static uplink symbols of the symbol set are repeated within the associated time slot without collision (block 720). For example, a network node (e.g., using communication manager 140 and/or receiving component 902 or transmitting component 904, depicted in fig. 9) can communicate over a set of symbols of a time slot, wherein multiple physical downlink shared channels and associated intra-slot repetitions do not collide with one or more semi-static uplink symbols of the set of symbols, as described above.

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

In a first aspect, at least one of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to communicate over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and associated intra-slot repetitions.

In a second aspect, at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remainder of the intra-slot repetition of the plurality of physical downlink shared channels and associated slots.

In a third aspect, process 700 includes transmitting feedback information for the remaining portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information does not include negative acknowledgements for the physical downlink shared channels or associated intra-slot repetitions.

In a fourth aspect, at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the plurality of physical downlink shared channels and associated intra-slot repetition, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remainder of the plurality of physical downlink shared channels and associated intra-slot repetition.

In a fifth aspect, at least one of the one or more semi-static uplink symbols is scheduled to collide with a second instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and wherein the network node is to use the downlink control information to communicate over the set of symbols, including the first instance of the physical downlink shared channel and excluding the second instance of the downlink shared channel, such that the network node does not receive the second instance of the physical downlink shared channel.

In a sixth aspect, process 700 includes transmitting feedback information for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

In a seventh aspect, the downlink control information includes a time domain resource assignment field associated with physical downlink shared channel map type B for each start and length indicator value corresponding to each physical downlink shared channel.

In an eighth aspect, the downlink control information includes a time domain resource assignment field not associated with physical downlink shared channel map type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use physical downlink shared channel map type B for the at least one physical downlink shared channel or associated repetition.

In a ninth aspect, the downlink control information includes a time domain resource assignment field not associated with physical downlink shared channel map type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use the value of the time domain resource assignment field for the at least one physical downlink shared channel and is to use physical downlink shared channel map type B for the associated repetition.

While fig. 7 shows exemplary blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than the blocks depicted in fig. 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

Fig. 8 is a diagram illustrating an example process 800 performed, for example, by a base station, in accordance with the present disclosure. Example process 800 is an example of an operation in which a network node (e.g., base station 110, network node 602-a, or network node 602-B, etc.) performs processing associated with PDSCH overlapping semi-static symbols.

As shown in fig. 8, in some aspects, process 800 may include transmitting downlink control information to a network node that schedules multiple physical downlink shared channels and repetition within an associated slot for a symbol set of the slot (block 810). For example, a base station (e.g., using communication manager 150 and/or transmission component 1004, depicted in fig. 10) can transmit downlink control information to a network node that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot, as described above.

As further shown in fig. 8, in some aspects, process 800 may include communicating with a network node and over a symbol set of a time slot, wherein a plurality of physical downlink shared channels and one or more semi-static uplink symbols of the symbol set are repeated within the associated time slot without collision (block 820). For example, a base station (e.g., using communication manager 150 and/or receiving component 1002 or transmitting component 1004, depicted in fig. 10) can communicate with a network node and over a set of symbols of a time slot, wherein multiple physical downlink shared channels and associated intra-slot repetitions do not collide with one or more semi-static uplink symbols of the set of symbols, as described above.

Process 800 may include additional aspects, such as any single aspect and/or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a third aspect, process 800 includes receiving feedback information for the remaining portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information does not include a negative acknowledgement for the physical downlink shared channel or the associated intra-slot repetition.

In a sixth aspect, process 800 includes receiving feedback information for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

While fig. 8 shows example blocks of the process 800, in some aspects, the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than the blocks depicted in fig. 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

Fig. 9 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a network node or the network node may comprise the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 900 may use a receive component 902 and a transmit component 904 to communicate with another apparatus 906, such as a UE, a base station, a network node, or another wireless communication device. As further shown, the apparatus 900 may include a communication manager 140. The communication manager 140 may include a PDSCH processing component 908 as well as other examples.

In some aspects, apparatus 900 may be configured to perform one or more operations described herein in connection with fig. 6. Additionally or alternatively, apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of fig. 7, or a combination thereof. In some aspects, the apparatus 900 and/or one or more components illustrated in fig. 9 may include one or more components of the network node described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 9 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 902 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 906. The receiving component 902 can provide the received communication to one or more other components of the apparatus 900. In some aspects, the receiving component 902 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 900. In some aspects, the receiving component 902 may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers/processors, memory, or a combination thereof of a network node described in connection with fig. 2.

The transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 906. In some aspects, one or more other components of apparatus 900 may generate a communication and may provide the generated communication to transmit component 904 for transmission to apparatus 906. In some aspects, the transmitting component 904 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 906. In some aspects, the transmit component 904 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or combinations thereof of the network node described in connection with fig. 2. In some aspects, the transmitting component 904 may be co-located with the receiving component 902 in a transceiver.

The receiving component 902 can receive downlink control information that schedules a plurality of physical downlink shared channels for a symbol set of a time slot and repetition within an associated time slot. The receiving component 902 or the transmitting component 904 can communicate over a set of symbols of a time slot, wherein a plurality of physical downlink shared channels and associated repetitions within the time slot do not collide with one or more semi-static uplink symbols of the set of symbols. For example, the receiving component 902 may receive a valid PDSCH repetition and the transmitting component 904 may transmit on a semi-static uplink symbol based at least in part on the receiving component 902 discarding receipt of an invalid PDSCH repetition.

The transmitting component 904 can transmit feedback information for a plurality of physical downlink shared channels and a remaining portion of the repetition within an associated time slot, wherein the feedback information does not include a negative acknowledgement for the repetition within the physical downlink shared channel or the associated time slot.

The transmitting component 904 can transmit feedback information for a portion of the plurality of physical downlink shared channels and associated time slots that is repeated, wherein the feedback information includes feedback information for a first instance of the physical downlink shared channel and does not include a negative acknowledgement for a second instance of the physical downlink shared channel. The PDSCH processing component 908 may process multiple PDSCH grants to determine whether the PDSCH or repeated instances thereof are valid or invalid.

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

Fig. 10 is a diagram of an exemplary apparatus 1000 for wireless communications. The apparatus 1000 may be a base station or the base station may include the apparatus 1000. In some aspects, apparatus 1000 may be a network node, such as a base station or a component of a base station (e.g., a component of a base station that is split), among other examples. In some aspects, the apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that can communicate with each other (e.g., via one or more buses and/or one or more other components). As shown, apparatus 1000 may use a receiving component 1002 and a transmitting component 1004 to communicate with another apparatus 1006, such as a UE, a base station, a network node, or another wireless communication device. As further shown, the apparatus 1000 may include a communication manager 150. The communication manager 150 may include a PDSCH scheduling component 1008 as well as other examples.

In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with fig. 6. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 of fig. 8, or a combination thereof. In some aspects, the apparatus 1000 and/or one or more components shown in fig. 10 may comprise one or more components of a base station described in connection with fig. 2. Additionally or alternatively, one or more of the components shown in fig. 10 may be implemented within one or more of the components described in connection with fig. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform functions or operations of the component.

The receiving component 1002 can receive a communication, such as a reference signal, control information, data communication, or a combination thereof, from the device 1006. The receiving component 1002 can provide the received communication to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 can perform signal processing (such as filtering, amplifying, demodulating, analog-to-digital converting, demultiplexing, deinterleaving, demapping, equalizing, interference cancellation or decoding, etc.) on the received communication and can provide the processed signal to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 can comprise one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers/processors, memory, or a combination thereof of a base station described in connection with fig. 2.

The transmission component 1004 can transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1006. In some aspects, one or more other components of apparatus 1000 may generate a communication, and the generated communication may be provided to transmission component 1004 for transmission to apparatus 1006. In some aspects, the transmission component 1004 can perform signal processing (such as filtering, amplifying, modulating, digital-to-analog converting, multiplexing, interleaving, mapping or encoding, etc.) on the generated communication and can transmit the processed signal to the device 1006. In some aspects, the transmit component 1004 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or a combination thereof of the base station described in connection with fig. 2. In some aspects, the transmitting component 1004 can be co-located with the receiving component 1002 in a transceiver.

The transmitting component 1004 can transmit downlink control information to a network node that schedules multiple physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot. The receiving component 1002 or the transmitting component 1004 can communicate with a network node and over a set of symbols of a time slot, wherein a plurality of physical downlink shared channels and repetition within an associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols. For example, the receiving component 1002 can receive on a resource for which the scheduled PDSCH is determined to be invalid, or the transmitting component 1004 can transmit an invalid PDSCH or cancel transmission of an invalid PDSCH to transmit another communication on a resource for which the scheduled PDSCH is determined to be invalid.

The receiving component 1002 can receive feedback information for a plurality of physical downlink shared channels and a remaining portion of the repetition within an associated time slot, wherein the feedback information does not include a negative acknowledgement for the repetition within the physical downlink shared channel or the associated time slot. The receiving component 1002 can receive feedback information for a plurality of physical downlink shared channels and a portion of a repetition within an associated time slot, wherein the feedback information includes feedback information for a first instance of the physical downlink shared channel and does not include a negative acknowledgement for a second instance of the physical downlink shared channel. PDSCH scheduling component 1008 may schedule multiple PDSCH grants and/or determine whether one or more of its PDSCH repetitions are valid or invalid.

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

Fig. 11 is a diagram illustrating an example 1100 of an O-RAN architecture according to the present disclosure. As shown in fig. 11, the O-RAN architecture may include a CU 1110 that communicates with a core network 1120 via a backhaul link. Further, CU 1110 can communicate with one or more DUs 1130 via corresponding mid-range links. The DUs 1130 may each communicate with one or more RUs 1140 via respective forward links, and the RUs 1140 may each communicate with respective UEs 120 via Radio Frequency (RF) access links. DU 1130 and RU 1140 may also be referred to as O-RAN DU (O-DU) 1130 and O-RAN RU (O-RU) 1140, respectively. One or more of the components of the O-RAN architecture may correspond to, include, or be included in the following: UE 120, base station 110, network node 610, network node 602-a, network node 602-B, apparatus 900 or apparatus 1000, among other examples.

In some aspects, DUs 1130 and RUs 1140 may be implemented according to a functional split architecture, where the functionality of base station 110 (e.g., eNB or gNB) is provided by DUs 1130 and one or more RUs 1140 communicating over an outbound link. Thus, as described herein, base station 110 may include a DU 1130 and one or more RUs 1140, which may be co-located or geographically distributed. In some aspects, the DUs 1130 and associated RUs 1140 may communicate via an outbound link to exchange real-time control plane information via a Lower Layer Split (LLS) control plane (LLS-C) interface, to exchange non-real-time management information via a LLS management plane (LLS-M) interface, and/or to exchange user plane information via a LLS user plane (LLS-U) interface.

Thus, DU 1130 may correspond to a logic unit that includes one or more base station functions to control the operation of one or more RUs 1140. For example, in some aspects, the DU 1130 may host the RLC layer, MAC layer, and one or more higher Physical (PHY) layers (e.g., forward Error Correction (FEC) encoding and decoding, scrambling, and/or modulation and demodulation) based at least in part on lower layer functional partitions. Higher layer control functions, such as PDCP, RRC, and/or Service Data Adaptation Protocol (SDAP), may be hosted by CU 1110. RU 1140, controlled by DU 1130, may correspond to a logical node hosting RF processing functions and low PHY layer functions (e.g., fast Fourier Transform (FFT), inverse FFT (iFFT), digital beamforming, and/or Physical Random Access Channel (PRACH) extraction and filtering) based at least in part on lower layer functional splitting. Thus, in the O-RAN architecture, RU 1140 handles all over-the-air (OTA) communications with UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with RU 1140 are controlled by corresponding DUs 1130, which enables DUs 1130 and CUs 1110 to be implemented in the cloud-based RAN architecture.

As indicated above, fig. 11 is provided as an example. Other examples may differ from what is described with respect to fig. 11.

The following provides an overview of some aspects of the disclosure:

Aspect 1: a method of wireless communication performed by a network node, comprising: receiving downlink control information that schedules a plurality of physical downlink shared channels and repetition within an associated slot for a symbol set of the slot; and communicating over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Aspect 2: the method of aspect 1, wherein at least one semi-static uplink symbol of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to communicate over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and associated intra-slot repetitions.

Aspect 3: the method of any of aspects 1-2, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remaining portion of the intra-slot repetitions of the plurality of physical downlink shared channels and associated slots.

Aspect 4: the method according to aspect 3, further comprising: transmitting feedback information for the remaining portion repeated within the plurality of physical downlink shared channels and associated time slots, wherein the feedback information does not include negative acknowledgements repeated within the physical downlink shared channels or associated time slots.

Aspect 5: the method of any of aspects 1-4, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remainder of the plurality of physical downlink shared channels and associated intra-slot repetitions.

Aspect 6: the method of any of aspects 1-5, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a second instance of a physical downlink shared channel in the plurality of physical downlink shared channels and associated intra-slot repetition, and wherein the network node is to use the downlink control information to communicate on the symbol set, including a first instance of the physical downlink shared channel and excluding the second instance of the downlink shared channel, such that the network node does not receive the second instance of the physical downlink shared channel.

Aspect 7: the method of aspect 6, further comprising: feedback information for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions is transmitted, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

Aspect 8: the method of any of aspects 1-7, wherein the downlink control information includes a time domain resource assignment field associated with physical downlink shared channel mapping type B for each start and length indicator value corresponding to each physical downlink shared channel.

Aspect 9: the method of any of aspects 1-8, wherein the downlink control information includes a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use physical downlink shared channel mapping type B for the at least one physical downlink shared channel or associated repetition.

Aspect 10: the method according to any of aspects 1-9, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use the value of the time domain resource assignment field for the at least one physical downlink shared channel and is to use physical downlink shared channel mapping type B for the associated repetition.

Aspect 11: a wireless communication method performed by a base station, comprising: transmitting downlink control information to the network node that schedules a plurality of physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot; and communicating with the network node and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

Aspect 12: the method of aspect 11, wherein at least one semi-static uplink symbol of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to communicate over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and associated intra-slot repetitions.

Aspect 13: the method of any of aspects 11-12, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remaining portion of the intra-slot repetitions of the plurality of physical downlink shared channels and associated slots.

Aspect 14: the method of aspect 13, further comprising: feedback information is received for the remaining portion repeated within the plurality of physical downlink shared channels and associated time slots, wherein the feedback information does not include negative acknowledgements repeated within the physical downlink shared channels or associated time slots.

Aspect 15: the method of any of aspects 11-14, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to use the downlink control information to communicate on the symbol set in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with a remainder of the plurality of physical downlink shared channels and associated intra-slot repetitions.

Aspect 16: the method of any of claims 11-15, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a second instance of a physical downlink shared channel in the plurality of physical downlink shared channels and associated intra-slot repetition, and wherein the network node is to use the downlink control information to communicate on the symbol set, including a first instance of the physical downlink shared channel and excluding the second instance of the downlink shared channel, such that the network node does not receive the second instance of the physical downlink shared channel.

Aspect 17: the method of aspect 16, further comprising: feedback information is received for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

Aspect 18: the method of any of aspects 11-17, wherein the downlink control information includes a time domain resource assignment field associated with physical downlink shared channel mapping type B for each start and length indicator value corresponding to each physical downlink shared channel.

Aspect 19: the method according to any of aspects 11-18, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use physical downlink shared channel mapping type B for the at least one physical downlink shared channel or associated repetition.

Aspect 20: the method according to any of the aspects 11-19, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and wherein the network node is to use the value of the time domain resource assignment field for the at least one physical downlink shared channel and is to use physical downlink shared channel mapping type B for the associated repetition.

Aspect 21: an apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 1 to 10.

Aspect 22: an apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-10.

Aspect 23: an apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-10.

Aspect 24: a non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-10.

Aspect 25: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 1-10.

Aspect 26: an apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to one or more of aspects 11-20.

Aspect 27: an apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 11-20.

Aspect 28: an apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 11-20.

Aspect 29: a non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 11-20.

Aspect 30: a non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of aspects 11-20.

The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term "component" is intended to be broadly interpreted as hardware, and/or a combination of hardware and software. "software" shall be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures and/or functions, and the like, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware and/or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware and/or combinations of hardware and software. The actual specialized control hardware or software code used to implement the systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods were described without reference to the specific software code because it will be understood by those skilled in the art that software and hardware can be designed to implement the systems and/or methods based at least in part on the description herein.

As used herein, a "meeting a threshold" may refer to a value greater than a threshold, greater than or equal to a threshold, less than or equal to a threshold, not equal to a threshold, etc., depending on the context.

Although specific combinations of features are set forth in the claims and/or disclosed in the specification, such combinations are not intended to limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. The disclosure of the various aspects includes each dependent claim combined with each other claim of the set of claims. As used herein, a phrase referring to "at least one item in a list of items" refers to any combination of these items (which includes a single member). As an example, "at least one of a, b, or c" is intended to encompass a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the article "a" is intended to include one or more items and may be used interchangeably with "one or more". Furthermore, as used herein, the article "the" is intended to include one or more items recited in connection with the article "the" and may be used interchangeably with "one or more. Furthermore, as used herein, the terms "set" and "group" are intended to include one or more items, and may be used interchangeably with "one or more". If only one item is intended, the phrase "only one" or similar terms will be used. Also, as used herein, the terms "having" and the like are intended to be open-ended terms that do not limit the element they modify (e.g., an element having "a may also have B). Furthermore, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and/or" unless otherwise specifically indicated (e.g., if used in conjunction with "either" or "only one").

Claims

1. A network node for wireless communication, comprising:

A memory; and

One or more processors coupled to the memory and configured to:

Receiving downlink control information that schedules a plurality of physical downlink shared channels and repetition within an associated slot for a symbol set of the slot; and

Communication is performed over the set of symbols of the time slot, wherein the multiple physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

2. The network node of claim 1, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetitions, and wherein the network node is to communicate over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and associated intra-slot repetitions.

3. The network node of claim 1, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and

Wherein in addition to the grant of the physical downlink shared channel, the network node is to use the downlink control information to communicate over the set of symbols such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and the remainder of the repetition within the associated time slot.

4. The network node of claim 3, wherein the one or more processors are further configured to:

Transmitting feedback information for the remaining portion repeated within the plurality of physical downlink shared channels and associated time slots, wherein the feedback information does not include negative acknowledgements repeated within the physical downlink shared channels or associated time slots.

5. The network node of claim 1, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and

6. The network node of claim 1, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a second instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and

Wherein the network node is to communicate on the set of symbols using the downlink control information, including a first instance of the physical downlink shared channel and excluding the second instance of the downlink shared channel, such that the network node does not receive the second instance of the physical downlink shared channel.

7. The network node of claim 6, wherein the one or more processors are further configured to:

Feedback information for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions is transmitted, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

8. The network node of claim 1, wherein the downlink control information comprises a time domain resource assignment field associated with physical downlink shared channel mapping type B for each start and length indicator value corresponding to each physical downlink shared channel.

9. The network node of claim 1, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and

Wherein the network node maps type B for the at least one physical downlink shared channel or associated re-used physical downlink shared channel.

10. The network node of claim 1, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and

Wherein the network node is to use a value of the time domain resource assignment field for the at least one physical downlink shared channel and is to map type B for the associated re-used physical downlink shared channel.

11. A base station for wireless communication, comprising:

A memory; and

One or more processors coupled to the memory and configured to:

Transmitting downlink control information to the network node that schedules a plurality of physical downlink shared channels and repetition within an associated time slot for a set of symbols of the time slot; and

Communicating with the network node and over the set of symbols of the slot,

Wherein the multiple physical downlink shared channels and the associated intra-slot repetition do not collide with one or more semi-static uplink symbols of the symbol set.

12. The base station of claim 11, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetition, and

Wherein the network node is to communicate over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not repeatedly collide with the plurality of physical downlink shared channels and associated time slots.

13. The base station of claim 11, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and

14. The base station of claim 13, wherein the one or more processors are further configured to:

Feedback information is received for the remaining portion repeated within the plurality of physical downlink shared channels and associated time slots, wherein the feedback information does not include negative acknowledgements repeated within the physical downlink shared channels or associated time slots.

15. The base station of claim 11, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and

16. The base station of claim 11, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a second instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and

17. The base station of claim 16, wherein the one or more processors are further configured to:

Feedback information is received for a portion of the plurality of physical downlink shared channels and associated intra-slot repetitions, wherein the feedback information includes feedback information for the first instance of the physical downlink shared channel and does not include a negative acknowledgement for the second instance of the physical downlink shared channel.

18. The base station of claim 11, wherein the downlink control information comprises a time domain resource assignment field associated with physical downlink shared channel mapping type B for each start and length indicator value corresponding to each physical downlink shared channel.

19. The base station of claim 11, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and

20. The base station of claim 11, wherein the downlink control information comprises a time domain resource assignment field not associated with physical downlink shared channel mapping type B for at least one start and length indicator value associated with at least one physical downlink shared channel or associated repetition, and

21. A method of wireless communication performed by a network node, comprising:

22. The method of claim 21, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetition, and

Including communicating over the set of symbols without using the downlink control information such that the one or more semi-static uplink symbols do not repeatedly collide with the plurality of physical downlink shared channels and associated time slots.

23. The method of claim 21, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and

Including communicating over the set of symbols using the downlink control information in addition to grant of the physical downlink shared channel such that the one or more semi-static uplink symbols do not collide with the plurality of physical downlink shared channels and a remaining portion of the repetition within the associated time slot.

24. The method of claim 23, further comprising:

25. The method of claim 21, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and

26. A method of wireless communication performed by a base station, comprising:

Communicating with the network node and over the set of symbols of the time slot, wherein the plurality of physical downlink shared channels and the repetition within the associated time slot do not collide with one or more semi-static uplink symbols of the set of symbols.

27. The method of claim 26, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with any of the plurality of physical downlink shared channels and associated intra-slot repetition, and

28. The method of claim 26, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a physical downlink shared channel or an associated intra-slot repetition of the plurality of physical downlink shared channels and associated intra-slot repetitions, and

29. The method of claim 28, further comprising:

30. The method of claim 26, wherein at least one of the one or more semi-static uplink symbols is scheduled to collide with a first instance of a physical downlink shared channel in the multiple physical downlink shared channels and associated intra-slot repetition, and