Wireless communication method at user equipment and base station and apparatus for wireless communication

Abstract

Various aspects of the present disclosure relate to downlink (DL) resource allocation features in wireless communication systems that are configured to address issues that may arise in sub-band full-duplex (SBFD) carriers (sometimes also referred to as flexible duplex carriers). For example, on a SBFD carrier, a timeslot may have a format in which an uplink (UL) portion of a carrier is located between two DL portions of the carrier. In situations where a scheduler operating in a new radio (NR) network utilizes a particular type of DL resource allocation, a situation may arise where a portion of the DL allocation falls into the UL portion of a carrier. Therefore, a scheduled entity may add the UL portion of a carrier to a set of resources indicated as unavailable for DL ​​transmission. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority to non-provisional patent application No. 17 / 313,923 filed in the United States Patent and Trademark Office on May 6, 2021, and a PCT application claiming priority and the benefit of provisional patent application No. 63 / 022,408 filed in the United States Patent and Trademark Office (USPTO) on May 8, 2020, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to resource allocation (e.g., frequency allocation in a time slot such as a sub-band full duplex (SBFD) time slot). Some aspects may include enabling and providing a communication device and method configured to mitigate and / or resolve potential conflicts between a time slot having a particular time slot format and a downlink (DL) resource allocation for the time slot, thereby facilitating resolution and mitigation of potential interference situations, thereby improving device performance and system throughput. Background Art

[0004] In wireless communications, a full-duplex link is one in which two endpoints can communicate with each other simultaneously on the same set of resources. Many wireless communications systems provide a full-duplex emulation, where two-way simultaneous communications occur between the respective endpoints, but different sets of resources are used for transmissions in different directions. For example, time division duplex (TDD) uses time division multiplexing to separate transmissions in different directions on a given channel from each other. That is, sometimes the channel is dedicated to transmissions in one direction, and at other times the channel is dedicated to transmissions in the other direction. As another example, frequency division duplex (FDD) allows transmissions in different directions to operate at different carrier frequencies.

[0005] In wireless communication systems utilizing orthogonal frequency division multiplexing (OFDM), a duplexing scheme commonly referred to as sub-band full duplex (SBFD) may be used. SBFD differs from conventional FDD in that, in FDD, a given carrier is typically fully dedicated to either uplink or downlink communications. With SBFD, a portion of the time-frequency resources on a given carrier is dedicated to the uplink, while a portion of the time-frequency resources on the same carrier supports the downlink. Thus, endpoints communicating using SBFD transmit and receive simultaneously, but on different frequency resources of the same carrier. That is, the downlink resources are separated from the uplink resources in the frequency domain.

[0006] As the demand for mobile broadband access continues to increase, people continue to advance wireless communication technology through research and development, which not only meets the growing demand for mobile broadband access, but also improves and enhances users' mobile communication experience. Summary of the invention

[0007] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not a comprehensive summary of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a prelude to a more detailed description presented later.

[0008] In various aspects, the present disclosure provides a downlink (DL) resource allocation feature in a wireless communication system that is configured to address issues that may arise in a sub-band full-duplex (SBFD) carrier (sometimes also referred to as a flexible duplex carrier). For example, on a SBFD carrier, a timeslot may have a format in which an uplink (UL) portion of the timeslot is located between multiple DL portions of the timeslot (in frequency). When a scheduler operating in a 3GPP New Radio (NR) network utilizes a particular type (e.g., type 1) of DL resource allocation, a situation may arise where a portion of the DL resource allocation overlaps with (e.g., falls within) the UL portion of the timeslot.

[0009] In some examples, user equipment (e.g., mobile devices) can communicate with a scheduling entity such as a base station (BS). The devices can communicate over a wireless carrier (e.g., an SBFD carrier) by sending one or more time slots having a specific time slot format to each other on the wireless carrier. For example, the time slot format can correspond to a configuration of resources (e.g., resource element (RE) sets) in one or more time slots. Resources can be designated for communication in one direction to send data over the wireless carrier (e.g., in the uplink portion of the time slot), or for communication in the other direction to receive data over the wireless carrier (e.g., in the downlink portion of the time slot).

[0010] In some examples, a scheduling entity may send a DL resource allocation to a user equipment (e.g., a mobile device). The DL resource allocation may include a scheduling or grant message that identifies a set of resources to facilitate communication between the user equipment and the scheduling entity over a wireless carrier. In some cases, the resources in the DL resource allocation may include a set of resources corresponding to a portion of a time slot that has been allocated for DL ​​communication (e.g., determined based on a time slot format of the time slot). However, in some cases, the set of resources in the DL resource allocation may also include at least some resources allocated for UL communication. In this case, one or more resources identified in the DL resource allocation including resources allocated for UL communication form an overlapping portion within a resource slot. If not mitigated, information corresponding to resources in the overlapping portion may conflict (e.g., interfere) with information sent in the opposite direction using the same resources in the overlapping portion according to one or more of the various techniques of the present invention.

[0011] According to one or more of the various techniques of the present invention, a user equipment (UE) may add a UL portion of a carrier to a resource set that is indicated as unavailable for DL ​​transmission (i.e., unavailable). In this case, the UE may receive a DL resource allocation (e.g., a grant message) that overlaps (completely or partially) with the UL portion (in frequency). In this case, the UE may determine to ignore information related to a specific portion of the DL resource allocation that overlaps with the UL portion because the UL portion of the carrier is indicated as unavailable for DL ​​transmission.

[0012] Some aspects of the present disclosure provide a method of wireless communication operable at a scheduled entity (e.g., a UE). In a more specific example, the method includes receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication. The method also includes receiving a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion, wherein at least a portion of the DL resource allocation overlaps with at least a portion of the first frequency portion of the time slot. In some examples, the method may also include determining that the overlapping portion includes resources that are unavailable for DL ​​transmission. The method also includes communicating through a wireless carrier using the time slot format while ignoring (e.g., ignoring, abandoning processing, etc.) information related to the overlapping portion.

[0013] Other aspects of the present disclosure provide an apparatus for wireless communication. In a more specific example, the apparatus includes a component for receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication. The apparatus also includes a component for receiving a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion, wherein at least a portion of the DL resource allocation overlaps with at least a portion of the first frequency portion of the time slot. In some examples, the apparatus may also include a component for determining that the overlapping portion includes resources that are unavailable for DL ​​transmission. The apparatus also includes a component for communicating over a wireless carrier using the time slot format while ignoring information related to the overlapping portion.

[0014] Other aspects of the present disclosure provide a non-transitory computer-readable medium storing computer executable code. In a more specific example, the code includes instructions for causing a user equipment (UE) to receive information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication. The code also includes instructions for causing the UE to receive a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion, wherein at least a portion of the downlink resource allocation overlaps with at least a portion of the first frequency portion of the time slot. In some examples, the code may also include instructions for causing the UE to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission. The code also includes instructions for causing the UE to communicate over a wireless carrier using the time slot format while ignoring information received in the overlapping portion.

[0015] Other aspects of the present disclosure provide a device for wireless communication. In a more specific example, the device includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured to receive information indicating a time slot format, which identifies a first frequency portion of the time slot for uplink (UL) communication and at least one other frequency portion of the time slot for downlink (DL) communication. The processor and the memory are also configured to receive a DL resource allocation for the time slot via the transceiver, the DL resource allocation including an overlapping portion, wherein at least a portion of the DL resource allocation overlaps with at least a portion of the first frequency portion of the time slot. In some examples, the processor and the memory may also be configured to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission. The processor and the memory are also configured to communicate through a wireless carrier using the time slot format while ignoring information related to the overlapping portion via the transceiver.

[0016] Some aspects of the present disclosure provide a method of wireless communication operable at a scheduling entity (e.g., a base station (BS)). In a more specific example, the method includes determining at least one first frequency portion of a time slot as being usable for uplink (UL) communication, and determining at least one second frequency portion of the time slot as being usable for downlink (DL) communication, wherein at least one first frequency portion of the time slot is not usable for DL ​​communication. The method also includes sending information indicating at least one first frequency portion of the time slot and at least one second frequency portion of the time slot via a transceiver. The method also includes sending a DL resource allocation to a user equipment (UE), the DL resource allocation including an overlapping portion, wherein the DL resource allocation at least partially overlaps with at least one first frequency portion of the time slot. The method also includes communicating with the UE via a wireless carrier using the time slot.

[0017] Other aspects of the present disclosure provide a device for wireless communication. In a more specific example, the device includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. The processor and the memory are configured to determine at least one first frequency portion of a time slot as being usable for uplink (UL) communication, and at least one second frequency portion of a time slot is determined to be usable for downlink (DL) communication, wherein at least one first frequency portion of a time slot is not usable for DL ​​communication. The processor and the memory are also configured to send information indicating at least one first frequency portion of a time slot and at least one second frequency portion of a time slot via the transceiver. The processor and the memory are also configured to send a DL resource allocation to a user equipment (UE), the DL resource allocation including an overlapping portion, wherein the DL resource allocation overlaps at least partially with at least one first frequency portion of a time slot. The processor and the memory are also configured to communicate with the UE via a wireless carrier using the time slot.

[0018] These and other aspects of the technology discussed herein will be more fully understood after reading the detailed description below. After reading the following description of certain examples in conjunction with the accompanying drawings, other aspects, features, and examples will become apparent to those skilled in the art. Although the following description may discuss various advantages and features associated with certain embodiments and the accompanying drawings, all embodiments may include one or more advantageous features discussed herein. In other words, although this description may discuss one or more examples as having certain advantageous features, one or more of these features may also be used according to the various examples discussed herein. Similarly, although this description may discuss exemplary embodiments as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1is a schematic diagram of a wireless communication system according to some embodiments.

[0020] Figure 2 is a conceptual diagram of an example of a radio access network (RAN) according to some embodiments.

[0021] Figure 3 is a schematic diagram of radio resource organization in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some embodiments.

[0022] Figure 4 is a detailed view of an example of a scheduling entity with an antenna panel according to some embodiments.

[0023] Figure 5 is a schematic diagram of in-band full-duplex (IBFD) communications according to some embodiments.

[0024] Figure 6 is a schematic diagram of sub-band full-duplex (SBFD) communications according to some embodiments.

[0025] Figure 7 is a conceptual diagram of example time slots configured for SBFD according to some embodiments.

[0026] Figure 8 is a schematic diagram of a series of time slots on a wireless carrier and corresponding operation of an antenna panel according to some embodiments.

[0027] Fig. 9 is a block diagram illustrating hardware or circuitry capable of performing a resource allocation process according to some embodiments.

[0028] Fig.10 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity in accordance with some embodiments.

[0029] Fig.11 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity in accordance with some embodiments.

[0030] Fig.12 is a flow chart illustrating an exemplary process for a scheduled entity to receive information identifying a particular set of resources as unavailable for downlink (DL) transmission in accordance with some embodiments.

[0031] Fig.13 is a flow chart illustrating an exemplary process for a scheduled entity to receive an indication that a portion of a timeslot designated for uplink (UL) communications in a timeslot format is unavailable for DL ​​transmissions in accordance with some embodiments.

[0032] Fig.14is a flow chart illustrating an exemplary process for a scheduled entity to implicitly assume that UL resources in a time slot are not available for DL ​​transmission in accordance with some embodiments.

[0033] Fig.15 is a flow chart illustrating an exemplary process for a scheduled entity to utilize a rate matching pattern with resource block group (RBG) level granularity around the UL portion of a slot in accordance with some embodiments.

[0034] Fig.16 is a flow chart illustrating an exemplary process for dynamically indicating that a preconfigured set of resources is unavailable for DL ​​transmission in accordance with some embodiments.

[0035] Fig.17 is a schematic diagram of SBFD communication including an overlap in frequency between a UL portion and a DL portion according to some embodiments. DETAILED DESCRIPTION

[0036] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations, rather than representing the only configurations in which the concepts described herein can be practiced. For the purpose of providing a thorough understanding of various probabilities, the specific embodiments include specific details. However, those skilled in the art will readily appreciate that these concepts can be practiced without these specific details. In some cases, the description provides known structures and components in block diagram form to avoid confusing these concepts.

[0037] Although the present description describes aspects and embodiments by the description of some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes and / or packaging arrangements. In one example, embodiments and / or use can be generated via integrated chip (IC) embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, various applicability of the innovation may occur. The scope of each implementation may range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems containing one or more aspects of the described technology. In some actual settings, the device incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described embodiments. In one example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The disclosed technology is intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or non-aggregated end-user devices, etc., of various sizes, shapes, and configurations.

[0038] The technology proposed herein is intended to help and / or resolve resource allocation and / or use conflicts. In some aspects, the present disclosure provides several methods and features configured to resolve potential or actual conflicts in frequency allocation. For example, these conflicts may occur in scenarios involving type 1 frequency domain resource allocation in sub-band full-duplex (SBFD). In some scenarios, the allocated downlink resources may overlap with the resources specified for uplink communication in a time slot format. As discussed herein, by resolving this overlap, communication device performance and system throughput are improved.

[0039] The following disclosure presents various concepts that can be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , as an illustrative example and not limiting, the schematic diagram shows various aspects of the present disclosure with reference to a wireless communication system 100. The wireless communication system 100 includes several interacting domains: a core network 102, a radio access network (RAN) 104, and at least one scheduled entity 106 (e.g., at least one user equipment (UE)). By means of the wireless communication system 100, the at least one scheduled entity 106 can be enabled to perform data communications with an external data network 110 (such as (but not limited to) the Internet).

[0040] The RAN 104 may implement any suitable one or more wireless communication technologies to facilitate communication between the scheduled entity 106 and the scheduling entity 108 (e.g., by providing radio access to the scheduled entity 106). In one example, the RAN 104 may operate in accordance with the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G or 5G NR). In some examples, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (commonly referred to as Long Term Evolution (LTE)). 3GPP refers to such a hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be used within the scope of the present disclosure.

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

[0042] As shown, the RAN 104 includes at least one scheduling entity 108, which in some examples can be a base station (BS). Broadly speaking, a BS is a network element in the RAN that provides radio transmission and reception to or from a scheduled entity 106 (e.g., a UE) in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a "base station" differently as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable term.

[0043] The RAN 104 supports wireless communications for multiple mobile devices. A person skilled in the art may refer to a mobile device as a UE, as in the 3GPP specification, but may also refer to a UE as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable term. A UE may be a device that provides access to network services. A UE may take many forms and may include a range of devices.

[0044] Within this document, a "mobile" device (also known as a UE) does not necessarily have the ability to move and can be stationary. The term mobile device or mobile device refers broadly to a wide variety of devices and technologies. A UE may include many hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include, for example, mobile phones, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, personal digital assistants (PDAs), and various embedded systems corresponding to the "Internet of Things" (IoT). A mobile device may additionally be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting devices, home security systems, smart meters, etc. The mobile device may additionally be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure devices that control power (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise devices; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, weaponry, etc. Further, the mobile device may provide networked medical or telemedicine support, i.e., health care at a distance. Telehealth devices may include telehealth monitoring devices and telehealth supervision devices, whose communications may be given priority treatment or prioritized access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or associated quality of service (QoS) for critical service data transmission.

[0045] The wireless communication between the RAN 104 and the scheduled entity 106 (e.g., UE) can be described as utilizing an air interface. Transmissions from the scheduling entity 108 (e.g., BS, UE, etc.) to the scheduled entity 106 (e.g., one or more UEs) over the air interface can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" may refer to point-to-multipoint transmissions originating at the scheduling entity 108. Another way to describe this scheme may be to use the term "broadcast channel multiplexing." On the other hand, transmissions from the scheduled entity 106 to the scheduling entity 108 may be referred to as uplink (UL) transmissions. According to other aspects of the present disclosure, the term "uplink" may refer to point-to-point transmissions originating at the scheduled entity 106. As Figure 1 As shown, the scheduling entity 108 may manage DL traffic 112 to one or more scheduled entities 106 and UL traffic 116 from one or more scheduled entities 106 .

[0046] In some examples, access to the air interface may be scheduled. This may include a scenario in which the scheduling entity 108 allocates wireless resources for communications between some or all devices and equipment within a cell (e.g., a service area of ​​the scheduling entity 108). Within the present disclosure, the scheduling entity 108 may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities 106. That is, for scheduled communications, the scheduled entity 106 utilizes the resources allocated by the scheduling entity 108. In one example, the scheduled entities 106 may include entities (e.g., UEs) scheduled for communication that are configured to utilize resources allocated by the scheduling entity 108.

[0047] It should be noted that the BS is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as the scheduling entity 108. Therefore, the UE can be configured to schedule resources for one or more scheduled entities (e.g., one or more other UEs) in the wireless communication system 100.

[0048] like Figure 1As shown, the scheduling entity 108 can broadcast DL traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, the traffic including DL traffic 112, and in some examples, including UL traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives DL control information (DCI) 114, which includes but is not limited to scheduling information (e.g., grants), synchronization or timing information, or other control information from another entity in the wireless communication network (e.g., from the scheduling entity 108). In one example, the scheduled entity 106 can receive a DL resource allocation for a time slot and determine that a portion of the DL resource allocation overlaps in frequency (e.g., completely or partially) with resources designated as unavailable for DL ​​transmission.

[0049] Typically, the scheduling entity 108 (e.g., one or more base stations (BSs)) may include a backhaul interface for communicating with the backhaul 120 of the wireless communication system 100. The backhaul 120 may provide a link between the scheduling entity 108 (e.g., BS) and the network 102. In addition, in some examples, the backhaul 120 may provide interconnections between multiple scheduling entities 108 (e.g., a first BS and a second BS, etc.). Various types of interfaces for the backhaul 120 may be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0050] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology (RAT) used in the RAN 104. In some examples, the core network 102 may be configured according to NR specifications (e.g., 5GC). In another example, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0051] It should be noted that the techniques described herein can be used for various wireless networks and radio technologies. Although some aspects of the present disclosure may be described using terms typically associated with 3G, 4G, and / or new radio (e.g., 5G NR) wireless technologies, various aspects of the disclosed techniques can be applied in other generation-based communication systems, as will be appreciated by those skilled in the art.

[0052] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. Those skilled in the art may refer to RATs differently as radio technologies, air interfaces, etc. Those skilled in the art may also refer to frequencies as carriers, subcarriers, frequency channels, component carriers, tones, subbands, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs.

[0053] Figure 2 The schematic diagram of RAN 200 is provided by way of example and not limitation. In some examples, RAN 200 may be connected to, for example, Figure 1 The RAN 200 is the same as the RAN 104 described above. For example, the RAN 200 may be an NR system (e.g., a 5G NR network). The RAN 200 may communicate with the core network 102. The core network 102 may communicate with one or more BSs 210, 212, 214, and / or 218 and / or UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 in the RAN 200 via one or more interfaces.

[0054] The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that a user equipment (UE) may uniquely identify based on an identity broadcast from an access point or base station (BS). Figure 2 Macro cells 202, 204, and 206 and small cells 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same BS. A radio link within a sector can be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antennas, each antenna being responsible for communicating with a UE in a portion of the cell.

[0055] Figure 2Two base stations (BSs) 210 and 212 in cells 202 and 204 are shown; and a third base station 214 controlling a remote radio head (RRH) 216 in cell 206 is shown. That is, the BS may have an integrated antenna, or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because BSs 210, 212, and 214 support cells with large sizes. In addition, BS 218 is shown in a small cell 208 (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNode B, etc.) that may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell because BS 218 supports a cell with a relatively small size. The cell size may be determined based on system design and component constraints.

[0056] RAN 200 may include any number of wireless BSs and cells. In addition, the RAN may include relay nodes to extend the size or coverage area of ​​a given cell. BSs 210, 212, 214, 218 provide wireless access points to core network 102 for any number of mobile devices. In some examples, BSs 210, 212, 214, and / or 218 may be connected to reference Figure 1 The scheduling entity 108 described is the same.

[0057] Figure 2 Also included is a quadcopter or drone 220 that can be configured to function as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move based on the location of a mobile base station such as a quadcopter 220.

[0058] Within the RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. In addition, each BS 210, 212, 214, 218, and 220 may be configured to provide an access point to the core network 102 for all UEs in the corresponding cell (see Figure 1 ). For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with BS 214 via RRH 216; UE 234 may communicate with BS 218; and UE 236 may communicate with mobile BS 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with, for example, reference BS 214. Figure 1 The scheduled entity 106 described is the same.

[0059] In some examples, a mobile network node (eg, quadcopter 220) may be configured to function as a UE. For example, quadcopter 220 may operate within cell 202 by communicating with base station 210.

[0060] In other aspects of the RAN 200, sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) may communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a BS (e.g., base station 212). In another example, UE 238 is shown communicating with UEs 240 and 242. Here, UE 238 may be used as a scheduling entity or a primary sidelink device, and UEs 240 and 242 may be used as scheduled entities or non-primary (e.g., auxiliary) sidelink devices. In yet another example, a UE may be used as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or in a mesh network. In the mesh network example, UEs 240 and 242 may optionally communicate directly with each other in addition to communicating with the scheduling entity 238. Thus, in a wireless communication system 100 having scheduled access to time-frequency resources and having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.

[0061] The air interface in RAN 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UE 222 and UE 224 to base station (BS) 210, and multiplexing is provided for DL ​​transmissions from BS 210 to one or more UEs 222 and 224 by utilizing orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (CFDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to such schemes. For example, the UE can provide UL multiple access using time division multiple access (TDMA), time division synchronous code division multiple access (TD-SCDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA) or other suitable multiple access schemes. Furthermore, BS 210 may multiplex DL transmissions to UEs 222 and 224 using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), OFDM, sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0062] In some examples, the network controller 250 can communicate with a set of BSs 210, 212, 214, and / or 218 and provide coordination and control for these BSs 210 (e.g., via the backhaul 120). In certain aspects, the network controller 250 can communicate with the core network 102 (e.g., 5G core network (5GC)), which provides various network functions such as access and mobility management, session management, user plane functions, policy control functions, authentication server functions, unified data management, application functions, network exposure functions, network repository functions, network slice selection functions, etc.

[0063] In some examples, the scheduled entity 106 (e.g., UE) can receive the DL resource allocation from the scheduling entity 108 (e.g., BS). The scheduled entity 106 can communicate with the scheduling entity 108 (e.g., via an air interface in the RAN 200) while ignoring (e.g., disregarding) at least some information of the DL resource allocation because the portion of the DL resource allocation falls within the portion of the carrier designated as unavailable for DL ​​transmission.

[0064] Figure 3 Various aspects of the present disclosure are schematically illustrated with reference to OFDM waveforms. It will be appreciated by those of ordinary skill in the art that various aspects of the present disclosure may be applied to DFT-s-OFDMA waveforms in substantially the same manner as described herein. That is, although some examples of the present disclosure may be focused on OFDM links for clarity, the present disclosure is not limited thereto, and it will be appreciated by those of ordinary skill in the art that one or more of the various techniques of the present disclosure may also be applied to, for example, DFT-s-OFDMA waveforms.

[0065] In some examples, a frame may refer to a predetermined duration for wireless transmission (e.g., 10 ms). And in addition, each frame may consist of a group of subframes (e.g., 10 subframes of 1 ms each). A given carrier may include one group of frames in the UL and another group of frames in the DL. Figure 3 An expanded view of an exemplary DL subframe 302 is illustrated, showing an OFDM resource grid 304. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein based on many factors. Here, time is in units of OFDM symbols in the horizontal direction. Frequency is in units of subcarriers or tones in the vertical direction.

[0066] Resource grid 304 can schematically represent the time-frequency resources for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding number of resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE, which is 1 subcarrier × 1 symbol, is the smallest discrete part of the time-frequency grid and can contain a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a specific implementation, each RE can represent one or more information bits. In some examples, a block of REs can be referred to as a physical resource block (PRB), or more simply as a resource block (RB) 308, which contains any appropriate number of consecutive subcarriers in the frequency domain. In an illustrative and non-limiting example, an RB can include twelve subcarriers (REs), independent of the number of parameter sets used. In some examples, depending on the parameter set, an RB can include any appropriate number of consecutive OFDM symbols in, for example, the time domain.

[0067] The scheduled entity 106 typically utilizes only a subset of the resource grid 304. An RB may be the smallest unit of resources that may be allocated to the scheduled entity 106. Thus, the more RBs are scheduled for the scheduled entity 106, and the higher the modulation scheme selected for the air interface, the higher the data rate for the scheduled entity 106.

[0068] In this illustration, RB 308 occupies less than the entire bandwidth of subframe 302, with some subcarriers shown above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, RB 308 is shown as occupying less than the entire duration of subframe 302, although this is merely one possible example.

[0069] The subframes may have various configurable characteristics. In some examples, the subframes may have a fixed duration or length or a configurable duration or length. In some examples, the subframes may be 1 ms. In some scenarios, each 1 ms subframe 302 may be composed of one or more adjacent time slots (e.g., a series of consecutive time slots). Figure 3 , as an illustrative example, a subframe 302 includes four time slots 310. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given CP length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-slots with shorter durations (e.g., one or two OFDM symbols). In some cases, the scheduling entity may send these mini-slots that occupy resources that are scheduled for ongoing time slot transmissions of the same or different UEs.

[0070] An expanded view of one of the time slots 310 illustrates the time slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry control channels (e.g., a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH)), and the data region 314 may carry data channels (e.g., a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH)). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown in is merely exemplary in nature, and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0071] Although in Figure 3 Although not shown in the figure, each RE 306 within the RB 308 can carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 can also carry pilots or reference signals (RS). These pilots or RS can prepare for a receiving device (e.g., UE) to perform channel estimation on the corresponding channel, which in some examples can enable coherent demodulation / detection of control and / or data channels within the RB 308.

[0072] In a DL transmission, a transmitting device (e.g., a scheduling entity 108) may allocate one or more REs 306 (e.g., within a control region 312) to carry one or more DL control channels. These DL control channels include DCI 114, which typically carries information originating from higher layers (e.g., physical broadcast channel (PBCH), PDCCH, etc.) to one or more scheduled entities 106. The PDCCH may carry DCI 114 for one or more UEs in a cell. This may include, but is not limited to, power control commands, scheduling information, grants, and / or allocation of REs for DL ​​and UL communications.

[0073] In some examples, the transmitting device may allocate one or more DL REs to carry DL physical signals that typically do not carry information from higher layers. These DL physical signals may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a CSI reference signal (CSI-RS), etc. In such an example, DL resources may be allocated to carry such DL physical signals.

[0074] The scheduling entity 108 may send synchronization signals (e.g., PSS and SSS, collectively referred to as SS), and in some examples, the PBCH in the SS block includes four consecutive OFDM symbols, which are numbered in ascending order from 0 to 3 by time index. In the frequency domain, the SS block may extend over 240 consecutive subcarriers, where the subcarriers are numbered in ascending order from 0 to 239 by frequency index. It should be noted that although the present disclosure may sometimes refer to one or more specific SS block configurations as illustrative examples, the present disclosure is not limited thereto, and a person of ordinary skill in the art will understand that other example configurations may also be applicable according to one or more of the various techniques disclosed herein. For illustration, additional or alternative examples may utilize more or less than two synchronization signals, may include one or more supplemental channels in addition to the PBCH, may omit the PBCH, and / or may use non-contiguous symbols for the SS block, to name a few.

[0075] For UL communications, a transmitting device (e.g., a scheduled entity 106) may utilize one or more REs 306 to carry one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. These UL control channels include UL control information (UCI) 118, which typically carries information originating from higher layers. In addition, UL REs may carry UL physical signals, such as a demodulation reference signal (DM-RS), a phase tracking reference signal (PT-RS), a sounding reference signal (SRS), etc., that typically do not carry information originating from higher layers. In some examples, the UCI 118 may include a scheduling request (SR) (e.g., a request for the scheduling entity 108 to schedule an UL transmission). In such an example, in response to receiving the SR sent on the control channel, the scheduling entity 108 may send a DCI 114 that may schedule resources for UL packet transmission.

[0076] The UCI 118 may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or negative acknowledgement (NACK), channel state information (CSI), or any other suitable UCI. HARQ is a technique well known to those skilled in the art, in which a receiving device may check the integrity of a packet transmission at the receiving side to ensure accuracy, for example, using any suitable integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the receiving device (e.g., UE) confirms the integrity of the transmission, it may send an ACK to a transmitting device (e.g., scheduling entity 108). If the integrity of the transmission is not confirmed, the receiving device may send a NACK to the transmitting device. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement catch-up combining, incremental redundancy, etc.

[0077] In addition to control information, one or more REs 306 may be allocated for user data or traffic data (e.g., within data region 314). Such traffic may be carried on one or more traffic channels (e.g., SBFD radio carriers), such as PDSCH for DL ​​transmissions (e.g., DL traffic 112) or PUSCH for UL transmissions (e.g., UL traffic 116).

[0078] In order for the scheduled entity 106 to obtain initial access to the cell, the RAN may provide system information (SI) that characterizes the cell. The RAN may provide this SI using minimum system information (MSI) and other system information (OSI). The RAN may periodically broadcast the MSI on the cell to provide the most basic information required for the scheduled entity 106 to perform initial cell access, and enable the scheduled entity 106 to obtain any OSI that the RAN may broadcast periodically or send on demand. In some examples, the network may provide the MSI over two different DL channels. For example, the PBCH may carry a master information block (MIB) and the PDSCH may carry an SI block type 1 (SIB1). Here, the MIB may provide the UE with parameters for detecting a control resource set. The control resource set may thereby provide the UE with scheduling information corresponding to the PDSCH, such as the resource location of SIB1. Those skilled in the art refer to SIB1 as remaining minimum system information (RMSI) in different ways.

[0079] In some examples, the OSI may include any SI not broadcast in the MSI. In some examples, the PDSCH may carry multiple SIBs, not limited to SIB1. Here, the RAN may provide the OSI in these SIBs (e.g., SIB2 and above).

[0080] This article describes and Figure 1 and / or Figure 3 The channels or carriers illustrated in FIG. 1 are not necessarily all channels or carriers that may be utilized between the scheduling entity 108 and the scheduled entity 106. One of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

[0081] In some examples, the physical layer may typically multiplex and map these physical channels described above to transport channels for processing at a medium access control (MAC) layer entity. The transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to a number of information bits, may be a controlled parameter.

[0082] In some examples, the air interface in RAN 200 can utilize one or more duplex algorithms. "Duplex" generally refers to a scenario in which two endpoints in a point-to-point communication link can communicate with each other in two directions. "Full-duplex" generally refers to a scenario in which two endpoints can communicate with each other simultaneously on the same set of resources. "Half-duplex" generally refers to a scenario in which only one endpoint can send information to another endpoint using a given resource at a time. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD). In an FDD system, transmissions in different directions operate at different carrier frequencies. In a TDD system, transmissions in different directions on a given channel (e.g., a given carrier) are separated from each other by using time division multiplexing. That is, a channel is sometimes dedicated to transmissions in one direction (e.g., DL), and at other times, a channel is dedicated to transmissions in another direction (e.g., UL), where the direction may change very quickly, such as several times per time slot.

[0083] Full-duplex carrier example

[0084] In a wireless link (e.g., wireless communication system 100), a full-duplex channel typically relies on physical isolation of the transmitter and receiver, as well as appropriate interference cancellation techniques. In some examples, the scheduling entity 108 can provide improved isolation between simultaneous transmit and receive operations. In one example, the scheduling entity 108 can use two separate, physically isolated antenna panels for UL communication and DL communication, respectively. In one example, Figure 4 As shown, when communicating over a full-duplex carrier, the scheduling entity 108 may use antenna panel 404 (eg, panel #1) for DL ​​transmission (Tx) and antenna panel 406 (eg, panel #2) for UL reception (Rx).

[0085] However, even with this physical isolation 408 of the transmit and receive antenna panels, wireless communication endpoints performing full-duplex communication are still subject to significant interference. And in particular, the self-interference generated at the same endpoint may be significant. In some examples, the transmit antenna and receive antenna at the scheduling entity 108 may be very close to each other. Therefore, DL transmissions may interfere with UL signals received, for example, using the antenna panel 406. This interference may make it difficult for the scheduling entity 108 to decode the received UL signals.

[0086] One example of a full-duplex communication scheme is generally referred to in the art as In-Band Full-Duplex (IBFD). Typically, in IBFD, DL and UL communications overlap in time and frequency. Figure 5A first example IBFD carrier 502 and a second example IBFD carrier 504 are illustrated. In some examples, the overlap can be complete / full, as shown in the first example, where the UL and DL completely overlap in frequency. In another example, the overlap can be partial, as shown in the second example, where the UL and DL partially overlap in frequency.

[0087] Although IBFD carriers 502 and / or 504 may be described as complete carriers in some cases, the technology of the present disclosure is not limited in this regard, and one of ordinary skill in the art will appreciate that IBFD carriers 502 and / or 504 may instead represent a particular bandwidth portion (BWP) on a given wireless carrier. That is, in various cases, a wireless carrier may include mixed BWPs such that the width of a particular BWP may include a mix of DL portions and UL portions in a single BWP of a given wireless carrier (e.g., IBFD carrier 502, IBFD carrier 504, etc.). It will be appreciated that a given wireless carrier may have multiple such BWPs (e.g., mixed BWPs, etc.).

[0088] Recently, attention has turned to what those skilled in the art may variously refer to as sub-band full duplex (SBFD) or flexible duplex. SBFD differs from conventional FDD in that, in FDD, a given carrier is typically fully dedicated to either UL communications or DL ​​communications. In the case of SBFD, a portion of the time-frequency resources on a given carrier is dedicated to the UL, while a portion of the time-frequency resources on the same carrier supports the DL. Thus, endpoints (e.g., scheduling entity 108, scheduled entity 106) communicating while utilizing SBFD transmit and receive simultaneously, but on different frequency resources of the same carrier. That is, the DL resources are separated from the UL resources in the frequency domain.

[0089] Figure 6 An example of a time slot of a SBFD carrier 602 is illustrated. In the illustrated example, a DL portion 604 of a time slot and a UL portion 606 of a time slot are separated in frequency from each other, while a guard band (GB) 605 exists between the respective UL and DL portions to reduce interference, e.g., UL leakage into DL or DL ​​leakage into UL. However, because the GB 605 may be relatively narrow (e.g., four resource blocks (RBs), five RBs, six RBs, etc.) compared to the separation between carriers in conventional FDD, wireless communications utilizing SBFD may be subject to a greater amount of interference than conventional FDD. With respect to self-interference, a scheduling entity 108 utilizing SBFD may have its DL transmissions disadvantageously leak into its UL receive portion; and a scheduled entity 106 utilizing SBFD may have its UL transmissions disadvantageously leak into its DL receive portion.

[0090] When communicating over an SBFD wireless carrier (e.g., SBFD carrier 602), the scheduling entity 108 may utilize antenna panel 404 to perform DL transmissions at one portion of the SBFD carrier while utilizing antenna panel 406 to perform UL reception at another portion of the SBFD carrier. Thus, self-interference at the scheduling entity 108 may be reduced to some extent via physical isolation 408 of the antennas. In various examples, the respective UL and DL portions of the SBFD carrier may be allocated within a given time slot using any suitable configuration and separated by frequency, time, or both frequency and time. Likewise, although the SBFD carrier 602 may be described as a complete carrier in some cases, the technology of the present disclosure is not limited thereto, and one of ordinary skill in the art will appreciate that the SBFD carrier 602 may instead represent a specific bandwidth portion (BWP) on a given wireless carrier. That is, in various cases, a wireless carrier may include a mixed BWP such that the width of a specific BWP may include a mix of a DL portion (e.g., DL portion 604) and a UL portion (e.g., UL portion 606) in a BWP of a given wireless carrier.

[0091] Figure 7 is a conceptual diagram of an example time slot configured for wireless communications utilizing sub-band full duplex (SBFD) according to an aspect of the present disclosure. In the time slot shown, an upper portion 704B and a lower portion 704A (in frequency) of the time slot are used for downlink (DL) communications, and there is an uplink (UL) portion 702 (e.g., a physical uplink shared channel (PUSCH)) between these portions for UL communications. As shown, one or more guard bands (GBs) can separate the UL portion 702 from the DL portion 704, located directly above and directly below (in frequency) the UL portion 702.

[0092] Figure 7 The example time slots shown on the left in frequency and time are Figure 7 The right side is also shown in amplitude and frequency for further elaboration. As shown, the amplitude of the DL communication is lower at the frequency portion corresponding to the UL portion 702 of the example time slot (e.g., between the DL portions 704A and 704B) and higher at the frequency portion corresponding to the DL portions 704A and 704B of the example time slot. Similarly, the amplitude of the UL communication is higher at the frequency portion corresponding to the UL portion 702 of the example time slot (e.g., between the DL portions 704A and 704B) and lower at the frequency portion corresponding to the DL portions 704A and 704B of the example time slot. The scheduled entity 106 and the scheduling entity 108 can communicate with each other via the SBFD carrier using the example time slot having this time slot format or other such formats (e.g., having at least one DL portion and at least one UL portion).

[0093] Figure 8 A sequence of four consecutive time slots (e.g., time slots AD) on a wireless carrier is shown, which is configured to allow dynamic reconfiguration between time slots for time division duplex (TDD) and sub-band full duplex (SBFD) communications. In some examples, the scheduling entity 108 may designate a corresponding portion of the carrier within a given time slot as an uplink (UL) portion or a downlink (DL) portion. The scheduling entity 108 may signal the designation of the UL and DL portions to the scheduled entity 106 by utilizing an appropriate indication or configuration message that enables the scheduled entity 106 to determine the time slot format. For example, the scheduled entity 106 may determine the time slot format for a given time slot based on an appropriate indication or configuration message provided by the scheduling entity 108. The indication or configuration message may be included within DL control information (DCI) (e.g., DCI 114), within higher layer (e.g., radio resource control (RRC)) signaling, or within some combination of these. The slot format corresponds to the configuration of resource elements (REs) within a slot, such as being configured for UL, DL, or in some examples being configured as flexible (can be UL or DL). In various examples, the configuration or indication message used by the scheduling entity 106 to determine the slot format can correspond to any suitable number of one or more slots, and can correspond to concurrently used and / or later used slots.

[0094] As shown, the first time slot (time slot A) is configured for TDD, where the full carrier bandwidth is used for DL ​​communication except for the last one or two OFDM symbols of the time slot, where the full carrier bandwidth can be used for UL communication, such as HARQ-ACK, channel state feedback (e.g., CSI) and / or UL user data. The second time slot (time slot B) and the third time slot (time slot C) are configured as described herein and Figure 7 Substantially the same approach shown is configured using SBFD, where DL communications are performed at the upper and lower portions of a timeslot (e.g., on a carrier) and UL communications are performed between the DL portions. As discussed herein, the UL portion of a carrier is shown separated from the DL portion of the carrier by a suitable bandwidth guard band (GB) above and below (in frequency) the UL portion. Figure 8 The fourth slot (Slot D) shown is configured for TDD, such as being configured entirely for UL communications. In some examples, the slots shown may represent portions of a carrier (e.g., a bandwidth portion (BWP) of a carrier) or a complete carrier, depending on the implementation.

[0095] In reference Figure 4 In the example of the scheduling entity 108 described above, which includes at least one first antenna panel 404 and at least one second antenna panel 406, Figure 84 and 5. The operation of the corresponding antenna panels during different time slots is illustrated below the corresponding time slots in FIG. That is, in the first time slot (time slot A), both antenna panels 404 and 406 are used for DL ​​communication. Similarly, in the fourth time slot (time slot D), the scheduling entity 108 can use both antenna panels 404 and 406 for UL reception. In the second and third time slots shown (time slots B and C) configured for SBFD, the first antenna panel 404 is configured for DL ​​transmission, while the second antenna panel 406 is configured for UL reception.

[0096] Resource Mapping

[0097] For transmission of PDSCH, the scheduling entity 108 may modulate the codeword using any suitable modulation scheme, including but not limited to QPSK, 16QAM, 64QAM, 256QAM, etc. Fig. 9 In the depicted example, a modulation mapper 902 at the scheduling entity 108 may convert a codeword (e.g., a codeword comprising a sequence of binary digits (0 or 1)) into a complex-valued symbol sequence 912 corresponding to a selected modulation scheme. After the modulation mapper 902, a virtual resource block (VRB) mapper 904 maps the complex-valued sequence 912 to resource elements (REs) in a selected VRB 914. A physical resource block (PRB) mapper 906 then maps the VRB 914 to a PRB 918. Here, the PRB 918 is the actual physical resource used by the scheduling entity 108 to provide DL transmissions. The scheduling entity 108 may utilize the VRB 914 between the modulation mapper 902 and the PRB mapper 906 to provide interleaving in wireless transmissions.

[0098] According to one example, the VRB mapper 904 may map the complex-valued sequence 912 to only those VRBs 914 assigned for transmission that meet a set of defined criteria, as described in Section 7.3.1.5 of 3GPP TS 38.211. In such an example, the VRB mapper 904 may not map the complex-valued sequence 912 to VRBs 914 that do not meet the set of criteria. For example, the VRB mapper 904 may map the complex-valued sequence 912 to those VRBs that the scheduling entity 108 assigned for transmission (e.g., those resources that will be scheduled by the scheduled entity 106 in the DCI 114). In another example, the VRB mapper 904 may determine to map the complex-valued sequence 912 using VRBs whose corresponding PRBs 918 are declared available for PDSCH (e.g., not declared unavailable). In some examples, the bitmap may indicate whether the PRBs are declared unavailable or available, for example, using a binary indicator of the PRBs to designate them as available or alternatively as unavailable. In another example, the VRB mapper 904 may determine to map the complex-valued sequence 912 using VRBs, where the corresponding REs in the corresponding PRBs 918 of those VRBs are:

[0099] Not used for transmission of associated DM-RS or DM-RS for other co-scheduled UEs;

[0100] not used for non-zero power CSI-RS if the corresponding PRB is used for PDSCH scheduled by PDCCH with CRC scrambled by C-RNTI, MCS-C-RNTI, CSRNTI, or PDSCH with semi-persistent scheduling (SPS), unless the non-zero power CSI-RS is a CSI-RS configured by a higher layer parameter CSI-RS-Resource-Mobility in the MeasObjectNR information element (IE), or unless the non-zero power CSI-RS is a non-periodic non-zero power CSI-RS resource; and

[0101] Not used for PT-RS.

[0102] And in addition, according to Section 5.1.4 of 3GPP TS 38.214, the corresponding REs in the corresponding PRBs 918 of those VRBs shall not be declared as "unavailable" (i.e., "unusable") for PDSCH. For example, the corresponding REs cannot be occupied by SSBs, or are declared as unavailable using higher layer (e.g., radio resource control (RRC)) signaling. REs may also be unavailable for PDSCH when the PDSCH is scheduled by a PDCCH with a CRC scrambled by C-RNTI, MCS-C-RNTI, CS-RNTI, or a PDSCH with SPS. This list is not intended to be exhaustive or limiting, and within various aspects of the present disclosure, the scheduling entity 108 may utilize any suitable rules to declare such PRBs and / or REs within such PRBs as unavailable for PDSCH transmission. For resource sets indicated as unavailable for PDSCH transmission, the scheduling entity 106 may be configured with RB-level and / or RE-level granularity.

[0103] The VRB mapper 904 may further utilize a "type 0" or "type 1" frequency domain resource allocation (FDRA) to schedule resources in a given VRB for the PDSCH. With a type 0 DL resource allocation, the scheduling entity 108 may provide a bitmap to the scheduled entity 106, the bitmap having bits representing allocations in a plurality of resource block groups (RBGs). In some examples, each bit in the bitmap may inform the scheduled entity 106 whether the corresponding RBG is allocated to the scheduled entity 106 for DL ​​communication. RGB may represent a group of consecutive VRBs. In one example, an RBG may be defined by a higher layer parameter to represent a group of VRBs.

[0104] Through the type 1 DL resource allocation, the scheduling entity 108 may provide the scheduled entity 106 with continuous, adjacent RB allocations. In one example, the scheduling entity 108 may send information indicating a starting RB and information indicating the number of consecutive RBs (e.g., "L" RBs, where "L" is an integer) to the scheduled entity 106. In one example, the information sent to the scheduled entity 106 may include information related to the starting resource block (RB start ) or starting resource block group (RBG start ) corresponding to the resource indication value (RIV), and in the consecutively allocated resource blocks (L RB ) or in a group of consecutively allocated resource blocks (L RBG) in terms of length. In this manner, the scheduling entity 108 may send, and the scheduled entity 106 may in turn receive, a DL resource allocation in the form of a scheduling grant (e.g., a type 1 grant message). In one example, the scheduled entity 106 may receive a scheduling grant with a predefined DCI format indicator. Based on the DCI format indicator, the scheduled entity 106 may determine whether to use DL FDRA type 0 or type 1 (e.g., to communicate over a wireless carrier utilizing a time slot having a specific time slot format). In some examples, the DL resource allocation may include RIV information for processing and utilization by the scheduled entity 106 to determine whether there is an overlap (e.g., full / partial) between the DL resource allocation and resources designated as unavailable for DL ​​transmission on the SBFD wireless carrier.

[0105] By utilizing DL resource allocation of type 0, essentially any desired resource configuration can be provided, and any combination of bits in the bitmap is theoretically possible. However, the bitmap provided in DL resource allocation "type 0" results in increased overhead compared to DL resource allocation "type 1". That is, for DL ​​resource allocation, FDRA type 1 achieves resource allocation with significantly lower overhead compared to FDRA type 0.

[0106] In such an example, the PRB mapper 906 may map the VRBs 914 to the PRBs 918 according to an interleaved or non-interleaved mapping scheme. With the non-interleaved mapping scheme, the PRB mapper 906 may substantially directly map the VRBs to the corresponding PRBs. On the other hand, the interleaved mapping scheme substantially provides a shuffle between different frequency subcarriers.

[0107] As described above, with SBFD (e.g., flexible duplexing), a portion of a carrier bandwidth may be used for UL communications, while another portion of the same carrier bandwidth may be used for DL ​​communications. However, in the case of a type 1 DL resource allocation performed by the VRB mapper 904, a conflict with SBFD may result. That is, a continuous resource allocation for PDSCH (as performed for a type 1 DL resource allocation) may overlap with resources already reserved for PUSCH in the same carrier. Although there may be some advantages to utilizing the overlap between DL and UL communications in some specific cases, according to one aspect of the present disclosure, it may be advantageous for the scheduled entity 106 (typically in the case of SBFD) to avoid using resources related to such an overlap as "unavailable" for DL ​​when the scheduled entity 106 has identified such resources as "unavailable" for DL. In one example, the scheduled entity 106 may ignore resource elements (REs) related to such an overlap. That is, the scheduled entity 106 may assume that REs associated with such overlapping portions are unavailable for PDSCH, and thus, the scheduled entity 106 may ignore such REs and instead process REs in the non-overlapping portions when communicating over the SBFD carrier.

[0108] In some examples, as described above, the VRB mapper 904 can provide a set of contiguous resource blocks (RBs) in the frequency domain. In one example, the VRB mapper 904 can utilize a type 1 DL resource allocation (e.g., FDRA type 1) to provide a set of contiguous RBs allocated for the PDSCH. In this case, the PRB mapper 906 that utilizes non-staggered VRB to PRB mapping can also provide a contiguous frequency domain allocation for the PDSCH in the physical resource allocation. In addition, even if the PRB mapper 906 utilizes staggered VRB to PRB mapping, the staggering operation may still result in a contiguous frequency domain allocation for the PDSCH in the physical resource allocation depending on the staggering scheme. If a carrier is configured for SBFD (e.g., as a wireless carrier with a UL portion between the DL portion of the carrier, such as Figure 7 As shown in FIG. 1 , such continuous allocation for DL ​​channels (eg, PDSCH) may cause problems. Figure 7 As shown, there may be a relatively large RB band that is not available for DL ​​transmission because the band has been reserved for UL communication (eg, for PUSCH).

[0109] In some examples, if the starting RB of the type 1 DL resource allocation is lower than the PUSCH (in frequency) and the number of consecutive RBs of the type 1 DL resource allocation is sufficient to span this PUSCH, then there may be a conflict at the overlapping portion (e.g., partial overlap or full overlap) of a given time slot. In fact, such a conflict may sometimes be intentional or useful, for example, when the scheduling entity 108 may send information (including but not limited to SSB) via resources reserved for UL communication. However, in other cases, the scheduled entity 106 may receive and process information in the UL portion of the carrier, and therefore, the UL portion does not actually carry any information useful to the scheduled entity 106.

[0110] In certain specifications of 5G NR, this conflict can be resolved by including resources in the UL portion of the carrier as resources that are not allowed for DL ​​transmission. However, by providing a bitmap corresponding to those resources, these specifications only specify this behavior of including resources as not allowed, which can result in a large amount of control signaling overhead. This may be an unacceptable cost because type 1 DL resource allocation is generally intended to reduce such signaling overhead relative to type 0 DL resource allocation. That is, when using type 0 DL resource allocation, such conflicts do not usually occur because the scheduling entity 108 clearly indicates the available and unavailable resources to the scheduled entity 106 in the form of a large bitmap. However, when conflicts occur when using type 1 DL resource allocation, the potential non-ideal solution requires the scheduling entity 108 to clearly indicate the unavailable resource set to the scheduled entity 106 in the form of a similar large bitmap. Various aspects of the present disclosure are intended to solve the above-mentioned problems in type 1 DL resource allocation without the cost of such a significant increase in signaling overhead.

[0111] Notify the scheduled entity of unavailable resources

[0112] Some aspects of the present disclosure provide mechanisms and algorithms to address situations where, for a type 1 downlink (DL) frequency domain resource allocation (FDRA) on a SBFD carrier, at least a portion of a physical resource block (PRB) allocated for DL ​​communications overlaps with resources reserved for UL communications by a slot format. In one example, a slot format may reserve resources for different communications using a slot format indication that indicates which resources are so reserved.

[0113] Furthermore, the overlapping portion of the DL resource allocation (eg, allocated PRBs) overlapping the UL portion reserved for UL communications may include a partial overlap or a full overlap in frequency, wherein at least a portion of the DL resource allocation overlaps with at least a portion of the UL portion.

[0114] It should be noted that although the present disclosure may describe the time slot format as indicating certain frequency parts of the time slot in a specific form in some cases, the technology of the present invention is not limited thereto. It will be understood by those of ordinary skill in the art that the time slot format can represent various forms of information. In one example, the time slot format can indicate at least one first frequency part of the time slot according to at least one first bandwidth part (BWP) corresponding to the wireless carrier. Similarly, the time slot format can indicate at least one second frequency part of the time slot according to at least one second BWP corresponding to the wireless carrier. In an illustrative example, a base station (BS) can provide information to the UE indicating at least one first frequency part of the time slot for UL communication (e.g., unavailable for DL ​​communication) and at least one second frequency part of the time slot for DL ​​communication. In such an example, the BS can provide information indicating at least one first BWP and information indicating a second BWP to the UE, wherein at least one first frequency part of the time slot can correspond to at least one first BWP, and at least one second frequency part of the time slot can correspond to at least one second BWP. In this way, the UE can receive information indicating at least one first frequency part of the time slot for UL communication from the BS. Thus, the UE may determine at least one first BWP corresponding to at least one first frequency portion of the time slot, and similarly may determine at least one second BWP corresponding to at least one second frequency portion of the time slot.

[0115] In such an example, as described herein, the UE may receive a DL resource allocation from the BS. And upon determining to ignore information related to any resources falling within the overlapping portion of the DL resource allocation, the UE may further communicate with the BS (e.g., via the wireless carrier according to the bandwidth portion) while ignoring information related to the overlapping portion (e.g., corresponding to the first BWP). In this way, the UE may communicate with the BS via the wireless carrier using a time slot format while ignoring DL data corresponding to the overlapping portion of the time slot having resources that are not available for DL ​​communication (e.g., the overlapping portion of the first BWP).

[0116] Although the following description refers to the process generally illustrating the process occurring at the scheduled entity 106 (eg, user equipment (UE)), Figures 12 to 17 , but it should be understood that the present disclosure is not limited to the operations or processes at the scheduled entity 106. That is, the following description also describes the processes and operations occurring at the scheduling entity 108 (e.g., a base station (BS), another UE configured for scheduling, etc.), and the present disclosure is written to fully disclose the operations at both endpoints of the signaling exchange between the scheduled entity 106 and the scheduling entity 108.

[0117] Fig.121 is a flow chart illustrating an exemplary process 1200 for a scheduled entity 106 (e.g., a UE) to receive information (e.g., from a scheduling entity 108). The information may be configured to indicate or identify resources to be used for communication. According to some embodiments, this may include identifying a particular set of resources as unavailable for DL ​​transmission.

[0118] In one example, the scheduling entity 108 may identify a resource set as unavailable for DL ​​transmission. In such an example, the scheduling entity 108 may transmit the resource set (e.g., as a representation of the resource set) to the scheduled entity 106. In such an example, the scheduled entity 106 may utilize the resource set to determine which resources are available for DL ​​transmission (e.g., resources corresponding to the DL portion of the SBFD carrier). Additionally or alternatively, the scheduled entity 106 may utilize the resource set or the representation of the resource set to determine which resources are unavailable for DL ​​transmission. In one example, such unavailable resources may include resources of the SBFD carrier reserved for UL communications, resources corresponding to a guard band (GB) portion of the SBFD carrier, resources corresponding to a dynamically indicated portion of the SBFD carrier, and the like. In this way, the scheduled entity 106 may determine when to allocate appropriate processing resources to more fully consider (and / or allow further passing through the wireless network) certain DL data corresponding to those resources that are considered available for DL ​​transmission. Additionally or alternatively, the scheduled entity 106 may determine when it is advantageous to ignore DL data corresponding to those resources deemed unavailable for DL ​​transmission, eg, to avoid adversely affecting any UL data conveyed in one or more UL transmissions over the SBFD carrier.

[0119] As described herein, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. Fig.10 The scheduling entity 1000 shown in and / or Fig.11 The scheduled entity 1100 shown in FIG. 1100 may be configured to perform process 1200. In some examples, process 1200 may be performed by any suitable device or component for performing the functions or algorithms described herein.

[0120] At block 1202, the scheduled entity 106 may determine a slot format for one or more time slots. In one example, the scheduled entity 106 may receive an indication or configuration message from the scheduling entity 108 (e.g., a BS) sufficient for the scheduled entity 106 to determine the slot format for a given time slot. The indication or configuration message may identify the UL portion of the time slot (e.g., a first frequency portion) and at least one DL portion of the time slot (e.g., a second frequency portion). That is, the slot format indication or configuration message may identify at least a portion of the time slot as being used for UL communication and at least one other portion as being used for DL ​​communication. In some scenarios, additionally or alternatively, the scheduled entity 106 may determine a slot format for at least one time slot on the SBFD carrier. A time slot configured according to the slot format may include at least one first frequency portion and at least one other frequency portion. Therefore, at least one first frequency portion of such a formatted time slot may be used for UL communication, and at least one other frequency portion may be used for DL ​​communication.

[0121] Messaging related to the slot format may take various forms. In one example, the slot format indication or configuration message may include a format index identifying the slot format configuration. The scheduled entity 106 may utilize the format index to determine the frequency portion of the slot that has been reserved for UL communication. In some examples, higher layer parameters may configure the scheduled entity 106 with a slot format to have at least one frequency portion designated for DL ​​communication and at least one frequency portion designated for UL communication.

[0122] At block 1204, the scheduled entity 106 may receive a control message (e.g., a radio resource control (RRC) message) from another entity (e.g., a scheduling entity or other wireless device). The control message may indicate or identify a resource set corresponding to the UL portion of the time slot as including resources that are not available for DL ​​transmission. In one example, the scheduling entity 108 may provide appropriate signaling to the scheduled entity 106 (e.g., by utilizing higher layer signaling such as RRC signaling) to inform the scheduled entity 106 that the UL portion of the time slot is included in the resource set that is not available for DL ​​transmission. In some examples, this mechanism may be similar to the scheduling entity 108 signaling to the scheduled entity 106 that there is rate matching around the UL portion (e.g., around the UL frequency band).

[0123] Control messaging can have a variety of features. In some examples, the scheduling entity 108 can provide information to the scheduled entity 106 that indicates a starting indication (e.g., a starting RB; or a starting RE) and a length indication (e.g., a number of RBs; or a number of REs) of certain resources that are unavailable for DL ​​transmission. In such examples, the control message (e.g., a radio resource control (RRC) message) can include the starting resources (e.g., a starting indication) and the length corresponding to the resources that are unavailable for DL ​​transmission (e.g., a number of REs, a number of RBs). In some examples, the control message can include information indicating a group of starting resources. In such examples, the control message can be based on a starting resource block group (RBG). start ) to specify the start indication. Similarly, the control message may include an indication according to RBG (e.g., L RBG The control message may include information of a length specified by a set of RBGs (or a predetermined number of RBGs), where the resources within the set of RBGs may then be designated as corresponding to resources that are unavailable for DL ​​transmission. That is, the control message may utilize various levels of granularity, such as by utilizing RE-level granularity, RB-level granularity, or RBG-level granularity as further discussed herein, thereby effectively designating (e.g., assigning) certain resources as unavailable for DL ​​transmission.

[0124] In some cases, the control message may include information indicating a resource set used in the communication. This may indicate whether the resource set includes less than the entire resource set corresponding to the entire UL portion when the start indication and length indication are provided. In another example, the resource set may include more than the entire resource set corresponding to the entire UL portion. In one example, the control message may indicate that the UL portion is not available for DL ​​transmission and that additional resources (indicated by the start resource and length resource) are also not available for DL ​​transmission. In such an example, the scheduled entity 106 may receive the start resource and length resource for the UL portion (e.g., an explicit indication), or may determine such resources corresponding to the UL portion from information indicating the time slot format (e.g., a format index). In any case, the control message may configure the scheduled entity 106 to determine a resource set that is not available for DL ​​transmission.

[0125] Thus, the scheduled entity 106 may utilize the control message to specify any resource (e.g., any RB / RE / RBG) of the time slot. Some of these resources may fall after the starting resource (e.g., the starting indication) and fall within the length corresponding to the resource (e.g., the length indication) that is not available for DL ​​transmission due to being effectively unavailable for DL ​​transmission. That is, the scheduled entity 106 may determine that the resource after the starting indication within the length indication corresponds to the resource that is not available for DL ​​transmission. Thus, the scheduled entity 106 may utilize the information from the control message to subsequently identify the resource set that is designated as being unavailable for DL ​​transmission accordingly. In some cases, the resource set may correspond to at least some UL portions of the time slot (e.g., at least one UL frequency band or first frequency portion of the time slot). In addition, the resource set may also correspond to one or more guard band (GB) portions of the time slot that overlap with the first frequency portion of the time slot for UL communication. That is, in some cases, the UL frequency portion of the time slot may effectively include one or more GB portions that are indicated as being unavailable for DL ​​transmission (e.g., via the start and length indications, and / or via dynamic indications).

[0126] At block 1206, the scheduled entity 106 may receive a type 1 DL grant message for the time slot. In one example, the scheduled entity 106 may receive a DL resource allocation for the time slot from the scheduling entity 108. The scheduled entity 106 may receive the grant message because there are multiple RBs or REs (related to different frequency portions of the time slot) that the scheduled entity 106 may consider (e.g., by determining processing) or otherwise ignore (e.g., disregard, forgo processing, omit, discard, exclude, etc.) according to one or more of the various techniques of this disclosure.

[0127] At block 1208, the scheduled entity 106 may determine whether an overlap scenario may occur or is occurring. An overlap scenario may exist when a DL grant message overlaps in frequency (e.g., partially or completely) with resources designated as unavailable for DL ​​transmission. In one example, the scheduled entity 106 may determine whether any portion of a DL resource allocation for a time slot (e.g., a DL grant message) overlaps with resources designated as unavailable for DL ​​communication (e.g., by a SBFD wireless carrier).

[0128] Alternatively, when communicating over the wireless carrier, the scheduled entity 106 may make this determination by ignoring any portion of the DL grant message that overlaps with resources designated as unavailable for DL ​​communication. That is, in some cases, for purposes of illustration, the present disclosure assumes that a particular example for a DL grant message includes an overlapping portion ("yes" at block 1208), thereby allowing the present disclosure to describe how the scheduled entity 106 may then ignore information related to the overlapping portion. However, in some cases, the DL grant message may not include any overlapping portion, in which case the scheduled entity 106 may utilize all resources of the DL grant message to communicate over the wireless carrier, rather than ignoring certain of these resources, as the scheduled entity 106 may do if there is an overlapping portion. In any case, the scheduled entity 106 may identify the overlapping portion of the DL resource allocation (e.g., DL grant message) by effectively disregarding information related to certain resources on a frequency (e.g., related to a bandwidth portion (BWP) of a frequency portion that is determined to be exclusively allocated for communication in another direction (e.g., UL, reverse sidelink (SL) direction, etc.)). In this way, the scheduled entity 106 can communicate with the scheduling entity 108 over the wireless carrier while ignoring information related to one or more overlapping portions. The scheduled entity 106 can do this by providing UL transmissions and receiving DL transmissions in time slots on the wireless carrier, where, for example, both entities advantageously pay attention to a specific time slot format of the time slot in a specific manner disclosed.

[0129] In some examples, the scheduled entity 106 may determine in any suitable manner whether the DL grant message includes resources that overlap with resources that are unavailable for DL ​​transmission. In some examples, the scheduled entity 106 may determine whether the DL grant message includes resources that overlap with resources that are unavailable for DL ​​transmission by comparing at least a portion of a set of resources that are designated as unavailable (e.g., via a control message) with resources corresponding to a DL resource allocation for a time slot (e.g., a DL grant message). In this way, the scheduled entity 106 may determine whether there is an overlap between at least some of the resources in the two resource sets when compared to each other. In one example, the scheduled entity 106 may determine that both sets imply one or more identical resources (e.g., a subset of REs in the overlapping portion of the DL resource allocation). The scheduled entity 106 may then determine that the overlapping portion of the DL resource allocation does exist, and therefore the overlapping portion includes (e.g., implies) resources that were previously designated as unavailable for DL ​​transmission.

[0130] If the DL grant message overlaps with resources designated as unavailable for DL ​​transmission, at block 1210, the scheduled entity 106 may take additional actions. One example action is that the scheduled entity 106 may ignore REs located within the overlapping portion of the DL grant message. Choosing not to use or ignore (e.g., disregarding, forgoing processing, omitting, discarding, excluding, etc.) resources in the overlapping portion of the DL grant message may include passively not using and / or more actively blocking resources related to the overlapping portion of the DL grant message. In an illustrative example, the scheduled entity 106 may receive information for the DL grant message from the scheduling entity 108, the information including a complete set of resources (e.g., a set of REs). The scheduled entity 106 may receive information for the DL grant message corresponding to a first subset of resources of the complete set of resources for the DL grant message. In this case, the first subset of resources includes resources of a time slot located in a portion of the DL grant message that overlaps with the UL portion of the time slot (e.g., a portion consisting of resources that are considered unavailable for DL ​​transmission). In addition, the scheduled entity 106 may receive information corresponding to a second subset of resources of the complete set of resources for the DL grant message. In this case, the second subset of resources includes other resources of the time slots located in a second non-overlapping portion of the DL grant message (eg, in the portion of the time slots consisting of resources deemed acceptable for DL ​​communications).

[0131] In this illustrative example, the scheduled entity 106 may determine to process information corresponding to the second subset of resources (e.g., in the non-overlapping portion) and may ignore resources from the first subset of resources (e.g., in the overlapping portion). That is, the scheduled entity 106 may ignore resources from the first subset of resources without attempting to identify and / or retain any further information or data represented by the first subset of resources. The scheduled entity 106 may actively ignore such resources (e.g., by performing some processing to isolate such resource elements (REs) in the overlapping portion) and remove information related to the overlapping portion from any further processing. In another example, the scheduled entity 106 may ignore information related to such overlapping portions in frequency based on a purely passive mechanism, whereby the scheduled entity 106 allocates processing resources for processing information related to the non-overlapping portion while intentionally skipping any resource elements determined to be related to the overlapping portion.

[0132] In such an example, the scheduled entity 106 may prioritize allocating processing resources to process information associated with one or more non-overlapping portions. Thus, the scheduled entity 106 may then determine to allocate any processing resources reserved for processing information associated with overlapping portions of the wireless carrier and then use them to process information associated with the non-overlapping portions or save such processing resources instead. In this way, the scheduled entity 106 communicates over the wireless carrier using a slotted format while ignoring (e.g., disregarding, moving / reallocating processing resources, etc.) any information associated with overlapping portions, such as where a DL resource allocation at least partially overlaps with a UL frequency portion.

[0133] In such a case, the scheduled entity 106 may ignore (e.g., disregard) information of the DL grant message corresponding to the UL portion of the time slot. In one example, the scheduled entity 106 may communicate via the SBFD wireless carrier using the time slot while ignoring (e.g., disregarding) REs received in the overlapping portion of the DL grant message (e.g., information related to the overlapping portion). That is, the scheduled entity 106 may communicate via the wireless carrier using the time slot format (e.g., using the time slot on the carrier configured according to the time slot format) while ignoring information related to (e.g., falling within) the overlapping portion.

[0134] If there is no such overlap (i.e., no overlapping portion), then at block 1212, the scheduled entity 106 can utilize the resources allocated in the DL grant message and can receive and process the corresponding REs. In such an example, the scheduled entity 106 can communicate over the wireless carrier using the slot format while also utilizing all resources of the type 1 DL resource allocation for the slot in such a case. That is, the scheduled entity 106 can utilize all information corresponding to the REs allocated in the DL grant message while ignoring the REs located in any portion of the DL grant message because the overlapping portion creates a conflict between the slot format and the DL resource allocation.

[0135] Fig.13 1 is a flow chart illustrating an exemplary process 1300 for a scheduled entity 106 (e.g., a UE) to receive an indication that a portion of a time slot designated for UL communication in a time slot format is not available for DL ​​transmission according to some embodiments. As described herein, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Fig.10 The scheduling entity 1000 shown in and / or Fig.11 The scheduled entity 1100 shown in FIG. 1300 may be configured to perform the process 1300. In some examples, the process 1300 may be performed by any suitable device or component for performing the functions or algorithms described herein.

[0136] At block 1302, the scheduled entity 106 may determine a slot format for one or more time slots. In one example, the scheduled entity 106 may receive an indication or configuration message from the scheduling entity 108 (e.g., a BS) sufficient for the scheduled entity 106 to determine the slot format for a given time slot. The indication or configuration message may identify a UL portion of the time slot (e.g., a first frequency portion) and at least one DL portion of the time slot (e.g., a second frequency portion).

[0137] At block 1304, the scheduled entity 106 may receive an indication that the entire UL portion of the time slot (specified in the time slot format configuration) is unavailable for DL ​​transmission. In one example, the scheduled entity 108 may explicitly configure the scheduled entity 106 to specify the entire UL portion of the time slot as resources unavailable for DL ​​transmission. In such a case, the scheduled entity 106 may determine that the entire UL portion of the time slot includes resources unavailable for DL ​​transmission.

[0138] Additionally or alternatively, the scheduling entity 108 may explicitly configure the scheduled entity 106 to designate one or more guard band (GB) portions on either or both sides of the UL portion of the time slot (e.g., the UL portion and at least one DL portion of the adjacent time slot) as resources that are (also) unavailable for DL ​​transmission. In such a case, the scheduled entity 106 may determine that the entire UL portion of the time slot and the one or more GB portions on either or both sides of the UL portion of the time slot include an entire set of resources that are unavailable for DL ​​transmission.

[0139] In some examples, the scheduling entity 108 may provide explicit signaling to indicate to the scheduled entity 106 that the UL portion of the time slot, and in some examples, one or more GBs (as indicated using the time slot format configuration) are unavailable (i.e., cannot be used) for DL ​​transmission. In yet another example, the time slot format configuration or indication message itself may include such an indication that the UL portion of the time slot, and in some examples, one or more GBs are unavailable for DL ​​transmission. In one example, the scheduled entity 106 may receive the time slot format configuration from the scheduling entity 108 and determine the time slot format of the time slot based on the time slot format configuration. Thus, when determining the time slot format, the scheduled entity 106 may also determine based on the time slot format configuration that the entire UL portion of the time slot (and in some cases, one or more GB portions) represents resources that are unavailable for DL ​​transmission. In some examples, this mechanism may be similar to the scheduling entity 108 signaling to the scheduled entity 106 that there is rate matching around the UL portion (e.g., around the UL frequency band).

[0140] At block 1306, the scheduled entity 106 may receive a type 1 DL grant message for the time slot. In one example, the scheduled entity 106 may receive a DL resource allocation for the time slot from the scheduling entity 108. The scheduled entity 106 may receive the grant message because there are multiple RBs or REs (related to different frequency portions of the time slot) that the scheduled entity 106 may consider (e.g., by determining processing) or otherwise ignore (e.g., disregard, forgo processing, omit, discard, exclude, etc.) according to one or more of the various techniques of this disclosure.

[0141] At block 1308, the scheduled entity 106 may determine whether the DL grant message overlaps (e.g., partially or completely) in frequency with resources designated as unavailable for DL ​​transmission. In one example, the scheduled entity 106 may determine whether any portion of the DL resource allocation for the time slot (e.g., the DL grant message) overlaps with resources designated as unavailable for DL ​​communication (e.g., by an SBFD wireless carrier). Alternatively, as described above, when communicating via a wireless carrier, the scheduled entity 106 may make this determination by ignoring any portion of the DL grant message that overlaps with resources designated as unavailable for DL ​​communication. In one example, block 1308 may represent optional items (e.g., descriptive items, or assumed fact items for specific communications for example illustration). In one example, the items may be shown for illustrative purposes, indicating that there may be overlapping portions in some cases. This block 1308 may be further shown as being included in an example flow chart to indicate how one or more of the various techniques of the present disclosure may be applied to resolve certain DL information related to overlapping portions. As described herein, the techniques of the present disclosure address certain DL information related to overlapping portions in a manner that seeks to avoid portions of DL transmissions from interfering with portions of UL transmissions when the scheduled entity 106 is communicating with the scheduling entity 108 utilizing a particular wireless carrier.

[0142] If the DL grant message overlaps with resources designated as unavailable for DL ​​transmission, at block 1310, the scheduled entity 106 may ignore REs located within the overlapping portion of the DL grant message. In this way, the scheduled entity 106 may ignore information of the DL grant message corresponding to the UL portion of the time slot. In one example, the scheduled entity 106 may communicate over the SBFD wireless carrier using the time slot while ignoring (e.g., disregarding, abandoning processing, omitting, discarding, excluding, etc.) REs received in the overlapping portion of the DL grant message (e.g., information related to the overlapping portion). That is, the scheduled entity 106 may communicate over the wireless carrier using the time slot format (e.g., using a time slot on a carrier configured according to the time slot format) while ignoring information related to (e.g., falling within) the overlapping portion.

[0143] If there is no such overlap (i.e., no overlapping portion), then at block 1312, the scheduled entity 106 may utilize the resources allocated in the DL grant message and may receive and process the corresponding REs. In such an example, the scheduled entity 106 may communicate over a wireless carrier using a slot format (e.g., sending a slot on a carrier that is formatted according to a slot format), wherein in such a case, the scheduled entity 106 may utilize all resources of a type 1 DL resource allocation for the slot. That is, the scheduled entity 106 may utilize all information corresponding to the REs allocated in the DL grant message while ignoring REs located in any portion of the DL grant message because the overlapping portion creates a conflict between the slot format and the DL resource allocation.

[0144] Fig.14 1 is a flow chart illustrating an exemplary process 1400 for a scheduled entity 106 (e.g., a UE) to implicitly assume that UL resources in a time slot format are unavailable for DL ​​transmissions according to some embodiments. As described herein, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Fig.10 The scheduling entity 1000 shown in and / or Fig.11 The scheduled entity 1100 shown in FIG. 1400 may be configured to perform the process 1400. In some examples, the process 1400 may be performed by any suitable device or component for performing the functions or algorithms described herein.

[0145] At block 1402, the scheduled entity 106 may determine a slot format for one or more time slots. In one example, the scheduled entity 106 may receive an indication or configuration message from the scheduling entity 108 (e.g., a BS) sufficient for the scheduled entity 106 to determine the slot format for a given time slot. The indication or configuration message may identify at least one UL portion of the time slot (e.g., at least one first frequency portion) and at least one DL portion of the time slot (e.g., at least one second frequency portion). In an illustrative and non-limiting example, the indication or configuration message may identify at least one first bandwidth portion (BWP) as a portion of the time slot that the scheduling entity 108 has designated as being used for UL communication (e.g., unavailable for DL ​​communication). Additionally, the indication or configuration message may identify at least one second BWP as a portion of the time slot that the scheduling entity 108 has designated as being used for DL ​​communication. In such an example, the indication or configuration message may identify at least one UL portion of the time slot and at least one DL portion of the time slot. In another example, the indication or configuration message may identify respective frequency portions that the scheduling entity 108 has designated as being used for DL ​​communication and for UL communication in the time slot. This information may be used when the scheduling entity 108 and the scheduled entity 106 communicate information (eg, data, content, etc.) over a particular wireless carrier (eg, a SBFD carrier) utilizing a slot format, such as when sending time slots on a wireless carrier according to the slot format.

[0146] In some examples, when determining the timeslot format, the scheduled entity 106 can identify that the UL portion of the timeslot represents resources that are implicitly unavailable for DL ​​transmission. That is, rather than having the scheduling entity 108 provide explicit signaling for this purpose, the scheduled entity 106 can implicitly assume that the UL portion of the timeslot is included in the resources that are unavailable for DL ​​transmission.

[0147] At block 1404, the scheduled entity 106 may receive a type 1 DL grant message for the time slot. In one example, the scheduled entity 106 may receive a DL resource allocation for the time slot from the scheduling entity 108. The scheduled entity 106 may receive the grant message because there are multiple RBs or REs (e.g., related to different frequency portions of the time slot) that the scheduled entity 106 may consider (e.g., by determining processing) or otherwise ignore (e.g., disregard, forgo processing, omit, discard, exclude, etc.) according to one or more of the various techniques of this disclosure.

[0148] At block 1406, the scheduled entity 106 may determine whether the DL grant message overlaps (e.g., partially or completely) in frequency with resources identified as unavailable for DL ​​transmission. In one example, the scheduled entity 106 may determine whether any portion of the DL resource allocation for the time slot (e.g., the DL grant message) overlaps with resources designated as unavailable for DL ​​communication (e.g., by an SBFD wireless carrier). Alternatively, as described above, when communicating via a wireless carrier, the scheduled entity 106 may make this determination by ignoring any portion of the DL grant message that overlaps with resources designated as unavailable for DL ​​communication. In one example, block 1406 may represent an optional item (e.g., a descriptive item, or an assumed fact item for a particular communication illustrated by the example). In one example, an item may be shown for illustrative purposes, thereby indicating that there may be overlapping portions in some cases. This block 1406 may be further shown as being included in an example flow chart to indicate how one or more of the various techniques of the present disclosure may be applied to resolve certain DL information related to overlapping portions. As described herein, the techniques of the present disclosure address certain DL information related to overlapping portions in a manner that seeks to avoid portions of DL transmissions from interfering with portions of UL transmissions when the scheduled entity 106 is communicating with the scheduling entity 108 utilizing a particular wireless carrier.

[0149] If the DL grant message overlaps with resources identified as corresponding to the UL portion in the time slot format, at block 1408, the scheduled entity 106 may ignore the REs located within the overlapping portion of the DL grant message. In this way, the scheduled entity 106 may ignore the information of the DL grant message corresponding to the UL portion of the time slot. In one example, the scheduled entity 106 may communicate over the SBFD wireless carrier using the time slot while ignoring (e.g., disregarding, abandoning processing, omitting, discarding, excluding, etc.) the REs received in the overlapping portion of the DL grant message (e.g., information related to the overlapping portion). That is, the scheduled entity 106 may communicate over the wireless carrier using the time slot format (e.g., using the time slot on the carrier configured according to the time slot format) while ignoring information related to (e.g., falling within) the overlapping portion.

[0150] If there is no such overlap (i.e., no overlapping portion), then at block 1410, the scheduled entity 106 can utilize the resources allocated in the DL grant message and can receive and process the corresponding REs. In such an example, the scheduled entity 106 can communicate over the wireless carrier using the time slot format while also utilizing all resources of the type 1 DL resource allocation for the time slot in such a case. That is, the scheduled entity 106 can utilize all information corresponding to the REs allocated in the DL grant message while ignoring the REs located in any portion of the DL grant message because the overlapping portion creates a conflict between the time slot format and the DL resource allocation.

[0151] PDSCH resource mapping with RBG level granularity

[0152] Fig.15 1 is a flow chart illustrating an exemplary process 1500 for a scheduled entity 106 (e.g., a UE) to utilize a rate matching pattern with resource block group (RBG) level granularity around the UL portion of a time slot (e.g., on a SBFD wireless carrier) in accordance with some embodiments. As described herein, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Fig.10 The scheduling entity 1000 shown in and / or Fig.11 The scheduled entity 1100 shown in FIG. 15 can be configured to perform process 1500. In some examples, process 1500 can be performed by any suitable device or component for performing the functions or algorithms described herein.

[0153] At block 1502, the scheduled entity 106 may determine a slot format for one or more time slots. In one example, the scheduled entity 106 may receive an indication or configuration message from the scheduling entity 108 (e.g., a BS) sufficient for the scheduled entity 106 to determine the slot format for a given time slot. The indication or configuration message may identify at least one UL portion of the time slot (e.g., a first frequency portion) and at least one DL portion of the time slot (e.g., a second frequency portion).

[0154] At block 1504, the scheduled entity 106 may receive a rate matching pattern with resource block group (RBG) level granularity. In one example, the rate matching pattern may include a bitmap string indicating RBGs corresponding to those unavailable resources. In such an example, the rate matching pattern may correspond to the UL portion of a timeslot (e.g., on a SBFD wireless carrier).

[0155] In existing 3GPP specifications for 5G NR (e.g., TS 38.214), the scheduling entity 108 can address the overlap between the frequency domain resource allocation (FDRA) for DL ​​and the resources reserved for UL communication by including the resources of the UL portion as resources that are unavailable for DL ​​transmission. However, in some cases, these specifications may only specify such inclusion behavior of resources (e.g., including as unavailable) by having the scheduling entity 108 provide a bitmap string corresponding to those unavailable resources to the scheduled entity 106, where the bits in the bitmap represent RE-level or RB-level granularity. In one example, the bitmap string may indicate a resource set that is unavailable for DL ​​transmission using one bit per RE or one bit per RB. That is, one bit may be used for each RE and / or each RB in the bitmap string, where the bitmap string has a specific length that is determined according to the number of REs or RBs corresponding to the resource set that is unavailable for DL ​​transmission. Because the amount of resources reserved for the UL portion may be relatively large, the RE-level or RB-level granularity may result in a large amount of control signaling overhead.

[0156] In one aspect of the present disclosure, the scheduling entity 108 may provide a rate matching pattern with RBG-level granularity to the scheduled entity 106. With the RBG-level granularity, the amount of control signaling overhead at the scheduling entity 108 may be effectively reduced. That is, an RBG may include multiple RBs, so that using a bitmap to indicate bits used for an RBG rather than for an RB may effectively reduce the amount of control signaling overhead (e.g., by using fewer bits for each bitmap). In some examples, the rate matching pattern may be configured to utilize a combination of RBG-level granularity with RB-level or RE-level granularity to provide more or less granularity for portions of a timeslot having a particular timeslot format.

[0157] In another implementation example, the scheduled entity 106 may receive a rate matching pattern in a control message. In such an example, the control message may further identify the starting resource and the length of the resource using different granularity levels. Therefore, the rate matching pattern may provide a bitmap that identifies certain RBGs as corresponding to resources that are unavailable for DL ​​transmission, wherein the start and length indicators provide auxiliary or additional support for the scheduled entity 106 to identify a complete set of resources that are unavailable for DL ​​transmission. In an illustrative and non-limiting example, the scheduled entity 106 may determine a first portion of resources that are unavailable for DL ​​transmission using a rate matching pattern that specifies an RBG granularity level. In addition, the scheduled entity 106 may determine a second portion of resources that are unavailable for DL ​​transmission using start and length indicators with different granularity levels (e.g., RB granularity level, RE granularity level, etc.). The second portion may correspond to one or more adjacent GB portions that imply fewer resources than the UL portion, and therefore, the scheduled entity 106 may benefit from utilizing different granularity levels and / or benefit from utilizing a rate matching pattern to determine less than a complete set of resources that are unavailable for DL ​​transmission. In this way, the scheduled entity 106 can determine the complete set of resources that are unavailable for DL ​​transmission as including resources from both the first and second portions of resources determined to be unavailable for DL ​​transmission. Thus, the scheduled entity 106 can utilize the rate matching pattern and the start and length indicators to determine that the overlapping portion corresponds to resources that are unavailable for DL ​​transmission.

[0158] In any number of different implementation examples described herein, the scheduled entity 106 may determine that the rate matching pattern corresponds to an overlapping portion of the DL resource allocation, at least one GB adjacent to the overlapping portion of the DL resource allocation includes resources that are not available for DL ​​transmission, the resources identified in the control message correspond to the overlapping portion of the DL resource allocation, and / or the UL portion generally includes resources that are not available for DL ​​transmission. That is, based on any combination of one or more of the disclosed techniques, the scheduled entity 106 may determine a complete set of resources that are not available for DL ​​transmission. Of course, the scheduled entity 106 may determine to utilize a rate matching pattern to determine a complete set of resources that are not available for DL ​​transmission, wherein the rate matching pattern has an RBG level granularity as further described herein. The combination of techniques may depend on the specific application, time slot format, or other parameters.

[0159] In a given implementation, the scheduling entity 108 may configure the rate matching pattern on a per-serving cell basis (e.g., using the ServingCellConfig IE). In another example, the scheduling entity 108 may configure the rate matching pattern on a dynamic, per-bandwidth part (BWP) basis (e.g., using the PDSCH-Config IE).

[0160] In the frequency domain, the scheduling entity 108 may provide the rate matching frequency domain pattern as a bitmap, for example, one bit per RBG. In another example, the scheduling entity 108 may provide the rate matching frequency domain pattern based on the RBGs of the UL BWP. In some examples, the scheduling entity 108 may indicate the rate matching pattern using one or more RBGs.

[0161] In the time domain, the scheduling entity 108 may provide the rate matching time domain pattern as a bitmap, for example, one bit per OFDM symbol (e.g., utilizing 14 bits per time slot, or 7 bits per mini-time slot, etc.). In another example, the scheduling entity 108 may provide the rate matching time domain pattern according to a periodicity and pattern. For example, the scheduling entity 108 may provide N bits mapped to N time slots to the scheduled entity 106. In such an example, the scheduling entity 108 may use "1" to, for example, indicate a time slot utilizing the indicated time domain pattern.

[0162] At block 1506, the scheduled entity 106 may receive a type 1 DL grant message for the time slot. In one example, the scheduled entity 106 may receive a DL resource allocation for the time slot from the scheduling entity 108. The scheduled entity 106 may receive the grant because there are multiple RBs or REs (related to different frequency portions of the time slot) that the scheduled entity 106 may consider (e.g., by determining processing) or otherwise ignore (e.g., disregard, forgo processing, omit, discard, exclude, etc.) according to one or more of the various techniques of this disclosure.

[0163] At block 1508, the scheduled entity 106 may determine whether the DL grant message overlaps (e.g., partially or completely) in frequency with resources designated as unavailable for DL ​​transmission. In one example, the scheduled entity 106 may determine whether any portion of the DL resource allocation for the time slot (e.g., the DL grant message) overlaps with resources designated as unavailable for DL ​​communication (e.g., via an SBFD wireless carrier). Alternatively, as described above, when communicating via a wireless carrier, the scheduled entity 106 may make this determination by ignoring any portion of the DL grant message that overlaps with resources designated as unavailable for DL ​​communication. In one example, block 1508 may represent optional items (e.g., descriptive items, or assumed fact items for specific communications for example illustration). In one example, an item may be shown for illustrative purposes, indicating that there may be overlapping portions in some cases. This block 1508 may be further shown as being included in an example flow chart to indicate how one or more of the various techniques of the present disclosure may be applied to resolve certain DL information related to overlapping portions. As described herein, the techniques of the present disclosure address certain DL information related to overlapping portions in a manner that seeks to avoid portions of DL transmissions from interfering with portions of UL transmissions when the scheduled entity 106 is communicating with the scheduling entity 108 utilizing a particular wireless carrier.

[0164] If the DL grant message overlaps with resources designated as unavailable for DL ​​transmission, at block 1510, the scheduled entity 106 may ignore REs located within the overlapping portion of the DL grant message. In this way, the scheduled entity 106 may ignore information of the DL grant message corresponding to the UL portion of the time slot. In one example, the scheduled entity 106 may communicate over the SBFD wireless carrier using the time slot while ignoring (e.g., disregarding, abandoning processing, omitting, discarding, excluding, etc.) REs received in the overlapping portion of the DL grant message (e.g., information related to the overlapping portion). That is, the scheduled entity 106 may communicate over the wireless carrier using the time slot format (e.g., using a time slot on a carrier configured according to the time slot format) while ignoring information related to (e.g., falling within) the overlapping portion.

[0165] If there is no such overlap (i.e., no overlapping portion), then at block 1512, the scheduled entity 106 can utilize the resources allocated in the DL grant message and can receive and process the corresponding REs. In such an example, the scheduled entity 106 can communicate over the wireless carrier using the time slot format while also utilizing all resources of the type 1 DL resource allocation for the time slot in such a case. That is, the scheduled entity 106 can utilize all information corresponding to the REs allocated in the DL grant message while ignoring the REs located in any portion of the DL grant message because the overlapping portion creates a conflict between the time slot format and the DL resource allocation.

[0166] Indicator of unavailable resource set for downlink (DL)

[0167] Fig.16 1 is a flow chart illustrating an example process 1600 for dynamically indicating a set of preconfigured resources that are unavailable for downlink (DL) transmissions according to some aspects of the present disclosure. As described herein, certain implementations may omit some or all of the illustrated features, and some of the illustrated features may not be required to implement all embodiments. In some examples, Fig.10 The scheduling entity 1000 shown in and / or Fig.11 The scheduled entity 1100 shown in FIG. 1600 may be configured to perform the process 1600. In some examples, the process 1600 may be performed by any suitable device or component for performing the functions or algorithms described herein.

[0168] At block 1602, a scheduled entity 106 (e.g., a UE) may receive information defining resource sets that may be dynamically made unavailable for DL ​​transmission. In one example, a scheduling entity 108 (e.g., a BS) may provide information to the scheduled entity 106 defining those resources that the scheduling entity 108 may dynamically make unavailable for DL ​​transmission (e.g., for PDSCH) when utilizing SBFD. In this way, the scheduled entity 106 may determine one or more resource sets that are configured to be dynamically made unavailable or available for DL ​​transmission. That is, the scheduled entity 106 may receive one or more resource sets from the scheduling entity 108, which indicates the one or more resource sets as being configured to be dynamically made available and unavailable in a time slot for DL ​​communication.

[0169] At block 1604, the scheduled entity 106 may determine a slot format for one or more time slots. In one example, the scheduled entity 106 may receive an indication or configuration message from the scheduling entity 108 sufficient for the scheduled entity 106 to determine the slot format for a given time slot. The indication or configuration message may identify a UL portion of the time slot (e.g., a first frequency portion) and at least one DL portion of the time slot (e.g., a second frequency portion). In some examples, the slot format configuration may indicate a set of resources that may be dynamically made available for DL ​​transmission.

[0170] At block 1606, the scheduled entity 106 may receive a dynamic indication that one or more resource sets are unavailable for DL ​​transmission. In one example, the scheduling entity 108 may dynamically indicate activation of the one or more resource sets identified at block 1602 (e.g., by sending an appropriate DCI or MAC-CE to the scheduled entity 106). When the scheduled entity 106 receives the dynamic indication from the scheduling entity 108, the scheduled entity 106 may then designate the set of resources (e.g., of preconfigured resource sets) as unavailable for DL ​​transmission. In some examples, the scheduling entity 108 and the scheduled entity 106 may utilize such a dynamic indication signal when the scheduling entity 108 and the scheduled entity 106 accept that a particular DL transmission (e.g., an SSB) may overlap with some or all of the UL portion of the time slot. That is, the dynamic indication may be useful even if there is overlap with the UL portion on the wireless carrier, such as when the scheduling entity 108 is to transmit the SSB over the carrier.

[0171] At block 1608, the scheduled entity 106 may receive a type 1 DL grant message for the time slot. In one example, the scheduled entity 106 may receive a DL resource allocation for the time slot from the scheduling entity 108. The scheduled entity 106 may receive the grant because there are multiple RBs or REs (e.g., related to different frequency portions of the time slot) that the scheduled entity 106 may consider (e.g., by determining processing) or otherwise ignore (e.g., disregard, forgo processing, omit, discard, exclude, etc.) according to one or more of the various techniques of this disclosure.

[0172] At block 1610, the scheduled entity 106 may determine whether the DL grant message overlaps (e.g., partially or completely) in frequency with resources designated as unavailable for DL ​​transmission. In one example, the scheduled entity 106 may determine whether any portion of the DL resource allocation for the time slot (e.g., the DL grant message) overlaps with resources designated as unavailable for DL ​​communication (e.g., by an SBFD wireless carrier). Alternatively, as described above, when communicating via a wireless carrier, the scheduled entity 106 may make this determination by ignoring any portion of the DL grant message that overlaps with resources designated as unavailable for DL ​​communication. In one example, block 1619 may represent an optional item (e.g., a descriptive item, or an assumed fact item for a particular communication illustrated in an example). In one example, an item may be shown for illustrative purposes, thereby indicating that there may be overlapping portions in some cases. This block 1610 may be further shown as being included in an example flow chart to indicate how one or more of the various techniques of the present disclosure may be applied to resolve certain DL information related to overlapping portions. As described herein, the techniques of the present disclosure address certain DL information related to overlapping portions in a manner that seeks to avoid portions of DL transmissions from interfering with portions of UL transmissions when the scheduled entity 106 is communicating with the scheduling entity 108 utilizing a particular wireless carrier.

[0173] If the DL grant message overlaps with resources designated as unavailable for DL ​​transmission, at block 1612, the scheduled entity 106 may ignore REs located within the overlapping portion of the DL grant message. In this way, the scheduled entity 106 may ignore information of the DL grant message corresponding to the UL portion of the time slot. In one example, the scheduled entity 106 may communicate over the SBFD wireless carrier using the time slot while ignoring (e.g., disregarding, abandoning processing, omitting, discarding, excluding, etc.) REs received in the overlapping portion of the DL grant message (e.g., information related to the overlapping portion). That is, the scheduled entity 106 may communicate over the wireless carrier using the time slot format (e.g., using a time slot on a carrier configured according to the time slot format) while ignoring information related to (e.g., falling within) the overlapping portion.

[0174] If there is no such overlap (i.e., no overlapping portion), then at block 1614, the scheduled entity 106 can utilize the resources allocated in the DL grant message and can receive and process the corresponding REs. In such an example, the scheduled entity 106 can communicate over the wireless carrier using the time slot format while also utilizing all resources of the type 1 DL resource allocation for the time slot in such a case. That is, the scheduled entity 106 can utilize all information corresponding to the REs allocated in the DL grant message while ignoring the REs located in any portion of the DL grant message because the overlapping portion creates a conflict between the time slot format and the DL resource allocation.

[0175] Although generally described with reference to the various figures, the present teachings are not limited thereto. Scheduled entities 106 may communicate via wireless carriers using a time slot format while scheduling based on, for example, reference Figures 12 to 16 Any combination of one or more of the described techniques may be used to ignore information related to the overlapping portions.

[0176] Fig.17 1 is a schematic diagram of sub-band full duplex (SBFD) communications including an overlap (in frequency) between uplink (UL) and downlink (DL) communications. In this example, the overlap causes a conflict that the scheduled entity 106 is configured to identify and / or resolve according to one or more of the various techniques of the present disclosure. In one example, the scheduled entity 106 (e.g., UE) may use a reference Figures 12 to 16 Any one or more of the techniques described to identify overlaps.

[0177] As shown, the overlapping portion is between the UL and DL frequency portions of the time slot for the SBFD carrier 1702. In the example shown, the DL frequency portions 1704A and 1704B of the time slot and the UL frequency portion 1706 of the time slot are separated in frequency from each other in some non-overlapping portions of the time slot. However, the DL resource allocations in this example at least partially overlap with the UL frequency portion 1706, as conceptually shown, where at least some of the DL frequency portions 1704A overlap with the UL frequency portion 1706, thereby affecting or implying resources designated as unavailable for DL ​​transmission. In accordance with any one or more of the various techniques of the present disclosure, the scheduled entity 106 may determine to ignore any DL data related to the scheduled entity 106 determining its DL resource allocations in the overlapping portion (e.g., based on references such as Figures 12 to 16In this way, the scheduled entity 106 can communicate via the SBFD carrier 1702 using the time slot while ignoring any information related to the overlapping portion of the DL frequency portion 1704A. In addition, the scheduled entity 106 can process any information related to the non-overlapping portion, such as all information related to the DL frequency portion 1704B and at least some resource elements (REs) of the DL frequency portion 1704A that do not overlap with the UL frequency portion 1706.

[0178] In such a case, the scheduled entity 106 may ignore information related to the overlapping portion of the DL frequency portion 1704A and the UL frequency portion 1706. In this way, the scheduled entity 106 may provide UL transmissions in the UL frequency portion 1706, including using a bandwidth part (BWP) related to the overlapping portion of the UL frequency portion 1706, while not compromising the integrity of UL transmissions in other overlapping portions.

[0179] In this example, the slot format may be such that a guard period (GP) may be further located between the UL frequency portion 1706 and the DL frequency portion 1704A, which may also be in the overlapping portion. In such a case, the scheduled entity 106 may ignore the portion of the DL 1704A that overlaps the GP between the UL frequency portion 1706 and the DL frequency portion 1704A, in accordance with one or more of the various techniques of the present disclosure. In some examples, the carriers shown may represent portions of a carrier (e.g., a hybrid bandwidth portion (BWP) of a carrier) or an entire carrier, depending on the implementation.

[0180] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for resolving conflicts between downlink (DL) resource allocations (eg, using Type 1 DL resource allocations) and resources in a time slot designated as unavailable for DL ​​transmissions.

[0181] The following description provides an example of a user equipment (UE) and a scheduling entity that coordinates which information the UE is to process based on the position where the information appears in the time slot relative to other parts in the time slot, and does not limit the scope, applicability, or examples set forth in the claims. Without departing from the scope of the present disclosure, changes may be made to the functions and arrangements of the elements discussed. Various examples may omit, replace, or add various programs or components when appropriate. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. In addition, the features described in conjunction with some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functions, or structures and functions in addition to the various aspects of the present disclosure set forth herein, or such devices or methods that are practiced using other structures, functions, or structures and functions that are different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosed technology may be embodied by one or more elements of the claims.

[0182] The present disclosure provides several mechanisms and algorithms for resolving potential conflicts that may arise with DL frequency domain resource allocation (FDRA) type 1 in sub-band full duplex (SBFD), where the allocated DL resources overlap with resources that the slot format has designated for uplink (UL) communications. Although described with reference to DL resource allocation type 1, in some examples throughout the present disclosure, the present disclosure is not limited thereto, and one of ordinary skill in the art will appreciate that one or more of the techniques of the present disclosure may also be applied to other wireless carriers or other resource allocation types (e.g., UL resource allocation, non-type 1 resource allocation, SL resource allocation, etc.).

[0183] In one illustrative and non-limiting example, a group of UEs may communicate via a sidelink (SL) utilizing the techniques of the present disclosure, wherein in such an example, a first UE may operate as a scheduling entity and another UE may operate as a scheduled entity, thereby enabling the group of UEs to exchange information that allows identification of resources in overlapping portions, the information relating to frequency portions allocated for SL communications in a first direction relative to the first UE (e.g., at least one first bandwidth portion (BWP)) and frequency portions allocated for SL communications in a second direction relative to the first UE (e.g., at least one second bandwidth portion (BWP)). In some cases, these directions may be likened to DL communications / directions and UL communications / directions to determine when there may be a conflict between communications in different directions.

[0184] In one example, when utilizing type 1 DL resource allocations, conflicts may arise between DL resource allocations and time slot formats. Accordingly, the scheduling entity 108 may indicate unavailable resource sets in the form of bitmaps. These bitmaps, when used in this manner, may be quite large and may generate significant overhead if not used in a restricted manner (e.g., by using one bit per resource block group (RBG) for RBG-level granularity rate matching). Accordingly, one or more of the various techniques of the present disclosure resolve such conflicts by determining whether portions of a DL resource allocation overlap with certain resources of a time slot that is designated as unavailable for DL ​​transmission (configured and / or dynamically indicated), and then ignoring (e.g., disregarding) information included in those overlapping portions while communicating over a wireless carrier using the time slot format.

[0185] In some aspects, the present disclosure provides apparatus, methods, processing systems, and computer-readable media for determining that an overlapping portion includes resources that are unavailable for DL ​​transmission. The present disclosure provides multiple examples and processes, which, for example, describe how a scheduled entity can determine that such an overlapping portion consists of resources that are unavailable for DL ​​transmission. Although described with reference to different figures, in some cases, a scheduled entity can employ one or a combination of such processes to facilitate communication through an SBFD wireless carrier. Other aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for communicating through a wireless carrier using a time slot format while ignoring (e.g., disregarding) information related to the overlapping portion.

[0186] Scheduling Entity

[0187] Fig.10 1004. The scheduling entity 1000 may be a processor 1004, as described herein, for example, with reference to FIG. Figure 1 , Figure 2 and / or Figure 4 The scheduling entity 1000 may be an example of a scheduling entity 108 (eg, a BS). Figure 1 , Figure 2 and / or Figure 4 For example, the scheduling entity 1000 may be a BS as shown in any one or more of the figures. Figure 1 and / or Figure 2 A user equipment (UE) is described.

[0188] The scheduling entity 1000 includes a processing system 1014 having one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, the scheduling entity 1000 can be configured to perform any one or more of the functions described herein. That is, the processor 1004 utilized in the scheduling entity 1000 can be configured (e.g., in conjunction with the memory 1005 and the transceiver 1010) to implement the functions described herein and as described herein. Figures 12 to 17 Any one or more of the processes and procedures shown in .

[0189] In this example, the processing system 1014 can be implemented with a bus architecture generally represented by bus 1002. Depending on the specific application and overall design constraints of the processing system 1014, the bus 1002 may include any number of interconnecting buses and bridges. The bus 1002 communicatively couples various circuits including one or more processors (generally represented by processor 1004), memory 1005, and computer-readable media (generally represented by computer-readable media 1006). The bus 1002 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and are not described in detail. The bus interface 1008 provides an interface between the bus 1002 and the transceiver 1010. The transceiver 1010 provides a communication interface or component for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1012 (e.g., a keypad, a display, a speaker, a microphone, a joystick) may also be provided. Of course, such a user interface 1012 is optional, and some examples (such as base stations) may omit it.

[0190] In some aspects of the present disclosure, the processor 1004 may include a timeslot formatting circuit 1040, which is configured (e.g., in cooperation with the memory 1005 and the transceiver 1010) for various functions, including, for example, determining a timeslot format and transmitting it to one or more scheduled entities 106, including a corresponding portion of a timeslot for UL communication, for DL ​​communication, or in some examples, resources that can be flexibly allocated for UL or DL ​​communication. The processor 1004 may further include a resource scheduling circuit 1042, which is configured (e.g., in cooperation with the memory 1005 and the transceiver 1010) for various functions, including, for example, determining a DL resource allocation (e.g., a grant message) for one or more wireless carriers (e.g., for one or more timeslots) and transmitting it to one or more scheduled entities 106.

[0191] The processor 1004 is responsible for managing the bus 1002 and general processing, including the execution of software stored on the computer-readable medium 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described herein for any particular device. The processor 1004 may also use the computer-readable medium 1006 and the memory 1005 to store data that the processor 1004 manipulates when executing the software.

[0192] One or more processors 1004 in the processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other. Software can reside on computer-readable media 1006. Computer-readable media 1006 can be non-temporary computer-readable media. As an example, non-temporary computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks and any other suitable for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 1006 may reside in the processing system 1014, reside external to the processing system 1014, or be distributed among multiple entities including the processing system 1014. The computer readable medium 1006 may be embodied in a computer program product. As an example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0193] In one or more examples, the computer-readable storage medium 1006 can store computer-executable code including time slot formatting instructions 1052 that configure the scheduling entity 1000 for various functions. For example, the time slot formatting instructions 1052 can be configured to enable the scheduling entity 1000 to implement the combination of Figures 12 to 17One or more functions described include, for example, block 1202, determining a time slot format for a time slot on a SBFD wireless carrier, determining a UL frequency portion of a time slot, determining a resource of a time slot indicated as unavailable for DL ​​transmission, determining that the UL portion is unavailable for DL ​​transmission, etc. The computer-readable storage medium 1006 may store computer-executable code including resource scheduling instructions 1054 that configure the scheduling entity 1000 for various functions including, for example, receiving a type 1 DL resource allocation, determining that the DL resource allocation has a portion that overlaps with a portion of the time slot that is unavailable for DL ​​transmission, and facilitating communication over the SBFD wireless carrier while ignoring (e.g., disregarding) information received via the DL resource allocation regarding the overlapping portion.

[0194] The foregoing description is provided to enable any person skilled in the art to practice various functions, including, for example, facilitating wireless communications between a scheduling entity 108 and a scheduled entity 106 while reducing overhead and overlap between UL and DL communications on an SBFD wireless carrier utilizing a DL Type 1 FDRA using limited signaling exchanged between the entities.

[0195] Of course, in the examples disclosed herein, the circuits included in the processor 1004 are provided only as examples, and other components for performing the functions described may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1006, or in Figures 1 to 4 any of the figures described herein and using, for example, Figures 12 to 17 Any other suitable means or components of the described processes and / or algorithms.

[0196] Scheduled Entity

[0197] Fig.11 1 is a block diagram conceptually illustrating an example of a hardware implementation for an exemplary scheduled entity 1100 employing a processing system 1114. According to various aspects of the present disclosure, the processing system 1114 may include an element, or any portion of an element, or any combination of elements having one or more processors 1104. The scheduled entity 1100 may be, for example, as described herein with reference to Figure 1 and / or Figure 2 An example of a scheduled entity 106 (eg, UE) is described.

[0198] The scheduled entity 1100 includes a processing system 1114 having one or more processors 1104. The processing system 1114 may be associated with Fig.10The processing system 1014 shown is substantially the same, including a bus interface 1108, a bus 1102, a memory 1105, a processor 1104, and a computer readable medium 1106. In addition, the scheduled entity 1100 may include the same Fig.10 The user interface and transceiver described herein may be substantially similar to the user interface 1112 and the transceiver 1110. That is, the processor 1104 utilized in the scheduled entity 1100 may be configured (e.g., in conjunction with the memory 1105 and the transceiver 1110) to implement the methods described herein and as described herein. Figures 12 to 17 Any one or more of the processes shown in .

[0199] In some aspects of the present disclosure, the processor 1104 may include a resource overlap determination circuit 1140 that is configured (e.g., in cooperation with the memory 1105 and the transceiver 1110) for various functions, including, for example, determining that a DL resource allocation overlaps at least partially in frequency (e.g., completely / partially) with a portion of a time slot that the time slot format indicates is used for UL communication, and determining that the overlapping portion consists of resources that are not available for DL ​​transmission. For example, the resource overlap determination circuit 1140 may be configured (e.g., in cooperation with the memory 1105 and the transceiver 1110) for various functions, including, for example, in conjunction with Figures 12 to 17 Processor 1104 may further include communication circuitry 1142 that is configured (eg, in conjunction with memory 1105 and transceiver 1110) for various functions, including, for example, communicating over a wireless air interface (eg, via one or more wireless carriers).

[0200] And further, the computer-readable storage medium 1106 may store computer-executable code including resource overlap determination instructions 1152 that will configure the scheduling entity 1100 (e.g., in conjunction with the memory 1105 and the transceiver 1110) for various functions, including, for example, in conjunction with Figures 12 to 17 The computer-readable storage medium 1106 may further store computer-executable code including communication instructions 1154 that configure the scheduling entity 1100 (e.g., in conjunction with the memory 1105 and the transceiver 1110) for various functions, including, for example, communicating over a wireless air interface (e.g., communicating over a wireless carrier using one or more time slots having one or more time slot formats).

[0201] In one configuration, a scheduled entity 1100 for wireless communication includes means for determining a slot format for a slot on a SBFD wireless carrier, means for determining that a DL resource allocation for the slot has an overlap portion in which at least a portion of the DL resource allocation overlaps with a UL portion, means for determining that the UL portion has resources indicated as unavailable for DL ​​transmission, and means for communicating over the SBFD wireless carrier using the slot format while ignoring (e.g., disregarding, discarding, etc.) certain information related to REs in the overlap portion. In one aspect, the above means may be Fig.11 The processing system 1114 is shown configured to perform the functions listed by the above-mentioned means. In another aspect, the above-mentioned means may be a circuit or any apparatus configured to perform the functions listed by the above-mentioned means.

[0202] Of course, in the examples disclosed herein, the circuits included in the processor 1104 are provided only as examples, and other components for performing the functions described may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1106, or in Figures 1 to 4 any of the figures described herein and using, for example, Figures 12 to 17 Any other suitable device or component of the described process and / or algorithm.In any case, the preceding description is provided to enable any person skilled in the art to practice the various aspects described herein.

[0203] Other examples with various characteristics:

[0204] Example 1: A method, apparatus, system, and non-transitory computer-readable medium for: receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink communications and a second frequency portion of the time slot for downlink communications; receiving a downlink resource allocation for the time slot, the downlink resource allocation including an overlapping portion, wherein at least a portion of the downlink resource allocation overlaps with at least a portion of the first frequency portion of the time slot for uplink communications; determining that the overlapping portion consists of resources that are unavailable for downlink transmission; and communicating over a wireless carrier using the time slot while ignoring information received in the overlapping portion.

[0205] Example 2: The method, apparatus, system, and non-transitory computer-readable medium according to Example 1 further include receiving a control message identifying resources in a time slot corresponding to a first frequency portion of the time slot for uplink communication, wherein determining that the overlapping portion consists of resources that are unavailable for downlink transmission includes determining that the resources identified in the control message correspond to the overlapping portion.

[0206] Example 3: The method, apparatus, system, and non-transitory computer-readable medium of Examples 1 to 2, wherein the control message includes a starting resource and a resource length of resources that are unavailable for downlink transmission.

[0207] Example 4: A method, apparatus, system, and non-transitory computer-readable medium according to Examples 1 to 3, wherein determining that the overlapping portion consists of resources unavailable for downlink transmission includes an indication that the first frequency portion of the received time slot for uplink communication is at least a portion of the resources unavailable for downlink transmission.

[0208] Example 5: The method, apparatus, system, and non-transitory computer-readable medium of Examples 1 to 4, further comprising receiving an indication that at least one guard band adjacent to the overlapping portion is also part of the resources unavailable for downlink transmission.

[0209] Example 6: The method, apparatus, system, and non-transitory computer-readable medium of Examples 1 to 5, wherein determining that the overlapping portion consists of resources unavailable for downlink transmission includes determining that the overlapping portion corresponds to a first frequency portion of the time slot used for uplink communication.

[0210] Example 7: The methods, devices, systems, and non-transitory computer-readable media according to Examples 1 to 6 also include receiving a rate matching pattern corresponding to a first frequency portion of a time slot for uplink communication, the rate matching pattern having a resource block group (RBG) level granularity, wherein determining that the overlapping portion is composed of resources that are unavailable for downlink transmission includes determining that the rate matching pattern corresponds to the overlapping portion.

[0211] Example 8: The methods, devices, systems and non-transitory computer-readable media according to Examples 1 to 7 further include: receiving information defining one or more resource sets that can be dynamically made available for downlink transmission; and receiving a dynamic indication in a time slot that the defined one or more resource sets are unavailable for downlink transmission, wherein determining that the overlapping portion consists of resources that are unavailable for downlink transmission includes determining that the overlapping portion is at least a portion of the defined one or more resource sets.

[0212] Example 9: A method, apparatus, system, and non-transitory computer-readable medium for: receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication; receiving a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion in which the DL resource allocation at least partially overlaps with the first frequency portion; determining that the overlapping portion includes resources that are unavailable for DL ​​transmission; and communicating over a wireless carrier using the time slot while ignoring (e.g., disregarding) information related to the overlapping portion.

[0213] Example 10: The method, apparatus, system, and non-transitory computer-readable medium according to Example 9 further includes receiving a control message identifying resources corresponding to the first frequency portion, wherein determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: determining that the resources identified in the control message correspond to the overlapping portion.

[0214] Example 11: The method, apparatus, system, and non-transitory computer-readable medium of Examples 9 to 10, wherein the control message includes: a starting resource and a length corresponding to resources that are unavailable for DL ​​transmission.

[0215] Example 12: The method, apparatus, system, and non-transitory computer-readable medium of Examples 9 to 11, wherein determining that the overlapping portion includes resources unavailable for DL ​​transmission comprises receiving an indication that the first frequency portion includes resources unavailable for DL ​​transmission.

[0216] Example 13: The method, apparatus, system, and non-transitory computer-readable medium of Examples 9 to 12, wherein determining that the overlapping portion includes resources that are unavailable for DL ​​transmission further comprises determining that at least one guard band adjacent to the overlapping portion includes resources that are unavailable for DL ​​transmission.

[0217] Example 14: The method, apparatus, system, and non-transitory computer-readable medium of Examples 9 to 13, wherein determining that the overlapping portion includes resources that are unavailable for DL ​​transmission comprises determining that the overlapping portion corresponds to the first frequency portion.

[0218] Example 15: The methods, devices, systems, and non-transitory computer-readable media according to Examples 9 to 14 further include receiving a rate matching pattern corresponding to a first frequency portion, the rate matching pattern having a resource block group (RBG) level granularity, wherein determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: determining that the rate matching pattern corresponds to the overlapping portion.

[0219] Example 16: The methods, apparatus, systems, and non-transitory computer-readable media of Examples 9 to 15 further include: receiving information defining one or more resource sets configured to dynamically make them unavailable for DL ​​transmission; and receiving an indication that one or more resource sets are unavailable for DL ​​transmission, wherein determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: determining that the overlapping portion includes one or more resource sets.

[0220] Example 17: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication operable at a user equipment (UE), comprising: receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication; receiving a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion in which the DL resource allocation at least partially overlaps with the first frequency portion; and communicating over a wireless carrier using the time slot while ignoring information related to the overlapping portion.

[0221] Example 18: The method, apparatus, system, and non-transitory computer-readable medium of Example 17, wherein communicating over the wireless carrier while ignoring information related to the overlapping portion comprises determining that the overlapping portion of the DL resource allocation includes resources that are unavailable for DL ​​transmission.

[0222] Example 19: The methods, devices, systems and non-transitory computer-readable media according to Examples 17 to 18 further include: receiving a control message identifying a resource set that is unavailable for DL ​​transmission, wherein the control message includes: a starting resource of the resource set and a length corresponding to the resource set that is unavailable for DL ​​transmission, and wherein communicating through a wireless carrier while ignoring information related to the overlapping portion includes: determining that the overlapping portion of the DL resource allocation includes a resource set that is unavailable for DL ​​transmission.

[0223] Example 20: The methods, devices, systems, and non-transitory computer-readable media of Examples 17 to 19 further include: receiving an indication that the first frequency portion includes resources that are unavailable for DL ​​transmission, and wherein communicating over the wireless carrier while ignoring information related to the overlapping portion includes: determining that the overlapping portion of the DL resource allocation includes one or more resources of the first frequency portion.

[0224] Example 21: The method, apparatus, system, and non-transitory computer-readable medium of Examples 17 to 20, wherein communicating over the wireless carrier while ignoring information related to the overlapping portion comprises: determining that at least one guard band adjacent to the overlapping portion includes resources that are unavailable for DL ​​transmission. And determining that the overlapping portion includes one or more resources of the at least one guard band.

[0225] Example 22: The method, apparatus, system, and non-transitory computer-readable medium of Examples 17 to 21, wherein communicating over a wireless carrier while ignoring information related to the overlapping portion includes determining that the overlapping portion corresponds to one or more resources of the first frequency portion.

[0226] Example 23: The methods, devices, systems, and non-transitory computer-readable media of Examples 17 to 22 further include: receiving a rate matching pattern corresponding to a first frequency portion, the rate matching pattern having a resource block group (RBG) level granularity, and wherein communicating over a wireless carrier while ignoring information related to the overlapping portion includes: determining that the overlapping portion corresponds to the rate matching pattern.

[0227] Example 24: The methods, devices, systems, and non-transitory computer-readable media of Examples 17 to 23 further include: receiving information defining one or more resource sets configured to dynamically make them unavailable for DL ​​transmission; and receiving an indication that one or more resource sets are unavailable for DL ​​transmission, wherein communicating over a wireless carrier while ignoring information related to the overlapping portion includes: determining that the overlapping portion includes one or more resource sets.

[0228] Example 25: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication operable at a base station (BS), comprising: determining at least one first frequency portion of a time slot as available for uplink (UL) communication and determining at least one second frequency portion of the time slot as available for downlink (DL) communication, wherein at least one first frequency portion of the time slot is not available for DL ​​transmission; sending information indicating at least one first frequency portion of the time slot and at least one second frequency portion of the time slot; sending a DL resource allocation to a user equipment (UE), the DL resource allocation including an overlapping portion in which the DL resource allocation at least partially overlaps with the at least one first frequency portion of the time slot; and communicating with the UE via a wireless carrier using the time slot.

[0229] Example 26: The method, apparatus, system, and non-transitory computer-readable medium of Example 25, wherein the wireless carrier comprises a sub-band full-duplex (SBFD) wireless carrier.

[0230] Example 27: The method, apparatus, system, and non-transitory computer-readable medium of Examples 25 to 26, wherein at least one first frequency portion corresponds to a first bandwidth portion (BWP) and at least one second frequency portion corresponds to a second bandwidth portion (BWP).

[0231] Example 28: A method, apparatus, system, and non-transitory computer-readable medium according to Examples 25 to 27, wherein sending information indicating at least one first frequency portion of a time slot and at least one second frequency portion of a time slot includes: sending a control message identifying a set of resources that are unavailable for DL ​​transmission, the resource set corresponding to at least one first frequency portion of a time slot.

[0232] Example 29: The method, apparatus, system, and non-transitory computer-readable medium of Example 28, wherein the control message comprises: a starting resource of the resource set and a length corresponding to the resource set that is unavailable for DL ​​transmission.

[0233] Example 30: The method, apparatus, system, and non-transitory computer-readable medium of Examples 25 to 29, wherein the DL resource allocation comprises a type 1 DL resource allocation.

[0234] Example 31: A method, apparatus, system, and non-transitory computer-readable medium according to Examples 25 to 30, wherein sending information indicating at least one first frequency portion of a time slot and at least one second frequency portion of a time slot includes: sending at least one first frequency portion including an indication of resources that are unavailable for DL ​​transmission.

[0235] Example 32: A method, apparatus, system, and non-transitory computer-readable medium according to Example 31, wherein at least one first frequency portion includes an indication of resources that are unavailable for DL ​​transmission, including at least one guard band portion adjacent to the at least one first frequency portion including at least a portion of the resources that are unavailable for DL ​​transmission.

[0236] Example 33: An apparatus for wireless communication, comprising: a component for receiving information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication; a component for receiving a DL resource allocation for the time slot, the DL resource allocation including an overlapping portion in which the DL resource allocation at least partially overlaps with the first frequency portion; a component for determining that the overlapping portion includes resources that are unavailable for DL ​​transmission; and a component for communicating over a wireless carrier using the time slot while ignoring information related to the overlapping portion.

[0237] Example 34: The apparatus according to Example 33 further includes: a component for receiving a control message identifying resources corresponding to the first frequency portion, wherein the component for determining that the overlapping portion includes resources unavailable for DL ​​transmission includes: a component for determining that the resources identified in the control message correspond to the overlapping portion.

[0238] Example 35: The apparatus of Examples 33 to 34, wherein the control message comprises: a starting resource and a length corresponding to resources that are unavailable for DL ​​transmission.

[0239] Example 36: The apparatus of Examples 33 to 35, wherein the means for determining that the overlapping portion includes resources unavailable for DL ​​transmission comprises: means for receiving an indication that the first frequency portion includes resources unavailable for DL ​​transmission.

[0240] Example 37: The apparatus of Examples 33 to 36, wherein the means for determining that the overlapping portion includes resources unavailable for DL ​​transmission comprises: means for determining that at least one frequency band of the time slot includes resources unavailable for DL ​​transmission.

[0241] Example 38: An apparatus according to Examples 33 to 37, wherein the component for determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: a component for identifying that the first frequency portion includes resources that are unavailable for DL ​​transmission; and a component for determining that the overlapping portion corresponds to the first frequency portion.

[0242] Example 39: The apparatus of Examples 33 to 38 further includes: a component for receiving a rate matching pattern corresponding to the first frequency portion, the rate matching pattern having a resource block group (RBG) level granularity, wherein the component for determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: a component for determining that the rate matching pattern corresponds to the overlapping portion.

[0243] Example 40: The apparatus of Examples 33 to 39 further includes: a component for identifying one or more resource sets that are configured to dynamically make them unavailable for DL ​​transmission; and a component for receiving an indication that one or more resource sets are unavailable for DL ​​transmission, wherein the component for determining that the overlapping portion includes resources that are unavailable for DL ​​transmission includes: a component for determining that the overlapping portion includes one or more resource sets.

[0244] Example 41: A non-transitory computer-readable medium storing computer executable code, comprising instructions for causing a user equipment (UE) to: receive information indicating a time slot format, the information identifying a first frequency portion of the time slot for uplink (UL) communication and at least one other portion of the time slot for downlink (DL) communication; receive a DL resource allocation for the time slot, the DL resource allocation comprising an overlapping portion in which the DL resource allocation at least partially overlaps with the first frequency portion; determine that the overlapping portion includes resources that are unavailable for DL ​​transmission; and communicate using the time slot over a wireless carrier while ignoring information received in the overlapping portion.

[0245] Example 42: A non-transitory computer-readable medium according to Example 41, wherein the computer executable code also includes instructions for causing the UE to: receive a control message identifying resources corresponding to the first frequency portion, wherein in order for the UE to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission, the instructions are configured to cause the UE to: determine that the resources identified in the control message correspond to the overlapping portion.

[0246] Example 43: The non-transitory computer readable medium of Examples 41-42, wherein the control message comprises: a starting resource and a length corresponding to resources that are unavailable for DL ​​transmission.

[0247] Example 44: A non-transitory computer-readable medium according to Examples 41 to 43, wherein in order for the UE to determine that the overlapping portion includes resources unavailable for DL ​​transmission, the instructions are configured to cause the UE to: receive an indication that the first frequency portion includes resources unavailable for DL ​​transmission.

[0248] Example 45: The non-transitory computer-readable medium of Examples 41 to 44, wherein the computer-executable code further comprises instructions for causing the UE to: determine that at least one guard band adjacent to the overlapping portion includes resources that are unavailable for DL ​​transmission.

[0249] Example 46: The non-transitory computer-readable medium of Examples 41 to 45, wherein in order for the UE to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission, the instructions are configured to cause the UE to: determine that the overlapping portion corresponds to the first frequency portion.

[0250] Example 47: A non-transitory computer-readable medium according to Examples 41 to 46, wherein the computer executable code also includes instructions for causing the UE to: receive a rate matching pattern corresponding to a first frequency portion, the rate matching pattern having a resource block group (RBG) level granularity, wherein in order for the UE to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission, the instructions are configured to cause the UE to: determine that the rate matching pattern corresponds to the overlapping portion.

[0251] Example 48: A non-transitory computer-readable medium according to Examples 41 to 47, wherein the computer executable code also includes instructions for causing the UE to: receive information defining one or more resource sets that are configured to be dynamically made unavailable for DL ​​transmission; and receive an indication that one or more resource sets are unavailable for DL ​​transmission, wherein in order for the UE to determine that the overlapping portion includes resources that are unavailable for DL ​​transmission, the instructions are configured to cause the UE to: determine that the overlapping portion includes one or more resource sets.

[0252] The present disclosure presents several aspects of wireless communication networks with reference to exemplary implementations. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system. NR is an emerging wireless communication technology under development. As will be readily appreciated by those skilled in the art, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0253] For example, various aspects of the present disclosure may be implemented within systems defined by an organization named "3rd Generation Partnership Project" (3GPP) (e.g., LTE) and other organizations including Evolved Packet System (EPS) and / or Universal Mobile Telecommunications System (UMTS), and / or described in documents from the above organizations. Various aspects may also be extended to systems defined by an organization named 3rd Generation Partnership Project 2 (3GPP2) and / or described in documents from the above organizations. Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. It should be noted that the terms "network" and "system" are often used interchangeably.

[0254] In some examples, a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTTRA), which includes Wideband CDMA (WCDMA) and other variants. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as NR (e.g., 5G NR), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions of UMTS that use EUTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, UMB, and GSM are described in 3GPP documents.

[0255] This disclosure uses the word "exemplary" to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0256] The present disclosure uses the term "coupling" to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may be considered coupled to each other even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object has never been in direct physical contact with the second object. The present disclosure uses the terms "circuit" and "loop" broadly to include hardware implementations of electrical devices and conductors (electrical devices and conductors that are capable of performing the functions described in the present disclosure when connected and configured, without limiting the type of electronic circuits) and software implementations of information and instructions (information and instructions that are capable of performing the functions described in the present disclosure when executed by a processor).

[0257] Figures 1 to 17 One or more of the components, steps, features and / or functions shown in the drawings can be rearranged and / or combined into a single component, step, feature or function, or embodied in several components, steps or functions. Additional elements, components, steps and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 17 The apparatus, devices and / or components shown in the can be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein can also be effectively implemented in software and / or embedded in hardware.

[0258] The method disclosed herein includes one or more steps or actions to implement the method. These method steps and / or actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions can be modified without departing from the scope of the claims. It should be understood that the specific order or hierarchy of steps in the disclosed method is a diagram of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the method can be rearranged. The attached method claims present the elements of each step in an example order and are not meant to be limited to the specific order or hierarchy presented, except as specifically described therein.

[0259] The applicant provides this description to enable any person skilled in the art to practice the various aspects described herein. Those skilled in the art will easily recognize various modifications to these aspects, and the general principles defined herein can be applied to other aspects. The applicant does not intend to limit the claims to the various aspects shown herein, but to be given the full scope consistent with the language of the claims, wherein unless such a statement is explicitly made, the elements mentioned in the singular form are not intended to mean "one and only one", but "one or more". Unless otherwise explicitly stated, the present disclosure uses the term "some" to refer to one or more. The phrase "at least one" mentioned in the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover: a; b; c; a and b (ab); a and c (ac); b and c (bc); and a, b and c (abb), as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other order of a, b and c). As used herein, the term "determine" covers a variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information such as a reference signal), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0260] All structural and functional equivalents to the elements of various aspects described throughout the disclosure that are known or later known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims.

[0261] The various operations of the disclosed technology can be performed by any suitable components capable of performing the corresponding functions. The components may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors. Generally, where there are operations shown in the figures, these operations may have corresponding corresponding components plus functional components with similar numbers.

[0262] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and devices described herein without departing from the scope of the claims. The description of the disclosed technology is provided to enable those skilled in the art to practice the various aspects described herein. However, the claims are not intended to be limited to the various aspects shown herein, but to be given the full scope consistent with the language of the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects.

Claims

1. A method of wireless communication operable at a user equipment (UE), comprising: receiving information indicating a time slot format, the information identifying a first frequency portion of a time slot for uplink (UL) communications and at least one other frequency portion of the time slot for downlink (DL) communications, the first frequency portion and the at least one other frequency portion being on one wireless carrier; receiving a DL resource allocation for the time slot, the DL resource allocation comprising an overlapping portion where the DL resource allocation at least partially overlaps with the first frequency portion; as well as Communicating over the wireless carrier using the time slot format while ignoring information related to the overlapping portion.

2. The method according to claim 1, wherein: The communicating via the wireless carrier while ignoring the information related to the overlapping portion includes: The overlapping portion of the DL resource allocation is determined to include resources that are unavailable for DL ​​transmission.

3. The method according to claim 1, further comprising: receiving a control message identifying a resource set that is unavailable for DL ​​transmission, wherein the control message includes: a starting resource of the resource set and a length corresponding to the resource set that is unavailable for DL ​​transmission, and Wherein, performing the communication through the wireless carrier while ignoring the information related to the overlapping portion comprises: Determining the overlapping portion of the DL resource allocation includes the set of resources that are unavailable for DL ​​transmission.

4. The method according to claim 1, further comprising: receiving an indication that the first frequency portion includes resources unavailable for DL ​​transmission, and Wherein, performing the communication through the wireless carrier while ignoring the information related to the overlapping portion comprises: It is determined that the overlapping portion of the DL resource allocation includes one or more resources of the first frequency portion.

5. The method according to claim 1, wherein: The communicating via the wireless carrier while ignoring the information related to the overlapping portion includes: determining that at least one guard band adjacent to the overlapping portion includes resources that are unavailable for DL ​​transmission; and It is determined that the overlapping portion includes one or more resources of the at least one guard band.

6. The method according to claim 1, wherein: The communicating via the wireless carrier while ignoring the information related to the overlapping portion includes: It is determined that the overlapping portion corresponds to one or more resources of the first frequency portion.

7. The method according to claim 1, further comprising: receiving a rate matching pattern corresponding to the first frequency portion, the rate matching pattern having a resource block group (RBG) level granularity, and Wherein, performing the communication through the wireless carrier while ignoring the information related to the overlapping portion comprises: The overlapping portion is determined to correspond to the rate matching pattern.

8. The method according to claim 1, further comprising: receiving information defining one or more sets of resources configured to be dynamically made unavailable for DL ​​transmission; as well as receiving an indication that the one or more resource sets are unavailable for DL ​​transmission, Wherein, performing the communication through the wireless carrier while ignoring the information related to the overlapping portion comprises: It is determined that the overlapping portion includes the one or more resource sets.

9. A method of wireless communication operable at a base station BS, comprising: determining at least one first frequency portion of a time slot as available for uplink (UL) communications and determining at least one second frequency portion of the time slot as available for downlink (DL) communications, wherein the at least one first frequency portion of the time slot is not available for DL ​​communications, the at least one first frequency portion and the at least one second frequency portion being on one wireless carrier; sending information indicating a time slot format, the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot; sending a DL resource allocation to a user equipment UE, the DL resource allocation comprising an overlapping portion of the DL resource allocation at least partially overlapping with the at least one first frequency portion of the time slot; as well as Communicate with the UE via the wireless carrier using the time slot.

10. The method according to claim 9, wherein: The wireless carrier includes a sub-band full-duplex (SBFD) wireless carrier.

11. The method according to claim 9, wherein: The at least one first frequency portion corresponds to a first bandwidth portion BWP, and the at least one second frequency portion corresponds to a second bandwidth portion BWP.

12. The method according to claim 9, wherein: The sending of the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot comprises: A control message is sent identifying a set of resources that are unavailable for DL ​​transmission, the set of resources corresponding to the at least one first frequency portion of the time slot.

13. The method according to claim 12, wherein: The control message includes a starting resource of the resource set and a length corresponding to the resource set that is unavailable for DL ​​transmission.

14. The method according to claim 9, wherein: The DL resource allocation includes a Type 1 DL resource allocation.

15. The method according to claim 9, wherein: The sending of the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot comprises: Sending an indication that the at least one first frequency portion includes resources unavailable for DL ​​transmission.

16. The method according to claim 15, wherein: The indication that the at least one first frequency portion includes resources unavailable for DL ​​transmission comprises at least one guard band portion adjacent to the at least one first frequency portion including at least a portion of the resources unavailable for DL ​​transmission.

17. An apparatus for wireless communication, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory, communicatively coupled to the processor, Wherein, the processor and the memory are configured as follows: determining at least one first frequency portion of a time slot as available for uplink (UL) communications and determining at least one second frequency portion of the time slot as available for downlink (DL) communications, wherein the at least one first frequency portion of the time slot is not available for DL ​​communications, the at least one first frequency portion and the at least one second frequency portion being on one wireless carrier; transmitting, via the transceiver, information indicating a time slot format, the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot; sending a DL resource allocation to a user equipment UE, the DL resource allocation comprising an overlapping portion of the DL resource allocation at least partially overlapping with the at least one first frequency portion of the time slot; and Communicate with the UE via the wireless carrier using the time slot.

18. The device according to claim 17, wherein: The wireless carrier includes a sub-band full-duplex (SBFD) wireless carrier.

19. The device according to claim 17, wherein: The at least one first frequency portion corresponds to a first bandwidth portion BWP, and the at least one second frequency portion corresponds to a second bandwidth portion BWP.

20. The device according to claim 17, wherein: To transmit the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot, the processor and the memory are configured to: A control message is sent identifying a set of resources that are unavailable for DL ​​transmission, the set of resources corresponding to the at least one first frequency portion of the time slot.

21. The device according to claim 20, wherein: The control message includes a starting resource of the resource set and a length corresponding to the resource set that is unavailable for DL ​​transmission.

22. The device according to claim 21, wherein The DL resource allocation includes a Type 1 DL resource allocation.

23. The device according to claim 17, wherein: To transmit the information indicating the at least one first frequency portion of the time slot and the at least one second frequency portion of the time slot, the processor and the memory are configured to: Sending an indication that the at least one first frequency portion includes resources unavailable for DL ​​transmission.

24. The device according to claim 23, wherein: The indication that the at least one first frequency portion includes resources unavailable for DL ​​transmission comprises at least one guard band portion adjacent to the at least one first frequency portion including at least a portion of the resources unavailable for DL ​​transmission.

25. An apparatus for wireless communication, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory, communicatively coupled to the processor, Wherein, the processor and the memory are configured as follows: receiving information indicating a time slot format, the information identifying a first frequency portion of a time slot for uplink (UL) communications and at least one other frequency portion of the time slot for downlink (DL) communications, the first frequency portion and the at least one other frequency portion being on one wireless carrier; receiving, via the transceiver, a DL resource allocation for the time slot, the DL resource allocation comprising an overlapping portion where the DL resource allocation at least partially overlaps with the first frequency portion; as well as Communicating over the wireless carrier via the transceiver utilizing the time slot format while ignoring information related to the overlapping portion.

26. The device according to claim 25, wherein To communicate over the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: The overlapping portion of the DL resource allocation is determined to include resources that are unavailable for DL ​​transmission.

27. The device according to claim 25, wherein: The processor and the memory are further configured to: receiving a control message identifying a resource set that is unavailable for DL ​​transmission, wherein the control message comprises a start indication corresponding to a starting resource of the resource set and a length indication corresponding to the resource set that is unavailable for DL ​​transmission, and Wherein, in order to communicate through the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: Determining the overlapping portion of the DL resource allocation includes the set of resources that are unavailable for DL ​​transmission.

28. The device according to claim 25, wherein The processor and the memory are further configured to: receiving an indication that the first frequency portion includes resources that are unavailable for DL ​​transmission, and Wherein, in order to communicate through the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: It is determined that the overlapping portion of the DL resource allocation includes one or more resources of the first frequency portion.

29. The device according to claim 28, wherein The processor and the memory are further configured to: receiving, via the transceiver, an indication that at least one guard band adjacent to the overlapping portion includes resources that are unavailable for DL ​​transmission, and Wherein, in order to communicate through the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: It is determined that the overlapping portion includes one or more resources of the at least one guard band.

30. The device according to claim 25, wherein: To communicate over the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: It is determined that the overlapping portion corresponds to one or more resources of the first frequency portion.

31. The apparatus of claim 25, wherein: The processor is further configured to: receiving, via the transceiver, a rate matching pattern corresponding to the first frequency portion, the rate matching pattern comprising a resource block group (RBG) level granularity; as well as Wherein, in order to communicate through the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: The overlapping portion is determined to correspond to the rate matching pattern.

32. The apparatus of claim 25, wherein: The processor and the memory are further configured to: identifying one or more resource sets in the slotted format configured to dynamically make them available for DL ​​transmission; and receiving, via the transceiver, a dynamic indication that the one or more resource sets are unavailable for DL ​​transmission, Wherein, in order to communicate through the wireless carrier while ignoring the information related to the overlapping portion, the processor and the memory are configured to: It is determined that the overlapping portion includes the one or more resource sets.

33. An apparatus for wireless communication, comprising means for performing the method of any one of claims 1-8.

34. An apparatus for wireless communication, comprising means for performing the method of any one of claims 9-16.

35. A non-transitory computer readable medium having stored thereon instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1-16.

36. A program product comprising instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1-16.

Images