Method and apparatus for a hybrid automatic repeat request process for subband full-duplex.

Abstract

A UE can identify time slots to transmit and / or receive information related to one or more HARQ procedures in a frame structure that includes both subband full-duplex time slot types and time-division duplex time slot types. Based on a first time slot used for control information, the UE can identify a second time slot for PUSCH or PDSCH communication based on an offset between a first and a second time slot determined by calculating a time slot offset (e.g., based on parameters received from a base station). In some aspects, the UE can exclude certain time slot duplex types (e.g., SBFD or TDD) when calculating the time slot offset. In some aspects, the UE can calculate the time slot offset in different ways for different HARQ procedures corresponding to a frame. In some aspects, the time slot offset behavior can be based on the priority of information associated with the HARQ procedure.

Description

[0001] This application is a divisional application of patent application No. 202180032737.X, entitled "Hybrid Automatic Repeat Request Process for Subband Full-Duplex". The application date is May 26, 2021.

[0002] Cross-reference to related applications

[0003] This application is a PCT application claiming priority to non-provisional patent application No. 17 / 330,199, filed May 25, 2021, with the United States Patent and Trademark Office, and claiming priority to provisional patent application No. 63 / 031,477, filed May 28, 2020, with the United States Patent and Trademark Office. The entire contents of both applications are incorporated herein by reference as if their whole and all applicable purposes were fully set forth herein. Technical Field

[0004] In general, the technologies discussed below relate to wireless communication systems, and more specifically, to Hybrid Automatic Repeat Request (HARQ). Example deployments may occur in frame structures comprising one or more Sub-Band Full-Duplex (SB-FD) slots and one or more Time Division Duplex (TDD) slots. Some aspects may include technologies for enabling and providing communication devices configured to utilize both SB-FD and TDD slots (e.g., in some cases, for individual HARQ procedures and / or groups of HARQ procedures). Background Technology

[0005] In wireless communication, a full-duplex link is a link in which two endpoints can communicate with each other simultaneously on the same resource set. Many wireless communication systems specify full-duplex emulation, enabling bidirectional simultaneous communication between endpoints, but using different resource sets for transmissions in different directions. For example, Time Division Duplex (TDD) specifies the use of time-division multiplexing to separate transmissions in different directions on a given channel. That is, at certain times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in the other direction. In another example, Frequency Division Duplex (FDD) specifies that transmissions in different directions operate at different carrier frequencies.

[0006] In wireless communication systems utilizing Orthogonal Frequency Division Multiplexing (OFDM), a duplexing scheme commonly referred to as Subband Full-Duplex (SB-FD) can be used. SB-FD differs from traditional FDD in that, in FDD, a given carrier is typically dedicated entirely to either uplink or downlink communication. With SB-FD, a portion of the time-frequency resources on a given carrier is dedicated to the uplink, while a portion of the same carrier's time-frequency resources supports the downlink. Therefore, endpoints using SB-FD can simultaneously transmit and receive on different frequency resources of the same carrier. That is, downlink and uplink resources are separated in the frequency domain.

[0007] With the ever-increasing demand for mobile broadband access, research and development are continuously advancing wireless communication technologies. This is not only to meet the growing need for mobile bandwidth access but also to improve and enhance the user's mobile communication experience. As mobile communication technology has developed, its applications have diversified. For example, some applications require higher bandwidth than others. Similarly, some applications require lower latency than others. Applications such as video streaming may require high downlink bandwidth but only moderate uplink requirements. Meanwhile, real-time applications such as remotely controlling critical equipment may require extremely low latency with only moderate bandwidth requirements. Summary of the Invention

[0008] The following provides a brief overview of one or more aspects of this disclosure to offer a basic understanding of these aspects. This disclosure is not an exhaustive summary of all the features considered in this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to describe the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in a simplified form as a prelude to the more detailed description that follows.

[0009] In various aspects, this disclosure provides HARQ techniques. For example, HARQ can be used in wireless communication procedures through which a user equipment (UE) can implement or process HARQ in various full-duplex scenarios. A specific example is the use of HARQ in a frame structure that includes sub-band full-duplex (SB-FD) time slots and time-division duplex (TDD) time slots. The UE can identify the time slots in which to transmit and / or receive information associated with one or more HARQ procedures by calculating time slot offsets based on parameters received from the base station. In some aspects, the UE can exclude certain time slot duplex types when calculating time slot offsets. In some aspects, the UE can calculate time slot offsets in different ways for different subsets of HARQ procedures. In some aspects, the UE can calculate the time slot offset of a given HARQ procedure based on the priority of the information associated with that given HARQ procedure.

[0010] One aspect of this disclosure provides a wireless communication method operable at a user equipment (UE). The method includes: receiving, via a transceiver, a first downlink time slot offset parameter in a first time slot associated with a first Hybrid Automatic Repeat Request (HARQ) procedure. The first HARQ procedure corresponds to a frame structure including one or more sub-band full-duplex (SB-FD) time slots and one or more time-division duplex (TDD) time slots. The method further includes: receiving, via the transceiver, a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ procedure. The second time slot associated with the first HARQ procedure is offset relative to the first time slot associated with the first HARQ procedure by a number of time slots corresponding to the first downlink time slot offset parameter. The method further includes: transmitting, via the transceiver, first HARQ-ACK information in a third time slot associated with the first HARQ procedure, indicating whether the UE has successfully decoded the first PDSCH. The third time slot associated with the first HARQ procedure is offset relative to the second time slot associated with the first HARQ procedure by the number of time slots corresponding to the first HARQ timing parameters.

[0011] In another aspect of this disclosure, a wireless communication device operable as a user equipment (UE) includes: a processor; a memory coupled to the processor; and a transceiver coupled to the processor. The processor and the memory are configured to cause the UE to receive a first downlink time slot offset parameter via the transceiver in a first time slot associated with a first Hybrid Automatic Repeat Request (HARQ) procedure. The first HARQ procedure corresponds to a frame structure including one or more sub-band full-duplex (SB-FD) time slots and one or more time-division duplex (TDD) time slots. The processor and the memory are further configured to cause the UE to receive a first physical downlink shared channel (PDSCH) transmission via the transceiver in a second time slot associated with the first HARQ procedure. The second time slot associated with the first HARQ procedure is offset relative to the first time slot associated with the first HARQ procedure by a number of time slots corresponding to the first downlink time slot offset parameter. The processor and the memory are further configured to cause the UE to: transmit, via the transceiver, in a third time slot associated with the first HARQ procedure, a first HARQ-ACK message indicating whether the UE has successfully decoded the first PDSCH, the third time slot being offset relative to the second time slot associated with the first HARQ procedure by a number of time slots corresponding to the first HARQ timing parameters.

[0012] Another aspect of this disclosure provides a wireless communication device operable as a user equipment (UE). The device includes: a unit for receiving a first downlink time slot offset parameter in a first time slot associated with a first Hybrid Automatic Repeat Request (HARQ) procedure. The first HARQ procedure corresponds to a frame structure including one or more sub-band full-duplex (SB-FD) time slots and one or more time-division duplex (TDD) time slots. The device further includes: a unit for receiving a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ procedure. The second time slot associated with the first HARQ procedure is offset relative to the first time slot associated with the first HARQ procedure by a time slot number corresponding to the first downlink time slot offset parameter. The device further includes: a unit for transmitting first HARQ-ACK information indicating whether the UE has successfully decoded the first PDSCH in a third time slot associated with the first HARQ procedure. The third time slot associated with the first HARQ procedure is offset relative to the second time slot associated with the first HARQ procedure by a time slot number corresponding to the first HARQ timing parameter.

[0013] In another aspect of this disclosure, a non-transitory computer-readable medium is provided that stores computer-executable code operable by a user equipment (UE). The medium includes code for instructing the UE to receive a first downlink time slot offset parameter via a transceiver in a first time slot associated with a first Hybrid Automatic Repeat Request (HARQ) procedure. The first HARQ procedure corresponds to a frame structure comprising one or more sub-band full-duplex (SB-FD) time slots and one or more time-division duplex (TDD) time slots. The medium also includes code for instructing the UE to receive a first physical downlink shared channel (PDSCH) transmission via the transceiver in a second time slot associated with the first HARQ procedure. The second time slot associated with the first HARQ procedure is offset relative to the first time slot associated with the first HARQ procedure by a number of time slots corresponding to the first downlink time slot offset parameter. The medium also includes code that causes the UE to perform the following operation: transmit via the transceiver in a third time slot associated with the first HARQ procedure a first HARQ-ACK message indicating whether the UE has successfully decoded the first PDSCH, the third time slot being offset relative to the second time slot associated with the first HARQ procedure by a number of time slots corresponding to the first HARQ timing parameters.

[0014] These and other aspects enable communication systems comprising one or more UEs to adaptively use subband full-duplex time slot formats. In some cases, the adaptive or variable use of the SB-FD time slot format can be used in conjunction with the time-division duplex time slot format. This arrangement can accommodate the bandwidth and latency requirements of various applications and terminal use cases. And as discussed in more detail below, some aspects and different deployments enable and provide techniques for adapting to changes in requirements over short periods of time (e.g., a few seconds or less, or periods involving low-latency communication).

[0015] These and other aspects of the invention will be more fully understood by browsing the following detailed description. Other aspects, features, and embodiments will become apparent to those skilled in the art when viewed in conjunction with the accompanying drawings of the specific, exemplary embodiments described below. Although features may be discussed with reference to some embodiments and figures below, all embodiments may include one or more of the preferred features discussed herein. In other words, while one or more embodiments may be discussed as having certain preferred features, one or more of these features may also be used according to the various embodiments discussed herein. Similarly, although exemplary embodiments may be discussed below as embodiments of devices, systems, or methods, it should be understood that these exemplary embodiments may be implemented in various devices, systems, and methods. Attached Figure Description

[0016] Figure 1 It is a schematic diagram of a wireless communication system based on some aspects.

[0017] Figure 2 This is a conceptual diagram based on some aspects of a radio access network.

[0018] Figure 3 It is a schematic diagram of the organization of radio resources in an air interface using orthogonal frequency division multiplexing (OFDM) based on some aspects.

[0019] Figure 4 This is a detailed view of an example of a base station with physically separated and isolated antenna panels, based on some aspects.

[0020] Figure 5 This is a schematic diagram based on some aspects of in-band full-duplex (IBFD) communication.

[0021] Figure 6 This is a schematic diagram of sub-band full-duplex (SB-FD) communication based on some aspects.

[0022] Figure 7 This is a schematic diagram of the time slots configured for SB-FD based on certain aspects.

[0023] Figure 8 It is a schematic diagram of the operation of a series of time slots on a flexible duplex carrier and the corresponding operation of physically separated and isolated antenna panels.

[0024] Figure 9 It is a schematic diagram of a series of time slots on uplink flexible duplex carriers and downlink flexible duplex carriers based on some aspects, in which the user equipment (UE) performs a hybrid automatic repeat request (HARQ) process and its corresponding time slot offset calculation for both time division duplex (TDD) and SB-FD time slots.

[0025] Figure 10 It is a schematic diagram of a series of time slots on the uplink flexible duplex carrier and downlink flexible duplex carrier based on some aspects, wherein the UE only performs the HARQ process and its corresponding time slot offset calculation for the TDD time slot.

[0026] Figure 11 It is a schematic diagram of a series of time slots on the uplink flexible duplex carrier and downlink flexible duplex carrier based on some aspects, wherein the UE only performs the HARQ procedure and its corresponding time slot offset calculation for the SB-FD time slot.

[0027] Figure 12It is a block diagram that conceptually illustrates an example of a hardware implementation of a scheduling entity based on some aspects.

[0028] Figure 13 It is a block diagram that conceptually illustrates an example of the hardware implementation of the scheduled entity based on some aspects.

[0029] Figure 14 This is a flowchart illustrating an exemplary process by which a UE communicates on a flexible duplex carrier including TDD and SB-FD time slots using one or more downlink HARQ procedures, based on some aspects.

[0030] Figure 15 This is a flowchart illustrating an exemplary process in which a UE communicates on a flexible duplex carrier including both TDD and SB-FD time slots using one or more uplink HARQ procedures, based on some aspects.

[0031] Figure 16 This is a flowchart illustrating an exemplary process in which the UE divides the HARQ procedure into two groups based on some aspects, wherein the UE calculates the slot offset of the first group based only on the TDD slot and the slot offset of the second group based only on the SB-FD slot.

[0032] Figure 17 This is a flowchart illustrating an exemplary process in which the UE divides the HARQ procedure into two groups based on some aspects, wherein the UE calculates the slot offset of the first group based solely on the TDD slot and calculates the slot offset of the second group based on both the TDD and SB-FD slots.

[0033] Figure 18 This is a flowchart illustrating an exemplary process in which the UE calculates the slot offset for low-priority HARQ communication based solely on the TDD slot and calculates the slot offset for high-priority HARQ communication based on both the TDD and SB-FD slots, according to some aspects.

[0034] Figure 19 This is a flowchart illustrating another exemplary process by which a UE schedules HARQ-ACK transmissions when the UE uses TDD and SB-FD time slot communication, according to some aspects.

[0035] Figure 20 This is a flowchart illustrating yet another exemplary process by which a UE schedules HARQ-ACK transmissions when the UE uses TDD and SB-FD time slot communication, based on some aspects. Detailed Implementation

[0036] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations, and not as representations of the only configuration in which the concepts described herein are implemented. Specific details are included in the specific embodiments for the purpose of providing a comprehensive understanding of the various concepts. However, it will be apparent to those skilled in the art that these design concepts can be implemented without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0037] While aspects and embodiments have been described in this application by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, embodiments and / or uses may occur via integrated chip embodiments and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, broad applicability of the described innovations is possible. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further involve aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and embodiment of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / converters, etc.). The aim is that the innovations described herein can be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with varying sizes, shapes, and constructions.

[0038] This disclosure provides several mechanisms and techniques for processing sub-band full-duplex (SB-FD) and time-division duplex (TDD) time slots associated with one or more Hybrid Automatic Repeat Request (HARQ) procedures. The various examples disclosed herein enable devices and systems to interpret HARQ scheduling parameters, which are not explicitly specified by existing standards, based on messages or other indications shared between devices. The features of these mechanisms and algorithms, further explained below, can provide additional flexibility in wireless communication networks where the bandwidth and latency requirements of different devices may differ from each other and may change over time. In some examples, multiple HARQ procedures can be grouped into one or more groups based on signals transmitted by the network or devices. In other examples, the network or devices can transmit signals identifying the priority of one or more individual HARQ procedures.

[0039] It will be understood that while some examples are discussed in relation to the characteristics or operations of scheduled entities such as User Equipment (UE) or other devices, aspects of this disclosure relate to and can implicitly describe the corresponding characteristics and operations of one or more scheduling entities (e.g., base stations and similar devices and systems). Similarly, although some examples are discussed for downlink or uplink communication, it should be understood that the various examples will apply to uplink or downlink communication respectively. Furthermore, the aspects and characteristics discussed herein can be used in open RAN deployments, which may include various units and components such as Remote Units (RUs), Centralized Units (CUs), and Distributed Units (DUs). Deployments may also occur in peer-to-peer or sidelink scenarios where controlled scheduling may or may not be used, but rather device-self-organizing types of communication may be used instead.

[0040] Scheduling entities (including base stations) and scheduled entities (e.g., UEs) are dedicated computing devices that may be equipped with operating systems or dedicated circuitry to perform similar functions. These devices instantiate computational processes in memory by using computing resources (e.g., memory allocation and processing cycles) to execute machine code or other machine-readable program code and managing the use of these resources. In this context, a HARQ process is a dedicated computational process that can be instantiated by a scheduling entity or a scheduled entity to generate feedback signals for error correction purposes. These feedback signals can be shared with other devices to inform them whether their transmitted signals have been successfully received or to provide an estimate of the fidelity of these signals received by other devices. A device can execute multiple HARQ processes, and each HARQ process can be assigned to process a specific portion of the incoming communication signal. Therefore, it can be said that a HARQ process corresponds to or is associated with a specific group of incoming signals and a specific group of outgoing signals for transmitting the output signal generated by that process.

[0041] The various concepts presented throughout this disclosure can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards. Reference is now made to... Figure 1 As a non-limiting illustrative example, reference is made to wireless communication system 100, illustrating various aspects of this disclosure. Wireless communication system 100 includes three interaction domains: core network 102, radio access network (RAN) 104, and user equipment (UE) 106. With the aid of wireless communication system 100, UE 106 can communicate data with external data network 110 (such as, but not limited to, the Internet).

[0042] RAN 104 can implement any suitable wireless communication technology or some technology to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, RAN 104 can operate in a hybrid of 5G NR, commonly referred to as LTE, and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard. 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be used within the scope of this disclosure.

[0043] As shown, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for transmitting and receiving data to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station (BS) may also be referred to by those skilled in the art as a base transceiver unit (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), eNodeB (eNB), gNode B (gNB), or some other suitable term.

[0044] A radio access network 104 supporting wireless communication for multiple mobile devices is also illustrated. Mobile devices are referred to as User Equipment (UE) in the 3GPP standard, but may also be referred to by those skilled in the art as Mobile Station (MS), User Station, Mobile Unit, User Unit, Radio Unit, Remote Unit, Mobile Device, Radio Device, Wireless Communication Device, Remote Device, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handheld Device, Terminal, User Agent, Mobile Client, Client, or some other suitable term. The UE may be a means (e.g., a mobile device) that provides users with access to network services.

[0045] In this document, a “mobile” device does not necessarily have the ability to move and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE can include multiple hardware structural components of different sizes, shapes, and arrangements to facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebook computers, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems (e.g., corresponding to the “Internet of Things” (IoT)). A mobile device can also be an automobile or other transport 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-rotor aircraft, a quadcopter, a remote control device, consumer and / or wearable devices such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, such as remote healthcare. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, whose communications can be given priority processing or access to other types of information, such as priority access to the transmission of critical service data and / or related QoS aspects of critical service data transmission.

[0046] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions via the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to a point-to-multipoint transmission initiated at a scheduling entity (further described below, e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to other aspects of this disclosure, the term uplink can refer to a point-to-point transmission originating from a scheduled entity (further described below; e.g., UE 106).

[0047] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and apparatuses within its service area or cell. Within this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UE 106 (which may be a scheduled entity) can use the resources allocated by scheduling entity 108.

[0048] Base station 108 is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).

[0049] like Figure 1 As shown, scheduling entity 108 can send downlink service 112 to one or more scheduled entities 106. In general, scheduling entity 108 is a node or device responsible for scheduling services in the wireless communication network, including downlink service 112 and (in some examples) uplink service 116 from one or more scheduled entities 106 to scheduling entity 108. On the other hand, scheduled entity 106 is a node or device that receives downlink control information 114, which includes, but is not limited to, scheduling information (e.g., permission), synchronization or timing information, or other control information from another entity in the wireless communication network (such as scheduling entity 108).

[0050] Typically, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of a wireless communication system. Backhaul 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network can provide interconnection between the individual base stations 108. Various types of backhaul interfaces can be employed, such as direct physical connections using any suitable transport network, virtual networks, etc.

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

[0052] Now refer to Figure 2 A schematic diagram of RAN 200 is provided by way of example rather than limitation. In some examples, RAN 200 can be described above and... Figure 1 The same as RAN 104 shown. The geographical area covered by RAN 200 can be divided into cellular areas (cells) that can be uniquely identified by a user equipment (UE) based on an identifier broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206, and small cell 208 are shown, 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 base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into multiple sectors, multiple sectors within the cell can be formed by antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0053] exist Figure 2 In the illustration, two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, the base station can have an integrated antenna, or it can be connected to an antenna or RRH via a feed cable. In the illustrated example, cells 202, 204, and 216 can be referred to as macro cells when base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in a small cell 208 (e.g., microcell, picocell, femtocell, home base station, home node B, home eNodeB, etc.) that may overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports cells with relatively small sizes. Cell size adjustments can be made according to system design and component constraints.

[0054] It should be understood that the radio access network 200 may include any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be used in conjunction with those described above and Figure 1 The base station / scheduling entity 108 shown is the same.

[0055] Figure 2 It also includes a quadcopter or drone 220, which can be configured to be used as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell can move depending on the location of the mobile base station (such as the quadcopter 220).

[0056] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Additionally, each base station 210, 212, 214, 218, and 220 can be configured to provide access to the core network 102 (participating in...) to all UEs in each cell. Figure 1 Access points. For example, UE 222 and UE 224 can communicate with base station 210; UE 226 and UE 228 can communicate with base station 212; UE 230 and UE 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can communicate with the access points described above and... Figure 1 The UE / scheduled entity 106 shown is the same.

[0057] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to act as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

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

[0059] The air interface in the radio access network 200 can use one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiplexing access for UL transmissions from UEs 222 and 224 to base station 210, and utilizes Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) to multiplex DL transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform-Extended-OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. Alternatively, Time Division Multiplexing (TDM), Code Division Multiplexing (CDM), Frequency Division Multiplexing (FDM), Orthogonal Frequency Division Multiplexing (OFDM), Sparse Code Multiplexing (SCM) or other suitable multiplexing schemes can be used to provide multiplexing for DL ​​transmission from base station 210 to UE 222 and UE 224.

[0060] Reference Figure 3The OFDM waveforms illustrated herein are used to describe various aspects of this disclosure. Those skilled in the art should understand that various aspects of this disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described herein. That is, although some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to DFT-s-OFDMA waveforms.

[0061] Within this disclosure, a frame can generally refer to a 10 ms duration used for wireless transmission, where each frame consists of 10 subframes, each lasting 1 ms. On a given carrier, there may be one set of frames in the UL and another set in the DL. Now refer to Figure 3 An extended view of an exemplary DL subframe 302 is shown, which illustrates the OFDM resource grid 304. However, as those skilled in the art will readily recognize, the PHY transport structure for any particular application can differ from the example described herein based on any number of factors. Here, time is in OFDM symbols in the horizontal direction; and frequency is in subcarriers or tones in the vertical direction.

[0062] Resource grid 304 can be used to schematically represent the time-frequency resources of 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. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more information bits. In some examples, an RE block can be referred to as a physical resource block (PRB), or resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers. In some examples, an RB can include any suitable number of consecutive OFDM symbols in the time domain.

[0063] UEs typically use only a subset of resource grid 304. An RB can be the smallest unit of resource that can be allocated to a UE. Therefore, the more RBs scheduled for a UE and the more sophisticated the modulation scheme selected for the air interface, the higher the UE's data rate.

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

[0065] Each subframe 302 (e.g., a 1ms subframe) can consist of one or more adjacent time slots. Figure 3 In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. In some examples, time slots can be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Other examples may include micro-time slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). These micro-time slots may, in some cases, occupy resources scheduled for ongoing time slot transmissions for the same or different UEs.

[0066] An expanded view of one of the time slots in time slot 310 shows time slot 310 including control region 312 and data region 314. Typically, control region 312 may carry control channels, and data region 314 may carry data channels. Of course, the 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 is merely exemplary in nature, and different time slot structures can be used, and may include one or more of each of the control and data regions.

[0067] Despite Figure 3 Not shown, but various REs 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can provide the receiving equipment with the ability to perform channel estimation for the corresponding channels, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0068] In DL transmission, the transmitting device (e.g., scheduling entity 108 or base station 108) may allocate one or more REs 306 (e.g., within control area 312) to carry DL control information 114 destined for one or more scheduled entities or UEs 106. This includes one or more DL control channels that typically carry information originating from higher layers (e.g., Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), etc.). Additionally, DL REs may be allocated to carry DL physical signals that do not typically carry information originating 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 channel state information reference signal (CSI-RS), etc.

[0069] Synchronization signals PSS and SSS (collectively referred to as SS), and in some examples, PBCH, can be transmitted in an SS block comprising four consecutive OFDM symbols, numbered in ascending order from 0 to 3 via a time index. In the frequency domain, the SS block can be extended over 240 consecutive subcarriers, where the subcarriers are numbered in ascending order from 0 to 239 via a frequency index. Of course, this disclosure is not limited to this particular SS block configuration. Within the scope of this disclosure, other non-limiting examples may use more or fewer synchronization signals; one or more supplementary channels may be included in addition to PBCH; PBCH may be omitted; and / or non-consecutive symbols may be used for the SS block.

[0070] The PDCCH can carry downlink control information (DCI) for one or more UEs in the cell. This may include, but is not limited to, power control commands, scheduling information, permission and / or allocation of REs for DL ​​and UL transmissions.

[0071] In UL transmission, the transmitting device (e.g., the scheduled entity 106) can use one or more REs 306 to carry UL control information 118 (UCI). The UCI can be initiated from a higher layer to the scheduling entity 108 via one or more UL control channels (e.g., Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), etc.). Furthermore, the UL RE can carry UL physical signals that typically do not carry information originating from higher layers, such as demodulation reference signals (DM-RS), phase tracking reference signals (PT-RS), sounding reference signals (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request for scheduling uplink transmissions to the scheduling entity 108. In this document, in response to an SR transmitted on control channel 118, the scheduling entity 108 can transmit a DCI 114, which can schedule resources for uplink packet transmissions.

[0072] UCI may also include Hybrid Automatic Repeat Request (HARQ) feedback, such as Acknowledgment (ACK) or Negative Acknowledgment (NACK), Channel State Information (CSI), or any other suitable UL control information. HARQ is a technique well known to those skilled in the art, in which the integrity of packet transmissions can be checked at the receiving end for accuracy, for example, using any suitable integrity checking mechanism, such as checksums or Cyclic Redundancy Check (CRC). If the integrity of the transmission is acknowledged, an ACK can be sent, and if no ACK is received, a NACK can be sent. In response to a NACK, the transmitting device can send a HARQ retransmission, which can implement catch-up combination, incremental redundancy, etc. However, conventional HARQ techniques do not consider frame structures that include SB-FD slots in addition to slots of other slot duplex types (e.g., TDD slots, such as uplink slots, downlink slots, or “special” slots). As used herein, the term “slot duplex type” should be understood to describe the duplex configuration of associated slots, including but not limited to SB-FD and TDD slot duplex types.

[0073] In addition to control information, one or more RE 306s can be allocated for user data or service data (e.g., within data area 314). This service can be carried on one or more service channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmission; or the Physical Uplink Shared Channel (PUSCH) for UL transmission.

[0074] To enable a UE to gain initial access to a cell, the RAN can provide system information (SI) characterizing the cell. This system information can be provided using minimum system information (MSI) and other system information (OSI). MSI can be periodically broadcast on the cell to provide the most basic information required for initial cell access, as well as any OSI that can be broadcast periodically or sent on demand. In some examples, MSI can be provided on two different downlink channels. For example, the PBCH can carry a Master Information Block (MIB), and the PDSCH can carry System Information Block Type 1 (SIB1). In the art, SIB1 may be referred to as Residual Minimal System Information (RMSI).

[0075] OSI can include any SI that is not broadcast in MSI. In some examples, PDSCH can carry multiple SIBs, not limited to SIB1 discussed above. In this paper, OSI can be provided in these SIBs, such as SIB2 and later.

[0076] The above description and Figure 1 and Figure 3The channels or carriers shown are not necessarily all channels or carriers that can be used between the scheduling entity 108 and the scheduled entity 106, and those skilled in the art will recognize that other channels or carriers, such as other service, control and feedback channels, may be used in addition to those shown.

[0077] These physical channels are typically multiplexed and mapped to transport channels for processing at the Medium Access Control (MAC) layer. The transport channels carry blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to the number of information bits, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0078] The air interface in the radio access network 200 can use one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously on the same resource set. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Full-duplex simulations are often performed for wireless links using Frequency Division Duplex (FDD) or Time Division Duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel. That is, at some times, the channel is dedicated to transmissions in one direction (e.g., DL), while at other times, the channel is dedicated to transmissions in the other direction (e.g., UL), where the direction can change very rapidly, for example, several times per time slot.

[0079] In wireless links, full-duplex channels typically rely on the isolation between the transmitter and receiver. Suitable isolation techniques include physical isolation, electromagnetic shielding, and interference cancellation. In some examples, base stations can provide improved isolation between simultaneous transmit and receive operations by using two separate, physically isolated antenna panels, one for the UL and one for the DL. Figure 4 As shown in the illustration, when communicating via a full-duplex carrier, the base station can use panel 1 for DL ​​transmission, while the base station can use panel 2 for UL reception.

[0080] However, even with this physical isolation between the transmitting and receiving antenna panels, wireless communication endpoints performing full-duplex communication still face significant interference. In particular, self-interference generated at the same endpoint can be substantial. That is, because the transmitting and receiving antennas at the base station are very close to each other, the base station can also interfere with nearby receiving antennas when transmitting downlink signals. This makes it difficult for the base station to decode the received UL signal.

[0081] An example of a full-duplex communication scheme is commonly referred to in the art as in-band full-duplex (IB-FD). Figure 5 Two examples are shown. In IB-FD, UL and DL communications typically overlap in time and frequency. In some examples, the overlap can be partial, as shown on the right, where only a portion of the UL overlaps with the DL. In other examples, the overlap can be complete, as shown on the left, where the entire UL overlaps with the DL.

[0082] Recently, interest has turned to a technology that can be called Subband Full-Duplex (SB-FD) or Flexible Duplex. SB-FD differs from traditional FDD in that, in FDD, a given carrier is typically dedicated entirely to UL or DL ​​communication. With SB-FD, a portion of the time-frequency resources on a given carrier is dedicated to UL, while a portion of the time-frequency resources on the same carrier supports DL. Therefore, endpoints using SB-FD can simultaneously transmit and receive on different frequency resources of the same carrier. That is, DL resources and UL resources are separated in the frequency domain. Figure 6 An example of an SB-FD carrier is shown. In the example shown, the DL and UL portions of the carrier are frequency-separated from each other, with a guard band (GB) between the respective UL and DL portions to reduce interference, such as UL leakage to DL or DL ​​leakage to UL. However, since the GB may be relatively narrow (e.g., 5 RBs) compared to the spacing between carriers in conventional FDD, wireless communication using SB-FD may suffer from a greater amount of interference than conventional FDD. Regarding self-interference, a base station using SB-FD may suffer from its DL transmission leakage into its UL reception; and a UE using SB-FD may suffer from its UL transmission leakage into its DL reception.

[0083] Refer again Figure 4 When communicating with an SB-FD carrier, the base station can use panel 1 to perform DL transmission on one portion of the SB-FD carrier, while using panel 2 to perform UL reception on the other portion. Therefore, physical isolation via antennas can reduce self-interference at the base station to some extent. In various examples, the corresponding UL and DL portions of the SB-FD carrier can be allocated within a given time slot using any suitable configuration, separated by frequency, time, or both.

[0084] Figure 7An example of a time slot format for wireless communication utilizing SB-FD according to an aspect of this disclosure is shown. In the shown time slot, the upper portion 702 and the lower portion 704 of the carrier are used for DL ​​communication, and there is a UL portion 706 between these portions for UL communication. Two GBs 708 and 710 separate the UL portion from the DL portion, and they are immediately above and below the UL portion in frequency.

[0085] Figure 8 The diagram illustrates a sequence 800 of four consecutive time slots 802, 804, 806, and 808 in a carrier, configured to allow dynamic reconfiguration between time slots for TDD and SB-FD communication. In some examples, portions of the carrier within a given time slot may be designated by the base station as UL portions or DL ​​portions, and signaled to the UE using appropriate indication or configuration messages that enable the UE to determine the time slot format. For example, the UE may determine the time slot format for a given time slot based on appropriate indication or configuration messages provided by the base station. These indication or configuration messages may be contained within the DCI, within higher-layer (e.g., RRC) signaling, or some combination thereof. The time slot format corresponds to the RE configuration within the time slot, where each RE is designated for UL, DL, or, in some examples, flexible (either UL or DL). In various examples, the configuration or indication messages used by the UE to determine the time slot format may correspond to any suitable number of one or more time slots, and may correspond to time slots used simultaneously and / or later.

[0086] As shown, the first time slot 802 is configured for TDD, where the entire carrier bandwidth is used for DL ​​communication, rather than the last one or two OFDM symbols of the time slot, where the entire carrier bandwidth can be used for UL communication, such as HARQ-ACK, CSF, and / or uplink user data. For example, the first time slot 802 can be considered a "special" time slot because it includes both uplink and downlink time domain allocations. The second time slot 804 and the third time slot 806 are configured in accordance with the above description and... Figure 7 The method shown is essentially the same as the SB-FD configuration, with DL communication in the upper and lower portions of the carrier and UL communication in between. As discussed above, the UL portion of the carrier is shown separated from the DL portion by appropriate bandwidth guard bands above and below the UL portion. The fourth time slot 808 is configured for TDD, dedicated entirely to UL communication.

[0087] Including those described above and in Figure 4 In the example of a base station with two antenna panels shown, the operation of each antenna panel during different time slots... Figure 8The corresponding time slots are shown below. That is, in the first time slot 802, both antenna panels are used for DL ​​communication; while in the fourth time slot 808, both antenna panels are used for UL communication. In the second and third time slots 804 and 806, which are configured for SB-FD, the top antenna panel is configured for DL ​​transmission, while the bottom antenna panel is configured for UL reception.

[0088] The 5G NR specification provides asynchronous HARQ in both the uplink and downlink. Therefore, for HARQ between the base station and the UE, HARQ timing information must be provided to the UE by the base station. The UE can receive HARQ timing information via DCI of the PDCCH sent by the base station, RRC signaling sent by the base station, or other applicable control signaling sent by the base station. HARQ timing information for DL ​​can include a downlink slot offset parameter K0 and a HARQ-ACK timing parameter K1 (sometimes referred to as "HARQ timing parameter K1"). The downlink slot offset parameter K0 defines the slot offset (e.g., the number of slot transitions) between the slot carrying the DL scheduling information in the PDCCH and the slot carrying the corresponding scheduled PDSCH for the corresponding DL HARQ procedure. The HARQ timing parameter K1 defines the slot offset between the slot carrying the PDSCH and the slot carrying the ACK / NACK sent by the UE in response to the PDSCH for the corresponding DL HARQ procedure. The uplink slot offset parameter K2 defines the slot offset between the slot carrying UL scheduling information in the PDCCH and the slot carrying the corresponding scheduled PUSCH sent by the UE in the corresponding UL HARQ procedure.

[0089] In aspects of this disclosure, for one or more HARQ procedures of the UE, the UE can determine which slot duplex types to ignore (i.e., exclude) when calculating slot offsets based on parameters K0, K1, and / or K2. Based on the slot duplex type of a given slot, this configuration of the UE can effectively prohibit the carrying of scheduled data and / or HARQ-ACK in that slot. In some aspects, for all or a subset of active HARQ procedures, the UE can exclude SB-FD slots from the slot offset calculation. In some aspects, for all or a subset of active HARQ procedures, the UE can exclude TDD slots from the slot offset calculation. In some aspects, for all or a subset of active HARQ procedures, the UE can perform slot offset calculations regardless of the slot duplex type.

[0090] Figure 9Illustrated time slot sequences 900 (e.g., frames or portions of frames) corresponding to a DL HARQ procedure (i.e., the DL HARQ procedure is allocated to operate on DL transmissions over the depicted time slot sequence) and 930 (e.g., frames or portions of frames) corresponding to a UL HARQ procedure (i.e., the UL HARQ procedure is allocated to operate on UL transmissions over the depicted time slot sequence) are shown according to one aspect of this disclosure. Any of these HARQ procedures can correspond to a procedure performed by a UE (e.g., Figure 1 and / or Figure 2 The communication is performed by one of UEs 106, 234, 236, and 238. The frame structure of both the DLHARQ and UL HARQ procedures includes a combination of SB-FD and TDD time slots (e.g., an uplink time slot specified by "U" and a downlink time slot specified by "D"). In this document, "TDD time slot" may refer to a time slot with uplink, downlink, or "special" time slot duplex types. In the examples shown, each time slot sequence 900 and 930 includes the time slot pattern DDD(SB-FD)U, which may be repeated over the length of the frame. In each example sequence, the example time slot pattern is repeated twice. The use of this particular time slot pattern is intended to be illustrative and not restrictive. In the examples shown, according to one aspect of this disclosure, the UE is configured to transmit and receive information on a carrier according to one or more HARQ procedures and calculate the corresponding time slot offset, regardless of the time slot duplex type. Therefore, when calculating the slot offset, the UE can at least consider the TDD and SB-FD slot duplex types, and can send and receive data corresponding to the DL HARQ and UL HARQ procedures in the TDD and SB-FD slots, regardless of the slot duplex type of the PDCCH, PDSCH or PUSCH on which the slot offset calculation is based.

[0091] First, referring to the time slot sequence 900 corresponding to the DL HARQ procedure (i.e., the DL HARQ procedure is allocated to operate on DL transmissions in the depicted time slot sequence), the UE can receive control signaling. Control signals can be received from the base station in DL time slot 902 via a control channel (e.g., PDCCH 904), which includes scheduling information for the corresponding PDSCH (e.g., PDSCH 908) and an indication of whether the scheduled TB in the PDSCH will carry an initial transmission or a HARQ retransmission. Here, DL time slot 902 is configured for TDD. PDCCH 904 may also include a DCI defining the time slot offset parameter K0 = 1 and the HARQ timing parameter K1 = 1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided to the UE by the base station before DL time slot 902 can define parameters K0 and K1 for the DL HARQ procedure.

[0092] The UE can calculate the time slot offset from DL time slot 902. DL time slot 902 is the time slot carrying the corresponding PDCCH. This calculation can determine, based on the time slot offset parameter K0, that the base station will send PDSCH 908 to the UE in DL time slot 906. As shown, DL time slot 906 is also configured for TDD. Here, the time slot offset between DL time slot 902 and DL time slot 906 is one time slot because the time slot offset parameter K0 = 1. According to one aspect of this disclosure, the UE can calculate this time slot offset between DL time slot 902 and DL time slot 906 regardless of the time slot duplex type of DL time slot 902, DL time slot 906, and any other time slots between them (if such time slots exist).

[0093] When PDSCH 908 is received in DL slot 906, the UE can calculate one or more CRCs for one or more TBs included in PDSCH 908. The UE can then compare the corresponding CRC bits received in PDSCH 908 with the calculated CRC bits to determine whether to send an ACK or NACK 912 (sometimes referred to as "ACK / NACK" or "A / N") for the received TB. For example, the UE can send an ACK to the base station in response to determining that the received CRC bits match the calculated CRC bits. An ACK can indicate that the UE has successfully received and correctly decoded PDSCH 908. Alternatively, the UE can send a NACK to the base station in response to determining that the received CRC bits do not match the calculated CRC bits. A NACK can indicate that the UE has not successfully received and decoded PDSCH 908. The base station can interpret a NACK as a request for HARQ retransmission of the information included in PDSCH 908.

[0094] The UE can identify the slot offset from DL slot 906 (e.g., the slot carrying the scheduled PDSCH) based on the HARQ timing parameter K1 to determine the slot in which to send the corresponding ACK / NACK 912 (i.e., the ACK / NACK designated to indicate the ACK / NACK status of the PDSCH scheduled for DL ​​slot 906). Because the HARQ timing parameter indicates a slot offset (i.e., K1 = 1) in the example shown, the UE sends ACK / NACK 912 in SB-FD slot 910. As shown, SB-FD slot 910 is configured for SB-FD. Again, in this example, the UE can calculate this slot offset between DL slot 906 and SB-FD slot 910, regardless of the slot duplex type of DL slot 906, SB-FD slot 910, and any other slots between them (if such slots exist). The UE can then wait until it receives another PDCCH 916 corresponding to the DL HARQ procedure, for example in DL slot 914.

[0095] In the example shown, after receiving ACK / NACK 912 in SB-FD slot 910, the base station can send a DCI. The DCI is carried in PDCCH 916, which is transmitted in DL slot 914. The DCI in PDCCH 916 can update the value of the slot offset parameter to two slots (i.e., K0 = 2), while the HARQ timing parameter remains equal to 1 (i.e., K1 = 1). Furthermore, in PDCCH 916 carried in DL slot 914, the base station can send scheduling information for the corresponding PDSCH (e.g., PDSCH 920) and an indication of whether the scheduled TB in the PDSCH carries an initial transmission or a HARQ retransmission. The UE can calculate the time slot offset relative to DL time slot 914 (e.g., the time slot carrying the corresponding PDCCH 916) based on the time slot offset parameter indicating two time slots (i.e., K0 = 2) to determine that the base station will transmit the corresponding scheduled PDSCH 920 in SB-FD time slot 918 two time slots later. As shown, SB-FD time slot 918 is configured for SB-FD. Similarly, in this example, the UE can calculate this time slot offset between DL time slot 914 and SB-FD time slot 918, regardless of the time slot duplex type of DL time slot 914, SB-FD time slot 918, and any other time slots between them (if such time slots exist).

[0096] As described above, the UE can determine whether to send an ACK or NACK based on the CRC bits and TB in PDSCH 920. The UE can calculate the slot offset relative to SB-FD slot 918 (e.g., the slot carrying the corresponding PDSCH 920) based on the HARQ timing parameter K1 used for the DL HARQ procedure. The UE can send an ACK / NACK 924 in UL slot 922 one slot later (i.e., K1 = 1). As shown, UL slot 922 is also configured for TDD.

[0097] Referring now to the slot sequence 930 corresponding to the UL HARQ procedure (i.e., the UL HARQ procedure is allocated to operate on UL transmissions in the depicted slot sequence), the UE can receive PDCCH 934 from the base station. In some scenarios, PDCCH 934 can be in DL slot 932. PDCCH 934 may include scheduling information for the corresponding PUSCH (e.g., PUSCH 938). PDCCH 934 may also include an indication of whether the scheduled TB in the PUSCH carries an initial transmission or a HARQ retransmission. Here, DL slot 932 is configured for TDD. PDCCH 934 may also include DCI defining the slot offset parameter K2 = 2. Alternatively, another control signal provided to the UE by the base station before DL slot 932 (e.g., a previous PDCCH or RCC signaling) may define the parameter K2 for the UL HARQ procedure.

[0098] The UE can calculate the time slot offset relative to DL time slot 932 based on the time slot offset parameter K2 to determine which time slot the UE is scheduled to transmit PUSCH. In this example, the UE determines that PUSCH 938 is scheduled to use SB-FD time slot 936. Here, the time slot offset between DL time slot 932 and SB-FD time slot 936 is two time slots (because the time slot offset parameter K2 = 2). As shown, time slot 936 is configured for SB-FD. According to one aspect of this disclosure, the UE can calculate this time slot offset between DL time slot 932 and SB-FD time slot 936, regardless of the time slot duplex type of DL time slot 932, SB-FD time slot 936, and any other time slots between them (if such time slots exist).

[0099] The UE can then send PUSCH 938 to the base station in SB-FD slot 936. The UE can then wait to receive another PDCCH 942 from the base station corresponding to the UL HARQ procedure, for example in DL slot 940.

[0100] In the example shown, after receiving PUSCH 938 in SB-FD slot 936, the base station can transmit DCI. In this example, the DCI is transmitted in PDCCH 942. PDCCH 942 is carried in SB-FD slot 940 and used to update the value of the slot offset parameter K2 (K2 = 1). Furthermore, in PDCCH 942, the base station can transmit scheduling information for the corresponding PUSCH (e.g., PUSCH 946) and an indication of whether the scheduled TB in the PUSCH will carry the initial transmission or a HARQ retransmission. As shown, SB-FD slot 940 is also configured for SB-FD.

[0101] The UE can then calculate the slot offset relative to SB-FD slot 940 based on the slot offset parameter K2 used for the UL HARQ procedure. The UE can then transmit the initial transmission or HARQ retransmission in PUSCH 946 in UL slot 944 after K2 = 1 slot (e.g., according to the indication included in PDCCH 942). As shown, UL slot 944 is also configured for TDD.

[0102] Figure 10 Illustrative time slot sequences 1000 (e.g., frames or portions of frames) corresponding to a DL HARQ procedure and 1030 (e.g., frames or portions of frames) corresponding to a UL HARQ procedure are shown, according to another aspect of this disclosure. Any of these HARQ procedures may correspond to a procedure performed by a UE (e.g., Figure 1 and / or Figure 2 The communication is performed by one of UEs 106, 234, 236, and 238. The frame structure of both the DL HARQ and UL HARQ procedures includes a combination of SB-FD and TDD time slots (e.g., an uplink time slot specified by "U" and a downlink time slot specified by "D"). In the example shown, each time slot sequence 1000 and 1030 includes an illustrative time slot pattern DDD(SB-FD)U, which may repeat over the length of the frame. In the example shown, according to one aspect of this disclosure, the UE is configured to transmit and receive information on a carrier according to one or more HARQ procedures and calculate a corresponding time slot offset excluding SB-FD time slots (e.g., only for TDD time slots). Therefore, when calculating the time slot offset based on parameters K0, K1, and K2, the UE can ignore or skip time slots of the SB-FD time slot duplex type. After receiving the PDCCH corresponding to a given HARQ procedure, the UE can send and receive information corresponding to that HARQ procedure (e.g., via PDSCH, PUSCH, and / or ACK / NACK) only in the time slot of the TDD time slot duplex type (e.g., including UL, DL, and special time slot duplex types).

[0103] First, referring to the time slot sequence 1000 corresponding to the DL HARQ procedure, the UE can receive PDCCH 1004 from the base station in DL time slot 1002, including scheduling information for the corresponding PDSCH (e.g., PDSCH 1008) and an indication of whether the TB in the PDSCH will carry the initial transmission or HARQ retransmission. Here, DL time slot 1002 is configured for TDD. PDCCH 1004 may also include DCI defining the time slot offset parameter K0 = 1 and the HARQ timing parameter K1 = 1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided to the UE by the base station before DL time slot 1002 can define parameters K0 and K1 for the DL HARQ procedure.

[0104] The UE can calculate the time slot offset relative to DL time slot 1002 (e.g., the time slot carrying the corresponding PDCCH). The UE's calculation can determine, based on the time slot offset parameter K0, that the base station will send PDSCH 1008 to the UE in DL time slot 1006. As shown, DL time slot 1006 is also configured for TDD. Here, the time slot offset between DL time slot 1002 and DL time slot 1006 is one time slot because the time slot offset parameter K0 = 1. According to one aspect of this disclosure, when calculating this time slot offset between DL time slot 902 and DL time slot 906, the UE can exclude any time slot of the SB-FD time slot duplex type, if such a time slot exists.

[0105] When PDSCH 1008 is received in DL slot 1006, as described above, the UE determines whether to send an ACK or NACK to the base station based on the content of PDSCH 1008 and the corresponding CRC comparison. The UE can identify the slot offset relative to DL slot 1006 (e.g., the slot carrying the scheduled PDSCH 1008) based on the HARQ timing parameter K1 to determine the slot in which to send the corresponding ACK / NACK 1012. Since the HARQ timing parameter K1 is a slot in the example shown, and the UE is configured to exclude SB-FD slot 1010, the UE sends ACK / NACK 1012 in UL slot 1011. As shown, UL slot 1011 is configured for TDD. Again, in this example, the UE can calculate this slot offset between DL slot 1006 and UL slot 1011, excluding SB-FD slot duplex type slots if such slots exist. Here, the slot offset between DL slot 1006 and UL slot 1011 is nominally one slot because the HARQ timing parameter K1 = 1, but it is actually two slots because the UE excludes SB-FD slot 1010 from the slot offset calculation. The UE can then wait until it receives another PDCCH 1016 corresponding to the DL HARQ procedure, for example, in DL slot 1014.

[0106] In the example shown, after receiving ACK / NACK 1012 in UL slot 1011, the base station can transmit DCI in PDCCH 1016 carried in DL slot 1014. While in some aspects of this disclosure, DCI in PDCCH 1016 may include updated values ​​of parameters K0 and K1, DCI does not include such updates as in the example shown. In PDCCH 1016 carried in DL slot 1014, the base station can transmit scheduling information for the corresponding PDSCH (e.g., PDSCH 1020) and an indication of whether the scheduled TB in the PDSCH will carry an initial transmission or a HARQ retransmission. The UE can calculate the slot offset relative to DL slot 1014 (e.g., the slot carrying the corresponding PDCCH 1016) based on the slot offset parameter K0 = 1 to determine that the base station will transmit the corresponding scheduled PDSCH 1020 in DL slot 1017 one slot later. As shown, DL slot 1017 is configured for TDD. Similarly, in this example, the UE can calculate the slot offset between DL slot 1014 and DL slot 1017, excluding slots of the SB-FD slot duplex type, if such slots exist.

[0107] As described above, the UE can determine whether to send an ACK or NACK based on the CRC bits and TB in PDSCH 1020. The UE can calculate the slot offset relative to DL slot 1018 based on the HARQ timing parameter K1 used for the DL HARQ procedure, excluding SB-FD slot 1021. The UE can send ACK / NACK 1024 in UL slot 1022 one slot later (K1 = 1). As shown, UL slot 1022 is also configured for TDD. Similarly, in this example, the UE can calculate this slot offset between DL slot 1018 and UL slot 1022, excluding SB-FD slot duplex type slots if such slots exist.

[0108] Referring now to the slot sequence 1030 corresponding to the UL HARQ procedure, the UE can receive PDCCH 1034 from the base station in DL slot 1032, including scheduling information for the corresponding PUSCH (e.g., PUSCH 1038) and an indication of whether the scheduled TB in the PUSCH will carry the initial transmission or a HARQ retransmission. Here, DL slot 1032 is configured for TDD. PDCCH 1034 may also include DCI defining the slot offset parameter K2 = 2. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided to the UE by the base station before DL slot 1032 can define the parameter K2 for the UL HARQ procedure.

[0109] The UE can calculate the time slot offset relative to DL time slot 1032 based on the time slot offset parameter K2, while excluding SB-FD time slot 1036, to determine that the UE is scheduled to transmit PUSCH 1038 at UL time slot 1037. Here, the time slot offset between DL time slot 1032 and UL time slot 1037 is nominally two time slots because the time slot offset parameter K2 = 2, but it is actually three time slots because the UE excludes SB-FD time slot 1036 from the time slot offset calculation. As shown, UL time slot 1037 is configured for TDD. According to one aspect of this disclosure, when calculating this time slot offset between DL time slot 1032 and UL time slot 1036, the UE can exclude time slots of the SB-FD time slot duplex type, if such time slots exist.

[0110] The UE can then send PUSCH 1038 to the base station in UL slot 1037. The UE can then wait to receive another PDCCH 1042 from the base station, for example, in DL slot 1040.

[0111] In the example shown, after receiving PUSCH 1038 in UL slot 1037, the base station can transmit DCI in PDCCH 1042 carried in DL slot 1040 to update the value of the slot offset parameter K2 (K2 = 1). Furthermore, in PDCCH 1042 carried in DL slot 1040, the base station can transmit scheduling information for the corresponding PUSCH (e.g., PUSCH 1046) and an indication of whether the scheduled TB in the PUSCH will carry an initial transmission or a HARQ retransmission. As shown, DL slot 1040 is also configured for TDD.

[0112] The UE can determine the time slot offset relative to DL time slot 1040 based on the time slot offset parameter K2 used for the UL HARQ procedure, excluding SB-FD time slot 1043. As shown, SB-FD time slot 1043 is also configured for SB-FD. The UE can then transmit the initial transmission or HARQ retransmission in PUSCH 1046, determined by K2 = 1 (one time slot later), in UL time slot 1044 (e.g., according to the indication included in PDCCH 1042). Here, the time slot offset between DL time slot 1040 and UL time slot 1044 is nominally one time slot because the time slot offset parameter K2 = 1, but is actually two time slots because the UE excludes SB-FD time slot 1043 from the time slot offset calculation. As shown, UL time slot 1044 is also configured for TDD. Similarly, in this example, the UE can calculate the slot offset between DL slot 1040 and UL slot 1044, excluding SB-FD slot duplex type slots if such slots exist.

[0113] Figure 11 Illustrative time slot sequences 1100 (e.g., frames or portions of frames) corresponding to a DL HARQ procedure and 1130 (e.g., frames or portions of frames) corresponding to a UL HARQ procedure are shown, according to another aspect of this disclosure. Any of these HARQ procedures may correspond to a procedure performed by a UE (e.g., Figure 1 and / or Figure 2The communication is performed by one of UEs 106, 234, 236, and 238. The frame structure of both the DL HARQ and UL HARQ procedures includes a combination of SB-FD and TDD time slots (e.g., an uplink time slot specified by "U" and a downlink time slot specified by "D"). In the example shown, each time slot sequence 1100 and 1130 includes an illustrative time slot pattern DDD(SB-FD)U, which may repeat over the length of the frame. In the example shown, according to one aspect of this disclosure, the UE is configured to transmit and receive information on a carrier according to one or more HARQ procedures and calculate a corresponding time slot offset excluding TDD time slots (e.g., only for SB-FD time slots). Therefore, when calculating the time slot offset based on parameters K0, K1, and K2, the UE can ignore or skip time slots of TDD time slot duplex types (e.g., including UL, DL, and special time slot duplex types). After receiving the PDCCH corresponding to a given HARQ procedure, the UE can send and receive information corresponding to that HARQ procedure (e.g., via PDSCH, PUSCH, and / or ACK / NACK) only in a slot of the SB-FD slot duplex type.

[0114] First, referring to the slot sequence 1100 corresponding to the DL HARQ procedure, the UE can receive PDCCH 1104 from the base station in SB-FD slot 1102, including scheduling information for the corresponding PDSCH (e.g., PDSCH 1106) and an indication of whether the TB in the PDSCH will carry the initial transmission or HARQ retransmission. Here, SB-FD slot 1102 is configured for SB-FD. PDCCH 1104 may also include DCI defining the slot offset parameter K0 = 0 and the HARQ timing parameter K1 = 1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided to the UE by the base station before SB-FD slot 1102 can define parameters K0 and K1 for the DL HARQ procedure.

[0115] The UE can calculate the time slot offset relative to SB-FD time slot 1102 (e.g., the time slot carrying the corresponding PDCCH) based on the time slot offset parameter K0 to determine that the base station will transmit PDSCH 1106 to the UE in the same SB-FD time slot 1102. In the example shown, the time slot offset is zero because the time slot offset parameter K0 = 0, resulting in the UE receiving PDCCH 1104 and PDSCH 1106 in the same SB-FD time slot 1102. According to one aspect of this disclosure, when calculating this time slot offset, the UE can exclude any time slot of TDD time slot duplex type, if such a time slot exists.

[0116] When PDSCH 1106 is received in SB-FD slot 1102, as described above, the UE determines whether to send ACK or NACK based on the content of PDSCH 1106 and the corresponding CRC bit comparison. The UE can identify the slot offset relative to SB-FD slot 1102 (e.g., the slot carrying the scheduled PDSCH) based on the HARQ timing parameter K1 to determine the slot in which to send the corresponding ACK / NACK 1110. Since the HARQ timing parameter K1 = 1 (i.e., one slot) in the example shown, and the UE is configured to exclude TDD slots, the UE sends ACK / NACK 1110 in SB-FD slot 1108. As shown, SB-FD slot 1108 is configured for SB-FD. Again, in this example, the UE can calculate this slot offset between SB-FD slot 1102 and SB-FD slot 1108, excluding TDD slot duplex type slots if such slots exist. Here, the slot offset between SB-FD slot 1102 and SB-FD slot 1108 is nominally one slot because the HARQ timing parameter K1 = 1, but it is actually five slots because the UE excludes the TDD slot from the slot offset calculation. The UE can then wait until it receives another PDCCH from the base station.

[0117] Referring now to the slot sequence 1130 corresponding to the UL HARQ procedure, the UE can receive PDCCH 1134 from the base station in SB-FD slot 1132, including scheduling information for the corresponding PUSCH (e.g., PUSCH 1138) and an indication of whether the scheduled TB in the PDSCH will carry the initial transmission or a HARQ retransmission. Here, SB-FD slot 1132 is configured for SB-FD. PDCCH 1134 may also include DCI defining the slot offset parameter K2 = 1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided to the UE by the base station before SB-FD slot 1132 can define the parameter K2 for the UL HARQ procedure.

[0118] The UE can calculate the time slot offset relative to SB-FD time slot 1132 based on the time slot offset parameter K2, while excluding TDD time slots, to determine that the UE is scheduled to transmit PUSCH 1138 at SB-FD time slot 1136. Here, the time slot offset between SB-FD time slot 1132 and SB-FD time slot 1136 is nominally one time slot because the time slot offset parameter K2 = 1, but is actually five time slots because the UE excludes the intermediate TDD time slot from the time slot offset calculation. As shown, SB-FD time slot 1136 is configured for TDD. According to one aspect of this disclosure, when calculating this time slot offset between SB-FD time slot 1132 and SB-FD time slot 1136, the UE can exclude TDD time slot duplex type time slots, if such time slots exist. The UE can then transmit PUSCH 1138 to the base station in SB-FD time slot 1136. The UE can then wait to receive another PDCCH from the base station.

[0119] Figure 12 This is a block diagram illustrating an example hardware implementation of a scheduling entity 1200 using the processing system 1214. For example, the scheduling entity 1200 may be as follows: Figure 1 , Figure 2 and / or Figure 4 The base stations shown in any one or more of the figures. In another example, scheduling entity 1200 can be as follows: Figure 1 and / or Figure 2 The UE shown in any one or more of the figures.

[0120] Scheduling entity 1200 may include processing system 1214, which includes one or more processors 1204. Examples of processors 1204 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, scheduling entity 1200 may be configured to perform any one or more of the functions described herein. That is, processor 1204 (as used in scheduling entity 1200) may be used to implement any one or more of the procedures and programs described below.

[0121] In this example, processing system 1214 may include a bus architecture, typically represented by bus 1202. Bus 1202 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1214 and overall design constraints. Bus 1202 communicatively couples together various circuits including one or more processors (typically represented by processor 1204), memory 1205, and computer-readable media (typically represented by computer-readable media 1206). Bus 1202 may also link together various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. Bus interface 1008 provides an interface between bus 1202 and transceiver 1210. Transceiver 1210 provides a communication interface or a unit for communicating with various other devices over a transmission medium. Depending on the characteristics of the device, a user interface 1212 (e.g., keyboard, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1212 is optional and may be omitted in some examples (such as base stations).

[0122] In some aspects of this disclosure, processor 1204 may include time slot formatting circuitry 1240 configured (e.g., in conjunction with time slot formatting instruction 1252) for various functions, including, for example, determining and transmitting time slot formats to one or more UEs, including portions of time slots for UL communication, for DL ​​communication, or, in some examples, resources that can be flexibly allocated for UL or DL ​​communication. Processor 1204 may also include resource scheduling circuitry 1242 configured (e.g., in conjunction with resource scheduling instruction 1254) for various functions, including, for example, determining and transmitting resource allocations (e.g., grants) for one or more time slots or for one or more carriers to one or more UEs.

[0123] Processor 1204 is responsible for managing bus 1202 and general processing, including executing software stored on computer-readable medium 1206. This software may include time slot formatting instructions 1252 and resource scheduling instructions 1254. When processor 1204 executes the software, the software causes processing system 1214 to perform various functions for any particular device. As an example, processor 1204 may use time slot formatting circuitry 1240 to determine a sequence of time slots including any suitable combination of TDD and SB-FD time slots as described herein, and to determine the priority of HARQ-ACK processes for these time slots, taking into account the time slot formats of the various time slots and the priority of communications associated with these time slots. Computer-readable medium 1206 and memory 1205 may also be used to store data manipulated by processor 1204 while executing the software.

[0124] One or more processors 1204 in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, software should be broadly interpreted as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. The software may reside on a computer-readable medium 1206. The computer-readable medium 1206 may be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical discs (e.g., compressed optical discs (CDs) or digital versatile optical discs (DVDs)), smart cards, flash memory devices (e.g., card, stick, 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 medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1206 may be located within, outside, or distributed across multiple entities including processing system 1214. Computer-readable medium 1206 may be embodied in a computer program product. For example, a computer program product may include a computer-readable medium within encapsulation material. Those skilled in the art will recognize how the functionality described throughout this disclosure can be optimally implemented, depending on the specific application and the overall design constraints imposed on the system.

[0125] Figure 13 This is a conceptual diagram illustrating an example hardware implementation of an exemplary scheduled entity 1300 using processing system 1314. According to various aspects of this disclosure, processing system 1314, including one or more processors 1304, can implement elements, any portion of elements, or any combination of elements. For example, scheduled entity 1300 can be as follows: Figure 1 and / or Figure 2 Any one or more of the UEs shown in the figures.

[0126] Processing system 1314 is essentially compatible with Figure 12 The processing system 1214 shown is identical to that described above, including: bus interface 1308, bus 1302, memory 1305, processor 1304, and computer-readable medium 1306. Additionally, the scheduled entity 1300 may include entities that are essentially the same as... Figure 12 The user interfaces 1312 and transceiver 1310 described above are similar. That is, the processor 1304 (as used in the scheduled entity 1300) can be used to implement the following and... Figures 14-20Any one or more processes shown in the diagram.

[0127] In some aspects of this disclosure, processor 1304 may include HARQ circuitry 1340 configured for various functions, including, for example, processing communications associated with one or more active HARQ processes, calculating time slot offsets for one or more active HARQ processes, and / or determining whether an ACK or NACK should be sent based on (e.g., one or more TBs and / or CRCs of the received PDSCH). For example, HARQ circuitry 1340 may be configured (e.g., in conjunction with HARQ instruction 1352) to implement the following description. Figures 14-18 One or more of the functions described. Processor 1304 may also include a communication controller 1342 configured (e.g., in conjunction with communication instructions 1354) for various functions, including, for example, communicating via one or more wireless carriers.

[0128] UE DL HARQ process

[0129] Some aspects of this disclosure provide mechanisms and algorithms for handling communications associated with one or more active HARQ procedures for frame structures that include both TDD and SB-FD slots.

[0130] Although the following description references Figures 14-18 , Figures 14-18 The procedures that occur at the UE are described, but it should be understood that this disclosure is not limited to the operations or procedures at the UE. That is, the following description also describes the procedures and operations that occur at the base station, and this disclosure is prepared to fully disclose the operations at both endpoints of the signaling exchange between the UE and the base station.

[0131] Figure 14 This is a flowchart illustrating an exemplary process 1400 in which a UE performs communication operations associated with one or more DL HARQ procedures. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the shown features may be unnecessary for implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown can execute process 1400. In some examples, any suitable means or unit for performing the functions or algorithms described below can execute process 1400. In some examples, process 1400 can be performed by... Figure 13 The scheduled entity or UE 1300 shown is used to execute this.

[0132] In some examples, process 1400 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1400 may be executed by a processor 1304 of a scheduled entity 1300 (e.g., a UE) using HARQ processing circuitry and a communication controller (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354).

[0133] As described above, according to some examples, at block 1402, the UE can use a communication controller (e.g., communication controller 1342) to receive control information (e.g., via DCI, RRC signaling, and / or another applicable control signaling) from the base station via a transceiver (e.g., transceiver 1310). The control information defines a slot offset parameter K0 and a HARQ timing parameter K1 that combine a frame structure with both TDD and SB-FD slots for one or more HARQ procedures.

[0134] At box 1404, the UE uses the communication controller to receive the PDCCH via the transceiver in the first timeslot. The PDCCH includes DL scheduling information. For example, the DL scheduling information may define the resource blocks in which the base station will send the PDCCH to the UE.

[0135] At block 1406, the UE identifies a second time slot in which to monitor resources identified in the DL scheduling information, by calculating a time slot offset relative to a first time slot carrying the PDCCH, based on the time slot offset parameter K0. In some aspects of this disclosure, the UE can be configured to consider all time slot duplex types (e.g., time slots with SB-FD time slot duplex type and time slots with TDD time slot duplex type) when calculating the time slot offset. In other aspects of this disclosure, the UE can be configured to consider only some time slot duplex types (e.g., only time slots with SB-FD time slot duplex type or only time slots with TDD time slot duplex type) when calculating the time slot offset, and can exclude other time slot duplex types from being considered.

[0136] At box 1408, the UE uses the communication controller and transceiver to receive the PDSCH in the second time slot. The PDSCH may include one or more TBs and one or more CRCs for error detection.

[0137] At box 1410, the UE uses HARQ circuitry to calculate one or more CRCs for the TB of the PDSCH. The UE uses HARQ circuitry to compare the calculated CRC with the received CRC to determine whether the UE should send an ACK or NACK to the base station. For example, if the UE determines that the compared CRCs match, the UE can determine that it should send an ACK to the base station for the received TB. For example, if the UE determines that the compared CRCs do not match, the UE can determine that it should send a NACK to the base station for the received TB.

[0138] At box 1412, the UE identifies the third time slot in which to send ACK / NACK by calculating the time slot offset relative to the time slot carrying PDSCH (i.e., the first time slot) based on the HARQ timing parameter K1. As indicated above, in some cases, the UE can be configured to exclude or “skip” time slots of a given time slot duplex type when calculating the time slot offset. In other cases, the UE can be configured to count time slots of all time slot duplex types when calculating the time slot offset.

[0139] At box 1414, the UE sends an ACK / NACK generated using the HARQ circuit to the base station in the third time slot.

[0140] At box 1416, the UE waits to receive the next PDCCH from the base station. Once the UE receives the next PDCCH from the base station, the process returns to box 1404.

[0141] It should be understood that certain aspects of Example Process 1400 and other processes described herein may relate to and implicitly describe the characteristics or operations of a scheduling entity (e.g., a base station communicating with the aforementioned UE). For example, the base station may generate or otherwise receive desired time slot offsets for various HARQ procedures to be performed by the UE on downlink data received from the base station. As an additional example, the base station may determine (or receive) a bitmap format that the UE can use to select between different HARQ-ACK scheduling behaviors as described herein. As yet another example, the base station may determine the priority of each HARQ-ACK procedure, or the priority of requests received from the network or another device such as the UE, and transmit desired time slot offsets for the HARQ-ACK procedure to the UE based on those priorities.

[0142] UE UL HARQ process

[0143] Figure 15This is a flowchart illustrating an exemplary process 1500 in which a UE performs communication operations associated with one or more UL HARQ procedures. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the shown features may be unnecessary for all implementations. In some examples, Figure 13 The scheduled entity or UE 1300 shown may execute procedure 1500. In some examples, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1500.

[0144] In some examples, process 1500 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1500 may be executed by a processor of UE 1304, such as scheduled entity 1300, using HARQ processing circuitry and communication controllers (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354).

[0145] As described above, according to some examples, at block 1502, the UE uses a transceiver (e.g., transceiver 1310) and a communication controller to receive control information (e.g., via DCI, RRC signaling, and / or another applicable control signaling) from the base station. The control information defines a slot offset parameter K2 that combines a frame structure including both TDD slots and SB-FD slots for one or more HARQ procedures.

[0146] At box 1504, the UE receives a PDCCH, including UL-approved permissions, from the base station via a transceiver. For example, UL approval can define the resources in which the UE will send PUSCH to the base station.

[0147] At block 1506, the UE identifies the time slot in which to transmit the PUSCH (e.g., in a resource identified in the UL permission) by calculating the time slot offset relative to the time slot carrying the PDCCH based on the time slot offset parameter K2. In some aspects of this disclosure, the UE can be configured to consider all time slot duplex types (e.g., SB-FD and TDD time slot duplex types) when calculating the time slot offset. In other aspects of this disclosure, the UE can be configured to consider only some time slot duplex types when calculating the time slot offset (e.g., only time slots with the SB-FD time slot duplex type or only time slots with the TDD time slot duplex type), and can exclude other time slot duplex types from being considered.

[0148] At box 1508, the UE uses the communication controller to send PUSCH to the base station via the transceiver in a time slot.

[0149] At box 1510, the UE waits to receive the next PDCCH from the base station. Once the UE receives the next PDCCH from the base station, the UE returns to box 1504.

[0150] UE HARQ procedures with HARQ procedure groups excluding SB-FD and excluding TDD

[0151] Figure 16 This is a flowchart illustrating an exemplary process 1600 in which a UE performs communication operations associated with a first set of HARQ procedures and a second set of HARQ procedures. For the first set of HARQ procedures, the UE is configured to exclude SB-FD time slots (i.e., time slots with SB-FD time slot duplex type) when performing time slot offset calculation. For the second set of HARQ procedures, the UE is configured to exclude TDD time slots (i.e., time slots with TDD time slot duplex type) when performing time slot offset calculation. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the features shown may be unnecessary for implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown can execute procedure 1600. In some examples, any suitable means or unit for performing the functions or algorithms described below can execute procedure 1600. In some examples, in addition to the first and second sets of HARQ procedures, the UE can also manage additional HARQ procedures regardless of the time slot duplex type, as described above. Figure 9 As described.

[0152] In some examples, process 1600 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1600 may be executed by a processor of UE 1304, such as scheduled entity 1300, using HARQ processing circuitry and communication controllers (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354).

[0153] At box 1602, the UE can use HARQ circuitry to assign a HARQ procedure to either the first or second group based on a partition indicator. The UE can use a communication controller and transceiver (e.g., transceiver 1310) to receive control information (e.g., DCI, RRC signaling, or other control information) including the partition indicator from the base station. In this example, when performing a HARQ procedure for the first group, the UE is configured to exclude the SB-FD time slot from the time slot offset calculation. When performing a HARQ procedure for the second group, the UE is configured to exclude the TDD time slot from the time slot offset calculation.

[0154] At box 1604, for the first group of DL HARQ procedures, the UE executes... Figure 14 The process is 1400, and the SB-FD time slot is excluded when calculating the time slot offset.

[0155] At box 1606, for the first group of UL HARQ procedures, the UE executes... Figure 15 The process is 1500, while SB-FD time slots are excluded when calculating time slot offset.

[0156] At box 1608, for the second group of DL HARQ procedures, the UE executes... Figure 14 The process is 1400, while TDD time slots are excluded when calculating time slot offset.

[0157] At box 1610, for the second group of UL HARQ procedures, the UE performs... Figure 15 The process is 1500, while TDD time slots are excluded when calculating time slot offset.

[0158] It should be understood that the order in which boxes 1604-1610 are executed shown herein is illustrative, not restrictive. Boxes 1604-1610 may be executed in any desired order.

[0159] It should be understood that execution procedure 1600 can be used to divide multiple HARQ procedures into two subsets: a first subset in which HARQ scheduling parameters are computed only for TDD time slots, and a second subset in which HARQ scheduling parameters are computed only for SB-FD time slots. In some examples, HARQ procedures belonging to the first subset can operate only on TDD time slots, while HARQ procedures belonging to the second subset can operate only on SB-FD time slots. In contrast, in other previously disclosed examples, HARQ procedure scheduling can be performed without distinguishing between TDD, SB-FD, and other time slot formats.

[0160] UE HARQ procedures with excluding SB-FD and fully included HARQ procedure partitioning

[0161] Figure 17 This is a flowchart illustrating an exemplary procedure 1700 in which a UE performs communication operations associated with a first set of HARQ procedures and a second set of HARQ procedures. For the first set of HARQ procedures, the UE is configured to exclude SB-FD time slots (i.e., time slots with SB-FD time slot duplex type) when performing time slot offset calculation. For the second set of HARQ procedures, the UE is configured to perform time slot offset calculation without considering time slot duplex type. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the features shown may be unnecessary for implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown may execute procedure 1700. In some examples, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1700.

[0162] In some examples, process 1700 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1700 may be executed by a processor of UE 1304, such as scheduled entity 1300, using HARQ processing circuitry and communication controllers (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354).

[0163] At box 1702, the processor assigns a HARQ procedure to either the first or second group based on a partition indicator. The UE can receive control information (e.g., DCI, RRC signaling, or other control information) including the partition indicator from the base station using a communication controller and transceiver (e.g., transceiver 1310). In this example, for the HARQ procedure of the first group, the UE is configured (including its HARQ circuitry) to exclude the SB-FD time slot from the time slot offset calculation. For the HARQ procedure of the second group, the UE is configured (including its HARQ circuitry) to perform the time slot offset calculation regardless of the time slot duplex type.

[0164] At box 1704, for the first group of DL HARQ procedures, the UE executes... Figure 14 The process is 1400, and the SB-FD time slot is excluded when calculating the time slot offset.

[0165] At box 1706, for the first group of UL HARQ procedures, the UE executes... Figure 15 The process is 1500, while SB-FD time slots are excluded when calculating time slot offset.

[0166] At box 1708, for the second group of DL HARQ procedures, the UE executes... Figure 14 The process is 1400, regardless of the time slot duplex type.

[0167] At box 1710, for the second group of UL HARQ procedures, the UE performs... Figure 15 The process is 1500, regardless of the time slot duplex type.

[0168] It should be understood that the order in which boxes 1704-1710 are executed is illustrative, not restrictive. Boxes 1704-1710 can be executed in any desired order.

[0169] It should be understood that execution procedure 1700 can be used to divide multiple HARQ procedures into two subsets: a first subset in which HARQ scheduling parameters are computed only for TDD time slots, and a second subset in which HARQ scheduling parameters are computed without distinguishing between TDD, SB-FD, and / or other time slot formats. In some examples, HARQ procedures belonging to the first subset may operate only on TDD time slots, while HARQ procedures belonging to the second subset may operate on both TDD and SB-FD time slots. In some examples, procedure 1700 and other procedures disclosed herein may be executed as part of a communication scheme capable of providing multiple communication service levels tailored to different devices and services on the same network resources. As a non-limiting example, the network may provide an Enhanced Mobile Broadband (eMBB) service level and an Ultra-Reliable Low-Latency Communication (URLLC) service level, as defined in 3GPP 5G NR Standard Release 16. In a specific, non-restrictive example, HARQ procedures associated with eMBB data services may be assigned to a first subset described in combination procedure 1700, and HARQ procedures associated with URLLC services may be assigned to a second subset described in combination procedure 1700.

[0170] HARQ procedure based on UE priority

[0171] Figure 18 This is a flowchart illustrating an exemplary procedure 1800 in which a UE performs communication operations associated with an active HARQ procedure to process transmissions with defined priorities. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the shown features may be unnecessary for implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown may execute procedure 1800. In some examples, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1800.

[0172] In some examples, process 1800 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1800 may be executed by a processor 1304 of a scheduled entity 1300 (i.e., the UE in this example), using HARQ processing circuitry and communication controllers (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354).

[0173] At box 1802, the UE uses a communication controller and a transceiver coupled to the communication controller (e.g., transceiver 1310) to receive control information including a priority indicator (e.g., DCI, RRC signaling, or other applicable control information). The priority indicator can define a high or low priority level for the corresponding transmission to be processed by the UE in conjunction with the active HARQ procedure. In this example, for low-priority transmissions, the processor (including its HARQ circuitry) is configured to exclude the SB-FD time slot from the time slot offset calculation. For high-priority transmissions, the UE is configured (including its HARQ circuitry) to perform the time slot offset calculation regardless of the time slot duplex type.

[0174] At box 1804, the UE determines the transmission priority based on the priority indicator.

[0175] At box 1806, if the UE determines that the transmission priority is low, the process proceeds to box 1808. Otherwise, if the UE determines that the transmission priority is high, the process proceeds to box 1814.

[0176] At box 1808, the UE determines (e.g., based on control information) whether the transmission is for DL ​​or UL. If the UE determines the transmission is for DL, the process proceeds to box 1810. Otherwise, if the UE determines the transmission is for UL, the process proceeds to box 1812.

[0177] At box 1810, in response to determining that the transmission is a low-priority DL transmission, the UE performs... Figure 14 The process is 1400, and the SB-FD time slot is excluded when calculating the time slot offset.

[0178] At box 1812, in response to determining that the transmission is a low-priority UL transmission, the UE performs... Figure 15 The process is 1500, while SB-FD time slots are excluded when calculating time slot offset.

[0179] At box 1814, the UE determines (e.g., based on control information) whether the transmission is for DL ​​or UL. If the UE determines the transmission is a DL transmission, the process proceeds to box 1816. Otherwise, if the UE determines the transmission is a UL transmission, the process proceeds to box 1818.

[0180] At box 1816, in response to determining that the transmission is a high-priority DL transmission, the UE executes... Figure 14 The process is 1400, regardless of the time slot duplex type.

[0181] At box 1818, in response to determining that the transmission is a high-priority UL transmission, the UE performs... Figure 15 The process is 1500, regardless of the time slot duplex type.

[0182] It should be understood that execution procedure 1800 can be used to divide multiple HARQ procedures into two subsets: a first subset in which HARQ scheduling parameters are computed for TDD time slots only when a relatively lower priority is assigned, and a second subset in which HARQ scheduling parameter computation is computed without distinguishing between TDD, SB-FD, and / or other time slot formats when a relatively higher priority is assigned. In some examples, HARQ procedures belonging to the first subset may operate only on TDD time slots, while HARQ procedures belonging to the second subset may operate on both TDD and SB-FD time slots.

[0183] It should be understood that the methods described above and the devices implementing them can be used to provide certain technological advantages, including enabling higher bandwidth and lower latency communication for different types of devices or users of these devices. Furthermore, by prioritizing communications requiring particularly low latency over lower priority communications, improvements in overall network capacity and performance metrics can be achieved, ensuring that service level objectives for a range of different devices can be met without investing in reducing latency for all connected devices or increasing the available bandwidth for every anticipated device that may connect to the wireless communication network. Moreover, the service level provided to each connected device does not need to be static and can be adjusted based on user input or without human intervention using computational techniques known in the art, including machine learning techniques, to provide different levels of service tailored to the needs of individual devices at different points in time.

[0184] Additional example procedure:

[0185] Figure 19 This is a flowchart illustrating an exemplary process 1900 in which a UE performs communication operations associated with an active HARQ procedure to process transmissions associated with a frame structure having TDD and SB-FD time slots. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the shown features may be unnecessary for all implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown may execute procedure 1900. In some examples, any suitable means or unit for performing the functions or algorithms described below may execute procedure 1900.

[0186] In some examples, process 1900 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 1900 may be executed by a processor (e.g., UE 1304 of scheduled entity 1300), HARQ processing circuitry and a communication controller (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354), and a transceiver (e.g., transceiver 1310) coupled to the communication controller.

[0187] At box 1902, the UE may use the communication controller and transceiver to receive a first downlink slot offset parameter and a first HARQ timing parameter for a first hybrid automatic repeat request (HARQ) procedure corresponding to a frame structure including at least one slot of subband full-duplex (SB-FD) slot duplex type and at least one slot of time division duplex (TDD) slot duplex type.

[0188] At box 1904, the UE receives first downlink scheduling information using the communication controller and transceiver in the first time slot associated with the first HARQ procedure.

[0189] At box 1906, the UE identifies the second time slot associated with the first HARQ procedure by calculating the first time slot offset relative to the first time slot associated with the first HARQ procedure based on the first downlink time slot offset parameter.

[0190] At box 1908, the UE receives the first physical downlink shared channel (PDSCH) in the second time slot associated with the first HARQ procedure;

[0191] At box 1910, the UE identifies the third time slot associated with the first HARQ procedure by calculating a second time slot offset relative to the second time slot associated with the first HARQ procedure based on the first HARQ timing parameters; and

[0192] At block 1912, the UE uses the communication controller and transceiver to transmit a first acknowledgment in a third time slot associated with the first HARQ procedure, corresponding to the information received on the first PDSCH, generated using the HARQ circuitry.

[0193] Figure 20This is a flowchart illustrating another exemplary process 2000 in which a UE performs communication operations associated with an active HARQ procedure to process transmissions associated with a frame structure having TDD and SB-FD time slots. As described below, some or all of the features shown may be omitted in certain implementations within the scope of this disclosure, and some of the shown features may be unnecessary for implementations of all embodiments. In some examples, Figure 13 The scheduled entity or UE 1300 shown may execute procedure 2000. In some examples, any suitable means or unit for performing the functions or algorithms described below may execute procedure 2000.

[0194] In some examples, process 2000 may be executed by any suitable means or unit for performing the functions or algorithms described below. In one example, process 2000 may be executed by a processor (e.g., UE1304 of scheduled entity 1300), HARQ processing circuitry and a communication controller (e.g., HARQ circuitry 1340 and communication controller 1342) that execute computer-readable instructions (e.g., HARQ instructions 1352 and communication instructions 1354), and a transceiver (e.g., transceiver 1310) coupled to the communication controller.

[0195] At box 2002, the UE receives a partitioning indicator for the frame structure, which includes both SB-FD and TDD time slots. In this example, the UE is configured to operate two HARQ procedures, denoted as “HARQ[1]” and “HARQ[2]”. The UE then proceeds to boxes 2010-2020 (where the UE performs the action associated with HARQ[1]) and boxes 2030-2040 (where the UE performs the action associated with HARQ[2]).

[0196] At box 2010, the UE receives the first downlink time slot offset parameter in the first time slot associated with HARQ[1]. The UE may also optionally receive the first HARQ timing parameter (also associated with HARQ[1]) in the same time slot. In some respects, the UE may receive the first HARQ timing parameter in any other suitable time slot or by any other suitable means.

[0197] In box 2012, the UE selects an offset behavior for HARQ[1] based on the partition indicator received at box 2002. The offset behavior specifies how the UE should treat different types of time slots (i.e., SB-FD and TDD) when calculating the offset between time slots to determine when to expect a PDSCH associated with a given HARQ procedure and when to send HARQ-ACK information for that HARQ procedure relative to the time slot in which the PDSCH is received. In one example offset behavior, the UE determines the time slot offset regardless of the time slot type. In another example offset behavior, the UE ignores the SB-FD time slot when determining the time slot offset. In yet another example offset behavior, the UE ignores the TDD time slot when determining the time slot offset.

[0198] At box 2014, the UE uses the first DL slot offset parameter to determine the offset relative to the first slot associated with HARQ[1] based on the selected offset behavior.

[0199] At box 2016, the UE receives a first PDSCH transmission in a second time slot associated with HARQ[1], the second time slot being offset relative to the first time slot associated with HARQ[1] by the number of time slots corresponding to the first DL time slot offset parameter.

[0200] At box 2018, the UE uses the first HARQ timing parameter to determine the offset relative to the second time slot associated with HARQ[1] based on the selected offset behavior for HARQ[1].

[0201] At box 2020, the UE transmits a first HARQ-ACK message for the first PDSCH in a third time slot associated with HARQ[1], the third time slot being offset relative to the second time slot associated with HARQ[1] by the number of time slots corresponding to the first HARQ timing parameters.

[0202] Meanwhile, at box 2030, the UE receives the second downlink time slot offset parameter in the first time slot associated with HARQ[2]. The UE may also optionally receive the second HARQ timing parameter (also associated with HARQ[2]) in the same time slot. In some respects, the UE may receive the second HARQ timing parameter in any other suitable time slot or by any other suitable means.

[0203] At box 2032, the UE selects the offset behavior for HARQ[2] based on the partition indicator received at box 2002, as described above in conjunction with box 2012.

[0204] At box 2034, the UE uses a second downlink slot offset parameter to determine the offset relative to the first slot associated with HARQ[2] based on the selected offset behavior for HARQ[2].

[0205] At box 2036, the UE receives a second PDSCH transmission in a second time slot associated with HARQ[2]. The second time slot associated with HARQ[2] is offset relative to the first time slot associated with HARQ[2] by the number of time slots corresponding to the second downlink time slot offset parameter.

[0206] At box 2038, the UE uses the second HARQ timing parameters to determine the offset relative to the second time slot associated with HARQ[2] based on the selected offset behavior for HARQ[2].

[0207] At box 2040, the UE transmits second HARQ-ACK information for the second PDSCH in a third time slot associated with HARQ[2], the third time slot being offset relative to the second time slot associated with HARQ[2] by the number of time slots corresponding to the second HARQ timing parameters.

[0208] Other examples with multiple characteristics:

[0209] Example 1: A method, apparatus, and non-transitory computer-readable medium operable by a UE for wireless communication, comprising: receiving a first downlink time slot offset parameter in a first time slot associated with a first Hybrid Automatic Repeat Request (HARQ) procedure. The first HARQ procedure corresponds to a frame structure including one or more sub-band full-duplex (SB-FD) time slots and one or more time-division duplex (TDD) time slots. The example further comprises: receiving a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ procedure. The second time slot associated with the first HARQ procedure is offset relative to the first time slot associated with the first HARQ procedure by a number of time slots corresponding to the first downlink time slot offset parameter. The example further comprises: transmitting first HARQ-ACK information indicating whether the UE has successfully decoded the first PDSCH in a third time slot associated with the first HARQ procedure. The third time slot associated with the first HARQ procedure is offset relative to the second time slot associated with the first HARQ procedure by a number of time slots corresponding to a first HARQ timing parameter.

[0210] Example 2: The method, apparatus, and non-transitory computer-readable medium of Example 1 further includes: receiving the first HARQ timing parameters in the first time slot associated with the first HARQ procedure via the transceiver. This example further includes: receiving a second downlink time slot offset parameter and a second HARQ timing parameter for a second HARQ procedure corresponding to the frame structure in the first time slot associated with the second HARQ procedure. This example further includes: receiving a second physical downlink shared channel in the second time slot associated with the second HARQ procedure. The second time slot associated with the second HARQ procedure is offset relative to the first time slot associated with the second HARQ procedure by a time slot number corresponding to the second downlink time slot offset parameter. This example further includes: transmitting a second acknowledgment corresponding to information received on the second PDSCH in the third time slot associated with the second HARQ procedure. The third time slot associated with the second HARQ procedure is offset relative to the second time slot associated with the second HARQ procedure by a time slot number corresponding to the second HARQ timing parameter. The example also includes receiving a partition indicator indicating a first offset behavior for the first HARQ procedure and a second offset behavior, different from the first behavior, for the second HARQ procedure. In this example, the number of time slots corresponding to the first downlink time slot offset parameter excludes any SB-FD time slots between the first time slot associated with the first HARQ procedure and the second time slot associated with the first HARQ procedure, based on the first offset behavior. In this example, the number of time slots corresponding to the first HARQ timing parameter excludes any SB-FDs between the second time slot associated with the first HARQ procedure and the third time slot associated with the first HARQ procedure, based on the first offset behavior.

[0211] Example 3: According to the method, apparatus, and non-transitory computer-readable medium of Example 2, the number of time slots corresponding to the second downlink time slot offset excludes any TDD time slots between the first time slot associated with the second HARQ procedure and the second time slot associated with the second HARQ procedure, based on the second offset behavior. In this example, the number of time slots corresponding to the second HARQ timing parameter excludes any TDD time slots between the second time slot associated with the second HARQ procedure and the third time slot associated with the second HARQ procedure, based on the second offset behavior.

[0212] Example 4: According to the method, apparatus, and non-transitory computer-readable medium of Example 2, the number of time slots corresponding to the second downlink time slot offset parameter includes any TDD time slots and any SB-FD time slots between the first time slot associated with the second HARQ procedure and the second time slot associated with the second HARQ procedure. In this example, the number of time slots corresponding to the second HARQ timing parameter includes any TDD time slots and any SB-FD time slots between the second time slot associated with the second HARQ procedure and the third time slot associated with the second HARQ procedure.

[0213] Example 5: The method, apparatus, and non-transitory computer-readable medium of Example 1 further includes: selecting an offset action from one of a first offset action or a second offset action for the first HARQ process based on the content of a message associated with at least the first HARQ process. In the first offset action, the number of time slots corresponding to the first downlink time slot offset parameter excludes any SB-FD time slots between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process; and the number of time slots corresponding to the first HARQ timing parameter excludes any SB-FD time slots between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process. In the second offset behavior, the number of time slots corresponding to the first downlink time slot offset parameter includes any SB-FD time slot between the first time slot associated with the first HARQ procedure and the second time slot associated with the first HARQ procedure; and the number of time slots corresponding to the first HARQ timing parameter includes any SB-FD time slot between the second time slot associated with the first HARQ procedure and the third time slot associated with the first HARQ procedure.

[0214] Example 6: The method, apparatus, and non-transitory computer-readable medium of Example 5 further includes: receiving a second downlink time slot offset parameter and a second Hybrid Automatic Repeat Request (HARQ) timing parameter for the second HARQ procedure in a first time slot associated with a second HARQ procedure corresponding to the frame structure. This example further includes: receiving a second physical downlink shared channel in a second time slot associated with the second HARQ procedure. The second time slot associated with the second HARQ procedure is offset relative to the first time slot associated with the second HARQ procedure by a time slot number corresponding to the second downlink time slot offset parameter. This example further includes: transmitting a second acknowledgment corresponding to information received on the second physical downlink shared channel in a third time slot associated with the second HARQ procedure. The third time slot associated with the second HARQ procedure is offset relative to the second time slot associated with the second HARQ procedure by a time slot number corresponding to the second HARQ timing parameter.

[0215] In this example, selecting the offset behavior includes: selecting the first offset behavior for the first HARQ procedure based on the first priority; and selecting the second offset behavior for the second HARQ procedure based on the second priority. In this example, the number of time slots corresponding to the second downlink time slot offset includes, according to the second offset behavior, any SB-FD time slot between the first time slot associated with the second HARQ procedure and the second time slot associated with the second HARQ procedure; in this example, the number of time slots corresponding to the second HARQ timing parameters includes, according to the second offset behavior, any SB-FD time slot between the second time slot associated with the second HARQ procedure and the third time slot associated with the second HARQ procedure.

[0216] Example 7: According to the method, apparatus, and non-transitory computer-readable medium of Example 1, the number of time slots corresponding to the first downlink time slot offset parameter includes any TDD time slots between the first time slot associated with the first HARQ procedure and the second time slot associated with the first HARQ procedure, and any SB-FD time slots between the first time slot associated with the first HARQ procedure and the second time slot associated with the first HARQ procedure. In this example, the number of time slots corresponding to the first HARQ timing parameter includes any TDD time slots between the second time slot associated with the first HARQ procedure and the third time slot associated with the first HARQ procedure, and SB-FD time slots between the second time slot associated with the first HARQ procedure and the third time slot associated with the first HARQ procedure.

[0217] Several aspects of wireless communication networks have been described with reference to exemplary implementations. As will be readily understood by those skilled in the art, the various aspects described throughout this disclosure can be extended to other telecommunications systems, network architectures, and communication standards.

[0218] For example, various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimized (EV-DO). Other examples can 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. The actual telecommunications standards, network architecture, and / or communication standards used will depend on the specific application and the overall design constraints imposed on the system.

[0219] In this disclosure, the term “exemplary” is used 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 superior to other aspects of this disclosure. Similarly, the term “aspect” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term “coupling” is used herein to refer to direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C are still 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 never has direct physical contact with the second object. The terms “circuit” and “circuit system” are used broadly and are intended to include both hardware implementations of electronic devices and conductors (the performance, when connected and configured, capable of realizing the functions described in this disclosure, without limitation on the type of electronic circuit) and software implementations of information and instructions (the performance, when executed by a processor, capable of realizing the functions described in this disclosure).

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

[0221] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged according to design preferences. The appended method claims give the elements of various steps in an exemplary order, and unless specifically stated herein, are not intended to limit us to the given specific order or hierarchy.

[0222] The above description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are consistent with the entire scope of protection of the language of the claims, wherein, unless specifically stated otherwise, references to elements in the singular are not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated otherwise, the term “some” refers to one or more. The phrase “at least one” referring to the list of items means any combination of these 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; a and c; b and c; and a, b, and c. All structures and functions known or to be known by one of ordinary skill in the art that are equivalent to the elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be included in the claims.

[0223] Furthermore, regardless of whether the disclosure is explicitly stated in the claims, the disclosure herein is not intended to be offered to the public. The terms “may” and “can” used in conjunction with aspects and features herein are equivalent and refer to an element present in some aspects but not necessarily in others, or describe an action performed by a particular device or component in one aspect that can be performed by other devices or components in the aspect.

[0224] Furthermore, it should be understood that in some examples, one or more devices (or any other suitable devices) described as performing the processes described herein are tangibly configured to perform all or part of one or more of these processes prior to performing the actions described herein.

Claims

1. A method of wireless communication operable by a user equipment (UE), comprising: receiving, via a transceiver, a first downlink slot offset parameter in a first slot associated with a first hybrid automatic repeat request (HARQ) process, the first HARQ process corresponding to a frame structure comprising one or more sub-band full duplex (SB-FD) slots and one or more time division duplex (TDD) slots, wherein, for the SB-FD slots, a portion of time-frequency resources for a given carrier is used for uplink communication and a portion of the time-frequency resources for the given carrier is used for downlink communication; receiving, via the transceiver, a first transmission in a second slot associated with the first HARQ process, the second slot being offset from the first slot associated with the first HARQ process by one or more slots corresponding to the first downlink slot offset parameter; and transmitting, via the transceiver, first HARQ-acknowledgement (HARQ-ACK) information indicating whether or not the UE successfully decoded the first transmission in a third slot associated with the first HARQ process, the third slot being offset from the second slot associated with the first HARQ process by one or more slots corresponding to a first HARQ timing parameter.

2. The method of claim 1, further comprising: receiving, via the transceiver, the first HARQ timing parameter in the first slot associated with the first HARQ process; receiving, via the transceiver, a second downlink slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure in a first slot associated with the second HARQ process; receiving, via the transceiver, a second transmission in a second slot associated with the second HARQ process, the second slot being offset from the first slot associated with the second HARQ process by one or more slots corresponding to the second downlink slot offset parameter; transmitting, via the transceiver, a second acknowledgement corresponding to information received in the second transmission in a third slot associated with the second HARQ process, the third slot being offset from the second slot associated with the second HARQ process by one or more slots corresponding to the second HARQ timing parameter; and receiving, via the transceiver, a partition indicator indicating a first offset behavior for the first HARQ process and a second offset behavior for the second HARQ process different from the first offset behavior; wherein: the one or more slots corresponding to the first downlink slot offset parameter are excluded from any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process in accordance with the first offset behavior; and the one or more slots corresponding to the second downlink slot offset parameter are excluded from any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process in accordance with the second offset behavior. The one or more slots corresponding to the second downlink slot offset parameter include any TDD slots and any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and 3. The method of claim 2, wherein, The second transmission comprises a physical downlink shared channel (PDSCH) transmission.

4. The method of claim 2, wherein: The one or more slots corresponding to the second downlink slot offset parameter exclude any TDD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process according to the second offset behavior; and The one or more slots corresponding to the second HARQ timing parameter exclude any TDD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process according to the second offset behavior.

5. The method of claim 2, wherein: The one or more slots corresponding to the second downlink slot offset parameter include any TDD slots and any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and The one or more slots corresponding to the second HARQ timing parameter include any TDD slots and any SB-FD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process.

6. The method of claim 1, further comprising: receiving control information, the control information comprising a partition indicator for the frame structure; selecting an offset behavior from one of the following offset behaviors based on the partition indicator: a first offset behavior for the first HARQ process, wherein: The one or more slots corresponding to the first downlink slot offset parameter exclude any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and The one or more slots corresponding to the first HARQ timing parameter exclude any SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process; or a second offset behavior for the first HARQ process, wherein: The one or more slots corresponding to the first downlink slot offset parameter include any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and The one or more slots corresponding to the first HARQ timing parameter include any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process.

7. The method of claim 6, the method further comprising: receiving, via the transceiver, a second downlink slot offset parameter and a second hybrid automatic repeat request (HARQ) timing parameter for a second HARQ process associated with the frame structure in a first slot; receiving, via the transceiver, a second physical downlink shared channel in a second slot associated with the second HARQ process, the second slot being offset from the first slot associated with the second HARQ process by one or more slots corresponding to the second downlink slot offset parameter; and transmitting, via the transceiver, a second acknowledgement corresponding to information received on the second physical downlink shared channel in a third slot associated with the second HARQ process, the third slot being offset from the second slot associated with the second HARQ process by one or more slots corresponding to the second HARQ timing parameter; wherein the control information indicates a first priority associated with the first HARQ process; and the control information further indicates a second priority associated with the second HARQ process, the second priority being different than the first priority; and wherein selecting the offset behavior further comprises: selecting the first offset behavior for the first HARQ process based on the first priority; and selecting the second offset behavior for the second HARQ process based on the second priority; wherein the one or more slots corresponding to the second downlink slot offset parameter include, according to the second offset behavior, any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and wherein the one or more slots corresponding to the second HARQ timing parameter include, according to the second offset behavior, any SB-FD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process.

8. The method of claim 1, wherein: the one or more slots corresponding to the first downlink slot offset parameter include any TDD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process, and any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter include any TDD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process, and any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process. The one or more slots corresponding to the first HARQ timing parameter include any TDD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process, and SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

9. A wireless communication device operable as a user equipment (UE), comprising: one or more processors; a memory coupled to the one or more processors; and a transceiver coupled to the one or more processors; wherein the one or more processors are configured to cause the UE to: receive, via a transceiver, a first downlink slot offset parameter in a first slot associated with a first hybrid automatic repeat request (HARQ) process, the first HARQ process corresponding to a frame structure comprising one or more sub-band full duplex (SB-FD) slots and one or more time division duplex (TDD) slots, wherein, for the SB-FD slots, a portion of time-frequency resources for a given carrier is used for uplink communication and a portion of the time-frequency resources for the given carrier is used for downlink communication; receive, via the transceiver, a first transmission in a second slot associated with the first HARQ process, the second slot being offset relative to the first slot associated with the first HARQ process by one or more slots corresponding to a first HARQ timing parameter; and 10. The wireless communication device of claim 9, wherein, transmit, via the transceiver, first HARQ-acknowledgement (HARQ-ACK) information indicating whether or not the UE successfully decoded the first transmission in a third slot associated with the first HARQ process, the third slot being offset relative to the second slot associated with the first HARQ process by one or more slots corresponding to the first HARQ timing parameter. The one or more processors are further configured to cause the UE to: receive, via the transceiver, the first HARQ timing parameter in the first slot associated with the first HARQ process; receive, via the transceiver, a second downlink slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure in a first slot associated with the second HARQ process; receive, via the transceiver, a second transmission in a second slot associated with the second HARQ process, the second slot being offset relative to the first slot associated with the second HARQ process by one or more slots corresponding to the second downlink slot offset parameter; transmit, via the transceiver, a second acknowledgement corresponding to information received in the second transmission in a third slot associated with the second HARQ process, the third slot being offset relative to the second slot associated with the second HARQ process by one or more slots corresponding to the second HARQ timing parameter; and receiving, via the transceiver, a partition indicator indicating a first offset behavior for the first HARQ process and a second offset behavior for the second HARQ process different from the first offset behavior; wherein: the one or more slots corresponding to the first downlink slot offset parameter exclude, according to the first offset behavior, any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter exclude, according to the first offset behavior, any SB-FD between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

11. The wireless communication device of claim 10, wherein, the second transmission comprises a physical downlink shared channel (PDSCH) transmission.

12. The wireless communication device of claim 10, wherein: the one or more slots corresponding to the second downlink slot offset parameter exclude, according to the second offset behavior, any TDD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and the one or more slots corresponding to the second HARQ timing parameter exclude, according to the second offset behavior, any TDD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process.

13. The wireless communication device of claim 10, wherein: the one or more slots corresponding to the second downlink slot offset parameter include any TDD slots and any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and the one or more slots corresponding to the second HARQ timing parameter include any TDD slots and any SB-FD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process.

14. The wireless communication device of claim 9, wherein, the one or more processors are further configured to cause the UE to: receive control information including a partition indicator for the frame structure; select, based on the partition indicator, an offset behavior from one of: a first offset behavior for the first HARQ process, wherein: the one or more slots corresponding to the first downlink slot offset parameter exclude any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter exclude any SB-FD between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process. the one or more slots corresponding to the first HARQ timing parameter exclude any SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process; or a second offset behavior for the first HARQ process, wherein: the one or more slots corresponding to the first downlink slot offset parameter include any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter include any SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

15. The wireless communication device of claim 14, wherein, the one or more processors are further configured to cause the UE to: receive, via the transceiver, a second downlink slot offset parameter and a second hybrid automatic repeat request (HARQ) timing parameter for a second HARQ process corresponding to a second frame structure in a first slot associated with the second HARQ process; receive, via the transceiver, a second physical downlink shared channel in a second slot associated with the second HARQ process, the second slot being offset from the first slot associated with the second HARQ process by one or more slots corresponding to the second downlink slot offset parameter; and transmit, via the transceiver, a second acknowledgement corresponding to information received on the second physical downlink shared channel in a third slot associated with the second HARQ process, the third slot being offset from the second slot associated with the second HARQ process by one or more slots corresponding to the second HARQ timing parameter; wherein the control information indicates a first priority associated with the first HARQ process; and the control information further indicates a second priority associated with the second HARQ process, the second priority being different than the first priority; and wherein selecting the offset behavior further comprises: selecting the first offset behavior for the first HARQ process based on the first priority; and selecting the second offset behavior for the second HARQ process based on the second priority; wherein the one or more slots corresponding to the second downlink slot offset parameter include, in accordance with the second offset behavior, any SB-FD slots between the first slot associated with the second HARQ process and the second slot associated with the second HARQ process; and wherein the one or more slots corresponding to the second HARQ timing parameter include, in accordance with the second offset behavior, any SB-FD slots between the second slot associated with the second HARQ process and the third slot associated with the second HARQ process.

16. The wireless communication device of claim 9, wherein: the one or more slots corresponding to the first downlink slot offset parameter include any TDD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process, and any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter include any TDD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process, and SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

17. A wireless communication device operable as a user equipment (UE), comprising: means for receiving, in a first slot associated with a first hybrid automatic repeat request (HARQ) process, a first downlink slot offset parameter, the first HARQ process corresponding to a frame structure comprising one or more sub-band full duplex (SB-FD) slots and one or more time division duplex (TDD) slots, wherein, for the SB-FD slots, a portion of time-frequency resources for a given carrier is used for uplink communications and a portion of the time-frequency resources for the given carrier is used for downlink communications; means for receiving, in a second slot associated with the first HARQ process, a first transmission, the second slot being offset from the first slot associated with the first HARQ process by one or more slots corresponding to the first downlink slot offset parameter; and means for transmitting, in a third slot associated with the first HARQ process, first HARQ-ACK information indicating whether or not the UE successfully decoded the first transmission, the third slot being offset from the second slot associated with the first HARQ process by one or more slots corresponding to a first HARQ timing parameter.

18. The wireless communication device of claim 17, further comprising: means for receiving, in the first slot associated with the first HARQ process, the first HARQ timing parameter; means for receiving, in a first slot associated with a second HARQ process, a second downlink slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure; means for receiving, in a second slot associated with the second HARQ process, a second transmission, the second slot being offset from the first slot associated with the second HARQ process by one or more slots corresponding to the second downlink slot offset parameter; a second transmission comprising a physical downlink shared channel (PDSCH) transmission; and a unit for receiving a partition indicator indicating a first offset behavior for the first HARQ process and a second offset behavior for the second HARQ process different from the first offset behavior; wherein: the one or more slots corresponding to the first downlink slot offset parameter exclude, according to the first offset behavior, any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter exclude, according to the first offset behavior, any SB-FD between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

19. The wireless communication device of claim 18, wherein, the second transmission comprises a physical downlink shared channel (PDSCH) transmission.

20. The wireless communication device of claim 17, wherein: the one or more slots corresponding to the first downlink slot offset parameter include, according to the first offset behavior, any TDD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process, and any SB-FD slots between the first slot associated with the first HARQ process and the second slot associated with the first HARQ process; and the one or more slots corresponding to the first HARQ timing parameter include, according to the first offset behavior, any TDD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process, and SB-FD slots between the second slot associated with the first HARQ process and the third slot associated with the first HARQ process.

21. A non-transitory computer-readable medium storing computer-executable code executable by a user equipment (UE), comprising code for causing the UE to: receiving, via the transceiver, a first downlink slot offset parameter in a first slot associated with a first hybrid automatic repeat request (HARQ) process, the first HARQ process corresponding to a frame structure comprising one or more sub-band full duplex (SB-FD) slots and one or more time division duplex (TDD) slots, wherein, for the SB-FD slots, a portion of time-frequency resources for a given carrier is for uplink communication and a portion of the time-frequency resources for the given carrier is for downlink communication; receive, via the transceiver, a first transmission in a second slot associated with the first HARQ process, the second slot being offset, relative to the first slot associated with the first HARQ process, by one or more slots corresponding to the first downlink slot offset parameter; and a second transmission comprising a physical downlink shared channel (PDSCH) transmission. transmit, via the transceiver, first HARQ-ACK information indicating whether the UE successfully decoded the first transmission in a third slot associated with the first HARQ process, the third slot being offset from the second slot associated with the first HARQ process by one or more slots corresponding to a first HARQ timing parameter.

Images