Hybrid automatic repeat request process for sub-band full duplex

Abstract

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

Description

[0001] This application is a divisional application of a patent application filed on May 26, 2021, entitled “Hybrid Automatic Repeat Request Process for Sub-band Full-Duplex” and application number 202180032737.X.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

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

[0004] In general, the techniques discussed below relate to wireless communication systems, and more specifically, the techniques discussed below relate to hybrid automatic repeat request (HARQ). Example deployments may occur in 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. Some aspects may include enabling and providing techniques for communication devices configured to utilize SB-FD time slots and TDD time slots (e.g., in some cases, for separate HARQ processes and / or HARQ process groups). Background Art

[0005] In wireless communications, a full-duplex link is one in which two endpoints can communicate with each other simultaneously on the same set of resources. Many wireless communications systems provide for full-duplex emulation, with two-way simultaneous communication between endpoints, but using different sets of resources for transmissions in different directions. For example, time division duplex (TDD) provides for the use of time division multiplexing to separate transmissions in different directions on a given channel from each other. 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) provides for transmissions in different directions to operate at different carrier frequencies.

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

[0007] As the demand for mobile broadband access continues to grow, research and development continues to advance wireless communication technology, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user's mobile communication experience. As mobile communication technology has evolved, the uses of the technology 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 bandwidth in the downlink direction, but may have only modest uplink requirements. At the same time, real-time applications such as remote control of critical equipment may require extremely low latency but only modest bandwidth requirements. Summary of the invention

[0008] A brief summary of one or more aspects of the present disclosure is provided below to provide a basic understanding of these aspects. The present disclosure is not an exhaustive review of all considered features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a preface to the more detailed description presented later.

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

[0010] One aspect of the present disclosure provides a wireless communication method operable at a user equipment (UE). The method includes: receiving a first downlink time slot offset parameter via a transceiver in a first time slot associated with a first hybrid automatic repeat request (HARQ) process. The first HARQ process 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 also includes: receiving a first physical downlink shared channel (PDSCH) transmission via the transceiver in a second time slot associated with the first HARQ process. The second time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first downlink time slot offset parameter relative to the first time slot associated with the first HARQ process. The method also includes: sending, via the transceiver, a first HARQ-ACK information indicating whether the UE successfully decoded the first PDSCH in a third time slot associated with the first HARQ process. The third time slot associated with the first HARQ process is offset relative to the second time slot associated with the first HARQ process by an amount of time slots corresponding to a first HARQ timing parameter.

[0011] In another aspect of the present 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 in a first time slot associated with a first hybrid automatic repeat request (HARQ) process via the transceiver. The first HARQ process 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 also configured to cause the UE to: receive a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ process via the transceiver. The second time slot associated with the first HARQ process is offset relative to the first time slot associated with the first HARQ process by the 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: send, via the transceiver, first HARQ-ACK information indicating whether the UE successfully decoded the first PDSCH in a third time slot associated with the first HARQ process, the third time slot being offset by a number of time slots corresponding to a first HARQ timing parameter relative to the second time slot associated with the first HARQ process. The third time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

[0012] Another aspect of the present 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) process. The first HARQ process 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 also includes: a unit for receiving a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ process. The second time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first downlink time slot offset parameter relative to the first time slot associated with the first HARQ process. The device also includes: a unit for sending a first HARQ-ACK information indicating whether the UE successfully decoded the first PDSCH in a third time slot associated with the first HARQ process. The third time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

[0013] In another aspect of the present disclosure, a non-transitory computer-readable medium storing computer executable code operable by a user equipment (UE) is provided. The medium includes code for causing the UE to perform the following operations: receiving a first downlink time slot offset parameter in a first time slot associated with a first hybrid automatic repeat request (HARQ) process via a transceiver. The first HARQ process 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 medium also includes code for causing the UE to perform the following operations: receiving a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ process via the transceiver. The second time slot associated with the first HARQ process is offset relative to the first time slot associated with the first HARQ process by the 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 operations: sending, via the transceiver, first HARQ-ACK information indicating whether the UE successfully decoded the first PDSCH in a third time slot associated with the first HARQ process, wherein the third time slot is offset from the second time slot associated with the first HARQ process by a number of time slots corresponding to a first HARQ timing parameter.

[0014] These and other aspects enable a communication system including one or more UEs to adaptively use a sub-band full-duplex time slot format. In some cases, the adaptive or variable use of the SB-FD time slot format can be used together with the time division duplex time slot format. This arrangement can adapt to the bandwidth and latency requirements of various applications and terminal usage scenarios. And as discussed in more detail below, some aspects and different deployments enable and provide a technology for adapting to changes in demand in a short period of time (e.g., a period of several seconds or less or a period involving low-latency communication).

[0015] By browsing the following detailed description, these and other aspects of the present invention will be more completely understood. When browsing the following description of specific, exemplary embodiments in conjunction with the accompanying drawings, other aspects, features and embodiments will become apparent to those of ordinary skill in the art. Although features may be discussed with reference to certain embodiments and figures below, all embodiments may include one or more of the preferred features discussed herein. In other words, although 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. In a similar manner, although exemplary embodiments may be discussed hereinafter as equipment, system or method embodiments, it should be understood that these exemplary embodiments can be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects.

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

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

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

[0021] Figure 6 is a schematic diagram of sub-band full-duplex (SB-FD) communications according to some aspects.

[0022] Figure 7 is a schematic diagram of time slots configured for SB-FD according to some aspects.

[0023] Figure 8 is a schematic diagram of a series of time slots on a flexible duplex carrier and corresponding operation of physically separated and isolated antenna panels in accordance with some aspects.

[0024] Fig. 9 A schematic diagram of a series of time slots on an uplink flexible duplex carrier and a downlink flexible duplex carrier according to some aspects, wherein a 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] Fig.10 is a schematic diagram of a series of time slots on an uplink flexible duplex carrier and a downlink flexible duplex carrier according to some aspects, wherein a UE performs a HARQ process and its corresponding time slot offset calculation only for TDD time slots.

[0026] Fig.11 is a schematic diagram of a series of time slots on an uplink flexible duplex carrier and a downlink flexible duplex carrier according to some aspects, wherein a UE performs a HARQ process and its corresponding time slot offset calculation only for SB-FD time slots.

[0027] Fig.12is a block diagram conceptually illustrating an example of a hardware implementation of a scheduling entity, according to some aspects.

[0028] Fig.13 is a block diagram conceptually illustrating an example of a hardware implementation of a scheduled entity, according to some aspects.

[0029] Fig.14 is a flow chart illustrating an example process for a UE to communicate using one or more downlink HARQ processes on a flexible duplex carrier including TDD and SB-FD time slots in accordance with some aspects.

[0030] Fig.15 is a flow chart illustrating an example process for a UE to communicate using one or more uplink HARQ processes on a flexible duplex carrier including both TDD and SB-FD time slots in accordance with some aspects.

[0031] Fig.16 is a flow chart illustrating an example process for a UE to divide a HARQ process into two groups, wherein the UE calculates slot offsets for a first group based only on TDD slots and calculates slot offsets for a second group based only on SB-FD slots, according to some aspects.

[0032] Fig.17 is a flow chart illustrating an example process for a UE to divide a HARQ process into two groups, wherein the UE calculates slot offsets for a first group based only on TDD slots and calculates slot offsets for a second group based on both TDD and SB-FD slots, according to some aspects.

[0033] Fig.18 is a flow chart illustrating an exemplary process for a UE to calculate a slot offset for low priority HARQ communications based only on TDD slots and to calculate a slot offset for high priority HARQ communications based on both TDD and SB-FD slots in accordance with some aspects.

[0034] Fig.19 is a flow chart illustrating another example process for a UE to schedule HARQ-ACK transmissions when the UE communicates using TDD and SB-FD time slots in accordance with some aspects.

[0035] Fig. 20 is a flow chart illustrating yet another example process for a UE to schedule HARQ-ACK transmissions when the UE communicates using TDD and SB-FD time slots in accordance with some aspects. DETAILED DESCRIPTION

[0036] The specific embodiments described below in conjunction with the accompanying drawings are intended to be descriptions of various configurations, rather than to represent the only configuration in which the concepts described herein are implemented. For the purpose of providing a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is obvious 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 the form of block diagrams to avoid obscuring these concepts.

[0037] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses may occur via integrated chip embodiments and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, devices with AI functions, etc.). Although some examples may or may not be specifically targeted at use cases or applications, the wide applicability of the described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations, and further relate to aggregated, distributed or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the required and described embodiments. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the innovations described herein may be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having various sizes, shapes, and configurations.

[0038] The present disclosure provides several mechanisms and techniques for processing sub-band full-duplex (SB-FD) time slots and time division duplex (TDD) time slots associated with one or more hybrid automatic repeat request (HARQ) processes. Various examples disclosed herein enable devices and systems to interpret HARQ scheduling parameters specified differently 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 be different from each other and may change over time. In some examples, multiple HARQ processes can be divided into one or more groups based on signals sent by a network or device. In other examples, a network or device may send a signal identifying the priority of one or more individual HARQ processes.

[0039] It will be understood that while certain examples are discussed with respect to features or operations of a scheduled entity such as a user equipment (UE) or other device, aspects of the present disclosure relate to and may implicitly describe corresponding features and operations of one or more scheduling entities (e.g., base stations and similar devices and systems). Similarly, while certain examples are discussed with respect to downlink or uplink communications, it will be understood that the various examples will apply to uplink or downlink communications, respectively. In addition, the aspects and features discussed herein may be used in an open RAN deployment, which may include various units and components, such as a remote unit (RU), a centralized unit (CU), and a distributed unit (DU). Deployment may also occur in a peer or sidelink scenario that may or may not use controlled scheduling but instead uses device self-organizing type communications.

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

[0041] The various concepts presented throughout this disclosure may be implemented in a wide variety of telecommunication systems, network architectures and communication standards. Figure 1 , various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as a non-limiting illustrative example. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to communicate data with an external data network 110, such as (but not limited to) the Internet.

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

[0043] As shown, the RAN 104 includes a number of base stations 108. In broad terms, a base station is a network element in a radio access network that is responsible for transmission and reception to or from a UE in one or more cells. A base station (BS) may also be referred to differently by those skilled in the art as a base transceiver (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), or some other suitable terminology in different technologies, standards, or contexts.

[0044] Also shown is a radio access network 104 that supports wireless communications for multiple mobile devices. Mobile devices are referred to as user equipment (UE) in the 3GPP standards, but may also be referred to as mobile stations (MS), user stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other appropriate terminology by those of ordinary skill in the art. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[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 device refers to a wide variety of devices and technologies. A UE may include a plurality of hardware structural components of a size, shape, and arrangement to facilitate communication; such components may 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 (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, 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 may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may additionally be a digital home or smart home device, such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. The mobile device may also be a smart energy device, security device, solar panel or solar array, municipal infrastructure equipment that controls power (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise equipment; logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, etc. Further, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or priority access to other types of information, for example, in terms of priority access to the transmission of critical service data and / or the associated QoS of the transmission of critical service data.

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

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

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

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

[0050] Typically, the base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of the wireless communication system. The backhaul 120 may provide a link between the base stations 108 and the core network 102. Additionally, in some examples, the backhaul network may provide interconnections between the various base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, etc.

[0051] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the 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 a RAN 200 is provided by way of example and not limitation. In some examples, the RAN 200 may be similar to that described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular areas (cells) that may 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 are shown, as well as a small cell 208, 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. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into multiple sectors, multiple sectors within a cell may be formed by antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0053] exist Figure 2 , 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 may have an integrated antenna or may be connected to an antenna or RRH by a feeder cable. In the illustrated example, when base stations 210, 212, and 214 support cells with large sizes, cells 202, 204, and 126 may be referred to as macro cells. In addition, a base station 218 is shown in a small cell 208 (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home node B, a home eNodeB, etc.) that may overlap with one or more macro cells. In this example, since base station 218 supports cells with relatively small sizes, cell 208 may be referred to as a small cell. Cell sizing may be accomplished based on system design and component constraints.

[0054] It should be understood that the radio access network 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless 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 similar to those described above and described in Figure 1 The base station / scheduling entity 108 shown in FIG.

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

[0056] Within the RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the respective cells. Figure 1 ) access point. 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 through RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base station 220. In some examples, UE 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can communicate with the above-described and Figure 1 The UE / scheduled entity 106 shown in FIG. 1 is the same as that shown in FIG.

[0057] In some examples, a mobile network node (eg, quadcopter 220) may be configured to act as a UE. For example, quadcopter 220 may 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 signals 227 without relaying communications through a base station (e.g., base station 212). In another example, UE 238 is shown as communicating with UEs 240 and 242. Here, UE 238 can be used as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can be used as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE can be used 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 the 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 having a cellular configuration, a P2P configuration, or a mesh configuration, a scheduling entity and one or more scheduled entities may communicate using the scheduled resources.

[0059] The air interface in the radio access network 200 may use one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and in order to multiplex DL transmissions from the base station 210 to one or more UEs 222 and 224, orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) is utilized. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform-spread-OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UE 222 and UE 224 may be provided using 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.

[0060] Will refer to Figure 3Various aspects of the present disclosure are described with reference to the OFDM waveform schematically illustrated in FIG. It should be understood by those of ordinary skill in the art that various aspects of the present disclosure can be applied to DFT-s-OFDMA waveforms in substantially the same manner as described herein below. That is, although some examples of the present 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] In this disclosure, a frame may generally refer to a duration of 10 ms for wireless transmission, where each frame consists of 10 subframes of 1 ms each. On a given carrier, there may be one set of frames in the UL and another set of frames in the DL. Now referring to Figure 3 , shows an expanded view of an exemplary DL subframe 302 showing an OFDM resource grid 304. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein according to any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers or tones in the vertical direction.

[0062] The 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 plurality of resource grids 304 can be used for communication. The resource grid 304 is divided into a plurality of resource elements (REs) 306. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete portion 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, a block of REs can be referred to as a physical resource block (PRB), or a 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] A UE typically uses only a subset of the resource grid 304. An RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, the higher the modulation scheme selected for the air interface, and the higher the data rate for the UE.

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

[0065] Each subframe 302 (eg, a 1 ms subframe) may be composed 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, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Other examples may include mini-slots with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). These mini-slots can be sent in some cases occupying resources scheduled for ongoing time slot transmissions for the same or different UEs.

[0066] An expanded view of one of the time slots 310 shows the time slot 310 including a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 may carry data channels. Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The structure shown in is merely exemplary in nature, and different slot structures may be used and may include one or more of each of the control region and the data region.

[0067] Despite Figure 3 Although not shown in the figure, various REs 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilot or reference signals. These pilot or reference signals may provide a receiving device with the ability to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control and / or data channels within the RB 308.

[0068] In a DL transmission, a transmitting device (e.g., a scheduling entity 108 or a base station 108) may allocate one or more REs 306 (e.g., within a control region 312) for carrying DL control information 114 to one or more scheduled entities or UEs 106, including one or more DL control channels that typically carry information originating from higher layers (e.g., a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc.). In addition, DL REs may be allocated to carry DL physical signals that typically do not 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] The synchronization signals PSS and SSS (collectively referred to as SS), and in some examples, the PBCH, may be sent in an SS block comprising 4 consecutive OFDM symbols, numbered in increasing order from 0 to 3 via a time index. In the frequency domain, the SS block may extend over 240 consecutive subcarriers, where the subcarriers are numbered in increasing order from 0 to 239 via a frequency index. Of course, the present disclosure is not limited to this particular SS block configuration. Other non-limiting examples within the scope of the present disclosure may use more or less than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit the PBCH; and / or may use non-contiguous symbols for the SS block.

[0070] The PDCCH may 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, grants, and / or allocation of REs for DL ​​and UL transmissions.

[0071] In UL transmission, a transmitting device (e.g., scheduled entity 106) may utilize one or more REs 306 to carry UL control information 118 (UCI). The UCI may originate from higher layers 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.). In addition, the UL REs may 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 the scheduling entity 108 to schedule an uplink transmission. In this context, in response to the SR sent on the control channel 118, the scheduling entity 108 may send DCI 114, which may schedule resources for uplink packet transmission.

[0072] The UCI may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or a negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technique known to those of ordinary skill in the art, in which the integrity of packet transmissions may be checked on the receiving side for accuracy, for example, using any suitable integrity check mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if not, a NACK may be sent. In response to the NACK, the transmitting device may send a HARQ retransmission, which may implement catch-up combining, incremental redundancy, and the like. However, conventional HARQ techniques do not consider a frame structure including SB-FD time slots other than time slot duplex types (e.g., TDD time slots, such as uplink time slots, downlink time slots, or "special" time slots). As used herein, the term "time slot duplex type" should be understood to describe the duplex configuration of the associated time slot, including but not limited to SB-FD and TDD time slot duplex types.

[0073] In addition to control information, one or more REs 306 may be allocated for user data or traffic data (e.g., within data region 314). Such traffic may be carried on one or more traffic channels, such as the physical downlink shared channel (PDSCH) for DL ​​transmissions or the physical uplink shared channel (PUSCH) for UL transmissions.

[0074] In order for the UE to obtain initial access to a cell, the RAN may provide system information (SI) that characterizes the cell. The system information may be provided using minimum system information (MSI) and other system information (OSI). The MSI may be broadcast periodically on the cell to provide the most basic information required for initial cell access, as well as for obtaining any OSI that may be broadcast periodically or sent on demand. In some examples, the MSI may be provided on two different downlink channels. For example, the PBCH may carry a master information block (MIB) and the PDSCH may carry a system information block type 1 (SIB1). In the art, SIB1 may be referred to as remaining minimum system information (RMSI).

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

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

[0077] These aforementioned physical channels are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. Transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0078] The air interface in the radio access network 200 may use one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other simultaneously on the same set of resources. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Full-duplex simulation is often implemented for wireless links by using frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate on different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at certain times, the channel is dedicated to transmissions in one direction (e.g., DL), and at other times, the channel is dedicated to transmissions in another direction (e.g., UL), where the direction can change very quickly, for example, several times per time slot.

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

[0080] However, even with this physical separation of the transmit and receive antenna panels, wireless communication endpoints performing full-duplex communication still face significant interference. In particular, the self-interference generated at the same endpoint can be large. That is, because the transmit antenna and receive antenna at the base station are very close to each other, the base station will also cause interference to the nearby receive antenna when sending downlink signals. This can make it difficult for the base station to decode the received UL signal.

[0081] One 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, typically, UL and DL communications 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. And in some 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 what may be referred to as sub-band full duplex (SB-FD) or flexible duplex. SB-FD differs from conventional FDD in that, in FDD, a given carrier is typically fully dedicated to either UL or DL ​​communications. 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. Thus, endpoint communications using SB-FD transmit and receive simultaneously but on different frequency resources of the same carrier. That is, DL resources are separated from UL resources 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 separated from each other in frequency, with a guard band (GB) between the respective UL and DL portions to reduce interference, such as UL leakage to DL or leakage DL to UL. However, because the GB may be relatively narrow (e.g., 5 RBs) compared to the spacing between carriers in conventional FDD, wireless communications using SB-FD may suffer from a greater amount of interference than conventional FDD. With respect to self-interference, a base station using SB-FD may suffer from its DL transmissions leaking into its UL reception; and a UE using SB-FD may suffer from its UL transmissions leaking into its DL reception.

[0083] Reference again Figure 4 , when communicating with an SB-FD carrier, the base station may use panel 1 for DL ​​transmission on one portion of the SB-FD carrier while using panel 2 for UL reception on another portion of the SB-FD carrier. Thus, via the physical isolation of the antennas, self-interference at the base station may be reduced to some extent. In various examples, the respective UL and DL portions of the SB-FD carrier may be allocated within a given time slot using any suitable configuration, separated by frequency, time, or both frequency and time.

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

[0085] Figure 8 A sequence 800 of four consecutive time slots 802, 804, 806 and 808 in a carrier is shown, which is configured to allow dynamic reconfiguration between time slots for TDD and SB-FD communications. In some examples, the various parts of the carrier within a given time slot can be designated as UL parts or DL ​​parts by the base station, and are sent to the UE by using a suitable indication or configuration message that enables the UE to determine the time slot format. For example, the UE can determine the time slot format of a given time slot based on a suitable indication or configuration message provided by the base station. The indication or configuration message may be included in the DCI, in a high-level (e.g., RRC) signaling, or in some combination of these. The time slot format corresponds to the RE configuration within the time slot, where each RE is designated as being used for UL, DL, or in some examples, flexible (can be UL or DL). In various examples, the configuration or indication message 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 full carrier bandwidth is used for DL ​​communications, rather than the last one or two OFDM symbols of the time slot, where the full carrier bandwidth can be used for UL communications, 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 as described above and in Figure 7 SB-FD configuration is utilized in substantially the same manner as shown in , with DL communications in the upper and lower portions of the carrier and UL communications in between. As discussed above, the UL portion of the carrier is shown separated from the DL portion of the carrier by appropriate bandwidth guard bands above and below the UL portion. While the fourth time slot 808 is configured for TDD, it is used entirely for UL communications.

[0087] In the above-described and Figure 4 In the example of a base station with two antenna panels shown in FIG. , the operation of each antenna panel during different time slots is Figure 8That is, in the first time slot 802, both antenna panels are used for DL ​​communication; and in the fourth time slot 808, both antenna panels are used for UL communication. In the second and third time slots 804 and 806 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 for asynchronous HARQ in the uplink and downlink. Therefore, for HARQ between a base station and a UE, HARQ timing information must be provided by the base station to the UE. The UE may receive the HARQ timing information via the DCI of the PDCCH sent by the base station, via RRC signaling sent by the base station, or via other applicable control signaling sent by the base station. The HARQ timing information for DL ​​may 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 process. 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 process. The uplink time slot offset parameter K2 defines the time slot offset between the time slot carrying the UL scheduling information in the PDCCH and the time slot carrying the corresponding scheduled PUSCH sent by the UE for the corresponding UL HARQ process.

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

[0090] Fig. 9An illustrative sequence of time slots 900 (e.g., a frame or a portion of a frame) corresponding to a DL HARQ process (i.e., a DL HARQ process is allocated to operate on a DL transmission on the depicted sequence of time slots) and an illustrative sequence of time slots 930 (e.g., a frame or a portion of a frame) corresponding to a UL HARQ process (i.e., a UL HARQ process is allocated to operate on a UL transmission on the depicted sequence of time slots) are shown in accordance with one aspect of the present disclosure. Any of these HARQ processes may correspond to a UE (e.g., Figure 1 and / or Figure 2 106, 234, 236, 238 of the UE 106, 234, 236, 238). The frame structure of both the DL HARQ process and the UL HARQ process includes a combination of SB-FD time slots and TDD time slots (e.g., an uplink time slot specified by "U" and a downlink time slot specified by "D"). Herein, "TDD time slot" may refer to a time slot with an uplink, downlink or "special" time slot duplex type. In the example shown, each time slot sequence 900 and 930 includes a 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 example shown, according to one aspect of the present disclosure, the UE is configured to: send and receive information on a carrier according to one or more HARQ processes, and calculate a corresponding time slot offset, regardless of the time slot duplex type. Therefore, the UE can consider at least the TDD and SB-FD time slot duplex types when calculating the time slot offset, and can send and receive data corresponding to the DL HARQ process and the UL HARQ process in the TDD time slot and the SB-FD time slot, regardless of the time slot duplex type of the PDCCH, PDSCH or PUSCH on which the time slot offset calculation is based.

[0091] Referring first to the time slot sequence 900 corresponding to the DL HARQ process (i.e., the DL HARQ process is assigned to operate on the DL transmission on the depicted time slot sequence), the UE can receive control signaling. A control signal can be received from a base station via a control channel (e.g., PDCCH 904) in a DL time slot 902, the control signal including scheduling information for a 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, the DL time slot 902 is configured for TDD. The PDCCH 904 may also include a DCI defining a time slot offset parameter K0=1 and a HARQ timing parameter K1=1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided by the base station to the UE at a time before the DL time slot 902 may define parameters K0 and K1 for the DL HARQ process.

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

[0093] Upon receiving the PDSCH 908 at the DL time slot 906, the UE may calculate one or more CRCs for one or more TBs included in the PDSCH 908. The UE may then compare the corresponding CRC bits received in the 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 TBs. For example, the UE may send an ACK to the base station in response to determining that the received CRC bits match the calculated CRC bits. The ACK may indicate that the UE has successfully received and correctly decoded the PDSCH 908. Alternatively, the UE may send a NACK to the base station in response to determining that the received CRC bits do not match the calculated CRC bits. The NACK may indicate that the UE did not successfully receive and decode the PDSCH 908. The base station may view the NACK as a request for a HARQ retransmission of the information included in the PDSCH 908.

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

[0095] In the example shown, after receiving ACK / NACK 912 in SB-FD slot 910, the base station can send DCI. The DCI is carried in PDCCH 916, which is sent 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). In addition, in the PDCCH 916 carried in the 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 may calculate a slot offset relative to a DL slot 914 (e.g., a slot carrying a corresponding PDCCH 916) based on a slot offset parameter indicating two slots (i.e., K0=2) to determine that the base station will send a corresponding scheduled PDSCH 920 in an SB-FD slot 918 two slots later. As shown, the SB-FD slot 918 is configured for SB-FD. Likewise, in this example, the UE may calculate this slot offset between the DL slot 914 and the SB-FD slot 918, regardless of the slot duplex type of the DL slot 914, the SB-FD slot 918, and any other slots therebetween (if such slots exist).

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

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

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

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

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

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

[0102] Fig.10 An illustrative sequence of time slots 1000 (e.g., a frame or a portion of a frame) corresponding to a DL HARQ process and an illustrative sequence of time slots 1030 (e.g., a frame or a portion of a frame) corresponding to a UL HARQ process are shown according to another aspect of the present disclosure. Any of these HARQ processes may correspond to a UE (e.g., Figure 1 and / or Figure 2 106, 234, 236, 238 of the UE 106, 234, 236, 238). The frame structure of both the DL HARQ process and the UL HARQ process includes a combination of SB-FD time slots and TDD time slots (e.g., uplink time slots designated by "U" and downlink time slots designated by "D"). In the example shown, each time slot sequence 1000 and 1030 includes an illustrative time slot pattern DDD (SB-FD) U, which can be repeated over the length of the frame. In the example shown, according to one aspect of the present disclosure, the UE is configured to: send and receive information on a carrier according to one or more HARQ processes, and calculate a corresponding time slot offset (e.g., only for TDD time slots) excluding SB-FD time slots. Therefore, when calculating the time slot offset based on parameters K0, K1, and K2, the UE can ignore or skip the time slots of the SB-FD time slot duplex type. After receiving the PDCCH corresponding to a given HARQ process, the UE can send and receive information corresponding to the HARQ process (e.g., via PDSCH, PUSCH and / or ACK / NACK) only in time slots of TDD time slot duplex types (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 process, the UE can receive PDCCH 1004 from the base station in the 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 an initial transmission or a HARQ retransmission. Here, the DL time slot 1002 is configured for TDD. PDCCH 1004 may also include a DCI defining a time slot offset parameter K0=1 and a HARQ timing parameter K1=1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided by the base station to the UE at a time before the DL time slot 1002 may define parameters K0 and K1 for the DL HARQ process.

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

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

[0106] In the example shown, after receiving ACK / NACK 1012 in UL slot 1011, the base station can send DCI in PDCCH 1016 carried in DL slot 1014. Although the DCI in PDCCH 1016 can include updated values ​​of parameters K0 and K1 in some aspects of the present disclosure, the DCI does not include such updates in the example shown. In PDCCH 1016 carried in DL slot 1014, the base station can send 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 the 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 send the corresponding scheduled PDSCH 1020 in DL slot 1017 one slot later. As shown, DL slot 1017 is configured for TDD. Likewise, in this example, the UE may calculate the timeslot offset between DL timeslot 1014 and DL timeslot 1017, excluding timeslots of the SB-FD timeslot duplex type, if such timeslots exist.

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

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

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

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

[0111] In the example shown, after receiving PUSCH 1038 in UL time slot 1037, the base station can send DCI in PDCCH 1042 carried in DL time slot 1040 to update the value of slot offset parameter K2 (K2=1). In addition, in PDCCH 1042 carried in DL time slot 1040, the base station can send 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 time slot 1040 is also configured for TDD.

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

[0113] Fig.11 An illustrative sequence of time slots 1100 (e.g., a frame or a portion of a frame) corresponding to a DL HARQ process and an illustrative sequence of time slots 1130 (e.g., a frame or a portion of a frame) corresponding to a UL HARQ process are shown according to another aspect of the present disclosure. Any of these HARQ processes may correspond to a UE (e.g., Figure 1 and / or Figure 2106, 234, 236, 238 of the UE 106, 234, 236, 238). The frame structure of both the DL HARQ process and the UL HARQ process includes a combination of SB-FD time slots and TDD time slots (e.g., uplink time slots designated by "U" and downlink time slots designated by "D"). In the example shown, each time slot sequence 1100 and 1130 includes an illustrative time slot pattern DDD (SB-FD) U, which can be repeated over the length of the frame. In the example shown, according to one aspect of the present disclosure, the UE is configured to: send and receive information on a carrier according to one or more HARQ processes, 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 type (e.g., including UL, DL and special time slot duplex types). After receiving the PDCCH corresponding to a given HARQ process, the UE may send and receive information corresponding to the HARQ process (eg, via PDSCH, PUSCH, and / or ACK / NACK) only in slots of the SB-FD slot duplex type.

[0114] First, referring to the time slot sequence 1100 corresponding to the DL HARQ process, the UE can receive PDCCH 1104 from the base station in the SB-FD time 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 an initial transmission or a HARQ retransmission. Here, the SB-FD time slot 1102 is configured for SB-FD. PDCCH 1104 may also include a DCI defining a time slot offset parameter K0=0 and a HARQ timing parameter K1=1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided by the base station to the UE at a time before the SB-FD time slot 1102 may define parameters K0 and K1 for the DL HARQ process.

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

[0116] When PDSCH 1106 is received in SB-FD time 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 time slot offset relative to SB-FD time slot 1102 (e.g., the time slot carrying the scheduled PDSCH) based on the HARQ timing parameter K1 to determine the time slot in which to send the corresponding ACK / NACK 1110. Since the HARQ timing parameter K1=1 (i.e., one time slot) in the example shown, and the UE is configured to exclude TDD time slots, the UE sends ACK / NACK 1110 in SB-FD time slot 1108. As shown, SB-FD time slot 1108 is configured for SB-FD. Again, in this example, the UE can calculate this time slot offset between SB-FD time slot 1102 and SB-FD time slot 1108, excluding time slots of TDD time slot duplex type, if such time 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 is actually five slots because the UE excludes TDD slots from the slot offset calculation. The UE may then wait until it receives another PDCCH from the base station.

[0117] Referring now to the time slot sequence 1130 corresponding to the UL HARQ process, the UE may receive a PDCCH 1134 from the base station in the SB-FD time 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 an initial transmission or a HARQ retransmission. Here, the SB-FD time slot 1132 is configured for SB-FD. The PDCCH 1134 may also include a DCI defining a time slot offset parameter K2=1. Alternatively, another control signal (e.g., a previous PDCCH or RCC signaling) provided by the base station to the UE at a time prior to the SB-FD time slot 1132 may define the parameter K2 for the UL HARQ process.

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

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

[0120] The scheduling entity 1200 may include a 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, gating logic, discrete hardware circuits, and other appropriate hardware configured to perform the various functions described throughout the present disclosure. In various examples, the scheduling entity 1200 may be configured to perform any one or more of the functions described herein. That is, the processor 1204 (as used in the scheduling entity 1200) may be used to implement any one or more of the processes and procedures described below.

[0121] In this example, the processing system 1214 may include a bus architecture, generally represented by bus 1202. Bus 1202 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1214 and the overall design constraints. Bus 1202 communicatively couples various circuits including one or more processors (generally represented by processor 1204), memory 1205, and computer-readable media (generally represented by computer-readable media 1206). Bus 1202 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and 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 on 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 the present disclosure, processor 1204 may include a slot formatting circuit 1240 configured (e.g., in conjunction with slot formatting instructions 1252) for various functions, including, for example, determining and communicating a slot format to one or more UEs, including portions of a slot for UL communications, for DL ​​communications, or, in some examples, resources that may be flexibly allocated for UL or DL ​​communications. Processor 1204 may also include a resource scheduling circuit 1242 configured (e.g., in conjunction with resource scheduling instructions 1254) for various functions, including, for example, determining and communicating a resource allocation (e.g., grant) for one or more slots or for one or more carriers to one or more UEs.

[0123] The processor 1204 is responsible for managing the bus 1202 and general processing, including executing software stored on the computer-readable medium 1206. The software may include time slot formatting instructions 1252 and resource scheduling instructions 1254. When the processor 1204 executes the software, the software causes the processing system 1214 to perform the various functions described below for any particular device. As an example, the processor 1204 can use the time slot formatting circuit 1240 to determine a time slot sequence including any suitable combination of TDD and SB-FD time slots as described herein, and determine the priority of the HARQ-ACK process for these time slots, taking into account the time slot format of the various time slots and the priority of the communication associated with these time slots. The computer-readable medium 1206 and the memory 1205 can also be used to store data manipulated by the processor 1204 when 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 to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc. The software can be located on a computer-readable medium 1206. The computer-readable medium 1206 can be a non-transitory computer-readable medium. For example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer readable medium 1206 may be located within the processing system 1214, external to the processing system 1214, or distributed among multiple entities including the processing system 1214. The computer readable medium 1206 may be embodied by a computer program product. For example, a computer program product may include a computer readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the entire system.

[0125] Fig.13 1300 using a processing system 1314. According to various aspects of the present disclosure, the processing system 1314 including one or more processors 1304 can implement the elements, or any portion of the elements, or any combination of the elements. For example, the scheduled entity 1300 can be such as Figure 1 and / or Figure 2 Any one or more of the UEs shown in the figures.

[0126] The processing system 1314 can be substantially connected to Fig.12 The processing system 1214 shown in FIG. 1 is the same as that shown in FIG. 1 , including: a bus interface 1308, a bus 1302, a memory 1305, a processor 1304, and a computer readable medium 1306. In addition, the scheduled entity 1300 may include a processor 1304 that is essentially the same as that shown in FIG. Fig.12 That is, the processor 1304 (as used in the scheduled entity 1300) can be used to implement the following and Figure 14-Figure 20Any one or more of the processes shown in .

[0127] In some aspects of the present disclosure, the processor 1304 may include a HARQ circuit 1340 configured for various functions, including, for example, processing communications associated with one or more active HARQ processes, calculating a time slot offset for one or more active HARQ processes, and / or determining whether an ACK or NACK should be sent based on one or more TBs and / or CRC of a (e.g., received) PDSCH. For example, the HARQ circuit 1340 may be configured (e.g., in conjunction with the HARQ instructions 1352) to implement the following instructions for Figure 14-18 Processor 1304 may also include a communication controller 1342 that is configured (eg, in conjunction with communication instructions 1354) for various functions including, for example, communicating over one or more wireless carriers.

[0128] UE DL HARQ process

[0129] Certain aspects of the present disclosure provide mechanisms and algorithms to handle communications associated with one or more active HARQ processes for a frame structure that includes both TDD time slots and SB-FD time slots.

[0130] Although the following description refers to Figure 14-18 , Figure 14-18 The process occurring at the UE is described, but it should be understood that the present disclosure is not limited to the operations or processes at the UE. That is, the following description also describes the processes and operations occurring at the base station, and the present disclosure is written to fully disclose the operations at both endpoints of the signaling exchange between the UE and the base station.

[0131] Fig.14 1400 is a flow chart illustrating an exemplary process 1400 for a UE to perform communication operations associated with one or more DL HARQ processes. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 14 may perform process 1400. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1400. In some examples, process 1400 may be performed by Fig.13 The scheduling entity or UE 1300 is shown to be executed.

[0132] In some examples, process 1400 may be performed by any suitable device or unit for performing the functions or algorithms described below. In one example, process 1400 may be performed by a processor such as processor 1304 of scheduled entity 1300 (e.g., UE) using HARQ processing circuits and communication controllers (e.g., HARQ circuits 1340 and communication controllers 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 may receive control information (e.g., via DCI, RRC signaling, and / or another applicable control signaling) from a base station via a transceiver (e.g., transceiver 1310) using a communication controller (e.g., communication controller 1342). The control information defines a slot offset parameter K0 and a HARQ timing parameter K1 for one or more HARQ processes in conjunction with a frame structure having both TDD time slots and SB-FD time slots.

[0134] At block 1404, the UE receives a PDCCH in a first time slot via a transceiver using a communication controller. The PDCCH includes DL scheduling information. For example, the DL scheduling information may define resource blocks in which the base station will send a PDSCH to the UE.

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

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

[0137] At block 1410, the UE calculates one or more CRCs for the TBs of the PDSCH using the HARQ circuitry. The UE compares the calculated CRCs with the received CRCs using the HARQ circuitry to determine whether the UE should send an ACK or a NACK to the base station. For example, if the UE determines that the compared CRCs match, the UE may determine that the UE should send an ACK to the base station for the received TBs. For example, if the UE determines that the compared CRCs do not match, the UE may determine that the UE should send a NACK to the base station for the received TBs.

[0138] At block 1412, the UE identifies a third time slot in which to send an ACK / NACK by calculating a time slot offset relative to the time slot carrying the PDSCH (i.e., the first time slot) based on the HARQ timing parameter K1. As indicated above, in some cases, the UE may 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 may be configured to count time slots of all time slot duplex types when calculating the time slot offset.

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

[0140] At block 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 block 1404.

[0141] It should be understood that certain aspects of example process 1400 and other processes described herein may involve and may implicitly describe features or operations of a scheduling entity (e.g., a base station communicating with the above-mentioned UE). For example, a base station may generate or otherwise receive desired time slot offsets for various HARQ processes 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 another example, the base station may determine the priority of each HARQ-ACK process, or the priority of a request received from a network or another device such as a UE, and transmit the desired time slot offset for the HARQ-ACK process to the UE based on those priorities.

[0142] UE UL HARQ process

[0143] Fig.151 is a flow chart illustrating an exemplary process 1500 for a UE to perform communication operations associated with one or more UL HARQ processes. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1500 may perform process 1500. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1500.

[0144] In some examples, process 1500 can be performed by any suitable device or unit for performing the functions or algorithms described below. In one example, process 1500 can be performed by a processor of UE 1304, such as scheduled entity 1300, using HARQ processing circuits and communication controllers (e.g., HARQ circuits 1340 and communication controllers 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 receives control information (e.g., via DCI, RRC signaling, and / or another applicable control signaling) from a base station using a transceiver (e.g., transceiver 1310) and a communication controller. The control information defines a slot offset parameter K2 for one or more HARQ processes in conjunction with a frame structure that includes both TDD slots and SB-FD slots.

[0146] At block 1504, the UE receives, via the transceiver, a PDCCH including a UL grant from the base station. For example, the UL grant may define resources in which the UE will send a PUSCH to the base station.

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

[0148] At block 1508, the UE transmits a PUSCH to the base station via the transceiver in the time slot using the communications controller.

[0149] At block 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 block 1504.

[0150] UE HARQ process with HARQ process group excluding SB-FD and excluding TDD

[0151] Fig.16 16 is a flow chart illustrating an exemplary process 1600 for a UE to perform communication operations associated with a first set of HARQ processes and a second set of HARQ processes. For the first set of HARQ processes, the UE is configured to exclude SB-FD time slots (i.e., time slots with a SB-FD time slot duplex type) when performing time slot offset calculations. For the second set of HARQ processes, the UE is configured to exclude TDD time slots (i.e., time slots with a TDD time slot duplex type) when performing time slot offset calculations. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1 may perform process 1600. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1600. In some examples, in addition to the first and second groups of HARQ processes, the UE may also manage additional HARQ processes regardless of the time slot duplex type, as described above in conjunction with Fig. 9 as described.

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

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

[0154] At block 1604, for the first set of DL HARQ processes, the UE performs Fig.14 The process 1400 is performed while excluding the SB-FD time slots when calculating the time slot offset.

[0155] At block 1606, for the first set of UL HARQ processes, the UE performs Fig.15 Process 1500 while excluding the SB-FD time slots when calculating the time slot offset.

[0156] At block 1608, for the second set of DL HARQ processes, the UE performs Fig.14 Process 1400 while excluding TDD time slots when calculating the time slot offset.

[0157] At block 1610, for the second set of UL HARQ processes, the UE performs Fig.15 Process 1500 while excluding TDD time slots when calculating the time slot offset.

[0158] It should be understood that the order in which blocks 1604-1610 are performed as shown herein is illustrative and not limiting. Blocks 1604-1610 may be performed in any desired order.

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

[0160] UE HARQ process with SB-FD excluded and fully included HARQ process partitioning

[0161] Fig.17 1700 is a flow chart illustrating an exemplary process 1700 for a UE to perform communication operations associated with a first set of HARQ processes and a second set of HARQ processes. For the first set of HARQ processes, the UE is configured to exclude SB-FD time slots (i.e., time slots with a SB-FD time slot duplex type) when performing time slot offset calculations. For the second set of HARQ processes, the UE is configured to perform time slot offset calculations without regard to the time slot duplex type. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1700 may perform process 1700. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1700.

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

[0163] At block 1702, the processor assigns the HARQ process to the first group or the second group based on the partition indicator. The UE may receive control information (e.g., DCI, RRC signaling, or other control information) including the partition indicator from a base station using a communication controller and a transceiver (e.g., transceiver 1310). In this example, for the HARQ process of the first group, the UE is configured (including its HARQ circuitry) to exclude SB-FD time slots from the time slot offset calculation. For the HARQ process 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 block 1704, for the first set of DL HARQ processes, the UE performs Fig.14 The process 1400 is performed while excluding the SB-FD time slots when calculating the time slot offset.

[0165] At block 1706, for the first set of UL HARQ processes, the UE performs Fig.15 Process 1500 while excluding the SB-FD time slots when calculating the time slot offset.

[0166] At block 1708, for the second set of DL HARQ processes, the UE performs Fig.14 Process 1400 regardless of the time slot duplex type.

[0167] At block 1710, for the second set of UL HARQ processes, the UE performs Fig.15 Process 1500 regardless of the time slot duplex type.

[0168] It should be understood that the order in which blocks 1704-1710 are performed is illustrative and not limiting. Blocks 1704-1710 may be performed in any desired order.

[0169] It should be understood that the execution process 1700 can be used to divide multiple HARQ processes into two subsets: a first subset in which HARQ scheduling parameters are calculated only for TDD time slots, and a second subset in which HARQ scheduling parameters are calculated without distinguishing between TDD, SB-FD and / or other time slot formats. In some examples, the HARQ process belonging to the first subset can operate only on the TDD time slot, while the HARQ process belonging to the second subset can operate on both TDD and SB-FD time slots. In some examples, the process 1700 and other processes disclosed herein can be performed as part of a communication scheme that can provide multiple communication service levels customized for different devices and services on the same network resources. As a non-limiting example, the network can provide an "enhanced mobile broadband" (eMBB) service level and an "ultra-reliable low-latency communication" (URLLC) service level, as defined in Release 16 of the 3GPP 5G NR standard. In one specific non-limiting example, HARQ processes associated with eMBB data services may be assigned to the first subset described in conjunction with process 1700, and HARQ processes associated with URLLC services may be assigned to the second subset described in conjunction with process 1700.

[0170] HARQ process based on UE priority

[0171] Fig.18 1 is a flow chart illustrating an exemplary process 1800 for a UE to perform communication operations associated with an active HARQ process to handle transmissions with a defined priority. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1800 may perform process 1800. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1800.

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

[0173] At block 1802, the UE receives control information (e.g., DCI, RRC signaling, or other applicable control information) including a priority indicator using a communications controller and a transceiver coupled to the communications controller (e.g., transceiver 1310). The priority indicator may define a high or low priority level for a corresponding transmission to be processed by the UE in conjunction with an active HARQ process. In this example, for low priority transmissions, the processor is configured (including its HARQ circuitry) to exclude SB-FD time slots 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 block 1804, the UE determines a priority for the transmission based on the priority indicator.

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

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

[0177] At block 1810, in response to determining that the transmission is a low priority DL transmission, the UE performs Fig.14 The process 1400 is performed while excluding the SB-FD time slots when calculating the time slot offset.

[0178] At block 1812, in response to determining that the transmission is a low priority UL transmission, the UE performs Fig.15 Process 1500 while excluding the SB-FD time slots when calculating the time slot offset.

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

[0180] At block 1816, in response to determining that the transmission is a high priority DL transmission, the UE performs Fig.14 Process 1400 regardless of the time slot duplex type.

[0181] At block 1818, in response to determining that the transmission is a high priority UL transmission, the UE performs Fig.15 Process 1500 regardless of the time slot duplex type.

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

[0183] It should be understood that the above-described methods and devices implementing these methods can be used to confer certain technical advantages, including enabling higher bandwidth communications and lower latency communications for different types of devices or users of these devices. In addition, by prioritizing communications that require particularly low latency over lower priority communications, improvements in overall network capacity and performance metrics can be achieved, ensuring that service level targets for a range of different devices can be met without investing in reducing latency for all connected devices or increasing available bandwidth for each expected device that may be connected to the wireless communication network. In addition, the service level provided to each connected device does not have to be static and can be adjusted based on input from the user or without human intervention by employing computing 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 procedures:

[0185] Fig.19 1 is a flow chart illustrating an exemplary process 1900 for a UE to perform communication operations associated with an active HARQ process to process transmissions associated with a frame structure having TDD and SB-FD time slots. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1300 may perform process 1900. In some examples, any suitable device or unit for performing the functions or algorithms described below may perform process 1900.

[0186] In some examples, process 1900 may be performed by any suitable device or unit for performing the functions or algorithms described below. In one example, process 1900 may be performed by a processor (e.g., UE 1304 of scheduled entity 1300), using HARQ processing circuits and communication controllers (e.g., HARQ circuits 1340 and communication controllers 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 can use a communication controller and a transceiver to receive a first downlink time slot offset parameter and a first HARQ timing parameter for a first hybrid automatic repeat request (HARQ) process corresponding to a frame structure including at least one time slot of a sub-band full-duplex (SB-FD) time slot duplex type and at least one time slot of a time division duplex (TDD) time slot duplex type.

[0188] At block 1904, the UE receives first downlink scheduling information using a communications controller and a transceiver in a first time slot associated with a first HARQ process.

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

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

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

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

[0193] Fig. 202 is a flow chart illustrating another exemplary process 2000 for a UE to perform communication operations associated with an active HARQ process to process transmissions associated with a frame structure having TDD and SB-FD time slots. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required for implementation of all embodiments. In some examples, Fig.13 The scheduled entity or UE 1300 shown in FIG. 1 may perform process 2000. In some examples, process 2000 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0194] In some examples, process 2000 may be performed by any suitable device or unit for performing the functions or algorithms described below. In one example, process 2000 may be performed by a processor (e.g., UE 1304 of scheduled entity 1300), using HARQ processing circuits and communication controllers (e.g., HARQ circuits 1340 and communication controllers 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 block 2002, the UE receives a partition indicator for a frame structure including both SB-FD time slots and TDD time slots. In this example, the UE is configured to operate two HARQ processes, denoted as "HARQ[1]" and "HARQ[2]". The UE then proceeds to blocks 2010-2020 (where the UE performs actions associated with HARQ[1]) and blocks 2030-2040 (where the UE performs actions associated with HARQ[2]).

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

[0197] At block 2012, the UE selects an offset behavior for HARQ[1] based on the partition indicator received at block 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 process, and when to send HARQ-ACK information for that HARQ process relative to the time slot in which the PDSCH was received. In one example offset behavior, the UE determines the time slot offset without regard to the time slot type. In another example offset behavior, the UE ignores SB-FD time slots when determining the time slot offset. In another example offset behavior, the UE ignores TDD time slots when determining the time slot offset.

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

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

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

[0201] At box 2020, the UE sends first HARQ-ACK information for the first PDSCH in a third time slot associated with HARQ[1], and the third time slot is offset from the second time slot associated with HARQ[1] by a number of time slots corresponding to the first HARQ timing parameter.

[0202] At the same time, at block 2030, the UE receives a second downlink time slot offset parameter in the first time slot associated with HARQ [2]. The UE also optionally receives a second HARQ timing parameter (also associated with HARQ [2]) in the same time slot. In some aspects, 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 an 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 the second downlink time slot offset parameter to determine an offset relative to the first time slot associated with HARQ[2] based on the selected offset behavior for HARQ[2].

[0205] At block 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 by a number of time slots corresponding to a second downlink time slot offset parameter relative to the first time slot associated with HARQ[2].

[0206] At box 2038, the UE uses the second HARQ timing parameter to determine an offset relative to a second time slot associated with HARQ[2] according to the selected offset behavior for HARQ[2].

[0207] At box 2040, the UE sends second HARQ-ACK information for the second PDSCH in a third time slot associated with HARQ[2], which is offset from the second time slot associated with HARQ[2] by a number of time slots corresponding to the second HARQ timing parameter.

[0208] Other examples with multiple characteristics:

[0209] Example 1: Methods, apparatus, and non-transitory computer-readable media for wireless communications operable by a UE, comprising: receiving a first downlink time slot offset parameter in a first time slot associated with a first hybrid automatic repeat request (HARQ) process. The first HARQ process 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 also includes: receiving a first physical downlink shared channel (PDSCH) transmission in a second time slot associated with the first HARQ process. The second time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first downlink time slot offset parameter relative to the first time slot associated with the first HARQ process. The example also includes: sending a first HARQ-ACK information indicating whether the UE successfully decoded the first PDSCH in a third time slot associated with the first HARQ process. The third time slot associated with the first HARQ process is offset by a number of time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

[0210] Example 2: The method, apparatus, and non-transitory computer-readable medium according to Example 1 further include: receiving the first HARQ timing parameter in the first time slot associated with the first HARQ process via the transceiver. The example also includes: receiving a second downlink time slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure in a first time slot associated with a second HARQ process. The example also includes: receiving a second physical downlink shared channel in a second time slot associated with the second HARQ process. The second time slot associated with the second HARQ process is offset by a number of time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process. The example also includes: sending a second confirmation corresponding to the information received on the second PDSCH in a third time slot associated with the second HARQ process. The third time slot associated with the second HARQ process is offset by a number of time slots corresponding to the second HARQ timing parameter relative to the second time slot associated with the second HARQ process. The example also includes receiving a partition indicator indicating a first offset behavior for the first HARQ process and a second offset behavior for the second HARQ process that is different from the first behavior. In the 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 process and the second time slot associated with the first HARQ process according to the first offset behavior. In the example, the number of time slots corresponding to the first HARQ timing parameter excludes any SB-FD between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process according to the first offset behavior.

[0211] Example 3: A method, apparatus, and non-transitory computer-readable medium according to Example 2, wherein 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 process and the second time slot associated with the second HARQ process according to 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 process and the third time slot associated with the second HARQ process according to the second offset behavior.

[0212] Example 4: A method, apparatus, and non-transitory computer-readable medium according to Example 2, wherein 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 process and the second time slot associated with the second HARQ process. 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 process and the third time slot associated with the second HARQ process.

[0213] Example 5: The method, apparatus, and non-transitory computer-readable medium according to Example 1 further include: selecting an offset behavior from one of a first offset behavior for the first HARQ process or a second offset behavior for the first HARQ process based on the content of a message associated with at least the first HARQ process. In the first offset behavior, 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 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 includes 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.

[0214] Example 6: The method, apparatus, and non-transitory computer-readable medium according to Example 5 further include: receiving a second downlink time slot offset parameter and a second hybrid automatic repeat request (HARQ) timing parameter for a second HARQ process in a first time slot associated with the second HARQ process corresponding to the frame structure. The example also includes: receiving a second physical downlink shared channel in a second time slot associated with the second HARQ process. The second time slot associated with the second HARQ process is offset by the number of time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process. The example also includes: sending a second confirmation corresponding to information received on the second physical downlink shared channel in a third time slot associated with the second HARQ process. The third time slot associated with the second HARQ process is offset by the number of time slots corresponding to the second HARQ timing parameter relative to the second time slot associated with the second HARQ process.

[0215] In this example, selecting the offset behavior includes: 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. In this example, the number of time slots corresponding to the second downlink time slot offset includes any SB-FD time slots between the first time slot associated with the second HARQ process and the second time slot associated with the second HARQ process according to the second offset behavior; in this example, the number of time slots corresponding to the second HARQ timing parameter includes any SB-FD time slots between the second time slot associated with the second HARQ process and the third time slot associated with the second HARQ process according to the second offset behavior.

[0216] Example 7: A method, apparatus, and non-transitory computer-readable medium according to Example 1, wherein 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 process and the second time slot associated with the first HARQ process, and 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. 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 process and the third time slot associated with the first HARQ process, and 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.

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

[0218] For example, various aspects may 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 (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard used will depend on the specific application and the overall design constraints imposed on the system.

[0219] In the present disclosure, the word "exemplary" is used to mean "serving as an example, instance or illustration". Any implementation or aspect described as "exemplary" in this article is not necessarily to be interpreted as preferred or more advantageous than other aspects of the present disclosure. Similarly, the term "aspect" does not require that all aspects of the present disclosure include the discussed features, advantages or modes of operation. The term "coupling" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C can still be considered to be coupled to each other - even if they are not directly physically in contact with each other. For example, a first object can be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" and "circuitry" are used in a broad sense and are intended to include both hardware implementations and conductors of electronic devices (when they are connected and configured to achieve the performance of the functions described in the present disclosure, without limitation to the type of electronic circuits) and software implementations of information and instructions (when executed by a processor, it can achieve the performance of the functions described in the present disclosure).

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

[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 may be rearranged based on design preferences. The accompanying method claims present elements of the various steps in an example order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated therein.

[0222] The above description is provided to enable any person skilled in the art to implement the various aspects described herein. Various modifications of these aspects are obvious to those skilled in the art, and the general principles defined herein can 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 claim language, wherein, unless otherwise specified, references to elements in the singular form are not intended to refer to "one and only one", but to "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. The phrase "at least one" mentioned in the list of items refers to 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 equivalent to the elements of the various aspects described throughout the present disclosure that are known or to be known to those of ordinary skill in the art are hereby expressly incorporated herein by reference, and are intended to be included in the claims.

[0223] In addition, no matter whether the disclosure is explicitly recited in the claims, the content disclosed herein is not intended to be dedicated to the public. The terms "may" and "can" used in conjunction with the aspects and features of this document are equivalent and refer to elements that are present in some aspects but not necessarily in other aspects, or describe actions performed by a specific device or component in one aspect that can be performed by other devices or components in the aspect.

[0224] Additionally, it should be understood that in some examples, one or more devices described as performing the processes described herein (or any other suitable devices) are tangibly configured to perform all or a portion 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 time slot offset parameter in a first time slot associated with a first hybrid automatic repeat request (HARQ) process, the first HARQ process corresponding 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; receiving, via the transceiver, a first transmission in a second time slot associated with the first HARQ process, the second time slot being offset relative to the first time slot associated with the first HARQ process by one or more time slots corresponding to the first downlink time slot offset parameter; as well as First HARQ-acknowledgement (HARQ-ACK) information indicating whether the UE successfully decoded the first transmission is sent via the transceiver in a third time slot associated with the first HARQ process, and the third time slot is offset by one or more time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

2. The method according to claim 1, wherein: The first transmission includes a grant of resources.

3. The method according to claim 1, wherein: The first transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

4. The method according to claim 1, further comprising: receiving, via the transceiver, the first HARQ timing parameter in the first time slot associated with the first HARQ process; receiving, via the transceiver, in a first time slot associated with the second HARQ process, a second downlink time slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure; receiving, via the transceiver, a second transmission in a second time slot associated with the second HARQ process, the second time slot being offset by one or more time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process; transmitting, via the transceiver, a second acknowledgment corresponding to information received in the second transmission in a third time slot associated with the second HARQ process, the third time slot being offset relative to the second time slot associated with the second HARQ process by one or more time slots corresponding to the second HARQ timing parameter; as well as 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 that is different from the first behavior; in: The one or more time slots corresponding to the first downlink time slot offset parameter exclude any SB-FD time slot between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process according to the first offset behavior; and The one or more time slots corresponding to the first HARQ timing parameters exclude any SB-FD between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process according to the first offset behavior.

5. The method according to claim 4, wherein: The second transmission includes a grant of resources.

6. The method according to claim 4, wherein: The second transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

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

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

9. The method according to claim 1, further comprising: Based on the content of the message associated with at least the first HARQ process, an offset behavior is selected from one of the following offset behaviors: A first offset behavior for the first HARQ process, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter exclude any SB-FD time slot between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process; and The one or more time slots corresponding to the first HARQ timing parameters exclude any SB-FD time slot between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process; or A second offset behavior for the first HARQ process, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter include 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 one or more time slots corresponding to the first HARQ timing parameters include 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.

10. The method according to claim 9, further comprising: receiving, via the transceiver, a second downlink time slot offset parameter and a second hybrid automatic repeat request (HARQ) timing parameter for a second HARQ process corresponding to the frame structure in a first time slot associated with the second HARQ process; receiving, via the transceiver, a second physical downlink shared channel in a second time slot associated with the second HARQ process, the second time slot being offset by one or more time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process; as well as transmitting, via the transceiver, a second acknowledgment corresponding to information received on the second physical downlink shared channel in a third time slot associated with the second HARQ process, the third time slot being offset relative to the second time slot associated with the second HARQ process by one or more time slots corresponding to the second HARQ timing parameter; wherein the message indicates a first priority associated with the first HARQ process; and the message further indicates a second priority associated with the second HARQ process, the second priority being different from the first priority; and Wherein, selecting the offset behavior further includes: 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 time slots corresponding to the second downlink time slot offset include any SB-FD time slots between the first time slot associated with the second HARQ process and the second time slot associated with the second HARQ process according to the second offset behavior; and The one or more time slots corresponding to the second HARQ timing parameters include any SB-FD time slots between the second time slot associated with the second HARQ process and the third time slot associated with the second HARQ process according to the second offset behavior.

11. The method according to claim 1, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter include any TDD 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 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 one or more time slots corresponding to the first HARQ timing parameters include any TDD time slots between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process, and an SB-FD time slot between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process.

12. A wireless communication device operable as a user equipment (UE), comprising: one or more processors; a memory coupled to the one or more processors; as well as a transceiver coupled to the one or more processors; The one or more processors are configured to cause the UE to perform the following operations: 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) process, the first HARQ process corresponding 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; receiving, via the transceiver, a first transmission in a second time slot associated with the first HARQ process, the second time slot being offset relative to the first time slot associated with the first HARQ process by one or more time slots corresponding to the first downlink time slot offset parameter; and First HARQ-acknowledgement (HARQ-ACK) information indicating whether the UE successfully decoded the first transmission is sent via the transceiver in a third time slot associated with the first HARQ process, and the third time slot is offset by one or more time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

13. The wireless communication device according to claim 12, wherein: The first transmission includes a grant of resources.

14. The wireless communication device according to claim 12, wherein: The first transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

15. The wireless communication device according to claim 12, wherein: The one or more processors are further configured to cause the UE to perform the following operations: receiving, via the transceiver, the first HARQ timing parameter in the first time slot associated with the first HARQ process; receiving, via the transceiver, in a first time slot associated with the second HARQ process, a second downlink time slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure; receiving, via the transceiver, a second transmission in a second time slot associated with the second HARQ process, the second time slot being offset by one or more time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process; transmitting, via the transceiver, a second acknowledgment corresponding to information received in the second transmission in a third time slot associated with the second HARQ process, the third time slot being offset relative to the second time slot associated with the second HARQ process by one or more time slots corresponding to the second HARQ timing parameter; as well as 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 that is different from the first behavior; in: The one or more time slots corresponding to the first downlink time slot offset parameter exclude any SB-FD time slot between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process according to the first offset behavior; and The one or more time slots corresponding to the first HARQ timing parameters exclude any SB-FD between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process according to the first offset behavior.

16. The wireless communication device according to claim 15, wherein: The second transmission includes a grant of resources.

17. The wireless communication device according to claim 15, wherein: The second transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

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

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

20. The wireless communication device according to claim 12, wherein: The one or more processors are further configured to cause the UE to perform the following operations: Based on the content of the message associated with at least the first HARQ process, an offset behavior is selected from one of the following offset behaviors: A first offset behavior for the first HARQ process, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter exclude any SB-FD time slot between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process; and The one or more time slots corresponding to the first HARQ timing parameters exclude any SB-FD time slot between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process; or A second offset behavior for the first HARQ process, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter include 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 one or more time slots corresponding to the first HARQ timing parameters include 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.

21. The wireless communication device according to claim 20, wherein: The one or more processors are further configured to cause the UE to perform the following operations: receiving, via the transceiver, a second downlink time slot offset parameter and a second hybrid automatic repeat request (HARQ) timing parameter for a second HARQ process corresponding to the frame structure in a first time slot associated with the second HARQ process; receiving, via the transceiver, a second physical downlink shared channel in a second time slot associated with the second HARQ process, the second time slot being offset by one or more time slots corresponding to the second downlink time slot offset parameter relative to the first time slot associated with the second HARQ process; as well as transmitting, via the transceiver, a second acknowledgment corresponding to information received on the second physical downlink shared channel in a third time slot associated with the second HARQ process, the third time slot being offset relative to the second time slot associated with the second HARQ process by one or more time slots corresponding to the second HARQ timing parameter; wherein the message indicates a first priority associated with the first HARQ process; and the message further indicates a second priority associated with the second HARQ process, the second priority being different from the first priority; and Wherein, selecting the offset behavior further includes: 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 time slots corresponding to the second downlink time slot offset include any SB-FD time slots between the first time slot associated with the second HARQ process and the second time slot associated with the second HARQ process according to the second offset behavior; and The one or more time slots corresponding to the second HARQ timing parameters include any SB-FD time slots between the second time slot associated with the second HARQ process and the third time slot associated with the second HARQ process according to the second offset behavior.

22. The wireless communication device of claim 12, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter include any TDD 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 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 one or more time slots corresponding to the first HARQ timing parameters include any TDD time slots between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process, and an SB-FD time slot between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process.

23. A wireless communication device operable as a user equipment (UE), comprising: means for receiving a first downlink time slot offset parameter in a first time slot associated with a first hybrid automatic repeat request (HARQ) process, the first HARQ process corresponding 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; means for receiving a first transmission in a second time slot associated with the first HARQ process, the second time slot being offset relative to the first time slot associated with the first HARQ process by one or more time slots corresponding to the first downlink time slot offset parameter; as well as A unit for sending first HARQ-ACK information indicating whether the UE successfully decoded the first transmission in a third time slot associated with the first HARQ process, wherein the third time slot is offset from the second time slot associated with the first HARQ process by one or more time slots corresponding to a first HARQ timing parameter.

24. The wireless communication device according to claim 23, wherein: The first transmission includes a grant of resources.

25. The wireless communication device of claim 23, wherein: The first transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

26. The wireless communication device of claim 23, further comprising: means for receiving the first HARQ timing parameter in the first time slot associated with the first HARQ process; means for receiving, in a first time slot associated with the second HARQ process, a second downlink time slot offset parameter and a second HARQ timing parameter for a second HARQ process corresponding to the frame structure; means for receiving a second transmission in a second time slot associated with the second HARQ process, the second time slot being offset relative to the first time slot associated with the second HARQ process by one or more time slots corresponding to the second downlink time slot offset parameter; means for sending a second acknowledgment corresponding to information received in the second transmission in a third time slot associated with the second HARQ process, the third time slot being offset relative to the second time slot associated with the second HARQ process by one or more time slots corresponding to the second HARQ timing parameter; as well as means 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 that is different from the first behavior; in: The one or more time slots corresponding to the first downlink time slot offset parameter exclude any SB-FD time slot between the first time slot associated with the first HARQ process and the second time slot associated with the first HARQ process according to the first offset behavior; and The one or more time slots corresponding to the first HARQ timing parameters exclude any SB-FD between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process according to the first offset behavior.

27. The wireless communication device according to claim 26, wherein: The second transmission includes a grant of resources.

28. The wireless communication device of claim 26, wherein: The second transmission comprises a Physical Downlink Shared Channel (PDSCH) transmission.

29. The wireless communication device of claim 23, wherein: The one or more time slots corresponding to the first downlink time slot offset parameter include any TDD 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 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 one or more time slots corresponding to the first HARQ timing parameters include any TDD time slots between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process, and an SB-FD time slot between the second time slot associated with the first HARQ process and the third time slot associated with the first HARQ process.

30. A non-transitory computer-readable medium storing computer-executable code operable by a user equipment (UE), comprising code for causing the UE to: 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) process, the first HARQ process corresponding 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; receiving, via the transceiver, a first transmission in a second time slot associated with the first HARQ process, the second time slot being offset relative to the first time slot associated with the first HARQ process by one or more time slots corresponding to the first downlink time slot offset parameter; as well as First HARQ-ACK information indicating whether the UE successfully decoded the first transmission is sent via the transceiver in a third time slot associated with the first HARQ process, and the third time slot is offset by one or more time slots corresponding to the first HARQ timing parameter relative to the second time slot associated with the first HARQ process.

Images